Re: Kernel 2.6 compile problem - Solved

[Russ Cook <russcook@mbo.net>]

David Clymer wrote:

> On Thu, 2004-10-21 at 07:06, Russ Cook wrote:
>  
>
> > >      
> > The problem turned out to be the lack of module-init-tools on my 
> > system.  An additional problem was that module-init-tools conflicted 
> > with modutils already installed.  I had to upgrade modutils to most 
> > current version first, then install module-init-tools.  All is fine now, 
> > except that during the process of upgrading all my packages (which 
> > probably wasn't necessary) I have lost my /boot/boot.b -> 
> > /boot/boot-menu.b .  The system boots into vmlinuz-2.6.8 just fine, and 
> > my modules load, but I don't have a menu option for booting into the 
> > previous kernel.  I need to obtain another boot-menu.b somehow.
> >
> >    
>
> you may need to set a boot delay in /etc/lilo.conf. If you do that, you
> will be able to select a kernel to boot. 
>
> Take a look at 
> http://www.linuxheadquarters.com/howto/basic/lilo.shtml
>
> or man lilo.conf for more details.
>
> -davidc
>
>
>  
No, the problem APPEARS to be that /boot/boot.b is a symlink pointing to 
/boot/boot-menu.b .  And, boot-menu.b does not exist.  I have no *.b 
files except boot.b .
I tried reinstalling lilo and running lilo again, but nothing changed.  
This confuses me, because I thought the *.b file was the secondary boot 
loader, phase 2 of the boot process, and the system wouldn't boot 
without it.  So, off to do some more digging.