BlackBerry Forums Support Community

BlackBerry Forums Support Community (http://www.blackberryforums.com/)
-   Linux Users Corner (http://www.blackberryforums.com/linux-users-corner/)
-   -   Berry does not detect BB (http://www.blackberryforums.com/linux-users-corner/121652-berry-does-not-detect-bb.html)

patb 03-21-2008 10:37 PM

Berry does not detect BB
 
Hi. I have a BB 7730 and want to sync it on Ubuntu Linux 7.10. I have installed Barry but none of the tools detects my BB via a direct USB connection. Some possibly relevant output is shown below. I would appreciate any guidance.

To anticipate some possible questions: Barry version is 0.11, Berry_charge is disabled, usb_storage is disabled, I have read the howto's on this site and I have Googled feverishly. :)

Thanks in advance, Pat.

Code:

pat@ubuntu:~$ btool -l
Blackberry devices found:

Code:

pat@ubuntu:~$ lsusb
Bus 003 Device 001: ID 0000:0000 
Bus 002 Device 001: ID 0000:0000 
Bus 001 Device 003: ID 046d:c016 Logitech, Inc. M-UV69a Optical Wheel Mouse
Bus 001 Device 001: ID 0000:0000

Code:

pat@ubuntu:~$ bidentify -v
usb_set_debug: Setting debugging level to 9 (on)
usb_os_init: Found USB VFS at /dev/bus/usb
usb_os_find_busses: Found 003
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 003
error obtaining child information: Operation not permitted
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: couldn't get connect info
usb_os_find_devices: Found 003 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: Operation not permitted
error obtaining child information: Operation not permitted
usb_os_find_busses: Found 003
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 003
error obtaining child information: Operation not permitted
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: couldn't get connect info
usb_os_find_devices: Found 003 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: Operation not permitted
error obtaining child information: Operation not permitted


rivviepop 03-22-2008 11:09 AM

Start by going to root, then "lsusb -v > lsusb.txt" and scan that for the word "Research" or maybe "RIM" to find the full entry for your device, then post that block here. For instance, the 8320 looks like this:

Code:

Bus 003 Device 003: ID 0fca:0004 Research In Motion, Ltd.
Device Descriptor:
  bLength                18
  bDescriptorType        1
  bcdUSB              1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass        0
  bDeviceProtocol        0
  bMaxPacketSize0        16
  idVendor          0x0fca Research In Motion, Ltd.
  idProduct          0x0004
  bcdDevice            1.06
  iManufacturer          1 Research In Motion
  iProduct                5 RIM Composite Device
  iSerial                3 XXXXPRIVATEXXXX
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                9
    bDescriptorType        2
    wTotalLength          97
    bNumInterfaces          2
    bConfigurationValue    1
    iConfiguration          0
    bmAttributes        0x80
    MaxPower              500mA

(lots and lots more, snipped for brevity)

NOTE: this is with berry_charge active and not btool/bcharge, but you should get something that looks somewhat similar, probably a lot shorter.

What you're looking for in that block above from your 'lsusb -v' is the idProduct and idVendor stuff, that's what identifies your device as a BlackBerry to the computer (for any of the tools).

patb 03-22-2008 04:56 PM

Thanks for the help, Rivviepop.

I'm still stuck, I'm afraid. I (hopefully) enabled berry_charge by commenting out the blacklist line in /etc/modprobe.d/blacklist-berry_charge (I followed ideas from this link)

Then I rebooted (to ensure the new rules applied) with the BB connected. But still "sudo lsusb -v" shows nothing about "RIM" or "Research". I did check the full output. Here is a cut down extract:

Code:

pat@ubuntu:~$ sudo lsusb -v | grep -iE 'bus|manuf|prod'
Bus 003 Device 001: ID 0000:0000 
  idProduct          0x0000
  iManufacturer          3 Linux 2.6.22-14-generic ehci_hcd
  iProduct                2 EHCI Host Controller
Bus 002 Device 001: ID 0000:0000 
  idProduct          0x0000
  iManufacturer          3 Linux 2.6.22-14-generic ohci_hcd
  iProduct                2 OHCI Host Controller
Bus 001 Device 003: ID 046d:c016 Logitech, Inc. M-UV69a Optical Wheel Mouse
  idProduct          0xc016 M-UV69a Optical Wheel Mouse
  iManufacturer          1 Logitech
  iProduct                2 Optical USB Mouse
      (Bus Powered)
  (Bus Powered)
Bus 001 Device 001: ID 0000:0000 
  idProduct          0x0000
  iManufacturer          3 Linux 2.6.22-14-generic ohci_hcd
  iProduct                2 OHCI Host Controller

For some reason, my system does not seem to detect the BB via the USB connection. Any other ideas would be welcome.

Cheers, Pat.

rivviepop 03-22-2008 08:22 PM

For the moment being, just put the idea of Barry, bcharge, btool and berry_charge out of mind; pretend they don't exist. The core problem it appears is that your device does not show up to the Linux subsystem itself; when the device is plugged in - even if nothing actually works (USB, charging, etc.) it should properly be listed as something in the output of lsusb -v. I call this the "is it plugged in?" test (regardless of what tech we're talking about).

You have a rather recent kernel, so that shouldn't be it - the core bits & pieces needed should be properly compiled. Have you tried loading the "uhci" USB subsystem for your machine instead of the "ehci" subsystem? It's very machine dependent which one you use (depends on the chips on your motherboard), this would be the first test I'd try and do. I'm not an Ubuntu guy to know how this distro allows you to "switch" the subsystems, but it's usually in /etc/modprobe.conf (if not, it's possible it's compiled into an initrd file - you'll need to Google for the specific Ubuntu way).

Google link for 'uhci ehci ubuntu" - lotsa hits:
http://www.google.com/search?hl=en&c...tu&btnG=Search

Try also examining /var/log/messages and /var/log/dmesg when you plug in the BlackBerry - do you see any errors or messages that might help give a clue why your system isn't registering the basic connection? I think you get where I'm going - ignore all the high level tools until you can at least get some sort of lsusb -v entry showing up on your machine, somehow some way.

patb 03-22-2008 09:01 PM

Quote:

Originally Posted by rivviepop (Post 866666)
For the moment being, just put the idea of Barry, bcharge, btool and berry_charge out of mind; pretend they don't exist. The core problem it appears is that your device does not show up to the Linux subsystem itself...

Love it, Rivviepop! You certainly know how to put someone back on track! :smile:

I'll try along the lines you suggest. Failing that, I'll see if the Ubuntu forums can help. If I do find a solution, I'll post here just to "complete" the thread.

Thanks again for your valuable help.

Cheers, Pat.

rivviepop 03-22-2008 09:06 PM

Quote:

Originally Posted by patb (Post 866706)
Love it, Rivviepop! You certainly know how to put someone back on track! :smile:

It's what I do for a living. :)

BTW, I forgot to mention - my laptop uses the UHCI (Thinkpad T43 running Fedora 8) USB subsystem which is why I brought that up, it was a key difference between our two machines that I saw from what you posted previously.

patb 04-01-2008 08:38 PM

Still no luck with this problem. No useful response at Ubuntu Forums, but I have found this bug report.

I have confirmed the problem is that my system continuously connects and disconnects rather than fails to detect the BB.

I tried loading the uhci module described by Rivviepop but that did not work. Ditto the fixes discussed in the bug report. I have not been able to make any other workaround. If I do find a solution, I'll post here.

Cheers, Pat.

rivviepop 04-04-2008 10:38 AM

Pat, I had a thought for you (but then got busy and didn't have playtime for forums ;) ) -- try downloading some "Live CD" ISO files and boot them on your computer and see if they work - maybe the tried-and-true Knoppix, a Fedora one, an Ubuntu one, there's even a CentOS one if you wanna do that - they're everywhere.

The idea is to just try other distros real quick without harming your computer, and see how *they* interact with your hardware and BB device. Just make sure to get something recent and not an old crufty one, you want the latest kernel in a LiveCD that you can get for the best tests...

patb 04-05-2008 04:49 PM

Quote:

Originally Posted by rivviepop (Post 883647)
Pat, I had a thought for you (but then got busy and didn't have playtime for forums ;) ) -- try downloading some "Live CD" ISO files and boot them on your computer and see if they work...

Yes Rivviepop, I should have mentioned that I tried several. Those that recognise the device without the continuous connects and disconnects include Puppy linux, DSL (Damn small linux) and Fluxbuntu (a lightweight installation of Ubuntu linux).

Those that fail include 'standard' Ubuntu, a 'recovery mode' boot into standard Ubuntu (administrator level command line only), and Xubuntu (a medium weight installation which uses the xfce desktop).

Puppy for instance gives the following (trimmed) output from lsusb -v:
Code:

T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 14 Spd=12  MxCh= 0
D:  Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS= 8 #Cfgs=  1
P:  Vendor=0fca ProdID=0001 Rev= 0.02
S:  Manufacturer=Research In Motion
S:  Product=Terminal mobile RIM
C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 4 Cls=ff(vend.) Sub=ff Prot=ff Driver=
E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=83(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=04(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms

So I'm thinking it's a problem to do with the Ubuntu setup, possibly to do with what modules are loaded. I'll keep looking for a solution.

Thanks and cheers, Pat.

ISBB 08-24-2008 05:15 PM

stupid question.. did you accidentally turn off usb ports in your BIOS? some work some dont :P


All times are GMT -5. The time now is 02:36 AM.

Powered by vBulletin® Version 3.6.12
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.