on first site i would assume the mmc has a corrupt fat on it or it is formatted as a superfloppy
what does a mount on /dev/mmc say ? Quoting Rein Velt <[EMAIL PROTECTED]>: > Dear people, > > I have a fox lx816 and a GM add-on card with a MMC device. The MMC > device has some problems. When i mount it manually i can read and > write to the mmc device, but when i mount it during startup > (in /etc/init/boottime/mountmmc.sh and /etc/fstab) the device is > only readable but not writable. > > It worked before (with exactly the procedure as i use now). Hope you > have an idea to solve this problem.. > > > my mount command is: > $ mount /t vfat -o sync /dev/mmc0 /root > > here are some results from the dmesg command > -------------------------------------------- > mmc : MMC Driver for FoxBoard Version 2.5 (280106) -- Made by K. > John '2B|!2B' Crispin ([EMAIL PROTECTED]) > mmc_drv.ko : response : 1 > mmc : Card Found > mmc : card in op mode > mmc : SIZE : 201, nMUL : 7, COUNT : 3876, NAME : SD02G > mmc : Card Initialised > mmc : The inserted card has a capacity of 1016070144 Bytes > mmc : adding disk > mmc: mmc1 > mmc : Card was Found > cse0: Probing a 0x04000000 bytes large window at 0xe0000000. > cse0: Probing for AMD compatible flash... > cse0: unknown flash device at 0x0, mfr id 0x20, dev id 0x22ca > cse0: Found no AMD compatible device at location zero > cse0: Found 1 x16 devices at 0x0 in 16-bit bank > cse0: Found an alias at 0x400000 for the chip at 0x0 > cse0: Found an alias at 0x800000 for the chip at 0x0 > cse0: Found an alias at 0xc00000 for the chip at 0x0 > cse0: Found an alias at 0x1000000 for the chip at 0x0 > cse0: Found an alias at 0x1400000 for the chip at 0x0 > cse0: Found an alias at 0x1800000 for the chip at 0x0 > cse0: Found an alias at 0x1c00000 for the chip at 0x0 > cse0: Found an alias at 0x2000000 for the chip at 0x0 > cse0: Found an alias at 0x2400000 for the chip at 0x0 > cse0: Found an alias at 0x2800000 for the chip at 0x0 > cse0: Found an alias at 0x2c00000 for the chip at 0x0 > cse0: Found an alias at 0x3000000 for the chip at 0x0 > cse0: Found an alias at 0x3400000 for the chip at 0x0 > cse0: Found an alias at 0x3800000 for the chip at 0x0 > cse0: Found an alias at 0x3c00000 for the chip at 0x0 > Amd/Fujitsu Extended Query Table at 0x0040 > cse0: Swapping erase regions for broken CFI table. > number of CFI chips: 1 > cfi_cmdset_0002: Disabling erase-suspend-program due to code > brokenness. > cse1: Probing a 0x04000000 bytes large window at 0xe4000000. > cse1: Probing for AMD compatible flash... > cse1: unknown flash device at 0x0, mfr id 0x90, dev id 0x2c4 > cse1: Found no AMD compatible device at location zero > CFI: Found no cse1 device at location zero > cse0: 0x00400000 bytes of flash memory. > Found a valid partition table at 0xf001000a-0xf0010056. > /dev/flash1 at 0x00010000, size 0x00350000 > /dev/flash2 at 0x00360000, size 0x004a0000 > Adding readonly flash partition for romfs image: > /dev/flash3 at 0x000e3f5a, size 0x00250000 > Creating 4 MTD partitions on "cse0": > 0x00000000-0x00010000 : "part0" > 0x00010000-0x00360000 : "part1" > 0x00360000-0x00800000 : "part2" > mtd: partition "part2" extends beyond the end of device "cse0" -- > size truncated to 0xa0000 > 0x000e3f5a-0x00333f5a : "romfs" > ..... > > ..... > FAT: Filesystem panic (dev mmc1) > fat_free_clusters: deleting FAT entry beyond EOF > File system has been set read-only > --------------------------------------------- > > > >
