Bluetooth On Opie?

[Harlequin]

Has anyone got bluetooth working on 3.5.2 w/ opie 1.1.7 on collie?  If so could you post a basic howto?

I just got a belkin bluetooth card.  I was expecting a similar setup to the irda but I don't seem to be getting anywhere.  Card is picked up as a compaq bluetooth sleeve.

New to bluetooth and I'm not sure where to go from here.  Ultimate goal is to dial out through my phone.

Thanks,

Harry.

[EdbO]

Hello Harry,

I have a Billionton bluetoothcard and it works great! I have done the following to get my card working:

1. install package "setserial"
2. exec. setserial /dev/ttyS3 baud_base 921600
3. exec. modprobe hci_uart
4. exec. hciattach /dev/ttyS3 bcsp  <--- maybe you have to change this
5. exec. hciconfig hci0 up

Now you have your bluetoothcard working. STFW and search this forum to get a connection to your phone. You can also start at the BlueZ website

[maslovsky]

Belkin bluetooth card will not work without a kernel patch, which allows to set unusual baude rates, such as 100000. Tis patch is included in Cacko ROM kernel tarrball. It should apply to the 500 kernel source tree, but I haven't tried.

[lardman]

I don't have a Belkin card, so this is not exactly what you need, but...

I've got a Socket rev E (I think) which works fine with a simple 'hciconfig hci0 up'.

I've not got pand working (yet), but have been a bit too busy to try of late.

The Bluetooth manager also seems to be lacking, in that it will show your paired devices, but the tree doesn't open up any further (I guess that it should show the capabilities for each device when you click on them).

I've not tried the obex apps yet, but a GUI would be nice (tumnus' app in development seems to be a good starting point).


Si

[Harlequin]

Let's imagine for a second that out of frustration with trying to dial out through my sony ericsson phone over infra red, I went and bought a bluetooth card.  Let's say that it turns out that the belkin bluetooth card also needs a kernel patch.  Let's imagine that I'm now prepared to throw cash at the problem (not being a programmer) and will now go out and buy a second bluetooth card.

I can't seem to track down a billionton card for sale anywhere.  Are there any other bluetooth cards that have not given any trouble under 3.5.2?

Harry.



btw I think the amount of work put into this project by the small number of developers is incredible, and I'm not criticising.  I'm laughing at my own bad luck.

[maslovsky]

These are the card that are proven to work on Zaurus without any tweaks:

 - Socket rev. E, F
 - Ambicom BT2000E (old revision, yellow sticker)
 - Pretec (same as ambicom)
 - Anycom (old revision, NOT C300)

Socket G and H are supported by the drivers but may need some tweaks under OZ.

[rgodinez]

Belkin bluetooth card will not work without a kernel patch, which allows to set unusual baude rates, such as 100000. Tis patch is included in Cacko ROM kernel tarrball. It should apply to the 500 kernel source tree, but I haven't tried.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

I've got a Belkin F8T020, and a SL5500-S with  OZ 3.5.2 (with all the upgrades up to date).
And it works pairing with my Windows 2000 box, browsing services, ... but I can't establish PAN connections...

** CONSOLE CONFIG

1. insert card. It is detected as "Compaq iPAQ Bluetooth Sleeve", doesn't matters...
Automatically managed by serial_cs module. The card's green light is on.

2. hciattach /dev/ttyS3 bcsp 921600
The light is off, and the hci_uart module is loaded (as it can be stated by running 'lsmod').
'hciconfig' shows the interface hci0 with MAC 00:...:00

3. hciconfig hci0 up
The interface shows its real MAC.

** AUTOMATIC CONFIG
1. Put into file /etc/sysconfig/bluetooth the values for variables
  BLUETOOTH=yes
  BLUETOOTH_PORT=/dev/ttyS3
  BLUETOOTH_PROTOCOL=bcsp
  BLUETOOTH_SPEED=921600
This file is readed from script /etc/bluetooth/hciattach

2. ln -s /etc/bluetooth/hciattach /usr/sbin/hciattach
/usr/sbin/hciattach is called from init script /etc/pcmcia/bluetooth to activate serial bluetooth configurated devices, after card insertion.

3. Insert the card, "et voila!!" it is recognised and correctly activated.
You can see by executing 'hciconfig' that hci0 is up.

** GRAPHICAL TOOLS

1. bluepin is installed at /opt/QtPalmtop/bin/bluepin, but I only can see it if I invoke from command line on console. I've never seen it called from any connection asking for my PIN...
If we choose so, bluepin saves the pin encoded in the file ~/Settings/bluepin.conf ,
and change the pin_helper entry at /etc/bluetooth/hcid.conf

2. bluetooth manager only detects devices, but doesn't show the provided services, and always tell in status tab (I don't know how to change this):
  Device name: Ipaq
  MAC address: no idea
  Class: PDA
It saves its configuration in ~/Settings/bluetoothmanager.conf

Why any of these graphical tools looks into /etc/bluetooth ?
There is no real sync between the "handmade" configuration written in /etc/bluetooth and the one saved by opie tools.

