anyone running android sdk to talk to a real phone on fedora 14?

Tom Horsley horsley1953 at gmail.com
Sun Apr 24 02:57:19 UTC 2011


I can't figure out if this is a kernel problem or what
(though I lean towards kernel since it works one way
immediately after powering up the system and a different
way after that).

If I plug in my samsung intercept phone right after powering off then powering back up
and booting fedora 14, I see this show up in /var/log/messages:

Apr 23 22:31:52 zooty kernel: [  242.131064] usb 2-3: new high speed USB device using ehci_hcd and address 4
Apr 23 22:31:52 zooty kernel: [  242.354901] usb 2-3: New USB device found, idVendor=04e8, idProduct=681c
Apr 23 22:31:52 zooty kernel: [  242.354905] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 23 22:31:52 zooty kernel: [  242.374157] usb 2-3: can't set config #1, error -71

And lsusb shows this:

Bus 002 Device 004: ID 04e8:681c Samsung Electronics Co., Ltd Galaxy Portal/Spica Android Phone

which isn't really right as it is an Intercept, not a Galaxy.

Now I unplug the phone, and leaving the system up, plug the phone back in again:

unplug:

Apr 23 22:38:48 zooty kernel: [  658.159285] usb 2-3: USB disconnect, address 4

replug:

Apr 23 22:39:26 zooty kernel: [  696.061086] usb 2-3: new high speed USB device using ehci_hcd and address 5
Apr 23 22:39:26 zooty kernel: [  696.257079] usb 2-3: device descriptor read/64, error -71
Apr 23 22:39:26 zooty kernel: [  696.559082] usb 2-3: device descriptor read/64, error -71
Apr 23 22:39:26 zooty kernel: [  696.762074] usb 2-3: new high speed USB device using ehci_hcd and address 6
Apr 23 22:39:27 zooty kernel: [  696.957078] usb 2-3: device descriptor read/64, error -71
Apr 23 22:39:27 zooty kernel: [  697.249077] usb 2-3: device descriptor read/64, error -71
Apr 23 22:39:27 zooty kernel: [  697.452060] usb 2-3: new high speed USB device using ehci_hcd and address 7
Apr 23 22:39:38 zooty kernel: [  707.854076] usb 2-3: device not accepting address 7, error -110
Apr 23 22:39:38 zooty kernel: [  707.956083] usb 2-3: new high speed USB device using ehci_hcd and address 8
Apr 23 22:39:38 zooty kernel: [  707.956083] usb 2-3: new high speed USB device using ehci_hcd and address 8
Apr 23 22:39:48 zooty kernel: [  718.358072] usb 2-3: device not accepting address 8, error -110
Apr 23 22:39:48 zooty kernel: [  718.358083] hub 2-0:1.0: unable to enumerate USB device on port 3
Apr 23 22:39:48 zooty kernel: [  718.599078] usb 10-1: new full speed USB device using uhci_hcd and address 2
Apr 23 22:40:03 zooty kernel: [  733.704071] usb 10-1: device descriptor read/64, error -110
Apr 23 22:40:19 zooty kernel: [  748.911074] usb 10-1: device descriptor read/64, error -110
Apr 23 22:40:19 zooty kernel: [  749.114059] usb 10-1: new full speed USB device using uhci_hcd and address 3
Apr 23 22:40:20 zooty kernel: [  750.534082] hub 10-0:1.0: unable to enumerate USB device on port 1

It just goes completely wacko after the first time I plug it in.
No matter how many times I plug in in after that, I'll see the same
thing.

On the other hand, an ancient crappy system I have with only
usb 1 ports seems to work fine. It detects a communications
device and creates a /dev/ttyACM0 (or something like that)
as well as a storage device for the SD card.

Does this sound like something I should report as a kernel
bug?


More information about the users mailing list