sagemintblue
2nd July 2008, 07:34 PM
I've been looking around for ways I might further debug a bluetooth connectivity issue i'm having.
I recently purchased a Bluetooth USB adapter (Azio USB Micro Bluetooth Adapter BTD-V201) for my desktop. I'm running Fedora Core 7 (32-bit). The adapter seems to be working fine, as seen by the following status output:
# grep hcid /var/log/messages
Jul 2 12:27:30 seward hcid[2305]: HCI dev 0 registered
Jul 2 12:27:30 seward hcid[2305]: HCI dev 0 up
Jul 2 12:27:30 seward hcid[2305]: Device hci0 has been added
Jul 2 12:27:30 seward hcid[2305]: Starting security manager 0
Jul 2 12:27:30 seward hcid[2305]: Device hci0 has been activated
...
# /sbin/lsusb
Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
...
# /etc/rc.d/init.d/bluetooth status
hcid (pid 2305) is running...
sdpd (pid 2311) is running...
# hcitool dev
Devices:
hci0 00:1B:DC:00:21:41
# /usr/sbin/hciconfig
hci0: Type: USB
BD Address: 00:1B:DC:00:21:41 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:15581 acl:0 sco:0 events:490 errors:0
TX bytes:1919 acl:0 sco:0 commands:210 errors:0
When I place my Bluetooth headset (Jabra JX-10 version 1) in pairing mode so it's discoverable, hcitool scan properly finds the device:
# hcitool scan
Scanning ...
00:07:A4:D2:03:67 Jabra JX10
# hcitool info 00:07:A4:D2:03:67
Requesting information ...
BD Address: 00:07:A4:D2:03:67
LMP Version: 1.2 (0x2) LMP Subversion: 0x80e
Manufacturer: Cambridge Silicon Radio (10)
Features: 0xff 0xff 0x8b 0x78 0x18 0x18 0x00 0x80
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<park state> <RSSI> <channel quality> <SCO link> <HV2 packets>
<HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme>
<transparent SCO> <broadcast encrypt> <enhanced iscan>
<interlaced iscan> <interlaced pscan> <inquiry with RSSI>
<AFH cap. slave> <AFH class. slave> <AFH cap. master>
<AFH class. master> <extended features>
But when I try to connect to it via hcitool cc, it silently fails, with no added info in syslog or elsewhere that I can find...
# time hcitool cc 00:07:A4:D2:03:67
real 0m1.321s
user 0m0.000s
sys 0m0.001s
# hcitool con
Connections:
Any thoughts?? Also, here's the contents of my /etc/bluetooth/hcid.conf file:
# 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 user;
# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;
# Default PIN code for incoming connections
#passkey "PIN:0000";
# modify this script to include device pin when pairing
#pin_helper /etc/bluetooth/feed-pin.sh;
}
# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "%h-%d";
# Local device class
class 0x120104;
# 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;
# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;
# authentication / encryption
auth disable;
encrypt disable;
}
