Bluetooth failure after upgrading the BCM20702A0 device in Ubuntu 22.04.1 LTS

Ubuntu
1

KINIVO BLUETOOTH (BT ) ADAPTER, NOT WORKING ON UBUNTU 22.04.1 LTS, JAMMY JELLY FISH SYSTEM OF THE DELL INSPIRON 15R N5010 LAPTOP

STATUS BEFORE, WITH FOCAL FOSSA INSTALLED & IN USE:

anand@jjfish:~$ sudo apt install fwupd

Identified face as anand
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
fwupd is already the newest version (1.7.9-1~22.04.1).
fwupd set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

anand@jjfish:~$ fwupdmgr get-devices

WARNING: UEFI firmware can not be updated in legacy BIOS mode

See PluginFlag:legacy bios · fwupd/fwupd Wiki · GitHub for more information.

Inspiron N5010
│
├─BCM20702A0: # [Broadcom Bluetooth Device/KINIVO Adapter]
│ Device ID: a73094e179d6a5b429503e8b3132d1bea2617edc
│ Current version: 1.12
│ Vendor: Broadcom Corp (USB:0x0A5C)
│ GUIDs: 6faa2765-8bc2-51d3-bf6b-ffd6312c24d2
│ a1e76ca3-d35b-53b8-a17c-454b700274ea
│ Device Flags: • Updatable
│
├─CT500MX500SSD1:
│ Device ID: 602b0a6cc821d155208724f0e22f8d111542b74c
│ Summary: ATA drive
│ Current version: M3CR023
│ Vendor: Micron (ATA:0x1344, OUI:00a075)
│ GUIDs: 2722d904-6dd9-5899-b97c-208d9b6de770
│ 4a382f63-5319-5261-b05d-4c598d8bcd8b
│ ea728598-6b78-58ff-ad8a-e82eb571af3b
│ Device Flags: • Internal device
│ • Updatable
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│
└─Dell Wireless 365 Bluetooth Module:
Device ID: 2816bb0d9cbc984cc6699c17cd0752ddebb45e80
Current version: 1.73
Vendor: Dell Computer Corp (USB:0x413C)
GUIDs: f9f00d0b-b331-5c6a-801f-15ad2db91662
1f742ccc-9709-599b-9081-4fac3f77eb21
Device Flags: • Updatable

STATUS AFTER UPGRADING TO JAMMY JELLYFISH:

anand@jjfish:~$ fwupdmgr get-updates

WARNING: UEFI firmware can not be updated in legacy BIOS mode

See PluginFlag:legacy bios · fwupd/fwupd Wiki · GitHub for more information.

Devices with no available firmware updates:

• BCM20702A0
• CT500MX500SSD1
• Dell Wireless 365 Bluetooth Module

No updatable devices

anand@jjfish:~$ sudo apt install efibootmgr

Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
efibootmgr is already the newest version (17-1ubuntu2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

anand@jjfish:~$ sudo efibootmgr

EFI variables are not supported on this system

anand@jjfish:~$ sudo dmesg | grep -i bluetooth
Identified face as anand
[ 4.556165] usb 2-1.6.3: Product: Dell Wireless 365 Bluetooth Module
[ 4.971149] Bluetooth: Core ver 2.22
[ 4.971204] NET: Registered PF_BLUETOOTH protocol family
[ 4.971207] Bluetooth: HCI device and connection manager initialized
[ 4.971213] Bluetooth: HCI socket layer initialized
[ 4.971216] Bluetooth: L2CAP socket layer initialized
[ 4.971222] Bluetooth: SCO socket layer initialized
[ 6.924258] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 6.924267] Bluetooth: BNEP filters: protocol multicast
[ 6.924274] Bluetooth: BNEP socket layer initialized
[ 8.465482] Bluetooth: RFCOMM TTY layer initialized
[ 8.465500] Bluetooth: RFCOMM socket layer initialized
[ 8.465509] Bluetooth: RFCOMM ver 1.11
[ 68.529938] Bluetooth: hci1: BCM: chip id 63
[ 68.530913] Bluetooth: hci1: BCM: features 0x07
[ 68.546930] Bluetooth: hci1: BCM20702A
[ 68.546941] Bluetooth: hci1: BCM20702A1 (001.002.014) build 0000
[ 68.549168] Bluetooth: hci1: BCM: firmware Patch file not found, tried:
[ 68.549176] Bluetooth: hci1: BCM: ‘brcm/BCM20702A1-0a5c-21e8.hcd’
[ 68.549178] Bluetooth: hci1: BCM: ‘brcm/BCM-0a5c-21e8.hcd’

