HowTo: Use bcharge to charge your BB under linux - Page 2 - BlackBerryForums.com : Your Number One BlackBerry Community

rivviepop · 05-16-2007, 01:36 PM

Quote:

Originally Posted by breakerfall

feisty, charge icon stays on for about 2 seconds...

Not that I know what's wrong, but have y'all watched your syslog and/or dmesg output, looking for entries that might provide a clue? It sounds like bcharge runs, adjusts the current, then 'something else' runs and re-resets the port.

The question is..... what's 'something else'.

breakerfall · 05-16-2007, 01:40 PM

good idea...
ill check when i get home...

should i see anything special along with the plug-in event?

rivviepop · 05-16-2007, 02:14 PM

Quote:

Originally Posted by breakerfall

should i see anything special along with the plug-in event?

You should see a typical pattern of "detected new USB device", followed by an invocation of 'bcharge' at least once to set the flow. What you're looking for is something after that pattern, but what exactly that is I don't know yet (just going on gut instinct at this point).

Do this: as root, do 'tail -f /var/log/messages', then hit ENTER a couple of times to clear the screen. Plug in your device and let the messages flow, then cut&paste everything from that window from where it started into the forum here (use the CODE + /CODE forums tags around it to protect the formatting).

HuwSy · 05-16-2007, 04:49 PM

Iv had the same problem for a while, ever since i went from edgy to feisty. But since gutsy it sometimes charges other times behaves in this way. Iv yet to determine whats different either time. But even running bcharge manually says it changer the current to 500mA but most of the time the charge icon on the phone doesn't stay and it doesn't charge.

breakerfall · 05-16-2007, 09:03 PM

Code:

May 16 21:36:27 kmiketop kernel: [14284.728000] usb 2-1: new full speed USB device using uhci_hcd and address 3
May 16 21:36:27 kmiketop kernel: [14284.892000] usb 2-1: configuration #1 chosen from 1 choice

nothing exciting here...

the above is the result of "sudo tail -f /var/log/messages" after plugging in and running bcharge (which indicates that it does adjust charge setting)

lsusb never indicates a change in the MaxPower from 100mA, even if i run it when the charge indicator is showing (all 2 secs of it)...

cregmak00 · **How! Do I install bcharge (in english please) -** 05-30-2007, 11:05 PM

Help! I'm new with linux, and it seems to be impossible to find any kind of decent instructions on how to install bcharge. Where can I just find "do this.. do this.." type instructions on how to install this for a blackberry pearl. Please direct to newbie instructions (i don't know how to compile and run scripts). If there is an .exe type install file that would be grrrrrreat too.

Thanks!

rivviepop · 05-31-2007, 02:33 PM

Quote:

Originally Posted by cregmak00

Help! I'm new with linux, and it seems to be impossible to find any kind of decent instructions on how to install bcharge. Where can I just find "do this.. do this.." type instructions on how to install this for a blackberry pearl. Please direct to newbie instructions (i don't know how to compile and run scripts). If there is an .exe type install file that would be grrrrrreat too.

If you run Fedora Core 6:

1) download these files:
http://downloads.sourceforge.net/bar...7&big_mirror=0
http://downloads.sourceforge.net/bar...1&big_mirror=0

2) as 'root' on your machine in the directory you downloaded to, type:

Code:

rpm -Uhv barry-* libbarry-*

3) drink a beer and congratulate yourself on being a nerd.

rivviepop · 05-31-2007, 02:36 PM

FYI: for all you Ubuntu folks having problems, the mailing list indicates it's a problem with your prepackaged kernel. Compiling your own or whatnot 'fixes' your charging problem.

see here (towards the bottom):
http://sourceforge.net/mailarchive/f...me=barry-devel

breakerfall · 05-31-2007, 08:51 PM

ugh, its been soooo long since i 'rolled my own' ...
think 3+ hours on a 486DX2/50 !!!!

Dwaine · 06-11-2007, 08:29 PM

Looks like the new BlackBerry charger module is now in the official kernell

[root@www ~]# btool -l
Blackberry devices found:
Device ID: 0x92ec588. PIN: 205a66cc
[root@www ~]# lsmod
Module Size Used by
berry_charge 8133 0
vfat 16321 0
fat 53877 1 vfat

lib/modules/2.6.21-ARCH/kernel/drivers/usb/misc/berry_charge.ko

Greg must of added the 8800 ID to the module. The computer is charging the 8800 fine.

rivviepop · 06-11-2007, 09:57 PM

Quote:

Originally Posted by breakerfall

ugh, its been soooo long since i 'rolled my own' ...
think 3+ hours on a 486DX2/50 !!!!

I was still running OS/2 on that motherboard.

Oh man, the day I went from 4 up to 8 megs of RAM was I twitterpated....

rivviepop · 06-11-2007, 10:09 PM

Quote:

Originally Posted by Dwaine

Looks like the new BlackBerry charger module is now in the official kernell

As of 2.6.21 it's in the mainline kernel, but...

Quote:

