Problem mounting ramdisk image

Problem mounting ramdisk image

["Häpe, Sebastian, HRD/AB"]

Hi everybody,

I have a litte problem with an initrd-image on a custom board:

I created a gzip-compressed image of an initrd which is loaded to RAM =
by the
bootloader (U-Boot) before it starts the kernel. The kernel is compiled =
with
support for initial ramdisks and knows the right addresses of the image =
in
RAM.
Now the following effects occur:

 -  if i do not tell the kernel which filesystem I have in my image =
(only
entering: 'root=3D/dev/ram rw init=3D/bin/busybox')
    he tells me the following:
   =20
    RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 =
blocksize
    RAMDISK: Compressed image found at block 0
    Freeing initrd memory: 709k freed
    Kernel panic: VFS: Unable to mount root fs on 01:00

 -  if I tell the kernel to use TMPFS or RAMFS (rootfs=3Dtmpfs or
rootfs=3Dramfs), the error is

    RAMDISK: Compressed image found at block 0
    Freeing initrd memory: 709k freed
    VFS: Mounted root filesystem (tmpfs/ramfs)
    Kernel panic: No init found. Try to pass init=3D... To the kernel =
command
line    =20

    When I examine the return value of the execve() function, I get
error-code 2, which means: File or directory not found

My distribution (ELinOS) creates two files, 'Image.gz' and =
'Image.initrd'.
If I extract Image.gz, the full filesystem is extracted.=20
How can I check wheather the 'Image.initrd' file is correct?
(U-Boot tells me it is correct if I enter 'imi [address of image]')

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

Greetings,
Sebastian H=E4pe

Re: Problem mounting ramdisk image

[Wolfgang Denk]

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