So that all Gentoo users can get up to speed with the new x11-drivers/nvidia-legacy-drivers ebuild, I would like to mark it stable on both platforms. Please post any objections here. I plan on doing this in one week depending on feedback. Soon after this I also plan on removing the old media-video/nvidia-(glx/kernel) ebuilds.
(In reply to comment #0) > So that all Gentoo users can get up to speed with the new > x11-drivers/nvidia-legacy-drivers ebuild, I would like to mark it stable on > both platforms. > > Please post any objections here. I plan on doing this in one week depending on > feedback. > > Soon after this I also plan on removing the old media-video/nvidia-(glx/kernel) > ebuilds. > I was pleased to find out that the nvidia-legacy-drivers package is the first version beyond 6xxx to work on my x86 laptop (and the *only* one to work with xorg 7.0 and kernel 2.6.14-r5); thanks very much. WFM! :)
kernel 2.6.17.6 (and 2.6.16) nvidia-legacy-drivers-1.0.7182 works ok here
works fine here for me.
The nvidia-legacy-drivers cause some KDE apps (like Kontact or KMyMoney) to lock up the X server. The X process consumes nearly 100% of the CPU. The machine no longer reacts to keyboard or mouse events. The only way to get out of this situation is by killing X from an remote session. The nv drivers from xorg work fine. Also never experienced any problems with kernel versions < 2.6.16 and nvidia-(glx/kernel). Package info: - nvidia-legacy-drivers-1.0.7182 - xorg-x11-r1 - kdebase-meta-3.5.2 (+ some seperately installed KDE apps) - gentoo-sources-2.6.17-r4 Some emerge --info output: ACCEPT_KEYWORDS="x86" CFLAGS="-O2 -march=pentium3 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" USE="x86 X a52 aac acpi aim alsa apm arts asf audiofile avi berkdb bitmap-fonts bzip2 cdr crypt cups curl dlloader dri dvd encode exif expat fam ffmpeg firefox foomaticdb gdbm gif glut glx gphoto2 icq idn imlib ipv6 java jpeg kde lcms libg++ libwww mad mikmod mime mmx mng motif mp3 mpeg msn ncurses nls nptl nsplugin nvidia ogg opengl oscar pam pcre pdf pdflib perl png python qt3 qt4 quicktime readline real reflection sdl session spell spl sse ssl tcpd tiff truetype truetype-fonts type1-fonts udev unicode usb vcd vorbis win32codecs wmf xml xml2 xorg xv xvid yahoo zlib elibc_glibc input_devices_keyboard input_devices_mouse kernel_linux linguas_en linguas_nl userland_GNU video_cards_nv video_cards_nvidia"
(In reply to comment #4) I see the same thing on my machine. When I open certain web pages in konqueror, xorg start using up 99% of my CPUs and quits responding.
How is 7184 for everyone? It seems to be quite stable on my AMD64 box.
(In reply to comment #6) > How is 7184 for everyone? It seems to be quite stable on my AMD64 box. After upgrading to 2006.1 (gcc-4.1.1, glibc-2.4, etc.) it is not even possible to load the module. :-(
(In reply to comment #7) > (In reply to comment #6) > > How is 7184 for everyone? It seems to be quite stable on my AMD64 box. > > After upgrading to 2006.1 (gcc-4.1.1, glibc-2.4, etc.) it is not even possible > to load the module. :-( > I had the same problem after I upgraded to gcc-4.1.1 and glibc-2.4. Then I figured it might have something to do with the kernel being compiled on the previous version of gcc. So I recompiled the kernel with the new gcc and then reemerged nvidia-legacy-drivers. Now it loads fine.
(In reply to comment #8) > (In reply to comment #7) > > (In reply to comment #6) > > > How is 7184 for everyone? It seems to be quite stable on my AMD64 box. > > > > After upgrading to 2006.1 (gcc-4.1.1, glibc-2.4, etc.) it is not even possible > > to load the module. :-( > > > > I had the same problem after I upgraded to gcc-4.1.1 and glibc-2.4. Then I > figured it might have something to do with the kernel being compiled on the > previous version of gcc. So I recompiled the kernel with the new gcc and then > reemerged nvidia-legacy-drivers. Now it loads fine. > Of course, my bad. After recompiling the kernel, the module loads just fine. KDE apps still make X take up 99% of the CPU though, leaving the system unresponsive. The newer drivers do not solve this problem.
(In reply to comment #9) > (In reply to comment #8) > > (In reply to comment #7) > > > (In reply to comment #6) > > > > How is 7184 for everyone? It seems to be quite stable on my AMD64 box. > > > > > > After upgrading to 2006.1 (gcc-4.1.1, glibc-2.4, etc.) it is not even possible > > > to load the module. :-( > > > > > > > I had the same problem after I upgraded to gcc-4.1.1 and glibc-2.4. Then I > > figured it might have something to do with the kernel being compiled on the > > previous version of gcc. So I recompiled the kernel with the new gcc and then > > reemerged nvidia-legacy-drivers. Now it loads fine. > > > > Of course, my bad. After recompiling the kernel, the module loads just fine. > KDE apps still make X take up 99% of the CPU though, leaving the system > unresponsive. The newer drivers do not solve this problem. > I don't know where you're getting that from. I've tried several different kde apps and apps in kde and they all take up very minimal CPU using 7184. Have you tried using the nv driver instead of the nvidia one to see if it does the same thing?
(In reply to comment #10) > Have > you tried using the nv driver instead of the nvidia one to see if it does the > same thing? See my previous comment #4. The nv driver works OK.
(In reply to comment #11) > (In reply to comment #10) > > Have > > you tried using the nv driver instead of the nvidia one to see if it does the > > same thing? > > See my previous comment #4. The nv driver works OK. > I tried Kontact and KMyMoney on my AMD64 system. I'm not getting 100% cpu usage. I'm getting very minimal CPU usage. What do you have set for the nvidia module? If you have NvAGP set, I'd recommend disabling that since it has been nothing but problems from what I've read.
(In reply to comment #12) > What do you have set for the > nvidia module? If you have NvAGP set, I'd recommend disabling that since it > has been nothing but problems from what I've read. NvAGP is not touched in any way. I did experimented with some options and it turns out that the nvidia-legacy-drivers do not work with: Option "RenderAccel" "true" Option "AllowGLXWithComposite" "true" AFAIK these are pretty common options. The nvidia-kernel/nvidia-glx used to work OK with these settings. As a workaround the lines mentioned above can be commented out. IMHO this should not be the permanent soultion though.
(In reply to comment #13) > (In reply to comment #12) > > What do you have set for the > > nvidia module? If you have NvAGP set, I'd recommend disabling that since it > > has been nothing but problems from what I've read. > > NvAGP is not touched in any way. I did experimented with some options and it > turns out that the nvidia-legacy-drivers do not work with: > > Option "RenderAccel" "true" > Option "AllowGLXWithComposite" "true" > > AFAIK these are pretty common options. The nvidia-kernel/nvidia-glx used to > work OK with these settings. As a workaround the lines mentioned above can be > commented out. IMHO this should not be the permanent soultion though. > Notice the EXPERIMENTAL and ENABLE AT YOUR OWN RISK in the nvidia changelog. This does not have anything to do with the stability of the driver in Gentoo and therefore the amd64 arch should be marked stable for the 7184 driver. Option "RenderAccel" "boolean" Enable or disable hardware acceleration of the RENDER extension. THIS OPTION IS EXPERIMENTAL. ENABLE IT AT YOUR OWN RISK. There is no correctness test suite for the RENDER extension so NVIDIA can not verify that RENDER acceleration works correctly. Default: hardware acceleration of the RENDER extension is disabled. Option "AllowGLXWithComposite" "boolean" Enables GLX even when the Composite X extension is loaded. ENABLE AT YOUR OWN RISK. OpenGL applications will not display correctly in many circumstances with this setting enabled. Default: GLX is disabled when Composite is loaded.
Newsletter says going to remove the legacy drivers so thought I better try the new nvidia-legacy-drivers ebuild. The system did it on has an TNT on it that would only work with the nvidia-kernel-1.0.7174-r2 version. Nothing else. Pickiest card ever seen. Tried the nvidia-legacy-drivers-1.0.7184 and worked perfect as far as can tell. I'm sure I'll hear from them in a few days if something doesn't seem correct. Played some video, they run KDE and everything seemed good. Card doesn't shut down correctly and get garbage on console screen when shutdown, but bootup is fine. It's been like that a long time though. AMD64 system, x86_64 build, with the new gcc-4.1.1, glibc-2.4, 2006.1 profile.
I experience the same problem as comment #4/comment #5; I'm on x86 (an Athlon XP Thoroughbred B running a 2.6.18-rc7 vanilla kernel) with an "nVidia Corporation NV11 [GeForce2 MX/MX 400]", disabling Option "RenderAccel" (comment #14) resolved the problem.
for me the nvidia-legacy-drivers die horribly on startx with a black screen followed by a hard lock. I have AccelRender "false" and have none of the composite options set in xorg.conf. The nv driver seems to work fine.
amd64 stable. It merges fine, but I couldn't do any testing beyond that because I lack the hardware to do so.
