question concerning ram filestructure

Greg Griffes ggg at
Wed Apr 10 08:59:45 EST 2002


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.


> >
> > 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

More information about the Linuxppc-embedded mailing list