public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>
Subject: Re: initramfs howto?
Date: Thu, 08 Apr 2004 22:56:49 -0700	[thread overview]
Message-ID: <1081490209.28834.19.camel@camp4.serpentine.com> (raw)
In-Reply-To: <1081451826.238.23.camel@clubneon.priv.hereintown.net>

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


  reply	other threads:[~2004-04-09  5:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08 19:17 initramfs howto? Chris Meadors
2004-04-09  5:56 ` Bryan O'Sullivan [this message]
2004-04-09  6:48   ` Miles Bader
2004-04-09 17:21     ` Bryan O'Sullivan
2004-04-10  0:50       ` Miles Bader
2004-04-19 19:48       ` Chris Lingard
2004-04-19 21:39         ` H. Peter Anvin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1081490209.28834.19.camel@camp4.serpentine.com \
    --to=bos@serpentine.com \
    --cc=akpm@osdl.org \
    --cc=clubneon@hereintown.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox