Arch Linux

Sivar

Member

From: Poiand

Registered: 2025-07-02

Posts: 2

[SOLVED] Bluetooth is not detected after kernel update

Hello!
I have problem with my bluetooth device and I could use some help with fixing it. I'm running Arch Linux only, no other systems are installed, so no Windows mess here.
Device itself is part of my motherboard - ASRock X870 RIPTIDE WIFI
It worked without any issue since I've installed the system to the week ago, when I did system update. From that point it is no longer detected in my system.
Packages bluedevil, bluez, bluez-utils are installed and are in newest versions available
Bluetooth service is dead on boot and I can start it only if I execute bluetoothctl first (my guess is it loads module to the kernel?) - it does not connect to bluetoothd, but then I can start bluetooth service. After that bluetoothctl does connect to the bluetoothd, but list does not return any controllers.
It is not visible by any command. Like the device is not there. I did not yet test it with live usb to check if it is still alive - but it was responding just before the update, so I assume that (hopefully) the hardware is not damaged.

systemctl status bluetooth.service returns:

○ bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: inactive (dead)
       Docs: man:bluetoothd(8)

paź 02 23:38:46 hulk systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
paź 02 23:38:48 hulk systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
paź 02 23:38:48 hulk systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
paź 02 23:38:49 hulk systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).

After starting bluetooth.service as mentioned above:

● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Thu 2025-10-02 22:48:15 CEST; 15min ago
 Invocation: a4e75c5ede694e9da531a8805675ca0a
       Docs: man:bluetoothd(8)
   Main PID: 20958 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 73816)
     Memory: 632K (peak: 2.3M)
        CPU: 13ms
     CGroup: /system.slice/bluetooth.service
             └─20958 /usr/lib/bluetooth/bluetoothd

paź 02 22:48:15 hulk systemd[1]: Starting Bluetooth service...
paź 02 22:48:15 hulk bluetoothd[20958]: Bluetooth daemon 5.84
paź 02 22:48:15 hulk systemd[1]: Started Bluetooth service.
paź 02 22:48:15 hulk bluetoothd[20958]: Starting SDP server
paź 02 22:48:15 hulk bluetoothd[20958]: Bluetooth management interface 1.23 initialized

Full pacman logs from that day: https://pastebin.pl/view/embed/f5352cf2
Packages updated that I think might be related to my issue:

[2025-09-26T22:54:36+0200] [ALPM] upgraded bluez (5.83-1 -> 5.84-1)
[2025-09-26T22:54:36+0200] [ALPM] upgraded bluez-libs (5.83-1 -> 5.84-1)
[2025-09-26T22:54:36+0200] [ALPM] upgraded bluez-utils (5.83-1 -> 5.84-1)
[2025-09-26T22:54:39+0200] [ALPM] upgraded linux-headers (6.16.7.arch1-1 -> 6.16.8.arch3-1)
[2025-09-26T22:54:39+0200] [ALPM] upgraded linux-lts (6.12.47-1 -> 6.12.49-1)
[2025-09-26T22:54:40+0200] [ALPM] upgraded linux-lts-headers (6.12.47-1 -> 6.12.49-1)

journalctl -b

