linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "David Grab" <d.grab@hima.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: AW: initrd rootfs ramdisk
Date: Tue, 05 Jul 2005 18:01:49 +0200	[thread overview]
Message-ID: <20050705160149.3BDF7353A5E@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 05 Jul 2005 13:18:54 +0200." <000801c58153$54af2400$f201a8c0@SN7606>

In message <000801c58153$54af2400$f201a8c0@SN7606> you wrote:
> 
> >But the kernel prints the boot parameters just fine.
> 
> Maybe because i defined it in kernel configuration! But from u-boot i don´t
> get any arguments.

Then you must be using a wrong image type. Are you sure you use "make
uImage" to build your kernel image for U-Boot?

> I thougt i can give the linux kernel position from u-boot where initrd is
> located, but i have the same problem.

You don;t. U-Boot passes this information automatically.

> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> loop: loaded (max 8 devices)
> VFS: Cannot open root device "<NULL>" or unknown-block(3,1)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(3,1)

Block device 3, 1 is /dev/hda1 - is your ramdisk known to be working?


Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"The majority of the stupid is  invincible  and  guaranteed  for  all
time.  The  terror  of their tyranny, however, is alleviated by their
lack of consistency."                               - Albert Einstein

  reply	other threads:[~2005-07-05 16:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-05  6:36 initrd rootfs ramdisk David Grab
2005-07-05  8:18 ` Wolfgang Denk
2005-07-05 11:18   ` AW: " David Grab
2005-07-05 16:01     ` Wolfgang Denk [this message]
2005-07-06  9:07       ` AW: " David Grab
2005-07-06 10:30         ` David Grab

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=20050705160149.3BDF7353A5E@atlas.denx.de \
    --to=wd@denx.de \
    --cc=d.grab@hima.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).