wifi enabled but no networks showing sequoia

[fgxr8]

Hi all 

 

I have the bcm4360 module (via a pcie card)

 

blue tooth is working and wifi is enabled see attached screenshots (wifi is not faulty as it works flawlessly in windows)

also have attached EFI (please note I have removed the larger kexts to meet the file upload size and just placed dummy kexts witht he same name- just for sake of completeness)

however it finds no wifi networks

 

disableiomapper has been disabled

nvram was reset multiple times

EFI.zip

[strangeron]

with OCLP...

 

Edited November 22, 2025 by strangeron

[schrup21]

19 hours ago, strangeron said:

with OCLP...

 

Y

You don't need any Fixup KEXTs for any BCM94360x - turn them off or better delete them. 

You should set MaxKernel to 24.99.99, because as for now, there's no Tahoe Modern Wifi Patch available, so you don't want have the KEXTs or the Excluding active in Tahoe.

I guess you already have AMFIPass.kext activated - AMFIPass would be a better choice than the bootarg amfi=0x80.

 

The latest Wifi and AMFIPass KEXTs can be found here: 

https://github.com/dortania/OpenCore-Legacy-Patcher/tree/main/payloads/Kexts/Wifi 

https://github.com/dortania/OpenCore-Legacy-Patcher/tree/main/payloads/Kexts/Acidanthera 

 

@fgxr8 If I remember correctly, wrong connected or missing antennas can cause the module not getting initialized - macOS probes them. You also should check /var/log/wifi.log

Edited November 23, 2025 by schrup21

[fgxr8]

On 11/22/2025 at 3:14 PM, fgxr8 said:

Hi all 

 

I have the bcm4360 module (via a pcie card)

 

blue tooth is working and wifi is enabled see attached screenshots (wifi is not faulty as it works flawlessly in windows)

also have attached EFI (please note I have removed the larger kexts to meet the file upload size and just placed dummy kexts witht he same name- just for sake of completeness)

however it finds no wifi networks

 

disableiomapper has been disabled

nvram was reset multiple times

EFI.zip 3.43 MB · 4 downloads

 

 

 

 

https://limewire.com/d/ktG6l#pBqNFxg4ZL

 

here is the full EFI, had to use external upload site

 

Stats: i9-9900k, asus z390f mobo, radeon 6700xt, 32gb ram, bcm4360 bluetooth/wireless (via pcie card)

[schrup21]

I doubt there's a config problem, otherwise your module won't show up.

 

In general, I recommend setting a separate SSID for 2.4 GHz Wi-Fi on your router so that macOS uses only 5 GHz Wi-Fi. There are known issues with Bluetooth and 2.4 GHz Wi-Fi coexisting.

 

As mentioned previously, your problem could be caused by incorrect or faulty antenna connections. Try swapping the MAIN and AUX connections.

 

Which module do you have? If it's a BCM94360NG it might be the module itself, that's causing the issues - actually only BCM94360CS,  BCM94360CS2, BCM94360CD are native Apple Modules.

[deeveedee]

@fgxr8 I'm inclined to agree with schrup21 that it's not a config problem.  My suggestion would be to test with macOS Ventura (which did not need any Wi-Fi framework patching) to eliminate any physical issues with the card/antennas and to eliminate any issues with OCLP post-install patching.  To test macOS Ventura, you can disable the following kexts in your config.plist:

• IOSkywalkFamily.kext
• IO80211FamilyLegacy.kext
• IO80211FamilyLegacy.kext/Contents/PlugIns/AirPortBrcmNIC.kext
• AMFIPass.kext

Disable Kernel > Block for "Allow IOSkywalkFamily Downgrade"

Also for your Ventura testing, you won't need to apply an OCLP patches.

 

Once you have Wi-Fi working in macOS Ventura, then you can proceed to later versions of macOS.

 

 

Also, while not related to your Wi-Fi issues, you do not need SSDT-UIAC.  This SSDT does nothing with USBMap.kext.  You can delete it from folder OC/ACPI and remove it from ACPI > Add in your config.plist.

 

EDIT: I see that you have implemented MinKernel 23.0.0 properties for all but AMFIPass.kext, so you should be able to test Ventura with minimal changes to your config.plist.

Edited November 23, 2025 by deeveedee

[fgxr8]

Thank you both

 

 

anyway as a last ditch before installing the other os's i ran into a OCLP guide, ran it, and rebooted, and voila wifi is connected.

 

Also thanks for the ACPI tip @deeveedee

[LockDown]

1 hour ago, fgxr8 said:

i ran into a OCLP guide, ran it, and rebooted, and voila wifi is connected.

what was it then?

[fgxr8]

2 hours ago, LockDown said:

what was it then?

 

not really sure ot be honest, ran the OCLP it did its magic and now it seems to connect and work.

[deeveedee]

@fgxr8 If I'm understanding you, it seems as though Open Core Legacy Patcher (OCLP) post install patches for Wi-Fi were not installed.  When you "ran the OCLP" and "it did its magic" that would have installed the patches which resulted in working Wi-Fi.  Am I understanding correctly?

[fgxr8]

8 hours ago, deeveedee said:

@fgxr8 If I'm understanding you, it seems as though Open Core Legacy Patcher (OCLP) post install patches for Wi-Fi were not installed.  When you "ran the OCLP" and "it did its magic" that would have installed the patches which resulted in working Wi-Fi.  Am I understanding correctly?

yeah before i was starting to downgrade and try other olde ros this seemed like a quicker fix

 

ran the oclp wifi fic patch (with sam eefi and didnt touch anythign else) reset nvram, and it booted back into a working wifi connection

[deeveedee]

@fgxr8 It looks like @strangeron figured that out here and I completely missed it.  I thought you had applied the OCLP patches - my mistake. Glad all is working for you now.