Unable to access/(auto)-mount SD card on Fedora 28
6
votes
4
answers
6912
views
I am trying to access SD cards on Fedora 28, but do not have any success. System info is as follows:
$ lsb_release -a
LSB Version: :core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch
Distributor ID: Fedora
Description: Fedora release 28 (Twenty Eight)
Release: 28
Codename: TwentyEight
I was not able to access different SD cards using two different card readers. Despite of being accessible on both macOS and Windows, none of them is shown in the Nautilus file browser, the desktop or elsewhere obvious.
The card readers are recognized by the system as per
lsusb
output:
$ lsusb -v
# some other USB devices
Bus 001 Device 005: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x058f Alcor Micro Corp.
idProduct 0x6362 Flash Card Reader/Writer
bcdDevice 1.29
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 250mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
# some other USB devices
Bus 001 Device 006: ID 0dda:2027 Integrated Circuit Solution, Inc. USB 2.0 Card Reader
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0dda Integrated Circuit Solution, Inc.
idProduct 0x2027 USB 2.0 Card Reader
bcdDevice 1.6e
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 5
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
# some other USB devices
I then had a look at the udev events while plugging a card in and out:
$ udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[701.434565] change /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host4/target4:0:0/4:0:0:2/block/sde (block)
UDEV [714.263816] change /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host4/target4:0:0/4:0:0:2/block/sde (block)
KERNEL[748.477184] change /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host4/target4:0:0/4:0:0:2/block/sde (block)
UDEV [761.338940] change /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host4/target4:0:0/4:0:0:2/block/sde (block)
In addition, I had a look at the kernel messages:
$ dmesg
[ 603.846840] usb-storage 1-3:1.0: USB Mass Storage device detected
[ 603.847749] scsi host4: usb-storage 1-3:1.0
[ 605.703531] scsi 4:0:0:0: Direct-Access Generic CF 1.6E PQ: 0 ANSI: 0 CCS
[ 605.704982] scsi 4:0:0:1: Direct-Access Generic MS 1.6E PQ: 0 ANSI: 0 CCS
[ 606.509034] scsi 4:0:0:2: Direct-Access Generic MMC/SD 1.6E PQ: 0 ANSI: 0 CCS
[ 606.510387] scsi 4:0:0:3: Direct-Access Generic SM 1.6E PQ: 0 ANSI: 0 CCS
[ 606.511519] sd 4:0:0:0: Attached scsi generic sg4 type 0
[ 606.511943] sd 4:0:0:1: Attached scsi generic sg5 type 0
[ 606.512177] sd 4:0:0:2: Attached scsi generic sg6 type 0
[ 606.512408] sd 4:0:0:3: Attached scsi generic sg7 type 0
[ 608.924586] sd 4:0:0:1: [sdd] Attached SCSI removable disk
[ 629.830776] sd 4:0:0:2: [sde] Attached SCSI removable disk
[ 633.048754] sd 4:0:0:3: [sdf] Attached SCSI removable disk
[ 639.490479] sd 4:0:0:0: [sdc] Attached SCSI removable disk
Both the output of dmesg
and udevadm monitor
are telling that the card should be shown as sde
. However, fdisk -l
does not list sde
. Besides that, trying to mount the device manually, raises an error:
$ mount -t auto /dev/sde /mnt/
mount: /mnt: no medium found on /dev/sde.
I am not sure, whether the needed driver module is loaded properly, since there is no mmc0
-like entry in the dmesg
output (as I am used to know from Debian-based systems). lsmod
does not list the mmc0
kernel module either:
$ lsmod | grep mm
rtl8192c_common 61440 1 rtl8192cu
rtlwifi 98304 3 rtl8192c_common,rtl_usb,rtl8192cu
The only mmc
-like modules which seems to be available but are not loaded are mmc_block
and mmc_core
:
$ modprobe mm # listing suggestions using tab auto-completion
mma7660 mmc_block mmc_core mms114
How could I solve this problem or at least narrow it down?
Asked by albert
(191 rep)
Jul 16, 2018, 07:57 PM
Last activity: Aug 3, 2025, 09:48 AM
Last activity: Aug 3, 2025, 09:48 AM