mt7925e: add PCI ID 14c3:7927 (MediaTek MT7927, WiFi 7) — no bind, new_id rejects it

Open
  • Is something wrong?
#1,142 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
c, linux
Domain
networking, operating-systems

Research direction

Start by locating the mt7925e PCI ID table and the probe or chip-id validation path that rejects 0x7927. Review the existing MT7925 firmware-selection handling and verify whether the available mt7925 firmware is used. Done means the device binds on the reported board, creates a wireless interface, and the driver loads without errors.

Written by the indexing model from the issue text.

Description

Hardware

  • Motherboard: ASUS ROG STRIX X870-F GAMING WIFI (BIOS 2402, 2026-07-13)
  • On-board combo Wi-Fi/BT chip, lspci -nnk: 
    07:00.0 Network controller [0280]: MEDIATEK Corp. Device [14c3:7927]
    Subsystem: Foxconn International, Inc. Device [105b:e124]
  • Kernel: 7.0.0-31-generic (Ubuntu), in-tree mt7925e driver present and loadable.

Problem

The device (14c3:7927, "MT7927") never binds to mt7925e. modinfo mt7925e shows only two PCI aliases in this build:

alias:          pci:v000014C3d00000717sv*sd*bc*sc*i*
alias:          pci:v000014C3d00007925sv*sd*bc*sc*i*

7927 is not present, so the module never auto-loads a binding for it (ip link shows no wlan*; /sys/bus/pci/devices/0000:07:00.0/driver doesn't exist).

Firmware present on disk is only mediatek/mt7925/{WIFI_MT7925_PATCH_MCU_1_1_hdr.bin,WIFI_RAM_CODE_MT7925_1_1.bin} — no MT7927-named blobs shipped in this linux-firmware snapshot either.

What I tried

Manual modprobe mt7925e loads the module (and its full dependency chain: mt7925_common, mt792x_lib, mt76_connac_lib, mt76, mac80211, cfg80211) with no errors, but nothing binds to 07:00.0.

Tried forcing a bind via the standard PCI new_id mechanism:

# echo "14c3 7927" > /sys/bus/pci/drivers/mt7925e/new_id
tee: /sys/bus/pci/drivers/mt7925e/new_id: Invalid argument

This is rejected outright (no dmesg output at all for the attempt), which reads as more than a missing modalias entry — it suggests the driver's own probe/id validation path doesn't recognize 0x7927 as a supported chip revision yet, not just a PCI-ID-table omission that new_id could patch around.

Ask

MT7927 appears to be a newer MediaTek WiFi 7 (802.11be) SKU shipping on current ASUS AM5 boards (X870-F GAMING WIFI at least). Could mt7925e get a PCI ID entry (and, if the ASIC needs it, whatever chip-id/firmware-selection branch MT7925 already has) added for 14c3:7927? Happy to test a patch against this exact board/BIOS if one is proposed — I have the hardware in hand and no working driver path currently.

Dominant language
C
Stars
895
Forks
461
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openwrt/mt76

All issues in openwrt/mt76

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.