USB devices give error when connected.

trebek · 10-16-2009, 01:25 AM

Hi there folks. It's been a while since I've posted here.

I have been having some trouble with USB devices when plugged into my machine, specially mp3 players and phones. Before, i used to be able to just connect a device and a mount point would appear on my desktop, by itself. Now, i get an error when connecting my mp3 player or a mobile phone. See the output from messages below:

Oct 15 19:41:27 punisher-laptop kernel: [ 1570.849579] usb 2-2: configuration #1 chosen from 1 choice
Oct 15 19:41:27 punisher-laptop kernel: [ 1570.904354] cdc_acm 2-2:1.1: ttyACM0: USB ACM device
Oct 15 19:41:27 punisher-laptop kernel: [ 1570.913125] usb 2-2: bad CDC descriptors
Oct 15 19:41:27 punisher-laptop kernel: [ 1570.913160] usb 2-2: bad CDC descriptors
Oct 15 19:45:32 punisher-laptop kernel: [ 1815.334035] usb 2-2: USB disconnect, address 12

Same thing on dmesg.

root@punisher-laptop:~# dmesg | tail
[ 1023.161192] usb 2-1: configuration #1 chosen from 1 choice
[ 1023.215323] cdc_acm 2-1:1.1: ttyACM0: USB ACM device
[ 1023.225288] usb 2-1: bad CDC descriptors
[ 1023.225323] usb 2-1: bad CDC descriptors
[ 1065.854177] usb 2-1: USB disconnect, address 6
[ 1069.604054] usb 2-1: new full speed USB device using ohci_hcd and address 7
[ 1069.817660] usb 2-1: configuration #1 chosen from 1 choice
[ 1069.873341] cdc_acm 2-1:1.1: ttyACM0: USB ACM device
[ 1069.879122] usb 2-1: bad CDC descriptors
[ 1069.879156] usb 2-1: bad CDC descriptors

Does anybody know what solves this problem? I suppose something about cdc descriptors, error which i haven't encountered before.

Thanks for your help.

business_kid · 10-16-2009, 03:15 AM

Some mp3 players need a special utility to talk to them. You gotta be specific here.
Ditto for phones - even phones with linux on them.

trebek · 10-16-2009, 07:45 PM

Well, the phone is a Nokia 6300, and the mp3 player is a sandisk e250.

For instance, for the mp3 player, i get the following on dmesg and messages respectively:

[ 307.184064] usb 1-2: new high speed USB device using ehci_hcd and address 3
[ 309.096073] hub 1-0:1.0: unable to enumerate USB device on port 2

Oct 16 18:42:59 punisher-laptop kernel: [ 307.184064] usb 1-2: new high speed USB device using ehci_hcd and address 3
Oct 16 18:45:11 punisher-laptop kernel: [ 438.284061] usb 1-2: new high speed USB device using ehci_hcd and address 4

business_kid · 10-17-2009, 03:18 AM

AFAIK, some of these devices don't advertise their presence. I know my phone doesn't.

I know nothing about those ones, but if they smell of drm you could have trouble. I mount my phone this way
mount /dev/.sdb
(This throws an error. I know it's there, but the pc doesn't)
mount /dev/sdb1 -t vfat /mnt

That goes.

trebek · 10-18-2009, 08:59 PM

Hi there.

Today, the computer decided to discover the mp3 player and it showed me the files. Nevertheless, i was not able to write or delete anything off of it. Here is the output from dmesg from all these activities. I think there's something very wrong with my kernel. Let me know if you guys need anything else to help me troubleshoot this problem.

[ 6452.768163] FAT: Filesystem panic (dev sdb)
[ 6452.768170] fat_get_cluster: invalid cluster chain (i_pos 0)
[ 6454.903545] FAT: Filesystem panic (dev sdb)
[ 6454.903555] invalid access to FAT (entry 0x0000fa0c)
[ 6454.912607] FAT: Filesystem panic (dev sdb)
[ 6454.912619] fat_get_cluster: invalid cluster chain (i_pos 0)
[ 6454.965363] FAT: Filesystem panic (dev sdb)
[ 6454.965376] fat_get_cluster: invalid cluster chain (i_pos 0)
[ 6455.007212] FAT: Filesystem panic (dev sdb)
[ 6455.007222] fat_get_cluster: invalid cluster chain (i_pos 0)
[ 6456.127714] FAT: Filesystem panic (dev sdb)
[ 6456.127726] fat_get_cluster: invalid cluster chain (i_pos 0)
[ 6456.136793] FAT: Filesystem panic (dev sdb)
[ 6456.136803] invalid access to FAT (entry 0x0000f53b)
[ 6456.161970] FAT: Filesystem panic (dev sdb)
[ 6456.161980] fat_get_cluster: invalid cluster chain (i_pos 0)
[ 6456.180605] FAT: Filesystem panic (dev sdb)

