I had just installed Gentoo, emerged kde, and then recompiled my kernel in order to get some modules I had left out. I replaced the old kernel with the new (I figured since I had simple added a module, adding a new kernel file wouldn't be a big idea). My machine then hung on reboot. A simple /sbin/lilo being run after I had overwritten the old kernel would've prevented this, and I had no idea it needed to be done until someone on the forums asked if I'd already attempted it. Perhaps just a tiny blurb stating this (or is it there and I missed it--entirely possible)? Thanks! Reproducible: Always Steps to Reproduce: 1. Get a working system using LILO as the bootloader. 2. Recompile kernel, copy bzImage over the kernel image in /boot. 3. Reboot WITHOUT doing an /sbin/lilo. Actual Results: System froze on "Loading Gentoo........................."
During the installation of Gentoo, when installing LILO, the following is mentioned: """ Now save the file and exit. To finish up, you have to run /sbin/lilo so LILO can apply the /etc/lilo.conf to your system (i.e. install itself on the disk). Code Listing 13: Finishing the LILO installation # /sbin/lilo """ It's listed if you know what was meant with "apply the /etc/lilo.conf to your system", but that's not trivial :) I'll update the instructions to note that this must happen too when you install a new kernel.
Fixed in CVS.
