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

[jlrycm]

10 hours ago, eSaF said:

Sleep is broken on my machine, I need to look Into that.

Despite what the report says, AirDrop for me and others is not working.

I’m experiencing macOS Sequoia freezing from time to time which started happening right after I installed the BCM43602CS card. Also, if the computer goes to sleep it would panic and freeze which is one of the limitations reported in the repo.

[schrup21]

you can place the key bcmc-default-country-code in the DeviceProperty, type String, Value EU (kidding) - GB

there is also a bcmc-enable-auto-country which I believe sets the country code of your operating system

 

https://github.com/0xFireWolf/AppleBCMWLANCompanion/blob/main/Documentation/DeviceProperties.md

[kgp]

12 minutes ago, eSaF said:

As you can see from the attached pics, I believe the entries I made are correct, yet the Country Code is incorrect.

I will continue to search for a solution.

Cheers.

 

Your country code is GB, man 🙃! https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#Current_codes

 

key: bcmc-default-country-code Value: GB Type: STRING     

 

 

Edited October 17, 2025 by KGP-iMacPro

[kgp]

5 hours ago, jlrycm said:

I’m experiencing macOS Sequoia freezing from time to time which started happening right after I installed the BCM43602CS card. Also, if the computer goes to sleep it would panic and freeze which is one of the limitations reported in the repo.

 

As already stated several times, I am also experiencing random freezes (KPs) under both Tahoe and Sequoia with the AppleBCMWLANCompanion.kext enabled. Sleep/Wake is just impossible with the AppleBCMWLANCompanion.kext enabled. Instant KP on Sleep. You might want to upload KP logs for @Austere.J: System Information -> logs -> Panic (system crashes) log or /Library/Logs/DiagnosticReports/Kernel-2025-xx-xx-xxxxxx.panic.

Edited October 17, 2025 by KGP-iMacPro

[Anto65]

This

bcmc:OSData *AppleBCMWLANChipConfigurator:: readSROMFromRegisters() const Error: SROM Control [0x00000032] indicates that SROM is not present on this chip

 

makes me think that I have reached the end of the game, with the card BCM4350    0x14E4, 0x43A3

 

 

Apparently even if it seems to have all the requirements... something is missing in the Rom / Srom 🤔

 

It was just a curiosity, if it activates, I don't even use it.

[jlrycm]

3 hours ago, Anto65 said:

This

bcmc:OSData *AppleBCMWLANChipConfigurator:: readSROMFromRegisters() const Error: SROM Control [0x00000032] indicates that SROM is not present on this chip

 

makes me think that I have reached the end of the game, with the card BCM4350    0x14E4, 0x43A3

 

 

Apparently even if it seems to have all the requirements... something is missing in the Rom / Srom 🤔

 

It was just a curiosity, if it activates, I don't even use it.

@Anto65 have you defined this property which is required for your card?

bcmc-srom-slide:

Property Type: Data in Plist

Value: 40000000 in Plist

 

did you correctly type the firmware folder path and name in device properties? /usr/local/share/firmware/wifi/brcmfmac4350-pcie_7.35.180.119.bin

 

are you using device properties related to camouflaging your Wi-Fi chip? If yes, these settings may be the culprit.

Edited October 17, 2025 by jlrycm

[Anto65]

Why doesn't it work without those properties ? 😆

 

Of course, I even tried with and without camouflage and other flags, but nothing.

 

"SROM is not present on this chip"  persists.

 

Spoiler

 

 

[jlrycm]

8 hours ago, KGP-iMacPro said:

 

As already stated several times, I am also experiencing random freezes (KPs) under both Tahoe and Sequoia with the AppleBCMWLANCompanion.kext enabled. Sleep/Wake is just impossible with the AppleBCMWLANCompanion.kext enabled. Instant KP on Sleep. You might want to upload KP logs for @Austere.J: System Information -> logs -> Panic (system crashes) log or /Library/Logs/DiagnosticReports/Kernel-2025-xx-xx-xxxxxx.panic.

@KGP-iMacPro this is the most recent panic log I have. I also attached my wifi logs.Kernel-2025-10-14-002454.panicwifi.logwifi.log.0.bz2

Edited October 17, 2025 by jlrycm

[jlrycm]

3 hours ago, Anto65 said:

Why doesn't it work without those properties ? 😆

 

Of course, I even tried with and without camouflage and other flags, but nothing.

 

"SROM is not present on this chip"  persists.

 

  Hide contents

 

 

It seems like you need guidance / additional support from @Austere.J here

[kgp]

