Subject: Re: initramfs howto?
From: "Bryan O'Sullivan" <bos@serpentine.com>
To: Chris Meadors <clubneon@hereintown.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, Andrew Morton <akpm@osdl.org>
In-Reply-To: <1081451826.238.23.camel@clubneon.priv.hereintown.net>
References: <1081451826.238.23.camel@clubneon.priv.hereintown.net>
Content-Type: text/plain
Message-Id: <1081490209.28834.19.camel@camp4.serpentine.com>
Mime-Version: 1.0
Date: Thu, 08 Apr 2004 22:56:49 -0700
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1356
Lines: 33

On Thu, 2004-04-08 at 12:17, Chris Meadors wrote:

> Then I cpio'd up the
> tree, gzip'd it, and put it where I told grub to find it:
>  "initrd (hd0,0)/boot/test/initramfs.cpio.gz"

Did you use a newc-format cpio archive?  Sounds like yes, but I want to
be sure.

> When I boot the kernel associated with that initrd line, it says that it
> found a compressed image at block 0.  But then panics saying it can't
> mount the root filesystem.

You need a patch to force the kernel not to bother trying to mount a
root filesystem.  This has been floating around for a while somewhere. 
If you don't use this patch, the kernel won't fall through to initramfs
and panics instead, as you are seeing.

Ooh, I see that Olaf Hering has a recent variant of this patch which is
in -aa kernels.  Andrew, can you consider dropping this into -mc or -mm,
please?  It won't break normal operation, but will relieve the pain of
the not-yet-battle-scarred.  It's less fugly than the earlier dev=0:0
patch.  Maybe.

http://www.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.6/2.6.5-rc3-aa1/initramfs-search-for-init

	<b

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/