I know that G50+ is not expected to work, but I'm reporting what happens with my card.
Created attachment 16844 [details] 2008 05 31 X log
Anything in the kernel log?
Created attachment 16906 [details] Kernel log Ignore the installing nvidia part at the bottom (nv won't pick up my monitor correctly).
Created attachment 18046 [details] X log 2008 07 31 Updated X log
Created attachment 18047 [details] 2008 07 31 Kernel log
I think the lack of voodoo is the issue. This can be extracted from a mmio-trace. So the first step would be to get a mmio-trace, if you haven't already got one.
Sending an MMIO trace now.
Also happens on my 8400 GS. (II) [drm] DRM interface version 1.3 (II) [drm] DRM open master succeeded. (II) NOUVEAU(0): [drm] Using the DRM lock SAREA also for drawables. (II) NOUVEAU(0): [drm] framebuffer handle = 0xd0000000 (II) NOUVEAU(0): [drm] added 1 reserved context for kernel (II) NOUVEAU(0): X context handle = 0x1 (II) NOUVEAU(0): [drm] installed DRM signal handler (EE) NOUVEAU(0): Failed to allocate memory for framebuffer! Fatal server error: AddScreen/ScreenInit failed for driver 0 Can I help?
Created attachment 19503 [details] 2008 10 07 Xorg log I've sent the MMIO trace, is there any progress on this? Should I resend?
Created attachment 20046 [details] 2008 11 04 Xorg log This log seems less noisy than before.
Created attachment 20047 [details] 2008 11 04 Kernel Log Updated Kernel log
I had the same problem with a 7900 GS and fixed it by removing frame buffer support from the kernel. Is there any chance that doing so works for you?
Nov 4 18:24:16 belthazor-saved kernel: [27911.257328] [drm:nv50_graph_init_ctxctl] *ERROR* no ctxprog for chipset NV94 This means someone needs to extract one from a mmio-trace.
I've already sent one (Comment #7). What should I do to make sure this one gets picked up? Will just mentioning the bug report number be enough?
Can you update to latest DRM git and try again, I just added the necessary data to get NV94 up and running.
Created attachment 20800 [details] 2008 12 03 Xorg log It displays some garbage on the screen as well as the X cursor (which I can move) but then it crashes.
Created attachment 20801 [details] 2008 12 03 Kernel log
Did you send that mmio-trace to mmio.dumps@gmail.com? Because i can't find it.
I've just sent another trace, but nVidia's driver seemed to act strange while traced. It never displays it's splash screen, for example, but while mmiotrace was enabled it did (linux 2.6.27.9-custom). X also didn't last that long, once it came up.
Created attachment 21285 [details] A small change. Try this patch, maybe it helps.
Created attachment 21608 [details] 2009 01 01 Xorg log Tried your patch, X still opens up and crashes. Nothing else but the initial garabage is ever drawn. It seems that the resolution appears to be the correct one though, as I can kind of tell from the X mouse I get.
Created attachment 21609 [details] 2009 01 01 Kernel log
Can you please retry with latest drm git.
Created attachment 22918 [details] Working Xorg log Starts up perfectly now. Switching to VT and back fails, and changing resolutions sort of works, but leaves artifacts and displaces the mouse. I will open up new bugs :-)
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.