1 hour ago, jlrycm said:

@KGP-iMacPro this is the most recent panic log I have. I also attached my wifi logs.Kernel-2025-10-14-002454.panicwifi.logwifi.log.0.bz2

 

@jlrycm, I am not an expert in reading kernel panics, but most of my kernel panics (and there are quite few, see attachment) can be directly related with BCMC.

 

Investigating your panic report, I noticed, that we use quite different boot flags though:

 

Yours: -lilubetaall watchdog=0 darkwake=3 keepsyms=1 swd_panic=1 -btlfxboardid -hbfx-disable-patch-pci wlan.pcie.detectsabotage=0

 

Mine:  -v darkwake=0 keepsyms=1 debug=0x100 agdpmod=pikera wlan.pcie.detectsabotage=0 restrict=1 revpatch=pci,sbvmm -rtcfxex

 

I don't know if darkwake=3 isn't obsolete with Sequoia/Tahoe. As you also seem to use SMBIOS MacPro7,1 -> I am further missing in your boot flags restrict=1 revpatch=pci,sbvmm (PCI and Memory Fix). You don't use RestrictEvents.kext? Finally, -lilubetaall is obsolete. 

 

Just something that came to my mind additionally and might help somehow.. 

 

btw.. when booting your system in verbose mode (-v),  do you also get several times the error message: "couldn´t alloc class AppleBCMWLANCompanion" ???

 

Panic-logs.rtf

Edited October 17, 2025 by KGP-iMacPro

[jlrycm]

58 minutes ago, KGP-iMacPro said:

 

@jlrycm, I am not an expert in reading kernel panics, but most of my kernel panics (and there are quite few, see attachment) can be directly related with BCMC.

 

I noticed, that we use quite different boot flags though:

 

Yours: -lilubetaall watchdog=0 darkwake=3 keepsyms=1 swd_panic=1 -btlfxboardid -hbfx-disable-patch-pci wlan.pcie.detectsabotage=0

 

Mine:  -v darkwake=0 keepsyms=1 debug=0x100 agdpmod=pikera wlan.pcie.detectsabotage=0 restrict=1 revpatch=pci,sbvmm -rtcfxex

 

I don't know if darkwake=3 isn't obsolete with Sequoia/Tahoe. As you also seem to use SMBIOS MacPro7,1 -> I am further missing in your boot flags restrict=1 revpatch=pci,sbvmm (PCI and Memory Fix). You don't use RestrictEvents.kext? Finally, -lilubetaall is obsolete. 

 

Just something that came to my mind additionally and might help somehow.. 

 

Panic-logs.rtf 72.48 kB · 0 downloads

I use RestrictedEvents.kext. I forgot to remove the lilubetaall. I don’t use WEG so no agdpmod=pikera. Will verify the other boot args I have versus yours.

Edited October 17, 2025 by jlrycm

[kgp]

13 minutes ago, jlrycm said:

I use RestrictedEvents.kext. I forgot to remove the lilubetaall. About hbfx-disable-patch-pci, I don’t remember having this boot arg, will verify that. I don’t use WEG so no agdpmod=pikera. Will verify the other boot args I have versus yours.

 

Please mainly focus on darkwake, restrict=1 and revpatch=pci,sbvmm. I use -rtcfxex in line with RTCMemoryFixup.kext, which might not be of your interest anyway. I can use my system with and without WhateverGreen. 

 

Please also reply if, when booting your system in verbose mode (-v),  you also get several times the error message: "couldn´t alloc class AppleBCMWLANCompanion" ???

 

One more thing: as soon as I enable AppleBCMWLANCompanion.kext in my config.plist, "System Information" -> "PCI" is corrupted. It would be Interesting for me to know if you face the same issue. Everything is fine, if I just disable AppleBCMWLANCompanion.kext. 

 

Thanks in advance! 

Edited October 17, 2025 by KGP-iMacPro

[jlrycm]

11 minutes ago, KGP-iMacPro said:

 

Please mainly focus on darkwake, restrict=1 and revpatch=pci,sbvmm. I use -rtcfxex in line with RTCMemoryFixup.kext, which might not be of your interest anyway. I can use my system with and without WhateverGreen. 

 

Please also reply if, when booting your system in verbose mode (-v),  you also get several times the error message: "couldn´t alloc class AppleBCMWLANCompanion" ???

 

One more thing: as soon as I enable AppleBCMWLANCompanion.kext in my config.plist, "System Information" -> "PCI" is corrupted. It would be Interesting for me to know if you face the same issue. Everything is fine, if I just disable AppleBCMWLANCompanion.kext. 

 

