Did anyone figure out the cause of bluetooth not working after kernel 6.11.2?

Issues & Assistance
1

I have 3 pc’s running garuda…on the one I am including the garuda-inxi for bluetooth has not worked for quite some time…adding a 2nd bluetooth dongle makes no difference…attempting to pair shows a blank screen with no devices.

On the 2nd machine bluetooth works fine even with newer kernels but it uses the ancient bubblebee bluetooth driver.

On the 3rd pc (laptop) bluetooth is via a dongle…on it when first trying to use bluetooth it acts just like the first pc BUT if I pull the dongle and replug it back in then the adapter starts working as it’s supposed to. Sadly I have no way to recreate it on pc #1 which is a mini pc and as mentioned even putting the dongle on pc #1 and selecting that adapter in bluetooth does not remedy the issue.

System:
  Kernel: 6.13.0-rc2-1-mainline-x64v3 arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: acpi_pm parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-mainline-x64v3
    root=UUID=5ad7fecd-1a14-4590-8ce1-42685c5ee6c8 rw rootflags=subvol=@ quiet
    rd.luks.uuid=2bdec0d6-999c-4a5a-9278-70a5c8e236d9 loglevel=3 ibt=off
  Desktop: KDE Plasma v: 6.2.4 tk: Qt v: N/A info: frameworks v: 6.8.0 wm: kwin_wayland
    with: krunner vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Desktop Mobo: N/A model: N/A serial: <superuser required> uuid: <superuser required>
    UEFI: American Megatrends LLC. v: AM08ProP01_P5C5V14 date: 08/11/2023
Battery:
  Device-1: hidpp_battery_7 model: Logitech M570 serial: <filter> charge: 95% rechargeable: yes
    status: discharging
CPU:
  Info: model: AMD Ryzen 7 7735HS with Radeon Graphics bits: 64 type: MT MCP arch: Zen 3+ gen: 3
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25) model-id: 0x44 (68)
    stepping: 1 microcode: 0xA404102
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 3786 min/max: 400/4829 boost: enabled scaling: driver: amd-pstate-epp
    governor: performance cores: 1: 3786 2: 3786 3: 3786 4: 3786 5: 3786 6: 3786 7: 3786 8: 3786
    9: 3786 10: 3786 11: 3786 12: 3786 13: 3786 14: 3786 15: 3786 16: 3786 bogomips: 102245
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Rembrandt [Radeon 680M] driver: amdgpu v: kernel
    arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s
    lanes: 16 ports: active: HDMI-A-1 empty: DP-1, DP-2, DP-3, DP-4, DP-5, HDMI-A-2, Writeback-1
    bus-ID: e5:00.0 chip-ID: 1002:1681 class-ID: 0300 temp: 67.0 C
  Device-2: Sunplus Innovation Full HD webcam driver: snd-usb-audio,uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-1.1.4.2:13 chip-ID: 1bcf:2284 class-ID: 0102
    serial: <filter>
  Display: wayland server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4 compositor: kwin_wayland
    driver: X: loaded: amdgpu unloaded: modesetting alternate: fbdev,vesa dri: radeonsi gpu: amdgpu
    display-ID: 0
  Monitor-1: HDMI-A-1 res: 2752x1152 size: N/A modes: N/A
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi device: 1 drv: swrast
    gbm: drv: kms_swrast surfaceless: drv: radeonsi wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.3.1-arch1.3 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon 680M (radeonsi rembrandt LLVM 18.1.8 DRM 3.59
    6.13.0-rc2-1-mainline-x64v3) device-ID: 1002:1681 memory: 3.91 GiB unified: no display-ID: :1.0
  API: Vulkan v: 1.4.303 layers: 4 device: 0 type: integrated-gpu name: AMD Radeon 680M (RADV
    REMBRANDT) driver: N/A device-ID: 1002:1681 surfaces: xcb,xlib,wayland device: 1 type: cpu
    name: llvmpipe (LLVM 18.1.8 256 bits) driver: N/A device-ID: 10005:0000
    surfaces: xcb,xlib,wayland
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Rembrandt Radeon High Definition Audio
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: e5:00.1
    chip-ID: 1002:1640 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] ACP/ACP3X/ACP6x Audio Coprocessor driver: snd_pci_acp6x
    v: kernel alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_acp_pci,
    snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh,
    snd_sof_amd_acp63, snd_sof_amd_acp70 pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: e5:00.5
    chip-ID: 1022:15e2 class-ID: 0480
  Device-3: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio driver: snd_hda_intel
    v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: e5:00.6 chip-ID: 1022:15e3 class-ID: 0403
  Device-4: Sunplus Innovation Full HD webcam driver: snd-u
