linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "\"Häpe, Sebastian, HRD/AB\"" <sebastian.haepe@eads.com>
Cc: "'linuxppc-embedded@ozlabs.org'" <linuxppc-embedded@ozlabs.org>
Subject: Re: Problem mounting ramdisk image
Date: Thu, 21 Jul 2005 14:46:38 +0200	[thread overview]
Message-ID: <20050721124638.21ACA3525B2@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 20 Jul 2005 12:35:16 +0200." <2D9AB865A49FD511914700105A0EF6790252BDCE@morse.smart.lfk.eads.net>

In message <2D9AB865A49FD511914700105A0EF6790252BDCE@morse.smart.lfk.eads.net> you wrote:
> 
> I have a litte problem with an initrd-image on a custom board:

It is considered a good idea to search a  bit  in  the  mailing  list
archives  before  posting.  If you had done so, you should have found
several similar requests before (even within the last few  days)  and
saved us all the effort to reiterate the whole thing again.

> Now the following effects occur:
> 
>  -  if i do not tell the kernel which filesystem I have in my image (only
> entering: 'root=/dev/ram rw init=/bin/busybox')

You do not tell it to the kernel, and you don't tell us. This is  not
really helpful. So what is it? ext2?

>     RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 > blocksize
>     RAMDISK: Compressed image found at block 0

Good.

>     Freeing initrd memory: 709k freed
>     Kernel panic: VFS: Unable to mount root fs on 01:00

Did you enable ext2 support in your kernel configuration?


>  -  if I tell the kernel to use TMPFS or RAMFS (rootfs=tmpfs or
> rootfs=ramfs), the error is

You get what you ask for: garbage in, garbage out.

> My distribution (ELinOS) creates two files, 'Image.gz' and > 'Image.initrd'.
> If I extract Image.gz, the full filesystem is extracted. 
> How can I check wheather the 'Image.initrd' file is correct?

How should we know which commands your  distribution  uses  to  build
these images? They can contain anything.

> (U-Boot tells me it is correct if I enter 'imi [address of image]')

Grrrghh.. I wich you had posted complete information at least  for  a
single of your questions. And which sort of image type is reported by
U-Boot?

> Or does anyone did have the same problem? Have I forgotten any kernel
> options?

Yes, many people have asked the same before. It's all in the archives.

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
When in doubt, mumble;   when in trouble, delegate;  when in  charge,
ponder.                                             -- James H. Boren

      reply	other threads:[~2005-07-21 12:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-20 10:35 Problem mounting ramdisk image "Häpe, Sebastian, HRD/AB"
2005-07-21 12:46 ` Wolfgang Denk [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=20050721124638.21ACA3525B2@atlas.denx.de \
    --to=wd@denx.de \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=sebastian.haepe@eads.com \
    /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).