"No Bluetooth Found" after upgrade from 6.3.12 to 6.4.4

The Gnome software app showed a system update available this morning which I executed. After the upgrade none of my bluetooth devices would connect. In Setting, the Bluetooth pane displays "No Bluetooth Found.

I ran up a terminal and got the bluetooth status from systemctl. It reports the bluetooth service is enabled and running.

I upgraded a second machine and observed exactly the same results. That machine is dual boot and displays a boot menu. It shows the most recent ‘version’ as 6.4.4. If I select the previous entry 6.3.12 and boot into that, bluetooth is available and working fine.

By comparing the results of systemctl status bluetooth on both machines I can see the results for 6.3.12 are different to what I’m seeing on 6.4.4. On the machine currently running 6.4.4 the status reports some additional lines.

Bluetooth daemon 5.68
Started bluetooth.service - Bluetooth service.
Starting SDP server
src/plugin.c:plugin_init() System does not support csip plugin
src/plugin.c:plugin_init() System does not support vcp plugin
src/plugin.c:plugin_init() System does not support mcp plugin
src/plugin.c:plugin_init() System does not support bass plugin
src/plugin.c:plugin_init() System does not support bap plugin

That’s about as far as my knowledge and skills will take me in troubleshooting this. I’m guessing I need to change permissions on a directory? Just not sure which directory or what the permissions should be. If anyone is able to point me in the right direction I’d really appreciate it. Hesitant to just start hacking away at things I don’t understand and making a bigger problem.

Thanks!

Please show us the result of lspci -nnk and the full output of systemctl status bluetooth.service > status.log both on the machine running 6.4.4.

Thanks Jeff

The results of lspci -nnk is below.

00:00.0 Host bridge [0600]: Intel Corporation Broadwell-U Host Bridge -OPI [8086:1604] (rev 09)
	DeviceName: SATA
	Subsystem: Apple Inc. Device [106b:011a]
	Kernel driver in use: bdw_uncore
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 6000 [8086:1626] (rev 09)
	Subsystem: Apple Inc. Device [106b:011a]
	Kernel driver in use: i915
	Kernel modules: i915
00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller [8086:160c] (rev 09)
	Subsystem: Apple Inc. Device [106b:011a]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:14.0 USB controller [0c03]: Intel Corporation Wildcat Point-LP USB xHCI Controller [8086:9cb1] (rev 03)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: xhci_hcd
00:15.0 DMA controller [0801]: Intel Corporation Wildcat Point-LP Serial IO DMA Controller [8086:9ce0] (rev 03)
	Subsystem: Intel Corporation Wildcat Point-LP Serial IO DMA Controller [8086:9ce0]
	Kernel driver in use: dw_dmac_pci
00:15.4 Serial bus controller [0c80]: Intel Corporation Wildcat Point-LP Serial IO GSPI Controller #1 [8086:9ce6] (rev 03)
	Subsystem: Intel Corporation Wildcat Point-LP Serial IO GSPI Controller #1 [8086:9ce6]
	Kernel driver in use: pxa2xx_spi_pci
	Kernel modules: spi_pxa2xx_pci
00:16.0 Communication controller [0780]: Intel Corporation Wildcat Point-LP MEI Controller #1 [8086:9cba] (rev 03)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: mei_me
	Kernel modules: mei_me
00:1b.0 Audio device [0403]: Intel Corporation Wildcat Point-LP High Definition Audio Controller [8086:9ca0] (rev 03)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 [8086:9c90] (rev e3)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root Port #2 [8086:9c92] (rev e3)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: pcieport
00:1c.2 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 [8086:9c94] (rev e3)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: pcieport
00:1c.4 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root Port #5 [8086:9c98] (rev e3)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: pcieport
00:1c.5 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root Port #6 [8086:9c9a] (rev e3)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: pcieport
00:1f.0 ISA bridge [0601]: Intel Corporation Wildcat Point-LP LPC Controller [8086:9cc3] (rev 03)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: lpc_ich
	Kernel modules: lpc_ich
00:1f.3 SMBus [0c05]: Intel Corporation Wildcat Point-LP SMBus Controller [8086:9ca2] (rev 03)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801
00:1f.6 Signal processing controller [1180]: Intel Corporation Wildcat Point-LP Thermal Management Controller [8086:9ca4] (rev 03)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: intel_pch_thermal
	Kernel modules: intel_pch_thermal
02:00.0 Multimedia controller [0480]: Broadcom Inc. and subsidiaries 720p FaceTime HD Camera [14e4:1570]
	Subsystem: Broadcom Inc. and subsidiaries 720p FaceTime HD Camera [14e4:1570]
03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03)
	Subsystem: Apple Inc. Device [106b:0117]
	Kernel driver in use: wl
	Kernel modules: bcma, wl
04:00.0 SATA controller [0106]: Samsung Electronics Co Ltd Device [144d:a801] (rev 01)
	Subsystem: Samsung Electronics Co Ltd Device [144d:a801]
	Kernel driver in use: ahci
05:00.0 PCI bridge [0604]: Intel Corporation DSL5320 Thunderbolt 2 Bridge [Falcon Ridge 2C 2013] [8086:156b]
	Kernel driver in use: pcieport