Greg must of added the 8800 ID to the module. The computer is charging the 8800 fine.

...at 100mA, not 500mA (check your lsusb -v output). I was on the email CC from Greg, and the problem with adding the 8100+ to the module for proper detection is that usb-storage conflict (the devices with SD cards *always* present a USB Mass Storage interface, even if you've disabled it on your 8x00 device).

Last I heard (which was awhile ago) he was going to work with the usb-storage people (??) and try and figure something out. That module, though, *should* be working for the 8700 and older devices!

Linux Headquarters - Kernel v2.6.21 /drivers/usb/misc/berry_charge.c

Notice the #define BLACKBERRY 0x0001 -- it doesn't support our newer 0x0006/0x0004 SD-enabled devices. :-/

HuwSy · 06-12-2007, 12:00 AM

hum... im using 2.6.22 but still cant get it to charge. I get

Code:

Bus 002 Device 006: ID 0fca:0001 Research In Motion, Ltd. Blackberry Handheld
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass       255 Vendor Specific Subclass
  bDeviceProtocol       255 Vendor Specific Protocol
  bMaxPacketSize0        64
  idVendor           0x0fca Research In Motion, Ltd.
  idProduct          0x0001 Blackberry Handheld
  bcdDevice            1.04
  iManufacturer           1 
  iProduct                2 
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           46
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           4
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0 
      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
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 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     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
cannot read device status, Operation not permitted (1)

from lsusb -v and dont have any udev rules inplace for it anymore, seeing as bcharge very rarely worked. Do i still need a udev rule for it invoking the kernel module at all? Even loading the module through modprobe does nothing.

rivviepop · 06-12-2007, 12:11 PM

Quote:

Originally Posted by HuwSy

Code:

    MaxPower              500mA

Huh, that lsusb says that the computer has adjusted to 500mA, which means *something* worked. Do this:

1) unplug BB
2) rmmod berry_charge
3) modprobe berry_charge debug=1
4) tail -f /var/log/messages

...now plug in your BB and you should see the debug info of "device detected" blah blah blah. I suspect that the problem is the same as you were having before; the charging indicator on the device isn't staying on, which I guess was an Ubuntu kernel bug?

HuwSy · 06-13-2007, 04:44 PM

After connecting i get the following appear.

Code:

Jun 13 22:38:52 Demon kernel: [ 1146.709787] usb 2-2: new full speed USB device using uhci_hcd and address 8
Jun 13 22:38:53 Demon kernel: [ 1146.883475] usb 2-2: configuration #1 chosen from 1 choice
Jun 13 22:38:53 Demon kernel: [ 1147.428706] usb 2-2: USB disconnect, address 8
Jun 13 22:38:53 Demon kernel: [ 1147.668288] usb 2-2: new full speed USB device using uhci_hcd and address 9
Jun 13 22:38:54 Demon kernel: [ 1147.841747] usb 2-2: configuration #1 chosen from 1 choice
Jun 13 22:38:54 Demon kernel: [ 1148.379182] usb 2-2: USB disconnect, address 9
Jun 13 22:38:54 Demon kernel: [ 1148.618773] usb 2-2: new full speed USB device using uhci_hcd and address 10
Jun 13 22:38:54 Demon kernel: [ 1148.792082] usb 2-2: configuration #1 chosen from 1 choice

then nothing else adds until i remove it and get the following

Code:

Jun 13 22:43:34 Demon kernel: [ 1427.506375] usb 2-2: USB disconnect, address 10

is there any known conflicting kernel modules?

smoosh · 07:03 PM

I too was experiencing the problems that many are describing where the charging icon would stay on for about 2 seconds and then disappear.

I am using Ubuntu 7.04 and a Blackberry 8700r with OS 4.2.

What appeared to be happening was that when bcharge ran, it did indeed set the power output to the appropriate level, but then something else seemed to drop it back down about 2 seconds later.

The work around I found...which is by no means a fix in the strictest sense...was to write a script that runs bcharge every 1 second.

Now I plug in the blackberry, run the script and blammo...a charging blackberry.

My detailed procedure if required is Here

titetanium · 06-26-2007, 11:55 PM

I found out in the kernel mailing list that somewhere in 2.6.20+ kernels, the libusb code changed somewhat. Apparently, if you have usb suspend enabled in the kernel, it will stop charging due to autosuspending. There is a patch that works around this issue by telling the kernel not to autosuspend when blackberries are connected via usb. I'm using it with usb suspend enabled in the patched kernel and it works.

If you need the link, i can't remember exactly how I found the patch, it was through google.

rivviepop · 06-27-2007, 12:15 PM

Quote:

Originally Posted by titetanium

If you need the link, i can't remember exactly how I found the patch, it was through google.

It made it's way onto barry-devel as well, from the linux-usb-devel list.

http://sourceforge.net/mailarchive/f...me=barry-devel

titetanium · 06-27-2007, 06:15 PM

Quote:

Originally Posted by rivviepop

It made it's way onto barry-devel as well, from the linux-usb-devel list.

SourceForge.net: barry-dev