emerged, configured, installed and booted development-sources 2.6.9-rc3 emerged nvidia-kernel. nvidia.ko is installed in /lib/modules/2.6.9-rc3/video uname -r returns 2.6.9-rc3n, so modprobe etc looks in /lib/modules/2.6.9-rc3n and can't find nvidia.ko and says so It was fixed by copying the video directory from 2.6.9-rc3 to 2.6.9-rc3n and running depmod. Then modprobe nvidia succeeds Reproducible: Always Steps to Reproduce: 1.emerge, configure, installe and boot development-sources 2.6.9-rc3 2.emerge nvidia-kernel 3.modprobe nvidia-kernel Actual Results: see details Expected Results: install nvidia.ko in /lib/modules/2.6.9-rc3n/video
Try this patch, does it solve the install problem cd /usr/portage/media-video/nvidia-kernel/ patch -Np0 < /path/to/this.patch --- nvidia-kernel-1.0.6111-r2.ebuild.old 2004-10-11 15:36:48.979002512 +1000 +++ nvidia-kernel-1.0.6111-r2.ebuild 2004-10-11 15:37:22.809859440 +1000 @@ -99,7 +99,7 @@ src_install() { # The driver goes into the standard modules location - insinto /lib/modules/${KV}/video + insinto /lib/modules/`uname -r`/video # Insert the module doins nvidia.${KV_OBJ}
i fixed this by updating to the 2.6 kernel headers.
The reason for this (and I know because I did it myself when running make oldconfig), is that when it prompted for localversion, instead of hitting enter, you hit 'n' which of course set localversion to 'n'.
*** Bug 68660 has been marked as a duplicate of this bug. ***
*** Bug 68834 has been marked as a duplicate of this bug. ***
Marking invalid as this was user error
Regarding this localversion thing... Shouldn't the eclass for handling installation of external kernel modules check to see if this localversion setting is set? So that it installs the modules in the correct path even though localversion is set?
Yes. see bug 67804
*** Bug 69094 has been marked as a duplicate of this bug. ***
*** Bug 69632 has been marked as a duplicate of this bug. ***