Fuze Won't Connect In Linux

I’m running a fully updated Kubuntu 9.04 install, and absolutely nothing happens when I plug it in under MSC mode. MTP mode is not an option for me because I use the Fuze as a USB drive frequently. lsusb doesn’t show it, and the player goes through it’s usual connecting ritual, except it doesn’t charge (no lightning bolt or blinky battery, out of power if left connected overnight (oops)).

I didn’t check dmesg, but I probably should. I’ll post it if it shows anything (I booted in to windows so I can load some fresh music on it…).

I’m pretty Linux-savvy, but this baffles me.

This is strange. I haven’t used the Fuze with Kubuntu 9.04 but I can operate the player in MSC mode with similar Linux systems:

  • Ubuntu 9.04 Desktop

  • Ubuntu 9.04 Netbook Remix

  • Xubuntu 9.04 Desktop

  • Debian 5.0 Lenny

There is a known problem that the player will be handled as USB1.1 device instead of USB2.0 on certain hardware. But still it connects.

Maybe you could try a Live-CD containing one of these? Could you try unplugging the player/cable multiple times just to make sure there is no connector/cable problem?

Those are all the same OS with a different UI (as in same kernel, same modules, same userland. Just GNOME gets swapped for KDE gets swapped for XFCE ad nasuem). Except Debian, it has it’s own kernel image. Which is where Ubuntu gets it’s kernel from.

A kernel update for K/X/Ubuntu got released just now, I installed it and rebooted, and it appears to work perfectly fine now. from dmesg:

[67240.629109] hub 1-0:1.0: unable to enumerate USB device on port 3 [67241.008048] usb 3-1: new full speed USB device using uhci\_hcd and address 3 [67241.152211] usb 3-1: not running at top speed; connect to a high speed hub [67241.185772] usb 3-1: configuration #1 chosen from 1 choice [67241.322367] Initializing USB Mass Storage driver... [67241.353268] scsi2 : SCSI emulation for USB Mass Storage devices [67241.354282] usbcore: registered new interface driver usb-storage [67241.354285] USB Mass Storage support registered. [67241.354448] usb-storage: device found at 3 [67241.354450] usb-storage: waiting for device to settle before scanning

Nothing is mentioned in the kernel changelog about the USB stack, so who knows. Must be a ghost in the system :stuck_out_tongue:

So I guess the solution to the problem is to be up-to-date as of 06-19-2009.

Looks like it was too good to be true. It mounts and then the kernel thinks it’s dead, and it gets unmounted:

[67238.324061] usb 1-3: new high speed USB device using ehci\_hcd and address 5 [67240.425895] ehci\_hcd 0000:00:1d.7: port 3 reset error -110 [67240.425929] hub 1-0:1.0: hub\_port\_status failed (err = -32) [67240.629109] hub 1-0:1.0: unable to enumerate USB device on port 3 [67241.008048] usb 3-1: new full speed USB device using uhci\_hcd and address 3 [67241.152211] usb 3-1: not running at top speed; connect to a high speed hub [67241.185772] usb 3-1: configuration #1 chosen from 1 choice [67241.322367] Initializing USB Mass Storage driver... [67241.353268] scsi2 : SCSI emulation for USB Mass Storage devices [67241.354282] usbcore: registered new interface driver usb-storage [67241.354285] USB Mass Storage support registered. [67241.354448] usb-storage: device found at 3 [67241.354450] usb-storage: waiting for device to settle before scanning [67246.354262] usb-storage: device scan complete [67246.357448] scsi 2:0:0:0: Direct-Access SanDisk Sansa Fuze 4GB v01. PQ: 0 ANSI: 0 [67246.369261] scsi 2:0:0:1: Direct-Access SanDisk Sansa Fuze 4GB v01. PQ: 0 ANSI: 0 [67246.400255] sd 2:0:0:0: [sdb] 7964672 512-byte hardware sectors: (4.07 GB/3.79 GiB) [67246.414251] sd 2:0:0:0: [sdb] Write Protect is off [67246.414258] sd 2:0:0:0: [sdb] Mode Sense: 04 00 00 00 [67246.414263] sd 2:0:0:0: [sdb] Assuming drive cache: write through [67246.424232] sd 2:0:0:0: [sdb] 7964672 512-byte hardware sectors: (4.07 GB/3.79 GiB) [67246.436616] sd 2:0:0:0: [sdb] Write Protect is off [67246.436623] sd 2:0:0:0: [sdb] Mode Sense: 04 00 00 00 [67246.436627] sd 2:0:0:0: [sdb] Assuming drive cache: write through [67246.436643] sdb: [67246.451818] sd 2:0:0:0: [sdb] Attached SCSI removable disk [67246.451939] sd 2:0:0:0: Attached scsi generic sg1 type 0 [67246.472325] sd 2:0:0:1: [sdc] 3932160 512-byte hardware sectors: (2.01 GB/1.87 GiB) [67246.480324] sd 2:0:0:1: [sdc] Write Protect is off [67246.480331] sd 2:0:0:1: [sdc] Mode Sense: 04 00 00 00 [67246.480335] sd 2:0:0:1: [sdc] Assuming drive cache: write through [67246.492234] sd 2:0:0:1: [sdc] 3932160 512-byte hardware sectors: (2.01 GB/1.87 GiB) [67246.495220] sd 2:0:0:1: [sdc] Write Protect is off [67246.495225] sd 2:0:0:1: [sdc] Mode Sense: 04 00 00 00 [67246.495229] sd 2:0:0:1: [sdc] Assuming drive cache: write through [67246.495237] sdc: sdc1 [67246.528279] sd 2:0:0:1: [sdc] Attached SCSI removable disk [67246.528351] sd 2:0:0:1: Attached scsi generic sg2 type 0 [67322.233126] usb 3-1: USB disconnect, address 3 [67322.242568] Buffer I/O error on device sdc1, logical block 7690 [67322.242574] lost page write due to I/O error on sdc1 [67322.242586] Buffer I/O error on device sdc1, logical block 845031 [67322.242589] lost page write due to I/O error on sdc1 [67322.242595] Buffer I/O error on device sdc1, logical block 1750568 [67322.242599] lost page write due to I/O error on sdc1 [67322.242605] Buffer I/O error on device sdc1, logical block 3677708 [67322.242608] lost page write due to I/O error on sdc1 [67322.242656] Buffer I/O error on device sdc1, logical block 3677709 [67322.242660] lost page write due to I/O error on sdc1 [67322.242664] Buffer I/O error on device sdc1, logical block 3677710 [67322.242668] lost page write due to I/O error on sdc1 [67322.277918] scsi 2:0:0:0: rejecting I/O to dead device [67322.380668] scsi 2:0:0:1: rejecting I/O to dead device

 Could this be a hardware issue with my player itself or it’s cable?

