public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Eric Buddington <ebuddington@verizon.net>
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com
Subject: Re: /init not found in initramfs in 2.6.27.[34]
Date: Tue, 11 Nov 2008 11:19:22 +0000	[thread overview]
Message-ID: <20081111111922.GA8485@hack.voiplan.pt> (raw)
In-Reply-To: <20081110232313.GA29539@pool-96-236-120-128.spfdma.east.verizon.net>

On Mon, Nov 10, 2008 at 11:23:14PM +0000, Eric Buddington wrote:
>I am successfully booting into an initramfs under 2.6.26.5.
>
>However, on 2.6.27.3 and 2.6.27.4, the kernel uncompresses the
>initramfs, then complains that it can't find /init. I am using the
>same initramfs.cpio.gz in all cases, and the newer kernels have a
>.config derived from the working kernel
>
>I have tried compiling the initramfs into the kernel, loading it via
>the initrd= parameter, and doing both simultaneously, with no success.
>
>I see no discussion of this on the lists, so it's probable that I'm
>doing something stupid - but I can't see what would have changed
>between kernels and I know the initramfs.cpio.gz is good.
>

Looks weird...


>Here is the .config from my non-working 2.6.27.4:
>

<snip>

Do you use the same config for 2.6.26.5 and 2.6.27.4 ?
If not, could you please send the diff between these two configs?

Thanks.

Cc: hpa@zytor.com

-- 
"Sometimes The Only way to stay sane is to go a little crazy."


  reply	other threads:[~2008-11-11 11:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-10 23:23 /init not found in initramfs in 2.6.27.[34] Eric Buddington
2008-11-11 11:19 ` Américo Wang [this message]
2008-11-12 19:02   ` Eric Buddington
2008-11-12 19:01     ` H. Peter Anvin
2008-11-12 19:19       ` Eric Buddington
2008-11-17 10:28         ` Américo Wang

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=20081111111922.GA8485@hack.voiplan.pt \
    --to=xiyou.wangcong@gmail.com \
    --cc=ebuddington@verizon.net \
    --cc=hpa@zytor.com \
    --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