1 |
A recent post had me investigating this. I'm on net-wireless/bluez-5.43-r1 |
2 |
which thankfully provides the hciconfig utility. I have used hciconfig for |
3 |
years now to enable the bluetooth adapter on my laptop. |
4 |
|
5 |
Starting /etc/init.d/bluetooth does not enable the adapter itself. Setting |
6 |
|
7 |
AutoEnable = true |
8 |
|
9 |
causes an error in the logs: |
10 |
============================ |
11 |
in Mar 28 15:50:20 dell_xps bluetoothd[10619]: Bluetooth daemon 5.43 |
12 |
Mar 28 15:50:20 dell_xps bluetoothd[10619]: Unknown key AutoEnable in |
13 |
main.conf |
14 |
Mar 28 15:50:20 dell_xps bluetoothd[10619]: Starting SDP server |
15 |
Mar 28 15:50:20 dell_xps bluetoothd[10619]: Bluetooth management interface |
16 |
1.14 initialized |
17 |
Mar 28 15:50:20 dell_xps bluetoothd[10619]: Failed to obtain handles for |
18 |
"Service Changed" characteristic |
19 |
Mar 28 15:50:20 dell_xps bluetoothd[10619]: Endpoint registered: sender=:1.34 |
20 |
path=/MediaEndpoint/A2DPSource |
21 |
Mar 28 15:50:20 dell_xps bluetoothd[10619]: Endpoint registered: sender=:1.34 |
22 |
path=/MediaEndpoint/A2DPSink |
23 |
============================ |
24 |
|
25 |
The adapter remains disabled: |
26 |
|
27 |
# hciconfig |
28 |
hci0: Type: Primary Bus: USB |
29 |
BD Address: 90:4C:E5:FA:F2:A8 ACL MTU: 1021:8 SCO MTU: 64:8 |
30 |
DOWN |
31 |
RX bytes:1058 acl:0 sco:0 events:52 errors:0 |
32 |
TX bytes:951 acl:0 sco:0 commands:52 errors:0 |
33 |
|
34 |
|
35 |
Enabling it manually with hciconfig works as always had: |
36 |
|
37 |
# hciconfig hci0 up piscan |
38 |
# hciconfig |
39 |
hci0: Type: Primary Bus: USB |
40 |
BD Address: 90:4C:E5:FA:F2:A8 ACL MTU: 1021:8 SCO MTU: 64:8 |
41 |
UP RUNNING PSCAN ISCAN |
42 |
RX bytes:1599 acl:0 sco:0 events:80 errors:0 |
43 |
TX bytes:1559 acl:0 sco:0 commands:80 errors:0 |
44 |
|
45 |
So, what's the solution if hciconfig et al are not installed with future |
46 |
versions of bluez and the AutoEnable option does not seem to take? |
47 |
-- |
48 |
Regards, |
49 |
Mick |