@mngrif wrote:

Could this be a hardware issue with my player itself or it’s cable?

 

This is what I suspect in first place. See my last post. If you have one of the (KX)Ubuntu Live-CDs at hand you might try on different computers too. Go and visit your friends … Watch the lsusb and dmesg output. You should really use the Live-CDs and not any installed system to get comparable results.

A few questions: Are you connecting the Fuze to USB ports at front/back side of your computer or via hub? I’m a bit confused to see two devices sdb (4GB) and sdc (2GB) showing up in your log at about the same time. Are you using an external mircoSD card? And from the log again there is no partition table found. Looks strange to me. How did you format the Fuze?

Maybe it is a good idea to start reformatting your Fuze and (re)applying the last firmware. Good luck!

I reformatted it right before installing .26A using the builtin device format (I thought it was odd it didn’t have a partition table too, but that’s how it formats itself). I do have a 2GB SD card and for now that has been sufficient for me to change out music on (I keep full albums on the internal flash). I’m plugging it in to any and all ports, and they all have the same results. I found a hub but I can’t find it’s power supply so there’s no sense in trying it just in case the problem is my USB ports not being able to supply enough power. I can’t even replicate that latest dmesg now, even from a cold boot.

I’m gonna hunt up the power supply for the hub and reformat the device again. If there’s still no go, I’ll request a replacement since I haven’t had this for more than a few months (although there’s enough scratches to make it look years old!). I absolutely love my Fuze :slight_smile:

I have found out the problem!

While jiggering with it on my netbook running Ubuntu 9.04 with it sitting on my lap, it started working. After testing some transfers, it stopped moving right when I moved. Ah-hah! A faulty cable! After a little testing I narrowed it down to the actual USB connection plug on the cable, and that it wasn’t just the one port (I’ve tested over 10 ports in total…).

I have confirmed that it is not the player or Linux causing the issue, it connects at USB1.1 on all my machines, and that’s fine. It’s most definitely the cable.

So, can someone link me to the process to get a replacement cable? It’s 5 months old.

The 30-pin Sansa cable is available from Griffin and Maximo, with both cables having excellent warranties.  Cables are also available via eBay and Amazon (just be sure that you are ordering a Sansa cable and not an iPod cable).  Prices vary from a few dollars to about $20.  The higher priced ones listed above have the advantage of future warranty support from their respective manufacturers.

The 30 pin Sansa cable is universal for all Sansas with the flat connector.  If you find a cable described as for the Connect, e200, or View for example, it will work fine with the Fuze.

I haven’t checked on the Support side, if replacement cables are available under the limited warranty, but you can contact them directly at 1-866-SanDisk.

µsansa