[SOLVED] No bluetooth adaptater on AX200

Xephobia · 2021-12-29 11:22:41

Hello, I have an AX200 card, and at some point after an upgrade (i don't remember which one), the Bluetooth stopped working. I have seen this could be caused by windows fast boot, but I don't have windows dual booted.
Kernel : 5.15.11-xanmod1-1
linux-firmware : most recent, the bug is also present on linux-firmware-git (AUR)

sudo dmesg | grep firm:

[    0.071602] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    3.999096] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-66.ucode failed with error -2
[    3.999120] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-65.ucode failed with error -2
[    3.999137] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-64.ucode failed with error -2
[    4.001626] iwlwifi 0000:04:00.0: loaded firmware version 63.c04f3485.0 cc-a0-63.ucode op_mode iwlmvm
[    4.106003] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[    4.215555] [drm] Loading DMUB firmware via PSP: version=0x0101001C
[    4.216415] [drm] Found VCN firmware Version ENC: 1.16 DEC: 5 VEP: 0 Revision: 3
[    4.216424] amdgpu 0000:05:00.0: amdgpu: Will use PSP to load VCN firmware
[  228.961879] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi

sudo rfkill list :

0: ideapad_wlan: Wireless LAN
	Soft blocked: no
	Hard blocked: no
1: ideapad_bluetooth: Bluetooth
	Soft blocked: no
	Hard blocked: no
3: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
4: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

bluetoothctl power on:
No default controller available

Any help would be appreciated.

Last edited by Xephobia (2022-01-03 16:27:17)

lula · 2021-12-29 12:16:30

There are many reports about bluetooth not working with kernel 5.15 and Intel hardware, e.g.

https://bbs.archlinux.org/viewtopic.php?id=271459

The workaround for me is to boot to linux-lts kernel

I've created a bug report https://bugs.archlinux.org/task/73151, you probably want to comment there

Xephobia · 2022-01-02 18:45:49

Hello, sorry for necro bumping, but with the kernel regressed to LTS, it still fails (worked for a bit of time)

jonno2002 · 2022-01-02 23:45:33

this may help: https://bbs.archlinux.org/viewtopic.php?id=272698

Xyne · 2022-01-03 05:50:50

Xephobia wrote:

Hello, sorry for necro bumping,

Replying to a 4-day-old thread is not necro-bumping, even if it's from last year
"Necrobumping" is replying months or years after the last post, and long after the discussion has reached its end.

Xephobia · 2022-01-03 14:56:55

jonno2002 wrote:

this may help: https://bbs.archlinux.org/viewtopic.php?id=272698

This didnt help, It is outputting "No default controller available"

seth · 2022-01-03 15:21:58

We may need to establish what "does not work" means - there's an unblocked controller in the rfkill output. But the double FW load looks suspicous (module might have crashed)

bluetoothctl show
lsusb
lspci
sudo journalctl -b | curl -F 'f:1=<-' ix.io

Xephobia · 2022-01-03 15:38:20

seth wrote:

We may need to establish what "does not work" means - there's an unblocked controller in the rfkill output. But the double FW load looks suspicous (module might have crashed)
bluetoothctl show
lsusb
lspci
sudo journalctl -b | curl -F 'f:1=<-' ix.io

[(16:36:43)xeph:~]bluetoothctl show
No default controller available
[(16:36:45)xeph:~]lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth
Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 048d:c101 Integrated Technology Express, Inc. ITE Device(8910)
Bus 001 Device 003: ID 13d3:56ff IMC Networks Integrated Camera
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[(16:36:53)xeph:~]lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166a
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166b
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166c
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166d
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166e
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166f
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1670
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1671
01:00.0 VGA compatible controller: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] (rev a1)
01:00.1 Audio device: NVIDIA Corporation Device 228e (rev a1)
02:00.0 Non-Volatile memory controller: SK hynix Device 174a
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
04:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne (rev c6)
05:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor
05:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1
05:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1
05:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller
06:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81)
06:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81)
[(16:37:08)xeph:~]sudo journalctl -b | curl -F 'f:1=<-' ix.io
[sudo] password for xeph: 
http://ix.io/3KRB

seth · 2022-01-03 16:00:42

What if you disable bluetooth-meshd ?

Xephobia · 2022-01-03 16:19:49

seth wrote:

What if you disable bluetooth-meshd ?

