Bug 24053

Summary: MMC cards aren't automounted.
Product: udisks Reporter: maximlevitsky
Component: detectionAssignee: David Zeuthen (not reading bugmail) <zeuthen>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: git formatted patch

Description maximlevitsky 2009-09-20 16:57:42 UTC
The core of this problem lies in:

 /lib/udev/rules.d/95-devkit-disks.rules:

ENV{DKD_PRESENTATION_NOPOLICY}="1"
KERNEL=="sd*|hd*|sr*", ENV{DKD_PRESENTATION_NOPOLICY}="0"

Thus, DKD_PRESENTATION_NOPOLICY is set on anything but hard disks and cdroms (and this includes usb drives)

However MMC/SD devices are reported as mmcblk*. There are also so called memstick devices, that are reported as mspblk*


So lets change those lines to:


ENV{DKD_PRESENTATION_NOPOLICY}="1"
KERNEL=="sd*|hd*|sr*|mmcblk*|mspblk*", ENV{DKD_PRESENTATION_NOPOLICY}="0"


Also there might be other devices, like floppy and maybe more.

The above change works for me
Comment 1 Martin Pitt 2009-10-09 05:56:31 UTC
Indeed, this makes sense. For the record, this is a complete dk-disks --dump which shows the problem:

http://launchpadlibrarian.net/33354340/devkit_dump.txt
Comment 2 Martin Pitt 2009-10-09 06:00:09 UTC
Created attachment 30217 [details] [review]
git formatted patch

Trivial patch, but with nice changelog, and with Maxim set as author. For David's convenience of just doing git am. :-)
Comment 3 David Zeuthen (not reading bugmail) 2009-10-09 06:52:18 UTC
(In reply to comment #2)
> Created an attachment (id=30217) [details]
> git formatted patch
> 
> Trivial patch, but with nice changelog, and with Maxim set as author. For
> David's convenience of just doing git am. :-)

Looks good. I've committed this with a different Subject line and added your name to the Signed-off-by line too. Thanks.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.