Thanks very much for your reply!
- I am kind of locked into using the 2.4.0 kernel, although I am not using a
"test" version. I am using the initial "official" release. Hopefully cramfs
is not broken in that kernel.
- As to setting the "unused" portions of the ramdisk to 0xff, I guess that I
am a little bit confused. My "ramdisk" image consists of the cramfs image
created by mkcramfs. My understanding is that the ramdisk mechanism simply
decompresses the cramfs image ( which I gzipped before I give it to the
kernel, which is looking for a compressed image ) and copies the blocks into
a place in memory where they are used. In this context, I am not sure which
part of the "partition" would be unused.
Does that make sense? I think that your suggestion could very well be
related to my problem, but I am not sure as to how it applies to my
scenerio. What do you think?
Thanks again,
-Joe
-----Original Message-----
From: Cliff Brake [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 19, 2001 10:02 AM
To: '[EMAIL PROTECTED]'; Edwards, Joseph W
Subject: RE: ramdisk using cramfs
I have not tried to use cramfs with a ramdisk, but I have used cramfs with
the MTD flash layer. The mkcramfs utility works fine with ARM-Linux. Two
suggestions:
* upgrade to the latest kernel. I think cramfs was broke a couple times
during the 2.4.0-test series.
* make sure you set unused portions of the ramdisk to 0xff. It seems that
unused portions of a partition must be erased for cramfs/jffs to work.
Cliff
>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]]On Behalf Of Edwards,
>Joseph W
>Sent: Monday, March 19, 2001 11:48 AM
>To: '[EMAIL PROTECTED]'
>Subject: ramdisk using cramfs
>
>
>I have been trying for a couple of weeks now to get cramfs to work on a
>SA-1110 board. My development platform is running a 2.2 kernel, and the
>SA1110 is running a 2.4.0 rmk2 kernel. My goal is to load the
>cramfs image
>into memory on the StrongARM board and mount it as the root device as a
>ramdisk. Originally, I kept getting the message "wrong magic,"
>but then I
>booted the kernel with the parameter "ramdisk_blocksize=4096",
>which in some
>cases will give me the message "cannot find init", and much
>more commonly
>will give the error:
>
>VFS: Mounted root (cramfs filesystem).
>Freeing init memory: 44K
>attempt to access beyond end of device
>01:00: rw=0, want 2950544, limit=4096
>attempt to access beyond end of device
>01:00: rw=0, want 2950548, limit=4096
>attempt to access beyond end of device
>01:00: rw=0, want 2950552, limit=4096
>Error -3 while decompressing!
>
>Is it possible that the mkcramfs that I have needs to be
>modified to make
>images that will work on a SA1110 platform?
>
>Any insight that anyone could give me into what might be going
>on with this
>would be greatly appreciated! Please let me know if I have left out any
>important details. Thanks very much for your help!
>
>-Joe Edwards
>
>
>
>
>_______________________________________________
>http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
>Please visit the above address for information on this list.
_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.
