Topic: how to boot my new 2.4kernel?

[Patrick]

Hi all,

I built a new kernel for my 5.5box and I'd like to boot it.
I copied them System.map and bzImage to /boot as System.map-2.4.18 and vmlinuz-2.4.18 which I then symlinked to System.map and vmlinuz.
I ran lilo and rebooted but then I saw the 2.2.19 kernel is still used. What did I miss?

[Zaphod Beeblebrox]

Try doing a "man lilo" on a box with manpages installed ...  

You'll want to make sure that /etc/lilo.conf is up to date...

then, as root type:

# lilo

this updates the bootblock to point at the kernel specified in /etc/lilo.conf

It's probably best to put a new lilo entry in for your 2.4 kernel, and keep the 2.2 entry (and kernel files) around - just so that if you really hose your box, you can always boot the 2.2 kernel.

Also, copying just the stuff in /boot isn't enough.  You've also got to worry about kernel modules (in /lib/modules/kernel-version) ...

[Patrick]

Hi,

I didn't forget the modules, I just forgot to mention them:)
I looked at lilo.conf but a) it's templated in 5.5 and b) there is no reference to any kernel at all or so it seems in the 5.5 lilo.conf so what is there to change?

Patrick

[Patrick]

aha, I found it. In the lower part of lilo.conf the boot image is defined:) I was under the impression that all I saw was all there was.