[SOLVED] Sansa Clip+ inaccessible

rbuchanan · 08-01-2015, 01:26 PM

dmesg|tail:

Code:

[ 1176.852192] usb 1-1: new high speed USB device using ehci_hcd and address 2
[ 1176.940112] hub 1-0:1.0: unable to enumerate USB device on port 1
[ 1178.092193] usb 1-1: new high speed USB device using ehci_hcd and address 3
[ 1178.226329] usb 1-1: New USB device found, idVendor=0781, idProduct=74d0
[ 1178.226338] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1178.226345] usb 1-1: Product: SanDisk Sansa Clip+
[ 1178.226350] usb 1-1: Manufacturer: SanDisk
[ 1178.226354] usb 1-1: SerialNumber: 0D1103083029C5A80000000000000000
[ 1178.227317] usb 1-1: configuration #1 chosen from 1 choice

The player's USB mode is set to MTP, and mtpfs is installed.

goumba · 08-04-2015, 08:08 PM

I know this isn't the answer you want, but I have never had any luck in using the Clip+ in MTP mode with Linux. The only way I could ever get it to work is in MSC mode.

rbuchanan · 08-16-2015, 04:44 AM

Quote:

Originally Posted by goumba

I know this isn't the answer you want, but I have never had any luck in using the Clip+ in MTP mode with Linux. The only way I could ever get it to work is in MSC mode.

How? Frankly, I'd be perfectly satisfied to establish access by any means. dmesg output ulterior to jointure of Clip+ in MSC mode:

Code:

[69894.974061] sd 5:0:0:0: [sdb] 15462400 512-byte logical blocks: (7.91 GB/7.37 GiB)
[69894.975558] sd 5:0:0:0: [sdb] Write Protect is off
[69894.975562] sd 5:0:0:0: [sdb] Mode Sense: 04 00 00 00
[69894.975564] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[69894.976562] sd 5:0:0:1: [sdc] Attached SCSI removable disk
[69894.978298] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[69894.978304]  sdb:
[69894.981961] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[69894.981966] sd 5:0:0:0: [sdb] Attached SCSI removable disk

goumba · 08-16-2015, 07:33 AM

Honestly, mine just works in MSC mode. Linux would recognize it in MTP mode, but no application could successfully transfer files. In MSC mode, it just shows up in a File Manager as "3.9GB Volume".

Launch your file manager of choice, and if it's not automatically mounted, look for the volume that matches in size. On most File Managers you simply click the device to mount it. That will make it appear just as any other drive.

rbuchanan · 08-16-2015, 07:51 AM

Quote:

Originally Posted by goumba

Honestly, mine just works in MSC mode. Linux would recognize it in MTP mode, but no application could successfully transfer files. In MSC mode, it just shows up in a File Manager as "3.9GB Volume".

Launch your file manager of choice, and if it's not automatically mounted, look for the volume that matches in size. On most File Managers you simply click the device to mount it. That will make it appear just as any other drive.

In Tux Commander, mount points listed in their toolbar are fixed, determined by fstab's configuration; PCManFM automatically recognizes every other storage device that I couple to this PC irrespective of its compatibility, but not the Clip+. As you can see above, dmesg yields no device name (sdb: ), so I'm confounded...!

goumba · 08-16-2015, 08:08 AM

It does list a device name, sdb.

The storage in the Clip+ is not partitioned, so, try this:

Code:

mount /dev/sdb /mnt

Replace /mnt with your mount point of choice. If that doesn't work, add -t msdos.

rbuchanan · 08-16-2015, 08:16 AM

That redressed my impasse; thank you so much! BTW, I can only mount the drive as root; how do I procure permissions to do so as [user]?

rbuchanan · 08-16-2015, 08:23 AM

Kindly disregard the (rather asinine) query of my prior post. I configured fstab to accommodate the Sansa and can now access it effortlessly. Again, thank you!