06:00.0 PCI bridge [0604]: Intel Corporation DSL5320 Thunderbolt 2 Bridge [Falcon Ridge 2C 2013] [8086:156b]
	Kernel driver in use: pcieport
06:03.0 PCI bridge [0604]: Intel Corporation DSL5320 Thunderbolt 2 Bridge [Falcon Ridge 2C 2013] [8086:156b]
	Kernel driver in use: pcieport
06:04.0 PCI bridge [0604]: Intel Corporation DSL5320 Thunderbolt 2 Bridge [Falcon Ridge 2C 2013] [8086:156b]
	Kernel driver in use: pcieport
06:05.0 PCI bridge [0604]: Intel Corporation DSL5320 Thunderbolt 2 Bridge [Falcon Ridge 2C 2013] [8086:156b]
	Kernel driver in use: pcieport
06:06.0 PCI bridge [0604]: Intel Corporation DSL5320 Thunderbolt 2 Bridge [Falcon Ridge 2C 2013] [8086:156b]
	Kernel driver in use: pcieport
07:00.0 System peripheral [0880]: Intel Corporation DSL5320 Thunderbolt 2 NHI [Falcon Ridge 2C 2013] [8086:156a]
	Kernel driver in use: thunderbolt
	Kernel modules: thunderbolt

I couldn’t see a way to attach the status.log file so I’ve reproduced the content of that file here.

● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Fri 2023-07-28 10:55:00 AEST; 5min ago
       Docs: man:bluetoothd(8)
   Main PID: 2924 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 9345)
     Memory: 2.0M
        CPU: 39ms
     CGroup: /system.slice/bluetooth.service
             └─2924 /usr/libexec/bluetooth/bluetoothd

Jul 28 10:55:00 pelorat (uetoothd)[2924]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Jul 28 10:55:00 pelorat bluetoothd[2924]: Bluetooth daemon 5.68
Jul 28 10:55:00 pelorat systemd[1]: Started bluetooth.service - Bluetooth service.
Jul 28 10:55:00 pelorat bluetoothd[2924]: Starting SDP server
Jul 28 10:55:00 pelorat bluetoothd[2924]: src/plugin.c:plugin_init() System does not support csip plugin
Jul 28 10:55:00 pelorat bluetoothd[2924]: src/plugin.c:plugin_init() System does not support vcp plugin
Jul 28 10:55:00 pelorat bluetoothd[2924]: src/plugin.c:plugin_init() System does not support mcp plugin
Jul 28 10:55:00 pelorat bluetoothd[2924]: src/plugin.c:plugin_init() System does not support bass plugin
Jul 28 10:55:00 pelorat bluetoothd[2924]: src/plugin.c:plugin_init() System does not support bap plugin
Jul 28 10:55:00 pelorat bluetoothd[2924]: Bluetooth management interface 1.22 initialized

I did not ask what hardware you have but it seems you have wifi with a broadcom BCM4360 which also normally provides the bluetooth.

Have you upgraded the broadcom-wl package with the new kernel?

It seems possible that a reboot too soon after the kernel update may have caused corruption in the driver for that card. Since broadcom-wl builds the driver as a kmod what does dnf list installed kmod* show?
Once you can identify the proper kmod-* package that is the drivers for that card then one may remove and rebuild it so one is sure the drivers were cleanly built and installed.
Removal is done with sudo dnf remove kmod-XXXX for the driver identified above.
Reinstall may be done with akmods --force and wait at least 5 minutes for the modules to be built and that kmod package be properly reinstalled before rebooting to load the new modules.

If everything is working as needed then bluetooth should be supported. If not then it seems likely that the driver may need updated for use with the newer kernel.

The installed kmod packages are:

kmod.x86_64
kmod-libs.x86_64
kmod-wl-6.3.11-200.fc38.x86_64.x86_64
kmod-wl-6.3.12-200.fc38.x86_64.x86_64
kmod-wl-6.4.4-200.fc38.x86_64.x86_64
kmodtool.noarch

So I’m guessing I’ll want to remove kmod-wl-6.4.4-200.fc38.x86_64.x86_64.

I removed the kmod-wl-6.4.4-200.fc38.x86_64.x86_64 package successfully and akmods --force found the 6.4.4 package to be rebuilt and successfully did so. I rebooted into the 6.4.4 kernel and I’m still not getting bluetooth working.

Should I have run the package removal and rebuild while running the 6.4.4 kernel?

I also seem to have this problem with bluetooth not behaving on 6.4.4 and 6.4.6, where it does on 6.3.12.

In my case I can’t connect reliably to my Bluetooth LE smartwatch. But connecting to my phone works fine. Sounds similar to this issue in that regard: https://www.dell.com/community/Linux-General/XPS-15-9575-2-in-1-Fedora-upgrade-Bluetooth-not-connecting/td-p/8419241

@sar6e Did you work something out?

I might supply more info on my problem. Please suggest what would be relevant in that case.

1 Like

6.4.7 fixed this for me

see https://discussion.fedoraproject.org/t/kernel-6-4-4-imac-bluetooth-module-no-longer-works

1 Like

Thanks for pointing me to your post!

However updating to and using 6.4.7 did not seem to help my situation. I’ll keep 6.3.12 around as a stable backup (using the method proposed in this comment).

Still having problems on 6.4.10.