Yes, I did, but to be sure I also tried it again after a reboot and got
pretty much the same:
27 March, 20:32 NZDT
>
> [...@zev ~] sudo bash
>
> [sudo] password for zev:
>
>
>> 27 March, 20:32 NZDT
>
> [r...@zev ~] btool
>
> Blackberry devices found:
>
> No device selected
>
>
>> 27 March, 20:32 NZDT
>
> [r...@zev ~] lsusb
>
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>
> Bus 004 Device 003: ID 0fca:0006 Research In Motion, Ltd.
>
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
>
>> 27 March, 20:32 NZDT
>
> [r...@zev ~] btool -lv
>
> usb_set_debug: Setting debugging level to 9 (on)
>
> usb_os_init: Found USB VFS at /dev/bus/usb
>
> Barry library version 0.16 (little endian)
>
> usb_os_find_busses: Found 002
>
> usb_os_find_busses: Found 003
>
> usb_os_find_busses: Found 004
>
> usb_os_find_busses: Found 001
>
> usb_os_find_devices: Found 001 on 002
>
> usb_os_find_devices: Found 001 on 003
>
> usb_os_find_devices: Found 003 on 004
>
> usb_os_find_devices: Found 001 on 004
>
> error obtaining child information: Inappropriate ioctl for device
>
> usb_os_find_devices: Found 001 on 001
>
> usb_os_find_busses: Found 002
>
> usb_os_find_busses: Found 003
>
> usb_os_find_busses: Found 004
>
> usb_os_find_busses: Found 001
>
> usb_os_find_devices: Found 001 on 002
>
> usb_os_find_devices: Found 001 on 003
>
> usb_os_find_devices: Found 003 on 004
>
> usb_os_find_devices: Found 001 on 004
>
> error obtaining child information: Inappropriate ioctl for device
>
> usb_os_find_devices: Found 001 on 001
>
> usb_os_find_busses: Found 002
>
> usb_os_find_busses: Found 003
>
> usb_os_find_busses: Found 004
>
> usb_os_find_busses: Found 001
>
> usb_os_find_devices: Found 001 on 002
>
> usb_os_find_devices: Found 001 on 003
>
> usb_os_find_devices: Found 003 on 004
>
> usb_os_find_devices: Found 001 on 004
>
> error obtaining child information: Inappropriate ioctl for device
>
> usb_os_find_devices: Found 001 on 001
>
> usb_os_find_busses: Found 002
>
> usb_os_find_busses: Found 003
>
> usb_os_find_busses: Found 004
>
> usb_os_find_busses: Found 001
>
> usb_os_find_devices: Found 001 on 002
>
> usb_os_find_devices: Found 001 on 003
>
> usb_os_find_devices: Found 003 on 004
>
> usb_os_find_devices: Found 001 on 004
>
> error obtaining child information: Inappropriate ioctl for device
>
> usb_os_find_devices: Found 001 on 001
>
> usb_os_find_busses: Found 002
>
> usb_os_find_busses: Found 003
>
> usb_os_find_busses: Found 004
>
> usb_os_find_busses: Found 001
>
> usb_os_find_devices: Found 001 on 002
>
> usb_os_find_devices: Found 001 on 003
>
> usb_os_find_devices: Found 003 on 004
>
> usb_os_find_devices: Found 001 on 004
>
> error obtaining child information: Inappropriate ioctl for device
>
> usb_os_find_devices: Found 001 on 001
>
> Blackberry devices found:
>
>
>> 27 March, 20:32 NZDT
>
> [r...@zev ~]
>
>
> If a firmware upgrade is needed, presumably I'll need to find a Windows PC
with Blackberry software on it? Might not be an easy option as I haven't had
any Windows machines in the household for a few years now!
On Fri, Mar 26, 2010 at 6:29 PM, Chris Frey <cdf...@foursquare.net> wrote:
> On Fri, Mar 26, 2010 at 06:24:57PM +1300, CzechWonderNine wrote:
> > OK, here's what I get after moving /etc/udev/rules.d/10-blackberry.rules:
>
> Just to confirm. You replugged your device after moving the file, right?
>
> According to the output, there are still 0's in the endpoint addresses.
> Next step would be a firmware update, to see if that helps.
>
> - Chris
>
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Barry-devel mailing list
> Barry-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/barry-devel
>
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel
