Sandisk Sansa e250 won't connect

[Mike Hurst]

My Sansdisk Sansa e250 won't connect while using Ubuntu 9.04 Alpha 6 updated 3/19/09. I does work with Debian.
lsusb says:
Bus 001 Device 015: ID 0781:7421 SanDisk Corp. Sansa E200 series
dmesg:
[22242.788126] usb 1-3: new high speed USB device using ehci_hcd and address 15
[22244.583922] usb 1-3: configuration #128 chosen from 1 choice
[22244.603240] scsi13 : SCSI emulation for USB Mass Storage devices
[22244.604337] usb-storage: device found at 15
[22244.604340] usb-storage: waiting for device to settle before scanning
[22252.108064] usb 5-1: new low speed USB device using uhci_hcd and address 4
[22252.286718] usb 5-1: configuration #1 chosen from 1 choice

[spiral (perfectdrug)]

I have the same problem with my sansa e280 v1.
Hardy works as expected.
The sansa toggles from "connected" to "disconnected".
Sansa is in MSC-mode.
MTP-mode is working.

output of dmesg while in MSC after connecting my sansa:

[ 275.282665] usb 1-7.2: USB disconnect, address 3
[ 294.584094] usb 1-7: reset high speed USB device using ehci_hcd and address 2
[ 294.996436] usb 1-7.2: new high speed USB device using ehci_hcd and address 4
[ 296.164417] usb 1-7.2: configuration #128 chosen from 1 choice
[ 296.209103] scsi3 : SCSI emulation for USB Mass Storage devices
[ 296.209610] usb-storage: device found at 4
[ 296.209615] usb-storage: waiting for device to settle before scanning

output of lsusb:

Bus 001 Device 004: ID 0781:7421 SanDisk Corp. Sansa E200 series
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

kernel version: 2.6.28-11-generic

output of fdisk -l:

/dev/sda1 * 1 3259 26177886 7 HPFS/NTFS
/dev/sda3 3260 19457 130110435 5 Erweiterte
/dev/sda5 18795 19457 5325516 82 Linux Swap / Solaris
/dev/sda6 3260 18794 124784824+ 83 Linux

[grasshopper (blackwolf-franken-online)]

My SanDisk Sansa e260 v1 has still the same issue with the newest release of Ubuntu 9.04 beta.

It can't connect in msc-mode.

uname -r
2.6.28-11-generic

output of lsusb:
Bus 001 Device 011: ID 0781:7421 SanDisk Corp. Sansa E200 series

dmesg tells:
[ 3022.916049] usb 1-3: new high speed USB device using ehci_hcd and address 11
[ 3023.073245] usb 1-3: configuration #128 chosen from 1 choice
[ 3023.112018] scsi10 : SCSI emulation for USB Mass Storage devices
[ 3023.116424] usb-storage: device found at 11
[ 3023.116427] usb-storage: waiting for device to settle before scanning

[nloewen (nloewen)]

me too. everything is the same.

[nloewen (nloewen)]

If I put in MTP mode, A noteifcation pops up saying "Unable to mount SanDisk Corp. Sansa E200 series (mtp): Error initializing camera: -1: Unspecified error"

MSC mode
lsusb
Bus 001 Device 010: ID 0781:7421 SanDisk Corp. Sansa E200 series

gmesg
[32596.304433] usb 1-4: new high speed USB device using ehci_hcd and address 10
[32597.462876] usb 1-4: configuration #128 chosen from 1 choice
[32597.584236] scsi5 : SCSI emulation for USB Mass Storage devices
[32597.594223] usb-storage: device found at 10
[32597.594229] usb-storage: waiting for device to settle before scanning

MTP mode
lsusb:
Bus 001 Device 009: ID 0781:7420 SanDisk Corp. Sansa E200 series (mtp)

gmesg
[32173.740268] usb 1-3: new high speed USB device using ehci_hcd and address 9
[32174.673594] usb 1-3: config 128 interface 0 altsetting 0 endpoint 0x81 has an invalid bInterval 100, changing to 10
[32174.708434] usb 1-3: configuration #128 chosen from 1 choice

[nloewen (nloewen)]

I just realized it will connect in mtp mode. (Intrepid didn't recognize it at all in mtp)

[Benjamin_L (benjamin-lebsanft)]

Indeed, it mounts when using mtp, even without my actual problem with the cardreader. Either way, something is wrong here and should be fixed. I'll provide any information necessary, just tell me what you need.

MSC mode mounts two devices (SD Player, this is because I had to unbrick mine, and Sandisk Corp. Sansa E200 series) when the card in my cardreader is present.

As rockbox uses MSC too I guess it's the same probleme there.

[Mário Buči (mario-buci)]

First, sorry for messing with status.

Anyway, i found a solution somewhere on anythingbutipod forum:

"Trying backing up /usr/share/hal/fdi/preprobe/10osvendor/20-libgphoto2.fdi and removing any references to your Sansa player. If that does not work, then move the file out of the 10osvendor directory and try plugging in the Sansa again."

I moved the file and now i see my sansa in nautilus :).. Oh, and i'm using latest rockbox so i can see my 8GB microSDHC card, too.

[nloewen (nloewen)]

that didn't work for me. anyone have any other suggestions?

[Benjamin_L (benjamin-lebsanft)]

nloewen: Did you move out the file? Afterwards my sansa connected without problems, but I think we need a more sophisticated fix for this.

[nloewen (nloewen)]

I did. Was I supposed to reboot or anything after? I put the file back because it wasn't working.

[Benjamin_L (benjamin-lebsanft)]

It worked instantly afterwards here.

[Daniel Holbert (dholbert)]

> It worked instantly afterwards here.

It worked for me as well. I didn't need to move the file -- I just edited it and removed the block of 132 lines relating to SanDisk products (all nodes of the form "<match key="usb.vendor_id" int="1921">...</match>), and then I reconnected my player (an e280 running Rockbox), and it worked.

[Reptile (achapman)]

removing the file worked for me too. very strange!

[dhed317 (zjhodson)]

Mário Buči's solution worked for but I learned nothing. If it would not be too much trouble could someone shoot me an e-mail to educate me as to why? I apologise if this is not an appropriate post.

Zach
<email address hidden>

[dhed317 (zjhodson)]

*update*

Worked for a while and then just stopped. Now I know even less than I did before.

Okay I tried restoring 20-libgphoto2.fdi to its original condition and removing all of the blocks that I could figure would apply to my e200.....no good

Then I tried to remove all lines that apply to portable audio players.....no good

Then I deleted the entire file....still nothing

I cannot fathom what dark sorcery would cause it to work briefly then un-mount and vanish again. A tricky one that jackalope is.

[Reptile (achapman)]

The trick also stopped working for me!

My Sony Ericsson W890i phone won't mount either!

I really hope they get this sorted soon, it's very annoying.

[bongtothesoo (bongsoojchoi)]

this is strange because i can connect my sansa e250 in virtualbox (xp guest, jaunty home)
hope this gets addressed soon. i dont want to run virtualbox every time i update my library...

[Ori Folger (calanya+launchpad)]

My Sansa e280 stopped working as well. Please set this as an important bug.

[HankB (hbarta)]

I renamed the .fdi file (tacked on ".dontuse") and have mounted my e280/Rockbox twice. :D

I hope it continues to work. This is following a fresh install of Jaunty (not beta, not RC)

thanks,
hank

[taka k. (scar)]

thanks. Mário Buči's solution worked for my e280 player. i removed two blocks of <match> (below) and my player is mounting now instantly, without reboot.

   <match key="usb.vendor_id" int="1921">
    <match key="usb.product_id" int="29728">
     <merge key="info.category" type="string">portable_audio_player</merge>
     <append key="info.capabilities" type="strlist">portable_audio_player</append>
     <merge key="portable_audio_player.access_method" type="string">user</merge>
     <merge key="portable_audio_player.type" type="string">mtp</merge>
     <append key="portable_audio_player.output_formats" type="strlist">audio/mpeg</append>
     <merge key="camera.libgphoto2.name" type="string">SanDisk Sansa e200/e250/e260/e270/e280</merge>
     <merge key="camera.libgphoto2.support" type="bool">true</merge>
    </match>
   </match>
   <match key="usb.vendor_id" int="1921">
    <match key="usb.product_id" int="29729">
     <merge key="info.category" type="string">portable_audio_player</merge>
     <append key="info.capabilities" type="strlist">portable_audio_player</append>
     <merge key="portable_audio_player.access_method" type="string">user</merge>
     <merge key="portable_audio_player.type" type="string">mtp</merge>
     <append key="portable_audio_player.output_formats" type="strlist">audio/mpeg</append>
     <merge key="camera.libgphoto2.name" type="string">SanDisk Sansa e280</merge>
     <merge key="camera.libgphoto2.support" type="bool">true</merge>
    </match>
   </match>

[fruchtschwert (fruchtschwert)]

Some guy at the forums at anythingbutipod.com said, that this problem has already been fixed in the SVN version of libgphoto.. see here

http://www.anythingbutipod.com/forum/showpost.php?p=349742&postcount=4

and here

http://gphoto.svn.sourceforge.net/viewvc/gphoto/branches/libgphoto2-2_4/libgphoto2/libgphoto2_port/usb/libusb.c?r1=12026&r2=12025&pathrev=12026

So probably it should come to ubuntu sooner or later :)

[jac0b (jacbrooks)]

Thank Mário Buči for the help it fixed my problem with my Gigabeat S series player on jaunty.

[bkristan (bkristan)]

Another data point to add - my e280 with Rockbox 3.2 doesn't connect, but with the same cable on the same machine my son's Fuze 4 GB does. Both are set to msc mode. The computer is a 64 bit, just updated to Jaunty. Both players connect fine to my laptop running Hardy. Not sure if this is helpful or redundant, but I'll be happy to give more details if it would be useful (lsusb or dmesg on either player, etc.).

[bkristan (bkristan)]

I figured it out! It's the file:

/usr/share/hal/fdi/information/10freedesktop/10-usb-music-players.fdi

The vendor id for SanDisk players is missing a leading zero. Line 445 of the file reads:

 <match key="@storage.originating_device:usb.vendor_id" int="0x781">

when it should read:

 <match key="@storage.originating_device:usb.vendor_id" int="0x0781">

Now my e280 is mounting as expected. Spread the word, there are lots of duplicate bugs I'll bet are being caused by this!

[Richard Mayhew (richard-bouncingfox)]

fix worked for me, changed and and mounted instantly 4 times in a row.

good find

[grasshopper (blackwolf-franken-online)]

The fix didn't worked for me with a Sansa e260 v1.

[bkristan (bkristan)]

Sorry it didn't work for you grasshopper... the strange thing is, my e280 never stopped working on my laptop running Hardy, yet the vendor ID in the 10-usb-music-players.fdi file is listed as 0x781. Very strange. Not sure why it would matter in Jaunty but not Hardy.

[bkristan (bkristan)]

Sorry, I was so excited about getting to contribute a fix instead of a problem I jumped to conclusions - for some reason the edit to 10-usb-music-players.fdi stopped working. Now I'm really confused.

[Tim (coacharnold)]

I'm having the same issue ..... did both file fixes ...... I'm working with the usr/share/hal/fdi/information/10freedesktop/10-usb-music-players.fdi fix for the moment ......

T

[Nicolas Ioannou (kyuubi1988)]

Hey guys, I had the same problem with my sansa e280.
I tried the 10-usb-music-players.fdi fix, but didnt'd work at all for me.

I have some insights though, that may be useful.
I have windows 7 beta on my Vbox machine, and there my e280 connects just fine
(assuming I have usb devices enabled)
Once I eject the device from Win7 and disable the usb devices from the Virtual Machine
( while it is still running)
the mp3 is mounted in ubuntu 9.04!! ( forgot to mention that it is in msc mode )

This is really strange...

Hope that helped!!

Nick

[HankB (hbarta)]

Add me to the group for whom the fixes are not permanent. This is on an Eee PC 901 running 9.04 lpia. It initially did not mount (as with every other 9.04 install I have performed) I fixed this by eliminating the Sansa entries in the gphoto fdi file. Last night it stopped working. I tried applying other fixes identified here (renaming the gphoto fdi file and making the device ID 4 digits in the 10-usb-music-players.fdi file.) Neither fix worked. Symptoms look the same with "waiting for device to settle" as the last line from dmesg.

I booted the "regular" install. (lpia runs from an SD card) This is 9.04 UNR for which I had renamed the gphpoto fdi file. It still mounts my Sansa. Following confirmation of that, I rebooted lpia and it still will not mount my Sansa.

Another data point, if it matters.

If there is an upstream fix, is there anyway to give it a go on a normal 9.04 install?

[holotone (holotone)]

Confirmed on multiple Jaunty installs on many different hardware configurations; Renaming /usr/share/hal/fdi/preprobe/10osvendor/20-libgphoto2.fdi has worked perfectly for me in every instance.

[HankB (hbarta)]

There is another bug filed for this problem: https://bugs.launchpad.net/ubuntu/+source/libgphoto2/+bug/355998 That bug report also includes a patch and directions to apply. I have done so and can confirm that it works for the lpia architecture.

[Kevin Moulton (kevinmoulton)]

This worked! Just backed up then deleted /usr/share/hal/fdi/preprobe/10osvendor/20-libgphoto2. Now I can mount my Sansa Clip in MSC mode, as I was able to do in earlier Ubuntu versions. You guys are the best. Thanks.

[Reuben Firmin (reubenf)]

To make this stranger still, my device (a 250) _does_ show up in KDE, although copying to it is horrendously slow. On Gnome, no dice.

[Reuben Firmin (reubenf)]

Interestingly, when I have connected using MSC, and then log out of Gnome, the device instantly connects. So something within Gnome is causing this.