All,

I compiled a new kernel (from 2.2.20 to 2.4.18). The compile went well and everything appeared to be correct. I checked the link for /vmlinuz and /boot/vmlinuz. Both are pointing to the new kernel (/boot/vmlinuz-2.4.18). The system.map and config-2.4.18 files are in the /boot directory. I updated the lilo config, as I am using lilo as my boot loader. There were no errors when the kernel was compiled.

Here is my problem: Everytime I start the machine, it loads the OLD kernel (vmlinuz-2.2.20-idepci). I can not find any references to the old kernel at all. Every link I have points to the new kernel.

Any ideas? I'm stumped!

Thanks

Mike

run `/sbin/lilo`

I forgot to mention that in the original post -- but I did run /sbin/lilo. It ran with no problems. the problem still persisted.........

can you post /etc/lilo.conf?

The current lilo.conf:

boot=/dev/hda1
root=/dev/hda1
compact
install=/boot/boot.b
map=/boot/map
vga=normal
delay=20
image=/vmlinuz
label = Linux
read-only


notes:
mikelinux3:/# ls -l /vmlinuz
lrwxrwxrwx 1 root root 19 Feb 27 12:54 /vmlinuz -> boot/vmlinuz-2.4.18
mikelinux3:/# ls -l /boot/vmlinuz
lrwxrwxrwx 1 root root 8 Feb 27 06:38 /boot/vmlinuz -> /vmlinuz

the only thing that screams at me is the lack of an absolute path to vmlinuz-2.4.18
it's missing a `/`
lrwxrwxrwx 1 root root 19 Feb 27 12:54 /vmlinuz -> boot/vmlinuz-2.4.18 should be
lrwxrwxrwx 1 root root 19 Feb 27 12:54 /vmlinuz -> /boot/vmlinuz-2.4.18

also, /boot/vmlinuz should link directly to vmlinuz-2.4.18 rather than to /vmlinuz -> boot/vmlinuz

another thing, if you uncomment line 77 of /usr/src/linux-2.4.18/Makefile, then run `make install` it automagically puts things in the right place.

You may also point lilo.conf directly to /boot/vmlinuz-2.4.18, it doesn't much care.

I made the changes you recommended... the problem persists...

SLAP!!!!

I missed it...

boot=/dev/hda #not hda1

then rerun lilo

This causes lilo to install to the MBR, which gets read at boot, as opposed to the partittion, which doesn't