Re: [Barry-devel] Blackberry 8830 on Ubuntu 7.10

2007-11-09 Thread Simon Ruggier 
On 11/9/07, Chris Frey [EMAIL PROTECTED] wrote:
 On Fri, Nov 09, 2007 at 10:11:24AM +0100, Niels De Vos wrote:
  On 11/8/07, Chris Frey [EMAIL PROTECTED] wrote:
   rmmod is not enough to prevent the conflict.  You need to rename the
   berry_charge module under /lib/modules before plugging in your device.
 
  Or add the following line to /etc/modprobe.conf:
  install berry_charge /bin/true
 
  This prevents modprobe loading the module. modprobe executes /bin/true 
  instead.

 Thanks!  That's so smooth, I'm tempted to put it right in the binary
 package.  That would save a lot of trouble.

Err, As far as I know, both of these solutions are hacks, and the
proper way to do it would be to create a file like
/etc/modprobe.d/blacklist-berry_charge containing:

# conflicts with barry bcharge utility
blacklist berry_charge

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] Blackberry 8830 on Ubuntu 7.10

2007-11-09 Thread Niels de Vos 
On 11/9/07, Simon Ruggier [EMAIL PROTECTED] wrote:
 On 11/9/07, Chris Frey [EMAIL PROTECTED] wrote:
  On Fri, Nov 09, 2007 at 10:11:24AM +0100, Niels De Vos wrote:
   On 11/8/07, Chris Frey [EMAIL PROTECTED] wrote:
rmmod is not enough to prevent the conflict.  You need to rename the
berry_charge module under /lib/modules before plugging in your device.
  
   Or add the following line to /etc/modprobe.conf:
   install berry_charge /bin/true
  
   This prevents modprobe loading the module. modprobe executes /bin/true 
   instead.
 
  Thanks!  That's so smooth, I'm tempted to put it right in the binary
  package.  That would save a lot of trouble.

 Err, As far as I know, both of these solutions are hacks, and the
 proper way to do it would be to create a file like
 /etc/modprobe.d/blacklist-berry_charge containing:

 # conflicts with barry bcharge utility
 blacklist berry_charge

You're correct, that looks even nicer :)

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] Blackberry 8830 on Ubuntu 7.10

2007-11-09 Thread Chris Frey 
On Fri, Nov 09, 2007 at 03:24:38PM +0100, Niels de Vos wrote:
 On 11/9/07, Simon Ruggier [EMAIL PROTECTED] wrote:
  Err, As far as I know, both of these solutions are hacks, and the
  proper way to do it would be to create a file like
  /etc/modprobe.d/blacklist-berry_charge containing:
 
  # conflicts with barry bcharge utility
  blacklist berry_charge
 
 You're correct, that looks even nicer :)


Thanks Simon and Niels.  Consider this added to the next binary
package release. :-)

- Chris


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] Blackberry 8830 on Ubuntu 7.10

2007-11-04 Thread Niels De Vos 
Hi all,

as far as I know the berry_charge driver/module conflicts with the
bcharge-tool. This might prevent other barry-tools from functioning
too.

Cheers,
Niels

On 11/4/07, Zach Stern [EMAIL PROTECTED] wrote:
 I have the same issue, and I can't use the sync tool either. I also have an 
 8830, ubuntu 7.10.

 I had the same issue on 7.04 as well.
 Sent from my Verizon Wireless BlackBerry

 -Original Message-
 From: Arvind Kalyan [EMAIL PROTECTED]

 Date: Sat, 3 Nov 2007 17:11:30
 To:barry-devel@lists.sourceforge.net
 Subject: [Barry-devel] Blackberry 8830 on Ubuntu 7.10


 Hi,

  I have installed barry from cvs (version .10).

 When I tried to invoke bcharge the power settings remain at 100mA (the device 
 id doesnt change to 0004. it remains at 0fca:0006).

 Here are the details. Please let me know if you would need further 
 information.


 OS: Ubuntu 7.10
 Ph: Blackberry 8830 / Verizon Wireless

 # uname -a
 Linux arvind-r61 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 
 GNU/Linux

 # lsusb
 Bus 001 Device 001: ID :
 Bus 005 Device 001: ID :
 Bus 003 Device 008: ID 0fca:0006 Research In Motion, Ltd.
 Bus 003 Device 001: ID :
 Bus 002 Device 001: ID :
 Bus 004 Device 001: ID :
 Bus 006 Device 001: ID :
 Bus 007 Device 001: ID :
 #

 # lsusb -v -d 0fca:0006

 Bus 003 Device 008: 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 5E1615F1623EF31A6519F809EE97BB1
 607FA0ECD
  bNumConfigurations 1
  Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength 32
  bNumInterfaces 1
  bConfigurationValue 1
  iConfiguration 0
  bmAttributes 0x80
  (Bus Powered)
  MaxPower 100mA
  Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber 0
  bAlternateSetting 0
  bNumEndpoints 2
  bInterfaceClass 8 Mass Storage
  bInterfaceSubClass 6 SCSI
  bInterfaceProtocol 80 Bulk (Zip)
  iInterface 4 RIM Mass Storage Device
  Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x86 EP 6 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 0x07 EP 7 OUT
  bmAttributes 2
  Transfer Type Bulk
  Synch Type None
  Usage Type Data
  wMaxPacketSize 0x0040 1x 64 bytes
  bInterval 0
 Device Status: 0x
  (Bus Powered)


 # grep 0fca /etc/udev/rules.d/*
 /etc/udev/rules.d/10-blackberry.rules:BUS==usb, SUBSYSTEM==usb_device, 
 ACTION==add, SYSFS{idVendor}==0fca, SYSFS{idProduct}==0001, 
 SYMLINK+=bb-%k, RUN=/usr/sbin/bcharge -p %p

 /etc/udev/rules.d/10-blackberry.rules:BUS==usb, SUBSYSTEM==usb_device, 
 ACTION==add, SYSFS{idVendor}==0fca, SYSFS{idProduct}==0006, 
 RUN=/usr/sbin/bcharge

 /etc/udev/rules.d/10-blackberry.rules:BUS==usb, SUBSYSTEM==usb_device, 
 ACTION==add, SYSFS{idVendor}==0fca, SYSFS{idProduct}==0004, 
 SYMLINK+=bb-%k, RUN=/usr/sbin/bcharge -p %p

 /etc/udev/rules.d/99-barry-perms:SYSFS{idVendor}==0fca, 
 SYSFS{idProduct}==0006, GROUP=barry, MODE=0660

 /etc/udev/rules.d/99-xmblackberry.rules:SUBSYSTEM==usb_device, 
 SYSFS{idVendor}==0fca, SYSFS{idProduct}==0006, ACTION==add, 
 RUN+=/bin/chown --reference=/dev/console $env{DEVNAME}

 #

 I have tried the following:

 1. Unload usb_storage. connect phone. Run bcharge. Run bcharge -o.
 2. Unload usb_storage. load berry_charge. Connect phone. Run bcharge.
 3. Unload usb_storage. load berry_charge. Connect phone. Run bcharge. Run 
 bcharge -o
 4. Unload usb_storage. load berry_charge. Connect phone. Unload usb_storage. 
 Run bcharge.
 5. Download 2.6.23 kernel from
 kernel.org http://kernel.org/  and compile with /boot/config-`uname -r`. 
 Tried 1,2,3,4 as above
 6. Download ubuntu kernel 2.6.22-9 and used current config, and tried out 
 1,2,3,4 as above.


 This is what happens each time:

 # dmesg
 [ 4140.328000] usbcore: deregistering interface driver usb-storage
 [ 4150.16] usb 3-1: new full speed USB device using uhci_hcd and address 9
 [ 4150.324000] usb 3-1: configuration #1 chosen from 1 choice
 [ 4150.356000] Initializing USB Mass Storage driver...
 [ 4150.356000 ] scsi10 : SCSI emulation for USB Mass Storage devices
 [ 4150.356000] usb-storage: device found at 9
 [ 4150.356000] usb-storage: waiting for device to settle before scanning
 [ 4150.356000] usbcore: registered new interface driver usb-storage
 [ 4150.356000] USB Mass Storage support registered.
 [ 4150.628000] usb 3-1: usbfs: interface 0 claimed by usb-storage while 
 'bcharge' sets config #1
 [ 4150.74] usb 3-1: reset full speed USB device using uhci_hcd and 
 address 9


 Or,

 # rmmod usb-storage

