* [gentoo-user] Sansa Clip+
@ 2010-02-18 23:34 sean
2010-02-18 23:41 ` Alan McKinnon
2010-02-19 1:25 ` [gentoo-user] " Nikos Chantziaras
0 siblings, 2 replies; 8+ messages in thread
From: sean @ 2010-02-18 23:34 UTC (permalink / raw
To: gentoo-user
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] Sansa Clip+
2010-02-18 23:34 [gentoo-user] Sansa Clip+ sean
@ 2010-02-18 23:41 ` Alan McKinnon
2010-02-19 0:15 ` sean
2010-02-19 1:25 ` [gentoo-user] " Nikos Chantziaras
1 sibling, 1 reply; 8+ messages in thread
From: Alan McKinnon @ 2010-02-18 23:41 UTC (permalink / raw
To: gentoo-user
On Friday 19 February 2010 01:34:36 sean wrote:
> 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?
Do you do yet the obvious first step, which is to plug in it and see what
happens?
If so, what happened?
If not, do so, then post what happened.
--
alan dot mckinnon at gmail dot com
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] Sansa Clip+
2010-02-18 23:41 ` Alan McKinnon
@ 2010-02-19 0:15 ` sean
2010-02-19 0:17 ` Alan McKinnon
2010-02-19 12:50 ` Damian
0 siblings, 2 replies; 8+ messages in thread
From: sean @ 2010-02-19 0:15 UTC (permalink / raw
To: gentoo-user
Alan McKinnon wrote:
>
> Do you do yet the obvious first step, which is to plug in it and see what
> happens?
>
> If so, what happened?
> If not, do so, then post what happened.
>
>
That I had tried.
The device is not seen.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] Sansa Clip+
2010-02-19 0:15 ` sean
@ 2010-02-19 0:17 ` Alan McKinnon
2010-02-22 17:57 ` sean
2010-02-19 12:50 ` Damian
1 sibling, 1 reply; 8+ messages in thread
From: Alan McKinnon @ 2010-02-19 0:17 UTC (permalink / raw
To: gentoo-user
On Friday 19 February 2010 02:15:49 sean wrote:
> Alan McKinnon wrote:
> > Do you do yet the obvious first step, which is to plug in it and see what
> > happens?
> >
> > If so, what happened?
> > If not, do so, then post what happened.
>
> That I had tried.
> The device is not seen.
what is the output from dmesg?
--
alan dot mckinnon at gmail dot com
^ permalink raw reply [flat|nested] 8+ messages in thread
* [gentoo-user] Re: Sansa Clip+
2010-02-18 23:34 [gentoo-user] Sansa Clip+ sean
2010-02-18 23:41 ` Alan McKinnon
@ 2010-02-19 1:25 ` Nikos Chantziaras
1 sibling, 0 replies; 8+ messages in thread
From: Nikos Chantziaras @ 2010-02-19 1:25 UTC (permalink / raw
To: gentoo-user
On 02/19/2010 01:34 AM, sean wrote:
> 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?
I have a Sansa Fuze (in MSC mode) and I can confirm it's working as long
as I have "USB Mass Storage" support enabled in the kernel and my user
is in the "usb" and "plugdev" groups.
If that won't work, please do the following
dmesg -c (as root)
Now plug the device in and wait for about 10 seconds. Then:
dmesg
and post the output.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] Sansa Clip+
2010-02-19 0:15 ` sean
2010-02-19 0:17 ` Alan McKinnon
@ 2010-02-19 12:50 ` Damian
2010-02-22 17:59 ` sean
1 sibling, 1 reply; 8+ messages in thread
From: Damian @ 2010-02-19 12:50 UTC (permalink / raw
To: gentoo-user
On Fri, Feb 19, 2010 at 1:15 AM, sean <tech.junk@myfairpoint.net> wrote:
> Alan McKinnon wrote:
>>
>> Do you do yet the obvious first step, which is to plug in it and see what
>> happens?
>>
>> If so, what happened?
>> If not, do so, then post what happened.
>>
>>
>
> That I had tried.
> The device is not seen.
That's strange. I have a Sansa Clip (although not the + model) and I
get the following message after plugging the device:
Feb 19 13:47:49 bucephalus kernel: [48421.594931] usb 7-5: New USB
device strings: Mfr=1, Product=2, SerialNumber=3
Feb 19 13:47:49 bucephalus kernel: [48421.594938] usb 7-5: Product:
SanDisk Sansa Clip
Feb 19 13:47:49 bucephalus kernel: [48421.594942] usb 7-5: Manufacturer: SanDisk
Feb 19 13:47:49 bucephalus kernel: [48421.594947] usb 7-5:
SerialNumber: B408F9040339B6A80000000000000000
Feb 19 13:47:49 bucephalus kernel: [48421.595175] usb 7-5: uevent
Feb 19 13:47:49 bucephalus kernel: [48421.595214] usb 7-5: usb_probe_device
Feb 19 13:47:49 bucephalus kernel: [48421.595222] usb 7-5:
configuration #1 chosen from 1 choice
Feb 19 13:47:49 bucephalus kernel: [48421.596891] usb 7-5: adding
7-5:1.0 (config #1, interface 0)
Did you enable USB in your kernel?
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] Sansa Clip+
2010-02-19 0:17 ` Alan McKinnon
@ 2010-02-22 17:57 ` sean
0 siblings, 0 replies; 8+ messages in thread
From: sean @ 2010-02-22 17:57 UTC (permalink / raw
To: gentoo-user
Alan McKinnon wrote:
>
> what is the output from dmesg?
>
I have the Sansa Clip + in MSC mode, though have tried the other two modes.
The tail end of my last few connects, and disconnects.
Not sure of how much to include.
[16243.196854] usb 3-3.2: new full speed USB device using ohci_hcd and
address 6
[16248.196977] usb 3-3.2: khubd timed out on ep0in len=0/64
[16253.197094] usb 3-3.2: khubd timed out on ep0in len=0/64
[16258.196213] usb 3-3.2: khubd timed out on ep0in len=0/64
[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
tardis sean
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] Sansa Clip+
2010-02-19 12:50 ` Damian
@ 2010-02-22 17:59 ` sean
0 siblings, 0 replies; 8+ messages in thread
From: sean @ 2010-02-22 17:59 UTC (permalink / raw
To: gentoo-user
Damian wrote:
> Did you enable USB in your kernel?
>
>
Sure did, USB memory sticks work fine, and I believe they work on the
same principal as the Clip+.
I attached dmesg output into another reply.
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2010-02-22 18:20 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-02-18 23:34 [gentoo-user] Sansa Clip+ sean
2010-02-18 23:41 ` Alan McKinnon
2010-02-19 0:15 ` sean
2010-02-19 0:17 ` Alan McKinnon
2010-02-22 17:57 ` sean
2010-02-19 12:50 ` Damian
2010-02-22 17:59 ` sean
2010-02-19 1:25 ` [gentoo-user] " Nikos Chantziaras
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox