About a month ago I swapped the mainboard out on my FW13 (to an AMD ryzen 370) - it went well. But the wifi has been unreliable since, usually by not seeing any networks after waking from sleep. A reboot seems to resolve it, usually.
Right now as I type wifi is working, but showing a terrible signal quality, and I’m getting basically “modem” type speeds.
I’ve seen discussion of issues with wifi power management. But maybe I just messed up the antenna when putting the new mainboard in?
I’m just asking here for some diagnostic aid - any recommendations as to where to look?
Top places to look will be:
- If you’re on linux, update your kernel to 6.15 or later, there’s a lot o 300-series fixes in recent kernels.
- If you’re on windows, search these forums for driver bundles. There were some updated drivers passed out for windows to help with wifi issues.
- Find what wifi card you have, and search these forums for issues. Some wifi cards have been notoriously buggy, especially on AMD. You might find some fixes specific to yours.
Are you on windows or Linux?
For Windows, read this.
For Linux, read this and this as well.
These two post go any issues I’ve had on wifi. If you swapped boards and changed the wifi card, please remove the drivers and reinstall. Also, make sure that you have the antenna coaxial connections on tight and proper. If your antenna aren’t connected, then only whatever wifi signals that can reach the tiny nubs on the car are picked up.
I’m on linux (Fedora 42), and I’m using the same wifi module that my FW13 came with in 2023. I’m leaning towards the antenna connection being the problem.
I’m at work, so I can’t take a look, but I recall during reassembly having some fiddly issues with the wifi module. I probably just did a poor job putting it back together - if the cable is barely connected / sporadically detaching that would explain this behavior quite well.
1 Like
So, assuming I was experiencing a hardware issue, last night I took out the wifi card, verified connections to it and through to the antenna and put it all back together. Everything seemed fine, but this morning on wake my card saw no networks again.
A reboot “fixed” it, so I assume that this is going to be a power management issue as discussed in threads that were linked above. Will report back if I find a fix.
My wifi card, as reported by lspci is: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter
My mainboard is the new Ryzen 300.
Note I am running an up-to-date kernel, 6.17.4.
Per @HurricanePootis ‘s suggestion links, I disabled wifi powersaving. I’m now at 1.5 days uptime with multiple sleep/wakes without loss of wifi. So that’s a good start. Better than I was seeing earlier.
Hopefully this actually is a fix. Thanks!
1 Like
Yeah no problem! The mediatek driver’s one downside on Linux has always been support for sleep/suspend operations.
Remember to set your regdom as well to ensure you’re getting access to all of the bands supported in your country
So, it turns out I spoke too soon. Even with the suggested powersave settings, I’m seeing the wifi fail on wake from sleep again.
So the question is what are my options? Is there a different wifi card I could be using? I had zero wifi issues with my ryzen 7840 mainboard.
Is there a diagnostic I can run to better understant what’s broken here?
Also, from what I can tell reading man setregdomain and from the output of iw reg get it appears my reg domain is already US
Hey, what kernel version are you on? I remember my Mediatek mt7921 having really poor behavior from whenever waking up from sleep on older kernels, until it was fixed somewhat recently (within the past year)
If you are on an older kernel, maybe look into creating this script
#!/bin/bash
case $1 in
pre)
rmmod mt7925e mt7925_common mt792x_lib mt76_connac_lib mt76
;;
post)
modprobe mt7925e
;;
esac
at /usr/lib/systemd/system-sleep/wifi. This script will unload all the mediatek wifi stuff whenever the system sleeps, then reload it after after the system wakes. I used to use this script whenever I was on an older kernel.
Well, I’m on an up-todate kernel 6.17.6, via Fedora 43.
So, I did some searching on Fedora wifi powermanagement, just in case the suggestions you gave applied to Arch but needed some tweaking for Fedora. I had expected your suggestion to work, as my machine already had a etc/NetworkManager/conf.d dir.
Anyway, I stumbled on this:
I’ve run the script, and am going to see what comes of it. It’s my observation that it takes something like 4+ hours sleeping on battery without AC power for my wifi issues to kick in. It’s hard to repro in day to day use.
Also, I really do appreciate your help here - I’m one of those people who writes a lot of C++ but isn’t much good at diagnosing or fixing system issues.
No problem. I’m not a programmer at all, but I do a lot of system stuff on Linux lol.
So, the official wifi powermanagement script from the Framework repo didn’t work. I tried some of the diagnostics in that page, and interestingly:
nmcli radio
This indicated that WWAN-HW is missing when the issue occurs. The guide suggests that it could be a tlp issue, but it’s my understanding that Fedora deprecated tlp at least a version or two ago. That being said, this machine has been running Fedora for a couple years, and had tlp on it at some point in the past.
This makes me wonder if there’s some old cruft from the past causing this issue. I’m going to try today booting from a Fedora 43 ISO, and see if the issue persists there. If not, that tells me my system could use a good cleanup.
I’m also going to try your modprobe suggestion today. That would be a datapoint.
So, the modprobeapproach when the error occurs didn’t help. It was worth a try!
I also spent a couple days booted into a vanilla Fedora live install, or whatever it’s called. I thought, maybe my machine has some cruft from previous Fedoras like the deprecated tlp.
Wifi was coming back up after sleep/wake for about 1.5 days, but then it didn’t.
So, I did some searching and found that the Intel Wifi module (AX210 NGW) is considered good by AMD FW users. Worth a shot. Ordered one on amazon, so we’ll see how that goes.