1 |
On Thu, Oct 27, 2005 at 12:31:37AM -0400, James Hiscock wrote: |
2 |
> |
3 |
> Did you specify the correct device for moto4lin? Should be |
4 |
> /dev/ttyACM0. Also, check the permissions on /dev/ttyACM0 -- by |
5 |
> default, they're too restrictive. |
6 |
|
7 |
It defaults to /dev/usb/acm/0 which seems to be correct for me. At least |
8 |
this file exists, whereas /dev/ttyACM0 does not. |
9 |
|
10 |
I tried it as root to make sure there were no permissions problems - it |
11 |
had no effect. |
12 |
|
13 |
> If you run moto4lin from a terminal, it spits out a bit of debugging |
14 |
> info that might help too, that looks like this: |
15 |
. |
16 |
. |
17 |
> <snip> |
18 |
> doActConnect |
19 |
> doActConnect |
20 |
> P2kProc::doConnect() |
21 |
> New mode: 2 |
22 |
> doActConnect |
23 |
> Filelist received: 527 |
24 |
> </snip> |
25 |
> |
26 |
|
27 |
For me it produces: |
28 |
Form1 |
29 |
PhoneMan |
30 |
New mode: 1 |
31 |
doActConnect |
32 |
doActConnect |
33 |
P2kProc::doConnect() |
34 |
New mode: 0 |
35 |
|
36 |
> > What do your system messages look like? |
37 |
> |
38 |
> When I first plugged in the phone, I got this: |
39 |
> <snip> |
40 |
> usb 4-2: new full speed USB device using uhci_hcd and address 2 |
41 |
> usb 4-2: configuration #1 chosen from 2 choices |
42 |
> usb.agent[24980]: Keeping default configuration with |
43 |
> /sys//devices/pci0000:00/0000:00:1d.3/usb4/4-2 |
44 |
> cdc_acm 4-2:1.0: ttyACM0: USB ACM device |
45 |
> usbcore: registered new driver cdc_acm |
46 |
> drivers/usb/class/cdc-acm.c: v0.23:USB Abstract Control Model driver |
47 |
> for USB modems and ISDN adapters |
48 |
> </snip> |
49 |
|
50 |
Looks like the main clues are the error messages produced when I plug in: |
51 |
usb 1-1: new full speed USB device using uhci_hcd and address 8 |
52 |
usb 1-1: device descriptor read/64, error -71 |
53 |
usb 1-1: device descriptor read/64, error -71 |
54 |
usb 1-1: new full speed USB device using uhci_hcd and address 9 |
55 |
usb 1-1: device descriptor read/64, error -71 |
56 |
cdc_acm 1-1:1.0: ttyACM0: USB ACM device |
57 |
|
58 |
vs your |
59 |
usb 4-2: new full speed USB device using uhci_hcd and address 2 |
60 |
usb 4-2: configuration #1 chosen from 2 choices |
61 |
usb.agent[24980]: Keeping default configuration with |
62 |
/sys//devices/pci0000:00/0000:00:1d.3/usb4/4-2 |
63 |
cdc_acm 4-2:1.0: ttyACM0: USB ACM device |
64 |
|
65 |
and the fact that you get a /dev/ttyACM0 and I get a /dev/usb/acm/0. |
66 |
I wonder if that indicates a slight USB driver change between our |
67 |
two kernels? |
68 |
|
69 |
I assume the two addresses I get on connect reflect the fact that my |
70 |
phone has two interfaces defined - one comm. with a single endpoint, and |
71 |
one data with 2 endpoints. Yours seems to have two configurations |
72 |
whereas mine has Cfg#=1 |
73 |
|
74 |
Errno 71 corresponds to "protocol error" which doesn't sound good. |
75 |
|
76 |
What does your /proc/bus/usb/devices entry show for the phone? |
77 |
|
78 |
Regards, |
79 |
DigbyT |
80 |
-- |
81 |
Digby R. S. Tarvin digbyt@××××××.com |
82 |
http://www.digbyt.com |
83 |
-- |
84 |
gentoo-user@g.o mailing list |