linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Jin <shawnxjin@gmail.com>
To: "Adrian B. Weissman" <aweissma_ppc@yahoo.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: A question regarding ramdisks
Date: Thu, 1 Sep 2005 10:38:56 -0700	[thread overview]
Message-ID: <c3d0340b050901103871860dac@mail.gmail.com> (raw)
In-Reply-To: <20050901054650.11322.qmail@web35208.mail.mud.yahoo.com>

> Kernel panic - not syncing: VFS: Unable to mount root
> fs on unknown-block(1,0)
>  <0>Rebooting in 180 seconds..

If you're sure that you enable INITRD and EXT2 support in the kernel
and the problem still exist, check if initrd_start and initrd_end are
set correctly in platform_init().

In 2.6.x, parse_bootinfo() doesn't recognize u-boot's bd_t. One quick
and dirty solution is to set initrd_start and initrd_end to r4 and r5
respectively in platform_init().

=09/* set initrd parameters */
#ifdef CONFIG_BLK_DEV_INITRD
=09if (r4) {
=09  =09initrd_start =3D r4 + KERNELBASE;
=09=09initrd_end =3D r5 + KERNELBASE;
=09}
#endif /* CONFIG_BLK_DEV_INITRD */

Regards,
-Shawn.

      parent reply	other threads:[~2005-09-01 17:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-01  5:46 A question regarding ramdisks Adrian B. Weissman
2005-09-01  7:16 ` Murray.Jensen
2005-09-01 17:38 ` Shawn Jin [this message]

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=c3d0340b050901103871860dac@mail.gmail.com \
    --to=shawnxjin@gmail.com \
    --cc=aweissma_ppc@yahoo.com \
    --cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).