If I emerge nvidia-kernel-1.0.6229 and nvidia-glx, the X server malfunctions on my laptop. backing off to 1.0.6111 makes it work again. Reproducible: Always Steps to Reproduce: startx with a driver of "nvidia" Actual Results: screwed-up screen: The general appearance is blank with assorted horizontal white lines. Returning to the console often leaves it in a state with washed-out (whiteish) colors. Expected Results: X windows goodness. from /proc/pci: I/O at 0x7400 [0x743f]. Bus 1, device 0, function 0: VGA compatible controller: nVidia Corporation NV17 [GeForce4 440 Go 64M] (re v 163). IRQ 11. Master Capable. Latency=248. Min Gnt=5.Max Lat=1. Non-prefetchable 32 bit memory at 0xe2000000 [0xe2ffffff]. Prefetchable 32 bit memory at 0xf0000000 [0xf7ffffff]. Prefetchable 32 bit memory at 0xf8000000 [0xf807ffff].
Try this with the latest 1.0.7667 driver. Let me know if you're still having problems.
Created attachment 62943 [details] Xorg server configuration file I upgraded to nvidia-glx-1.0.7667 and nvidia-kernel-1.0.7667. It works fine on the laptop's LCD, but when I try to run it in dual-screen mode with the LCD as :0.0 + an SVideo output as :0.1, it locks up the whole machine. The LCD appears as blocky white, black, blue and pink noise. The host stops responding to pings. I have to hold down the power button to turn it off. Needless to say I'll be retreating to 6111. Things are getting ugly back here in Working Driver Land. I'm having to avoid modern versions of opengl-update and xorg-x11 because they conflict with it.
I have upgraded from kernel 2.4.28-gentoo-r9 to 2.6.12-gentoo-r6 (final blocking issue has been resolved for me). Now nvidia-kernel-1.0.7667 supports the dual-screen LCD/SVideo output I need. I have not tested kernel 2.6.12 with other versions of the nvidia driver. I'm not sure how you could adjust portage to warn people of potential problems when nvidia > 6111 interacts with 2.4.*. I also do not know if this problem affects more than just my laptop. I'm not sure if a resolution of WONTFIX or FIXED is more appropriate.
So if I'm running a new kernel nvidia-kernel-1.0.7667 should work? Is anything being done about this problem or is this bug basically waiting for ner kernel/nvidia-kernel versions to resolve?
As stated, this works fine in 2.6 and causes some problem in 2.4 with the 6* drivers, so I'm not sure this is really worth looking into much further.
