maemo.org Bugzilla – Bug 2672
Sandisk 8GB microSD not detected
Last modified: 2008-12-06 16:09:21 UTC
You need to log in before you can comment on or make changes to this bug.
STEPS TO REPRODUCE THE PROBLEM: Insert one of these: http://www.sandisk.com/Products/Item(2537)-SDSDQR-8192-SanDisk_microSDHC_8_GB.aspx with a microSD-to-miniSD adapter into the N810's card slot. EXPECTED OUTCOME: Card gets recognised and mounted, dmesg should report something along these lines (seen when inserting a working 4GB card): [ 4555.070312] menelaus 1-0072: Setting voltage 'VMMC' to 3100 mV (reg 0x0a, val 0xf8) [ 4555.093750] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8) [ 4555.187500] mmcblk1: mmc0:3591 SD04G 3932160KiB [ 4555.187500] mmcblk1: p1 ACTUAL OUTCOME: Card is not recognised, kernel reports: [ 333.328125] menelaus 1-0072: Setting voltage 'VMMC' to 3100 mV (reg 0x0a, val 0xf8) [ 333.351562] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8) [ 335.710937] menelaus 1-0072: Shutting off 'VMMC' REPRODUCIBILITY: Always EXTRA SOFTWARE INSTALLED: Nothing kernel-related. OTHER COMMENTS: The N810 is running OS 2.2007.50-2. I also get the same results on two N800s, using either the internal or external slot. Kernel messages from OS 2007 (I would swear it's running 4.2007.38-2, but "About Product" now says 4.2007.26-8 and "uname -a": Linux Nokia-N800-26 2.6.18-omap1 #2 Fri Sep 21 16:27:36 EEST 2007 armv6l unknown): [ 277.903503] mmci-omap mmci-omap.1: cover is now closed [ 277.904754] menelaus: Setting 'VMMC' to 3100 mV (reg 0x0a, val 0xf8) [ 277.927795] menelaus: Setting 'VMMC' to 3000 mV (reg 0x0a, val 0xb8) [ 280.297637] menelaus: Shutting off 'VMMC' OS 2008 (2.2007-50-2, Linux Nokia-N800-50-2 2.6.21-omap1 #2 Fri Dec 7 11:17:13 EET 2007 armv6l unknown): [ 126.664062] menelaus 1-0072: Setting voltage 'VDCDC3' to 3300 mV (reg 0x07, val 0x39) [ 126.687500] menelaus 1-0072: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29) [ 129.046875] menelaus 1-0072: Shutting off 'VDCDC3' Not sure whether the issue is with the card, the tablets or both. The N800s have worked fine with all other cards I've tried (up to 16GB). I haven't even experienced the corruption issue that was fixed in 38-2. The card itself works fine on my laptop, connected either via the bundled USB reader or the laptop's built-in SD reader (using the same adapter plus an additional miniSD-to-SD one). When inserted in the latter, the kernel reports: [192019.589674] tifm_core: MMC/SD card detected in socket 0:3 [192019.657766] mmcblk0: mmc0:aaaa SU08G 7977472KiB [192019.657794] mmcblk0: p1 See also http://internettablettalk.com/forums/showthread.php?t=13531
I just flashed the kernel from http://intr.overt.org/4.2007.38-mmc-kernel/ on the OS2007 N800. No improvement, but more verbose logging. I don't know if it helps but here it is: [ 129.805328] bat_cover (GPIO 110) is now closed [ 129.805389] mmci-omap mmci-omap.1: cover is now closed [ 129.805450] mmc0: clock 0Hz busmode 1 powermode 1 cs 0 Vdd 21 width 0 timing 0 [ 129.806701] menelaus: Setting 'VMMC' to 3100 mV (reg 0x0a, val 0xf8) [ 129.822570] mmc0: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 21 width 0 timing 0 [ 129.824798] mmc0: clock 400000Hz busmode 1 powermode 2 cs 1 Vdd 21 width 0 timing 0 [ 129.827209] mmc0: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 21 width 0 timing 0 [ 129.829742] mmc0: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 18 width 0 timing 0 [ 129.832550] menelaus: Setting 'VMMC' to 3000 mV (reg 0x0a, val 0xb8) [ 129.844329] mmc0: clock 400000Hz busmode 1 powermode 2 cs 1 Vdd 18 width 0 timing 0 [ 129.846832] mmc0: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 18 width 0 timing 0 [ 132.198272] mmc0: clock 400000Hz busmode 2 powermode 2 cs 0 Vdd 18 width 0 timing 0 [ 132.199584] mmc0: clock 0Hz busmode 1 powermode 0 cs 0 Vdd 0 width 0 timing 0 [ 132.199615] menelaus: Shutting off 'VMMC'
There have been several reports on ITT Forum[1] of problems when using a SanDisk MicroSD to MiniSD adapter with the N810. There definately seems to be a SanDisk MicroSD to MiniSD adapter issue when using large (4GB+?) SDHC MicroSD cards in the N810 - other brands of adapter appear to work OK. 1. http://www.internettablettalk.com/forums/showthread.php?t=13531
Yeah, I did see that thread (and even referenced it in the description) but thanks for pointing it out because while re-reading it I suddenly remembered I have a 512MB microSD card & microSD-SD adapter lying around (came with the Neo, never had a use for them before) and did some more testing. It turns out that the 512MB card doesn't work in the N810 either using the same adapter as before. In fact it even throws CRC errors before menelaus gives up and switches it of (whereas the 8GB one was just failing silently): [37858.343750] menelaus 1-0072: Setting voltage 'VMMC' to 3100 mV (reg 0x0a, val 0xf8) [37858.367187] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8) [37858.406250] mmci-omap mmci-omap.1: command CRC error (CMD55, arg 0x00000000) [37858.406250] mmci-omap mmci-omap.1: command CRC error (CMD55, arg 0x00000000) [37858.429687] mmci-omap mmci-omap.1: command CRC error (CMD55, arg 0x00000000) [37858.429687] mmci-omap mmci-omap.1: command CRC error (CMD55, arg 0x00000000) [37858.429687] mmci-omap mmci-omap.1: command CRC error (CMD55, arg 0x00000000) [37858.429687] mmci-omap mmci-omap.1: command CRC error (CMD55, arg 0x00000000) [37858.437500] menelaus 1-0072: Shutting off 'VMMC' On the other hand, both cards work fine on both slots of both N800s when using the microSD-SD adapter. I even played some video off the 8GB one to make sure there are no read errors, no problems whatsoever. So it seems that card & tablets are ok, the issue is definitely caused by the adapter, and it affects non-HC cards too. Just to confuse things a bit, the working adapter is made by Sandisk, while the non-working one isn't (for what it's worth, it's one of these: <http://www.mobymemory.com/products/MobyMemory/microSD-to-miniSD-Adapter-(for-miniSD-devices).asp>). I will try to find and test some alternative adapters, but it's going to take several days due to the holidays. Will report back when I have more info.
Got a couple of these: <http://www.nextdaymemory.co.uk/device/microsd_to_minisd_adapter-157076.html>, and they seem to work fine so far. The card is recognised and mounted, no CRC or other errors during use. BTW, feel free to close this as invalid. It would be useful to document working/non-working adapters somewhere, but this is probably not the right place for it.
(In reply to comment #4) > Got a couple of these: > <http://www.nextdaymemory.co.uk/device/microsd_to_minisd_adapter-157076.html>, > and they seem to work fine so far. The card is recognised and mounted, no CRC > or other errors during use. > > BTW, feel free to close this as invalid. It would be useful to document > working/non-working adapters somewhere, but this is probably not the right > place for it. > I ordered, received and tested this adapter with my 8 GB SanDisk Card and find that it works with the N810. Thanks (In reply to comment #4) > Got a couple of these: > <http://www.nextdaymemory.co.uk/device/microsd_to_minisd_adapter-157076.html>, > and they seem to work fine so far. The card is recognised and mounted, no CRC > or other errors during use. > > BTW, feel free to close this as invalid. It would be useful to document > working/non-working adapters somewhere, but this is probably not the right > place for it. > (In reply to comment #4) > Got a couple of these: > <http://www.nextdaymemory.co.uk/device/microsd_to_minisd_adapter-157076.html>, > and they seem to work fine so far. The card is recognised and mounted, no CRC > or other errors during use. > > BTW, feel free to close this as invalid. It would be useful to document > working/non-working adapters somewhere, but this is probably not the right > place for it. >
The Sandisk 8GB microSD + Kingston microSD to miniSD adapter works fine in my N810 50-2: I put via rsync 4.5GB on it and read documents and videofrom it without issue.
*** This bug has been confirmed by popular vote. ***
(In reply to comment #0) > ACTUAL OUTCOME: > > Card is not recognised, kernel reports: > > [ 333.328125] menelaus 1-0072: Setting voltage 'VMMC' to 3100 mV (reg 0x0a, > val 0xf8) > [ 333.351562] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, > val 0xb8) > [ 335.710937] menelaus 1-0072: Shutting off 'VMMC' > I get the above messages in my dmesg when using my 8GB SanDisk microSD card and a no-name microSD-to-miniSD adapter, but only when I really jam the microSD card into the miniSD adapter. If I gently push the microSD card into the adapter and stop pushing the card when I feel the adapter grip the card, the card/adapter combo will mount sucessfully in my N810. When I slide the adapter into the N810, I prod it home until it clicks using only the stylus. I don't push on the card itself - I only push on the adapter to avoid forcing the card further into the adapter. It seems that pushing the card too hard and too far into the adapter somehow disrupts the electrical connection between the N810, adapter and card. It may not work for everyone, but it works for me. :)
This probably doesn't related to the bug, but... > I would swear it's running 4.2007.38-2, but > "About Product" now says 4.2007.26-8 This is a version corrupting cards. The bug is not really about SDHC cards, although it can happen easier with them due their normally larger power usage, more data being written to them and them possible being "more fragile". The issue has happened even with some 1GB cards. > The N800s have worked fine with all other cards I've tried (up to 16GB). > I haven't even experienced the corruption issue that was fixed in 38-2. It depends on your card power consumption (varies wildly between different card models) and how you use it (do you do writes to card when device would otherwise sleep, this could happen e.g. when using scp).
Fixed, you need to use a non-Sandisk Micro to Mini SD adapter.
Closing NOTABUG. This is a hardware problem. Everyone reporting such issues confirmed the microSD card working with a different adapter. Comments on this bug as well as various posts in forums identify this to be a hardware problem with the adapter. Thanks for the good comments and investigation, everyone!