On Thu, Apr 19, 2007 at 09:38:15PM -0400, [EMAIL PROTECTED] wrote: > Note that after a 'bcharge -o' the phone shows the charge symbol for > about 3 secs, then gives up and does not charge.
Thanks for your feedback! This is interesting, since below, in your lsusb -v output, you have: > MaxPower 500mA Which is the power it needs to charge on Linux. What indicates that it is not charging? Is the battery fully charged perhaps? > This is on feisty: > > Linux bicho 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007 i686 > GNU/Linux Good kernel for debugging... should have the usbfs_snoop patches already there. > which uses a new underlying usb driver: > > ii libusb-0.1-4 0.1.12-2 > userspace USB programming library > ii libusb-dev 0.1.12-2 > userspace USB programming library developmen I've used the latest on my machine, and haven't had any problems on Linux. The only place where this *might* be an issue is OpenBSD, to my knowledge. > However, I am still getting the timeout on btool -lt : [snip] > pair added! (read: 129,write: 2,type: 2) This is the only endpoint pair it sees. > BulkWrite to endpoint 2: > 00000000: 00 00 10 00 01 ff 00 00 a8 18 da 8d 6c 02 00 00 > ............l... > > Usb::Error caught: Timeout in usb_bulk_read And it fails. Normally we should see at least 2 endpoint pairs, and the second one is the one that works. Later on in the lsusb output: > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x02 EP 2 OUT > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 0 So far so good. > UNRECOGNIZED: 63 61 0a 09 30 38 20 20 4a 61 6d 61 69 63 61 > 0a 09 30 39 20 11 00 00 00 00 84 06 08 01 00 00 00 30 61 20 20 21 00 > 00 00 09 04 00 00 04 ff 01 ff 02 72 69 6e 20 84 06 08 00 00 00 00 00 > 00 00 00 6d 62 61 62 59 00 00 00 07 05 81 02 40 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 07 05 02 02 40 00 00 > Endpoint Descriptor: > bLength 0 > bDescriptorType 0 > bEndpointAddress 0x00 EP 0 OUT > bmAttributes 0 > Transfer Type Control > Synch Type None > Usage Type Data > wMaxPacketSize 0x0000 1x 0 bytes > bInterval 0 > Endpoint Descriptor: > bLength 0 > bDescriptorType 0 > bEndpointAddress 0x00 EP 0 OUT > bmAttributes 0 > Transfer Type Control > Synch Type None > Usage Type Data > wMaxPacketSize 0x0000 1x 0 bytes > bInterval 0 This is the first time I've seen an "unrecognized" message like that! I've been suspecting something like this all along, and maybe it's a combination of Linux kernel and Blackberry firmware issues that are tickling this bug. I'll have to examine that hex dump soon when I have time. Thanks very much for this. > cannot read device status, Operation not permitted (1) Did you run lsusb -v as root? - Chris ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