Thanks in advance! 

I use darkwake=3 after reading that it was more convenient for my build. It's a combination of darkwake=1 and 2. I don't have the revpatch boot arg like you as for some reason I defined it in 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 NVRAM entry instead; I will change it to match what you have. My PCI information has no issues / is not corrupted. I will reboot with -v to see if I get the error message "couldn´t alloc class AppleBCMWLANCompanion" and report back here.

[jlrycm]

29 minutes ago, KGP-iMacPro said:

Please also reply if, when booting your system in verbose mode (-v),  you also get several times the error message: "couldn´t alloc class AppleBCMWLANCompanion" ???

@KGP-iMacPro I also have this error reported multiple times in the boot log.

[kgp]

1 hour ago, jlrycm said:

I use darkwake=3 after reading that it was more convenient for my build. It's a combination of darkwake=1 and 2. I don't have the revpatch boot arg like you as for some reason I defined it in 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 NVRAM entry instead; I will change it to match what you have. My PCI information has no issues / is not corrupted. I will reboot with -v to see if I get the error message "couldn´t alloc class AppleBCMWLANCompanion" and report back here.

 

The issue with "System Information" -> "PCI" on my system is really weird and I don't find any other culprit than AppleBCMWLANCompanion.kext. 

 

With AppleBCMWLANCompanion.kext disabled:

 

 

With AppleBCMWLANCompanion.kext enabled:

 

 

although under IOReg everything is properly implemented 

 

 

No idea, how to remove this issue...

Edited October 17, 2025 by KGP-iMacPro

[surenmunoo]

On 10/17/2025 at 5:54 AM, eSaF said:

Ok, since using this method to regain WIFI in Tahoe, I have been weighing up the pros and the cons.

Although it is good to have WIFI working again, quite frankly the Fenvi card gives me more satisfaction in operation.

 

Sleep is broken with no fix at the moment, also I don't know if this has any impact on the machine but the hard drive activity light is constantly blinking.

For some reason I cannot boot into Sequoia or Sonoma (using one EFI Folder for all), haven't tried to boot into Windows as yet.

 

At this point I will remove this card and replace it with the Fenvi.

Somewhat disappointed but if I didn't take the plunge, I would be wondering and feeling left out reading about success stories.

 

The developer is correct in advising not to rely on it as a daily driver, it is still in an infancy stage.

I must admit I have no panics or freezes while running on Tahoe until Sleep kicks in then I have to do a hard reset and reboot.

 

Although lacking WIFI and its dependencies, Fenvi for me is the better option, which BTW the Drivers are available to also work in Windows in a multi-boot setup.

For the love of all things good, cannot find drivers for this Apple Card in Windows.

 

Now that the excitement and novelty has worn off, it is too much faffing around for very little gain,

Cheers.

Thanks for doing the test mate, saves me money  

[jlrycm]

24 minutes ago, eSaF said:

Actually I still have the Card in the machine.

With very helpful guidance from @Anto65 I managed to get some stabilisation with it. 

 

Maybe it is a bit unfair to be too critical about it as both it and Tahoe are Betas so I guess it is not a very good combination at the moment.

Although we have full WIFI, AirDrop is not working, also I noticed with this Card wireless Hand-off to iPhone Camera is not working in Tahoe, Sequoia and Sonoma. It is only functioning via USB connection.

 

For the time being, I will keep the Card in the machine and just happily play with it and Tahoe until I purchase the Mac-Mini in the New Year.

The other reason the Card didn't end up in my box of bits and pieces, I was not too happy spending money on it just to be a failure which would give the wife ammo to chew my ears off. 

@eSaF I still hope the kext will evolve and be more stable in the future. For me, having basic wifi plus a bluetooth card that works OOB without having to use the Intel Bluetooth kexts is a positive.

[Anto65]

Let's hope... especially for the protection of eSaF's ears  🤭

[schrup21]

I have to say that in my case, BCMC is working absolutely stable—except for the known restrictions of course.

 

I think the panics could be more related to AppleVTD than to BCMC itself. The lack of DMA reservations set by the motherboard manufacturer (dropping DMAR.aml) can lead to instability, just as Apple's reservations can lead to conflicts. This is how I understand @Mieze explanation of AppleVTD in a Hackintosh.
I'm using a laptop; the original only has a few reservations, and I don't even have to drop them (it doesn't make a difference)—so perhaps in my case, the risk of some conflict is lower?

We can conclude that a Hackintosh isn't really compatible with AppleVTD, its alway a little gamble.

 

Btw. according the bcmc-chip/user-otp - I found Cypress's description about OTP Memory Programming, and that's quite interesting (You probably know that Infineon is the owner of Cypress and Cypress had acquired the IoT division of Broadcom, which includes the WiFi chips) - if you wanna take a look in it... 

This doesn't mean, that bcmc-chip-otp or bcmc-user-otp is connected to this - I don't know...

 

@eSaF You asked why your country code is NL even though it's set to GB (I guess it's still the case?). I had a Dell DW1830 (an M.2 with a BCM43602 chip) for a while – with that card, I could only use the US. When I set the country code to DE, Wi-Fi didn't work (or was extremely slow). I'm guessing there might be some hard-coded parameters - OTP means One Time Programmable

OTP Memory Programming.pdf

Edited October 18, 2025 by schrup21

[kgp]

@schrup21, the only reserved memory region in my DMAR is the XHCI controller. I don’t drop my DMAR, and honestly, I’ve only encountered a few KPs since using AppleBCMWLANCompanion.kext, almost all of which have been related to that kext. Sleep/Wake seems impossible anyway for now.

Rather than speculating about the cause of these KPs, I’d prefer to wait for @Austere.J’s feedback -  if he ever returns to this thread, which has unfortunately become a bit less focused and at times somewhat self-centered recently. Thanks for getting things back on track, anyway. BTW, I have no issues with country code “DE”. Everything works flawlessly. And finally,  this feedback might be also of interest for others. 😉  

Edited October 18, 2025 by KGP-iMacPro

[kgp]

17 minutes ago, eSaF said:

Easy there Bro!!! From the time Apple changed how connection is handled in Sonoma, then changed yet again in Sequoia and now Tahoe, each time the task to get our once working hacked Broadcom Cards got more and more difficult.

Initially it took the OCLP Devs almost a year to find a viable working solution for Sonoma with an appeal asking all to be patient as the task is not easy and then again same thing with Sequoia.

 

Placing @Austere.J in a projected box and possibly labelling it egocentric is in my opinion counterproductive to the project.

I can only assume he alone is working on this whereas the OCLP Devs has a whole team and as was recently announced, one prominent member left and joined Apple so that in it self is a set back.

 

Bro I am not in anyway bad mouthing you, I can feel and relate with your frustration but we have to be patient. I have faith a solution will be found sooner or later.

I still have the Apple Card installed and whenever I hit a snag, I tend to put the blame on it and muse about putting the Fenvi back in place.

 

At the moment my loss is Sleep, AirDrop and Wireless Handoff to iPhone camera, which I had with the Fenvi Card after OCLP patching Sequoia and Sonoma in my multi-booting setup all running off a single EFI Folder.

In essence for me the benefits of this Card at the moment is way below the Fenvi but I am willing to wait it out and see how the project progresses. Yes I will swear and mutter under my breath every time I hit a snag but berating developers for assumed delays won't help me.

As the last macOS journey on our Intel and AMD machines, you'd think as a parting gift Tim and Crew would make the experience easy, as it turned out, not so much but what you gonna do??!! 

Cheers.

 

Bro, just to clarify — my remark about the thread becoming a bit less focused and at times somewhat self-centered was, of course, not directed at @Austere.J. I was rather referring to the last discussion from last night above, which, in my opinion, felt somewhat counterproductive and a bit impolite -  as also reflected by my not-so-amused emojis at the time. And honestly, it was not the first time I felt such..  

Edited October 18, 2025 by KGP-iMacPro

[Anto65]

Guys, have a laugh every now and then ... it helps ( This doesn't mean we shouldn't take this thread seriously, but we certainly can't make a drama out of it.)
I understand how much this might concern you , but the real problems lie elsewhere. 👋

Edited October 18, 2025 by Anto65

[Andres ZeroCross]

On 10/17/2025 at 11:46 PM, KGP-iMacPro said:

 

The issue with "System Information" -> "PCI" on my system is really weird and I don't find any other culprit than AppleBCMWLANCompanion.kext. 

 

With AppleBCMWLANCompanion.kext disabled:

 

 

With AppleBCMWLANCompanion.kext enabled:

 

 

although under IOReg everything is properly implemented 

 

 

No idea, how to remove this issue...

 

Same here

[cfmwan]

Yse! Now I feel one step closer to perfection.

Edited October 22, 2025 by cfmwan

[cfmwan]

1 hour ago, Andres ZeroCross said:

 

Same here

Just don't inject the slot information of the wireless network card.