When I either upgrade nvidia-kernel or gentoo-sources, do modules-rebuild, reboot and get back into X, xorg reports No Screens found. For some reason only the combination of nvidia-kernel-1.0.6629-r4 and gentoo-sources-2.6.12-r10 seems to work for me. This perplexes me. Reproducible: Always Steps to Reproduce: 1. Install gentoo-sources-2.6.13-r{3,5} 2. Or, echo "media-video/nvidia-kernel ~amd64" >> /etc/portage/package.keywords && emerge nvidia-kernel Actual Results: Xorg finds No Screens Expected Results: Xorg works, glxgears works, etc. Gentoo Base System version 1.6.13 Portage 2.0.51.22-r3 (default-linux/amd64/2005.0, gcc-3.4.4, glibc-2.3.5-r2, 2.6.12-gentoo-r10 x86_64) ================================================================= System uname: 2.6.12-gentoo-r10 x86_64 AMD Athlon(tm) 64 Processor 3400+ dev-lang/python: 2.3.5-r2, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.20 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-pipe -O3 -march=k8" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-pipe -O3 -march=k8" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X aac alsa audiofile avi berkdb bitmap-fonts bzip2 cdr crypt curl dvd dvdread eds emboss encode esd ethereal exif expat fam flac foomaticdb fortran gif glut gnome gpm gstreamer gtk gtk2 idn imlib ipv6 java jpeg lcms libvisual lzw lzw-tiff mng mp3 mpeg ncurses network nls ogg oggvorbis opengl pam pcre pdflib perl png python quicktime readline samba sdl softmmu speex spell sqlite ssl tcpd theora tiff truetype truetype-fonts type1-fonts udev usb userlocales vorbis xine xml2 xpm xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
I seem to have a similar problem (note that I have an x86 not amd64): I just upgraded from gentoo-sources-2.6.12-r9 to 2.6.14-r2. Reemerged nvidia-kernel-1.0.6629-r4 and rebooted. Now X won't start, it complains about not being able to initialize the nvidia driver. I double checked that the nvidia kernel module was loaded. I traced the problem to that /dev/nvidia0 and /dev/nvidiactl has disappeared (they reappear of I reboot the old kernel). A workaround is to create them manually. Seems something happend between kernel 2.6.12 and 2.6.{13,14} that broke udev's detection of nvidia kernel module. emerge --info Portage 2.0.51.22-r3 (default-linux/x86/2005.1, gcc-3.3.6, glibc-2.3.5-r2, 2.6 4-gentoo-r2 i686) ================================================================= System uname: 2.6.14-gentoo-r2 i686 AMD Athlon(tm) XP 2400+ Gentoo Base System version 1.6.13 ccache version 2.3 [enabled] dev-lang/python: 2.3.5-r2, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.20 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O3 -march=athlon-xp -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/ 1/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=athlon-xp -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp.du.se/pub/os/gentoo" LANG="C" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 3dnow 3dnowext X aac alsa apache2 apm audiofile avi bash-completion b kdb bitmap-fonts browserplugin bzip2 cdr crypt cups eds emboss ethereal exif e at foomaticdb fortran gdbm gif glut gpm gstreamer gtk gtk2 imlib java javascri jpeg lcms libg++ libwww mhash mmx mmxext mng mozilla mp3 mpeg mysql ncurses n nsplugin nvidia offensive ogg oggvorbis openal opengl pam pcre pdflib perl ph png python quicktime readline real recode samba sse ssl svg tcpd tga tiff true pe truetype-fonts type1-fonts udev vorbis win32codecs wmf xinerama xml2 xmms x xvid xvmc zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LC_ALL, LDFLAGS, LINGUAS
I can verify that this also reproduces with vanilla-sources-2.6.14.2, not just gentoo-sources. I too am missing /dev/nvidia* now. How do you manually create the correct entries?
NM, got it. For anyone else who needs to do this: mknod /dev/nvidia0 c 195 0 mknod /dev/nvidiactl c 195 255 chmod /dev/nvidia* 666 After performing these steps I can once again startx successfully.
I did some more searching and there seems to be some problems with the nvidia drivers and udev. One bug that might be related is bug #58294.
Peter Kasting, the last fine of your fix should be chmod 666 /dev/nvidia* But your right in that it works. Is there going to be a fix for version 6629? Installing the newer nvidia-kernel doesn't work for <= GeForce 2 users. Well, let's edit some udev rules now.
(In reply to comment #5) > Peter Kasting, the last fine of your fix should be > > chmod 666 /dev/nvidia* Oops! You're completely correct. Sorry for the typo.
I also ran into this problem. If I create the device nodes as mentioned above, will the devices remain after I reboot the system? I really don't know that much about udev.
If you put the commands mentioned in your /etc/modules.d/nvidia file they will be created at every bootup. This works for me and once again allowing me to waste hours playing enemy-territory.
Thanks for the tip, I had put the commands into /etc/conf.d/local.start Is there a simple way to make udev take care of this automatically, wouldn't that be a "cleaner" solution?
Of course there are the options to run /sbin/NVmakedevices.sh or to set RC_DEVICE_TARGALL="yes" in /etc/conf.d/rc, but all that looks rather ugly, so I hope someone will find a way to make this module udev-compatible.
Because this bug doesn't seem to have anything to do with AMD64 specifically (reproduces on x86), I think Hardware should be set to All. (I don't have permissions to do this myself.)
Good eye, done now.
Since this problem still exists with 1.0.6629-r5 and since this ist the latest stable version, the problem should either be fixed asap or a newer driver without this issue should be marked stable.
*** Bug 118030 has been marked as a duplicate of this bug. ***
*** Bug 127393 has been marked as a duplicate of this bug. ***
A patched 7174 driver using the latest 2.6.16 kernel will work and is reportedly stable on the x86 arch: http://bugs.gentoo.org/show_bug.cgi?id=127618
All the recent drivers work just fine here w/ udev. Closing.