business_kid · 10-19-2009, 03:42 AM

I googled sandisk linux and came up with the first thing you should have read
http://www.howtoforge.com/sandisk_mp3_player_linux

As for the phone, the same basic (nokia 6300 linux) check gave me this
http://nrw.free.fr/board.php?go=proj...linux.inc.html

:-o?

trebek · 10-20-2009, 08:44 AM

Too bad man, my sansa device does not have the USB Mode option.

michaelk · 10-20-2009, 09:45 AM

The method depends on the player model and firmware version. With the E250 one had to switch the HOLD/LOCK switch on, and hold the << button down during connection to put the player in MSC mode. I've also read that early version 3 units did not have a MSC mode. Have you upgraded your firmware?

trebek · 10-20-2009, 01:30 PM

Hi there, all of your help led me to fixing the issue. I ended up looking at the sansa forums, where i found all the info i needed. I managed to get it detected without the errors i saw in dmesg, and also upgraded my firmware for the device right from within ubuntu.

Thanks too much!!!! If allowed, i'll paste the link where it was fixed.

Let me know guys, thanks again.

trebek · 10-20-2009, 09:51 PM

Worked once, now i wanted to add more files, and having now the upgraded firmware, same thing on dmesg.

[44755.782808] atkbd.c: Unknown key released (translated set 2, code 0x9e on isa0060/serio0).
[44755.782814] atkbd.c: Use 'setkeycodes e01e <keycode>' to make it known.
[49638.288067] usb 1-2: new high speed USB device using ehci_hcd and address 15
[49643.052091] hub 1-0:1.0: unable to enumerate USB device on port 2
[49702.620261] usb 1-2: new high speed USB device using ehci_hcd and address 16
[49704.632092] hub 1-0:1.0: unable to enumerate USB device on port 2
[49847.273263] usb 1-2: new high speed USB device using ehci_hcd and address 17
[49849.524381] hub 1-0:1.0: unable to enumerate USB device on port 2
[49905.433054] usb 1-2: new high speed USB device using ehci_hcd and address 18
[49910.396071] hub 1-0:1.0: unable to enumerate USB device on port 2

manwithaplan · 10-20-2009, 09:54 PM

Quote:

Originally Posted by business_kid

I googled sandisk linux and came up with the first thing you should have read
http://www.howtoforge.com/sandisk_mp3_player_linux

As for the phone, the same basic (nokia 6300 linux) check gave me this
http://nrw.free.fr/board.php?go=proj...linux.inc.html

:-o?

Google is amazing isn't it ... You just need to search .

trebek · 10-21-2009, 08:04 AM

Already been there. I even registered into Sansa forums. I did not have the option like that, USB Mode, had to upgrade firmware from there. That meant having to change USB Mode by turning off the device, then placing it on hold and plug it with the left button pressed down; after this it got recognized, and i was able to upgrade it's firmware. Later, i connected it the second time, and it's not working again with neither of the 3 options of USB Mode the player comes with.

I'll try again from scratch once i get home. Perhaps it'll work after a reboot.

Thanks.

business_kid · 10-22-2009, 03:34 AM

It's a bad idea to look for help and only give half the story. If we had known all of that, we could come in where you were instead of starting at stage 1.

trebek · 10-22-2009, 09:17 PM

Hey, the other half of that story i did after one of the suggestions from the people who replied to my thread. I didn't know "all of that" until i was able to get it working for a short while.

Sorry if you misunderstood and thought that i was holding info from you, i promise you, i wasn't.

Thanks.

trebek · 11-02-2009, 09:23 PM

Quote:

Originally Posted by michaelk

The method depends on the player model and firmware version. With the E250 one had to switch the HOLD/LOCK switch on, and hold the << button down during connection to put the player in MSC mode. I've also read that early version 3 units did not have a MSC mode. Have you upgraded your firmware?

I have performed the firmware upgrade to v03.01.16A. Which is the latest according to the sandisk team. I am now able to switch usb modes from the menu list. I have upgraded my machine to ubuntu 9.10, and i can't get it to mount or appear when i plug it into my machine in either usb mode.

Here's the error i get from dmesg:

Code:

