headers
John Priddy | 4 Jun 2008 18:21
Picon
Favicon

Re: [patch included] Re: barry working under fc9?

Sorry about taking so long to get back to you about the patch.  I just 
grabbed everything from cvs and ran a generic configure, make, and 
everything seems to compile fine.  After a make install, when im running 
'btool' i get the following:

[jpriddy <at> boatanchor ~]$ sudo btool
Blackberry devices found:
Device ID: 0xXXXXXX. PIN: XXXXXX, Description: RIM 8800 Series Colour 
CDMA Handheld
Using device (PIN): XXXXX
[jpriddy <at> boatanchor ~]$

So it looks like it can see the device.  Other than not seing the 'not 
enough power' message on the LCD, is there a way to check that its 
sending out a charge to it?  I remember seeing something along the lines 
of 'bcharge sets BLAH'..

[jpriddy <at> boatanchor ~]$ sudo cat /var/log/messages | grep bcharge
[jpriddy <at> boatanchor ~]$

I went back and tried to recompile with opensync and gui, but you said 
those shouldnt work anyway right?

[jpriddy <at> boatanchor barry]$ ./configure --enable-gui 
--enable-opensync-plugin
--snip--
[jpriddy <at> boatanchor barry]$ make
--snip--
/bin/sh ../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I.. -I/home/jpriddy/apps/barry/cvs/barry -I/usr/include/opensync-1.0
(Continue reading)

Permalink | Reply |
headers
Chris Frey | 5 Jun 2008 00:30

Re: [patch included] Re: barry working under fc9?

On Wed, Jun 04, 2008 at 12:21:14PM -0400, John Priddy wrote:
> [jpriddy <at> boatanchor ~]$ sudo btool
> Blackberry devices found:
> Device ID: 0xXXXXXX. PIN: XXXXXX, Description: RIM 8800 Series Colour 
> CDMA Handheld
> Using device (PIN): XXXXX
> [jpriddy <at> boatanchor ~]$
> 
> 
> So it looks like it can see the device.

Excellent.

> Other than not seing the 'not 
> enough power' message on the LCD, is there a way to check that its 
> sending out a charge to it?  I remember seeing something along the lines 
> of 'bcharge sets BLAH'..

You can use the lsusb -v command to check the MaxPower field for your
Blackberry.  If it says 500mA, you're good.

> I went back and tried to recompile with opensync and gui, but you said 
> those shouldnt work anyway right?
> 
> 
> [jpriddy <at> boatanchor barry]$ ./configure --enable-gui 
> --enable-opensync-plugin
> --snip--
> [jpriddy <at> boatanchor barry]$ make
> --snip--
(Continue reading)

Permalink | Reply |
headers
John Priddy | 5 Jun 2008 03:35
Picon
Favicon

Re: [patch included] Re: barry working under fc9?

Thanks -- I can live without the opensync/gui for now, but it looks like 
it still may not be setting the right charge when plugging it in:

Bus 004 Device 004: ID 0fca:0006 Research In Motion, Ltd.
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x0fca Research In Motion, Ltd.
  idProduct          0x0006
  bcdDevice            1.06
  iManufacturer           1 Research In Motion
  iProduct                4 RIM Mass Storage Device
  iSerial                 3 97ECDA7E1D98FF58D46EA881D3A5C975F3091E88
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              100mA
    Interface Descriptor:
(Continue reading)

Permalink | Reply |
headers
Chris Frey | 5 Jun 2008 03:43

Re: [patch included] Re: barry working under fc9?

On Wed, Jun 04, 2008 at 09:35:28PM -0400, John Priddy wrote:
> Thanks -- I can live without the opensync/gui for now, but it looks like 
> it still may not be setting the right charge when plugging it in:

The backup GUI should work in Fedora 9.  Just not opensync without getting
opensync 0.22 packages.

>     MaxPower              100mA

In your previous email, you mentioned that you used "make install".
I'm assuming that you haven't updated your udev rules in /etc/udev/rules.d.

Try running bcharge from the command line, and see if MaxPower changes.
If it does, then you just need udev configured correctly for your system.

For Fedora systems, do the following from the source tree:

	cp udev/10-blackberry.rules /etc/udev/rules.d/
	cp udev/10-blackberry.perms /etc/security/console.perms.d/
	cp modprobe/blacklist-berry_charge /etc/modprobe.d/

- Chris

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
Permalink | Reply |
headers
John Priddy | 5 Jun 2008 04:12
Picon
Favicon

Re: [patch included] Re: barry working under fc9?

I dont know if its something I did wrong when building, or if its some 
variable that maybe should be passed on to the files under ./udev (i 
just took the defaults of /usr/local/), but as an FYI I had to change:

RUN="/usr/sbin/bcharge -p %p

To point to:
"/usr/local/sbin"

Now the charging is working perfectly.  I decided to compile the gui as 
well while I was at it, and that also appears to work.

Thanks again for your help and work -- its great to have support for this.

John

Chris Frey wrote:
> On Wed, Jun 04, 2008 at 09:35:28PM -0400, John Priddy wrote:
>   
>> Thanks -- I can live without the opensync/gui for now, but it looks like 
>> it still may not be setting the right charge when plugging it in:
>>     
>
> The backup GUI should work in Fedora 9.  Just not opensync without getting
> opensync 0.22 packages.
>
>
>   
>>     MaxPower              100mA
>>
(Continue reading)

Permalink | Reply |

Gmane