sb-audio,uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-1.1.4.2:13 chip-ID: 1bcf:2284 class-ID: 0102
    serial: <filter>
  API: ALSA v: k6.13.0-rc2-1-mainline-x64v3 status: kernel-api tools: N/A
  Server-1: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8125 2.5GbE driver: r8169 v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
    port: f000 bus-ID: 02:00.0 chip-ID: 10ec:8125 class-ID: 0200 temp: 68.5 C
  IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Realtek RTL8852BE PCIe 802.11ax Wireless Network driver: rtw89_8852be v: kernel pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 03:00.0 chip-ID: 10ec:b852 class-ID: 0280
  IF: wlp3s0 state: down mac: <filter>
  Info: services: NetworkManager, smbd, sshd, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.0 speed: 12 Mb/s lanes: 1
    mode: 1.1 bus-ID: 3-3:3 chip-ID: 0bda:b85b class-ID: e001 serial: <filter>
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2 lmp-v: 11 status:
    discoverable: no pairing: no class-ID: 6c0104
Drives:
  Local Storage: total: 2.77 TiB used: 1.08 TiB (38.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Intel model: SSDPEKNU020TZ size: 1.86 TiB block-size:
    physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: 003C
    temp: 72.8 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Crucial model: CT1000MX500SSD1 size: 931.51 GiB block-size:
    physical: 4096 B logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 043
    scheme: GPT
Partition:
  ID-1: / raw-size: 1.86 TiB size: 1.86 TiB (100.00%) used: 1.08 TiB (57.9%) fs: btrfs
    dev: /dev/dm-0 maj-min: 254:0 mapped: luks-2bdec0d6-999c-4a5a-9278-70a5c8e236d9
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 728 KiB (0.2%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 1.86 TiB size: 1.86 TiB (100.00%) used: 1.08 TiB (57.9%) fs: btrfs
    dev: /dev/dm-0 maj-min: 254:0 mapped: luks-2bdec0d6-999c-4a5a-9278-70a5c8e236d9
  ID-4: /var/log raw-size: 1.86 TiB size: 1.86 TiB (100.00%) used: 1.08 TiB (57.9%) fs: btrfs
    dev: /dev/dm-0 maj-min: 254:0 mapped: luks-2bdec0d6-999c-4a5a-9278-70a5c8e236d9
  ID-5: /var/tmp raw-size: 1.86 TiB size: 1.86 TiB (100.00%) used: 1.08 TiB (57.9%) fs: btrfs
    dev: /dev/dm-0 maj-min: 254:0 mapped: luks-2bdec0d6-999c-4a5a-9278-70a5c8e236d9
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 27.15 GiB used: 17.6 GiB (64.8%) priority: 100 comp: zstd
    avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 16 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 77.0 C mobo: 75.5 C gpu: amdgpu temp: 68.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 28 GiB available: 27.15 GiB used: 24.37 GiB (89.8%)
  Processes: 488 Power: uptime: 3d 1h 21m states: freeze,mem,disk suspend: s2idle wakeups: 0
    hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 10.85 GiB
    services: org_kde_powerdevil, power-profiles-daemon, upowerd Init: systemd v: 257
    default: graphical tool: systemctl
  Packages: 1620 pm: pacman pkgs: 1610 libs: 398 tools: octopi,paru pm: flatpak pkgs: 10
    Compilers: clang: 18.1.8 gcc: 14.2.1 Client: shell wrapper v: 5.2.37-release inxi: 3.3.36
Garuda (2.6.26-1):
  System install date:     2024-09-26
  Last full system update: 2024-12-13 ↻
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:
2

No bluetooth issues over here. :man_shrugging: I do not have a Realtek device though; maybe there is a kernel regression affecting your specific hardware.

This looks good actually. The btusb driver is loaded, the interface is up…looks like the device is not discoverable though. Have you tried getting it going with bluetoothctl?

Like this for example: Bluetooth headset - ArchWiki

bluetoothctl
[bluetooth]# power on
[bluetooth]# agent on
[bluetooth]# default-agent
[bluetooth]# scan on

Find the device you want to pair with and get the MAC address.

[bluetooth]# [NEW] Device 00:02:3C:BC:1A:E4 Sound Blaster JAM V2

Pair with the device and connect to it using the MAC address.

[bluetooth]# pair 00:02:3C:BC:1A:E4
[bluetooth]# connect 00:02:3C:BC:1A:E4

Optionally, you can trust if you want it to connect automatically in the future.

[bluetooth]# trust 00:02:3C:BC:1A:E4

If you run into any errors, paste them into the thread so we can take a look. Maybe there will be a clue as to what the problem is.

1 Like
3

Same as with the gui…no results found…and there are several on the pc that works from my smart watch to the roku sound bar I’m trying to connect to.

╭─famewolf@KAM08Pro in /etc/sysctl.d🔒 as 🧙 took 1m43s
╰─λ bluetoothctl
[bluetooth]# Agent registered
[bluetooth]# power on
[bluetooth]# Changing power on succeeded
[bluetooth]# agent on
Agent is already registered
[bluetooth]# default-agent
[bluetooth]# Default agent request successful
[bluetooth]# scan on
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# Discovery started
[bluetooth]# [CHG] Controller A8:43:A4:4B:3D:9F Discovering: yes
[bluetooth]#

On the pc next to it that has working bluetooth:

╭─famewolf@hp810-135qe in ~ as 🧙 took 56s
╰─λ bluetoothctl
[TCL Alto 6]# Agent registered
[TCL Alto 6]# scan on
[TCL Alto 6]# SetDiscoveryFilter success
[TCL Alto 6]# Discovery started
[TCL Alto 6]# [CHG] Controller 8C:88:2B:21:02:92 Discovering: yes
[TCL Alto 6]# [NEW] Device E0:B6:55:82:5B:7B MIBOX4
[TCL Alto 6]# exit
4

Strange!

Just curious: does Bluetooth work if you switch to the hardened kernel? (6.11.11)

sudo pacman -S linux-hardened linux-hardened-headers
1 Like
5

I have not tried hardened in particular but I’ve tried linux-zen, linux-zen3, mainline, linux-x86_64v3, and lts…none of those made a difference. I think if I had a snapshot to restore back to 6.11.2 and then upgraded to a newer kernel bluetooth might stay working like it did on the 2nd pc or if I had a way to fully “turn off and then back on” the adapter like pc #3 where pulling the dongle and re-plugging it back in it would work.

6

You could try to unload the module, then reload it.

sudo modprobe -r btusb
sudo modprobe btusb
1 Like
7 
╭─famewolf@KAM08Pro in /etc/sysctl.d🔒 as 🧙 took 3s
╰─λ sudo modprobe -r btusb

╭─famewolf@KAM08Pro in /etc/sysctl.d🔒 as 🧙 took 0s
╰─λ sudo modprobe btusb

╭─famewolf@KAM08Pro in /etc/sysctl.d🔒 as 🧙 took 0s
╰─λ bluetoothctl
[bluetooth]# Agent registered
[bluetooth]# scan on
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# Discovery started
[bluetooth]# [CHG] Controller A8:43:A4:4B:3D:9F Discovering: yes
[bluetooth]#

I left it running for quite a while…in fact it’s still running…no results.

8

Perhaps it is a hardware issue rather than a kernel issue, since it sounds like going back to 6.6 does not help.

I have not seen any other reports of this issue in the forums. Have you?

1 Like
9

Possible but it worked on kernel 6.11.2 and not on 6.11.3. Sadly I held out for an answer and let my older snapshots roll off and reinstalling 6.11.2 kernel does not seem to be sufficient. At the time I saw several posts regarding bluetooth not working here on the forum with folks rolling back snapshots to get it working again. I could always boot off the live iso from april to confirm the hardware is fine.

I’m assuming a config or something similar was updated to a condition that doesn’t work which is why just changing the kernel is not sufficient. This would explain why some people were able to install newer kernel’s and still have working bluetooth…if their config file had been customized it would not have been upgraded.

10

As a workaround I was able to get another usb dongle working on the mini pc after making the built in one unenabled and not visible.

11

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.