Re: [gentoo-user] Sansa Clip+
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 :01:00.1: urb 88023a512b40 path 3.2 ep0in 5fd6 cc 5 -- status -62 [16258.524141] ohci_hcd :01:00.1: urb 88023a512b40 path 3.2 ep0in 5ec2 cc 5 -- status -62 [16258.527141] ohci_hcd :01:00.1: urb 88023a512b40 path 3.2 ep0in 5ec2 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 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 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 :01:00.1: urb 88017cd349c0 path 3.2 ep0in 5fd6 cc 5 -- status -62 [16275.661133] ohci_hcd :01:00.1: urb 88017cd349c0 path 3.2 ep0in 5ec2 cc 5 -- status -62 [16275.664130] ohci_hcd :01:00.1: urb 88017cd349c0 path 3.2 ep0in 5ec2 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 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 evt 0004 [16277.276874] hub 3-3:1.0: state 7 ports 4 chg 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
Re: [gentoo-user] Sansa Clip+
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.
Re: [gentoo-user] Sansa Clip+
On Fri, Feb 19, 2010 at 1:15 AM, sean tech.j...@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: B408F9040339B6A8 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?
[gentoo-user] Sansa Clip+
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
Re: [gentoo-user] Sansa Clip+
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
Re: [gentoo-user] Sansa Clip+
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.
Re: [gentoo-user] Sansa Clip+
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
[gentoo-user] Sansa Clip+ no device for expansion card
I just got a Sansa Clip+ and when I plug it into my gentoo box, it sees the device as mass-storage, creates /dev/sdc, and I can mount it as vfat and put songs on it. That's all fine. However, I put an expansion micro-SD card into it. The player sees it fine. When I plug the player into my Mac, it puts two devices on the desktop. When I plug it into my Linux box, /var/log/messages only lists /dev/sdc (not /dev/sdc and /dev/sdd as I expected) being created. I can plug another USB device in and /dev/sdd is created, so there's nothing keeping the system from creating /dev/sdd. I have it's USB mode set to MSC. What else could be keeping it from seeing the expansion card? -- -M There are 10 kinds of people in this world: Those who can count in binary and those who cannot.
Re: [gentoo-user] Sansa Clip+ no device for expansion card
On Tue, Jan 19, 2010 at 3:43 PM, Michael George geo...@mutualdata.comwrote: I just got a Sansa Clip+ and when I plug it into my gentoo box, it sees the device as mass-storage, creates /dev/sdc, and I can mount it as vfat and put songs on it. That's all fine. However, I put an expansion micro-SD card into it. The player sees it fine. When I plug the player into my Mac, it puts two devices on the desktop. When I plug it into my Linux box, /var/log/messages only lists /dev/sdc (not /dev/sdc and /dev/sdd as I expected) being created. I can plug another USB device in and /dev/sdd is created, so there's nothing keeping the system from creating /dev/sdd. I have it's USB mode set to MSC. What else could be keeping it from seeing the expansion card? Probably kernel config - check to make sure you enabled Probe all LUNs on each SCSI device - under Device Drivers-SCSI device support -James
Re: [gentoo-user] Sansa Clip+ no device for expansion card
On Tue, 19 Jan 2010 18:43:35 -0500, Michael George wrote: However, I put an expansion micro-SD card into it. The player sees it fine. When I plug the player into my Mac, it puts two devices on the desktop. When I plug it into my Linux box, /var/log/messages only lists /dev/sdc (not /dev/sdc and /dev/sdd as I expected) being created. Make sure you have CONFIG_SCSI_MULTI_LUN=y in your kernel config. -- Neil Bothwick [unwieldy legal disclaimer would go here - feel free to type your own] signature.asc Description: PGP signature
Re: [gentoo-user] Sansa Clip+ no device for expansion card
On Tue, Jan 19, 2010 at 04:15:42PM -0800, James Ausmus wrote: On Tue, Jan 19, 2010 at 3:43 PM, Michael George geo...@mutualdata.comwrote: I just got a Sansa Clip+ and when I plug it into my gentoo box, it sees the device as mass-storage, creates /dev/sdc, and I can mount it as vfat and put songs on it. That's all fine. However, I put an expansion micro-SD card into it. The player sees it fine. When I plug the player into my Mac, it puts two devices on the desktop. When I plug it into my Linux box, /var/log/messages only lists /dev/sdc (not /dev/sdc and /dev/sdd as I expected) being created. I can plug another USB device in and /dev/sdd is created, so there's nothing keeping the system from creating /dev/sdd. I have it's USB mode set to MSC. What else could be keeping it from seeing the expansion card? Probably kernel config - check to make sure you enabled Probe all LUNs on each SCSI device - under Device Drivers-SCSI device support Ah, I checked and I didn't have that option set. I'll change it, rebuild, and reboot. Thanks to all who answered! -- -M There are 10 kinds of people in this world: Those who can count in binary and those who cannot.
