Installing the macOS operating system on a personal computer, known as Hackintosh, has always been fraught with a number of technical challenges, and macOS Big Sur is no exception. Wireless connectivity is particularly problematic, as Apple has dropped support for many older modules that previously worked via standard kexts in this version of the OS. If you've upgraded or are planning a clean installation, you should understand that your usual methods may no longer work.
The situation is aggravated by the fact that OpenCore, which is the de facto standard for booting, requires more fine-tuning of the configuration file config.plist Compared to Clover, many users encounter the module simply not being detected after installing the system or showing the status "No Wi-Fi hardware installed." This requires a deep dive into the driver setup and ACPI tables.
In this article, we'll explore current solutions, compatible card models, and software emulation methods. You'll learn how to properly implement the necessary patches and avoid common errors that lead to kernel panics or network instability.
⚠️ Attention: Any modifications to the bootloader and system files are performed at your own risk. Incorrect editing
config.plistmay result in the system failing to boot.
Wi-Fi Module Compatibility Analysis in Big Sur
The first step should always be to diagnose your hardware. In macOS Big Sur, the driver was removed. AirPortAtheros40.kext, which was responsible for the operation of a huge number of cards based on Atheros chips. If your device was running Catalina or Mojave, this does not guarantee that it will work on the new system without additional modifications.
Broadcom modules remain the most trouble-free, especially those with native macOS support. Cards with chips Broadcom BCM94360CD, BCM943602CDP or BCM94331PCIEBT4CAX They are often detected automatically. However, even these may require proper PCIe passthrough or device properties configuration.
- 📡 Broadcom: Full or partial native support (AirDrop, Handoff work).
- 📡 Intel: Requires installation of third-party drivers (itlwm), functionality is limited.
- 📡 Atheros/Realtek: There is no native support; complex patches or module replacement are required.
The situation has changed dramatically for Intel cards. A project has emerged itlwm, which allows these modules to work, but the functionality is often limited: AirDrop and Handoff may not function reliably or require additional workarounds. This is a compromise option for those who don't want to buy a new module.
Preparing the OpenCore bootloader and EFI structure
Before implementing the drivers, make sure your bootloader is updated to the latest version. Older versions of OpenCore may not correctly handle new ACPI requests or lack the necessary quirks for Big Sur. Download the latest release build from the official repository.
Proper placement of files in the folder is critical. EFI/OC. Drivers (.kext) should be located in the folder Kexts, and their paths must be specified in the section Kernel -> Add Configuration file. Kext loading order issues are a common cause of Wi-Fi failure.
☑️ Checking the EFI structure
Use the utility ProperTree for editing the configuration. It automatically checks the syntax and helps avoid indentation errors that can make the configuration unreadable for the bootloader. After making changes to config.plist Be sure to run the command Cmd + Shift + R (OC -> Snapshot) to update driver paths.
Installing drivers and patches for Broadcom
If you have a Broadcom card but it's not detected, the problem is likely due to missing dependencies. Native Apple drivers often require Lilu.kext And WhateverGreen.kextWithout them, device forwarding may not work.
In some cases, especially when using laptop cards (Mini PCIe) via adapters or specific desktop models, it is necessary to change the device ID. This is done through the section DeviceProperties -> Add In the OpenCore config, you need to find your card's PCI path and enter the necessary properties.
PciRoot(0x0)/Pci(0x1C,0x0)/Pci(0x0,0x0){
"name","pci14e4,4331"
}
It is also worth paying attention to the kext AirPortBrcm4360_Inject.kextIt's necessary for injecting a card's ID into the system if it isn't recognized as native. However, in Big Sur, its use has become less relevant for most modern cards, provided they are properly routed at the PCIe level.
List of commonly used kexts for Wi-Fi
Lilu.kext (base dependency), WhateverGreen.kext (video and device), AirportBrcmFixup.kext (fixes for Broadcom), IntelMausi.kext (for LAN, but often installed together).
Configuring Intel modules via itlwm and HeliPort
For Intel card owners, the only working option is to use the driver itlwm.kextUnlike native solutions, this driver does not integrate deeply into the macOS system stack the way Apple's original drivers do, so a separate application is required to manage the connection.
You need to install the application HeliPortIt takes over the functions of a wireless network manager: searching for networks, entering passwords, and saving profiles. Without HeliPort running, Wi-Fi won't work, as the standard macOS interface won't recognize the module.
The installation process requires careful attention. You need to download the archive from the project release, place it itlwm.kext to the OpenCore drivers folder and add it to the config file. The HeliPort app installs like a regular program in the Applications folder. After rebooting, the Wi-Fi icon will no longer appear in the menu bar—the HeliPort icon will appear instead.
⚠️ Attention: When using itlwm, AirDrop, Handoff, and Continuity Camera will not work. This is a driver architecture limitation, not a configuration issue.
Troubleshooting DeviceProperties and PCIe Passthrough
It often happens that the drivers are installed, but the system sees the device as "Unknown" or doesn't see it at all. In this case, it's necessary to check whether PCIe passthrough is working correctly. In Big Sur, the requirements for ACPI tables have increased, and sometimes patching the DSDT or using SSDT stubs is required.
Use the utility IORegistryExplorer to find your device. Find the branch that corresponds to your Wi-Fi module (usually by Vendor ID) 14e4 for Broadcom or 8086 (for Intel). If the device is grayed out or has an exclamation mark, it is not initialized.
| Problem | Possible cause | Solution method |
|---|---|---|
| There is no Wi-Fi icon | Kext not loaded | Check config.plist and file path |
| The module is not visible in IOReg | PCIe/ACPI issue | Add SSDT-PCI0 or DSDT patch |
| There is a network, but no internet | Incorrect routing/DNS | Check network settings and reset NVRAM |
| Kernel Panic | Driver conflict | Disable unnecessary kexts, check versions |
It's important to remember to reset the NVRAM. After any changes to the Wi-Fi configuration, especially those related to DeviceProperties, you must reset the bootloader's non-volatile memory. This can be done through the OpenCore menu (Reset NVRAM) or by pressing a hotkey during boot.
Diagnosing and troubleshooting common errors
Even with proper settings, you may still experience intermittent connection drops or low speeds. This could be due to software conflicts or issues with the antenna circuit. Make sure the antennas are connected to the correct ports on the card (Main and Aux).
Check the system logs. In the console (Console.app) you can filter messages by word kernel or WiFi. Errors of the type "firmware failed to load" will indicate a problem with the module firmware, and "link down" - problems with the signal or driver.
If all else fails, try creating a new user in macOS. Sometimes, issues with key permissions in the Keychain can block network services. Transferring settings to a new user often helps identify software conflicts at the profile level.
Why doesn't AirDrop work after setting up Wi-Fi?
AirDrop requires not only a working Wi-Fi connection but also a native Bluetooth module connected to the Wi-Fi card (usually an internal USB connection). If you have an Intel or Broadcom card without Bluetooth passthrough, AirDrop won't work. It also doesn't work over a guest network or when Stealth mode is enabled.
Can I use USB Wi-Fi adapters?
Theoretically, yes, if drivers for them exist for macOS (for example, some Realtek or MediaTek models). However, the performance and stability of such solutions are extremely low. They often overheat, lose connection, and don't support modern speed standards. This is an option only for extreme cases.
How to update drivers without reinstalling the system?
Drivers (kexts) are located in the EFI partition, not in the system itself. You just need to replace the files in the folder. EFI/OC/Kexts on a USB drive with a bootloader, update config.plist and reboot. Files in /Library/Extensions You don't need to touch it if you use OpenCore correctly.
Does motherboard BIOS version affect Wi-Fi?
Yes, it does. BIOS updates often change the ACPI table or IRQ allocation methods. After updating the BIOS, OpenCore settings may no longer work correctly. Always back up your working EFI before flashing the BIOS.