Righty-ho, I bought a socket BT card off ebay (the first rev, E perhaps?).
It seems to work fine, but...
Why are most of the binaries from the bluez-utils-nodbus ipk (like hciconfig) placed in /bin? Surely they should go in /usr/bin, or /sbin, or just somewhere else...?
The local device class is wrong (in that it's not valid as far as I can work out). It comes as 0x120112 (in /etc/bluetooth/hcid.conf), but should be 0x120110 IMHO (as the first two bytes should be 00 I think).
Should there be an /etc/bluetooth/givepin script? There's not one in the packages available in the feed, so I created one myself (I ask because this always seems to be required on most of the instructions on the net).
The bluepin script which is installed from the bluez-utils-nodbus ipk looks like it requires python and GPE to operate. Not ideal, I'd assumed this package was non-GUI-dependent.
I tried to create a PAN connection as described here (
http://www.jens-koenen.de/zaurus_pan.html), however it always fails with the following error after I issue the 'pand ...' command:
pand[4291]: Bluetooth PAN daemon version 2.11
pand[4291]: Connecting to 00:02:72:B3:0A:9D
pand[4291]: Connect to 00:02:72:B3:0A:9D failed. Invalid exchange(52)
Where 00:02:72:B3:0A:9D is my WinXP computer, via a BT USB dongle.
I've also tried to add my Z to the list of available devices using the WinXP GUI, however it always fails to exchange passkeys. If I tell it to not use a passkey (WinXP), I can look at the properties of my Z, but no services seem to be available.
All rather confusing :-) If anyone can shed some light that would be great.
For the most part, ignore my moaning above; once I get an SVN client running I'll grab the latest source and submit patches as required, however it may take a little time.
Si
P.S.
root@shepherd:/etc/bluetooth# more hcid.conf
#
# HCI daemon configuration file.
#
# $Id: hcid.conf,v 1.4 2004/04/29 20:14:21 holtmann Exp $
#
# HCId options
options {
# Automatically initialize new devices
autoinit yes;
# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security auto;
# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;
# PIN helper
pin_helper /opt/QtPalmtop/bin/bluepin;
# D-Bus PIN helper
# dbus_pin_helper;
}
# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "Bi-Valve";
# Local device class
#class 0x120112;
class 0x120110;
# Default packet type
#pkt_type DH1,DM1,HV1;
# Inquiry and Page scan
iscan enable;pscan enable;
# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
#
#lm accept,master;
#
lm accept;
# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
#
#lp hold,sniff;
#
lp rswitch,hold,sniff,park;
# Authentication and Encryption
#auth enable;
encrypt enable;
}
