Since I got my P1 a week ago, I had had trouble to get the SD card mounted. I tried with the following builds:
OpenMoko-openmoko-devel-image-glibc-ipk-P1-September-Snapshot-20070916-fic-gta01.rootfs.jffs2 uImage-2.6.22.5-moko11+svnr2937-r0-fic-gta01.bin and uImage-2.6.22.5-moko11+svnr2937-r3-neo1973.bin scaredycat-openmoko-devel-image-fic-gta01.jffs2 also with my own builds and couple older ones. All kernel boots were fine but none of them gave me the device /dev/mmcblk0p1, thus I never got the SD card mounted. The dmesg shows there are I/O errors: [EMAIL PROTECTED]:~$ dmesg | grep mmc <7>mmc_set_power(power_mode=0, vdd=0 ... <7>mmc_set_power(power_mode=2, vdd=20 <6>mmcblk0: mmc0:e624 SU512 495488KiB <6> mmcblk0:<3>mmcblk0: error 1 transferring data <4>end_request: I/O error, dev mmcblk0, sector 0 <3>Buffer I/O error on device mmcblk0, logical block 0 <3>mmcblk0: error 1 transferring data <4>end_request: I/O error, dev mmcblk0, sector 0 ... [EMAIL PROTECTED]:~$ I tried to force a mount, [EMAIL PROTECTED]:~$ mount /dev/mmcblk0 /media/card /dev/mmcblk0: Input/output error mount: /dev/mmcblk0: can't read superblock [EMAIL PROTECTED]:~$ I tried both MMC cards coming with my advance set as well as one of my own. Two cards I formated on my linux box with no problem to read and write otherwise. One (original) card I didn't do any format with it. But nothing mattered whence they were put on my P1 unit. I used both VFAT and ext2 formats. I tried to looked into the card from the console: GTA01Bv4 # mmcinit trying to detect SD Card... Manufacturer: 0x03, OEM "SD" Product name: "SU512", revision 8.0 Serial number: 281088817 Manufacturing date: 8/2007 CRC: 0x21, b0 = 1 READ_BL_LEN=15, C_SIZE_MULT=7, C_SIZE=3453 size = 2329935872 mmc_block_read: err SDIDSTA=0x00000024 GTA01Bv4 # GTA01Bv4 # ext2ls mmc 0 mmc_block_read: err SDIDSTA=0x00000024 bad MBR sector signature 0xfd33 ** Bad partition - mmc 0:1 ** GTA01Bv4 # So it looks like there is block read error. I don't think my cards are bad, so I kind of suspect that I may have a bad disk controller. Any idea on this? Who should I talk to at FIC about the possible hw defect? Thanks! Tom
