microSD slot fried?

Daniel Benoy daniel at benoy.name
Fri Sep 5 19:43:05 CEST 2008


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

On Friday 05 September 2008 12:48:11 Dmitry Makovey wrote:
> 
> --- Andy Green <andy at openmoko.com> wrote:
> 
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > Somebody in the thread at some point said:
> > | --- "Neng-Yu Tu (Tony Tu)" <tony at openmoko.com>
> > wrote:
> > |> These is marker from factory SMT line for
> > |> distinguish 900/1800/1900 and
> > |> 850/1800/1900 phones, not fired :)
> > |
> > | thanks! that's a definite releif. However question
> > | remains - why wouldn't my FreeRunner see microSD?
> > I'll
> > | try to locate some "other" microSD card to
> > testhoping
> > | it's not controller or something.
> > 
> > You need to do
> > 
> > dmesg
> > 
> > and post it here, it will try to talk to your card
> > during boot and
> > should give a clue where it went wrong, if it could
> > even talk to it at
> > all, etc.
> 
> 
> this is what I was looking for:
> 
> # 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
> ...
> 
> 
> # fdisk /dev/mmcblk0
> fdisk: cannot read from /dev/mmcblk0
> 
> (same for all 0, 1 and 2 devices)
> 
> but in case I was looking for the wrong stuff, here's
> the whole dmesg in attachment.
> 
> 



-- 
Daniel Benoy
http://daniel.benoy.name



More information about the support mailing list