You are not logged in.

Pages: 1

#1 2010-07-28 14:01:55

minimal
Member
From: Quito, Ecuador
Registered: 2009-10-29
Posts: 56

How can I tether my Blackberry over USB cable (to sync info)? [SOLVED]

Firstly, I have to thank all of you for making this such a great community and excellent guide to getting almost anything working on Linux - this is what makes Archlinux the best distro IMHO.  I have hardly ever needed to post anything here because the answers are almost always either in the wiki or the forums. big_smile

Lately though, I received a Blackberry 8310 and wanted to tether it to use its data plan here in Ecuador.  After following http://wiki.archlinux.org/index.php/Blu … GPRS_Howto using a small USB bluetooth adaptor, this has worked well and the connection stays up nicely, though very slow (to be expected).  Blueman is a great program!  Looking at improving my connection speeds (and reducing my latency), I am now trying to get the phone tethered via a USB cable to the phone, rather than over-the-air (Bluetooth).

The problem I am having is that I cannot establish which device exactly is the USB port connecting to?  Before this phone, this worked fine on my Nokia E51 setting the modem to be /dev/ACM0.  On Nokia, I would connect the phone, select PCSuite mode and 'sudo wvdial movistar' or my /etc/ppp/peers/movistar script would work fine.  Blackberry however is a whole different kind of animal.  I connect it with a standard USB cable, select 'no' to mass-storage-mode on the phone, and can see it in lsusb fine but the only device I seem to be able to use is /dev/tty2 but modem not initialising.

How can I be certain which device I am using?  Will post some lsusb and dmesg.log out put when I get home to give you more info.

thanks for any guidance you can give me,

Last edited by minimal (2010-11-16 16:18:48)

|\/|
_________________________________________________________________________________________
Never judge a man until you have walked 1000 miles in his shoes.
..that way you'll be 1000 miles away and you'll have his shoes.

Offline

#2 2010-07-29 02:35:49

minimal
Member
From: Quito, Ecuador
Registered: 2009-10-29
Posts: 56

Re: How can I tether my Blackberry over USB cable (to sync info)? [SOLVED]

Well, haven't got much further here unfortunately, though I have more logs and debug information now:

First, I connect the blackberry to the USB port and run 'lsusb':

Bus 004 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 002 Device 002: ID 0fca:0004 Research In Motion, Ltd. 
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

so I have my blackberry device listed by the looks of things..
I then run (for more info):

peter ~  $  lsusb -v -d 0fca:0004

Bus 002 Device 002: 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.07
  iManufacturer           1 Research In Motion
  iProduct                5 RIM Composite Device
  iSerial                 3 8F606BB12465F80D8C6F4F3CA17D9CC896C5F475
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           97
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           8
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      1 
      bInterfaceProtocol    255 
      iInterface              2 BlackBerry
      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
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x85  EP 5 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     0x06  EP 6 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     0x87  EP 7 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     0x08  EP 8 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      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     0x89  EP 9 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     0x0a  EP 10 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)

/etc/wvdial.conf :

[Dialer defaults]
Modem = /dev/modem
Baud = 115200
Init1 = ATZ
Init2 = ATE0
;Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0

[Dialer movistar]
Modem = /dev/tty2
Init3 = AT+cgdcont=1,"IP","wap.movistar.com.ec"
Phone = *99***1#
Stupid Mode = 1
Username = movistar
Password = movistar

..and the contents of the /etc/ppp/peers/movistar file:

show-password
noauth
#/dev/ttyACM1
# Peter: believe this is the Backberry 8310 device after running 'lsusb':
/dev/rfcomm0
debug
##115200
460800
connect /etc/ppp/peers/movistar-connect
disconnect /etc/ppp/peers/movistar-disconnect
defaultroute
#replacedefaultroute
noipdefault
# Peter: uncommented the following line to debug:
nodetach
usepeerdns
crtscts
local
ipcp-accept-local
#lcp-echo-interval 0
maxfail 10
lcp-echo-failure 0
lcp-echo-interval 0
#lcp-max-configure 0
#lcp-max-failure 10000
#lcp-max-terminate 0
#lcp-restart 30000
novj
nobsdcomp
novjccomp
nopcomp
noaccomp
linkname movistar
mtu 1500
mru 1500
user "movistar"
password "1234"

My /etc/ppp/peers/movistar-connect script :

 #!/bin/sh
