When I examine my bluetooth service, it shows it enabled and running. When I run a simple test to connect to a bluetooth device however, there is no default controller, so no devices ever show up for pairing. If I run the GUI for bluetooth manager, it comes default to off, switching it to on does not expose any devices either.
So I suspect something needs to be configured to get a working bluetooth on this AMD laptop running Arch Linux.
There are not apparent errors when stopping and starting the service, but it apparently is lacking a controller!!
mhh i have it from time to time that my bt controller dies and then i get the same error msg in arch.
i suspect the recent kernel update. But a reboot fixes it most of the times. did work flawlessly till the latest update xD
Ok. Good to know I am not alone. While it is true that the dead BT was revived with a reboot and then BT worked, it is concerning that simply using the machine can put it into a state of this dead BT… hopefully this is a transient error and will not be a consistent behaviour!
Yes, I had the exact problem you were describing on Arch. The issue was linux-firmware-mediatek was upgraded from 20250708-1 to 20250808-1.
I downgraded the package, and things started working as normal. From what I could tell (but don’t take my word for it) the firmware update introduced stricter power management protocols that broke compatibility. Hopefully, it will be fixed in the Future.