sansa mp3 players not mounted when plugged in

[Mark]

Ubuntu 8.04 does not mount 2 of our sansa mp3 players when they are plugged in. After plugging them in, absolutely nothing happens. Before, when i ran Fedora 8, they were both detected and auto mounted. I'm pretty sure something should happen when pluggin in a usb device like this.

Interestingly enough, if i drop to command line and enter "lsusb", the device will mount and Rythembox will open. The device is then mounted in /media.

Why is it not being auto mounted? Seems like a bug to me.

[sam tygier (samtygier)]

can you attach the output of lsusb, and dmesg.

[Mark (nix4me)]

I rebooted machine with Sansa M350 installed. It was mounted after the reboot was complete. I "ejected" it from desktop icon using right click. I unplugged and waited 2 minutes. I plugged it back in and waited 2 minutes. Then I collected dmesg and lsusb data as follows:

nix4me@desktop:~$ lsusb
Bus 008 Device 001: ID 0000:0000
Bus 007 Device 001: ID 0000:0000
Bus 006 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000

Dmesg is attached.

Once again, after the lsusb command, the player was mounted and rythembox appeared.

[sam tygier (samtygier)]

thanks. i'm setting back to new, as i'm not sure what to ask for next.
out of interest, are you plugging the player straight into the computer, or via a hub?

[Mark (nix4me)]

Straight into computer. For what it's worth, all 3 of my family's Sansa mp3 players do the same thing. They are all different models also.

[steve burdine (highfructose327)]

I have a similar issue with my Sansa fuze on Ubuntu 8.04 it does not mount automatically. I can either unplug it and plug it back in quickly and it will mount ,or run modprobe -r ehci_hcd and then modprobe ehci_hcd and it will mount the Sansa . If I only run modprobe -r ehci_hcd in Ubuntu 8.04 the Sansa will be automatically mounted upon plugging it in, but; of course the transfer speeds are slow by removing ehci_hcd. This is the only player that I tried that gives me this problem in 8.04, it will recognize a Cowon iaudio and a ipod no problem. I tried mounting the Sansa using Ubuntu 7.10 it mounted no problem.

 I have attached the output of dmesg and below is the output of lsub with ehci_hcd loaded in 8.04 kernel
 Linux-2.6.24-19-generic

$ lsusb
Bus 005 Device 004: ID 0644:0200 TEAC Corp.
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 007: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard
Bus 001 Device 006: ID 046d:c50e Logitech, Inc. MX-1000 Cordless Mouse Receiver
Bus 001 Device 001: ID 0000:0000
 The lsusb command does not mount my Sansa Fuze.

[gdselzer (geoff-selzers)]

I have virtually the exact same experience as highfructose327.

$ lsusb
Bus 005 Device 006: ID 0bda:0158 Realtek Semiconductor Corp. Mass Stroage Device
Bus 005 Device 005: ID 0781:7423 SanDisk Corp.
Bus 002 Device 007: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 002 Device 006: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

[steve burdine (highfructose327)]

gdselzer wrote:
> I have virtually the exact same experience as highfructose327.
>
> $ lsusb
> Bus 005 Device 006: ID 0bda:0158 Realtek Semiconductor Corp. Mass Stroage Device
> Bus 005 Device 005: ID 0781:7423 SanDisk Corp.
> Bus 002 Device 007: ID 413c:2003 Dell Computer Corp. Keyboard
> Bus 002 Device 006: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse
> Bus 002 Device 001: ID 0000:0000
> Bus 001 Device 001: ID 0000:0000
>
>
gdselzer, I finally gave up trying to get Ubuntu 8.04 to recognize my
Sansa Fuze. I did a fresh install of 8.10 while it was a beta and it
has never had issues seeing my Fuze. If you have a View I followed the
first two steps of the guide below for my wifes View. I do not know if
it works in 8.04 just 8.10.

http://ubuntuforums.org/showthread.php?t=650447

[gdselzer (geoff-selzers)]

highfructose327, I appreciate the response. I have a Sansa e260 and I would like to stick with Hardy because it has LTS. Given the LTS status, it would be nice if this bug were fixed.

