Bluetooth stopped working in ubuntu 24.04.4 LTS

Support and Help
,
1

Ubuntu Support Template

Ubuntu Version:
Ubuntu 24.04.4 LTS, kernel: 6.17.0-20-generic

Desktop Environment (if applicable):
KDE Plasma

Problem Description:
Ubuntu can not find my Bluetooth device. It did before (few hours ago) and Windows can find it.


~$ hostnamectl
 Static hostname: xxx.xx.xx
       Icon name: computer-desktop
         Chassis: desktop
      Machine ID: 5555555555555555555555555555
         Boot ID: 444444444444444444444444444
Operating System: Ubuntu 24.04.4 LTS              
          Kernel: Linux 6.17.0-20-generic
    Architecture: x86-64
 Hardware Vendor: Gigabyte Technology Co., Ltd.
  Hardware Model: Z790 GAMING X AX
Firmware Version: F15
   Firmware Date: Mon 2025-12-01
    Firmware Age: 4month 1d

I did:

~$ sudo systemctl enable bluetooth
Synchronizing state of bluetooth.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install enable bluetooth
~$ sudo systemctl start bluetooth
~$ lsusb | grep -i bluetooth
Bus 001 Device 012: ID 8087:0032 Intel Corp. AX210 Bluetooth

I also just did:

$ sudo modprobe bluetooth
modprobe: FATAL: Module bluetooth not found in directory /lib/modules/6.17.0-20-generic

Before moving to the new kernel 6.17.0-20-generic my PC was running under Linux 6.14.0-37-generic. I just returned to this old kernel and all is back to normal.

I need to add that under “kernel: 6.17.0-20-generic” I also “lost” my sound card and had some problems with the network card used by a bridge which was having problems with its gateway server address.

If my memory serves I was also having problems with kernel 6.17.0-19-generic so I was forced again to stay with my old kernel.

Thanks in advance

2

dmesg | grep tooth

maybe you miss a patch

user@toshi:~$ dmesg | grep tooth
[    3.926983] toshiba_bluetooth: Toshiba ACPI Bluetooth device driver
[    4.562734] Bluetooth: Core ver 2.22
[    4.562793] Bluetooth: HCI device and connection manager initialized
[    4.562800] Bluetooth: HCI socket layer initialized
[    4.562804] Bluetooth: L2CAP socket layer initialized
[    4.562814] Bluetooth: SCO socket layer initialized
[    5.854159] Bluetooth: hci0: BCM: chip id 70
[    5.855152] Bluetooth: hci0: BCM: features 0x06
[    5.871191] Bluetooth: hci0: BCM43142A
[    5.871201] Bluetooth: hci0: BCM43142A0 (001.001.011) build 0000
[    5.873367] Bluetooth: hci0: BCM43142A0 'brcm/BCM43142A0-0930-0225.hcd' Patch
[    6.505629] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    6.505638] Bluetooth: BNEP filters: protocol multicast
[    6.505647] Bluetooth: BNEP socket layer initialized
[    6.534162] Bluetooth: hci0: BCM: features 0x06
[    6.550179] Bluetooth: hci0: Broadcom Bluetooth Device (43142)
[    6.550189] Bluetooth: hci0: BCM43142A0 (001.001.011) build 0334
[    6.604604] Bluetooth: MGMT ver 1.23
[    9.765369] Bluetooth: RFCOMM TTY layer initialized
[    9.765386] Bluetooth: RFCOMM socket layer initialized
[    9.765397] Bluetooth: RFCOMM ver 1.11
3

Have you updated the operating system by any chance? Was bluetooth working before the update?

You do not tell us therefore I am guessing that you are on Ubuntu/Kubuntu 24.04 LTS. I am also on Ubuntu 24.04 LTS. It has Linux kernel 6.17.0-19-generic. The information you have provided mentions Linux kernel 6.17.0-20-generic.

I have two suggestions to make.

a) run in the terminal and make a note of any error messages these two comannds

sudo apt update

sudo apt upgrade

b) at the Grub boot menu select Advanced Options for Ubuntu. That should show you 4 Linux kernels. Two kernels will be with recovery mode. The kernel top of the list should linux 6.17.0-20-generic. The third on the list should be Linux 6.17.0-19-generic. Choose 6.17.0-19-generic.

If that kernel loads to a desktop and bluetooth is now working then keep loading 6.17.0-19-generic until an update/upgrade updates the 6.17.0-20 generic kernel.

Regards

4

My experience is that you need to press some button on the device to initiate “broadcast for detection”, which does timeout after a while.

Could the timeout factor be an issue here, not resolving the connection handshake before timeout?

5

Sounds like an issue with the new kernel install, might want to check in terminal dpkg -l|grep linux-modules-extra and see if it shows one for 6.17.0-20

1 Like