Announcement

**SteveTaylor** · Nov 09, 2009, 06:40 PM

Re: Continuing problem with Sansa Clip

I have installed Kubuntu 9.10 from scratch on another computer and the system recognizes the Sansa Clip just fine. The problem seems to be related to the Dell inspiron 1521 specifically. I also noticed that when I have the Sansa Clip plugged into the Dell, the Sansa says it is connected but it is not charging. With 9.04 and the newer kernel, it wouldn't be recognized but at least it charged when plugged in. A USB memory stick operates fine under all the systems.

**Snowhog** · Nov 09, 2009, 06:49 PM

Re: Continuing problem with Sansa Clip

Check to see if you have the following installed:

mtpfs mtp-tools

**SteveTaylor** · Nov 10, 2009, 11:28 AM

Re: Continuing problem with Sansa Clip

Those two items were not installed. I installed them and then plugged in the Clip and it was not recognized and was not charging. Then, leaving the Clip plugged in, I rebooted the computer. As it was booting, I noticed that the Clip was charging. After it booted up, the Clip was recognized and I could access it in Dolphin. I did a "Safely Remove" and unplugged it. A little while later, I plugged it back in and it still was not recognized and was not charging. So, basically, no change.

**KeithZG** · Nov 10, 2009, 11:51 PM

Re: Continuing problem with Sansa Clip

I have a Sansa Clip myself; I tried to see yesterday if I had the same problem but an unrelated matter ended up crashing the computer before I could check and reply to your post here, heh. Just tried it with my sister's Sansa Clip on a new Karmic install and by default it didn't work, but the fix is pretty easy.

So my question for you is, what is your Clip set to in Settings -> USB Mode? I'd suspect it's set to "Auto detect", which yeah in my experience worked fine in Jaunty (and Hardy) BUT, well . . .

okay, before I wax philosophical, here's the fix. On the Sansa Clip, just go Settings -> USB Mode -> select "MSC".

Okay, now for my supposition as to why that works. On "Auto Detect", it theoretically queries for MTP support, and if it doesn't find any it reverts to MSC (which is just the "it's a USB drive" mode, ie. what shows up in Dolphin). Now, previously of course Linux/Kubuntu/KDE wasn't telling the Clip that there was MTP support, but it's quite possible that now (is it Karmic? is it KDE 4.3?) something is telling the Clip to be in MTP mode. Probably Amarok would work fine with it, but using it as a straight-up storage device just switch the Clip manually to "MSC" (sometimes called "UMS" elsewhere) and voila.

Soooo yeah. Long rambling for a short fix, but that should work! If not, get back to us and we'll (I'm pretending to speak for the forums and a whole now) figure something else out

**SteveTaylor** · Nov 11, 2009, 01:16 PM

Re: Continuing problem with Sansa Clip

I think I remember trying both MSC and MTP before, but I just tried both again and there was no improvement. I did have the Sansa Clip set to the Auto mode. That works on my second computer running Karmic. It is only on my Dell where the Sansa used to work until the last kernel update in Jaunty and now it is still not working with Karmic.

**KeithZG** · Nov 11, 2009, 08:04 PM

Re: Continuing problem with Sansa Clip

Hmmmm. I assume you've tried all the different USB ports, but of course that wouldn't even help if they're all on the same controller (and I'd assume that's *somehow* part of the problem, although of course I could be entirely wrong) . . . when you have it plugged in, does lsusb show anything? Is there any difference in the output of lsusb between when it's plugged in and when it isn't?

On my end:

Code:

keithzg@easy:~$ lsusb
Bus 001 Device 004: ID 0781:7435 SanDisk Corp.

etc etc, and "lsusb -v" includes:

Code:

Bus 001 Device 004: ID 0781:7435 SanDisk Corp. 
...
 idVendor      0x0781 SanDisk Corp. 
...
  bInterfaceClass     8 Mass Storage      
   bInterfaceSubClass   6 SCSI          
   bInterfaceProtocol   80 Bulk (Zip)  
...

And so forth.

**SteveTaylor** · Nov 12, 2009, 11:28 AM

Re: Continuing problem with Sansa Clip

When I do "lsusb -v" I don't see any reference to Sansa, SanDisk, or anything recognizable as my Clip.
However, in one of the "Hub" sections, I notice a reference to a "high speed power connect" that was listed on port 1. I unplugged my Clip and moved it to another port and when I ran "lsusb -v" again that reference had moved. This is the report section where it shows up.

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 2.06
iManufacturer 3 Linux 2.6.31-14-generic ehci_hcd
iProduct 2 EHCI Host Controller
iSerial 1 0000:00:13.5
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
Hub Descriptor:
bLength 11
bDescriptorType 41
nNbrPorts 10
wHubCharacteristic 0x000a
No power switching (usb 1.0)
Per-port overcurrent protection
bPwrOn2PwrGood 10 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00 0x00
PortPwrCtrlMask 0xff 0xff
Hub Port Status:
Port 1: 0000.0100 power
Port 2: 0000.0501 highspeed power connect
Port 3: 0000.0100 power
Port 4: 0000.0100 power
Port 5: 0000.0100 power
Port 6: 0000.0100 power
Port 7: 0000.0100 power
Port 8: 0000.0100 power
Port 9: 0000.0100 power
Port 10: 0000.0100 power
Device Status: 0x0003
Self Powered
Remote Wakeup Enabled