exec chat                                               \
        TIMEOUT         5                               \
        ECHO            ON                              \
        ABORT           '\nBUSY\r'                      \
        ABORT           '\nERROR\r'                     \
        ABORT           '\nNO ANSWER\r'                 \
        ABORT           '\nNO CARRIER\r'                \
        ABORT           '\nNO DIALTONE\r'               \
        ABORT           '\nRINGING\r\n\r\nRINGING\r'    \
        ''              \rAT                            \
        TIMEOUT         12                              \
        SAY             "Press CTRL-C to close the connection at any stage!"    \
        SAY             "\ndefining PDP context...\n"   \
        OK              ATH                             \
        OK              ATE1                            \
        OK              'AT+CGDCONT=1,"IP","wap.movistar.com.ec","",0,0'        \
        OK              ATD*99#                         \
        TIMEOUT         22                              \
        SAY             "\nwaiting for connect...\n"    \
        CONNECT         ""                              \
        SAY             "\nConnected." \
        SAY             "\nIf the following ppp negotiations fail,\n"   \
        SAY             "try restarting the phone.\n"

my /var/log/dmesg.log :

Jul 29 21:11:11 el-duro kernel: ACPI: EC: GPE storm detected, transactions will use polling mode
Jul 29 21:11:13 el-duro logger: ACPI action undefined: BAT1
Jul 29 21:11:15 el-duro laptop-mode: Laptop mode
Jul 29 21:11:15 el-duro laptop-mode: disabled, not active
Jul 29 21:11:52 el-duro kernel: usb 3-1: new full speed USB device using uhci_hcd and address 2
Jul 29 21:11:52 el-duro kernel: Initializing USB Mass Storage driver...
Jul 29 21:11:52 el-duro kernel: scsi2 : usb-storage 3-1:1.1
Jul 29 21:11:52 el-duro kernel: usbcore: registered new interface driver usb-storage
Jul 29 21:11:52 el-duro kernel: USB Mass Storage support registered.
Jul 29 21:11:53 el-duro kernel: scsi 2:0:0:0: Direct-Access     RIM      Blackberry SD    0001 PQ: 0 ANSI: 4 CCS
Jul 29 21:11:53 el-duro kernel: sd 2:0:0:0: Attached scsi generic sg2 type 0
Jul 29 21:11:53 el-duro kernel: sd 2:0:0:0: [sdb] Attached SCSI removable disk
Jul 29 21:12:04 el-duro dnsmasq[2316]: reading /etc/resolv.conf
Jul 29 21:12:04 el-duro dnsmasq[2316]: using nameserver 208.67.222.222#53
Jul 29 21:12:04 el-duro dnsmasq[2316]: ignoring nameserver 127.0.0.1 - local interface

Here are my logs..
=============
/var/log/kernel.log :

Jul 29 21:11:11 el-duro kernel: ACPI: EC: GPE storm detected, transactions will use polling mode
Jul 29 21:11:52 el-duro kernel: usb 3-1: new full speed USB device using uhci_hcd and address 2
Jul 29 21:11:52 el-duro kernel: Initializing USB Mass Storage driver...
Jul 29 21:11:52 el-duro kernel: scsi2 : usb-storage 3-1:1.1
Jul 29 21:11:52 el-duro kernel: usbcore: registered new interface driver usb-storage
Jul 29 21:11:52 el-duro kernel: USB Mass Storage support registered.
Jul 29 21:11:53 el-duro kernel: scsi 2:0:0:0: Direct-Access     RIM      Blackberry SD    0001 PQ: 0 ANSI: 4 CCS
Jul 29 21:11:53 el-duro kernel: sd 2:0:0:0: Attached scsi generic sg2 type 0
Jul 29 21:11:53 el-duro kernel: sd 2:0:0:0: [sdb] Attached SCSI removable disk

/var/log/messages.log :

Jul 29 21:11:11 el-duro kernel: ACPI: EC: GPE storm detected, transactions will use polling mode
Jul 29 21:11:13 el-duro logger: ACPI action undefined: BAT1
Jul 29 21:11:15 el-duro laptop-mode: Laptop mode
Jul 29 21:11:15 el-duro laptop-mode: disabled, not active
Jul 29 21:11:52 el-duro kernel: usb 3-1: new full speed USB device using uhci_hcd and address 2
Jul 29 21:11:52 el-duro kernel: Initializing USB Mass Storage driver...
Jul 29 21:11:52 el-duro kernel: scsi2 : usb-storage 3-1:1.1
Jul 29 21:11:52 el-duro kernel: usbcore: registered new interface driver usb-storage
Jul 29 21:11:52 el-duro kernel: USB Mass Storage support registered.
Jul 29 21:11:53 el-duro kernel: scsi 2:0:0:0: Direct-Access     RIM      Blackberry SD    0001 PQ: 0 ANSI: 4 CCS
Jul 29 21:11:53 el-duro kernel: sd 2:0:0:0: Attached scsi generic sg2 type 0
Jul 29 21:11:53 el-duro kernel: sd 2:0:0:0: [sdb] Attached SCSI removable disk
Jul 29 21:12:04 el-duro dnsmasq[2316]: reading /etc/resolv.conf
Jul 29 21:12:04 el-duro dnsmasq[2316]: using nameserver 208.67.222.222#53
Jul 29 21:12:04 el-duro dnsmasq[2316]: ignoring nameserver 127.0.0.1 - local interface

