Broadcom FullMAC Wi-Fi support on macOS Sonoma, Sequoia and Tahoe without root patches

[Austere.J]

5 hours ago, arsradu said:

And the download speed difference is significant in my case. From a 300-400Mb/s download speed with VT-D enabled to 80-95Mb/s with it disabled...

 

Yes, this is expected as I documented here. When I tested BCMC with VT-d disabled, my Wi-Fi speed dropped from 500/300 Mbps to 130/130 Mbps (802.11ac, 5GHz, Channel 36).

 

@Mieze recently updated IntelLucy to add support for AppleVTD under macOS Tahoe. I assume that Mieze plans to bring that support to other Ethernet drivers as well?

 

Once the RTL8111 driver is updated, I strongly recommend enabling VT-d and removing the "bcmc-disable-io-mapper" property, which is really intended for users who cannot get AppleVTD working on their motherboards.

[kgp]

8 hours ago, Austere.J said:

 

Yes, this is expected as I documented here. When I tested BCMC with VT-d disabled, my Wi-Fi speed dropped from 500/300 Mbps to 130/130 Mbps (802.11ac, 5GHz, Channel 36).

 

@Mieze recently updated IntelLucy to add support for AppleVTD under macOS Tahoe. I assume that Mieze plans to bring that support to other Ethernet drivers as well?

 

Once the RTL8111 driver is updated, I strongly recommend enabling VT-d and removing the "bcmc-disable-io-mapper" property, which is really intended for users who cannot get AppleVTD working on their motherboards.

Talking about KPs, first at all, I am very happy with BCMC and both DEXT Driver and IntelLucy 1.1.5 just work flawless with AppleVTD enabled. However, from time to time, there are still random KPs with WIFI enabled. If I just toggle off WIFI, the system is rock solid, although AppleBCMWLANCompanion.kext version 1.1.0 remains enabled. I uploaded here KP logs already quite a while ago for the same issue with AppleBCMWLANCompanion.kext version 1.0.0. I don't know if they have been of any help in this issue.   

 

It would be absolutely gorgeous if we could totally remove the random KPs with AppleBCMWLANCompanion.kext, which are not frequent but still present and make my system just unstable . Due to OCLP-Mod (AppleHDA), I need to use csr-active-config 03080000 and AMFIPass.kext. I hope that these settings are not the cause of the remaining issues.

 

I don't mind about KP on sleep/wake. The KPs, I am talking about, occur during regular use of BCMC WIFI under Tahoe and are totally random. 

 

Nevertheless, congratulations for all the brilliant work you are doing and many thanks for all your extensive efforts for the community!

 

P.S.: just let me know if I can contribute to the further stabilisation of BCMC with further KP-logs or testing.

 

Alls the best,

 

KGP 

 

 

    

Edited November 29, 2025 by KGP-iMacPro

[Mieze]

@Austere.J I started working on AppleVTD support for RealtekRTL8111 after I finished IntelLucy and I'm already on the home straight. Expect a first test version soon.

 

Mieze 😺

[Wagalms]

Hey, huge congrats to developers @Austere.J (ELIAS64FR, CaseySJ) on the success of the latest version of the AppleBCMWlanCompanion driver!

This new version removes the need for AppleVTD, just like I suggested might be possible in my previous posts. Everything is working perfectly for me, since I really just need Wi-Fi for my schoolwork. @Austere.J, you're the man!

My machine is a Haswell i7 4510U (Hp Elitebook 850 G1/2016). It doesn't support VT-d, but it does have VT-x. Your new driver is a massive leap forward for the Hackintosh community. It's going to be a huge inspiration and a real time-saver for the OCLP 3.0.0 developers.

I'm super happy with this. If you ever come to Brazil, we're throwing a barbecue to celebrate together. Thanks for making this breakthrough available to countless users in this community.

Stay strong, warriors

 

Edited November 29, 2025 by Wagalms
To hide my SMBios and MAC address

[arsradu]

12 hours ago, Austere.J said:

I recall that you have an RTL8168 Ethernet card and you are using RealtekRTL8111? The Ethernet driver handles the interrupts when you unplug the cable. The freeze might be a sign of a kernel panic.

 

It is for sure a sign of KP, just can't pin point the cause... Could be Ethernet...but I don't recall ever having this issue before testing BCMC. But could be unrelated indeed... Will test more to confirm.

 

Z97S SLI Krait Edition motherboard is using, according to specs here, the RTL81111G controller.  

 

Update: I just realised I also never tested Ethernet with VT-D enabled.... So yeah, it could be Ethernet related rather than WiFi related.

Edited November 29, 2025 by arsradu

[kgp]

On 11/29/2025 at 11:03 AM, arsradu said:

 

It is for sure a sign of KP, just can't pin point the cause... Could be Ethernet...but I don't recall ever having this issue before testing BCMC. But could be unrelated indeed... Will test more to confirm.

 

Z97S SLI Krait Edition motherboard is using, according to specs here, the RTL81111G controller.  

 

Update: I just realised I also never tested Ethernet with VT-D enabled.... So yeah, it could be Ethernet related rather than WiFi related.

 

New version of RealtekRTL8111.kext, which adds support for AppleVTD under Tahoe 

 

 

[arsradu]

33 minutes ago, KGP-iMacPro said:

 

New version of RealtekRTL8111.kext, which adds support for AppleVTD under Tahoe 

 

 

Omg! So soon? I’m gonna give it a try asap.  Mieze, thank you so much!

[meg2014]

@Austere.J:

 

Slow boot times.

 

In Sequoia, I find that loading BCMC really slows down boot time.  Is this something that you have noticed or has been reported to you?  I do not see this problem in Sonoma (or perhaps it's not as prominent there).

 

So, if this is an issue with my system, well, fine, I most certainly can live with it.  But if you have any thoughts or tips, please comment here or drop me a PM.

 

I very much appreciate your work, and want to make sure you understand how much your utility has helped me.

 

[carlo_67]

Il 21/09/2025 alle 09:15, Austere.J ha detto:

Apple Broadcom Wi-Fi Companion (BCMC)

Rivivi le tue schede Wi-Fi Broadcom legacy su macOS Sonoma, Sequoia e Tahoe senza patch di root

 

 

>> Prologo

 

Ho iniziato questo progetto quando Apple ha rilasciato la prima versione beta per sviluppatori di macOS Sonoma perché non mi piace molto modificare il volume root e il downgrade dell'intero stack di rete wireless. Mentre ci lavoro a intermittenza, ho un prototipo relativamente stabile e vorrei invitare le persone a partecipare al beta test pubblico.

 

Si prega di utilizzare questo thread per discussioni generali e rapporti di prova.

 

>> Introduzione

 

Apple Broadcom Wi-Fi Companion (BCMC) è un'estensione del kernel macOS progettata per schede Wi-Fi Broadcom FullMAC selezionate. Consiste in un driver di dispositivo che configura chip Wi-Fi legacy e un plugin Lilu che garantisce la compatibilità con il nuovo driver Wi-Fi di Apple.

 

Le seguenti informazioni potrebbero non essere sempre aggiornate.

Si prega di fare riferimento al repository GitHub per informazioni aggiornate.

 

>> Sistemi supportati

• macOS Tahoe
  • 26,0 (25A354)
• macOS Sequoia
  • 15,7 (24G222)
• macOS Sonoma
  • 14.8 (23J21) (Non ancora verificato)

Si noti che altri sistemi non sono stati testati. I vecchi sistemi non saranno supportati a causa dell'onere di manutenzione.

 

>> Chip Wi-Fi supportati

• BCM43602 (0x14E4, 0x43BA)
• BCM4350 (0x14E4, 0x43A3)

Si noti che i chip Wi-Fi SoftMAC non sono e non saranno supportati.

 

>> Stato attuale

• BCMC è sottoposto a beta test pubblici e non è destinato all'uso quotidiano nei sistemi di produzione.
• BCMC è stato testato sotto macOS Sequoia 15.7 e macOS Tahoe 26.0.
• BCMC è stato testato con più test di velocità di rete e ha raggiunto una velocità di download di circa 500 Mbps e una velocità di caricamento di circa 300 Mbps (Ambiente di prova: Indoor, 802.11ac, 5GHz, Canale 36, Velocità massima Internet: 1 Gbps).
• BCMC è stato testato con frequenti commutati tra più punti di accesso e reti wireless protette da WPA2.
• BCMC è stato testato con applicazioni di mappa che si basano sul Wi-Fi per determinare la posizione attuale.

 

>> Iniziare

 

Si prega di leggere attentamente il manuale e aggiornare correttamente il file di configurazione del bootloader.

I binari predefiniti sono disponibili su GitHub: https://github.com/0xFireWolf/AppleBCMWLANCompanion

Il codice sorgente non è attualmente disponibile.

 

>> Proprietà del dispositivo e argomenti di avvio

 

Si prega di fare riferimento al manuale per l'elenco completo.

 

>> Domande

 

Sentiti libero di pubblicare le tue domande e aiutarti a vicenda qui.

 

Goditi 

 

-- Lupo di fuoco

BCM943224PCIEBT2  I managed to get this card working on AMD with Sequoia, it was from a late 2011 macbook air, no longer supported by Catalina

https://macos86.it/topic/7236-oclp-il-wi-fi-è-tornato-in-macos-sonoma-e-piu-recenti/page/25/#comment-158851

[jlrycm]

3 hours ago, carlo_67 said:

BCM943224PCIEBT2  I managed to get this card working on AMD with Sequoia, it was from a late 2011 macbook air, no longer supported by Catalina

https://macos86.it/topic/7236-oclp-il-wi-fi-è-tornato-in-macos-sonoma-e-piu-recenti/page/25/#comment-158851

So you made it work not using @Austere.J’s Apple Broadcom Wi-Fi Companion (BCMC) kext, right?

[carlo_67]

yes

[meg2014]

@Austere.J:

 

I have another issue I would like some help with.  I am only getting 24 Mbps on my BCMC devices, but other devices (that don't have BCMC enabled) using WiFi get much much faster throughput than that.

 

Anyone else seeing this issue?  Is it possible that my Mac is improperly reporting the TX speed?

Edited January 11 by meg2014
erroe

[jlrycm]

2 minutes ago, meg2014 said:

@Austere.J:

 

I have another issue I would like some help with.  I am only getting 24 Mbps on my BCMC devices, but other devices that have WiFi get much much faster throughput than that.

 

Anyone else seeing this issue?  Is it possible that my Mac is improperly reporting the TX speed?

Are you using the Broadcom Wi-Fi Companion (BCMC) kext with Apple VTD disabled? If yes, degraded network speed was expected as explained in the Kext repo manual https://github.com/0xFireWolf/AppleBCMWLANCompanion/blob/main/Documentation/GettingStarted.md.

[meg2014]

Thanks for the thought, but I am using VTD with BCMC

[schrup21]

@meg2014

 

https://github.com/0xFireWolf/AppleBCMWLANCompanion/blob/main/Documentation/Issues.md#incorrect-transmit-rate-shown-in-the-wi-fi-menu

[jlrycm]

3 hours ago, schrup21 said:

@meg2014

 

https://github.com/0xFireWolf/AppleBCMWLANCompanion/blob/main/Documentation/Issues.md#incorrect-transmit-rate-shown-in-the-wi-fi-menu

@meg2014 per the link above, it sounds like what you report here is a bug in the firmware causing the wifi menu to display the incorrect transmit rate. Is your card a BCM43602 which is the one having this bug? Have you tested your actual transmit rate in some way? I have a BCM43602 chip too so I’ll check if I see the same bug at my end.

[meg2014]

20 hours ago, jlrycm said:

@meg2014 per the link above, it sounds like what you report here is a bug in the firmware causing the wifi menu to display the incorrect transmit rate. Is your card a BCM43602 which is the one having this bug? Have you tested your actual transmit rate in some way? I have a BCM43602 chip too so I’ll check if I see the same bug at my end.

 

Yes, it is a bug.  At least it is on my system.

[floodlitworld]

I've been following this project for a few months now, and it's seriously impressive.

 

I have a Fenvi-T919 with a BCM_20702B0 chipset. Will this ever be within the scope of this project, or is it not possible to support this chipset using this method?

[schrup21]

3 hours ago, floodlitworld said:

Fenvi-T919 with a BCM_20702B0

This is the Bluetooth chip of the BCM94360CD module on the Fenvi. Unfortunately, there is no Fullmac firmware for it – it is not supported.

The module should be replaceable with a BCM943602CDP; both should have the same antenna connectors.

 

Fenvi T919

Spoiler

 

[Henties]

@all I spent considerable time today in configuring a universal OC 1.06 EFI in a way that I can start Sequoia 15.7.4 (24G503) without root patches and Tahoe 26.2 (25C56) with OCLP 3.1.4. 

 

It wasn't too difficult to get it all working using MinKernal 25.0.0 in a way that the kexts required for root patching only get started when booting Tahoe.

 

In the end I however I decided to revert back to root patching both Sequoia as well as Tahoe because of the loss of functionality of one of my NICs which require VTD and for which a kext making it work without VTD and for which DisableIomapper must stay on, is not and will probably never be available.

 

Another annoying drawback is the fact that Sequoia, when not root patched, still freezes when it enters sleep mode.

 

Staying with OCLP 3.1.4 for both Sequoia as well as Tahoe provides me with all the particular Apple gimmick features that a working WiFi stack provides and that I need and am interested in, of which unlocking my hacks via my Apple watch now works on all 4 of my hacks, with each hack able to boot Sequoia or alternatively Tahoe and able to be unlocked by my Apple chronometer.  

 

For the time being I will therefore wait for further advances in the development and refinement of the "without root patching" method before I will experiment with that method again. Since the last time I played with that method there seems not to have been any noticeable advance in solving issues that plague me in my particular environment.

 

It actually appears to me that development in this direction has come to a grinding halt, although I may actually be wrong on this score.

 

Greetings Henties

Edited January 18 by Henties

[jlrycm]

1 hour ago, Henties said:

@all I spent considerable time today in configuring a universal OC 1.06 EFI in a way that I can start Sequoia 15.7.4 (24G503) without root patches and Tahoe 26.2 (25C56) with OCLP 3.1.4. 

 

It wasn't too difficult to get it all working using MinKernal 25.0.0 in a way that the kexts required for root patching only get started when booting Tahoe.

 

In the end I however I decided to revert back to root patching both Sequoia as well as Tahoe because of the loss of functionality of one of my NICs which require VTD and for which a kext making it work without VTD and for which DisableIomapper must stay on, is not and will probably never be available.

 

Another annoying drawback is the fact that Sequoia, when not root patched, still freezes when it enters sleep mode.

 

Staying with OCLP 3.1.4 for both Sequoia as well as Tahoe provides me with all the particular Apple gimmick features that a working WiFi stack provides and that I need and am interested in, of which unlocking my hacks via my Apple watch now works on all 4 of my hacks, with each hack able to boot Sequoia or alternatively Tahoe and able to be unlocked by my Apple chronometer.  

 

For the time being I will therefore wait for further advances in the development and refinement of the "without root patching" method before I will experiment with that method again. Since the last time I played with that method there seems not to have been any noticeable advance in solving issues that plague me in my particular environment.

 

It actually appears to me that development in this direction has come to a grinding halt, although I may actually be wrong on this score.

 

Greetings Henties

You can try @Austere.J kext without VTD enabled to see how it performs in your case. Just need to use the device property  bcmc-disable-io-mapper

Edited January 18 by jlrycm

[NEOSoftWare]

Unable to boot the system:
- Module BCM943602CS (0x14E4, 0x43BA)
- BIOS Vt-d - disable
- DisableIoMapper - true, DisableIoMapperMapping - true
- File loaded: /usr/local/share/firmware/wifi/brcmfmac43602-pcie_7.35.177.61.bin
- Device path: PciRoot(0x0)/Pci(0x1C,0x2)/Pci(0x0,0x0)
- Properties set: bcmc-firmware-hash and bcmc-firmware-path
When enabling the AppleBCMWLANCompanion.kext kext, I get a kernel panic

Spoiler

Third-party modules like iOSkywalkFamily.kext, AirportBrcmFixup.kext, IO80211FamilyLegacy.kext, etc. are missing.
Without AppleBCMWLANCompanion.kext, the system boots (Wi-Fi, of course, doesn't work).

Spoiler

 

[jlrycm]

7 hours ago, NEOSoftWare said:

Unable to boot the system:
- Module BCM943602CS (0x14E4, 0x43BA)
- BIOS Vt-d - disable
- DisableIoMapper - true, DisableIoMapperMapping - true
- File loaded: /usr/local/share/firmware/wifi/brcmfmac43602-pcie_7.35.177.61.bin
- Device path: PciRoot(0x0)/Pci(0x1C,0x2)/Pci(0x0,0x0)
- Properties set: bcmc-firmware-hash and bcmc-firmware-path
When enabling the AppleBCMWLANCompanion.kext kext, I get a kernel panic

  Hide contents

Third-party modules like iOSkywalkFamily.kext, AirportBrcmFixup.kext, IO80211FamilyLegacy.kext, etc. are missing.
Without AppleBCMWLANCompanion.kext, the system boots (Wi-Fi, of course, doesn't work).

  Hide contents

 

@NEOSoftWare With VTD disabled, you have to define the device property bcmc-disable-io-mapper as 01000000 in your config.plist file as explained in the repo manual. Otherwise, you’ll have to enable VTD. If your Ethernet requires VTD to be disabled, the property bcmc-disable-io-mapper is required to be set as 01000000 in the config file.

Edited January 20 by jlrycm

[NEOSoftWare]

4 hours ago, jlrycm said:

@NEOSoftWare With VTD disabled, you have to define the device property bcmc-disable-io-mapper as 01000000 in your config.plist file as explained in the repo manual. Otherwise, you’ll have to enable VTD. If your Ethernet requires VTD to be disabled, the property bcmc-disable-io-mapper is required to be set as 01000000 in the config file.

Thanks, that helped.
I have a Realtek 8111 network card, and it doesn't seem to matter whether VTD is enabled or not.
 

In the BIOS, VTD - enable, bcmc-disable-io-mapper 00000000 - the computer won't boot and freezes.

If I set the BIOS to VTD - disable, bcmc-disable-io-mapper 01000000, the computer boots, WiFi works, but sleep mode doesn't work. The screen goes blank, the USB power goes out (I can see this from the indicator on the mouse), but the fans don't stop, and I can't wake it up with either the power button or USB devices. Can you tell me how to fix this?

[jlrycm]

On 1/20/2026 at 3:47 AM, NEOSoftWare said:

Thanks, that helped.
I have a Realtek 8111 network card, and it doesn't seem to matter whether VTD is enabled or not.
 

In the BIOS, VTD - enable, bcmc-disable-io-mapper 00000000 - the computer won't boot and freezes.

If I set the BIOS to VTD - disable, bcmc-disable-io-mapper 01000000, the computer boots, WiFi works, but sleep mode doesn't work. The screen goes blank, the USB power goes out (I can see this from the indicator on the mouse), but the fans don't stop, and I can't wake it up with either the power button or USB devices. Can you tell me how to fix this?

@NEOSoftWare I don’t know if you are using Tahoe so I’m sharing this FYI: mieze added Tahoe support to VTD for Realtek 8111 kext in the release below linked. If nothing else in your build forces you to disable VTD, you should keep VTD enabled in the BIOS and config file (disableiomapper set to false) and use both Mieze kext and AppleBCMcompanion kext. AppleBCMcompanion kext will deliver better wifi speeds with VTD enabled. Forget about sleep as this kext has not been updated yet to support sleep.

 

https://github.com/Mieze/RTL8111_driver_for_OS_X/releases

 

 

Edited January 21 by jlrycm