Re: mkinitrd errors.

[seb@frankengul.org]

On Thu, Jul 21, 2005 at 06:55:37PM +0100, Johan Groth wrote:
> Chris Wakefield wrote:
> >Hi all.
> >
> >Since 2.6.12.2 I've not been able to have mkinitrd output an image file.
> >I'm getting this error:
> >/usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed
> >
> >with:
> >mkinitrd -o initrd.img-2.6.12.3 2.6.12.3
> >
> >I'm not worried about the vga16fb or the resulting warning, just the fact 
> >that no image is outputted from this failed modprobe.  Curious problem 
> >with the find, wondering if mkinitrd is broken somehow?
> >
> >Does anyone have any idea as what my problem is?
> 
> mkinitrd nowadays requires you to give a absolute path for the image.
> So it should be:
> mkinitrd -o /my/full/path/initrd.img-2.6.12.3 2.6.12.3
> and you will find the image under /my/full/path.
> 
> 
Try to set -x to check what is wrong.
I used to had problem like this and ended up removing the exit statement
after the error check.

	Seb