So with some research I found out that the cable actually likes the pl2303 driver (I can force the usb-generic driver to connect but then I can't communicate -- the pl2303 driver attaches by itself and allows communication).
However, everytime I do anything using the link, the link breaks shortly into a transfer and I get:
Jul 23 00:59:02 rider kernel: usb 1-2: control timeout on ep0in
I'm going to recompile with usb debug support and try to figure out where things are going wrong -- but its a bit late for that tonight...
Either way, I wanted it to be on the list the DCU-11 and DCU-10 cables work with the pl2303 driver (at least sorta ;) ).
OK, so I compiled "verbose debugging" under USB into my kernel hoping to get somewhere, and it's really not verbose at all -- I think there is some extra information about my root hubs, but that's about it.
So I'm trying to figure out how to debug this and I've managed to get some information, but I'm not sure how to proceed:
I have to programs able to talk to Sony Ericsson phones: multisync and tsemgr. Both are able to make an initial connection to the phone and then timeout.
I strace'd multisync and I see it do some select-read pairs, and then successfully write (same descriptor), then fail a write with EAGAIN (Resource temporarily unavailable), have many selects timeout over and over again... and then eventually give up:
...
select(19, [18], NULL, NULL, {30, 0}) = 1 (in [18], left {29, 999000})
read(18, "0C000000\r\n", 2048) = 10
write(18, "\203\0H\1\0E\0t\0e\0l\0e\0c\0o\0m\0/\0p\0b\0/\0l\0u"..., 72) = 64
write(18, "\0v\0c\0f\0\0", 8) = -1 EAGAIN (Resource temporarily unavailable)
select(19, [18], NULL, NULL, {30, 0}) = 0 (Timeout)
Tsemgr does a select, read, select, read, select, read, and then reports a communication error, which I find odd because the read is successful:
select(7, [6], NULL, NULL, {1, 0}) = 1 (in [6], left {0, 998000})
read(6, "7cYrPZWzWj0aPL7+pcQ", 19) = 19
write(1, "Comm-error waiting for OK after "..., 43) = 43I don't see this being a user-space software issue since 2 pieces of software both have issues -- though they do have different issues, which baffles me. That leads be to think either:
1. There might be some communication issues in the pl2303 driver 2. Perhaps the DCU-11 cable does something odd 3. The cable is flaky (it's brand new but you never know)
And I don't really know how to troubleshoot much further, and was hoping for some pointers on narrowing it down a bit more.
Thanks.
-- Phil Dibowitz [EMAIL PROTECTED] Freeware and Technical Pages Insanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/
"They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin, 1759
signature.asc
Description: OpenPGP digital signature
