Grub and/or kernel problem...
William O'Higgins Witteman
william.ohiggins-H217xnMUJC0sA/PxXw9srA at public.gmane.org
Tue Nov 15 17:31:45 UTC 2005
On Tue, Nov 15, 2005 at 10:11:50AM -0500, Jamon Camisso wrote:
>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
Aha! Using the "--initrd" option on the make-kpkg worked very neatly.
>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.
Probably, but not in my case. I use Debian because I rarely need to
think about kernels, or drivers, or anything at all - apt-get and go.
However, I needed the kernel headers to get my Wacom tablet working (I
used this guide: http://www.i3s.unice.fr/~ol/success.html) and I could
not apt-get the headers for my kernel anymore, so I needed a new kernel
for the headers to relate to. I never used to make an initrd, but now I
seem to need to. Live and learn.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 189 bytes
Desc: Digital signature
More information about the Legacy