Grub and/or kernel problem...

Jamon Camisso jamon.camisso-H217xnMUJC0sA/PxXw9srA at
Tue Nov 15 15:11:50 UTC 2005

Lennart Sorensen wrote:
>>I have considered that the lack of an initrd image could be the problem,
>>but I don't know how to create such an image - the manpage of mkinitrd
>>made absolutely no sense to me, and several attempts have not appeared
>>to help.  Anyone have any ideas?  Thanks.
> Well the root= and such are all set based on the single level comments
> in /boot/grub/menu.lst (which update-grub looks at and then updates with
> kernels found in /boot).
> If you compiled your own kernel, then make sure you used --initrd with
> make-kpkg if you used the same type of modular filesystem/diskdriver
> setup as debian always does (I tend to for most things).  Otherwise the
> kernel will not generate an initrd when installed, and there won't be
> one for grub to use and the kernel will be unable to find the rood
> device.
> Lennart Sorensen

I'm well aware of the debates surrounding modular vs. monlithic kernels; 
however, in this instance wouldn't compiling filesystem modules into the 
kernel itself make an initrd image unnecessary? I've not tried this myself.

The Toronto Linux Users Group.      Meetings:
TLUG requests: Linux topics, No HTML, wrap text below 80 columns

More information about the Legacy mailing list