Linux booting problems

Kenny Donahue kennyd at mc.com
Thu Feb 27 16:05:26 EST 2003


Mark Komarinski wrote:

>On Thu, Feb 27, 2003 at 03:50:49PM -0500, Kenny Donahue wrote:
>  
>
>>pll at lanminds.com wrote:
>>    
>>
>>>I recommend not doing the make install, rather, manually copying
>>>arch/<arch>/boot/bzImage to /boot/vmlinuz-whatever and editing the 
>>>lilo.conf to add a new kernel.  Then run lilo to recognize this new 
>>>kernel and boot from it.
>>>
>>>That way you don't lose your old kernel.
>>>
>>>
>>>      
>>>
>>I did do a make modules.  Sorry about the spelling but I'm typing in anger.
>>I save the output from my "make install" and it does A LOT more then
>>just copy hte bzImage vmlinuz and System map
>>"make install &> /tmp/makeInstallOutput"
>>    
>>
>
>IIRC, the make install also fires off lilo, or at least configures
>lilo for you.  I'd stick to the previously-given advice and move the
>bzImage and System map manually into /boot.  I spent the first few days
>this week wrestling with the kernel, so this is a topical discussion
>for me.
>
>-Mark
>  
>
The "make install" claims that it modifies lilo.conf but it doesn't.
I modify it myself.  I am recompiling now (again :(  ) . I will try it
by hand.
My main questions was why was it trying to load modules when
I built it into the kernel?  I looked at modules.conf. that's ok.
I will look in modules.dep after I'm done. 
One more quick question do I need jbd with ext3? I am not including
it right now.
Thanks,
Kenny





More information about the gnhlug-discuss mailing list