When emerging nvidia-kernel-1.0.4349 and nforce-net-1.0.0248-r2, the modules are built without considering the kernel extra-version. If the kernel is just 2.4.20 everything will work fine. Otherwise, if the kernel is for example 2.4.20-xfs-r2 the two ebuilds build two 2.4.20 kernel module and copy them under /lib/modules creating the 2.4.20 directory. On the next boot, the modules are not loaded. For an immediate solution, the manual insertion of the complete kernel version is needed in the two ebuilds Reproducible: Always Steps to Reproduce: 1. 2. 3.
you have to make sure that /usr/src/linux points to the correctly installed kernel. i.e.: max@dozer nforce-net $ ls -l /usr/src total 7 -rw-r--r-- 1 root root 109 Apr 26 08:03 kernel-packages lrwxrwxrwx 1 root root 22 Apr 17 13:45 linux -> linux-2.4.20-gaming-r2 drwxr-xr-x 14 root root 720 Apr 8 07:12 linux-2.4.20 drwxr-xr-x 14 root root 720 Apr 26 07:58 linux-2.4.20-gaming-r2 drwxr-xr-x 2 root root 120 Mar 12 14:53 patches as you can see here, mine was installed into the correct kernel path: max@dozer nforce-net $ epm -ql nvidia-kernel /etc/modules.d/nvidia /lib/modules/2.4.20-gaming-r2/video/nvidia.o <---------- /usr/share/doc/nvidia-kernel-1.0.4363/README.gz /sbin/NVmakedevices.sh
check your symb link called linux in /usr/src (should point to your current kernel)
*** Bug 21656 has been marked as a duplicate of this bug. ***
