Not sure why the command line updates for pipewire-jack
didn’t work for me, but I was finally able to install the updates via the pamac
GUI after following this advise…
Now to figure why I’m having Bluetooth issues with the new 5.15.19-1
kernel…
$ journalctl --priority err --boot 0
Feb 05 10:33:56 AM4-5600X-Linux kernel: Bluetooth: hci0: command 0xfc01 tx timeout
Feb 05 10:34:04 AM4-5600X-Linux kernel: Bluetooth: hci0: FW download error recovery failed (-110)
Feb 05 10:34:04 AM4-5600X-Linux kernel: Bluetooth: hci0: sending frame failed (-19)
Feb 05 10:34:06 AM4-5600X-Linux kernel: Bluetooth: hci0: Failed to read MSFT supported features (-110)
Feb 05 10:34:16 AM4-5600X-Linux bluetoothd[717]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
I tried looking for a related .pacnew
file, but did not find any; hence why I suspect the kernel.
$ Inxi -Fazy
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-4:6
chip-ID: 8087:0029 class-ID: e001
Report: rfkill ID: hci0 rfk-id: 1 state: up address: see --recommends
$ rfkill list
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
EDIT: According to [Solved] No bluetooth from AX200 / Kernel & Hardware / Arch Linux Forums
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” andrfkill list
will have a bluetooth entry.
So I thought I’d give this a try, powered down, unplugged power for 15 seconds, rebooted, and journalctl
no longer reports bluetooth kernel errors.
Now that I think about it…I’ve seen the issue before (Anyone else experiencing Intel AX200 Bluetooth being disabled in kernel515? - #17 by Daniel-I) and had equated it to the AMD USB drop out issue that sometimes happens. On one kernel it was a crapshoot every reboot whether my mouse or bluetooth would not be detected… so this may be a kernel issue that get’s resolved down the road, or maybe there is a reliance an a newer AGESA with the newer kernel? Or maybe the Arch poster is right in saying the AX200 is “flakey”.