2.6.14.6 kernel using 2.4.31 modules Why?

dgrego · 06-14-2006, 09:55 PM

Upgraded the 2.4.31 kernel to 2.6.14.6. The gateway mx3560 booted into the new kernel without any major issues, but when I viewed the syslog I noticed some errors relating to insmod loading modules from /lib/modules/2.4.31/kernel/driver. Why isn't insmod loading modules from /lib/modules/2.6.14.6/driver? What in the slackware startup scripts is causing this? Is this normal? Anyway, I new at linux and I updated the kernel as a learning experience. Any insight would be much appreciated.

gbonvehi · 06-14-2006, 10:08 PM

Probably you forgot to re-run lilo to update it and make it point to the new kernel.

trey85stang · 06-14-2006, 11:41 PM

Quote:

Originally Posted by gbonvehi

Probably you forgot to re-run lilo to update it and make it point to the new kernel.

I would say you are right!

cwwilson721 · 06-15-2006, 12:06 AM

Or forgot 'make modules_install'

(I've never done that. Nope. Not me....)

Note: The rest of this message was cancelled due to poster getting zapped by lightning.......

davidsrsb · 06-15-2006, 09:43 AM

I had this happen on one machine when I installed the 2.6.16 kernel from /testing when I installed alsa before kernel-modules.

I have found that the best sequence is:
kernel-source
kernel-modules
alsa-driver
kernel-generic
mkinitrd -c -k 2.6.16.20 -m reiserfs 0r whatever modules you need preloaded
run lilo
reboot
alsaconf
run the NVIDIA script if appropriate
startx