I recently upgraded my version of Debian from 3.0r1 to 3.0r2 without any apparent problems. I then attempted to upgrade my kernel from 2.2.18 to 2.4.25. I first grabbed a precompiled kernel and installed it. When I rebooted, it got to the "LILO 22.2 ......." part, then my system reboot itself. And on and on this cycle went. I then attempted to compile my own kernel. The compilation process completed without errors. I then installed it with "dpkg -i" and again, no errors. When I rebooted the system, I had the same problem as before.

in /boot, there are the files
system.map-2.4.25
config-2.4.25
vmlinuz-2.4.25

along with a bunch of other stuff

in my /usr/src, I have
kernel-image-2.4.25_MyKernel2.4.25.deb
linux -> linux-2.4.25
linux-2.4.25

and in lilo.conf, I have
...
default=linux
image-/vmlinuz
label=Linux
initrd=/initrd.img
read-only

image-/vmlinuz.old
label=LinuxOLD
read-only
optional
...

So, I think my problem is with the linking of some file, but I dont know how to fix it without breaking things more then they are now. Shouldnt the install of the .deb file take care of all the correct linking? This is my first linux box and my first kernel compilation, so I am still trying to feel all this stuff out.

Also, as I was reading different howto's, I saw vmlinuz and bmlinuz refered to a couple of times. I think these have something to do with the kernel being to big, but I cant wrap my brain around the whole concept. Where would be a good place to get a good overview on this stuff?

Thanks in advance.

Maybe it's not the solution, but initrd=/initrd.img is not used with custom kernels. Might this be the problem?

You might want to switch to GRUB instead of LILO. GRUB is very easy to use and very clear about what it does. Bootlines can be changed at boottime and updating the bootmenu is very easy. (I had some real bad experiences with LILO, can you tell )

Add new entries in lilo.conf that point to your new kernel.

In example, add this:

image-/boot/vmlinuz-2.4.25
label=2.4.25
read-only
optional

run lilo -v as root. reboot. enjoy. Also, you can simply look at where the /vmlinuz symlinks point to (it will be a kernel in /boot) and replace them.

Normally, the deb install process specifically explains that to you. Did you enter through the text prompts without seeing this?

You want to do:

and then re-run lilo -v

If you are on x86 architecture don't worry about the kernel being "too big" unless you have gobs of stuff built in (like ALL the scsi drivers, all the video stuff, et al). Pay attention to the dates of those how-tos also. Often you find out-dated information (or info. that doesn't apply to your situation). The debian docs in /usr/share/doc are close to always correct.

If you make the correct symlinks and run lilo -v you'll be ok on next boot.

Good luck!

No luck, Im still in the same sticky loop. My root looks like this

lrwxrwxrwx 1 root root 20 Apr 14 22:13 vmlinuz -> /boot/vmlinuz-2.4.25
lrwxrwxrwx 1 root root 27 Apr 14 22:14 vmlinuz.old -> /boot/vmlinuz-2.2.20-idepci

my lilo.conf looks like this

default=Linux

image=/vmlinuz
label=Linux
# initrd=/initrd.img
read-only
# restricted
# alias=1

image=/vmlinuz.old
label=LinuxOLD
read-only
optional
# restricted

when I run "lilo -v" I get

LILO version 22.2, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2001 John Coffman
Released 05-Feb-2002 and compiled at 20:57:26 on Apr 13 2002.
MAX_IMAGES = 27

Reading boot sector from /dev/hda
Merging with /boot/boot-menu.b
Boot image: /vmlinuz -> /boot/vmlinuz-2.4.25
Fatal: read /vmlinuz: No such file or directory

This last message I dont understand because right before I rebooted, I ran the same command and got the messages "Added Linux *" for /vmlinuz and "Added LinuxOLD" /vmlinuz.old".