Created attachment 52902 [details]
I have an old Geforce2Go card (NV11). The nouveau framebuffer is working fine (KMS enabled), but X won't start with the nouveau driver (it's okay with fbdev):
[ 54.231] (II) NOUVEAU(0): Opened GPU channel 1
[ 54.231] (II) NOUVEAU(0): [DRI2] Setup complete
[ 54.231] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau_vieux
[ 54.231] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau_vieux
[ 54.233] (EE) NOUVEAU(0): Error allocating scanout buffer: 0
Fatal server error:
[ 54.233] AddScreen/ScreenInit failed for driver 0
I'm on Fedora 15 and I have tried with the latest packaged driver and with a build of xf86-video-nouveau from git.
xf86-video-nouveau: git 29 Oct 2011
I'm not interested in 3D, but I can't work out if there's something I've failed to disable. If you need me to enable more debug, please point to some instructions on how to do this.
dmesg, Xorg logs & cfg attached.
Created attachment 52903 [details]
Created attachment 52904 [details]
Does it work if you lower bpp/resolution for framebuffer and/or xserver?
On Sat, Oct 29, 2011 at 11:26:59PM +0100, Chris Paulson-Ellis wrote:
> On 29/10/11 22:06, Chris Paulson-Ellis wrote:
> > On 29/10/11 14:10, email@example.com wrote:
> >> https://bugs.freedesktop.org/show_bug.cgi?id=42384
> >> --- Comment #3 from Marcin Slusarz<firstname.lastname@example.org>
> >> 2011-10-29 13:10:12 UTC ---
> >> Does it work if you lower bpp/resolution for framebuffer and/or xserver?
> > Can't get bugzilla to work for this comment at present,...
Then please CC email@example.com - mails will be automatically
appended to bugreport.
> > Yes. It works if I reduce the framebuffer and the X server to 800x600
> > 16bpp. Just reducing to 16bpp doesn't work. Just changing the X server
> > doesn't work, I have to change the framebuffer too.
> > The card has 64MiB.
Nouveau detects only 16 MB of VRAM. Can you verify it by looking at the card?
According to http://www.nvidia.com/page/geforce2go.html there were 16, 32
and 64 MB versions of GeForce2 Go.
Very similar bug was reported few months ago:
Can you test patch (hack) posted there?
> I can also get it to work using "NoAccel", including at full 1600x1200,
> depth 24, although obviously with fbdev-like performance.
Note: that's almost half of your VRAM.
You're absolutely right. The VRAM is 16Mb. I was misled by the GART aperture being 64Mb.
No need for the hack. I managed to get it working by setting the framebuffer to 8bpp at the lowest resolution listed in the modelines from the Xorg log (640x350). I can then get X working at full resolution as long as I use 16bpp. These together account for <4Mb, so something is being profligate with the VRAM, but it works, so I'm happy. Thankyou for your help.
For the record, I put the following on the end of the kernel line in grub.conf:
and my xorg.conf looks like this:
I'll attach new logs.
Created attachment 52921 [details]
dmesg for working config
Created attachment 52922 [details]
xorg log for working config
Created attachment 52923 [details]
working xorg config
I'm willing to do testing if you want to make changes to make cards such as mine work out of the box, but I'm guessing you've got bigger fish to fry than to worry about such ancient hardware!
Many thanks for your efforts on the driver.
(In reply to comment #9)
> I'm willing to do testing if you want to make changes to make cards such as
> mine work out of the box, but I'm guessing you've got bigger fish to fry than
> to worry about such ancient hardware!
> Many thanks for your efforts on the driver.
Thanks for reporting, this should be fixed now with the latest nouveau kernel module (commit http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?id=787ffe1f651ce3af0d90040ec1c93f0ad177b3de).
I can confirm that with this fix (and everything else in the current nouveau linux git tree), I can now boot without a kernel command line video= parameter and without an xorg.conf.
Both the framebuffer and the X server use the full 1600x1200 of my laptop panel and X creates a 24 bit depth display.
Many thanks again,
I have this same problem. How can I install this patch? Do you know when it will make it into the ubuntu edgers binaries?
A patch referencing this bug report has been merged in Linux v3.2-rc2:
Author: Francisco Jerez <firstname.lastname@example.org>
Date: Sun Nov 6 21:21:28 2011 +0100
drm/nv10: Change the BO size threshold determining the memory placement range.