You are not logged in.
Pages: 1
Topic closed
Edit: Hello future searchers! It turns out it was a hardware issue that would also affect Windows (in which case it'd be greyed out in the device manager). Essentially there's a hardware bug with this chipset that sometimes causes bluetooth to fail, and it can be temporarily fixed by turning off the power, unplugging from the wall, waiting up to a minute, and then booting up again. Beyond that it seems to be random. When it's working, `lsusb` will give you "Intel Corp. AX200 Bluetooth" and `rfkill list` will have a bluetooth entry.
Hello! My motherboard has an integrated Intel AX200 card supplying wifi and bluetooth. The wifi works fine but I'm not getting anything at all on the bluetooth end.
I'm going to preface this with the fact that I'm dual booting with Windows 10, in which the bluetooth is working fine. This tells me it's probably not a hardware issue.
Kernel: `5.7.9-arch1-1`
`systemctl status bluetooth`:
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2020-07-19 13:48:00 BST; 5s ago
Docs: man:bluetoothd(8)
Main PID: 12893 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 19123)
Memory: 964.0K
CGroup: /system.slice/bluetooth.service
└─12893 /usr/lib/bluetooth/bluetoothd
Jul 19 13:48:00 hostname systemd[1]: Starting Bluetooth service...
Jul 19 13:48:00 hostname bluetoothd[12893]: Bluetooth daemon 5.54
Jul 19 13:48:00 hostname systemd[1]: Started Bluetooth service.
Jul 19 13:48:00 hostname bluetoothd[12893]: Starting SDP server
Jul 19 13:48:00 hostname bluetoothd[12893]: Bluetooth management interface 1.16 initialized
Following the debugging steps on the bluetooth wiki page, after stopping the bluetooth service I see this in the output of `sudo /usr/lib/bluetooth/bluetoothd -n -d`:
bluetoothd[12742]: src/adapter.c:read_index_list_complete() Number of controllers: 0
`lspci -knn | grep Net`:
2a:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
`lsmod | grep btusb` - potentially worth mentioning I needed to manually start this module with modprobe:
btusb 65536 0
btrtl 24576 1 btusb
btbcm 20480 1 btusb
btintel 32768 1 btusb
bluetooth 712704 11 btrtl,btintel,btbcm,bnep,btusb
`rfkill list`:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
`dmesg | grep blue` comes back empty. Here's `dmesg` where it loads the wifi driver:
[ 26.346131] Intel(R) Wireless WiFi driver for Linux
[ 26.346133] Copyright(c) 2003- 2015 Intel Corporation
[ 26.346213] iwlwifi 0000:2a:00.0: enabling device (0000 -> 0002)
[ 26.352579] iwlwifi 0000:2a:00.0: api flags index 2 larger than supported by driver
[ 26.352588] iwlwifi 0000:2a:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 68.3.35.22
[ 26.352590] iwlwifi 0000:2a:00.0: Found debug destination: EXTERNAL_DRAM
[ 26.352591] iwlwifi 0000:2a:00.0: Found debug configuration: 0
[ 26.352800] iwlwifi 0000:2a:00.0: loaded firmware version 53.c31ac674.0 cc-a0-53.ucode op_mode iwlmvm
[ 26.352820] iwlwifi 0000:2a:00.0: Direct firmware load for iwl-debug-yoyo.bin failed with error -2
...
[ 26.608472] iwlwifi 0000:2a:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
...
[ 26.973926] iwlwifi 0000:2a:00.0 wlo1: renamed from wlan0
Notably, here's what I see with `lsusb`:
Bus 004 Device 002: ID 05e3:0612 Genesys Logic, Inc. Hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID feed:1307
Bus 003 Device 003: ID 1532:002e Razer USA, Ltd RZ01-0058 Gaming Mouse [Naga]
Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID b58e:9e84 Blue Microphones Yeti Stereo Microphone
Bus 001 Device 003: ID 1462:7c90 Micro Star International MYSTIC LIGHT
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Some searching tells me I should probably be seeing `8087:0029 Intel Corp.` here.
Where to go from here? Cheers
Last edited by samhh (2020-08-01 17:35:47)
Offline
Did you get this fixed? Having the same issue.
Offline
See the edit at the top, it's a hardware problem. It seems to have stopped happening to me entirely now for some reason.
Offline
It isn't fixed for me, regardless of how many cold boots I perform.
I get an "hci0: Found device firmware: intel/ibt-20-1-3.sfi" message in `dmesg`, and `lsusb` shows "Intel Corp. AX200 Bluetooth", but the bluez stack doesn't (always*) show a controller, and scanning _never_ finds any bluetooth devices. (*) Last night, before I gave up on this for the night and shut the computer off, I had a controller. This morning, I don't.
I have a different, non-Intel-crap M.2 wifi board, but replacing it is beyond my comfort (or interest) level, and I'd like to get this one working before I disassemble the device that far and figure out where the soldered antenna leads are connected. Does anyone have a suggested software fix for this?
Offline
This topic is three years old and marked [solved], Please do not necrobump.
Instead, start a new topic (which you can marked solved when you find a solution) and link back to this one if you think it still applies.
Closing.
Offline
Pages: 1
Topic closed