3. I hope Colin Pinkney could soon release the graphical tools described at [a href=\"http://www.cpinkney.org.uk/zaurus.html]http://www.cpinkney.org.uk/zaurus.html[/url] .
Any news?


** NETWORK CONNECTIONS with MS Windows

I can pair my Zaurus with Windows by means of one script /etc/bluetooth/givepin that echoes one string of the form "PIN:1234".
In fact, it runs 'cat /etc/bluetooth/pin' , where I wrote that string.

I've followed the directions in Jensen's page at http://www.jens-koenen.de/index.html but I cannot establish link with
  pand --role PANU --service NAP --connect <MAC_dest> --nodetach

Always answer with "Permission denied(13)"
And in /var/log/messages can be read:
  hcid[####]: link_key_request (sba=xx:xx:xx:xx:xx:xx, dba=yy:yy:yy:yy:yy:yy)
  pand[####]: Connect to yy:yy:yy:yy:yy:yy failed. Permission denied(13)


Any help would be appreciated ;-)

Rafa.

[rgodinez]

If mountain doesn't come to Mohammed, Mohammed goes to the mountain...

1. I've connected to my W2K box enabling incoming PAN connections in Zaurus:

  pand --listen --role NAP

This can be automatically launched enabling PAND in /etc/default/bluetooth (change option   PAND_ENABLE=true), and restarting bluetooth stack:
  /etc/init.d/bluetooth stop;   /etc/init.d/bluetooth start

It is important to enable mastering in /etc/bluetooth/hcid.conf
  lm accept,master;

2. Then I start a connection from my W2K, and it is established without errors.

3. I've shared Internet outgoing connection with Bluetooth connection in my PC.
(It becomes 192.168.0.1 for incoming connections on Bluetooth)

4. Then I configure bnep0 interface to receive IP by means of DHCP:
   udhcpc -i bnep0
and automagically, bnep0 gets an IP, is up, and DNS is my PC (192.168.0.1). It can be showed by 'ifconfig bnep0'.

5. Ping www.google.com resolves and answers as was hoped.

I can surf the net !


But, still, I'd like to initiate the connection from OpenZaurus...
Any idea?

Rafa.

[tomtom]

These are the card that are proven to work on Zaurus without any tweaks:

 - Socket rev. E, F
 - Ambicom BT2000E (old revision, yellow sticker)
 - Pretec (same as ambicom)
 - Anycom (old revision, NOT C300)

Socket G and H are supported by the drivers but may need some tweaks under OZ.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=63762\"][{POST_SNAPBACK}][/a][/div]

Well I have a Anycom LSE039 card, and whenever I plug it in, I get a log message:

cardmgr[739]: executing: 'modprobe bluecard_cs 2>&1'
cardmgr[739]: + modprobe: Can't locate module bluecard_cs
cardmgr[739]: modprobe exited with status 255
cardmgr[739]: module /lib/modules/2.4.18-rmk7-pxa3-embedix/pcmcia/bluecard_cs.o not available

Hm, is this one of the "C300" class cards? Any way to get it working again? The card worked perfectly with OZ 3.5.0, and I really would like to use bluetooth with OZ...

[malloc]

Download http://bluez.sourceforge.net/download/zaur...18-mh14_arm.ipk

Rename it to bluez-kernel-2.4.18-mh14_arm.tar.gz and open it with winrar or winzip.
There is a bluecard_cs.o in this file. Copy it to your zaurus (lib/modules/2.4.18-rmk7-pxa3-embedix/kernel/drivers/bluetooth) and reboot.

At console use: hciconfig hci0 up
No the card blinks and is ready.

These are the card that are proven to work on Zaurus without any tweaks:

 - Socket rev. E, F
 - Ambicom BT2000E (old revision, yellow sticker)
 - Pretec (same as ambicom)
 - Anycom (old revision, NOT C300)

Socket G and H are supported by the drivers but may need some tweaks under OZ.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

Well I have a Anycom LSE039 card, and whenever I plug it in, I get a log message:

cardmgr[739]: executing: 'modprobe bluecard_cs 2>&1'
cardmgr[739]: + modprobe: Can't locate module bluecard_cs
cardmgr[739]: modprobe exited with status 255
cardmgr[739]: module /lib/modules/2.4.18-rmk7-pxa3-embedix/pcmcia/bluecard_cs.o not available

Hm, is this one of the "C300" class cards? Any way to get it working again? The card worked perfectly with OZ 3.5.0, and I really would like to use bluetooth with OZ...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=66706\"][{POST_SNAPBACK}][/a][/div]

[a href=\"http://bluez.sourceforge.net/download/zaurus/bluez-kernel-2.4.18-mh14_arm.ipk]this[/url]

[fripouille]

Hello

I have a bluetooth generic cf card and i cant get working on my sl5500

I have oz 3.5.2

with cardctl ident :

socket 0:
productinfo: "cf card","Generic","",""
manfid: 0x0279,0x950b
function:2 (serial)

...

I try all the tips but with no success,  

Anyone have an idea ?

Thanks