About kernel 2.2 to 2.4
 

Pls. HELP!!

I use "apt-get install 2.4xxx" to install the 2.4 kernel image.

I following the instructions:

Add "initrd=/initrd.img" under the line
"image=/vmlinuz" in lilo.conf

Add "do_initrd = Yes'
in /etc/kernel-img.conf

Type "lilo" to run the loader.

However, the machine cannot boot-up again.

What should I do? Which step I missed?

Pls. HELP!!

Please be more specific: Were you able to start lilo? If yes then what error message comes out when you try to boot your kernel?

Basically, when you ran apt, and you got that message, you should have opened another terminal, added the "initrd=/initrd.img" line under the "image=/vmlinux" portion of your /etc/lilo.conf and then run 'lilo' as root.

Personally, I have it installed under the global (beginning) portion of my lilo, but my setup doesn't demand too much flexibility. Your options now are not fun. One, reinstall. I hate that option, it's effective, but cheap and wasteful. Two, use your bootdisk. You have one, right? :D Then, assuming you can mount your drive, you edit and run lilo to correct the problem. (I never have bootdisks, so I'm a hypocrite, but a hypocrite that has used enough OS's to know how to skip by needing one, too.) Three, you can use your install disk in "rescue" mode (type 'rescue' at the lilo prompt, hit shift while booting if your disk doesn't bring up a lilo prompt at boot). Again, assuming you can mount your drive, you edit and run lilo to correct the problem. Fourth, you can 'chmod' into your drive from another distro (assuming you have another one loaded, or have a "livecd" like knoppix available). To do this, boot the other distro, mount your / drive, edit that partition's /etc/lilo.conf then:

chroot /mnt/otherdrive /sbin/lilo

Assuming, of course, that /mnt/otherdrive is where you mounted your other partition. The /sbin/lilo part is like doing it while that system is running. If you don't chroot, you'll install the lilo version of the system that booted.

Like I said, this is effective, but perhaps hard/scary/confusing for a newbie. It works though, and it's one of the reasons why hardened linux users laugh at winusers similar boot situations.