Thanks

**SteveTaylor** · Nov 12, 2009, 11:34 AM

Re: Continuing problem with Sansa Clip

I also ran this if it helps:

steve@steve-laptop:~$ tail -f /var/log/messages
Nov 12 08:24:15 steve-laptop kernel: [ 1885.189548] ata5.00: configured for UDMA/33
Nov 12 08:24:15 steve-laptop kernel: [ 1885.205557] ata5: EH complete
Nov 12 08:24:21 steve-laptop kernel: [ 1890.843459] ata5: soft resetting link
Nov 12 08:24:21 steve-laptop kernel: [ 1891.069565] ata5.00: configured for UDMA/33
Nov 12 08:24:21 steve-laptop kernel: [ 1891.085071] ata5: EH complete
Nov 12 09:09:23 steve-laptop kernel: [ 4592.795430] ata5: soft resetting link
Nov 12 09:09:23 steve-laptop kernel: [ 4593.020602] ata5.00: configured for UDMA/33
Nov 12 09:09:23 steve-laptop kernel: [ 4593.032906] ata5: EH complete
Nov 12 09:14:20 steve-laptop kernel: [ 4889.921052] usb 1-1: new high speed USB device using ehci_hcd and address 3
Nov 12 09:22:26 steve-laptop kernel: [ 5375.993798] usb 1-2: new high speed USB device using ehci_hcd and address 16

**kbunt** · Nov 14, 2009, 05:50 AM

Re: Continuing problem with Sansa Clip

It shouldn't be too hard. I have a Sansa e260 which is the generation just before the Clip came out.

Set the Clip to 'USB mode' and it should be mounted as if it was a regular flash drive. Problems arise when you try to use it as a MTP device or switch it to a MTP device. Of course, the MTP protocol is specific to Windoze so Linux must try to emulate it by using mtp-tools and other software/plugins which I am not sure it does well but I had issues when trying to use it but it works *sometimes*. You lose some of the features of the Sansa/Sandisk player when in USB MSC mode but it usually is more reliable because it's being treated as a USB drive device.

If you still have problems, change the player to USB mode. Turn it off. Plug it in your computer. Turn it on and see if Kubuntu detects it. Also, what media player are you using it with? I only have experience using it with Amarok.

You might try to keep it plugged in to the same usb port, too. If you still have issues, you might also try mounting it via fstab but it shouldn't be necessary.

**KeithZG** · Nov 15, 2009, 08:15 PM

Re: Continuing problem with Sansa Clip

kbunt: Umm as he mentions above, he's tried switching between the modes.

SteveTaylor: If you try switching it to MTP, is it detected by Amarok? (I'd expect no, since it seems to be detecting as something entirely different, but it's worth a long-shot try maybe?)

Gack. Other than that, I'm running low on ideas, although there must be some solution. You'd have to use a different computer obviously, but is your Clip updated to the latest firmware? Mine is V01.01.30A and my sisters' is V02.01.16A (hers is a version 2 clip, mine is version 1). Another link with info on the firmware is http://forums.sandisk.com/sansa/boar...hread.id=15109. Again, the problem sounds more like something to do with the kernel and your motherboard/usb-controller, and neither hers nor mine are up to date, but maybe worth a shot?

I wish I knew how to fix this!

Hmm. One other idea. Is there any change in the devices listed in /dev when you plug the Clip in? If you open GParted with the clip plugged in (in MSC) does it show up?

Edit to add: You might want to weigh in at this launchpad bug report with some details about exactly what hardware you're running, since it does look like others are having your problem: https://bugs.launchpad.net/ubuntu/+s...al/+bug/482995 The fact that it previously worked for you under specific kernel versions but not others might be useful information alone.

**SteveTaylor** · Nov 16, 2009, 08:51 PM

Re: Continuing problem with Sansa Clip

I checked my Sansa firmware and it is V01.01.32A. I added an entry at launchpad pertaining to this problem. I haven't had time to try the other couple suggestions yet, maybe tomorrow. I seem to remember looking for it under /dev and not seeing it, but I'll check that again.

**kbunt** · Nov 21, 2009, 10:12 AM

Re: Continuing problem with Sansa Clip

Originally posted by KeithZG

kbunt: Umm as he mentions above, he's tried switching between the modes.

SteveTaylor: If you try switching it to MTP, is it detected by Amarok? (I'd expect no, since it seems to be detecting as something entirely different, but it's worth a long-shot try maybe?)

Keith, I have had my troubles with Amarok with a Sansa e260 but eventually I got it working in either mode. It was a pita, though.

Also, Kubuntu seems finicky when moving usb devices around and who knows, maybe he moved it between changing modes. It could be anything. I recommend staying with usb mode and troubleshooting in that mode until he gets somewhere. I thought it was an easier configuration.

**binskipy2u** · Dec 06, 2009, 07:03 PM

Re: Continuing problem with Sansa Clip

Ive used ubuntu before, with NO problems.. now using kubuntu, my 8 gig sansa clip wont mount it says it's charging, but the readout is blinking differently then when it was charging on ubuntu, so I dont know if its working..
ive read everything.. it must be a simple fix, I shouldnt have to install ubuntu along w/kubuntu just to use a MP3 player should i

?

any help would be most appreciated

Announcement

Continuing problem with Sansa Clip

Continuing problem with Sansa Clip

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment