[gentoo-amd64] Sansa Clip+

[gentoo-amd64] Sansa Clip+

[sean]

Hello All,

	My son just purchased a Sansa Clip+ and from what I read it is supposed
to be accessible in Linux, it would look like a USB drive for drag and drop.

Anyway, I updated the firmware to the latest, and set the USB mode on
the Clip+ to MSC.

I am wondering if I need to setup support in the kernel, or something else?

Any tips anyone?

	Thanks
	Sean

[gentoo-amd64] Re: Sansa Clip+

[Duncan]

sean posted on Thu, 18 Feb 2010 17:28:30 -0500 as excerpted:

> My son just purchased a Sansa Clip+ and from what I read it is supposed
> to be accessible in Linux, it would look like a USB drive for drag and
> drop.
> 
> Anyway, I updated the firmware to the latest, and set the USB mode on
> the Clip+ to MSC.
> 
> I am wondering if I need to setup support in the kernel, or something
> else?

What are the other modes available on the clip+?  If I'm not mistaken, you 
want mass storage mode.

In mass storage mode, provided your kernel and udev is configured 
correctly, it should be detected (check the kernel logs, aka dmesg, just 
after plugging it in), activating the mass storage driver, which will 
detect the partitioning.  That will in turn activate udev to make 
available the device as a /dev/sdX device, with all the partitions, if 
any, available as /dev/sdXY, where X is a letter and Y is a number (like 
any other scsi system based block device, 
pata/sata/scsi/usb-mass-storage/whatever, only the old deprecated ide 
drivers use /dev/hdXY any more).  What happens after that (automounting, 
or simply available for you to mount manually) will depend on your fstab 
and hal config, etc.

Mass storage is by far the simplest mode to work with and troubleshoot.  
The other mode, media device or whatever, uses much lower level kernel 
drivers, usb and bit-banging or some such, with the higher level interface 
being userspace.  Generally, only specific media apps (such as amarok, 
with the appropriate USE flags, I assume there's a gtk/gnome media app 
that supports that too) with the userspace support built-in will be able 
to deal with devices in that mode.  In media mode, the device will not 
normally be available in a file manager, etc, as it isn't exposed as a 
block device, except in mass storage mode.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

Re: [gentoo-amd64] Re: Sansa Clip+

[sean]

Duncan wrote:
> 
> What are the other modes available on the clip+?  If I'm not mistaken, you 
> want mass storage mode.

From my reading, MSC is the setting I want.
I have tried the two others as well.

I have mass storage setup in the kernel, USB memory sticks work fine.
The Sansa reports fat32 as the file system.

Re: [gentoo-amd64] Re: Sansa Clip+

[sean]

Oh yea,

	Some info from dmesg.
I was not sure how much is needed.

[16258.262213] usb 3-3.2: device descriptor read/64, error -110
[16258.521154] ohci_hcd 0000:01:00.1: urb ffff88023a512b40 path 3.2
ep0in 5fd60000 cc 5 --> status -62
[16258.524141] ohci_hcd 0000:01:00.1: urb ffff88023a512b40 path 3.2
ep0in 5ec20000 cc 5 --> status -62
[16258.527141] ohci_hcd 0000:01:00.1: urb ffff88023a512b40 path 3.2
ep0in 5ec20000 cc 5 --> status -62
[16258.546169] hub 3-3:1.0: unable to enumerate USB device on port 2
[16258.549198] hub 3-3:1.0: state 7 ports 4 chg 0000 evt 0004
[16258.555149] hub 3-3:1.0: port 2, status 0100, change 0001, 12 Mb/s
[16258.758118] hub 3-3:1.0: debounce: port 2: total 175ms stable 100ms
status 0x100
[16260.159893] hub 3-3:1.0: state 7 ports 4 chg 0000 evt 0004
[16260.164996] hub 3-3:1.0: port 2, status 0101, change 0001, 12 Mb/s
[16260.278845] hub 3-3:1.0: debounce: port 2: total 100ms stable 100ms
status 0x101
[16260.345831] usb 3-3.2: new full speed USB device using ohci_hcd and
address 7
[16265.345960] usb 3-3.2: khubd timed out on ep0in len=0/64
[16270.345081] usb 3-3.2: khubd timed out on ep0in len=0/64
[16275.345208] usb 3-3.2: khubd timed out on ep0in len=0/64
[16275.411186] usb 3-3.2: device descriptor read/64, error -110
[16275.658149] ohci_hcd 0000:01:00.1: urb ffff88017cd349c0 path 3.2
ep0in 5fd60000 cc 5 --> status -62
[16275.661133] ohci_hcd 0000:01:00.1: urb ffff88017cd349c0 path 3.2
ep0in 5ec20000 cc 5 --> status -62
[16275.664130] ohci_hcd 0000:01:00.1: urb ffff88017cd349c0 path 3.2
ep0in 5ec20000 cc 5 --> status -62
[16275.683163] hub 3-3:1.0: unable to enumerate USB device on port 2
[16275.686154] hub 3-3:1.0: state 7 ports 4 chg 0000 evt 0004
[16275.692136] hub 3-3:1.0: port 2, status 0100, change 0001, 12 Mb/s
[16275.894652] hub 3-3:1.0: debounce: port 2: total 175ms stable 100ms
status 0x100
[16275.894660] hub 3-3:1.0: state 7 ports 4 chg 0000 evt 0004
[16277.276874] hub 3-3:1.0: state 7 ports 4 chg 0000 evt 0004
[16277.287223] hub 3-3:1.0: port 2, status 0101, change 0001, 12 Mb/s
[16277.431845] hub 3-3:1.0: debounce: port 2: total 125ms stable 100ms
status 0x101
[16277.498836] usb 3-3.2: new full speed USB device using ohci_hcd and
address 8
tar