Re: [Barry-devel] Barry and BB8800 ?
On Sat, Jul 05, 2008 at 08:15:12PM +0200, Reinhold Schoeb wrote: Also, does your device allow you to set the number of retries? ?You might want to set this to 10 or more. No, I can only choose between 3 til 5. Interesting. This would be the problem. :-) Most devices seem to allow for 10 retries. I'm not sure why yours is different, but perhaps throwing an exception at 5 reties left, like Barry does, is a bit extreme. I've updated the latest CVS to throw this exception at 2 instead of 5, which should fix the issue you are having. I notice you are using prebuilt binaries, so to test this, you'll need to compile things yourself. This is actually fairly easy. If you have cvs, autoconf, automake, libtool, g++ installed, you can do the following to build and test: Download from CVS: cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/barry login (press enter when it asks for password) cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/barry co -P barry Then build the command line tools: cd barry ./buildgen.sh ./configure make Then test that btool works, with: tools/btool -t -P password Please report back whether this works for you or not. If it does, I can help step you through building your own binary packages if you like. Hi Chris, Thanks a lot for your help. With your new CVS version everything works great, including barrybackup :-) Reinhold FYI: I have it now running with Debian Sid amd64. - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
Re: [Barry-devel] Barry and BB8800 ?
Hi Chris, Thanks a lot for your answer. Am Samstag, 5. Juli 2008 11:16:28 schrieb [EMAIL PROTECTED]: On Fri, Jul 04, 2008 at 03:35:07PM +0200, Reinhold Schoeb wrote: I am trying to get a BB8800 running with Barry, using Debian Sid amd64 and packages from http://www.koppenterprises.net/barry/barry-CVS/ 1. Bcharge works : mebsuta:~# bcharge Scanning for Blackberry devices... Found device #011...already at 500mA...already in desired Pearl mode...no change 2. Same with btool list devices : mebsuta:~# btool -l Blackberry devices found: Device ID: 0x655fa0. PIN: 253ddd86, Description: RIM 8800 Series Colour GPRS Handheld Hi Reinhold, Good to see the above works. Yes :-) 3. Thats what I get with btool -t [EMAIL PROTECTED]:~$ btool -t -P password -p 253ddd86 Blackberry devices found: Device ID: 0x654fa0. PIN: 253ddd86, Description: RIM 8800 Series Colour GPRS Handheld Using device (PIN): 253ddd86 Barry::Error caught: Fewer than 6 password tries remaining in device. Refusing to proceed, to avoid device zapping itself. Use a Windows client, or re-cradle the device. Do you have a Windows machine to test with? If you connect with Windows, then try on Linux again, does the error go away? I tryed on a Windows system with Desktop Manager. It works, but the problem with btool remains. Also, does your device allow you to set the number of retries? You might want to set this to 10 or more. No, I can only choose between 3 til 5. 4. And again with the verbose option : [EMAIL PROTECTED]:~$ btool -v -t -P asd0w -p 253ddd86 usb_set_debug: Setting debugging level to 9 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_os_find_busses: Found 002 usb_os_find_busses: Found 001 usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 001 on 002 [snip] usb_release_interface(0x651740,0) usb_close(0x651740) Barry::Error caught: Bad packet size. Packet: 26. DataSize(): 26. Required size: 44 Unfortunately, this is a different error than the password one, so I didn't get to see the raw packet during the password handshake. The only known way to fix the Bad packet size error right now, is to replug the device. Yes, you`re right. After replugging the device I get again the Fewer than 6 password ... message. Is there a way to accept 5 password retries ? Reinhold - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
[Barry-devel] Barry and BB8800 ?
I am trying to get a BB8800 running with Barry, using Debian Sid amd64 and packages from http://www.koppenterprises.net/barry/barry-CVS/ 1. Bcharge works : mebsuta:~# bcharge Scanning for Blackberry devices... Found device #011...already at 500mA...already in desired Pearl mode...no change 2. Same with btool list devices : mebsuta:~# btool -l Blackberry devices found: Device ID: 0x655fa0. PIN: 253ddd86, Description: RIM 8800 Series Colour GPRS Handheld 3. Thats what I get with btool -t [EMAIL PROTECTED]:~$ btool -t -P password -p 253ddd86 Blackberry devices found: Device ID: 0x654fa0. PIN: 253ddd86, Description: RIM 8800 Series Colour GPRS Handheld Using device (PIN): 253ddd86 Barry::Error caught: Fewer than 6 password tries remaining in device. Refusing to proceed, to avoid device zapping itself. Use a Windows client, or re-cradle the device. 4. And again with the verbose option : [EMAIL PROTECTED]:~$ btool -v -t -P asd0w -p 253ddd86 usb_set_debug: Setting debugging level to 9 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_os_find_busses: Found 002 usb_os_find_busses: Found 001 usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 001 on 002 error obtaining child information: Operation not permitted usb_os_find_devices: Found 011 on 001 usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 006 on 001 usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 005 on 001 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 004 on 001 skipped 1 class/vendor specific interface descriptors skipped 1 class/vendor specific interface descriptors usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 003 on 001 usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 002 on 001 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 001 on 001 error obtaining child information: Inappropriate ioctl for device error obtaining child information: Operation not permitted error obtaining child information: Operation not permitted error obtaining child information: Operation not permitted error obtaining child information: Operation not permitted error obtaining child information: Operation not permitted error obtaining child information: Operation not permitted usb_os_find_busses: Found 002 usb_os_find_busses: Found 001 usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 001 on 002 error obtaining child information: Operation not permitted usb_os_find_devices: Found 011 on 001 usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 006 on 001 usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 005 on 001 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 004 on 001 skipped 1 class/vendor specific interface descriptors skipped 1 class/vendor specific interface descriptors usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 003 on 001 usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 002 on 001 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 001 on 001 error obtaining child information: Inappropriate ioctl for device error obtaining child information: Operation not permitted error obtaining child information: Operation not permitted error obtaining child information: Operation not permitted error obtaining child information: Operation not permitted error obtaining child information: Operation not permitted error obtaining child information: Operation not permitted device_desc loaded bLength: 18 bDescriptorType: 1 bcdUSB: 272 bDeviceClass: 0 bDeviceSubClass: 0 bDeviceProtocol: 0 bMaxPacketSize0: 16 idVendor: 4042 idProduct: 4 bcdDevice: 262 iManufacturer: 1 iProduct: 5 iSerialNumber: 3 bNumConfigurations: 1 config_desc #0 loaded bLength: 9 bDescriptorType: 2 wTotalLength: 97 bNumInterfaces: 2 bConfigurationValue: 1 iConfiguration: 0 bmAttributes: 128 MaxPower: 250 interface_desc #0 loaded bLength: 9 bDescriptorType: 4 bInterfaceNumber: 0 bAlternateSetting: 0 bNumEndpoints: 8 bInterfaceClass: 255 bInterfaceSubClass: 1 bInterfaceProtocol: 255 iInterface: 2 endpoint_desc #0 loaded bLength: 7 bDescriptorType: 5 bEndpointAddress: 129 bmAttributes: 2 wMaxPacketSize: 64 bInterval: 0 bRefresh: 0 bSynchAddress: 0 endpoint added to map with bEndpointAddress: 129 pair.read = 129 pair.type = 2 endpoint_desc #1 loaded bLength: 7 bDescriptorType: 5 bEndpointAddress: 2 bmAttributes: 2 wMaxPacketSize: 64 bInterval: 0 bRefresh: 0 bSynchAddress: 0 endpoint added to map with bEndpointAddress: 2 pair.write = 2 pair.type = 2 pair added! (read: 129,write:
