[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: sd card not detected

On 11/02/2013 01:51 PM, Linux-Fan wrote:
On 11/01/2013 07:35 PM, Alex Mestiashvili wrote:
Hi All,

A card inserted into card reader is not mounted automatically and even
doesn't shown up in the dmesg output, but if I switch off and on the
monitor with cardreader or run lshw the card appears and is mounted.

the same happens with the second card reader in the pc. ( one is in
monitor, second in the computer itself)

other usb devices work fine.

The hci/usb modules:

lsmod | egrep "hci|usb_storage"
usb_storage            39406  0
ehci_pci               12432  0
ohci_hcd               22150  0
ehci_hcd               35820  1 ehci_pci
scsi_mod              131001  5 sg,usb_storage,libata,sd_mod,sr_mod
usbcore               110348  8

The system is jessie, kernel: 3.10-3-686-pae

Something must be missing, but I really wonder what, as far as I
understand hardware detection is kind of kernel feature..

Thank you,
I have the same problem here -- since the upgrade from Squeeze to Wheezy
when the HAL was removed, device nodes for CF and SD cards are not
automatically created after insertion. Reconnecting the cardreader helps
here as well, but I did not want to always reconnect the cardreader and
found the following workaround:


This C program allows you to "reset" a specific USB device which will
behave similar to reconnecting the cardreader in this case. Ater
inserting a SD-card, just use $ ./usbreset /dev/sde (if the card is
normally /dev/sde1) to make the device nodes available.

If you find a better solution, I would also be interested in hearing of
it. Also, the problem does not seem to be specific to a desktop
environment or even Kernel version: I am running "Linux 3.2.0-4-amd64"
and no desktop environment and get exactly the same behavior.


Hi Linux-Fan,

I didn't have much time to investigate the problem further but the problem is solved by udisks-daemon, udisks package. for some reason It doesn't run on boot in my case, but running udisks --enumerate or something similar triggers the daemon's start and it starts to poll the devices.


Reply to: