[HOW TO] Wi-Fi 6 Intel AX210 on macOS Sonoma

[Leesureone]

@Leesureone
I think that replacing kext is not mandatory.
Disable strategy doesn’t need replacement. But if the blocked kext has dependencies or is required by macOS can be a major problem.
Exclude strategy usually needs replacement.

AirPortBrcmNIC.kext is included in AirportBrcmFixup.kext, you can get older versions here.

I appreciate the explanation and I forgot just how many kexts are included in the AirportBrcmFixup.kext

 

[miliuco]

@Leesureone
Sorry, I edited my post while you were posting. AirportBrcmFixup.kext includes AirPortBrcm4360_Injector.kext and AirPortBrcmNIC_Injector.kext but, as you named specifically AirPortBrcmNIC.kext, I redirect the post towards IO80211FamilyLegacy.kext.

 

[Leesureone]

@Leesureone
Sorry, I edited my post while you were posting. AirportBrcmFixup.kext includes AirPortBrcm4360_Injector.kext and AirPortBrcmNIC_Injector.kext but, as you named specifically AirPortBrcmNIC.kext, I redirect the post towards IO80211FamilyLegacy.kext.

Just wanted to report back that using this similar Cudy New AX5400 Wireless WiFi 6E PCIe Card for PC, Bluetooth 5.2, AX210, 5400Mbps WiFi 6E Speed, Bluetooth 5.2/5/4.2/4.0, 802.11ax/ac/a/b/g/n, Windows 11, 10, WE3000 V2 I do not need to disable kexts (IOSkywalk.kext, IO80211FamilyLegacy.kext and AirPortBrcmNIC.kext) or disable IOSkywalk.kext blocking.

Wireless and Bluetooth works fine with OpenIntelWireless kexts for Sonoma, similar to if you were using an onboard intel card.

 

[miliuco]

@Leesureone
Yes, this Cudy PCIe piece integrates the same Intel AX210 wifi card.
All Intel wifi cards work with OpenIntelWireless kexts, they don’t need OCLP settings, only Broadcom and Atheros chipsets need OCLP settings.

 

[XanthraX]

Yes. So far, only Apple features as Airdrop, Continuity Camera, etc. are missing. Wifi and BT modules work fine for the rest of features.

Thank you so much for the explanations. I use Continuity Camera. So I stay with Ventura, at least for a while.

 

[Leesureone]

@Leesureone
Yes, this Cudy PCIe piece integrates the same Intel AX210 wifi card.
All Intel wifi cards work with OpenIntelWireless kexts, they don’t need OCLP settings, only Broadcom and Atheros chipsets need OCLP settings.

Sorry, I totally missed the part where you say Revert OCLP Changes…. I wrongly assumed this was a guide starting from scratch or no working WiFi or Bluetooth.

 

[Leesureone]

@Leesureone
Yes, this Cudy PCIe piece integrates the same Intel AX210 wifi card.
All Intel wifi cards work with OpenIntelWireless kexts, they don’t need OCLP settings, only Broadcom and Atheros chipsets need OCLP settings.

I've been tinkering with the Cudy PCIe card I mentioned and was having issue with sleep on my Asus Rog Crosshair X670E. With the Fenvi T919 I had previously installed sleep worked perfectly, I used the exact same internal USB port so it was a bit of a head scratcher as to why. I had the same behavior in both Ventura and Sonoma the only difference being the version of the AirportItwm.kext, the system would try to sleep but then immediately start running again.
Very odd, I ended up having to ditch the Cudy card in favor of the Fenvi AX210 model and now everything works perfectly as before. I would stay away from the Cudy PCIe card in favor of the model below.

https://www.amazon.com/gp/product/B08VWRW7X7/?tag=tonymacx86com-20

EDIT: Turns out it was a usb port mapping issue. Different pins on the USB header utilized causing the issues and need to remap ports.

 

[Edhawk]

@Leesureone did the two PCIe cards have the same USB cable layout, i.e. did the cables line up the same way in the motherboard header, usually on the bottom row of the header plug.

I have a number of different PCIe adapter cards from different manufacturers that have different 9-pin header cables. A couple of these don't line up and connect to the same USB port, when the cable is plugged in to the same header. I have had to change the Internal port so the new BT module works, when swapping a couple of the cards.

Each row of pins in the 9-pin header plug aligns with a specific USB port. So if the cables are in the bottom row in the header plug they will work only with the bottom USB port. Same goes for a cable plug where the cables are aligned in the top row of the header plug.

The issue comes when you have a cable that works in the header with the cables connecting the bluetooth module to the bottom USB port. Then switch PCIe adapter and cables and the second cable has the cables set to work with the USB port in the top row. The Bluetooth won't work in this case, not without first changing/activating the top USB port from the motherboard header.

When configuring our USBPorts.kext or USBMap.kext we would naturally only activate the USB port used by the Bluetooth module, the second USB port served from the header connector would be disabled/excluded from the kext, so as to keep within the 15 port limit.

 

[miliuco]

@Edhawk and others

I have the 3 BT kexts:

1. IntelBluetoothFirmware.kext
2. IntelBTPatcher.kext
3. BlueToolFixup.kext

BT looks working but System Profiler >> Bluetooth >> Chipset says THIRD_PARTY_DONGLE. Do you have any idea about it? Because I saw that your BT has a specific chipset name.

 

[Edhawk]

Those are the kexts I am using, and they are sorted in that order in the config.plist. I didn't need to do anything else to get the Intel AX210's Bluetooth module working in Sonoma.

No idea why the chipset name would be different in my setup, I haven't added any device properties or anything like that to make the BT module show differently.