x11-drivers/nvidia-drivers does not compile with linux 3.3 Reproducible: Always
Created attachment 305857 [details] build log
As of the final release the "256.35-unified-arch.patch" fails to apply as well...
The initial problem can be prevented with this: pushd /var/tmp/portage/x11-drivers/nvidia-drivers-295.20-r1/work/; sed -i 's/CFLAGS="$CFLAGS -I$SOURCES\/arch\/x86\/include"/CFLAGS="$CFLAGS -I$SOURCES\/arch\/x86\/include -I$SOURCES\/arch\/x86\/include\/generated"/' kernel/conftest.sh; popd ;
Created attachment 305869 [details] modified nvidia-drivers-295.20-r1.ebuild open for next xorg-server 1.12.0 + 1.13 On latest 3.3-rc* kernels you still have to do this before emerge: cp -av /usr/src/linux/arch/x86/include/generated/asm/*.h /usr/src/linux/arch/x86/include/asm/ for xorg-server 1.12 use my ebuild with your local overlay and run: ebuild /usr/local/portage/x11-drivers/nvidia-drivers/nvidia-drivers-295.17.ebuild digest Happy testing!
> for xorg-server 1.12 use my ebuild with your local overlay and run: > ebuild > /usr/local/portage/x11-drivers/nvidia-drivers/nvidia-drivers-295.17.ebuild > digest > > Happy testing! corected version for xorg-server 1.12 use my ebuild with your local overlay and run: ebuild /usr/local/portage/x11-drivers/nvidia-drivers/nvidia-drivers-295.20-r1.ebuild digest Happy testing!
Confirmed on ~amd64
(In reply to comment #4) > Created attachment 305869 [details] > modified nvidia-drivers-295.20-r1.ebuild open for next xorg-server 1.12.0 + > 1.13 > > On latest 3.3-rc* kernels you still have to do this before emerge: > > cp -av /usr/src/linux/arch/x86/include/generated/asm/*.h > /usr/src/linux/arch/x86/include/asm/ Please stop posting stuff that isn't related to the issue. Report abother bug about the xorg-server incompatibility.
Created attachment 305909 [details, diff] patch for nvidia drivers
Created attachment 305911 [details, diff] patch for ebuild
(In reply to comment #8) > Created attachment 305909 [details, diff] [details, diff] > patch for nvidia drivers The correct location of the generated .h files is $OUTPUT/arch/x86/include/generated. If you use the O= assignment or $KBUILD_OUTPUT, this is important.
Created attachment 305939 [details, diff] patch for nvidia drivers
I had the same problem and came up with a similar patch to Sven's, seems to work fine now.
*** Bug 409061 has been marked as a duplicate of this bug. ***
*** Bug 409093 has been marked as a duplicate of this bug. ***
+ 21 Mar 2012; Samuli Suominen <ssuominen@gentoo.org> + nvidia-drivers-295.20-r1.ebuild: + Fix building with Linux 3.3.x wrt #408841 http://sources.gentoo.org/viewvc.cgi/gentoo-x86/x11-drivers/nvidia-drivers/nvidia-drivers-295.20-r1.ebuild?r1=1.3&r2=1.4
(In reply to comment #10) > The correct location of the generated .h files is > $OUTPUT/arch/x86/include/generated. If you use the O= assignment or > $KBUILD_OUTPUT, this is important. Missed this comment. Should be fixed now with: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/x11-drivers/nvidia-drivers/nvidia-drivers-295.20-r1.ebuild?r1=1.4&r2=1.5
Could you please fix the 173 family too? That is affected, too.
Use nvidia-drivers-295.33
(In reply to comment #18) > Use nvidia-drivers-295.33 I have a GeForce FX 5200 :( and is only supported by that family.
Created attachment 306477 [details, diff] Patch for nvidia-drivers-173.14.31.ebuild
(In reply to comment #18) > Use nvidia-drivers-295.33 not an option for users needing x11-drivers/nvidia-drivers-96.43.20 and x11-drivers/nvidia-drivers-173.14.31
(In reply to comment #21) > (In reply to comment #18) > > Use nvidia-drivers-295.33 > > not an option for users needing > x11-drivers/nvidia-drivers-96.43.20 and > x11-drivers/nvidia-drivers-173.14.31 Both of these want to downgrade X.org to: [ebuild UD ] x11-base/xorg-server-1.10.6 [1.11.4] USE="ipv6 nptl udev xorg xvfb -dmx -doc -kdrive -minimal -static-libs -tslib -xnest" 0 kB So no, I don't think it's a good idea to try to fix these drivers. If there won't be any NVidia releases for newer X.org ABIs on the older series, it's time for users to upgrade into xf86-video-nouveau. Cardoe, OK for lastriting the older series for being incompatible with recent X.org servers?
(In reply to comment #22) > So no, I don't think it's a good idea to try to fix these drivers. If there > won't be any NVidia releases for newer X.org ABIs on the older series, > it's time for users to upgrade into xf86-video-nouveau. nouveau is a very poor choise. > > Cardoe, OK for lastriting the older series for being incompatible with > recent X.org servers? please don't. Just keep an old xorg-1.10 and these stabled versions.
(In reply to comment #23) > please don't. Just keep an old xorg-1.10 and these stabled versions. That won't be an option because of: [blocks B ] <x11-base/xorg-server-1.11.4 ("<x11-base/xorg-server-1.11.4" is blocking x11-libs/gtk+-3.4.0) As in, new xorg-server is required for new GTK+
(In reply to comment #24) > As in, new xorg-server is required for new GTK+ So what? Then gtk+-3 will not be available for these users. This is better than rendering their machines completely useless by removing their only working X driver. (Nouveau is not an option since it usually hangs all machines I tested after 1-2 minutes, and vesa framebuffer is unusable slow if it works at all.) And it might be that until gtk+-3 is really needed for basic packets that nvidia finally upgrades their legacy drivers...
295.33 doesn't seem to include the patch for supporting KBUILD_OUTPUT, that was added to 295.20-r1. It breaks when kernel build output is elsewhere.
(In reply to comment #26) > 295.33 doesn't seem to include the patch for supporting KBUILD_OUTPUT, that > was added to 295.20-r1. It breaks when kernel build output is elsewhere. 11 Apr 2012; Doug Goldstein <cardoe@gentoo.org> nvidia-drivers-295.33.ebuild: Fix 295.33 for Linux 3.3.x. bug #408841 Thanks, 295.40 also fine.
*** Bug 413475 has been marked as a duplicate of this bug. ***
http://weltall.heliohost.org/wordpress/2012/01/20/linux-kernel-3-3-rc1-and-nvidia-drivers/ lists two ways of fixing it. Let me quote it. [Quote] The first way is fixing the nvidia installer side. Extract the nvidia installer package with -x as argument passed to the sh package then go in the folder it was extracted to (should be /tmp) Then go to the kernel sub folder and open the conftest.sh search for CFLAGS=”$CFLAGS -I$SOURCES/arch/x86/include” and replace it with CFLAGS=”$CFLAGS -I$SOURCES/arch/x86/include -I$SOURCES/arch/x86/include/generated” [...] The second way is hacking a bit the include folders Go in /lib/modules/<kernelname>/source/arch/x86/include/ and do cp generated/asm/unistd*.h ./asm/ [End of quote] I haven't tried the first way (although it is more easily automatable), but the second one worked beautifully.
Please also update nvidia-drivers-290.10 for those people wishing to use kernel 3.3.X but are stuck at nvidia-drivers-290.10 due to nvidia bug described in http://www.nvnews.net/vbulletin/showthread.php?p=2551948#post2551948
(In reply to comment #30) > Please also update nvidia-drivers-290.10 for those people wishing to use > kernel 3.3.X but are stuck at nvidia-drivers-290.10 due to nvidia bug > described in > http://www.nvnews.net/vbulletin/showthread.php?p=2551948#post2551948 No. This leads to an infinite amount of usable combinations. As I tell everyone, find a kernel and driver release that works well on your hardware and stick to it until you want to find a new combination. I am maintaining this on a volunteer basis and only have so much time to dedicate to it so infinite use cases are not something I am interested in. The nvidia drivers only come in binary form so it's impossible to maintain a stable version. For Linux 3.3 or newer use 295.33 or newer. Otherwise you must stay at an older kernel release.
(In reply to comment #31) > (In reply to comment #30) > > Please also update nvidia-drivers-290.10 for those people wishing to use > > kernel 3.3.X but are stuck at nvidia-drivers-290.10 due to nvidia bug > > described in > > http://www.nvnews.net/vbulletin/showthread.php?p=2551948#post2551948 > > No. This leads to an infinite amount of usable combinations. As I tell > everyone, find a kernel and driver release that works well on your hardware > and stick to it until you want to find a new combination. I am maintaining > this on a volunteer basis and only have so much time to dedicate to it so > infinite use cases are not something I am interested in. The nvidia drivers > only come in binary form so it's impossible to maintain a stable version. > > For Linux 3.3 or newer use 295.33 or newer. Otherwise you must stay at an > older kernel release. OK. I have placed x11-drivers/nvidia-drivers-290.10-r2 in /usr/local/portage and applied the patch. The patched ebuild seems to work OK with 3.3.5. However I found 3.3.5 has performance issues with virtual machines (https://bugzilla.redhat.com/show_bug.cgi?id=806548) so I have reverted to 3.2.16.
