All of a sudden one day after a reboot my slackware machine is booting the wrong kernel. The kernel I am supposed to be running is 2.4.25 and the uname -a command is showing 2.4.22. I have no idea how this could have changed.

the link in /usr/src for linux is set to the 2.4.25 directory
/boot/vmlinuz is pointing to 2.4.25

I am using a boot disk to boot the system so I really dont think that would have changed at all ever. When booting it is showing errors trying to get modules from /lib/modules/2.4.22 and not 2.4.25. I dont know where to point to the correct location for the desired kernel.

My lsmod command shows nothing so no modules are being loaded at all. Any help would be greatly appreciated

what bootloader are you running?

if you are using lilo,

edit /etc/lilo.conf
and specify the kernels that should be available right before boot time,
also change the default kernel setting to the kernel that should be booted after timeout=n

and simply save the changes, and type,

/sbin/lilo
at the shell, then reboot.

NOTE: This will simply change the default kernel that boots, and you can make sure the kernel you are supposed to be booting is in the lilo.conf file so that it "can be booted" .

everything in lilo.conf file looks like it is pointing to the correct spot. I am using a boot disk that I made upon installation. I tried to write the boot loader info to the MBR with /sbin/lilo -M /dev/hda with no luck. It came up saying non-system disk error. I dont know how to make another boot disk with slackware either

The only thing I can think of is that when you used m ake menuconfig to compile a new kernel the version numbers got changed somehow, or you really are booted into a 2.4.22 kernel and forgot to do something with the 2.4.25 setup.

EDIT: recreate a bootdisk with a version number, that is why you are still booting 2.4.22

your bootdisk.

man mkbootdisk

Have you even compiled the kernel yet for the 2.4.25 kernel? (dumb question, but have you?)

ASLO, my man lilo doesnt show an -M , command, maybe mine is old,.

slackware doesnt have the mkbootdisk command. I didnt compile my own kernel but updated with swaret......so that may be my problem. I have another partition that used to have mandrake on it but now will be wiped for a fresh install. I will keep playing with it to check out and see if I can figure it out. Thanks for all your help!