Bluetooth stoped working after update to Fedora 41 Workstation Edition

Ask Fedora
1

My Bluetooth headphones worked fine under Fedora 40, but now it shows Bluetooth as not enabled with message to “plug in a dongle to use Bluetooth.”

Any suggestions?

2

Welcome to Fedora @rbjolly

It looks like that you have to do some adjustments with your drivers.

Can you please make a inxi -Fzxx in the terminal and post the output as pre formated text (</>), pls.

3

I’m not entirely sure if it is a driver issue. I dual boot between Fedora and Windows 11 and after posting this question I got the bright idea to boot into Windows and see if Bluetooth still worked, but it no longer does. So possibly a hardware failure has occurred. But here is the output of the inxi command:


System:
  Kernel: 6.11.5-300.fc41.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.43.1-2.fc41
  Desktop: GNOME v: 47.1 tk: GTK v: 3.24.43 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 41 (Workstation Edition)
Machine:
  Type: Desktop System: Micro (HK) Tech product: Venus Series v: N/A
    serial: <superuser required>
  Mobo: Shenzhen Meigao Equipment model: AHBTB serial: <superuser required>
    UEFI: American Megatrends LLC. v: 1.06 date: 02/19/2024
CPU:
  Info: 14-core (6-mt/8-st) model: 12th Gen Intel Core i9-12900HK bits: 64
    type: MST AMCP arch: Alder Lake rev: 3 cache: L1: 1.2 MiB L2: 11.5 MiB
    L3: 24 MiB
  Speed (MHz): avg: 400 min/max: 400/4900:5000:3800 cores: 1: 400 2: 400
    3: 400 4: 400 5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400
    13: 400 14: 400 15: 400 16: 400 17: 400 18: 400 19: 400 20: 400
    bogomips: 116736
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Alder Lake-P GT2 [Iris Xe Graphics] driver: i915 v: kernel
    arch: Gen-12.2 ports: active: DP-1 empty: DP-2,HDMI-A-1 bus-ID: 00:02.0
    chip-ID: 8086:46a6
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.3
    compositor: gnome-shell driver: gpu: i915 display-ID: 0
  Monitor-1: DP-1 model: Dell U2412M res: 1920x1200 dpi: 94
    diag: 611mm (24.1")
  API: OpenGL v: 4.6 vendor: intel mesa v: 24.2.5 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: Mesa Intel Graphics (ADL GT2)
    device-ID: 8086:46a6 display-ID: :0.0
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: Intel Alder Lake PCH-P High Definition Audio vendor: Realtek
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:51c8
  API: ALSA v: k6.11.5-300.fc41.x86_64 status: kernel-api
  Server-1: JACK v: 1.9.22 status: off
  Server-2: PipeWire v: 1.2.6 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
  Device-1: Intel Ethernet I226-V driver: igc v: kernel pcie: speed: 5 GT/s
    lanes: 1 port: N/A bus-ID: 02:00.0 chip-ID: 8086:125c
  IF: enp2s0 state: down mac: <filter>
  Device-2: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter
    driver: mt7921e v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 03:00.0
    chip-ID: 14c3:7961
  IF: wlp3s0 state: up mac: <filter>
Drives:
  Local Storage: total: 1.38 TiB used: 110.53 GiB (7.8%)
  ID-1: /dev/nvme0n1 vendor: Kingston model: OM8PGP4512Q-A0 size: 476.94 GiB
    speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 18.9 C
  ID-2: /dev/sda vendor: Samsung model: SSD 870 EVO 1TB size: 931.51 GiB
    speed: 6.0 Gb/s serial: <filter>
Partition:
  ID-1: / size: 904 GiB used: 110.51 GiB (12.2%) fs: ext4 dev: /dev/sda2
  ID-2: /boot/efi size: 11.99 GiB used: 19.4 MiB (0.2%) fs: vfat
    dev: /dev/sda1
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 40.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 32 GiB note: est. available: 31.07 GiB used: 5.29 GiB (17.0%)
  Processes: 417 Power: uptime: 6h 16m wakeups: 1 Init: systemd v: 256
    target: graphical (5) default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 96
    Compilers: N/A Shell: Bash v: 5.2.32 running-in: gnome-terminal inxi: 3.3.36
4

let’s see.

With rfkill you can find out if the device is blocked by hardware or software:
https://linuxconfig.org/how-to-manage-wifi-interfaces-with-rfkill-command-on-linux #works also for bluetooth

On this topic you find useful commands the user posted on his Bluetooth problem. This info might help us to debug your machine, like:

#every single line is a command to execute in the terminal.

sudo systemctl status bluetooth

bluetoothctl

lsusb | grep Bluetooth

lspci -nnk | grep -A3 -i network

rfkill

sudo dmesg | grep hci0
1 Like
5

I’m fairly sure at this point that it is a hardware failure. Booting is taking longer and even in Windows Device Manager, I have a USB device that is flagged as not working. Previously, Bluetooth worked on both Fedora and Windows, but now it is not working at all on either. Also, previously, I had done a hardware probe in Fedora. This probe reports the presence of a Bluetooth device (USB). The latest probe shows no device. Plus, I can see no setting in the BIOS to turn the Bluetooth device on/off so it is probably a failed device.

6

Might be kernel issues that might be fixed on 6.12 worth to try or downgrade to 6.10 where it was working to debug is it hardware or kernel

7

Please do a rfkill, this will show if the Bluetooth device is hard or soft blocked. I remember to read that one OS can block and then in both it is not visible?

$ rfkill
ID TYPE      DEVICE    SOFT      HARD
 0 wlan      phy0   blocked unblocked
 1 bluetooth hci0   blocked unblocked

The Hard blocked is that what I am talk about.