i should be working (but i'm fixing my computer).

I wanted to get my blackberry working in Linux on the Gateway LT3103u; and then I wanted to get it working via bluetooth.

...

In that order, since I have had the Tour working via USB and "Barry" on my Sony laptop, but not via bluetooth.

On the one hand, a wired connection will keep the Blackberry charged; on the other hand, a holstered Blackberry is a lot more convenient when moving around with a connected laptop.

Installing the "barry" packages from the OpenSUSE build service worked out fine and there is only one other step to remember -- the /etc/resolv.conf has to be modified to add the DNS entries. You can either run Barry and write down the DNS servers reported when you connect (and use those) or set up a resolv.conf with generic DNS servers, such as OpenDNS.

There is probably some other preferable way to do this, because changes to resolv.conf prevent some other automated changes. But, I don't know what that "other" way is. Anyway, works fine for me.

Now back to the Bluetooth option. Well, considering that the Sony>8703e bluetooth connection was working fine, I was not expecting to do anything other than change the MAC address of the bluetooth phone.

Hahaha.

I think the main problem is that I removed some icons and therefore forgot the method with which I used to make the connection. That is, I would run kbluetooth4 and then the bluetooth script(s) I reference in my wiki at daltrey.org/tw.

In addition, I had connected the Tour via the same dongle but on the other computer. Here's an issue I guess. I could read the connection (eg. sdptools browse) but I would get an input/output error when I tried to connect.

I tried hcitool, but I don't have an hci.conf or bluepin.conf, so I ran into commandline blues as it were. I then decided to remove the kde3 kbluetooth. This was probably an unnecessary step, but in any event, it caused me to realize I had not been running kbluetooth4.

Sooo. Connecting was now easy. I removed the earlier connection from the blackberry, put kbluetooth4 in discover mode and ran a connection search on the blackberry. Not only connected, but also put in to "controlled a/v mode" -- whatever that is.

But ... I couldn't get my bberry script to run. And the problem I have always had was that if it didn't connect, then rfcomm0 would get tied up and the script wouldn't run unless I re-booted the computer. Sheesh. So, I did some more research, with the thought in mind that if I have a connection to the blackberry, maybe I can simply run a pppd call separately, without worrying about my existing scripts.

This is when I discovered two useful commands: rfcomm release 0 and rfcomm connect 0. This utilized my existing (see daltrey.org/tw) rfcomm0.conf. I had previously used sdptools browse to learn the MAC of the Blackberry Tour, and had put that into the rfcomm.conf. So, by running rfcomm connect 0, I was able to connect in modem mode.

Now the good thing here is that when rfcomm would lock up from my existing script, "rfcomm release 0" unlocks it, so no more rebooting to clear the connection. Yay!

It occurred to me that once connected in modem mode, I could probably run my "bberry" script connection the same way I run the "barry" connection when connected via USB. So, I ran "pppd call bberry" and sure enough, successful connection.

But, some additional refinement is necessary here. I'm running "rfcomm connect 0" from an su konsole. When running, it pauses with a prompt "CTRL-C for hangup". So, I have to open a second su konsole to run "pppd call bberry". Then, interestingly, "CTRL-C" in the bberry window will also hang up rfcomm in the rfcomm window.

So, some launch icons and a bit of refinement relative to the hangup procedure will improve the "elegance" of the solution, but in any event. the Tour is now connecting via bluetooth in Linux (on the Sony). I assume this will all duplicate to the Gateway, but haven't done so yet.

Thank you for visiting and have a pleasant tomorrow.

ADDITIONAL:

So, then I wondered ... if I am simply setting up rfcomm0 as a dialup modem, could I use Kppp to make the connection?

Pages: 1· 2