Brand new machine with brand new installation of Fedora Server 43. Updated all packages and firmware to the latest and greatest. Wi-Fi download speeds were at to ~6 Mbps, while upload speeds remained normal (~140-150 Mbps). Download latency also spiked significantly during throughput tests (reaching ~200ms). Downgrading firmware brought download speeds back to normal. Steps to Reproduce: Install linux-firmware-20260110-1.fc43. Connect to a 5GHz WiFi network. Speed test through Ookla CLI. Observe near-total loss of download performance. Actual Results: Download: 6.62 Mbps | Upload: 140.05 Mbps | Download Latency: 196.36 ms Expected Results: Download: >600 Mbps | Upload: >900 Mbps (symmetric/Gigabit line speed) Workaround/Fix: Downgrading to the previous firmware package (linux-firmware-20251021-1) followed by a cold boot (complete power cycle to clear the chip's SRAM) restores full performance. Confirmed Working Results (after downgrade): Download: 609.35 Mbps | Upload: 938.39 Mbps | Download Latency: 10.10 ms Reproducible: Always Steps to Reproduce: 1. Install linux-firmware-20260110-1.fc43. 2. Connect to a 5GHz WiFi network. 3. Speed test through Ookla speed test CLI or similar. Actual Results: Download: 6.62 Mbps | Upload: 140.05 Mbps | Download Latency: 196.36 ms Expected Results: Download: >600 Mbps | Upload: >900 Mbps (symmetric/Gigabit line speed)
Hi, I have the same issue on my Asus Vivobook S14 M5406WA with MT7922 802.11ax Downgrading Mediatek Firmware fixes this issue. Hope Mediatek team will release fix in future version.
*** Bug 2441661 has been marked as a duplicate of this bug. ***
FEDORA-2026-445b31d485 (linux-firmware-20260410-1.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-445b31d485
FEDORA-2026-5d86317e79 (linux-firmware-20260410-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2026-5d86317e79
FEDORA-2026-f0f802a460 (linux-firmware-20260410-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-f0f802a460
FEDORA-2026-445b31d485 has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-445b31d485` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-445b31d485 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-f0f802a460 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-f0f802a460` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-f0f802a460 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-5d86317e79 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-5d86317e79` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-5d86317e79 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-5d86317e79 (linux-firmware-20260410-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-f0f802a460 (linux-firmware-20260410-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
Please reopen, the problem is still there with linux-firmware-20260410-1.fc44. Roughly 2-3Mbit/s with this firmware. No issues with linux-firmware-20251021-1
FEDORA-2026-445b31d485 (linux-firmware-20260410-1.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
Marcin is reporting that this is still a problem.
(In reply to Justin Christensen from comment #13) > Marcin is reporting that this is still a problem. are you as the original reporter still seeing an issue? Trying to ascertain if we have one or two different problems.
Unfortunately I don't have the time to re-verify this. I'm assuming if it's still an issue others will report the bug.