BCM43-142A0 Bluetooth driver installation issuet

HMS_Endeavour · March 18, 2022, 6:35pm

I almost wish I didn’t have to post this, but the closest to it is a Broadcom Wireless LAN driver issue. I had bluetooth working on Manjaro building the driver from the AUR.
I did the following:
pamac build broadcom-bt-firmware-git
sudo modprobe -rfv btusb
sudo modprobe -v btusb
sudo dmesg | grep -i blue
Of course, I only use pacman, so maybe there are some other dependencies, like for example there is no hciconfig installed.

So, in EOS I just did a makepkg -si without errors,

sudo modprobe -rfv btusb gave no errors.

$ sudo modprobe -v btusb
insmod /lib/modules/5.16.15-zen1-1-zen/kernel/crypto/ecdh_generic.ko.zst
insmod /lib/modules/5.16.15-zen1-1-zen/kernel/net/bluetooth/bluetooth.ko.zst
insmod /lib/modules/5.16.15-zen1-1-zen/kernel/drivers/bluetooth/btintel.ko.zst
insmod /lib/modules/5.16.15-zen1-1-zen/kernel/drivers/bluetooth/btbcm.ko.zst
insmod /lib/modules/5.16.15-zen1-1-zen/kernel/drivers/bluetooth/btrtl.ko.zst
insmod /lib/modules/5.16.15-zen1-1-zen/kernel/drivers/bluetooth/btusb.ko.zst reset=1