/var/log/everything.log :

Jul 29 21:11:11 el-duro kernel: ACPI: EC: GPE storm detected, transactions will use polling mode
Jul 29 21:11:13 el-duro logger: ACPI action undefined: BAT1
Jul 29 21:11:15 el-duro laptop-mode: Laptop mode
Jul 29 21:11:15 el-duro laptop-mode: disabled, not active
Jul 29 21:11:52 el-duro kernel: usb 3-1: new full speed USB device using uhci_hcd and address 2
Jul 29 21:11:52 el-duro load-modules.sh: 'usb:v0FCAp0004d0107dc00dsc00dp00icFFisc01ipFF' is not a valid module or alias name
Jul 29 21:11:52 el-duro kernel: Initializing USB Mass Storage driver...
Jul 29 21:11:52 el-duro kernel: scsi2 : usb-storage 3-1:1.1
Jul 29 21:11:52 el-duro kernel: usbcore: registered new interface driver usb-storage
Jul 29 21:11:52 el-duro kernel: USB Mass Storage support registered.
Jul 29 21:11:53 el-duro kernel: scsi 2:0:0:0: Direct-Access     RIM      Blackberry SD    0001 PQ: 0 ANSI: 4 CCS
Jul 29 21:11:53 el-duro kernel: sd 2:0:0:0: Attached scsi generic sg2 type 0
Jul 29 21:11:53 el-duro kernel: sd 2:0:0:0: [sdb] Attached SCSI removable disk
Jul 29 21:12:04 el-duro dnsmasq[2316]: reading /etc/resolv.conf
Jul 29 21:12:04 el-duro dnsmasq[2316]: using nameserver 208.67.222.222#53
Jul 29 21:12:04 el-duro dnsmasq[2316]: ignoring nameserver 127.0.0.1 - local interface

Maybe the blackberry required 'usb_modeswitch' - though I could not work out how to use this command sad

Any ideas out there?  Is there a simple way for me to probe USB devices in use?  As far as I can tell it IS /dev/tty2 but I need to confirm this. 

Many thanks,

Last edited by minimal (2010-07-30 14:55:19)

|\/|
_________________________________________________________________________________________
Never judge a man until you have walked 1000 miles in his shoes.
..that way you'll be 1000 miles away and you'll have his shoes.

Offline

#3 2010-08-10 02:54:43

minimal
Member
From: Quito, Ecuador
Registered: 2009-10-29
Posts: 56

Re: How can I tether my Blackberry over USB cable (to sync info)? [SOLVED]

I was thinking about this lately..  If Nokia works perfectly and Blackberry does not, I can only put this down to Blackberry being such a difficult animal to interoperate with Linux.  When I try to connect out via the USB cable, the blackberry phone appears to reboot.  Has anyone managed to get this working?

|\/|
_________________________________________________________________________________________
Never judge a man until you have walked 1000 miles in his shoes.
..that way you'll be 1000 miles away and you'll have his shoes.

Offline

#4 2010-08-10 03:13:20

nixpunk
Member
Registered: 2009-11-23
Posts: 271

Re: How can I tether my Blackberry over USB cable (to sync info)? [SOLVED]

To be honest, I looked into this briefly a few years back and didn't find much to go on.  I am certainly curious to see how far you can get, but ultimately, I wish I could offer more.

Offline

#5 2010-08-10 04:59:21

oiad
Member
Registered: 2010-03-02
Posts: 22

Re: How can I tether my Blackberry over USB cable (to sync info)? [SOLVED]

Are you using any program like NetDirect's Barry?  I am using a cdma network through usb.

Offline

#6 2010-08-11 20:19:25

minimal
Member
From: Quito, Ecuador
Registered: 2009-10-29
Posts: 56

Re: How can I tether my Blackberry over USB cable (to sync info)? [SOLVED]

I actually succeeded in syncing via usb cable using the recent Blackberry wiki article here: http://wiki.archlinux.org/index.php/Blackberry
Since that time, I have found a much simpler method.  In keeping with the KISS philosophy - download Google Sync for your phone from here: http://www.google.com/mobile/ and select your phone.  Your google Calendar and gmail contacts will be synced automatically on the hour after manually syncing the first time.  Even better, duplicate contacts are allowed on both the phone and gmail contacts so there's no danger of overwriting precious contact information! smile

@oiad: As for connecting out over the USB cable to my mobile operator's GPRS data plan, how did you manage to set this up with CDMA?  Which version of Barry did you use and what model is your blackberry and can I see your config files please?  I am just using ppp and wvdial at the moment trying to tether using a USB cable. 

thanks for sharing your experiences with this,

Last edited by minimal (2010-08-11 20:52:49)

|\/|
_________________________________________________________________________________________
Never judge a man until you have walked 1000 miles in his shoes.
..that way you'll be 1000 miles away and you'll have his shoes.

Offline

Pages: 1

Board footer

Powered by FluxBB