Re: [Barry-devel] Blackberry 8830 on Ubuntu 7.10

2007-11-04 Thread Arvind Kalyan 
On 11/4/07, Niels De Vos [EMAIL PROTECTED] wrote:

 Hi all,

 as far as I know the berry_charge driver/module conflicts with the
 bcharge-tool. This might prevent other barry-tools from functioning
 too.


rmmod berry_charge  usb-storage
followed by the plugging/running bcharge etc, doesn't seem to work either.
usb-storage successfully claims the blackberry to itself and doesn't let
bcharge do anything. As seen from the dmesg.

I wonder if anyone has a ubuntu 7.10 working with blackberry 8830 for
verizon broadband access connect.

Cheers,
 Niels


Thanks

On 11/4/07, Zach Stern [EMAIL PROTECTED] wrote:
  I have the same issue, and I can't use the sync tool either. I also have
 an 8830, ubuntu 7.10.
 
  I had the same issue on 7.04 as well.
  Sent from my Verizon Wireless BlackBerry
 
  -Original Message-
  From: Arvind Kalyan [EMAIL PROTECTED]
 
  Date: Sat, 3 Nov 2007 17:11:30
  To:barry-devel@lists.sourceforge.net
  Subject: [Barry-devel] Blackberry 8830 on Ubuntu 7.10
 
 
  Hi,
 
   I have installed barry from cvs (version .10).
 
  When I tried to invoke bcharge the power settings remain at 100mA (the
 device id doesnt change to 0004. it remains at 0fca:0006).
 
  Here are the details. Please let me know if you would need further
 information.
 
 
  OS: Ubuntu 7.10
  Ph: Blackberry 8830 / Verizon Wireless
 
  # uname -a
  Linux arvind-r61 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007
 i686 GNU/Linux
 
  # lsusb
  Bus 001 Device 001: ID :
  Bus 005 Device 001: ID :
  Bus 003 Device 008: ID 0fca:0006 Research In Motion, Ltd.
  Bus 003 Device 001: ID :
  Bus 002 Device 001: ID :
  Bus 004 Device 001: ID :
  Bus 006 Device 001: ID :
  Bus 007 Device 001: ID :
  #
 
  # lsusb -v -d 0fca:0006
 
  Bus 003 Device 008: 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 5E1615F1623EF31A6519F809EE97BB1
  607FA0ECD
   bNumConfigurations 1
   Configuration Descriptor:
   bLength 9
   bDescriptorType 2
   wTotalLength 32
   bNumInterfaces 1
   bConfigurationValue 1
   iConfiguration 0
   bmAttributes 0x80
   (Bus Powered)
   MaxPower 100mA
   Interface Descriptor:
   bLength 9
   bDescriptorType 4
   bInterfaceNumber 0
   bAlternateSetting 0
   bNumEndpoints 2
   bInterfaceClass 8 Mass Storage
   bInterfaceSubClass 6 SCSI
   bInterfaceProtocol 80 Bulk (Zip)
   iInterface 4 RIM Mass Storage Device
   Endpoint Descriptor:
   bLength 7
   bDescriptorType 5
   bEndpointAddress 0x86 EP 6 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 0x07 EP 7 OUT
   bmAttributes 2
   Transfer Type Bulk
   Synch Type None
   Usage Type Data
   wMaxPacketSize 0x0040 1x 64 bytes
   bInterval 0
  Device Status: 0x
   (Bus Powered)
 
 
  # grep 0fca /etc/udev/rules.d/*
  /etc/udev/rules.d/10-blackberry.rules:BUS==usb,
 SUBSYSTEM==usb_device, ACTION==add, SYSFS{idVendor}==0fca,
 SYSFS{idProduct}==0001, SYMLINK+=bb-%k, RUN=/usr/sbin/bcharge -p %p
 
  /etc/udev/rules.d/10-blackberry.rules:BUS==usb,
 SUBSYSTEM==usb_device, ACTION==add, SYSFS{idVendor}==0fca,
 SYSFS{idProduct}==0006, RUN=/usr/sbin/bcharge
 
  /etc/udev/rules.d/10-blackberry.rules:BUS==usb,
 SUBSYSTEM==usb_device, ACTION==add, SYSFS{idVendor}==0fca,
 SYSFS{idProduct}==0004, SYMLINK+=bb-%k, RUN=/usr/sbin/bcharge -p %p
 
  /etc/udev/rules.d/99-barry-perms:SYSFS{idVendor}==0fca,
 SYSFS{idProduct}==0006, GROUP=barry, MODE=0660
 
  /etc/udev/rules.d/99-xmblackberry.rules:SUBSYSTEM==usb_device,
 SYSFS{idVendor}==0fca, SYSFS{idProduct}==0006, ACTION==add,
 RUN+=/bin/chown --reference=/dev/console $env{DEVNAME}
 
  #
 
  I have tried the following:
 
  1. Unload usb_storage. connect phone. Run bcharge. Run bcharge -o.
  2. Unload usb_storage. load berry_charge. Connect phone. Run bcharge.
  3. Unload usb_storage. load berry_charge. Connect phone. Run bcharge.
 Run bcharge -o
  4. Unload usb_storage. load berry_charge. Connect phone. Unload
 usb_storage. Run bcharge.
  5. Download 2.6.23 kernel from
  kernel.org http://kernel.org/  and compile with /boot/config-`uname
 -r`. Tried 1,2,3,4 as above
  6. Download ubuntu kernel 2.6.22-9 and used current config, and tried
 out 1,2,3,4 as above.
 
 
  This is what happens each time:
 
  # dmesg
  [ 4140.328000] usbcore: deregistering interface driver usb-storage
  [ 4150.16] usb 3-1: new full speed USB device using uhci_hcd and
 address 9
  [ 4150.324000] usb 3-1: configuration #1 chosen from 1 choice
  [ 4150.356000] Initializing USB Mass Storage driver...
  [

Re: [Barry-devel] Blackberry 8830 on Ubuntu 7.10

2007-11-03 Thread Zach Stern 
I have the same issue, and I can't use the sync tool either. I also have an 
8830, ubuntu 7.10.

I had the same issue on 7.04 as well.
Sent from my Verizon Wireless BlackBerry

-Original Message-
From: Arvind Kalyan [EMAIL PROTECTED]

Date: Sat, 3 Nov 2007 17:11:30 
To:barry-devel@lists.sourceforge.net
Subject: [Barry-devel] Blackberry 8830 on Ubuntu 7.10


Hi,

    I have installed barry from cvs (version .10). 

When I tried to invoke bcharge the power settings remain at 100mA (the device 
id doesnt change to 0004. it remains at 0fca:0006).

Here are the details. Please let me know if you would need further information. 


OS: Ubuntu 7.10
Ph: Blackberry 8830 / Verizon Wireless

# uname -a
Linux arvind-r61 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 
GNU/Linux

# lsusb
Bus 001 Device 001: ID :  
Bus 005 Device 001: ID :  
Bus 003 Device 008: ID 0fca:0006 Research In Motion, Ltd. 
Bus 003 Device 001: ID :  
Bus 002 Device 001: ID :  
Bus 004 Device 001: ID :  
Bus 006 Device 001: ID :  
Bus 007 Device 001: ID :  
#

# lsusb -v -d 0fca:0006

Bus 003 Device 008: 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 5E1615F1623EF31A6519F809EE97BB1 
607FA0ECD 
  bNumConfigurations  1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength   32
    bNumInterfaces  1
    bConfigurationValue 1 
    iConfiguration  0 
    bmAttributes 0x80
  (Bus Powered)
    MaxPower  100mA
    Interface Descriptor:
  bLength 9
  bDescriptorType 4 
  bInterfaceNumber    0
  bAlternateSetting   0
  bNumEndpoints   2
  bInterfaceClass 8 Mass Storage
  bInterfaceSubClass  6 SCSI
  bInterfaceProtocol 80 Bulk (Zip) 
  iInterface  4 RIM Mass Storage Device
  Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x86  EP 6 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 0x07  EP 7 OUT
    bmAttributes    2
  Transfer Type    Bulk
  Synch Type   None 
  Usage Type   Data
    wMaxPacketSize 0x0040  1x 64 bytes
    bInterval   0
Device Status: 0x
  (Bus Powered)


# grep 0fca /etc/udev/rules.d/* 
/etc/udev/rules.d/10-blackberry.rules:BUS==usb, SUBSYSTEM==usb_device, 
ACTION==add, SYSFS{idVendor}==0fca, SYSFS{idProduct}==0001, 
SYMLINK+=bb-%k, RUN=/usr/sbin/bcharge -p %p 

/etc/udev/rules.d/10-blackberry.rules:BUS==usb, SUBSYSTEM==usb_device, 
ACTION==add, SYSFS{idVendor}==0fca, SYSFS{idProduct}==0006, 
RUN=/usr/sbin/bcharge 

/etc/udev/rules.d/10-blackberry.rules:BUS==usb, SUBSYSTEM==usb_device, 
ACTION==add, SYSFS{idVendor}==0fca, SYSFS{idProduct}==0004, 
SYMLINK+=bb-%k, RUN=/usr/sbin/bcharge -p %p 

/etc/udev/rules.d/99-barry-perms:SYSFS{idVendor}==0fca, 
SYSFS{idProduct}==0006, GROUP=barry, MODE=0660

/etc/udev/rules.d/99-xmblackberry.rules:SUBSYSTEM==usb_device, 
SYSFS{idVendor}==0fca, SYSFS{idProduct}==0006, ACTION==add, 
RUN+=/bin/chown --reference=/dev/console $env{DEVNAME} 

#

I have tried the following:

1. Unload usb_storage. connect phone. Run bcharge. Run bcharge -o.
2. Unload usb_storage. load berry_charge. Connect phone. Run bcharge. 
3. Unload usb_storage. load berry_charge. Connect phone. Run bcharge. Run 
bcharge -o 
4. Unload usb_storage. load berry_charge. Connect phone. Unload usb_storage. 
Run bcharge. 
5. Download 2.6.23 kernel from 
kernel.org http://kernel.org/  and compile with /boot/config-`uname -r`. 
Tried 1,2,3,4 as above 
6. Download ubuntu kernel 2.6.22-9 and used current config, and tried out 
1,2,3,4 as above.


This is what happens each time:

# dmesg
[ 4140.328000] usbcore: deregistering interface driver usb-storage 
[ 4150.16] usb 3-1: new full speed USB device using uhci_hcd and address 9
[ 4150.324000] usb 3-1: configuration #1 chosen from 1 choice
[ 4150.356000] Initializing USB Mass Storage driver...
[ 4150.356000 ] scsi10 : SCSI emulation for USB Mass Storage devices
[