Re: Bug#341738: linux-image-2.6.14-2-686: Could not read output for /sbin/modprobe -v -n --show-depends --set-version 2.6.14-2-686 auto (fatal)
On Sat, Dec 03, 2005 at 10:18:53AM +0200, Jari Aalto wrote:
> Erik van Konijnenburg <ekonijn@xs4all.nl> writes:
> | On Fri, Dec 02, 2005 at 06:36:41PM +0200, Jari Aalto wrote:
> | > Setting up linux-image-2.6.14-2-686 (2.6.14-4) ...
> | > Using /usr/sbin/mkinitrd.yaird to build the ramdisk.
> | > Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd /usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs.
> | > yaird error: Could not read output for /sbin/modprobe -v -n --show-depends --set-version 2.6.14-2-686 auto (fatal)
> |
> | Could you post the output of yaird -d -o /tmp/junk.img 2.6.14-2-686?
> | and dpkg -l yaird?
> ii yaird 0.0.11-12 Yet Another mkInitRD
OK, that's the most recent.
> root@host:~# yaird -d -o /tmp/junk.img 2.6.14-2-686
Output that follows looks correct: it seems you have fstype 'auto' in your
/etc/fstab entry for root, and yaird determines that the filesystem is
reisrfs. Versions prior to 0.0.11-12 had the problem you show in
parsing auto in fstab.
That suggests the problem is in how yaird is invoked. Perhaps the
kernel install script invokes a broken copy of yaird?
Things to check:
-- debsums -a yaird
if it says a anything other than ok ok ok, reinstall yaird.
-- hack /usr/sbin/mkinitrd.yaird to echo the yaird command line
and its own arguments to some scratch file, then do
dpkg-reconfigure linux-image-2.6.14-2-686
and see if there's a difference from the yaird call you did
just now.
Or, if getting the new kernel running is more interesting to you
than finding out the cause, replace the 'auto' keyword in your fstab
with the appropriate file system type.
Regards,
Erik
Reply to: