Hi Jay, On Tue, Feb 01, 2005 at 11:22:25PM -0600, Jay Austad wrote: > This is for my a768i phone. Does anyone have any idea how I would go > about reading /dev/roflash? I can't even cat it to a file. However, > it's readable on boot, it has to be because it contains the root > filesystem according to this: I don't know why you would not be able to cat from it, looks like it holds your root fs, I can cat from my harddrive raw partition. Could it be an initrd root fs? > # cat /proc/roflash_info > ROFLASH Driver status: Ready > > ROFLASH area name is rootfs > ROFLASH area size = 15728640 bytes > ROFLASH area offset = 1048576 bytes > ROFLASH area l_x_b(10) > ROFLASH area name is language > ROFLASH area size = 11141120 bytes > ROFLASH area offset = 5242880 bytes > ROFLASH area l_x_b(1000) > ROFLASH area name is setup > ROFLASH area size = 131072 bytes > ROFLASH area offset = 16384000 bytes > ROFLASH area l_x_b(1000) > # I wonder if this is an odd driver. I did a google on ROFLASH, but didn't get anywhere. How about lsmod? Or can you find the driver associated with it? How can we figure out the driver associated with /dev/roflash? Where does it come from? Have you done a dmesg to get the kernel log? Don't forget cat /proc/mounts, /proc/filesystems > Also /dev/mtd0 through /dev/mtd3 have info on them, but only 2 and 3 > appear in /dev. Any ideas how to work around this? I tried mknod and > got an operation not permitted error. How can you be sure mtd0 to mtd3 have info, but only 2,3 are in /dev? How would you access them if they don't have dev nodes setup? cramfs is read only, so that might explain the not permitted error, you could try writing on /tmp, or /ram. > Here are the mounted filesystems: > /dev/root on / type cramfs (rw) > none on /ram type ramfs (rw) > proc on /ram/proc type proc (rw) > /dev/roflash1 on /usr/language type cramfs (rw) > /dev/roflash2 on /usr/setup type cramfs (rw) > none on /dev/pts type devpts (rw) > /dev/mtdblock2 on /ezxlocal type vfm (rw,noatime) > /dev/tffsa1 on /diska type ext3 (rw,noatime) > Only /ezxlocal and /diska are writeable, even though they all say (rw). The cramfs is made with mkcramfs or some such tool, then it is dd'ed direct to a partition. You can dd it back to file, then mount it loop. The mtd0,mtd1 if I remember correct are associated with mtdblock0,1, and are used for indirect operations like formating. You may have empty slots(a mtdblock2, but not a mtdblock0,1). The mtd drivers are stock kernel for flash and special memory devices. A google on "vfm" file type shows maybe it's a special flash block driver from intel. How about /dev/tffsa1, whats that thing?