$ sudo dmesg | grep -i blue
[ 29.887125] Bluetooth: Core ver 2.22
[ 29.887159] NET: Registered PF_BLUETOOTH protocol family
[ 29.887161] Bluetooth: HCI device and connection manager initialized
[ 29.887167] Bluetooth: HCI socket layer initialized
[ 29.887170] Bluetooth: L2CAP socket layer initialized
[ 29.887175] Bluetooth: SCO socket layer initialized
[ 35.627993] Bluetooth: hci0: BCM: chip id 70
[ 35.628988] Bluetooth: hci0: BCM: features 0x06
[ 35.644945] Bluetooth: hci0: BCM43142A
[ 35.644950] Bluetooth: hci0: BCM43142A0 (001.001.011) build 0000
[ 35.871490] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[ 35.871494] Bluetooth: hci0: BCM: ‘brcm/BCM43142A0-04ca-2012.hcd’
[ 35.871495] Bluetooth: hci0: BCM: ‘brcm/BCM-04ca-2012.hcd’
[ 37.897304] Bluetooth: hci0: command 0x1003 tx timeout
[ 37.898946] Bluetooth: hci0: unexpected event for opcode 0x1003
[ 2970.587108] Bluetooth: hci0: BCM: chip id 70
[ 2970.588104] Bluetooth: hci0: BCM: features 0x06
[ 2970.604073] Bluetooth: hci0: BCM43142A
[ 2970.604079] Bluetooth: hci0: BCM43142A0 (001.001.011) build 0000
[ 2970.605125] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[ 2970.605128] Bluetooth: hci0: BCM: ‘brcm/BCM43142A0-04ca-2012.hcd’
[ 2970.605129] Bluetooth: hci0: BCM: ‘brcm/BCM-04ca-2012.hcd’
[ 2972.649353] Bluetooth: hci0: command 0x1003 tx timeout
[ 2972.651288] Bluetooth: hci0: unexpected event for opcode 0x1003
[ 4174.595379] Bluetooth: hci0: BCM: chip id 70
[ 4174.596367] Bluetooth: hci0: BCM: features 0x06
[ 4174.612369] Bluetooth: hci0: BCM43142A
[ 4174.612376] Bluetooth: hci0: BCM43142A0 (001.001.011) build 0000
[ 4174.613423] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[ 4174.613426] Bluetooth: hci0: BCM: ‘brcm/BCM43142A0-04ca-2012.hcd’
[ 4174.613428] Bluetooth: hci0: BCM: ‘brcm/BCM-04ca-2012.hcd’
[ 4176.648617] Bluetooth: hci0: command 0x1003 tx timeout
[ 4176.649387] Bluetooth: hci0: unexpected event for opcode 0x1003
[ 5808.325991] Bluetooth: hci0: BCM: chip id 70
[ 5808.326956] Bluetooth: hci0: BCM: features 0x06
[ 5808.342996] Bluetooth: hci0: BCM43142A
[ 5808.343002] Bluetooth: hci0: BCM43142A0 (001.001.011) build 0000
[ 5808.343961] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[ 5808.343965] Bluetooth: hci0: BCM: ‘brcm/BCM43142A0-04ca-2012.hcd’
[ 5808.343966] Bluetooth: hci0: BCM: ‘brcm/BCM-04ca-2012.hcd’
[ 5810.396210] Bluetooth: hci0: command 0x1003 tx timeout
[ 5810.398108] Bluetooth: hci0: unexpected event for opcode 0x1003
[ 7094.971973] Bluetooth: hci0: BCM: chip id 70
[ 7094.972933] Bluetooth: hci0: BCM: features 0x06
[ 7094.988970] Bluetooth: hci0: BCM43142A
[ 7094.988977] Bluetooth: hci0: BCM43142A0 (001.001.011) build 0000
[ 7094.989982] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[ 7094.989986] Bluetooth: hci0: BCM: ‘brcm/BCM43142A0-04ca-2012.hcd’
[ 7094.989988] Bluetooth: hci0: BCM: ‘brcm/BCM-04ca-2012.hcd’
[ 7097.017376] Bluetooth: hci0: command 0x1003 tx timeout
[ 7097.019013] Bluetooth: hci0: unexpected event for opcode 0x1003
[14983.655896] Bluetooth: hci0: BCM: chip id 70
[14983.656890] Bluetooth: hci0: BCM: features 0x06
[14983.672907] Bluetooth: hci0: BCM43142A
[14983.672914] Bluetooth: hci0: BCM43142A0 (001.001.011) build 0000
[14983.673960] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[14983.673964] Bluetooth: hci0: BCM: ‘brcm/BCM43142A0-04ca-2012.hcd’
[14983.673966] Bluetooth: hci0: BCM: ‘brcm/BCM-04ca-2012.hcd’
[14983.716383] audit: type=1130 audit(1647617875.112:255): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=bluetooth comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=failed’
[14985.725314] Bluetooth: hci0: command 0x1003 tx timeout
[14985.727034] Bluetooth: hci0: unexpected event for opcode 0x1003
[23570.420907] NET: Unregistered PF_BLUETOOTH protocol family
[23596.598816] Bluetooth: Core ver 2.22
[23596.598851] NET: Registered PF_BLUETOOTH protocol family
[23596.598853] Bluetooth: HCI device and connection manager initialized
[23596.598857] Bluetooth: HCI socket layer initialized
[23596.598859] Bluetooth: L2CAP socket layer initialized
[23596.598863] Bluetooth: SCO socket layer initialized
[23596.790741] audit: type=1130 audit(1647626488.411:361): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=bluetooth comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=failed’
[23596.815222] Bluetooth: hci0: BCM: chip id 70
[23596.816235] Bluetooth: hci0: BCM: features 0x06
[23596.832334] Bluetooth: hci0: BCM43142A
[23596.832344] Bluetooth: hci0: BCM43142A0 (001.001.011) build 0000
[23596.833341] Bluetooth: hci0: BCM43142A0 ‘brcm/BCM43142A0-04ca-2012.hcd’ Patch
[23597.607431] Bluetooth: hci0: Broadcom Bluetooth 4.0 USB
[23597.607448] Bluetooth: hci0: BCM43142A0 (001.001.011) build 0339

lsusb

I have Gnome 41, and the bluetooth settings cannot be activated.

Please chime in @ricklinux as you solved the last BCM43-143 driver issue recently, so maybe this is related even though the issue you helped with was wl related.

Thanks in advance,

Michael

ricklinux · March 18, 2022, 6:44pm

I just answered another post as i just fixed a bluetooth issue on another set up here at home for a user.
Check in /etc/modprobe.d/ what files are in there. I had one for the usb adapter on this system that had blacklisted the module btusb

