Ubuntu

SanDisk SDMX1 MP3 Player no longer automounts with Gutsy Kubuntu

Asked by Gerard

Previously with Feisty this device would appear on the desktop and I would be prompted to open in new window etc, now - after installing Gutsy (after a failed Feisty upgrade) this does not happen.

I can mount it manually, but who wants to do that :)

Here is a dmesg:

[ 1414.896000] usb 2-2: new high speed USB device using ehci_hcd and address 9
[ 1415.028000] usb 2-2: configuration #1 chosen from 1 choice
[ 1415.028000] scsi9 : SCSI emulation for USB Mass Storage devices
[ 1415.028000] usb-storage: device found at 9
[ 1415.028000] usb-storage: waiting for device to settle before scanning
[ 1420.028000] usb-storage: device scan complete
[ 1420.028000] scsi 9:0:0:0: Direct-Access SanDisk SDMX1 MP3 Player 0100 PQ: 0 ANSI: 4
[ 1420.028000] sd 9:0:0:0: [sdh] 2032896 512-byte hardware sectors (1041 MB)
[ 1420.032000] sd 9:0:0:0: [sdh] Write Protect is off
[ 1420.032000] sd 9:0:0:0: [sdh] Mode Sense: 38 00 00 00
[ 1420.032000] sd 9:0:0:0: [sdh] Assuming drive cache: write through
[ 1420.036000] sd 9:0:0:0: [sdh] 2032896 512-byte hardware sectors (1041 MB)
[ 1420.036000] sd 9:0:0:0: [sdh] Write Protect is off
[ 1420.036000] sd 9:0:0:0: [sdh] Mode Sense: 38 00 00 00
[ 1420.036000] sd 9:0:0:0: [sdh] Assuming drive cache: write through
[ 1420.036000] sdh: sdh1
[ 1420.040000] sd 9:0:0:0: [sdh] Attached SCSI removable disk
[ 1420.040000] sd 9:0:0:0: Attached scsi generic sg7 type 0

I would like to have the "normal" functionality back.

Cheers

Gerard

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Gerard
Solved:
Last query:
Last reply:
Revision history for this message
Gerard (gbendotti) said : 		#1

Additional: (too much Red Dwarf) this is the same on two other machines here 1 is a laptop fresh install. the other was a successful Feisty => Gusty upgrade.

Revision history for this message
Gerard (gbendotti) said : 		#2

https://bugs.launchpad.net/ubuntu/+source/hal/+bug/146812
Quote:

For what it's worth:
I got this error on gutsy beta today, just after having modified /etc/init.d/rc with
CONCURRENCY=shell
instead of the previous
CONCURRENCY=none
(I wanted some more speed from my dual core :-)

I took the change back and the
"Internal Error" "failed to initialize HAL!"
disappeared.