After installing gentoo-kernel 2.4.20 and the NVidia driver( kernel and GLX ) 1.0.3123, I started X and got a trashed display. The only way to restore the screen was to reboot the machine. I also tried the NVidia driver 1.0.4191 with the same results. I logged the X output, but there was no information indicating an error occurred. Both versions of the NVidia driver work fine when using gentoo-kernel 2.4.19. I searched the nvidia discussion groups( http://www.nvnews.net/vbulletin/ forumdisplay.php?s=&forumid=14 ) and found a few references to the same problem, but no resolution from NVidia. Reproducible: Always Steps to Reproduce: 1. 2. 3. Gentoo linux kernel 2.4.20-r1 Athlon XP 2000 CPU ASUS A7N8X motherboard (NForce2 based). MSI GeForce4-Ti 4600 GPU
Same problem over here, posted this message on the forum: I have exact the same problem. When doing a startx I only get a scrambled screen and my machine locks (even ctrl-alt-del doesn't work). I have build my base system using the stable packages after the RC3 release (gcc, binutils, etc.). When I started the "desktop installation" I did an ACCEPT_KEYWORDS="~x86" emerge kde to get xfree 4.3.0 I have a GeForce 4 Ti 4400 with an Athlon-XP and PDCraid. I'm building my machine with CFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer". Started at stage one. I have tried every combination with: glibc-2.3.1-r2.ebuild gcc-3.2.2.ebuild gentoo-sources-2.4.19-r10.ebuild gentoo-sources-2.4.20-r1.ebuild xfree-4.3.0.ebuild nvidia-glx-1.0.3123.ebuild + nvidia-kernel-1.0.4191-r1.ebuild nvidia-glx-1.0.4191-r1.ebuild + nvidia-kernel-1.0.3123-r2.ebuild I have tried virtually almost every possible combination in XF86Config. If I don't use the nVidia-driver I can do startx, but with the nVidia-driver I get a scrambled screen. I don't know if the problem is between: gentoo-sources and nvidia-drivers xfree 4.3.0 and nvidia-drivers gcc / binutils / glibc and nvidia-drivers Hence it can be something completely else. This is driving me crazy. I won't give up but I need to be sure what combination you people have that works. I don't even dream of finding a solution soon, but you friendly people can help me if you can confirm / decline what combination you have working I would be very happy. Specially the people who installed their system after RC3 or are completely sure that their system is equally build (emerge sync && emerge world -up is not always the same because it's possible that not ALL packages are build with latest gcc, glibc, binutils; using the --emptytree is more like post RC3)
Hmmmm, now with linebreaks: Same problem over here, posted this message on the forum: I have exact the same problem. When doing a startx I only get a scrambled screen and my machine locks (even ctrl-alt-del doesn't work). I have build my base system using the stable packages after the RC3 release (gcc, binutils, etc.). When I started the "desktop installation" I did an ACCEPT_KEYWORDS="~x86" emerge kde to get xfree 4.3.0 I have a GeForce 4 Ti 4400 with an Athlon-XP and PDCraid. I'm building my machine with CFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer". Started at stage one. I have tried every combination with: glibc-2.3.1-r2.ebuild gcc-3.2.2.ebuild gentoo-sources-2.4.19-r10.ebuild gentoo-sources-2.4.20-r1.ebuild xfree-4.3.0.ebuild nvidia-glx-1.0.3123.ebuild + nvidia-kernel-1.0.4191-r1.ebuild nvidia-glx-1.0.4191-r1.ebuild + nvidia-kernel-1.0.3123-r2.ebuild I have tried virtually almost every possible combination in XF86Config. If I don't use the nVidia-driver I can do startx, but with the nVidia-driver I get a scrambled screen. I don't know if the problem is between: gentoo-sources and nvidia-drivers xfree 4.3.0 and nvidia-drivers gcc / binutils / glibc and nvidia-drivers Hence it can be something completely else. This is driving me crazy. I won't give up but I need to be sure what combination you people have that works. I don't even dream of finding a solution soon, but you friendly people can help me if you can confirm / decline what combination you have working I would be very happy. Specially the people who installed their system after RC3 or are completely sure that their system is equally build (emerge sync && emerge world -up is not always the same because it's possible that not ALL packages are build with latest gcc, glibc, binutils; using the --emptytree is more like post RC3)
Similar problem here (screen just goes black). Switching back to kernel 2.4.19 fixed the problem. Also, the 'nv' module that comes with XFree86 works fine.
can one of you give lolo-sources latest a try, I wonder if this relates to the rmap vm system that is in the current gentoo-sources.
Ok, I will try lolo-sources-2.4.20.2_pre4.ebuild + xfree-4.3.0.ebuild + nvidia-glx-1.0.3123.ebuild + nvidia-kernel-1.0.3123-r2.ebuild, I will post the results after the compile.
Created attachment 8921 [details] Configuration, logs, etc.
Using the lolo sources had the same results as the gentoo-sources( i.e. both had screen corruption with both 3123 and 4191 NVidia drivers ). :( Also, I'm willing to act as a test bed( apply patches, turn on kernel debugging, etc. ), to help out. I've filed an attachment that contains a bunch of configuration files, logs, etc. They're in one big file( I didn't realize you could create attachements until now, I planned on pasting them into this message ).
Maybe have a look at: http://bugs.gentoo.org/show_bug.cgi?id=15722
I have installed lolo-sources-2.4.20.2_pre4.ebuild + xfree-4.3.0.ebuild + nvidia-glx-1.0.3123.ebuild + nvidia-kernel-1.0.3123-r2.ebuild and it works perfect. If you want me to do some tests please let me know.
My last test was done with lolo-r2-pre3, so I tried again with lolo-r2-pre4, and SUCCESS! After looking at bug 15722( http://bugs.gentoo.org/show_bug.cgi?id=15722 ) I noticed in the patches that ACPI may cause instability when using the NVidia driver, so I compiled out ACPI. Then everthing started to work with both the 3123 and 4191 nvidia drivers. To make sure I wasn't imagining things I recompiled ACPI back in and I got screen corruption again.
I'm using ACPI with lolo-sources-2.4.20.2_pre4.ebuild and it works good.
closing this bug
