Since gentoo-sources2.6.33-r2 was stabled on amd64, the current stable nvidia-drivers (190.42) will not compile against the kernel. (I'll add the message in a comment). Upgrading to 190.53-r1 and libvdpau-0.3-r2 works for me here. Reproducible: Always
Calculating dependencies ... done! >>> Verifying ebuild manifests >>> Emerging (1 of 1) x11-drivers/nvidia-drivers-190.42-r3 * NVIDIA-Linux-x86_64-190.42-pkg2.run RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * CPV: x11-drivers/nvidia-drivers-190.42-r3 * REPO: gentoo * USE: acpi amd64 elibc_glibc gtk kernel_linux multilib userland_GNU * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found kernel object directory: * /lib/modules/2.6.33-gentoo-r2/build * Found sources for kernel version: * 2.6.33-gentoo-r2 * Checking for MTRR support ... [ ok ] >>> Unpacking source... >>> Unpacking NVIDIA-Linux-x86_64-190.42-pkg2.run to /var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/work/NVIDIA-Linux-x86_64-190.42-pkg2 >>> Source unpacked in /var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/work >>> Preparing source in /var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/work/NVIDIA-Linux-x86_64-190.42-pkg2 ... * Applying NVIDIA_glx-defines.patch ... [ ok ] * Applying NVIDIA_glx-glheader.patch ... [ ok ] * Converting NVIDIA-Linux-x86_64-190.42-pkg2/usr/src/nv/Makefile.kbuild to use M= instead of SUBDIRS= ... [ ok ] >>> Source prepared. >>> Configuring source in /var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/work/NVIDIA-Linux-x86_64-190.42-pkg2 ... >>> Source configured. >>> Compiling source in /var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/work/NVIDIA-Linux-x86_64-190.42-pkg2 ... * Preparing nvidia module make -j5 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/2.6.33-gentoo-r2/build HOST_CC=x86_64-pc-linux-gnu-gcc clean module If you are using a Linux 2.4 kernel, please make sure you either have configured kernel sources matching your kernel or the correct set of kernel headers installed on your system. If you are using a Linux 2.6 kernel, please make sure you have configured kernel sources matching your kernel installed on your system. If you specified a separate output directory using either the "KBUILD_OUTPUT" or the "O" KBUILD parameter, make sure to specify this directory with the SYSOUT environment variable or with the equivalent nvidia-installer command line option. Depending on where and how the kernel sources (or the kernel headers) were installed, you may need to specify their location with the SYSSRC environment variable or the equivalent nvidia-installer command line option. *** Unable to determine the target kernel version. *** make: *** [select_makefile] Error 1 * ERROR: x11-drivers/nvidia-drivers-190.42-r3 failed: * Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/2.6.33-gentoo-r2/build HOST_CC=x86_64-pc-linux-gnu-gcc clean module * * Call stack: * ebuild.sh, line 54: Called src_compile * environment, line 4156: Called linux-mod_src_compile * environment, line 3088: Called die * The specific snippet of code: * eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" CROSS_COMPILE=${CHOST}- LDFLAGS=\"$(get_abi_LDFLAGS)\" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}"; * * If you need support, post the output of 'emerge --info =x11-drivers/nvidia-drivers-190.42-r3', * the complete build log and the output of 'emerge -pqv =x11-drivers/nvidia-drivers-190.42-r3'. * The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/temp/environment'. * S: '/var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/work/NVIDIA-Linux-x86_64-190.42-pkg2' >>> Failed to emerge x11-drivers/nvidia-drivers-190.42-r3, Log file: >>> '/var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/temp/build.log' * Messages for package x11-drivers/nvidia-drivers-190.42-r3: * ERROR: x11-drivers/nvidia-drivers-190.42-r3 failed: * Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/2.6.33-gentoo-r2/build HOST_CC=x86_64-pc-linux-gnu-gcc clean module * * Call stack: * ebuild.sh, line 54: Called src_compile * environment, line 4156: Called linux-mod_src_compile * environment, line 3088: Called die * The specific snippet of code: * eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" CROSS_COMPILE=${CHOST}- LDFLAGS=\"$(get_abi_LDFLAGS)\" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}"; * * If you need support, post the output of 'emerge --info =x11-drivers/nvidia-drivers-190.42-r3', * the complete build log and the output of 'emerge -pqv =x11-drivers/nvidia-drivers-190.42-r3'. * The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/temp/environment'. * S: '/var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/work/NVIDIA-Linux-x86_64-190.42-pkg2'
Doug, please adjust $summary as you see fit and CC amd64/x86 (asap?)
arch's please test and mark stable: 22:29 <@Cardoe> 195.36.24
amd64 stable for: media-video/nvidia-settings-195.36.24 x11-drivers/nvidia-drivers-195.36.24 x11-libs/libvdpau-0.4 (bug 299395) been using them since they got added to tree with my 9600 GT for mplayer+vdpau, opengl, composite with no problems.
I have the same problem. I when I was installing it one week ago, everything worked fine.
Look, I discussed this with x86 and amd64 in #gentoo-dev on May 26th, and MANY people stepped up saying the drivers worked great. Two specific people stepped up and said they were going to mark them stable immediately. I highlighed the urgency to get it done which is why I didn't make a ticket before prodding on IRC. Both these individuals told me it was unimportant to make a ticket. Plain and simple, I would mark these stable myself as I use them on SEVERAL stable only x86 and amd64 machines at my office. However last time I had to spend 3 days singing kumba-ya with devrel over hurting people's feelings for marking them stable myself. So I simply have a special mechanism at work that distributes a list of files that should be stable.
(In reply to comment #6) > Plain and simple, I would mark these stable myself as I use them on SEVERAL > stable only x86 and amd64 machines at my office. However last time I had to > spend 3 days singing kumba-ya with devrel over hurting people's feelings for > marking them stable myself. I would have no problem with you marking it stable yourself as I don't have any Nvidia card around anyway. Your tests would be better than mine.
This version is actually very *unstable* for me. Any moderately complex 3D game (like native NWN or Spore in Wine) hangs X unrecoverably and very consistently (on the game menu in both cases). NVIDIA already revved to 195.36.31, so to me it makes more sense to bump to that, and mark .24 unstable, at least for amd64.
I tested on x86 nvidia-drivers-195.36.24 together with libvdpau-0.4 (Bug #299395) and the (also still keyworded) nvidia-settings-195.36.24. Everything seems to be fine (including rdeps), although i can't actually test it "live" as i'm working remotely atm... The only thing i've found is dev-util/nvidia-cuda-sdk-2.2-r1 which claims * This package requires <=sys-devel/gcc-4.3 to build sucessfully. But that has nothing to do with the drivers... ;-)
x86 stable, closing, thanks Andreas! Sorry for the delay that left stable x86 nvidia systems broken. :(
*** Bug 323639 has been marked as a duplicate of this bug. ***
