This source has a unusually clean technical diagnosis. ZimaOS could see the MediaTek MT7920 PCIe device, and the correct mt7921e kernel driver was already loaded. Wi-Fi still did not appear because two firmware blobs required by the card were missing from the ZimaOS image, producing repeated error -2 firmware-load failures.
That gap was resolved in the ZimaOS 1.7 line. A community member verified both firmware files existed in 1.7.0 beta, and the original poster later returned on August 16, 2026 to say they were running 1.7 and could now connect to their network over Wi-Fi. That is source-confirmed success.
The MT7920 Was Detected on PCIe
The source showed:
03:00.0 Network controller [0280]:
MEDIATEK Corp. Device [14c3:7920]This ruled out a completely invisible PCIe card. The hardware enumerated correctly.
The mt7921e Driver Was Already in Use
The user then posted:
Kernel driver in use: mt7921e
Kernel modules: mt7921eThat is important because the problem was not “ZimaOS has no MediaTek driver at all.” The driver was present and bound to the card.
The Kernel Log Identified Missing Firmware Files
The decisive errors were:
mediatek/WIFI_RAM_CODE_MT7961_1a.bin
mediatek/WIFI_MT7961_patch_mcu_1a_2_hdr.binBoth failed to load with error -2, followed by hardware init failed. In this context, error -2 means the requested file could not be found.
Why nmtui Could Not Offer the Wi-Fi Interface
nmcli radio wifi could say Wi-Fi was enabled while nmtui still showed no usable wireless connection. The radio policy was enabled, but the hardware never completed firmware initialization, so the OS never got a functioning Wi-Fi interface to configure.
ZimaOS 1.7.0 Added the Required Firmware Files
In July 2026, piterdan said ZimaOS 1.7.0 included the missing MT7920 firmware. gelbuilding then verified on a ZimaCube running 1.7.0-beta1 that both required files existed under /lib/firmware/mediatek/.
The original poster waited for stable rather than moving to beta.
The Original Poster Confirmed Stable 1.7 Worked
On August 16, djmiek returned and said they were now running 1.7 and could connect to their network using Wi-Fi. That closes the original issue more strongly than simply finding the firmware files in a beta build.
Current Users Should Update Before Attempting Driver Surgery
Current ZimaOS is 1.7.1. If an MT7920 on an older 1.6.x system shows the exact missing-firmware errors from this source, update to the current stable release before considering custom firmware injection.
Use the current ZimaOS release baseline.
If MT7920 Still Fails on a Current Build, Capture the Same Evidence
lspci -nnk | grep -A3 7920
ip link
dmesg | grep -i mt79
dmesg | grep -i firmwareIf the driver and firmware both load but the interface still fails, the problem is no longer the same source bug and needs fresh diagnosis.
The RTL8125 Showing 1 Gbps Was a Separate Link-Negotiation Question
The user also noticed a 2.5GbE RTL8125 showing 1 Gbps in the UI. A 2.5GbE NIC will negotiate only 1 Gbps when connected to a 1GbE switch/router port or incompatible link partner. That has nothing to do with the MT7920 firmware failure.
Firmware and Driver Are Different Pieces
The MT7920 source is a useful example of why “driver missing” is often too vague. The Linux kernel module contained the code needed to control the MediaTek family, but the card also required binary firmware loaded into the device during initialization. One component was present; the other was not.
That distinction matters for support reports. If lspci -nnk shows a driver in use but dmesg reports missing firmware, asking IceWhale to add the firmware files is more precise than requesting an entirely new kernel driver.
Do Not Copy Random Firmware Blobs from Another Distribution First
Because ZimaOS packages its kernel and firmware as an appliance image, manually copying blobs into system paths can be overwritten by OTA updates or create mismatched firmware/kernel combinations. The source was ultimately fixed by the normal ZimaOS release containing the required files.
Wi-Fi and Bluetooth May Be Separate Functions on the Same Card
Combo cards expose more than one function and can require separate firmware/USB paths for Bluetooth. The source only proves the Wi-Fi side began working on ZimaOS 1.7. If Bluetooth still fails, capture its own device ID and kernel log instead of assuming the Wi-Fi fix guarantees both radios.
MT7920 FAQ
Was the MT7920 driver missing?
No. The source showed mt7921e loaded and bound to the device.
What was missing?
Two MediaTek firmware files required for hardware initialization.
Did the original user confirm ZimaOS 1.7 fixed it?
Yes. They later reported a working Wi-Fi connection on stable ZimaOS 1.7.