anand@jjfish:~$ $ cd /lib/firmware/brcm

(1) anand@jjfish:/lib/firmware/brcm$ sudo wget broadcom-bt-firmware/BCM20702A1-0a5c-21e8.hcd at master · winterheart/broadcom-bt-firmware · GitHub

The path of the location where the latest Linux driver for Broadcom Bluetooth firmware for dongle/device BCM20702A is available on the github website is given at the link above

anand@jjfish:~$ $ cd /lib/firmware/brcm
anand@jjfish:/lib/firmware/brcm
$ broadcom-bt-firmware/BCM20702A1-0a5c-21e8.hcd at master · winterheart/broadcom-bt-firmware · GitHub
Resolving github.com (github.com)… 20.207.73.82
Connecting to github.com (github.com)|20.207.73.82|:443… connected.
HTTP request sent, awaiting response… 200 OK
Length: unspecified [text/html]
Saving to: ‘BCM20702A1-0a5c-21e8.hcd’

BCM20702A1-0a5c-21e8.hcd [ <=> ] 143.42K --.-KB/s in 0.07s

2022-11-28 18:05:39 (1.94 MB/s) - ‘BCM20702A1-0a5c-21e8.hcd’ saved [146866]

Desired updated Linux BT device driver as above, successfully installed!

(2) anand@jjfish:/lib/firmware/brcm$ sudo modprobe -r btusb

(3) anand@jjfish:/lib/firmware/brcm$ sudo modprobe btusb

#

anand@jjfish:~$ sudo dmesg |grep -i bluetooth
Face detection timeout reached
[sudo] password for anand:
[ 4.413182] Bluetooth: Core ver 2.22
[ 4.413230] NET: Registered PF_BLUETOOTH protocol family
[ 4.413256] Bluetooth: HCI device and connection manager initialized
[ 4.413264] Bluetooth: HCI socket layer initialized
[ 4.413267] Bluetooth: L2CAP socket layer initialized
[ 4.413274] Bluetooth: SCO socket layer initialized
[ 4.558425] Bluetooth: hci0: BCM: chip id 63
[ 4.559413] Bluetooth: hci0: BCM: features 0x07
[ 4.579373] Bluetooth: hci0: BCM20702A
[ 4.579380] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[ 4.582180] Bluetooth: hci0: BCM20702A1 ‘brcm/BCM20702A1-0a5c-21e8.hcd’ Patch
[ 4.812111] usb 2-1.6.3: Product: Dell Wireless 365 Bluetooth Module
[ 6.664073] Bluetooth: hci0: command 0x0a0a tx timeout
[ 7.360480] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 7.360491] Bluetooth: BNEP filters: protocol multicast
[ 7.360499] Bluetooth: BNEP socket layer initialized
[ 8.811055] Bluetooth: RFCOMM TTY layer initialized
[ 8.811072] Bluetooth: RFCOMM socket layer initialized
[ 8.811081] Bluetooth: RFCOMM ver 1.11
[ 14.695922] Bluetooth: hci0: BCM: Patch command 0a0a failed (-110)
[ 14.695941] Bluetooth: hci0: BCM: Patch failed (-110)
[ 16.903920] Bluetooth: hci0: command 0x1001 tx timeout
[ 24.935909] Bluetooth: hci0: BCM: Reading local version info failed (-110)

                                                    # # #