[(17:10:17)xeph:~]sudo systemctl disable bluetooth-mesh.service
[sudo] password for xeph: 
Removed /etc/systemd/system/bluetooth.target.wants/bluetooth-mesh.service.
Removed /etc/systemd/system/dbus-org.bluez.mesh.service.
[(17:16:10)xeph:~]./btrestart.sh
No default controller available

there is no bluetooth-meshd service, nor an executable with this name

Xephobia · 2022-01-03 16:24:51

With a restart, it works! Thanks a lot, I should mark this as solved.

greenfoo · 2022-01-04 21:27:02

In case this helps someone:

I was also having the same problem. Ie. after an upgrade ("pacman -Syu") and a reboot ("systemctl reboot"), the bluetooth controller was "gone" ("bluetoothctl show" would reply with "No default controller available").

Now... the interesting things comes next: no matter how many times I rebooted ("systemctl reboot"), the problem would persist **but** as soon as I did the first power off ("systemctl poweroff" + manually press the power button to turn it on again), bluetooth would work once again and never fail from that point on.

This had already happened to me a few months ago. Back then, I only ran "systemctl reboot" twice before running "systemctl poweroff", so I was not sure if this was what fixed the issue. This time, however, I wanted to confirm my theory, so I ran "systemctl reboot" 5 times (none of which worked) before the final "systemctl poweroff" that fixed the issue.

"Reboot" and "Power off" seem to affect the hardware in different ways. Maybe the reset signal used by "Reboot" is not completely wiping out the bluetooth firmware and this interfers with the firmware loading process performed by the kernel? Who knows...

In any case, more people have experienced this issue (see here --> https://bbs.archlinux.org/viewtopic.php … #p2006904) and kernel developers are already aware (see here --> https://bugzilla.kernel.org/show_bug.cgi?id=215167).

lphrgg · 2024-05-01 09:43:29

greenfoo wrote:

In case this helps someone:
I was also having the same problem. Ie. after an upgrade ("pacman -Syu") and a reboot ("systemctl reboot"), the bluetooth controller was "gone" ("bluetoothctl show" would reply with "No default controller available").
Now... the interesting things comes next: no matter how many times I rebooted ("systemctl reboot"), the problem would persist **but** as soon as I did the first power off ("systemctl poweroff" + manually press the power button to turn it on again), bluetooth would work once again and never fail from that point on.
This had already happened to me a few months ago. Back then, I only ran "systemctl reboot" twice before running "systemctl poweroff", so I was not sure if this was what fixed the issue. This time, however, I wanted to confirm my theory, so I ran "systemctl reboot" 5 times (none of which worked) before the final "systemctl poweroff" that fixed the issue.
"Reboot" and "Power off" seem to affect the hardware in different ways. Maybe the reset signal used by "Reboot" is not completely wiping out the bluetooth firmware and this interfers with the firmware loading process performed by the kernel? Who knows...
In any case, more people have experienced this issue (see here --> https://bbs.archlinux.org/viewtopic.php … #p2006904) and kernel developers are already aware (see here --> https://bugzilla.kernel.org/show_bug.cgi?id=215167).

it works lol! wtf)

Arch Linux

#1 2021-12-29 11:22:41

[SOLVED] No bluetooth adaptater on AX200

#2 2021-12-29 12:16:30

Re: [SOLVED] No bluetooth adaptater on AX200

#3 2022-01-02 18:45:49

Re: [SOLVED] No bluetooth adaptater on AX200

#4 2022-01-02 23:45:33

Re: [SOLVED] No bluetooth adaptater on AX200

#5 2022-01-03 05:50:50

Re: [SOLVED] No bluetooth adaptater on AX200

#6 2022-01-03 14:56:55

Re: [SOLVED] No bluetooth adaptater on AX200

#7 2022-01-03 15:21:58

Re: [SOLVED] No bluetooth adaptater on AX200

#8 2022-01-03 15:38:20

Re: [SOLVED] No bluetooth adaptater on AX200

#9 2022-01-03 16:00:42

Re: [SOLVED] No bluetooth adaptater on AX200

#10 2022-01-03 16:19:49

Re: [SOLVED] No bluetooth adaptater on AX200

#11 2022-01-03 16:24:51

Re: [SOLVED] No bluetooth adaptater on AX200

#12 2022-01-04 21:27:02

Re: [SOLVED] No bluetooth adaptater on AX200

#13 2024-05-01 09:43:29

Re: [SOLVED] No bluetooth adaptater on AX200

Board footer