Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug] MediaTek RZ616 (MT7922, 14c3:0616): Wi-Fi not supported; Bluetooth works after adding USB ID 0e8d:0616 to SimpleMtkBtFw

Open
#336 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
macos, rust
Domain
backend

Research direction

Start by tracing how the builder packages experimental MediaTek Wi-Fi drivers and bundles SimpleMtkBtFw.kext; inspect its IOKitPersonalities for the reported USB ID 0e8d:0616. The report gives a working Bluetooth workaround, but does not name the packaging files or tests, so locate those entry points first. Done means the Bluetooth ID survives rebuilding the USB stick; Wi-Fi support is a separate request whose implementation is unspecified.

Written by the indexing model from the issue text.

Description

bug
Send logs report ID

nm-0000000

Where does it go wrong?

Building or writing the USB stick (1401 on Windows)

What happens

Summary

I built the USB stick with "Include experimental drivers (AMD RDNA 4 graphics, MediaTek Wi-Fi)" checked, but Wi-Fi cannot be turned on. EFI/OC/Kexts contains no MediaTek Wi-Fi kext, only SimpleMtkBtFw.kext (Bluetooth).

Bluetooth also did not work at first, because the card's Bluetooth USB ID (0e8d:0616) is not in SimpleMtkBtFw's IOKitPersonalities. After adding it manually, Bluetooth works.

Environment

  • 1401 version: 2.4.3
  • macOS: Sequoia 15.8.1
  • SMBIOS: MacPro7,1
  • Motherboard: ASRock B760 TW (OEM, GALLERIA VSA7C-R46T)
  • Wi-Fi card: MediaTek RZ616 Wi-Fi 6E 160MHz (MT7922)
    • PCI: 14C3:0616, Subsystem 061614C3
    • Bluetooth (USB): 0e8d:0616

Wi-Fi

  • The card is detected in system-profile.json ("RZ616 Wi-Fi 6E 160MHz", Device ID 14C3-0616)
  • No Wi-Fi kext for MediaTek is included in EFI/OC/Kexts
  • Wi-Fi cannot be turned on in macOS

Could RZ616 / MT7922 Wi-Fi support be added in a future version?

Bluetooth workaround (tested, working)

SimpleMtkBtFw was not loaded because 0e8d:0616 has no matching personality.
I copied the MT7922A entry and changed the IDs:

/usr/libexec/PlistBuddy
-c "Copy :IOKitPersonalities:SimpleMtkBtFw_MT7922A_35f5_7922 :IOKitPersonalities:SimpleMtkBtFw_MT7922A_0e8d_0616"
-c "Set :IOKitPersonalities:SimpleMtkBtFw_MT7922A_0e8d_0616:idVendor 3725"
-c "Set :IOKitPersonalities:SimpleMtkBtFw_MT7922A_0e8d_0616:idProduct 1558"
/Volumes/1401/EFI/OC/Kexts/SimpleMtkBtFw.kext/Contents/Info.plist

After rebooting, com.laobamac.SimpleMtkBtFw loads, Bluetooth can be turned on, nearby devices are found, and audio playback to a Bluetooth speaker works.

It would be great if this ID could be added to the bundled SimpleMtkBtFw, so the fix survives rebuilding the stick.

Written by you
  • I wrote this report myself. AI-written issues are closed without review (see CONTRIBUTING.md).
App or game (if it is one)

No response

Did you change anything yourself?

No response

Dominant language
Rust
Stars
2.5k
Forks
233
Avg merge
21h 20m
Merged PRs (30d)
3

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 nullmoth/nvidia-macos-driver

All issues in nullmoth/nvidia-macos-driver

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.