After installing the “hcd file” update patch from the git hub website for the Broadcom Bluetooth Adapter Device BCM20702A0, bluetooth system stopped working. How to resolve the issue or revert back to the original status before the device upgrade?
I am using x-64 bit, Ubuntu 22.04.1 LTS system with Gnome 42.5 version

2

Reinstall previous Ubuntu from a backup.
It would appear Ubuntu 22 is deficient, and your attempted patch of Dell wireless 365 module failed.
Make a bug report to Ubuntu

This seems to be a common issue with Ubuntu22

Regards
Neville

3

Bug report already submitted.

4

Sorry, but there is not much you can do. You did the obvious attempt to patch the driver… Some problems are impossible on your own.

If you want to stay with Ubuntu22, get a bluetooth dongle that is supported.

Regards
Neville

5

To my mind, the Ubuntu 22.04 version appears to have been released prematurely, without tying up basic upgrade issues; there are one too many problems with snap, not the cited one alone - it is quite frustrating. Reverting back to 20.04 might be a better option until the newer version stabilizes after the bugs are taken care.
Thanks for your support!

1 Like
6

Sage advice from all.
It’s not called “bleeding edge” for nothing.
I prefer to wait 6 months minimum after release for this exact reason.
I also start with a USB bootable.
This behavior includes hardware as well.

3 Likes
7

Damn - I’m running Ubu 22.04 - if this happens to me - it will be a showstopper - I bought a PCIe BT/WifFi combo card early last year - which the vendor certified as Linux compatible (Asus branded card, with chipset “compatible with Ubuntu” - that’s pretty easy to say) and it just works “out of the box”… Tried it with Ubuntu 20.04, 22.04, Fedora 35, 36 - no issues (to replace a VERY flaky Targus BT 4.0 USB dongle).
I’m running Ubuntu 22.04 'cause the AMD GPU drivers are allegedly FULLY supported and better supported in 22.04, than 20.04… If an update kills my BT, I reckon I’ll go back to Ubu 20.04 and tryout the Catalyst Software for Linux from AMD (which will give me two features lacking in the open source drivers - GPU monitor spanning, ray tracing).

Note - I had monitor spanning TEN F–KING years ago on Ubuntu 12.04 with a “lowly” (okay it was kinda middle / entry+ level in 2012) GTX650Ti OC using proprietary NVidia drivers - i.e. I could play Serious Sam 3 full screen across THREE Monitors! Ten years later and I can’t do that? WTF?

8

I am in sync with Dan tripp’s views. I too should have waited for at least 6 months before switching over from Ubuntu 20.04 to 22.04 with snap updates causing havoc with certain stable hardware-specific focal fossa configurations, which had been working beautifully before the upgrade. My BT is killed, Wallch doesn’t work etc and there are no solutions forthcoming (the errors persist), may be until the 22.04 second point release. Even my Software Updater driven upgrade from Ubuntu 20.04 to 22.04 was not smooth - throwing up errors, which had to be resolved one after another. Not a pleasant upgrade experience, in any case.

9

There is now a Ubuntu 22.10
and, for those unfamiliar with Ubuntu, the version numbers are year and month (yy.mm)

I assume this means those waiting for problems in 22.04 to be fixed, will wait forever. The solution seems to be to move to even more recent releases. So why dont they call it rolling release and be honest about it?

10

22.04 that I have is a LTS release, whereas rolling release 22.10 is not; hence, compatibility issues can be expected and hours of troubleshooting to follow, with snap driving the software. Not worth it; better to stick to focal for a while

1 Like
11

This LTS business is a con. All you get is patches for somebodys security holes. Real fixes for things annoying users seem to only happen with the next fixed release, if at all.

You cant assume that a problem like yours with bluetooth is because the 22.04 release is too new. It might be too old. It might be because some disinterested or incompetent programmer or manager made a mistake.

What a fixed release distro like Ubuntu is… is a really slow rolling release, with ‘fake LTS’ bridging the gaps. You would be better off
with a well managed rolling release. I emphasize well managed. Then you would at least have a chance of getting bug fixes in a reasonable time.

If you dont like Ubuntu rolling, there are other well managed rolling release distros.

1 Like