TL;DR: Do a battery reset after getting WiFi/Bluetooth firmware updates when troubleshooting. Might be MediaTek specific.
So I’ve been using Fedora for year or so now, starting with Silverblue, which is atomic, meaning you can roll back to a previous version or kernel if you’re having issues on a system. This works well for temporary fixes, but if the issue goes on for too long, you could be stuck on an older kernel, which is probably a security issue, and means you’ll be using outdated firmware/software. Silverblue was smooth sailing for about two months before Bluetooth gave out on me, but I just would rollback to a previous kernel, which worked relatively fine.
But at some point I hated trying to figure out how to do things that the atomic system didn’t like, so I switched to regular Fedora KDE, which meant I couldn’t do rollbacks anymore. I can’t remember completely, but I think it didn’t work straight out of the box, and I was too lazy to fiddle with kernels and stuff, so I kinda just lived with it for the past few months since I didn’t NEED it. I would passively look up info, only to be stuck again.
But finally I saw a Reddit post from last month complaining about recent kernel issues on Fedora 43, and one of the answers said to do a CMOS/Power reset after MediaTek WiFi /Bluetooth firmware updates, and it worked like a charm! I just hit the reset button on my motherboard. Now if my ELAN touchpad would work again, which is what I was actually searching for…
Maybe MediaTek is just shit unlike other drivers, but I wanted to make sure people on Lemmy (and internet search results) knew to try this before throwing in the towel like I did. No one had ever said some drivers need battery resets.
May your troubleshooting be short!
Interesting. I’ve been having Bluetooth issues with fedora as well. I’ll give this a go tomorrow and report back


