All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Andrew Walrond <andrew@walrond.org>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: (Sparc64) 2.6.20 seems to ignore initramfs
Date: Fri, 23 Feb 2007 13:32:30 +0000	[thread overview]
Message-ID: <45DEECEE.6070108@wpkg.org> (raw)
In-Reply-To: <200702231108.10185.andrew@walrond.org>

Andrew Walrond schrieb:
> On a Sun T1000 I am trying to boot 2.6.20 using initramfs. (I use the same 
> procedure successfully on x86_64 and itanium2 servers).
> 
> The relevent silo section looks like this:
> 
> image=/boot/2.6.20.image
>         label=2.6.20
>         initrd=/boot/2.6.20.initramfs
>         partition=2
>         read-only
> 
> The kernel loads and boots and I see
> 

(...)

> 
> So it knows about the initramfs, but then tries to mount a root filesystem 
> instead...
> 
> I haven't tried this (initramfs)  with earlier kernels, so I don't know 
> whether this is a regression. Any clues about how to solve this would be 
> greatly appreciated.

Does it make a difference if you embed initramfs directly in the kernel?

CONFIG_INITRAMFS_SOURCE="/path/to/your/initramfs/directory"


-- 
Tomasz Chmielewski
http://wpkg.org


WARNING: multiple messages have this Message-ID (diff)
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Andrew Walrond <andrew@walrond.org>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: (Sparc64) 2.6.20 seems to ignore initramfs
Date: Fri, 23 Feb 2007 14:32:30 +0100	[thread overview]
Message-ID: <45DEECEE.6070108@wpkg.org> (raw)
In-Reply-To: <200702231108.10185.andrew@walrond.org>

Andrew Walrond schrieb:
> On a Sun T1000 I am trying to boot 2.6.20 using initramfs. (I use the same 
> procedure successfully on x86_64 and itanium2 servers).
> 
> The relevent silo section looks like this:
> 
> image=/boot/2.6.20.image
>         label=2.6.20
>         initrd=/boot/2.6.20.initramfs
>         partition=2
>         read-only
> 
> The kernel loads and boots and I see
> 

(...)

> 
> So it knows about the initramfs, but then tries to mount a root filesystem 
> instead...
> 
> I haven't tried this (initramfs)  with earlier kernels, so I don't know 
> whether this is a regression. Any clues about how to solve this would be 
> greatly appreciated.

Does it make a difference if you embed initramfs directly in the kernel?

CONFIG_INITRAMFS_SOURCE="/path/to/your/initramfs/directory"


-- 
Tomasz Chmielewski
http://wpkg.org


  reply	other threads:[~2007-02-23 13:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23 11:08 (Sparc64) 2.6.20 seems to ignore initramfs Andrew Walrond
2007-02-23 13:32 ` Tomasz Chmielewski [this message]
2007-02-23 13:32   ` Tomasz Chmielewski
2007-02-23 14:46   ` Andrew Walrond
2007-02-23 15:17     ` Tomasz Chmielewski
2007-02-23 15:17       ` Tomasz Chmielewski
2007-02-23 15:47       ` Andrew Walrond
2007-02-24 15:23         ` Jan Engelhardt
2007-02-24 15:23           ` Jan Engelhardt
2007-02-24 16:35           ` Andrew Walrond

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=45DEECEE.6070108@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=andrew@walrond.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.