So i just had to comment it out to unblacklist it. Now bluetooth.service starts every boot. I’m not sure if yours will be the same as your bluetooth is probably on the WiFi chip. So it may be broadcom or it’s possible it’s the same module?

Edit: Just try

sudo modprobe btusb

Check if the bluetooth service is running?

systemctl status bluetooth

ricklinux · March 18, 2022, 6:50pm

Also do you have all the packages installed that are required?

HMS_Endeavour · March 18, 2022, 7:01pm

I know, I saw the post and hoped you would have some fresh knowledge on it. But that was a wireless 802.1x driver, this is bluetooth. What is strange: Broadcom made a combined wifi/bluetooth chipset, but when they sold the division, the new owners, required Broadcom to block the bluetooth. So it works perfectly on wireless but not on bluetooth. What is even stranger, is the above mentioned driver from the AUR worked on Manjaro, but not on EOS.

Just installed https://aur.archlinux.org/packages/broadcom-bt-firmware-git

Michael

ricklinux · March 18, 2022, 7:03pm

This is the same issue where the bluetooth.service is not active. Are there any files in /etc/moddprobe.d folder?

You can try the following

sudo modprobe btusb

sudo systemctl enable --now bluetooth.service

systemctl status bluetooth

HMS_Endeavour · March 18, 2022, 7:04pm

no, it’s empty
[michael@eos22 modprobe.d]$ ll
total 0
drwxr-xr-x 1 root root 0 3 févr. 07:14

ricklinux · March 18, 2022, 7:07pm

Try commands in above post.

ricklinux · March 18, 2022, 7:10pm

Have you seen this ?

HMS_Endeavour · March 18, 2022, 7:11pm

Job for bluetooth.service failed because the control process exited with error code.
See “systemctl status bluetooth.service” and “journalctl -xeu bluetooth.service” for details.

HMS_Endeavour · March 18, 2022, 7:13pm

I have heard it discussed in other forums while researching this problem.

HMS_Endeavour · March 18, 2022, 7:17pm

I just did a git clone but I don’t see a PKGBUILD file.
What to do?

ricklinux · March 18, 2022, 7:17pm

It seems others are having bluetooth issues also. I managed to get the one working on an old Antergos install converted to Arch. But it was a realtek usb bluetooth adapter.

ricklinux · March 18, 2022, 7:19pm

Is this the same one in the AUR?

https://aur.archlinux.org/packages/broadcom-bt-firmware-git

HMS_Endeavour · March 18, 2022, 7:21pm

Yes, it is. I left the git version alone because it was 5 years old. The laptop is about 6 years old. That’s why I got it off the AUR, safer

ricklinux · March 18, 2022, 7:23pm

The only thing i can tell you is if the bluetooth service is not starting the module must not be loaded.

HMS_Endeavour · March 18, 2022, 7:24pm

I also got the Microsoft drivers that were prepackaged when Broadcom’s division was sold, MS was the only company to have the complete drivers, so I converted a dll to hcd file and that works for me on Ubunbtu.

I mean worked for me, I no longer use Ubuntu.

ricklinux · March 18, 2022, 7:26pm

What does this show?

lsmod

HMS_Endeavour · March 18, 2022, 7:32pm

I grepped them or it would be too long.

lsmod | grep bt
btusb 69632 0
btrtl 28672 1 btusb
btbcm 20480 1 btusb
btintel 49152 1 btusb
bluetooth 794624 5 btrtl,btintel,btbcm,btusb

lsmod | grep blue
bluetooth 794624 5 btrtl,btintel,btbcm,btusb
ecdh_generic 16384 1 bluetooth
crc16 16384 2 bluetooth,ext4
rfkill 32768 7 acer_wmi,bluetooth,cfg80211

ricklinux · March 18, 2022, 7:39pm

There are a few bluetooth modules? Wonder which one. The btusb is the generic bluetooth module. I believe btbcm is the broadcom?

ricklinux · March 18, 2022, 7:42pm

Have you tried loading it?

sudo modprobe btbcm

systemctl enable bluetooth.service

systemctl status bluetooth