KDE Device notifier does not respond to sd card.

Brother77 · 09-02-2018, 11:21 AM

Dear people,
The device notifier of the KDE desktop finds al devices that i have used (cd, dvd, usb disk)
except the sd card.
The `fdisk -l` command does see the card and it is also no problem to mount it manually.

`sudo mount -t vfat /dev/mmcblk0p1 /home/neljor/Pictures`

Would like to see it appear automatically in the device notifier with a pop-up as the other devices do.

Any ideas?

OS Release: openSUSE Leap 15.0

Thanks in advantage!

Peter

ferrari · 09-02-2018, 11:05 PM

For udev/desktop "automatic" mounting to work, the device in question needs to be seen as removable.

Monitor the kernel and udev output when you first plug in the SD Card...

Code:

dmesg -w

Code:

udevadm monitor

Use the 'udevadm info' command to obtain the device attributes. For example (/dev/sdd)...

Code:

udevadm info -a -p /sys/block/sdd

Brother77 · 09-03-2018, 03:22 PM

Quote:

Originally Posted by ferrari

For udev/desktop "automatic" mounting to work, the device in question needs to be seen as removable.
Monitor the kernel and udev output when you first plug in the SD Card...

Code:

dmesg -w

Code:

udevadm monitor

Use the 'udevadm info' command to obtain the device attributes. For example (/dev/sdd)...

Code:

udevadm info -a -p /sys/block/sdd

Thank you Ferrari!

Output `dmesg -w`:
[16817.205922] mmc0: new high speed SDHC card at address 1234
[16817.206767] mmcblk0: mmc0:1234 SA16G 14.5 GiB
[16817.209601] mmcblk0: p1

Output `udevadm monitor`:
KERNEL[16817.086388] add /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.0/rtsx_usb_sdmmc.0.auto/mmc_host/mmc0/mmc0:1234 (mmc)
KERNEL[16817.087033] add /devices/virtual/bdi/179:0 (bdi)
KERNEL[16817.090137] add /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.0/rtsx_usb_sdmmc.0.auto/mmc_host/mmc0/mmc0:1234/block/mmcblk0 (block)
KERNEL[16817.090890] add /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.0/rtsx_usb_sdmmc.0.auto/mmc_host/mmc0/mmc0:1234/block/mmcblk0/mmcblk0p1 (block)
UDEV [16817.091412] add /devices/virtual/bdi/179:0 (bdi)
UDEV [16817.092950] add /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.0/rtsx_usb_sdmmc.0.auto/mmc_host/mmc0/mmc0:1234 (mmc)
UDEV [16817.184533] add /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.0/rtsx_usb_sdmmc.0.auto/mmc_host/mmc0/mmc0:1234/block/mmcblk0 (block)
UDEV [16817.279076] add /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.0/rtsx_usb_sdmmc.0.auto/mmc_host/mmc0/mmc0:1234/block/mmcblk0/mmcblk0p1 (block)

`udevadm info -a -p /sys/block/mmcblk0/` command gives long output of 172 lines, what are we looking for?

ferrari · 09-03-2018, 03:45 PM

Looking for the device attributes, is it classed as a removable device etc. Upload the complete output to https://pastebin.com/ and post the link to it here. Perhaps a custom udev rule is needed to get it handled appropriately.

Brother77 · 09-03-2018, 04:31 PM

Quote:

Originally Posted by ferrari

Looking for the device attributes, is it classed as a removable device etc. Upload the complete output to https://pastebin.com/ and post the link to it here. Perhaps a custom udev rule is needed to get it handled appropriately.

https://pastebin.com/3YuULhZE

ferrari · 09-03-2018, 06:19 PM

Returning to your opening post...

Quote:

The device notifier of the KDE desktop finds al devices that i have used (cd, dvd, usb disk)
except the sd card.

Just a thought - did you check the device notifier settings to make sure that new devices can be automatically mounted?

Assuming that's not the issue here, then read on...

There are rules in /usr/lib/udev/rules.d/80-udisks2.rules that are supposed to help identify such SD card devices (amongst others), and in particular I would have thought this rule would match against your particular device...

Code:

# TODO: figure out if the drive supports SD and SDHC and what the current
# kind of media is - right now we just assume SD
KERNEL=="mmcblk[0-9]", SUBSYSTEMS=="mmc", ENV{DEVTYPE}=="disk", ENV{ID_DRIVE_FLASH_SD}="1", ENV{ID_DRIVE_MEDIA_FLASH_SD}="1"

In any case, the device attribute output you shared means that other suitable custom rule matching is possible. For example...

Code:

SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bda",  ATTRS{idProduct}=="0129", ENV{ID_DRIVE_FLASH_SD}="1"

You could try creating a custom rule with the above rule eg /etc/udev/rules.d/40-SD_reader.rules. It should take effect following a reboot.

See how that goes.

Brother77 · 09-04-2018, 01:13 PM

Quote:

Originally Posted by ferrari

Returning to your opening post...

Just a thought - did you check the device notifier settings to make sure that new devices can be automatically mounted?

Assuming that's not the issue here, then read on...

There are rules in /usr/lib/udev/rules.d/80-udisks2.rules that are supposed to help identify such SD card devices (amongst others), and in particular I would have thought this rule would match against your particular device...

Code:

# TODO: figure out if the drive supports SD and SDHC and what the current
# kind of media is - right now we just assume SD
KERNEL=="mmcblk[0-9]", SUBSYSTEMS=="mmc", ENV{DEVTYPE}=="disk", ENV{ID_DRIVE_FLASH_SD}="1", ENV{ID_DRIVE_MEDIA_FLASH_SD}="1"

