Yes, I can boot the system with initrd, and mount the cramfs and access all the files. I also did use -r option to build the filesystem image.
I do not have proc built inside the kernel and no /proc directory. I do not have any /var and /tmp directories in the cramfs. How do I mount /var or /tmp inside the ram? What else should I check? I have 2.4.18 stock kernel. Am I supposed to apply any patch for cramfs to work? Lokesh -----Original Message----- From: Wolfgang Denk To: Lokesh Kumar Cc: linuxppc-embedded at lists.linuxppc.org Sent: 2/29/04 11:31 AM Subject: Re: cramfs mpc8xx 2.4.18 In message <294FD9D3403A0340BDAC38E48DCEFFDCA751 at RES-EXCH> you wrote: > > Kernel command line: root=/dev/mtdblock1 rootfstype=cramfs console=ttyS0,9600 ... > ok > mtdblock_open > mtdblock: read on "cramfs" at 0x0, size 0x1000 > mtdblock: read on "cramfs" at 0x1000, size 0x1000 > mtdblock: read on "cramfs" at 0x2000, size 0x1000 > mtdblock: read on "cramfs" at 0x3000, size 0x1000 > mtdblock_release > > And after this, I do not get the prompt back, and the target hangs. My > cramfs rootfilesystem has > > /bin, /dev, /etc, /sbin, /lib and /usr/sbin Are you sure? Can you mount the same filesystem when running with root filesystem mounted over NFS or from a ramdisk? Did you remember that you might need the "-r" option (reverse endian-ness of filesystem) when creating the filesystem? Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de I distrust all systematisers, and avoid them. The will to a system shows a lack of honesty. - Friedrich Wilhelm Nietzsche _G?tzen-D?mmerung [The Twilight of the Idols]_ ``Maxims and Missiles'' no. 26 ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
