[arch-general] portable player, usb plugging/mounting problems

[Guilherme M. Nogueira]

Hello dear Arch users,

I have a Sansa e200 portable media player and I'm having problems mounting
it. It used to work, but I can't recall when (I have been listening to the
same stuff for over 4 months now).
I'm using arch i686 with core, extra, community, kdemod-core and
kdemod-extragear  and updated system.

The player has two modes, MSC and MTP. I always use it in Mass Storage Class
mode.

Thing is, when I plug the device with HAL running I get the following:

$ dmesg:
usb 1-6: new high speed USB device using ehci_hcd and address 13
usb 1-6: configuration #128 chosen from 1 choice
scsi24 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 13
usb-storage: waiting for device to settle before scanning
usb 1-6: reset high speed USB device using ehci_hcd and address 13
scsi25 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 13
usb-storage: waiting for device to settle before scanning

If I stop HAL deamon, I get this:

$ dmesg
usb 1-6: new high speed USB device using ehci_hcd and address 4
usb 1-6: configuration #128 chosen from 1 choice
scsi14 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
scsi 14:0:0:0: Direct-Access     SanDisk  Sansa e270            PQ: 0 ANSI:
0
sd 14:0:0:0: [sdb] 11780096 512-byte hardware sectors: (6.03 GB/5.61 GiB)
sd 14:0:0:0: [sdb] Write Protect is off
sd 14:0:0:0: [sdb] Mode Sense: 45 00 00 00
sd 14:0:0:0: [sdb] Assuming drive cache: write through
sd 14:0:0:0: [sdb] 11780096 512-byte hardware sectors: (6.03 GB/5.61 GiB)
sd 14:0:0:0: [sdb] Write Protect is off
sd 14:0:0:0: [sdb] Mode Sense: 45 00 00 00
sd 14:0:0:0: [sdb] Assuming drive cache: write through
 sdb: sdb1 sdb2
sd 14:0:0:0: [sdb] Attached SCSI removable disk
sd 14:0:0:0: Attached scsi generic sg2 type 0
scsi 14:0:0:1: Direct-Access     SanDisk  Sansa e270            PQ: 0 ANSI:
0
sd 14:0:0:1: [sdc] 246016 512-byte hardware sectors: (125 MB/120 MiB)
sd 14:0:0:1: [sdc] Write Protect is off
sd 14:0:0:1: [sdc] Mode Sense: 45 00 00 00
sd 14:0:0:1: [sdc] Assuming drive cache: write through
sd 14:0:0:1: [sdc] 246016 512-byte hardware sectors: (125 MB/120 MiB)
sd 14:0:0:1: [sdc] Write Protect is off
sd 14:0:0:1: [sdc] Mode Sense: 45 00 00 00
sd 14:0:0:1: [sdc] Assuming drive cache: write through
 sdc: sdc1
sd 14:0:0:1: [sdc] Attached SCSI removable disk
sd 14:0:0:1: Attached scsi generic sg3 type 0
usb-storage: device scan complete

The output of lsusb is:
$ lsusb
Bus 001 Device 013: ID 0781:7421 SanDisk Corp. Sansa E200 series


I don't really understand why is this, since I read that HAL just gets
notified of the new device and provides the interface for other apps, but
the kernel and udev are the ones that really do the recognizing and
mounting.

Since in my mind udev is the one that does the job, I tried following a tip
I read in the mainling list archive and created a new udev rule in
/etc/udev/rules.d/sansa.rules with:
UBSYSTEMS=="usb", KERNEL=="sd*",
ATTRS{idProduct}=="7421",ATTRS{idVendor}=="0781", SYMLINK+="sansa",
GROUP="storage"

I ask for you help to understand what is going on here.

Thank you very much,

Guilherme.

-- 
Malformed message exception