Bluetooth speaker failing to connect due to CMAC error [Solved]

bradsk88 · 2019-04-06 19:07:39

When I run bluetoothctl, I'm able to pair with my device (Bose SoundLink Color II), but not connect.

# bluetoothctl 
Agent registered
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:15:83:F6:DD:40 Discovering: yes
[CHG] Device 04:52:C7:3E:DF:C2 RSSI: -65
[CHG] Device 04:52:C7:3E:DF:C2 TxPower: 10
[CHG] Device 04:52:C7:3E:DF:C2 Name: LE-Humidor
[CHG] Device 04:52:C7:3E:DF:C2 Alias: LE-Humidor
[CHG] Device 04:52:C7:3E:DF:C2 ManufacturerData Key: 0x0310
[CHG] Device 04:52:C7:3E:DF:C2 ManufacturerData Value:
  40 0d 01 b1 30 96 fb a2 af a8                    @...0.....      
[bluetooth]# scan off
Discovery stopped
[CHG] Controller 00:15:83:F6:DD:40 Discovering: no
[CHG] Device 04:52:C7:3E:DF:C2 TxPower is nil
[CHG] Device 04:52:C7:3E:DF:C2 RSSI is nil
[bluetooth]# trust 04:52:C7:3E:DF:C2
Changing 04:52:C7:3E:DF:C2 trust succeeded
[bluetooth]# pair 04:52:C7:3E:DF:C2
Attempting to pair with 04:52:C7:3E:DF:C2
[CHG] Device 04:52:C7:3E:DF:C2 Connected: yes
[NEW] Primary Service
	/org/bluez/hci0/dev_04_52_C7_3E_DF_C2/service0001
	0000febe-0000-1000-8000-00805f9b34fb
	Bose Corporation
[NEW] Characteristic
	/org/bluez/hci0/dev_04_52_C7_3E_DF_C2/service0001/char0002
	9ec813b4-256b-4090-93a8-a4f0e9107733
	Vendor specific
[NEW] Descriptor
	/org/bluez/hci0/dev_04_52_C7_3E_DF_C2/service0001/char0002/desc0004
	00002902-0000-1000-8000-00805f9b34fb
	Client Characteristic Configuration
[NEW] Characteristic
	/org/bluez/hci0/dev_04_52_C7_3E_DF_C2/service0001/char0005
	d417c028-9818-4354-99d1-2ac09d074591
	Vendor specific
[NEW] Descriptor
	/org/bluez/hci0/dev_04_52_C7_3E_DF_C2/service0001/char0005/desc0007
	00002902-0000-1000-8000-00805f9b34fb
	Client Characteristic Configuration
[NEW] Characteristic
	/org/bluez/hci0/dev_04_52_C7_3E_DF_C2/service0001/char0008
	234bfbd5-e3b3-4536-a3fe-723620d4b78d
	Vendor specific
[NEW] Primary Service
	/org/bluez/hci0/dev_04_52_C7_3E_DF_C2/service000a
	00001801-0000-1000-8000-00805f9b34fb
	Generic Attribute Profile
[NEW] Characteristic
	/org/bluez/hci0/dev_04_52_C7_3E_DF_C2/service000a/char000b
	00002a05-0000-1000-8000-00805f9b34fb
	Service Changed
[NEW] Descriptor
	/org/bluez/hci0/dev_04_52_C7_3E_DF_C2/service000a/char000b/desc000d
	00002902-0000-1000-8000-00805f9b34fb
	Client Characteristic Configuration
[NEW] Primary Service
	/org/bluez/hci0/dev_04_52_C7_3E_DF_C2/service0013
	0000180a-0000-1000-8000-00805f9b34fb
	Device Information
[NEW] Characteristic
	/org/bluez/hci0/dev_04_52_C7_3E_DF_C2/service0013/char0014
	00002a29-0000-1000-8000-00805f9b34fb
	Manufacturer Name String
[NEW] Characteristic
	/org/bluez/hci0/dev_04_52_C7_3E_DF_C2/service0013/char0016
	00002a24-0000-1000-8000-00805f9b34fb
	Model Number String
[NEW] Characteristic
	/org/bluez/hci0/dev_04_52_C7_3E_DF_C2/service0013/char0018
	00002a25-0000-1000-8000-00805f9b34fb
	Serial Number String
[NEW] Characteristic
	/org/bluez/hci0/dev_04_52_C7_3E_DF_C2/service0013/char001a
	00002a27-0000-1000-8000-00805f9b34fb
	Hardware Revision String