paź 02 22:06:38 hulk kernel: Linux version 6.16.8-arch3-1 (linux@archlinux) (gcc (GCC) 15.2.1 20250813, GNU ld (GNU Binutils) 2.45.0) #1 SMP PREEMPT_DYNAMIC Mon, 22 Sep 2025 22:08:35 +0000
paź 02 22:06:38 hulk kernel: Command line: root=PARTUUID=a8a80b1d-c357-43fc-88fa-54439c76861e zswap.enabled=0 rw rootfstype=ext4
paź 02 22:06:38 hulk kernel: x86/split lock detection: #DB: warning on user-space bus_locks
paź 02 22:06:38 hulk kernel: BIOS-provided physical RAM map:
paź 02 22:06:38 hulk kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
paź 02 22:06:38 hulk kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
paź 02 22:06:38 hulk kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009afefff] usable
paź 02 22:06:38 hulk kernel: BIOS-e820: [mem 0x0000000009aff000-0x0000000009ffffff] reserved
paź 02 22:06:38 hulk kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
paź 02 22:06:38 hulk kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a21dfff] ACPI NVS
paź 02 22:06:38 hulk kernel: BIOS-e820: [mem 0x000000000a21e000-0x000000000affffff] usable
paź 02 22:06:38 hulk kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b020fff] reserved
paź 02 22:06:38 hulk kernel: BIOS-e820: [mem 0x000000000b021000-0x000000008527efff] usable
paź 02 22:06:38 hulk kernel: BIOS-e820: [mem 0x000000008527f000-0x000000008b27efff] reserved
paź 02 22:06:38 hulk kernel: BIOS-e820: [mem 0x000000008b27f000-0x000000008d27efff] ACPI data
paź 02 22:06:38 hulk kernel: BIOS-e820: [mem 0x000000008d27f000-0x000000008f27efff] ACPI NVS
paź 02 22:06:38 hulk kernel: BIOS-e820: [mem 0x000000008f27f000-0x00000000973fefff] reserved
paź 02 22:06:38 hulk kernel: BIOS-e820: [mem 0x00000000973ff000-0x0000000099ff6fff] usable
paź 02 22:06:38 hulk kernel: BIOS-e820: [mem 0x0000000099ff7000-0x0000000099ffbfff] reserved
paź 02 22:06:38 hulk kernel: BIOS-e820: [mem 0x0000000099ffc000-0x0000000099ffffff] usable
paź 02 22:06:38 hulk kernel: BIOS-e820: [mem 0x000000009a000000-0x000000009bffffff] reserved
paź 02 22:06:38 hulk kernel: BIOS-e820: [mem 0x000000009d7f3000-0x000000009fffffff] reserved
paź 02 22:06:38 hulk kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
paź 02 22:06:38 hulk kernel: BIOS-e820: [mem 0x00000000f7000000-0x00000000ffffffff] reserved
paź 02 22:06:38 hulk kernel: BIOS-e820: [mem 0x0000000100000000-0x0000000fddd7ffff] usable
paź 02 22:06:38 hulk kernel: BIOS-e820: [mem 0x0000000fdedc0000-0x00000010801fffff] reserved
paź 02 22:06:38 hulk kernel: BIOS-e820: [mem 0x000000fd00000000-0x000000ffffffffff] reserved
paź 02 22:06:38 hulk kernel: NX (Execute Disable) protection: active
paź 02 22:06:38 hulk kernel: APIC: Static calls initialized
paź 02 22:06:38 hulk kernel: efi: EFI v2.9 by American Megatrends
paź 02 22:06:38 hulk kernel: efi: ACPI=0x8f265000 ACPI 2.0=0x8f265014 TPMFinalLog=0x8f232000 SMBIOS=0x970ce000 SMBIOS 3.0=0x970cd000 MEMATTR=0x7ef61698 ESRT=0x7f3f2c18 RNG=0x8c512f18 INITRD=0x7c6aa618 TPMEventLog=0x8c510018 
paź 02 22:06:38 hulk kernel: random: crng init done

dmesg: https://pastebin.pl/view/1c5bffdf
Bluetooth is mentioned only at the very end:

[  549.593689] Bluetooth: Core ver 2.22
[  549.593713] NET: Registered PF_BLUETOOTH protocol family
[  549.593714] Bluetooth: HCI device and connection manager initialized
[  549.593717] Bluetooth: HCI socket layer initialized
[  549.593719] Bluetooth: L2CAP socket layer initialized
[  549.593722] Bluetooth: SCO socket layer initialized
[  569.381616] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[  569.381619] Bluetooth: BNEP filters: protocol multicast
[  569.381622] Bluetooth: BNEP socket layer initialized
[ 1328.420855] usbcore: registered new interface driver btusb

lsusb:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 001 Device 003: ID 26ce:0a08 Generic USB Audio
Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 009: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 010: ID 1852:7022 GYROCOM C&C Co., LTD Fiio E10
Bus 001 Device 011: ID 3434:d030 Keychron  Keychron Link 
Bus 001 Device 012: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 002: ID 26ce:01a2 ASRock LED Controller
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

rfkill list returns only this:

0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

lspci -k: https://pastebin.pl/view/093c8f51
lsmod: https://pastebin.pl/view/5d5218eb
modinfo btusb: https://pastebin.pl/view/1b35c96a

I'm not sure if I can provide any more informations - if anything else could be helpful please let me know.
Thank you in advance! :)

Last edited by Sivar (2025-10-03 22:21:48)

LuxFerre

Member

Registered: 2010-03-01

Posts: 87

Re: [SOLVED] Bluetooth is not detected after kernel update

Do you have fast boot enabled in the bios? If so, try disabling it.
Is the wifi working? I think in these motherboards the wifi and bt are in the same card...

Sivar

Member

From: Poiand

Registered: 2025-07-02

Posts: 2

Re: [SOLVED] Bluetooth is not detected after kernel update

Do you have fast boot enabled in the bios? If so, try disabling it.
Is the wifi working? I think in these motherboards the wifi and bt are in the same card...

Fast Boot was enabled, but it was from the start. I did disabled it, sadly nothing has changed.
Yes, WiFi is working as expected. No issues here. Both WiFi and Bluetooth are on Mediatek MT7925.

I've tried to add mt7925e.disable_aspm=1 to the /boot/loader/entries/arch.conf as suggested here:
https://bbs.archlinux.org/viewtopic.php?id=306366
No results either.

Edit:
Well, I was getting quite desperate, and decided to give a try the other advice from this thread: i unplugged the PC from outlet, hit the power button and then powered it back on. Initially I've assumed that this shouldn't change anything but... Well, I have Bluetooth now. And I've become much more humble with my assumptions for sure.

Last edited by Sivar (2025-10-03 22:54:40)