[SOLVED] Bluetooth won't pair. bluez5 with current kernel 4.0.x

FNtastic · 2015-05-23 01:20:53

Okay. After putting that hcd file in, I'm getting slow boot times (presumably due to errors during boot) from this:

[   16.450641] usb 1-1.2: device descriptor read/64, error -110
[   31.627537] usb 1-1.2: device descriptor read/64, error -110
[   31.797530] usb 1-1.2: new full-speed USB device number 4 using ehci-pci
[   46.871149] usb 1-1.2: device descriptor read/64, error -110
[   62.048256] usb 1-1.2: device descriptor read/64, error -110
[   62.218325] usb 1-1.2: new full-speed USB device number 5 using ehci-pci
[   67.237322] usb 1-1.2: device descriptor read/8, error -110
[   72.356395] usb 1-1.2: device descriptor read/8, error -110
[   72.526377] usb 1-1.2: new full-speed USB device number 6 using ehci-pci
[   77.545414] usb 1-1.2: device descriptor read/8, error -110
[   82.664476] usb 1-1.2: device descriptor read/8, error -110
[   82.767796] usb 1-1-port2: unable to enumerate USB device

FNtastic · 2015-05-23 01:45:11

My system is booting slow. Again presumably due to the usb errors above. And my bluetooth is no further along in being fixed... I copied the file over from Windows as suggested into the correct folder. Nothing...

toz · 2015-05-23 11:49:00

I loaded the file you suggested.

Which file? What do the following return?