[NEW] Characteristic
	/org/bluez/hci0/dev_04_52_C7_3E_DF_C2/service0013/char001c
	00002a26-0000-1000-8000-00805f9b34fb
	Firmware Revision String
[NEW] Characteristic
	/org/bluez/hci0/dev_04_52_C7_3E_DF_C2/service0013/char001e
	00002a28-0000-1000-8000-00805f9b34fb
	Software Revision String
[NEW] Characteristic
	/org/bluez/hci0/dev_04_52_C7_3E_DF_C2/service0013/char0020
	00002a23-0000-1000-8000-00805f9b34fb
	System ID
[NEW] Characteristic
	/org/bluez/hci0/dev_04_52_C7_3E_DF_C2/service0013/char0022
	00002a50-0000-1000-8000-00805f9b34fb
	PnP ID
[CHG] Device 04:52:C7:3E:DF:C2 UUIDs: 00001101-0000-1000-8000-00805f9b34fb
[CHG] Device 04:52:C7:3E:DF:C2 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 04:52:C7:3E:DF:C2 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 04:52:C7:3E:DF:C2 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 04:52:C7:3E:DF:C2 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 04:52:C7:3E:DF:C2 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 04:52:C7:3E:DF:C2 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device 04:52:C7:3E:DF:C2 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device 04:52:C7:3E:DF:C2 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device 04:52:C7:3E:DF:C2 UUIDs: 0000febe-0000-1000-8000-00805f9b34fb
[CHG] Device 04:52:C7:3E:DF:C2 ServicesResolved: yes
[LE-Humidor]# connect 04:52:C7:3E:DF:C2
Attempting to connect to 04:52:C7:3E:DF:C2
Failed to connect: org.bluez.Error.Failed
[LE-Humidor]# exit

When I check dmesg:

[362550.930977] Bluetooth: Unable to create CMAC crypto context
[363754.325361] Bluetooth: hci0: security requested but not available

And I don't seem to have the CMAC module installed.

$ modprobe -v cmac
modprobe: FATAL: Module cmac not found in directory /lib/modules/5.0.3-arch1-1-ARCH

I suspect I just need to load this CMAC module. But, I couldn't find any info online.

Edit:

I rebooted my machine to rule out out-of-date kernel modules. Still can't connect, but also found this:

# systemctl bluetooth
Unknown operation bluetooth.
[root@AMELIA bradsk88]# systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
   Active: active (running) since Sat 2019-04-06 13:09:38 CST; 3min 1s ago
     Docs: man:bluetoothd(8)
 Main PID: 680 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   Memory: 3.2M
   CGroup: /system.slice/bluetooth.service
           └─680 /usr/lib/bluetooth/bluetoothd

Apr 06 13:09:38 AMELIA systemd[1]: Starting Bluetooth service...
Apr 06 13:09:38 AMELIA bluetoothd[680]: Bluetooth daemon 5.50
Apr 06 13:09:38 AMELIA systemd[1]: Started Bluetooth service.
Apr 06 13:09:38 AMELIA bluetoothd[680]: Starting SDP server
Apr 06 13:09:38 AMELIA bluetoothd[680]: Bluetooth management interface 1.14 initialized
Apr 06 13:11:13 AMELIA bluetoothd[680]: Error reading PNP_ID value: Unexpected error code
Apr 06 13:11:26 AMELIA bluetoothd[680]: Error reading PNP_ID value: Unexpected error code
Apr 06 13:11:45 AMELIA bluetoothd[680]: a2dp-sink profile connect failed for 04:52:C7:3E:DF:C2: Protocol not available

Last edited by bradsk88 (2019-04-07 18:54:13)

V1del · 2019-04-06 19:15:29

You ran a kernel upgrade and your running kernel is outdated. Verify that you had/have your /boot partition mounted (reinstall the kernel to be safe) and reboot into the new kernel.

Your old modules folder is deleted when the kernel updates and you should generally reboot as soon as convenient after having ran a kernel update.

Edit: You might have to install something that implements a2dp, so you will want to install pulseaudio and pulseaudio-bluetooth

Last edited by V1del (2019-04-06 19:16:36)

bradsk88 · 2019-04-07 18:53:58

Thanks. Looks like I missed the Audio section in the wiki. Following those steps, rebooting, and connecting did the trick.

Arch Linux

#1 2019-04-06 19:07:39

Bluetooth speaker failing to connect due to CMAC error [Solved]

#2 2019-04-06 19:15:29

Re: Bluetooth speaker failing to connect due to CMAC error [Solved]

#3 2019-04-07 18:53:58

Re: Bluetooth speaker failing to connect due to CMAC error [Solved]

Board footer