This is a request for an ebuild for the new nvidia legacy driver 1.0.7182 located here: http://www.nvidia.com/object/unix.html This driver is reported to fix compile problems and many other bugs that prevented legacy cards from being used on kernels >= 2.6.16.
*** Bug 138359 has been marked as a duplicate of this bug. ***
Created attachment 90740 [details] Emerge --info
The 1.0.6629 drivers stopped working on my system, but unfortunately despite much investigation I couldn't find out what had changed to stop them working. Non of the legacy drivers in portage worked. I even upgraded X to 7.1. In the end I installed the 7182 driver by hand, and it works. Renderaccel doesn't work - first of all I lose the fonts, and then it crashes. Unfortunately I am not clear on whether the issues I found are related to the X upgrade or the nvidia drivers. If I come across any more issues, I will report them here.
(In reply to comment #3) > The 1.0.6629 drivers stopped working on my system, but unfortunately despite > much investigation I couldn't find out what had changed to stop them working. > Non of the legacy drivers in portage worked. I even upgraded X to 7.1. In the > end I installed the 7182 driver by hand, and it works. Renderaccel doesn't work > - first of all I lose the fonts, and then it crashes. Unfortunately I am not > clear on whether the issues I found are related to the X upgrade or the nvidia > drivers. If I come across any more issues, I will report them here. > Did you update your kernel to 2.6.16 recently? The only legacy driver in portage right now that works with the 2.6.16 kernel is the 1.0.7174-r2 ebuild and only on the x86 arch. The 7182 driver came out to fix the problems with the previous 7174 driver and as I understand should be added to portage soon.
*** Bug 138993 has been marked as a duplicate of this bug. ***
> Did you update your kernel to 2.6.16 recently? The only legacy driver in > portage right now that works with the 2.6.16 kernel is the 1.0.7174-r2 ebuild > and only on the x86 arch. The 7182 driver came out to fix the problems with > the previous 7174 driver and as I understand should be added to portage soon. I did, but only after 1.0.6629 stopped working on my system. Unfortunately, I cannot put my finger on exactly what caused 6629 to stop working. My system is basically stable, with a few exceptions unrelated to Xorg. I normally leave the computer running, and emerge 2-3 times per week. I restarted the computer to access my windows partition (I know, I know, but I have a data logger for my glider with no non-windows software to download from it), and when restarting Linux, xorg failed to start. At the time, I had 2.6.13-r3. Trying 7174 failed, and so did re-emerging 6629, and doing a revdep-rebuild. After many fruitless hours, I made the decision to upgrade to 2.6.16, to emerge the new Xorg 7.1, and to try the latest (not in portage) legacy driver. All works OK, with the exception of the font problem, and screen corruption on kdm on first startup. I want to learn how to overlay the portage, and then I can write my own ebuild for this type of activity. Once the 7182 driver hits portage, I will use it through portage. Uptime is now >20hrs, without any other problem or apparent stability. I did consider going out and buying a new graphics card, but my motherboard doesn't have PCI express, and I want to upgrade to AMD64 sometime soon.
Created attachment 90918 [details] nvidia-glx hacked 7182 ebuild
Created attachment 90922 [details] nvidia-glx hacked 7182 ebuild
Created attachment 90923 [details] nvidia-kernel hacked 7182 ebuild Just uploaded two ebuilds I created editing version 7174's ebuild. They are working fine here (x86, kernel 2.6.17, xorg 7). Basically only the patches were commented out. Add them to a portage overlay, they were NOT tested on AMD64
Created attachment 91032 [details] nvidia-kernel-1.0.7182.ebuild I have only commented patches that didn't work and I have replaced "7174" using the eclass versionator. I didn't have tested it very well (only with ebuild /path/to/ebuild install), I'll test it better later.
Created attachment 91033 [details] nvidia-glx-1.0.7182.ebuild see #10
New ebuild committed to CVS: x11-drivers/nvidia-legacy-drivers-1.0.7182 Give it a try. :-)
With the kernel gentoo-sources-2.6.15-r7, xorg 6.8.2-r8 and the option RenderAccel set to off, it seems to be stable. With RenderAccel set to on, it hangs. :-/ I do not know if without it the performance will be less good.
media-libs/jasper doesn't like the ebuild in portage. When I emerge it I get 788 lines of "/usr/lib/opengl/nvidia/lib/libGLcore.so.1: undefined reference to `_nv000xxxgl' Where the three xxx's are 788 different numbers With or without the dlloader use-flag makes no difference... I am currently emerging kdebase-meta so if i find more problems i'll report them here. If someone wants me to check something, just name it...
I have installed the legacy driver, and downgraded from xorg 7.1 to xorg 7.0. Everything is working OK, with the following reservations: 1 - I put "nvidia-legacy" in the VIDEO_CARDS line in make.conf instead of nvidia. Not sure if this is correct, but it all appears to be working. I still "eselect opengl set nvidia" though. Perhaps "nvidia-legacy" should be a valid option through xorg configuration? 2 - kdm has a corrupted screen - the frame graphic from the terminal is ghosted repeated several times across the screen. The login dialog is readable/usable, and once past this point there is no more evidence of problems. 3 - 'Option "RenderAccel" "true"' is commented out in xorg.conf, as it caused xorg to crash. I will investigate this further and comment if appropriate.
(In reply to comment #15) > 1 - I put "nvidia-legacy" in the VIDEO_CARDS line in make.conf instead of > nvidia. Not sure if this is correct, but it all appears to be working. I still > "eselect opengl set nvidia" though. Perhaps "nvidia-legacy" should be a valid > option through xorg configuration? nvidia-legacy isn't valid VIDEO_CARDS option, at least now no ebuild (including xorg) is using it. If it becomes used, then all ebuilds using VIDEO_CARDS="nvidia" should be updated to include it so we don't get another bug 139500 :) eselect opengl (and other stuff?) could stay with "nvidia" IMHO, because it doesn't affect dependencies (needed to pull the correct driver) and you can't have both nvidia-drivers and nvidia-legacy-drivers anyway?