ls -l /lib/firmware/brcm/*

...and running with root privileges:

journalctl | grep -i bluetooth

.

usb 1-1.2: device descriptor read/64, error -110

This is probably related to a different issue. See, for example, https://bbs.archlinux.org/viewtopic.php?id=140184

.

Have you tried the lts kernel? I believe its a version before the kernel patch was included.

FNtastic · 2015-05-23 13:51:32

I loaded the hcd file that toz suggested to grab from Windows. I followed the link that I posted, downloaded that ~143MB driver file and searched through it for the one that the guide said to use. I'm no longer getting the errors after letting my laptop sit overnight. But, I'm starting to wonder if there may be a more appropriate hex file for my card/chip. I wonder if there is a more appropriate one for the Broadcom BCM94352, aka BCM4352, aka AzureWare2123 that I have....

Here are my results after booting up a few minutes ago. I'm currently running Network Manger for my WiFi. It doesn't appear to be causing an issue with my combo chip. I have read that the bluetooth needs to be on before WiFi. Although, my last results were completely on netctl, using wifi-menu. Anyway, here are my results:

$ dmesg | grep Bluetooth
[    2.462184] Bluetooth: Core ver 2.20
[    2.462204] Bluetooth: HCI device and connection manager initialized
[    2.462208] Bluetooth: HCI socket layer initialized
[    2.462212] Bluetooth: L2CAP socket layer initialized
[    2.462218] Bluetooth: SCO socket layer initialized
[    2.500282] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 lmp_ver=06 lmp_subver=220e
[    4.364991] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    4.364995] Bluetooth: BNEP filters: protocol multicast
[    4.365001] Bluetooth: BNEP socket layer initialized
[    4.558069] Bluetooth: hci0 command 0x303a tx timeout
[   12.558422] Bluetooth: hci0: BCM: patch command 303a failed (-110)
[   14.562678] Bluetooth: hci0 command 0x0c03 tx timeout
[   22.563010] Bluetooth: hci0: HCI_OP_RESET failed (-110)

$ sudo systemctl status bluetooth 
● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
   Active: active (running) since Sat 2015-05-23 09:30:22 EDT; 1min 26s ago
     Docs: man:bluetoothd(8)
 Main PID: 290 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─290 /usr/lib/bluetooth/bluetoothd

May 23 09:30:22 PC systemd[1]: Starting Bluetooth service...
May 23 09:30:22 PC bluetoothd[290]: Bluetooth daemon 5.30
May 23 09:30:22 PC bluetoothd[290]: Starting SDP server
May 23 09:30:22 PC systemd[1]: Started Bluetooth service.
May 23 09:30:22 PC bluetoothd[290]: Bluetooth management interface 1.8 initialized

$ dmesg | grep error
*no results*

$ bluetoothctl
[bluetooth]# power on
No default controller available

I did note that I didn't have to 'start' the bluetooth service manually on this boot. It was already started and running. I can't think of anything outside of me possibly having the wrong hex needed for my specific card...

Here are the requested outputs:

$ ls -l /lib/firmware/brcm/*
-rw-r--r-- 1 user user  69358 Aug  6  2013 /lib/firmware/brcm/BCM20702A0-13d3-3404.hcd
-rw-r--r-- 1 root  root  269595 May 11 01:49 /lib/firmware/brcm/bcm4329-fullmac-4.bin
-rw-r--r-- 1 root  root   96224 May 11 01:49 /lib/firmware/brcm/bcm43xx-0.fw
-rw-r--r-- 1 root  root     180 May 11 01:49 /lib/firmware/brcm/bcm43xx_hdr-0.fw
-rw-r--r-- 1 root  root  397312 May 11 01:49 /lib/firmware/brcm/brcmfmac43143.bin
-rw-r--r-- 1 root  root  385067 May 11 01:49 /lib/firmware/brcm/brcmfmac43143-sdio.bin
-rw-r--r-- 1 root  root  348160 May 11 01:49 /lib/firmware/brcm/brcmfmac43236b.bin
-rw-r--r-- 1 root  root  455745 May 11 01:49 /lib/firmware/brcm/brcmfmac43241b0-sdio.bin
-rw-r--r-- 1 root  root  403855 May 11 01:49 /lib/firmware/brcm/brcmfmac43241b4-sdio.bin
-rw-r--r-- 1 root  root  408682 May 11 01:49 /lib/firmware/brcm/brcmfmac43241b5-sdio.bin
-rw-r--r-- 1 root  root  479232 May 11 01:49 /lib/firmware/brcm/brcmfmac43242a.bin
-rw-r--r-- 1 root  root  253748 May 11 01:49 /lib/firmware/brcm/brcmfmac4329-sdio.bin
-rw-r--r-- 1 root  root  222126 May 11 01:49 /lib/firmware/brcm/brcmfmac4330-sdio.bin
-rw-r--r-- 1 root  root  397378 May 11 01:49 /lib/firmware/brcm/brcmfmac43340-sdio.bin
-rw-r--r-- 1 root  root  451566 May 11 01:49 /lib/firmware/brcm/brcmfmac4334-sdio.bin
-rw-r--r-- 1 root  root  569291 May 11 01:49 /lib/firmware/brcm/brcmfmac4335-sdio.bin
-rw-r--r-- 1 root  root  219557 May 11 01:49 /lib/firmware/brcm/brcmfmac43362-sdio.bin
-rw-r--r-- 1 root  root  493599 May 11 01:49 /lib/firmware/brcm/brcmfmac4339-sdio.bin
-rw-r--r-- 1 root  root  488193 May 11 01:49 /lib/firmware/brcm/brcmfmac43455-sdio.bin
-rw-r--r-- 1 root  root  591837 May 11 01:49 /lib/firmware/brcm/brcmfmac4354-sdio.bin
-rw-r--r-- 1 root  root  557056 May 11 01:49 /lib/firmware/brcm/brcmfmac43569.bin
-rw-r--r-- 1 root  root  593956 May 11 01:49 /lib/firmware/brcm/brcmfmac4356-pcie.bin
-rw-r--r-- 1 root  root  550333 May 11 01:49 /lib/firmware/brcm/brcmfmac43570-pcie.bin
-rw-r--r-- 1 root  root  588940 May 11 01:49 /lib/firmware/brcm/brcmfmac43602-pcie.ap.bin
-rw-r--r-- 1 root  root  590544 May 11 01:49 /lib/firmware/brcm/brcmfmac43602-pcie.bin

$ journalctl | grep -i bluetooth
*no results*

I'm going to try and change the owner of the hcd file to root as I can see that's the only thing different between those files. Will report back with results...

FNtastic · 2015-05-23 14:01:07

I'm thinking the USB errors are something outside of this. They only seem to happen when I use the 'sudo reboot' command.

sudo chown root:root /lib/firmware/brcm/BCM20702A0-13d3-3404.hcd

After reboot, seeing this with no errors in dmesg:

$ dmesg | grep Bluetooth
[    2.500910] Bluetooth: Core ver 2.20
[    2.501137] Bluetooth: HCI device and connection manager initialized
[    2.501142] Bluetooth: HCI socket layer initialized
[    2.501146] Bluetooth: L2CAP socket layer initialized
[    2.501154] Bluetooth: SCO socket layer initialized
[    2.530326] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 lmp_ver=06 lmp_subver=220e
[    4.591741] Bluetooth: hci0 command 0x303a tx timeout
[    5.172645] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    5.172648] Bluetooth: BNEP filters: protocol multicast
[    5.172653] Bluetooth: BNEP socket layer initialized
[   12.588702] Bluetooth: hci0: BCM: patch command 303a failed (-110)
[   14.596389] Bluetooth: hci0 command 0x0c03 tx timeout
[   22.593369] Bluetooth: hci0: HCI_OP_RESET failed (-110)

EDIT: I'm starting to think the USB errors are related to the bluetooth chip. When I do a reboot/restart rather than a full-cycle shutdown, I get the errors. In addition, with reboot/restart, I don't get bluetooth timeout errors, etc... With full-cycle off-on, I get the bluetooth timeout messages. Please note that my chip is technically using USB according to what I understand about it. btusb has to be loaded in order for it to be recognized...

EDIT 2: I also noticed that the md5 for the file that is loaded in my Windows partition is different than the file that was in the downloaded driver. I don't know if that means that the actual file is different that I need, or something else...

Last edited by FNtastic (2015-05-23 14:36:41)

toz · 2015-05-23 17:18:59

[ 2.530326] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 lmp_ver=06 lmp_subver=220e

Patch file found and patching...

[ 12.588702] Bluetooth: hci0: BCM: patch command 303a failed (-110)

...patching failed.

Probably the wrong patch file. What does the following return:

lsusb

toz · 2015-05-23 17:39:17

From the http://66.226.78.22/downloadsite/driver … .7900).zip firmware file, search Win64/bcbtums-win8x64-brcm.inf file for your device:

%AzBtModule.DeviceDesc%=RAMUSB3404, USB\VID_13D3&PID_3404 ; 4352HMB Azurewave Module

Assuming the VID is correct "13D3:3404", search for RAMUSB3404:

;;;;;;;;;;;;;RAMUSB3404;;;;;;;;;;;;;;;;;
[RAMUSB3404.CopyList]
bcbtums.sys
btwampfl.sys
BCM20702A1_001.002.014.1315.1356.hex

...to get the name of the associated firmware hex file. Run this file through "hex2hcd" and copy the resulting hcd to file /lib/firmware/brcm/. You may need to rename the file to match what it the loader is looking for.

At least that is what I would try.

FNtastic · 2015-05-24 02:09:31

toz wrote:

From the http://66.226.78.22/downloadsite/driver … .7900).zip firmware file, search Win64/bcbtums-win8x64-brcm.inf file for your device:
%AzBtModule.DeviceDesc%=RAMUSB3404, USB\VID_13D3&PID_3404 ; 4352HMB Azurewave Module
Assuming the VID is correct "13D3:3404", search for RAMUSB3404:
;;;;;;;;;;;;;RAMUSB3404;;;;;;;;;;;;;;;;;
[RAMUSB3404.CopyList]
bcbtums.sys
btwampfl.sys
BCM20702A1_001.002.014.1315.1356.hex
...to get the name of the associated firmware hex file. Run this file through "hex2hcd" and copy the resulting hcd to file /lib/firmware/brcm/. You may need to rename the file to match what it the loader is looking for.
At least that is what I would try.

This is what worked. I was using the right driver, I think that using hex2hcd is what made the difference. I was renaming the file previously. Which obviously didn't work. Thank you for your help with this. I now have Network Manager and bluetooth working together on cinnamon arch. Now, if I can just find a GUI bluetooth manager, I'll be set.

WorMzy · 2015-05-24 14:41:08

Hi FNtastic, I saw your report. You can mark your own topics as SOLVED by editing the subject in your first post.

ashishsharma71 · 2015-06-20 04:27:24

Dear all, I am new to Arch Linux, although have been using Linux (Ubuntu, Fedora etc. since long).

I had similar problem since last couple of days after a new install (of Arch) in bluetooth pairing (from my dell studio 1435 to my Android phone) as detailed below:

# systemctl status bluetooth
* bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Sat 2015-06-20 09:00:53 IST; 24min ago
Docs: man:bluetoothd(8)
Main PID: 315 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
`-315 /usr/lib/bluetooth/bluetoothd

Jun 20 09:00:54 mylappy bluetoothd[315]: Error adding Link Loss service
Jun 20 09:00:54 mylappy bluetoothd[315]: Not enough free handles to register service
Jun 20 09:00:54 mylappy bluetoothd[315]: Not enough free handles to register service
Jun 20 09:00:54 mylappy bluetoothd[315]: Not enough free handles to register service
Jun 20 09:00:54 mylappy bluetoothd[315]: Current Time Service could not be registered
Jun 20 09:00:54 mylappy bluetoothd[315]: gatt-time-server: Input/output error (5)
Jun 20 09:00:54 mylappy bluetoothd[315]: Not enough free handles to register service
Jun 20 09:00:54 mylappy bluetoothd[315]: Not enough free handles to register service
Jun 20 09:00:54 mylappy bluetoothd[315]: Sap driver initialization failed.
Jun 20 09:00:54 mylappy bluetoothd[315]: sap-server: Operation not permitted (1)

What suddenly worked for me was (as root):
# pacman -S bluez-firmware
warning: bluez-firmware-1.2-8 is up to date -- reinstalling

(I reinstalled bluez-firmware as it was recommended elsewhere for my hw)

# systemctl disable bluetooth
# systemctl enable bluetooth
# systemctl start bluetooth

Now, as a normal user, I am able to pair and transfer files to my phone.

Thanks.

zettaone · 2016-08-23 22:54:42

For `Failed to connect: org.bluez.Error.Failed` error try install the package: `pulseaudio-bluetooth`

# pacman -S pulseaudio-bluetooth

Last edited by zettaone (2016-08-23 22:56:47)

WorMzy · 2016-08-24 00:00:28

Please don't necrobump, especially solved threads.

Closing.

Arch Linux

#26 2015-05-23 01:20:53

Re: [SOLVED] Bluetooth won't pair. bluez5 with current kernel 4.0.x

#27 2015-05-23 01:45:11

Re: [SOLVED] Bluetooth won't pair. bluez5 with current kernel 4.0.x

#28 2015-05-23 11:49:00

Re: [SOLVED] Bluetooth won't pair. bluez5 with current kernel 4.0.x

#29 2015-05-23 13:51:32

Re: [SOLVED] Bluetooth won't pair. bluez5 with current kernel 4.0.x

#30 2015-05-23 14:01:07

Re: [SOLVED] Bluetooth won't pair. bluez5 with current kernel 4.0.x

#31 2015-05-23 17:18:59

Re: [SOLVED] Bluetooth won't pair. bluez5 with current kernel 4.0.x

#32 2015-05-23 17:39:17

Re: [SOLVED] Bluetooth won't pair. bluez5 with current kernel 4.0.x

#33 2015-05-24 02:09:31

Re: [SOLVED] Bluetooth won't pair. bluez5 with current kernel 4.0.x

#34 2015-05-24 14:41:08

Re: [SOLVED] Bluetooth won't pair. bluez5 with current kernel 4.0.x

#35 2015-06-20 04:27:24

Re: [SOLVED] Bluetooth won't pair. bluez5 with current kernel 4.0.x

#36 2016-08-23 22:54:42

Re: [SOLVED] Bluetooth won't pair. bluez5 with current kernel 4.0.x

#37 2016-08-24 00:00:28

Re: [SOLVED] Bluetooth won't pair. bluez5 with current kernel 4.0.x

Board footer