Hey! So how come LILO doesn't acknowledge my new 2.6 kernel?

Welp. I went out on a limb as a big, fat NOOB and decided to try my hand at compiling the new kernel. I followed all the steps correctly according to several posts and other, off-site articles. Everything went smoothly, and at the end of the process, the compiler spit out the location of the new kernel.

I copied the new kernel and System.map file to /boot. Next, I added the location of the new kernel to LILO. I ran lilo -t and it said "Added Linux265". No errors from LILO here.

Yet when I reboot, I only have the one option for my old 2.4 kernel.

What'd I do wrong?

I also had the same issu.it would help me also.
I didnt copy the system map file though.

I edit /etc/lilo.conf and no changes are reflected.



Thanks

If something's not working, it helps to provide a bit more information, like a copy of lilo.conf, for example. <EDIT> Errr, you're running lilo with the -t option?
</EDIT>

And gianh, make sure that any time you change lilo.conf you run the command 'lilo' as root. Even if you didn't change lilo.conf, and just replaced a kernel in your boot directory with a different kernel of the same name.

Nevermind. I fixed it.

To gianh:

I forgot to run straight up "lilo" to make my changes official with the boot loader. Maybe you forgot that step too.

But now I have that blank screen problem with the new kernel! Guess that's a different thread.

Do you by any chance have frame buffer enabled?

Don't know. how do I check?