Hey folks,
Just dropped in for a quick update.
Did additional extensive testing between Ubuntu 25.04 and Fedora 42; both fully updated, both attached to only power, nothing else.
Fedora Workstation 42, on my Eero mesh network was completely reliable. Zero issues.
Additionally, the mt7925 (RZ717) was able to see and access 6ghz, 5ghz and 2.4ghz without issue.
Ubuntu 25.04, with mt7925, is simply not there. Flaky connection status. Sees all the expected bands, but only connects successfully to 2.4ghz and 5ghz. At this time, Ubuntu’s simply not there at this time. Based on what I am seeing in my testing, feels like this is a wait until mt7925 matures a bit.
And this holds true for a number of distros I suspect. The mt7925 support feels super young. While Fedora has it dialed in well in my testing, obviously “it works on my computer” feels like a cop out and is not helpful to you all.
Here is the thing I discovered - even internally, wifi environments differ, to a degree that younger chips like mt7925 are not able to “roll with the punches” when something is slightly different from our own testing environment.
Where do we go from here?
Short of showing up on everyone’s door step and doing a validation test on your specific networks, let’s do the next best thing.
Sneak a peak
I need to get a peak at how your network and mt7925 card are talking to each other. Support will ask you to run a tool, to collect logs of course. But they only give us part of the story. We can gather event data, which is “fine”…for distros whereas it absolutely should be a solid experience like Fedora, we also need to understand your network data.
This brings us to the Enhanced WiFi Analyzer. We want you to run the following:
-
Complete WiFi Analysis
-
Error Analysis & Troubleshooting
-
DFS Channel Monitor (unlikely to be relevant, but not unheard of for specific situations)
When asked: “Would you like to run the Smart Channel Switcher to avoid DFS issues? [y/N]” - Choose N)
All of these will kick out individual log files capturing exactly what you are seeing the terminal. You will be sending these files to support.
Reaching out to support
- Please reach out to support.
- Let them know them know this is a support request regarding the RZ717 wifi card on Linux (mt7925).
- They should then pass along a procedure to ask for logs, with the collected logs, also include the text logs for the Enhanced WiFi Analyzer as well.
- Include a link to this thread please!
Mesh users, please also include
If you are using a mesh network and seeing issues, please also the WiFi Mesh Network Analyzer.
Run with this:
Complete Analysis (Recommended) (run both lines below to include an archive for support) Remember to run both the --check-power --detect-dropouts --roaming-test --html-report (be sure to follow the directions as they display in the terminal. The first check, micro-dropouts will sit there for 30 seconds.
So this is how this will go:
sudo python3 mesh_analyzer.py --check-power --detect-dropouts --roaming-test --html-repor
and then after
sudo python3 mesh_analyzer.py --create-archive
Once completed, you will want to grab two files:
In ~/.mesh_analyzer, you will see logs and reports. Grab the most recent html report from the reports directory and back in ~/.mesh_analyzer, include the zip folder created with logs generated.
Why all of this?
The idea here is simple - we need to see what your environment looks like. Here is what we know:
Ubuntu is a hard fail at this point.
Fedora, Arch and other distros with a modern stack should be working. If not, we cannot repo your network environment, but we can gather data to understand why you are experiencing mishaps.
With this data, this helps us to figure out what the edge cases are with distros where RZ717 should be fine with.
SOP for my agents is that when this stuff comes in, all you should be asked is to collect logs per their request and it gets sent straight to my Linux Specialists.
Thanks folks
