On # Mon, 7 Jul 2003 13:38:35 -0400, Matt Zimmerman wrote:
>> RAMDISK: cramfs filesystem found at block 0
>> RAMDISK: loading 1032 blocks [1 disk] into ram disk... done.
>> Freeing initrd memory: 1032k freed
>> cramfs: wrong magic
>> Kernel panic: VFS: Unable to mount root fs on 03:01
> Strange...it is recognized as a cramfs filesystem, but then fails to mount.
> Are you able to mount the initrd using a loop device?
Yes, I am. Here is what it contains:
124 Jul 7 20:09 bin
104 Jul 7 20:09 dev
0 Jul 7 20:08 devfs
24 Jul 7 20:09 etc
72 Jul 7 20:08 lib
566 Jul 7 20:08 linuxrc
48 Mar 13 2002 linuxrc.conf
137 Mar 13 2002 loadmodules
0 Mar 13 2002 mnt
0 Nov 22 2002 proc
80 Nov 22 2002 sbin
0 Mar 13 2002 script
0 Mar 13 2002 scripts
0 Mar 13 2002 tmp
16 Nov 22 2002 usr
0 Feb 2 2002 var
I must confess that I cannot see whether something is wrong here.
[I left the image at:
http://simbol.math.hr/~nenad/test/initrd.img-2.4.22-pre3c0
if somebody cares to look at it.]
> > Besides, it does not (yet) contain some of the features I need (e.g.
>> new ACPI).
> Neither does kernel.org source, and you can patch both of them easily.
Could I just use acpi-20030619 patch from ACPI project page, and apply
it to kernel-source-2.4.21-2? It was not working in 2.4.20.
--- Nenad.
