Hi, I observed an interesting phenomenon with my newly bought Intenso 4GB SDHC card.
While the 512MB card shipped with my Freerunner runs reliably and stable the new card shows the following behaviour: 1) Errors during boot process: ============================ [EMAIL PROTECTED]:~# dmesg |grep -E "glamo|mmc" glamo3362 glamo3362.0: Detected Glamo core 3650 Revision 0002 (49119232Hz CPU / 81887232Hz Memory) glamo3362 glamo3362.0: Glamo core now 49119232Hz CPU / 81887232Hz Memory) glamo-spi-gpio glamo-spi-gpio.0: registering c0373838: jbt6k74 glamo-mci glamo-mci.0: glamo_mci driver (C)2007 Openmoko, Inc glamo-mci glamo-mci.0: probe: mapped mci_base:c8864400 irq:0. glamo-mci glamo-mci.0: glamo_mci_set_ios: power down. glamo-mci glamo-mci.0: initialisation done. mmc_set_power(power_mode=1, vdd=20 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 0kHz div=255 (req: 0kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: Error after cmd: 0x120 glamo-mci glamo-mci.0: Error after cmd: 0x8120 glamo-mci glamo-mci.0: Error after cmd: 0x120 glamo-mci glamo-mci.0: Error after cmd: 0x8120 glamo-mci glamo-mci.0: Error after cmd: 0x120 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 16666kHz div=2 (req: 16666kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 16666kHz div=2 (req: 16666kHz). Bus width=2 mmc0: new high speed SDHC card at address b368 mmcblk0: mmc0:b368 SD 3931136KiB mmcblk0:<6>glamo-mci glamo-mci.0: Error after cmd: 0x8310 mmcblk0: error -110 sending read/write command end_request: I/O error, dev mmcblk0, sector 0 Buffer I/O error on device mmcblk0, logical block 0 glamo-mci glamo-mci.0: Error after cmd: 0x120 glamo-mci glamo-mci.0: Error after cmd: 0x122 mmcblk0: error -84 sending read/write command ============================ [many more of the last few lines following] 2) I can trick it to work doing the following steps: - check sd_drive parameter (not required) >[EMAIL PROTECTED]:~# cat /sys/module/glamo_mci/parameters/sd_drive >0 - re-set it to this (or possibly any other) value >[EMAIL PROTECTED]:~# echo 0 > /sys/module/glamo_mci/parameters/sd_drive - now the device works fine: >[EMAIL PROTECTED]:~# fdisk -l /dev/mmcblk0 Disk /dev/mmcblk0: 4025 MB, 4025483264 bytes 126 heads, 61 sectors/track, 1022 cylinders Units = cylinders of 7686 * 512 = 3935232 bytes Device Boot Start End Blocks Id System /dev/mmcblk0p1 1 1022 3927515+ 83 Linux ========================== A suspend/resume cycle seems to do the trick as well. I think that some parameter connected to sd_drive might be uninitialised before sd_drive is explicitly rewritten. Any ideas? Cheers, David _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community