[18789.252612] hub 1-0:1.0: unable to enumerate USB device on port 2
[18850.072078] usb 1-2: new high speed USB device using ehci_hcd and address 6
[18854.795941] hub 1-0:1.0: unable to enumerate USB device on port 2
[24147.839924] usb 1-2: new high speed USB device using ehci_hcd and address 7
[24152.648236] hub 1-0:1.0: unable to enumerate USB device on port 2

CHECK THIS OUT!!!

Just out of curiosity, i decided to unplug my usb mouse, and then plug the sandisk player into the machine. IT GOT RECOGNIZED WITHOUT THAT enumerate error message; and furthermore, i plugged my mouse into the usb slot and it's working fine! I surely don't think that this would be necessary: plug devices in a certain order to avoid problems. Interesting isn't it??? Have a look at the output after this weird test.

Code:

[18850.072078] usb 1-2: new high speed USB device using ehci_hcd and address 6
[18854.795941] hub 1-0:1.0: unable to enumerate USB device on port 2
[24147.839924] usb 1-2: new high speed USB device using ehci_hcd and address 7
[24152.648236] hub 1-0:1.0: unable to enumerate USB device on port 2
[27982.350388] ath5k phy0: unsupported jumbo
[38019.742714] usb 2-3: USB disconnect, address 2
[38029.191119] atkbd.c: Unknown key pressed (translated set 2, code 0x9f on isa0060/serio0).
[38029.191128] atkbd.c: Use 'setkeycodes e01f <keycode>' to make it known.
[38029.191187] atkbd.c: Unknown key released (translated set 2, code 0x9f on isa0060/serio0).
[38029.191193] atkbd.c: Use 'setkeycodes e01f <keycode>' to make it known.
[38033.015217] atkbd.c: Unknown key pressed (translated set 2, code 0x9e on isa0060/serio0).
[38033.015226] atkbd.c: Use 'setkeycodes e01e <keycode>' to make it known.
[38033.015285] atkbd.c: Unknown key released (translated set 2, code 0x9e on isa0060/serio0).
[38033.015291] atkbd.c: Use 'setkeycodes e01e <keycode>' to make it known.
[38064.721053] usb 1-2: new high speed USB device using ehci_hcd and address 8
[38069.440095] hub 1-0:1.0: unable to enumerate USB device on port 2
[38069.824054] usb 2-2: new full speed USB device using ohci_hcd and address 3
[38070.025095] usb 2-2: not running at top speed; connect to a high speed hub
[38070.043909] usb 2-2: configuration #1 chosen from 1 choice
[38070.054389] scsi3 : SCSI emulation for USB Mass Storage devices
[38070.054695] usb-storage: device found at 3
[38070.054700] usb-storage: waiting for device to settle before scanning
[38075.053324] usb-storage: device scan complete
[38075.059296] scsi 3:0:0:0: Direct-Access     SanDisk  Sansa e250       v03. PQ: 0 ANSI: 0
[38075.065262] scsi 3:0:0:1: Direct-Access     SanDisk  Sansa e250       v03. PQ: 0 ANSI: 0
[38075.066261] sd 3:0:0:0: Attached scsi generic sg2 type 0
[38075.066580] sd 3:0:0:1: Attached scsi generic sg3 type 0
[38075.098344] sd 3:0:0:0: [sdb] 3951616 512-byte logical blocks: (2.02 GB/1.88 GiB)
[38075.114306] sd 3:0:0:1: [sdc] Attached SCSI removable disk
[38075.119937] sd 3:0:0:0: [sdb] Write Protect is off
[38075.119951] sd 3:0:0:0: [sdb] Mode Sense: 04 00 00 00
[38075.119960] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[38075.173284] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[38075.173300]  sdb:
[38075.207249] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[38075.207263] sd 3:0:0:0: [sdb] Attached SCSI removable disk
[38090.701047] usb 2-1: new low speed USB device using ohci_hcd and address 4
[38090.908941] usb 2-1: configuration #1 chosen from 1 choice
[38090.925274] input: USB OpticalWheel Mouse as /devices/pci0000:00/0000:00:13.0/usb2/2-1/2-1:1.0/input/input9
[38090.925568] generic-usb 0003:04FC:0005.0002: input,hidraw0: USB HID v1.10 Mouse [USB OpticalWheel Mouse] on usb-0000:00:13.0-1/input0

And another weird thing, after it worked, i disconnected the device a second time, and plugged it back in, and it worked. After that, i detached it, and plugged it back in, and the error came back. I am starting to think that this is a bug with the module that handles i/o connections, but perhaps I'm wrong. If anybody could shed a light on this issue, it would be greatly appreciated.

Thanks for your help.