microSD slot fried?

Dmitry Makovey dmakovey at yahoo.com
Sat Sep 6 00:38:21 CEST 2008


--- Daniel Benoy <daniel at benoy.name> wrote:

> Looks like trouble.  Have you ruled out the card
> itself by checking it in another reader?


just did with another FreeRunner: co-worker has
NorthAmerican version and it did't have problem with
my card (except that the card doesn't have partition
information):

# dmesg | grep  mmc
VFS: Can't find a valid FAT filesystem on dev mmcblk0.
VFS: Can't find a valid FAT filesystem on dev mmcblk0.


We tried both cards (his and mine) in both devices and
both cards seem to behave the same in each device
respectively - in mine they throw errors, in his -
missing partition information (his was functional
before though, so I'm thinking my device corrupted the
card). Another difference is that my stack is OM2008.8
and his is QTopia. But my FreeRunner was unable to
work with microSD regardless of image/software stack
used.

Interestingly enough it does detect the card itself
and it's size, but then soon after it "blows up".

> On Friday 05 September 2008 12:48:11 Dmitry Makovey
> > # grep mmc om_dmesg
> > [    3.165000] mmcblk0: mmc0:b368 SMI   498176KiB
> > [    3.170000]  mmcblk0:<6>glamo-mci glamo-mci.0:
> > Error after cmd: 0x302
> > [    3.180000] mmcblk0: error -84 sending
> read/write
> > command
> > [    3.185000] end_request: I/O error, dev
> mmcblk0,
> > sector 0
> > [    3.185000] Buffer I/O error on device mmcblk0,
> > logical block 0
> > [    3.195000] glamo-mci glamo-mci.0: Error after
> cmd:
> > 0x8020
> > [    3.195000] glamo-mci glamo-mci.0: Error after
> cmd:
> > 0x8122
> > [    3.200000] mmcblk0: error -84 sending
> read/write
> > command
> > ...




More information about the support mailing list