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?