Upgraded to 2.4.31 from 2.4.26 with swaret and Slack still thinks it 2.4.26
 

I have upgrade to kernel 2.4.31 using swaret and when I restarted my machine "depmod" and "modprobe" ...etc are still looking for modules in the /lib/modules/2.4.26 directory which is no longer there, only 2.4.31 now exists.

As a test I tried create a sym link to 2.4.31 but then the module utils say something to the effect of found module but has be compliled for kernel 2.4.31 and this kernel is 2.4.31.

/proc/version still shows 2.4.26

/boot/ has the vmlinux link correct pointing to the new kernel

Has anyone run into this before or know anyways to get Slack to think it is version 2.4.31 so I can load modules?

Thanks.

I would ditch swaret. Then download all the kernel parts for 2.4.31 (headers, modules, kernel-ide (or whatever you needed) and sources) and upgradepkg all of them (and alsa if needed). Maker certain your /etc/lilo.conf lists the kernel properly (if you use lilo). Then rerun lilo. Reboot.

That did it, thanks!

I had the very same problem a few minutes ago when I updated my system to Slack Current with Kernel 2.4.32. The module search was trying to access the wrong folder. I tried each of the suggestions in the previous post. Apparently after upgrading the kernel with swaret you need to run lilo so that it knows that there is a new kernel version. I typed "lilo" at the command prompt and restarted....tada....it worked! Thanks!