A recent post had me investigating this. I'm on net-wireless/bluez-5.43-r1 which thankfully provides the hciconfig utility. I have used hciconfig for years now to enable the bluetooth adapter on my laptop.
Starting /etc/init.d/bluetooth does not enable the adapter itself. Setting AutoEnable = true causes an error in the logs: ============================ in Mar 28 15:50:20 dell_xps bluetoothd[10619]: Bluetooth daemon 5.43 Mar 28 15:50:20 dell_xps bluetoothd[10619]: Unknown key AutoEnable in main.conf Mar 28 15:50:20 dell_xps bluetoothd[10619]: Starting SDP server Mar 28 15:50:20 dell_xps bluetoothd[10619]: Bluetooth management interface 1.14 initialized Mar 28 15:50:20 dell_xps bluetoothd[10619]: Failed to obtain handles for "Service Changed" characteristic Mar 28 15:50:20 dell_xps bluetoothd[10619]: Endpoint registered: sender=:1.34 path=/MediaEndpoint/A2DPSource Mar 28 15:50:20 dell_xps bluetoothd[10619]: Endpoint registered: sender=:1.34 path=/MediaEndpoint/A2DPSink ============================ The adapter remains disabled: # hciconfig hci0: Type: Primary Bus: USB BD Address: 90:4C:E5:FA:F2:A8 ACL MTU: 1021:8 SCO MTU: 64:8 DOWN RX bytes:1058 acl:0 sco:0 events:52 errors:0 TX bytes:951 acl:0 sco:0 commands:52 errors:0 Enabling it manually with hciconfig works as always had: # hciconfig hci0 up piscan # hciconfig hci0: Type: Primary Bus: USB BD Address: 90:4C:E5:FA:F2:A8 ACL MTU: 1021:8 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:1599 acl:0 sco:0 events:80 errors:0 TX bytes:1559 acl:0 sco:0 commands:80 errors:0 So, what's the solution if hciconfig et al are not installed with future versions of bluez and the AutoEnable option does not seem to take? -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.