Compaq Presario M2000 Card Reader doesn't work after hibernate
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
linux-source-2.6.17 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
I'm running Kubuntu Dapper.
After booting, if I put an SD card into the flash slot on the laptop, the media is detected (the light near it flashes) and I'm asked by the KDE Media popup if I want to mount it. If I do mount it, I can read it fine.
After hibernating and powering back on, inserting media into the slot no longer works - the light does not flash, dmesg reveals no messages in response to the flash card being inserted, and the popup does not appear.
I've found that I can correct the problem by doing the follow after I return from a hibernate:
sudo rmmod sdhci
sudo rmmod mmc_core
sudo modprobe sdhci
After reloading those modules, plugging in the flash card again results in the popup prompting for a mount and the mount works and I can read photos again.
To recreate:
1. Boot up the laptop
2. Hibernate
3. Power on and wait for the laptop to return from hibernate
4. Plug in the flash memory to the memory slot
Result:
Nothing happens - the flash card does not appear to be detected.
Expected Result:
KDE Popup asking me if I want to open the card in a new window.
To fix:
After the laptop returns from hibernate, run the following:
sudo rmmod sdhci
sudo rmmod mmc_core
sudo modprobe sdhci
I think the following information from lspci relates to the controller for this card reader:
0000:06:09.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller
0000:06:09.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller
0000:06:09.4 0805: Texas Instruments PCI6411, PCI6421, PCI6611, PCI6621, PCI7411, PCI7
421, PCI7611, PCI7621 Secure Digital (SD) Controller
uname -a gives me:
Linux serenity 2.6.15-26-686 #1 SMP PREEMPT Mon Jul 17 20:14:14 UTC 2006 i686 GNU/Linux
(but I have seen this problem with previous releases of the kernel)
Setting package to linux-source- 2.6.15, so this bug gets out of the list of bugs without a package.
Can you confirm this bug still happens in edgy/feisty?
Thanks.