Booting into wrong kernel version

[Leck]

Hi. I'm a relative newbie, and I've just installed Debian Linux. The kernel was 2.2.20, so I recompiled to 2.4.18, but it still boots into 2.2.20. I'm pretty sure I compiled the kernel properly.

I edited /etc/lilo.conf, and ran /sbin/lilo, which works (no errors), but whatever I put in there, it ignores it and boots into 2.2.20 regardless.

It seems like it's totally ignoring lilo.conf, did I do something wrong, or is my lilo.conf just not set up right?

[Leck]

My lilo.conf follows:


boot=/dev/hda2
root=/dev/hda2
LBA32
install=/boot/boot.b
map=/boot/map
prompt
timeout=50
message=/boot/message

image=/boot/vmlinuz-2.4.18.280303
label=Linux-2.4.18
read-only

image=/boot/vmlinux-2.2.20-idepci
label=Linux-2.2.20
read-only

[Hayl]

if you compile the kernel the debian way, it will do all this stuff for you.

attached are instructions on how to compile a kernal the debian way.

[camelrider]

You could lengthen the timeout so you could choose which kernel to boot or you could add a line:
default=Linux-2.4.18
above the individual stanzas in /etc/lilo.conf.

[Leck]

My problem is that I did do it the Debian way, which is why I'm puzzled that it didn't work.

I've tried putting in timeout=100, but it doesn't make any difference. I'm not getting any choices at all at startup. Even default=Linux-2.4.18 doens't make any difference, it still boots into 2.2.20

[Leck]

I fixed it. I had to change 'boot=/dev/hda2' which it put in automatically, to 'boot='dev/hda'. Now it actually listens to the rest of my lilo.conf.

Only now my Kernel won't boot... but that's a different problem...