You are not logged in.
Update: This is solved enough for my needs, by buying a new memory card. The 4GB card is still unrecognized (if I can get it to show up as /dev/sdX, it has an I/O error when I try to dd anything to it) and even Windows sees it as a 35MB card. It works perfectly in my camera though. I'm going to write this one off as a card issue and not worry too much about it.
The integrated Ricoh multi-card reader in my Thinkpad W510 isn't working correctly, and I can't quite figure out why. Of the three SD cards I have, it reads a generic 2GB card fine and creates /dev/mmcblk0 as expected. However, it fails to create a device for both an SDHC card and another (known working) 512MB SD card.
I've tried removing one of the PCI devices -- it appears twice, you'll see that in a moment -- with the appropriate /sys/bus/pci/devices/.../remove, but I really have no idea what I'm doing with that. I've also tried unloading/reloading the appropriate kernel modules and issuing a PCI rescan to no avail.
lspci -nn |grep -i sd
0d:00.0 SD Host controller [0805]: Ricoh Co Ltd MMC/SD Host Controller [1180:e822] (rev 01)
17:00.0 SD Host controller [0805]: Ricoh Co Ltd MMC/SD Host Controller [1180:e822] (rev 01)When I insert either of the non-working cards, dmesg gives the following four lines:
[248378.394200] sdhci-pci 0000:0d:00.0: Will use DMA mode even though HW doesn't fully claim to support it.
[248378.453697] sdhci-pci 0000:0d:00.0: Will use DMA mode even though HW doesn't fully claim to support it.
[248378.517332] sdhci-pci 0000:0d:00.0: Will use DMA mode even though HW doesn't fully claim to support it.
[248378.580809] sdhci-pci 0000:0d:00.0: Will use DMA mode even though HW doesn't fully claim to support it.And for the working card, all is normal.
[247445.279520] mmc0: new high speed SD card at address d992
[247445.291966] mmcblk0: mmc0:d992 SD02G 1.83 GiB
[247445.292849] mmcblk0: p1Sadly, it's been months since I last tried to use an SD card (all of which used to work fine) so I have no idea what upgrade would have caused it, and any other related topics I can find are from before this device had official support in the kernel. Any ideas or other info I can provide?
Thanks.
Last edited by JeSuisNerd (2015-11-04 02:51:24)
Offline
This seems to a similar issue https://bbs.archlinux.org/viewtopic.php?id=204712
Offline