Ubuntu mspblk device Automount Problem
yadav.rajesh at nts.ricoh.co.jp
yadav.rajesh at nts.ricoh.co.jp
Tue Apr 20 03:07:33 UTC 2010
Hi all,
I have been using Ubuntu 10.04 beta2.
As there is a subsystem (memstick) in the kernel to support the MemorySitck
media cards. The kernel is supposed to automount the devices falling under
the memstick or mspblk (The Block device name as as specified in the
memstick subsystem).
I am trying the Sony memory stick cards with Ricoh's Memosry Stick host
controller and Host driver. When I insert the card it appears in the /dev
directory as /dev/mspblk0 and /dev/mspblk0p1. And also an icon appear in
the Places->Computer as A New Hard Disk but it does not get auto mount.
However I can mount it by just clicking on the icon under the
Places-->Computer// Hard Disk.
What I want is to get the card automatically mounted same as the MMC/SD
cards do. And also the card should be recognised as the MemoryStick
removable media instead of a hard disk.
The following are the messages I got by running some commands:
Output of gvfs-mount -li
ricoh at ricoh-desktop:~$ gvfs-mount -li
Drive(0): 250 MB Hard Disk
Type: GProxyDrive (GProxyVolumeMonitorGdu)
ids:
unix-device: '/dev/mspblk0'
themed icons: [drive-harddisk] [drive]
is_media_removable=0
has_media=1
is_media_check_automatic=0
can_poll_for_media=0
can_eject=0
can_start=0
can_stop=0
start_stop_type=unknown
Volume(0): 249 MB Filesystem
Type: GProxyVolume (GProxyVolumeMonitorGdu)
ids:
unix-device: '/dev/mspblk0p1'
themed icons: [drive-harddisk] [drive]
can_mount=1
can_eject=0
should_automount=0
Drive(1): CD/DVD Drive
Type: GProxyDrive (GProxyVolumeMonitorGdu)
ids:
unix-device: '/dev/sr0'
themed icons: [drive-optical] [drive]
is_media_removable=1
has_media=0
is_media_check_automatic=1
can_poll_for_media=1
can_eject=0
can_start=0
can_stop=0
start_stop_type=unknown
ricoh at ricoh-desktop:~$
Output of gvfs-mount -li
ricoh at ricoh-desktop:~$ udevadm info --attribute-walk --name /dev/mspblk0
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/pci0000:00/0000:00:1c.0/0000:02:00.1
/memstick_host/memstick0/memstick0/block/mspblk0':
KERNEL=="mspblk0"
SUBSYSTEM=="block"
DRIVER==""
ATTR{range}=="8"
ATTR{ext_range}=="8"
ATTR{removable}=="0"
ATTR{ro}=="0"
ATTR{size}=="487936"
ATTR{alignment_offset}=="0"
ATTR{capability}=="10"
ATTR{stat}==" 79 195 645 140 0 0
0 0 0 108 136"
ATTR{inflight}==" 0 0"
looking at parent device '/devices/pci0000:00/0000:00:1c.0/0000:02:00.1
/memstick_host/memstick0/memstick0':
KERNELS=="memstick0"
SUBSYSTEMS=="memstick"
DRIVERS=="mspro_block"
ATTRS{type}=="01"
ATTRS{category}=="00"
ATTRS{class}=="00"
looking at parent device '/devices/pci0000:00/0000:00:1c.0/0000:02:00.1
/memstick_host/memstick0':
KERNELS=="memstick0"
SUBSYSTEMS=="memstick_host"
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:1c.0/0000:02:00.1':
KERNELS=="0000:02:00.1"
SUBSYSTEMS=="pci"
DRIVERS=="ricoh_ms"
ATTRS{vendor}=="0x1180"
ATTRS{device}=="0xe230"
ATTRS{subsystem_vendor}=="0x104d"
ATTRS{subsystem_device}=="0x905e"
ATTRS{class}=="0x088000"
ATTRS{irq}=="17"
ATTRS{local_cpus}=="ff"
ATTRS{local_cpulist}=="0-7"
ATTRS{modalias}=="pci:v00001180d0000E230sv0000104Dsd0000905Ebc08sc80i00"
ATTRS{broken_parity_status}=="0"
ATTRS{msi_bus}==""
looking at parent device '/devices/pci0000:00/0000:00:1c.0':
KERNELS=="0000:00:1c.0"
SUBSYSTEMS=="pci"
DRIVERS=="pcieport"
ATTRS{vendor}=="0x8086"
ATTRS{device}=="0x3a40"
ATTRS{subsystem_vendor}=="0x0000"
ATTRS{subsystem_device}=="0x0000"
ATTRS{class}=="0x060400"
ATTRS{irq}=="25"
ATTRS{local_cpus}=="ff"
ATTRS{local_cpulist}=="0-7"
ATTRS{modalias}=="pci:v00008086d00003A40sv00000000sd00000000bc06sc04i00"
ATTRS{broken_parity_status}=="0"
ATTRS{msi_bus}=="1"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
Any ideas on this will greatly help me.
Thanks in advance
Rajesh
More information about the Ubuntu-devel-discuss
mailing list