On Tue, Jul 31, 2007 at 04:30:11PM +0200, Giulio Bottazzi wrote:
> Short update... it seems I found a voodoo to have the pearl
> recognized... the ritual has four steps
>
> 1 insert the device
> 2 #modprobe -r usb_storage
> 3 #./bcharge
> 4 #./bcharge -o
>
> and THEN (and only THEN) I have
>
> #./btool -l
> Blackberry devices found:
> Device ID: 0x522160. PIN: <xxxxxxxx>
>
>
> yes, you understood correctly, I had to give the command bcharge TWICE
> in that particular order. I guess you uber-hacker will work out an
> explanation for it :-) If you could suggest a less elaborated (and
> less black-magic sort of thing) way to have this done, I would
> appreciate!
You figured out the solution before I managed to reply. Excellent. :-)
This is a firmware issue, as I recall. I believe Troy Engel and
Miles Sabin ran into this before, if memory serves (seem mailing list
archives). Some people reported the problem went away after upgrading
the firmware on the Blackberry.
The core problem is that the endpoints for part of the configuration
are invalid to the linux kernel. If you view the device with lsusb -v,
you may get a hex dump depending on your version of lsusb. In btool,
it sees the config as a set of zeros, and so uses the wrong endpoint pair
to talk to the device. You can see this in the log you posted in
the previous email.... near the end of the configuration detail,
you'll see enpoints with 0's.
This is probably not the solution you wanted to hear, but it's the
best I've got so far. :-)
The fact that a firmware upgrade fixed this in the past makes me
strongly suspect the device itself, yet in theory, the device should
still work with Windows, so either there is a workaround in the
RIM Windows software that I'm not aware of, or maybe the Windows software
just resets the device multiple times anyway.
There are things we still don't know fully... that's why Barry is
only at version 0.7. :-)
Other things to try:
- a different kernel, or
- a different machine
I'd love to get my hands on a device like this to test with.
Unfortunately, all the devices I have work perfectly in this regard. :-)
- Chris
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Barry-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/barry-devel
