Bug 210611

Summary: No Bluetooth on Intel AX200
Product: Drivers Reporter: Laurentiu Nicola (lnicola)
Component: BluetoothAssignee: linux-bluetooth (linux-bluetooth)
Status: RESOLVED INVALID    
Severity: normal CC: matas234
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 5.9.13 Subsystem:
Regression: No Bisected commit-id:

Description Laurentiu Nicola 2020-12-10 15:48:05 UTC
Bluetooth works on Windows, but there's no mention of it in `dmesg` and no controller is detected.

See https://linux-hardware.org/?probe=e452d60d3e for logs.
Comment 1 matas234 2021-02-11 23:26:00 UTC
I am having this issue as well.


lsmod: https://0x0.st/-Hh2.txt 


https://dpaste.com/4XAHYD6ZE full paste oof? rfkill, lspci, lsusb and dmesg


https://0x0.st/-HhS.txt bluetooth systemctl and journalctl



```
~
❯ bt-device --list
**
ERROR:lib/bluez/adapter.c:165:adapter_get_dbus_object_path: assertion failed: (ADAPTER_IS(self))
Bail out! ERROR:lib/bluez/adapter.c:165:adapter_get_dbus_object_path: assertion failed: (ADAPTER_IS(self))
```
Comment 2 Laurentiu Nicola 2021-02-12 10:28:17 UTC
@matas234 you have a different issue, your adapter shows up in rfkill, unlike mine.

For anyone ending up here, I actually found a workaround for my problem, presumably specific to ASUS motherboards: I have to unplug the computer (or turn off the PSU), keep the power button pressed for a while, then turn it back on. This sounds like it might reset the CMOS, but doesn't do it. And it actually works, even when Windows no longer detects the adapter (that actually happens at times).

ASUS support was less than helpful -- they said it can't be a very common problem, and if it's electrical, it can't be fixed by a BIOS update. I'm not sure about that, but it probably can't be fixed by the kernel either.
Comment 3 matas234 2021-02-12 12:07:31 UTC
@Laurentiu ah my bad, sorry for polluting the thread. I tried that as well and it didn't seem to help. Will look for solutionsesewhere.
Comment 4 Laurentiu Nicola 2022-02-25 15:50:52 UTC
As mentioned, this must be a hardware problem.