In any case, the device attribute output you shared means that other suitable custom rule matching is possible. For example...

Code:

SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bda",  ATTRS{idProduct}=="0129", ENV{ID_DRIVE_FLASH_SD}="1"

You could try creating a custom rule with the above rule eg /etc/udev/rules.d/40-SD_reader.rules. It should take effect following a reboot.

See how that goes.

Yes, devices can be automatically mounted in the device notifier.
It reads SDHC also dmesg says so, have no other information.

`hwinfo --mmc`
23: MMC 00.0: 11700 MMC Controller
[Created at pci.1828]
Unique ID: 4KNU._NN+DZ1HDn4
SysFS ID: /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.0/rtsx_usb_sdmmc.0.auto/mmc_host/mmc0/mmc0:1234
SysFS BusID: mmc0:1234
Model: "SD Controller 0"
Vendor: int 0x6015
Device: int 0x0001 "SD Controller 0"
Driver: "mmcblk"
Config Status: cfg=new, avail=yes, need=no, active=unknow

Machine is rebooted with

Code:

SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bda",  ATTRS{idProduct}=="0129", ENV{ID_DRIVE_FLASH_SD}="1"

in
/etc/udev/rules.d/40-SD_reader.rules

Result: has no effect on device notifier when sd card is inserted.

ferrari · 09-04-2018, 02:12 PM

One question - did you remove (or at least comment out) the fstab entry for this device before testing with the notifier? Udisks2 will ignore the device in question if the entry exists. Please disregard if you have no such entry added.

ferrari · 09-04-2018, 02:19 PM

I'd also be interested in seeing what udisksctl makes of it....

Code:

udisksctl monitor

Brother77 · 09-04-2018, 02:27 PM

Quote:

Originally Posted by ferrari

I'd also be interested in seeing what udisksctl makes of it....

Code:

udisksctl monitor

% udisksctl monitor
Monitoring the udisks daemon. Press Ctrl+C to exit.
12:25:14.753: The udisks-daemon is running (name-owner :1.25).
12:25:24.619: Added /org/freedesktop/UDisks2/drives/SA16G_0x424a54e6
org.freedesktop.UDisks2.Drive:
CanPowerOff: true
Configuration: {}
ConnectionBus: usb
Ejectable: false
Id: SA16G-0x424a54e6
Media: flash_sd
MediaAvailable: true
MediaChangeDetected: true
MediaCompatibility: flash_sd
MediaRemovable: true
Model: SA16G
Optical: false
OpticalBlank: false
OpticalNumAudioTracks: 0
OpticalNumDataTracks: 0
OpticalNumSessions: 0
OpticalNumTracks: 0
Removable: true
Revision:
RotationRate: 0
Seat: seat0
Serial: 0x424a54e6
SiblingId: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.0
Size: 15548284928
SortKey: 01hotplug/1536089124612875
TimeDetected: 1536089124612875
TimeMediaDetected: 1536089124612875
Vendor:
WWN:
12:25:24.622: Added /org/freedesktop/UDisks2/block_devices/mmcblk0
org.freedesktop.UDisks2.Block:
Configuration: []
CryptoBackingDevice: '/'
Device: /dev/mmcblk0
DeviceNumber: 45824
Drive: '/org/freedesktop/UDisks2/drives/SA16G_0x424a54e6'
HintAuto: true
HintIconName:
HintIgnore: false
HintName:
HintPartitionable: true
HintSymbolicIconName:
HintSystem: false
Id:
IdLabel:
IdType:
IdUUID:
IdUsage:
IdVersion:
MDRaid: '/'
MDRaidMember: '/'
PreferredDevice: /dev/mmcblk0
ReadOnly: false
Size: 15548284928
Symlinks: /dev/disk/by-id/mmc-SA16G_0x424a54e6
/dev/disk/by-path/pci-0000:00:14.0-usb-0:6:1.0-platform-rtsx_usb_sdmmc.0.auto
org.freedesktop.UDisks2.PartitionTable:
Type: dos
12:25:24.703: Added /org/freedesktop/UDisks2/block_devices/mmcblk0p1
org.freedesktop.UDisks2.Block:
Configuration: []
CryptoBackingDevice: '/'
Device: /dev/mmcblk0p1
DeviceNumber: 45825
Drive: '/org/freedesktop/UDisks2/drives/SA16G_0x424a54e6'
HintAuto: true
HintIconName:
HintIgnore: false
HintName:
HintPartitionable: true
HintSymbolicIconName:
HintSystem: false
Id:
IdLabel:
IdType:
IdUUID:
IdUsage:
IdVersion:
MDRaid: '/'
MDRaidMember: '/'
PreferredDevice: /dev/mmcblk0p1
ReadOnly: false
Size: 15544090624
Symlinks: /dev/disk/by-id/mmc-SA16G_0x424a54e6-part1
/dev/disk/by-path/pci-0000:00:14.0-usb-0:6:1.0-platform-rtsx_usb_sdmmc.0.auto-part1
org.freedesktop.UDisks2.Partition:
Flags: 0
IsContained: false
IsContainer: false
Name:
Number: 1
Offset: 4194304
Size: 15544090624
Table: '/org/freedesktop/UDisks2/block_devices/mmcblk0'
Type: 0x0c
UUID:

ferrari · 09-04-2018, 03:08 PM

Okay, that looks as expected for a removable device. Time to submit a bug report I think....

https://en.opensuse.org/openSUSE:Submitting_bug_reports

Brother77 · 09-04-2018, 04:14 PM

Quote:

Originally Posted by ferrari

Okay, that looks as expected for a removable device. Time to submit a bug report I think....

https://en.opensuse.org/openSUSE:Submitting_bug_reports

Okay, thanks for your help.