[Hardy (gerhard-gerhard-vogt)]

I have a sansa e260 and I am running Ubuntu 8.10.
The sansa must be switch to USB mode MSC.

After connecting the sansa 2 USB devices appear in nautilus but nothing more.

So we have to make the system that it is mounting the device correctly.

Make a new directory:

<code>sudo mkdir /media/sansa</code>

Check which devices are used by the sansa with:

<code>sudo fdisk -l</code>

Now we have to edit the file /etc/fstab
<code>sudo gedit /etc/fstab&amp;</code>

And put the following line at the end of the file, assuming that the first drive of the sansa was found at /dev/sdf1 with the fdisk -l command:

<code>/dev/sdf1 /media/sansa vfat rw,user,noauto,exec 0 0</code>

After editing the file /etc/fstab you have to reboot because this is a static table.

You can also try it by hand with
<code>sudo mount -t vfat /dev/sdf1 /media/sansa</code>

If you want to mount it as normal user use the tool pmount. Normally this is not installed on the machines.
<code>pmount -t vfat /dev/sdf1 /media/sansa</code>

Normally that's it, now the sansa icon should appear on the desktop after connecting the device.
Don't forget to unmount the device before disconnecting.

Unfortunately I experienced some problems that it looked that the sansa was just mounted as read-only.
The reason for that was that some files were corrupted. So I connected the sansa to a Windows system and issued the command:

<code>chkdsk /F e:</code>

Now it worked fine on Ubuntu as well.

[Guido Scholz (gscholz)]

Hi all,
most probably this link will help:

http://forums.sandisk.com/sansa/board/message?board.id=sansafuse&thread.id=12910&page=4

Guido

[steve burdine (highfructose327)]

Guido that looks great!

I quoted what you did in the Ubuntu forums http://ubuntuforums.org/showthread.php?p=6521461#post6521461 and added your link.

Thanks

[Rob Hasselbaum (rhasselbaum)]

I am having the same problem with my Sansa e260, which was working just fine as a USB storage device under Ubuntu 8.10, but since switching to Kubuntu 9.04 and KDE 4.2, it won't mount consistently. (It worked once a few days ago, but not since.)

If I tail /var/log/messages when I plug it in, I can see it getting detected:

...kernel: [ 519.384118] usb 1-4: new high speed USB device using ehci_hcd and address 7
...kernel: [ 519.520350] usb 1-4: configuration #128 chosen from 1 choice
...kernel: [ 519.552853] scsi11 : SCSI emulation for USB Mass Storage devices
...kernel: [ 529.928151] usb 1-4: reset high speed USB device using ehci_hcd and address 7
...kernel: [ 530.076366] scsi12 : SCSI emulation for USB Mass Storage devices

One strange thing here is the "reset" that happens ten seconds later. I don't know what that's all about.

I can also see it in lsusb:

...
Bus 001 Device 007: ID 0781:7421 SanDisk Corp. Sansa E200 series
...

But it doesn't show up in the KDE device notifier at all.

[steve burdine (highfructose327)]

Rob_H,
in 9.04 with Gnome my Sansa FUZE shows up in either mode MSC or MTP, if left the Sansa was left on auto it choose MTP over MSC. With my FUZE in MSC mode I ran df in a terminal it showed up mounted in /media

/dev/sdh 7993408 2739072 5254336 35% /media/FUZE

you might try df and see where your e260 is mounted in MSC mode. Also when I had my FUZE mounted in MTP mode df returned nothing but lsusb showed it connected and it was visible in Nautilus. Good luck

[Rob Hasselbaum (rhasselbaum)]

It does not work in either mode for me.

[Dan Lenski (lenski)]

This bug should be merged with 355998 (https://bugs.launchpad.net/ubuntu/+source/libgphoto2/+bug/355998)

Long story short: the gphoto2 library handles MP3 players in MTP mode. Due to a bug in gphoto2 *and* a problem with its HAL configuration files, it tries to take over the Sansa MP3 player when it is plugged in to the computer. Thus no /dev/sdXX nodes get created.

gphoto2 has been patched upstream, and there are temporary fixes by modifying the gphoto2/HAL configuration files. See the bug I linked to.