question concerning ram filestructure

question concerning ram filestructure

[Steven Blakeslee]

I'm working with linux 2.4 on an embedded planet ep405.  I have been trying
to get a ram file structure working but I'm getting a reoccuring error.

RAMDISK: Compressed image found at block 0
crc errorFreeing initrd memory: 2201k freed
Kernel panic: VFS: Unable to mount root fs on 01:00
<0>Rebooting in 180 seconds..

I've seen this before on different ports of linux but I have not been able
to figure it out.  Does anyone have suggestions?
Steven Blakeslee

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: question concerning ram filestructure

[Greg Griffes]

>
> RAMDISK: Compressed image found at block 0
> crc errorFreeing initrd memory: 2201k freed
> Kernel panic: VFS: Unable to mount root fs on 01:00
> <0>Rebooting in 180 seconds..
>
> I've seen this before on different ports of linux but I have not been able
> to figure it out.  Does anyone have suggestions?
> Steven Blakeslee
>

I just had the same symptom in my port this morning.  In my case, the
kernel was not picking up the initrd_start or initrd_size from the boot
loader.  It was a bug in my *_setup.c file.  I tossed out the use of r4 and r5
and switched to using parse_bootinfo in platform_init().  That fixed it.

It could also be a problem in the boot loader.

Greg Griffes


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: question concerning ram filestructure

[Greg Griffes]

Steven,

I must retract my previous message.  After closer scrutiny of your
log message, I realized that you are getting a crc error, I assume
during the decompression.  I did not have that problem.

I wonder if it could be a difference in gzip that is used to compress
the ram disk on the host and the gunzip version built into your kernel.
Just speculating.

Greg

>
> >
> > RAMDISK: Compressed image found at block 0
> > crc errorFreeing initrd memory: 2201k freed
> > Kernel panic: VFS: Unable to mount root fs on 01:00
> > <0>Rebooting in 180 seconds..
> >
> > I've seen this before on different ports of linux but I have not been able
> > to figure it out.  Does anyone have suggestions?
> > Steven Blakeslee
> >
>
> I just had the same symptom in my port this morning.  In my case, the
> kernel was not picking up the initrd_start or initrd_size from the boot
> loader.  It was a bug in my *_setup.c file.  I tossed out the use of r4 and r5
> and switched to using parse_bootinfo in platform_init().  That fixed it.
>
> It could also be a problem in the boot loader.
>
> Greg Griffes
>
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: question concerning ram filestructure

[Alex Zeffertt]

Are you using mkimage to build a ppcboot-compatible ramdisk?  If not then have a look at SELF on
denx's FTP site for an example of how to build make one.

Alex

Steven Blakeslee wrote:

> I'm working with linux 2.4 on an embedded planet ep405.  I have been trying
> to get a ram file structure working but I'm getting a reoccuring error.
>
> RAMDISK: Compressed image found at block 0
> crc errorFreeing initrd memory: 2201k freed
> Kernel panic: VFS: Unable to mount root fs on 01:00
> <0>Rebooting in 180 seconds..
>
> I've seen this before on different ports of linux but I have not been able
> to figure it out.  Does anyone have suggestions?
> Steven Blakeslee
>
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/