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

[kgp]

1 hour ago, cfmwan said:

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

 

No matter, if I inject or don't inject additional PCIe device information for Broadcom WIFI via SSDT. As soon AppleBCMWLANCompanion.kext is enabled, all PCI information under System Information is gone on my system.   

[vinegar]

Also going back to OCLP for the time being. I don't need airdrop and don't use sleep, however i could not solve the random, overnight KPs in wifianalyticsd with my DW1830.

 

I really like the idea, but it's not stable enough yet. It's a shame source is not available for anyone to help if the author is going to be MIA.

[jlrycm]

4 hours ago, vinegar said:

Also going back to OCLP for the time being. I don't need airdrop and don't use sleep, however i could not solve the random, overnight KPs in wifianalyticsd with my DW1830.

 

I really like the idea, but it's not stable enough yet. It's a shame source is not available for anyone to help if the author is going to be MIA.

I’m considering to try sleepwatcher to deal with the KPs affecting the build sleep.

[HandaTakuya]

Hello,

I came across this project, and it looks really interesting. I used to have a BCM94360CS2 Wi-Fi card, but since it’s not compatible, I replaced it with a BCM943602CS specifically for this project.

I followed the guide carefully, but it didn’t work for me. When I booted with the -v flag, I got the message:
Couldn't alloc class "AppleBCMWLANCompanion"
I’m not sure if I made a mistake in my configuration or missed something.

P.S. I’m a Clover user — is there any guide or example configuration for the Clover bootloader?

 

 

[cfmwan]

To install this driver, you must turn on VD-T to load it. There is no Clover configuration, only OC configuration. See here for details.And closeDisableIoMapper，This is a required option.

config.plist

Edited October 24, 2025 by cfmwan

[HandaTakuya]

12 hours ago, cfmwan said:

To install this driver, you must turn on VD-T to load it. There is no Clover configuration, only OC configuration. See here for details.And closeDisableIoMapper，This is a required option.

config.plist 61.65 kB · 5 downloads

 

Oh, thank you so much! DisableIoMapper is also available in Clover Configurator — I turned it off, and my Wi-Fi started working again!!

 

 

 

However, there’s a side effect when disabling DisableIoMapper: my Ethernet stopped working, and the PCI section doesn’t load in the System Report anymore.

 

[Mieze]

@HandaTakuya My RTL8111 ethernet driver is incompatible with AppleVTD under Tahoe and there is no easy solution in sight. You'll have to decide which one you want to use. Frankly, I don't understand why anybody is considering to use BCBM for a production system at the moment. There might be KPs and sleep is also broken, which makes it unsuitable for productive work. BCMC is a remarkable piece of work, but at the moment, it's nothing more than a prove of concept.

 

Mieze 😺

[HandaTakuya]

19 minutes ago, Mieze said:

@HandaTakuya My RTL8111 ethernet driver is incompatible with AppleVTD under Tahoe and there is no easy solution in sight. You'll have to decide which one you want to use. Frankly, I don't understand why anybody is considering to use BCBM for a production system at the moment. There might be KPs and sleep is also broken, which makes it unsuitable for productive work. BCMC is a remarkable piece of work, but at the moment, it's nothing more than a prove of concept.

 

Mieze 😺

 

Thank you so much for replying about the RTL8111 Ethernet issue.
For me, since I’ve installed macOS Tahoe on my laptop, I haven’t been able to use Wi-Fi when I’m outside. As OCLP for Tahoe hasn’t been released yet, this workaround seems like an interesting alternative while waiting for OCLP support.
Even though it’s still not possible to use Wi-Fi and Ethernet simultaneously, at least I now have Wi-Fi working when I’m away from home.
Thanks again!

Edited October 24, 2025 by HandaTakuya

[jlrycm]

Hello Everyone! Below is the feedback and technical explanation about the sleep/wake issues provided by @Austere.J in GitHub 

 

Thanks for your interest in this project and for joining the beta testing.

The kernel panic (that happens when you put your computer to sleep) has nothing to do with the device properties, and I knew there would be a kernel panic before I even tried it while writing the Known Issues section.

I haven't yet looked into the power management routines, because I usually prioritize getting all necessary functionality working before tackling sleep/wake issues.

To give you a bit of technical detail, the Wi-Fi driver relies on another driver AppleOLYHALMac.kext, which requires a couple of ACPI methods to manipulate the GPIO signals. Instead of asking you all to add another SSDT with all the required dummy ACPI methods implemented, I decided to zero out some initialization routines in AppleOLYHALMac, and as a result, left some objects uninitialized (null pointers). When you put your computer to sleep, the Wi-Fi driver invokes the interface exposed by AppleOLYHALMac to change some power settings (because there is real platform device called AMFM on a real Mac). However, since the objects are null, a page fault would occur, as indicated by the kernel panic report uploaded by @andreszerocross (by the way, thanks for uploading the report -- this is exactly what I need for solving a problem).

I understand that you all want sleep/wake to work properly, but there is a lot of work that needs to be done behind the scenes. Yes, I can easily patch the OLY driver to avoid the page fault. However, the Wi-Fi chip will probably be powered off while your computer is sleeping, so when your computer wakes up, the driver needs to power it back on and download the firmware to the chip again. I need to analyze and understand the control flow and make sure that each step is compatible with legacy Wi-Fi chips, which requires significant reverse engineering effort and takes time. As such, I would appreciate your patience as I work through this.

 

 

[Austere.J]

Please note that I started replying from the first unread post, so I don't have the latest context.

Someone else might have already solved your problem, but I'll leave my thoughts and comments in case they're useful to someone else.

 

On 10/1/2025 at 10:24 PM, schrup21 said:

I would say they only work partially (at least for me)

-from iPhone to Mac: e.g. photos aren't always transmitted successfully at the first try

-from Mac to iPhone:  neither clipboard nor handoff is working

 

This might be an issue with DW1830's bluetooth. I remembered that handoff was partially broken when my laptop was running macOS Ventura.

 

On 10/2/2025 at 1:59 AM, KGP-iMacPro said:

 

Hi @Austere.J ,

 

many thanks for your quick reply to my fundamental question above. Really amazing and incredible what you achieved so far..

 

1.) I am using latest official BIOS 4701 and yes, I already contacted ASUS regarding the missing IOMMU/VT-d implementation of the X550-AT2 NICs on the WS X299 Sage/10G, but as expected and at least officially, they don’t provide any support or solution for macOS-related issues.

 

2.) I assume that many users are in a similar situation and depend on DisableIOMapper=true for Ethernet access, not only on X299 but also on other platforms where NIC drivers fail with AppleVTD enabled.

That’s why I think it would be worth considering a DMA-based Apple Wi-Fi patch that works without AppleVTD/IOMMU.

 

3.) Of course, this would only make sense if you succeed in enabling all continuity features – and especially AirDrop – with your patch. I guess this latter point would be of particular interest to all users relying on your solution.

 

Many thanks for your genius and hard work, anyway! 

 

KGP

 

First, double check all kexts related to the native network stack are unmodified, especially if you have used OCLP root patches before.

Details can be found in the OpenCore Legacy Patcher Users section at here: https://github.com/0xFireWolf/AppleBCMWLANCompanion/blob/main/Documentation/GettingStarted.md#check-your-system-integrity.
Make sure that the original IOSkywalkFamily.kext is not blocked.

 

Second, your Intel Ethernet should be supported by Apple's DriverKit (DEXT) driver. Enable the IOMMUs, set DisableIOMapper=false, and check whether your Ethernet cards work properly with Apple's driver.

 

On 10/2/2025 at 3:11 AM, eSaF said:

@Austere.J This is a most interesting and encouraging project.

As an owner of a BCM Card I was very excited at the thought of a major breakthrough having WIFI and all its decencies functional in Tahoe.

 

I was quite disappointed to learn that alas my Fenvi T-919 Card didn't qualify.

This left me contemplating whether to purchase a compatible Card only to find that not all Apple Services, one in particular that I use regularly, AirDrop is not available.

 

Considering this is our last macOS version on our Hacks, I would like to have access to all Apple Services.

Please understand I am not knocking the Project and think your progress is very admirable and hope you'll be able to fully increase the availability of all Services.

 

As other members here, I will continue to watch with enthusiasm and hope.

Good luck and thanks.

 

Thanks for your interest in this project. If you heavily rely on AirDrop daily, then you might want to stay with macOS Sequoia and use OCLP instead.

 

On 10/2/2025 at 8:04 AM, deeveedee said:

I tested this solution with my old Broadcom BCM 94352HMB (BCM4350 0x14E4).  The AppleBCMWLANCompanion.kext loads in Tahoe, but as stated in this thread, unable to connect via WPA/WPA2.  Just reporting in case this helps.

 

The chip model in your comment is confusing. 
BCM94352HMB uses the BCM4352 chip which is 0x14E4,43B1, while BCM4350 is 0x14E4,43A3.
So you probably have a card with BCM4350. Good to know that BCMC can load. Stay tuned as I am working on the WPA/WPA2 4-way handshake for BCM4350.

 

On 10/3/2025 at 6:06 AM, deeveedee said:

I have an HP 10th Gen Intel Laptop that I'm thinking about installing a BMC943602CS for working Wi-Fi in Tahoe without root patches.  Since I'd like to boot  macOS / Windows / Linux,  Is anyone currently using BMC943602CS for Wi-Fi and Bluetooth in Windows 11 and Linux and if so, does it work well?  Thanks.

 

No problem on Windows. You can download the latest BCMDHD driver (for Wi-Fi) from Windows Update. You will need the Bluetooth driver shipped in Apple's BootCamp package.

By default, the brcmfmac driver module is used on Linux. The Tx rate is also incorrect on Linux because that's the firmware issue.

There is also a proprietary driver provided by Broadcom available, but I have not yet tried that.

 

On 10/3/2025 at 7:04 AM, Stefanalmare said:

I'll do tonight and report.
Update: It works on latest sequoia. csr-active-config 00000000, SecureBootModel Default, and of course, no AMFI help.

Update 2: It works on latest Tahoe. Doesn't arrive to login with SecureBootModel Default, but is OK with csr-active-config 00000000. However if you need sound VoodooHDA or AppleAlc you need to lower csr-active-config. Also same {censored} with AppleVTD and network.

 

Yes, if you need AppleHDA on Tahoe, you need to set `csr-active-config` to `03080000`. BCMC works regardless of whether you disable SIP or not.

 

On 10/4/2025 at 9:49 AM, Anto65 said:

This is what I see at the end of the verbose

 

 Couldn't alloc class "AppleBCMWLANCompanion" 

 

Even though I get positive output with the command
kextstat | grep bcmc

  Reveal hidden contents

 

with the second :   sudo dmesg | grep bcmc ... nothing

 

The card in question is a BCM4350 , DW1820A , 0x14E4, 0x43A3 

 

  Reveal hidden contents

 

   

 

 

 

It should be among the compatible ones or am I doing something wrong ?

 

Tried both with DisableIoMapper / DisableIoMapperMapping on / off ...nothing

 

Please post the kernel log by running the following command:

sudo dmesg | grep bcmc

DisableIoMapper must be set to false. Setting it to true will disable AppleVTD.

You might want to check your config with @deeveedeewho was able to load the driver for BCM4350.

 

On 10/4/2025 at 11:50 AM, eSaF said:

The one thing I am apprehensive about is the possibility of AirDrop not working as reported hence the reason I was holding off.

 

Having Wi-Fi working on the others in the system and not Tahoe, twisted my arm to go this route.

 

In this case, get a real Mac so your ARM® will not get hurt. 🙃 IMHO, there is no perfect Hackintosh.

 

On 10/4/2025 at 1:51 PM, jlrycm said:

@Austere.J and/or anyone else that tested the kext in Tahoe: will the kext work in Tahoe with VT-D enabled in BIOS but patching the DMAR table to remove reserved regions and dropped the original DMAR table as explained in Dortania. Right now, that's the only way my i-225V ethernet card works in Tahoe. AppleIGC kext does not work in Tahoe with VT-D enabled in BIOS.

 

Did you try to use Apple's E1000 DriverKit driver? Does it work without patching the DMAR table?

 

[Austere.J]

On 10/5/2025 at 12:41 AM, cloudy said:

I have a question that may be related to this issue, or perhaps even off-topic. Can BCMC and Mykextinstaller live together? Because BCMC requires a clean installation, and Mykextinstaller requires KDK installation, they seem to be conflicting. Currently, I can use Wi-Fi, but not audio. What do you think?

 

In the manual, I said "You are strongly advised to make a clean installation and keep the System Integrity Protection (SIP) active before testing BCMC".

A clean installation is not required as long as you ensure that all kexts and frameworks related to the network stack are uncontaminated.

If you rely on AppleHDA.kext, you need to lower your `csr-active-config`. BCMC works regardless of whether SIP is enabled or not.

 

On 10/5/2025 at 11:51 AM, meg2014 said:

Success on Sequoia!  (I'll try Tahoe later).

 

i have a FullMac adapter (BCM43602) and  it works with this configuration.  Nice!

 

There were no real problems, just took my time to make sure my config was setup correctly, one reboot later, WIFI...

 

The only issue is that I have a 10G Ethernet interface and so the wireless interface will probably not get much use......but it's still nice to have.

 

And, I also have this drive encrypted and did the WiFi install after I encrypted it.   For FileVault, I do have to load apfs_aligned every time I boot, but that doesn't bother me and login is simple and smooth.  The encryption did not interfere at all with this WiFi config.

 

Thanks!

 

Thanks for reporting.

 

On 10/5/2025 at 12:11 PM, cloudy said:

@schrup21, After applying MyKextinstaller, my computer starts booting, then immediately reboots and freezes. I've tried several times, but the same thing happens. I can't even boot into Tahoe. As I said in the previous post, it seems that BCMC and MyKextinstaller cannot be applied together.

[edit]

I am on Tahoe 26.1

 

This is not related to BCMC. Your issue is probably because a wrong KDK was used when installing the kext to SLE.

You can verify this by disabling BCMC and then installing AppleHDA.kext via your kext installer.

 

On 10/5/2025 at 2:11 PM, BuXb said:

@Austere.J great project, congrats & respect!

 

Can you please share the steps how you managed to extract the Firmwares? I'd like to extract the FW from the original Apple BCM94360CS2 which I've been running 100% happily in my hackBook until Sequoia (VID: 14E4 | DID: 43A0 | SVID: 106B | SDID: 0117) and see if I can get it to work with your AppleBCMWLANCompanion kext.

 

The chip does not contain firmware. The driver downloads firmware to the chip. There is no firmware compatible with BCM4360 and the FullMAC driver.

 

On 10/5/2025 at 4:28 PM, KGP-iMacPro said:

The sweet bitter irony was that just the com.apple.iokit.IOSkywalkFamily manoeuvre for the OCLP-WIFI patch was the culprit for all related X550-AT2 problems.

 

Case closed. It's your config issue. You probably skipped the OCLP section in the manual.

 

On 10/6/2025 at 10:52 AM, Wayang-NT said:

BCM943602CS (0x14E4, 0x43A) still work  in macOS Tahoe 26.1 Beta 2 ... 

 

Good to know that.

 

On 10/6/2025 at 11:47 AM, eng_redaesm said:

My Card is BCM3602 Fenvi T919

Vendor 0x14E4 id 0x43BA

I Applied every step but didn’t work

 

Need more details. Configs, kernel logs, kext status, etc.

 

[Austere.J]

On 10/6/2025 at 1:31 PM, BuXb said:

@schrup21 @jlrycm understood re. Firmware, thanks for the infos! I guess each card requires its specific/ dedicated FW and it's not worth trying other cards' FW instead (not even knowing which one would be closest).

 

(a bit off-topic/ just out of curiosity: so I understand Linux does not provide a FW for the BCM94360CS2. I admit I never ran Linux after installing the BCM94360CS2, but I guess consequently it wouldn't work in Linux, either?)

 

BCM4360 should work on Linux and uses the `brcmsmac` driver.

 

On 10/7/2025 at 9:58 AM, Irish_Man said:

The issue I have is when I disable/uncheck DisableIOMapper I lose Ethernet connection. When I enable it, I have Ethernet but no WiFi.

I'm not sure that I can have both working at the same time. Is there a way?

 

If your Ethernet card is supported by Apple's DEXT driver, try to use that.

 

On 10/8/2025 at 1:53 AM, KGP-iMacPro said:

Ummm! AppleBCMWLANCompanion.kext started to behave extremely unstable on my system this morning. Several KPs within several minutes and after several reboots. Finally I had to disable the kext to reach again system stability. Attached some KP.logs...

 

I have taken a note on it.

 

On 10/8/2025 at 7:17 AM, Henties said:

I have applied this new method to get WiFi working successfully on 2 of my hacks, with both working like a dream.

 

The only issue I am having is sleep, manual sleep and also automatic timer controlled sleep.

 

Once the machines have entered sleep I lose all input functionality, mouse as well as wired keyboard, it appears to me that power to all

the configured USB ports is lost.

 

The hacks do not even enter sleep fully as the fans keep spinning. To regain input control over the hacks I have to hard reboot where after everything works flawlessly again until the next sleep cycle.

 

The problem manifests itself on the following systems:

 

1. Gigabyte GA-7490-Vision G (Bios F 21) with an Intel Core i9-10850K CPU

 

2. Gigabyte GA-Z790 D DDR4 (Bios F 11) with an Intel Core  i7-127000KF CPU

 

Would appreciate some advice to solve this problem.

 

Greetings Henties. 

 

This is a known issue.

 

On 10/8/2025 at 11:17 AM, ichelash said:

I got WI-FI working, but Ethernet is gone...not working. If i set disableiomapper to true in config..Wi-Fi disappear and Ethernet is working...if set to false..wifi working, Ethernet dead.

 

Setting DisableIOMapper to true is effectively disabling AppleVTD. If your Ethernet card is supported by Apple's DEXT driver, try to use that.

[Austere.J]

On 10/12/2025 at 4:30 AM, schrup21 said:

To all BCMC users: My update to Tahoe 26.1 Beta 2 has now stalled for the second time in the first phase (i.e., after it was loaded and prepared, after the reboot). Shortly after the installer started, there was no SSD activity (for several minutes).

 

The first time this happened, the update continued after a reboot. However, after that, my Wi-Fi card was somehow blocked (it only worked again after a full shutdown).

 

Today the same thing happened, but this time the reboot didn't help; Installer stalled again. So I disabled my Wi-Fi module in the BIOS, and the update completed. After completing the first phase, I re-enabled the Wi-Fi module, and the Wi-Fi worked after the update was complete.

 

It may have been just a coincidence and had nothing to do with BCMC at all—I didn't have Verbose enabled, so I'm not sure.

 

Still good to know that. Thanks for reporting this. I have not tried to load BCMC in Recovery, so it is possible that BCMC is not compatible with Recovery.

 

I will consider preventing BCMC from being loaded in Recovery. For now, please disable the kext (just like WhateverGreen) before you upgrade the OS.

 

On 10/12/2025 at 6:14 AM, jlrycm said:

@Austere.J how does having bcmc-srom-slide defined in Device Properties for a bcm43602CS card to specify the offset into SPROM area where the chip SROM is stored can prevent kernel panics?

 

This device property should have nothing to do with the kernel panic. If it is not specified, the default value (0) will be used instead.

 

On 10/13/2025 at 12:18 AM, KGP-iMacPro said:

@Austere.J, it seems there is another flaw, as soon as AppleBCMWLANCompanion.kext is enabled: unable to gather PCI device information in System Information! 

 

Please consider removing all SSDTs that add those unnecessary properties to the Wi-Fi device. BCMC renames the Wi-Fi device to ARPT automatically.

 

On 10/13/2025 at 10:01 AM, kaoskinkae said:

I have followed the guide perfectly and there is no support for the information even before the NVRAM 00000000 reset. The fenvi T919 card disappears in the peripheral if I add the corresponding ROM which I think is not mine and that is why it disappears. It is impossible to activate it.

 

BCM4360 (0x14E4, 0x43A0)

BCM94360CD

Fenvi T919

 

If you indeed have followed the guide perfectly, you would realize that your chip is not in the table of supported devices in the first step, "Check Your Wi-Fi Chip", in the manual.

 

On 10/15/2025 at 5:07 AM, KGP-iMacPro said:

 

@jlrycm, thanks for this hint. Adding device property bcmc-srom-slide indeed makes BCMC much more stable on my system, although @Austere.J mentions that the latter device property is not mandatory for BCM943602CDP and is set by default to 0x00 anyway. So far no further KP in daily use, however immediate KP on sleep persists.  

 

I honestly don't think the random kernel panics you mentioned earlier has anything to do with this device property.

 

On 10/15/2025 at 11:44 AM, schrup21 said:

@jlrycm @KGP-iMacPro I set all - didn't like the "Failed to find the device property" errors in dmesg 😅

 

Good. Now I am considering removing those errors (which are actually warnings) in the next version.

 

On 10/16/2025 at 7:26 AM, Mac Hosehead said:

It is saying in the report that it is supported so can't be wrong, right?

 

System Information says AirDrop is supported because the driver announces that AirDrop is supported, which is not identical to" the device supports it".

 

 

[Anto65]

@Austere

 

https://www.insanelymac.com/forum/topic/361710-broadcom-fullmac-wi-fi-support-on-macos-sonoma-sequoia-and-tahoe-without-root-patches/page/9/#findComment-2842381

 

[Austere.J]

On 10/16/2025 at 7:45 AM, Mac Hosehead said:

Maybe the mistake in the report should be reported as a bug with Apple.

 

This is not a bug.

 

On 10/16/2025 at 10:38 AM, KGP-iMacPro said:

 

I agree.. the lack of sleep/wake functionality and the missing AWDL functionality are the strongest drawbacks of BCMC for now beside other smaller flaws. However, it still  regains WIFI under Tahoe. What I don't understand however at all is the absence of @Austere.J in this thread (since exactly two weeks), which in my opinion is the strongest drawback at all. One feels abandoned with an implementation that is at most beta. Thread and project remain without guidance.   

 

Wow...

 

I think there may be a misunderstanding. I'm not obligated to be available and provide support whenever needed.

 

On 10/16/2025 at 9:05 PM, eSaF said:

Can you please tell me how to correct my Properties entry so that the correct Code is displayed or post your config.plist after removing your personal data and post it here.

 

Because the manual (https://github.com/0xFireWolf/AppleBCMWLANCompanion/blob/main/Documentation/DeviceProperties.md#bcmc-enable-auto-country) says the data type of `bcmc-enable-auto-country` is Data, and you are using String.

 

On 10/17/2025 at 12:42 AM, Anto65 said:

This

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

 

The error regarding to SROM Control is expected on BCM4350, and that's why you need to specify the slide of 64 in the device properties.

Please upload the full kernel log as a text file instead of posting a screenshot. I need to see the log related to downloading firmware.

 

On 10/17/2025 at 7:45 AM, 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

 

Good. I need logs and panic reports to solve problems instead of seeing complaints without any details.

[Austere.J]

On 10/17/2025 at 10:47 PM, schrup21 said:

 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

 

Yes, this is why I provide the device property that allows you to set the country code manually. Different countries might have different regulations. For example, 5 GHz with 80 MHz is available only in certain countries.

Typically, the Wi-Fi chip scans nearby access points and uses their announced country codes to determine its own country code. 

1 hour ago, jlrycm said:

Hello Everyone! Below is the feedback and technical explanation about the sleep/wake issues provided by @Austere.J in GitHub 

 

Thanks for your interest in this project and for joining the beta testing.

The kernel panic (that happens when you put your computer to sleep) has nothing to do with the device properties, and I knew there would be a kernel panic before I even tried it while writing the Known Issues section.

I haven't yet looked into the power management routines, because I usually prioritize getting all necessary functionality working before tackling sleep/wake issues.

To give you a bit of technical detail, the Wi-Fi driver relies on another driver AppleOLYHALMac.kext, which requires a couple of ACPI methods to manipulate the GPIO signals. Instead of asking you all to add another SSDT with all the required dummy ACPI methods implemented, I decided to zero out some initialization routines in AppleOLYHALMac, and as a result, left some objects uninitialized (null pointers). When you put your computer to sleep, the Wi-Fi driver invokes the interface exposed by AppleOLYHALMac to change some power settings (because there is real platform device called AMFM on a real Mac). However, since the objects are null, a page fault would occur, as indicated by the kernel panic report uploaded by @andreszerocross (by the way, thanks for uploading the report -- this is exactly what I need for solving a problem).

I understand that you all want sleep/wake to work properly, but there is a lot of work that needs to be done behind the scenes. Yes, I can easily patch the OLY driver to avoid the page fault. However, the Wi-Fi chip will probably be powered off while your computer is sleeping, so when your computer wakes up, the driver needs to power it back on and download the firmware to the chip again. I need to analyze and understand the control flow and make sure that each step is compatible with legacy Wi-Fi chips, which requires significant reverse engineering effort and takes time. As such, I would appreciate your patience as I work through this.

 

 

 

Good. I don't have to copy and paste it myself. Thanks.

[jlrycm]

 

1 hour ago, Austere.J said:

Did you try to use Apple's E1000 DriverKit driver? Does it work without patching the DMAR table

@Austere.J will try without patching DMAR.

Edited October 25, 2025 by jlrycm

[cfmwan]

 

2 hours ago, jlrycm said:

 

@Austere.J will try without patching DMAR.

My ROG STRIX Z690-E GAMING Wi-Fi must be loaded with AppleIntelI210Ethernet when VT-D is turned on. In addition, Intel X520-DA1 cannot use IntelLucy driver when VT-D is turned on. It can only load the SonnetEthernet-10GE driver, but this driver cannot show the interface speed.If the above two network cards turn off VT-D, AppleIGC and IntelLucy can be used.In addition, I found a very interesting thing. When two wired network cards cannot be used, the speed displayed by BCM43602 is 450MB instead of 24MB.Its display speed has been changing all the time.

Edited October 25, 2025 by cfmwan

[schrup21]

@eSaF could you cross-check the country code behaviour e.g in Ventura? As I mentioned earlier, I used to use a DELL DW1830 which only worked with country code US - I guess that a country code can be hardcoded on some devices 

 

@Austere.J thank you for answering all the questions!

 

In my case, BCMC is working nearly perfect - except of the known restrictions of course.

So far, Wi-Fi has only stopped working after booting up a few times.

I haven't experienced any Panics so far (except when I hadn't disabled sleep/hibernation yet and my computer went into sleep)—I would consider that perfectly normal, since BCMC is in beta.

[deeveedee]

@Austere.J Thank you for your patience with our questions and for your detailed responses.  Clearly, you're the right person for the job.  Outstanding work.

[schrup21]

@eSaF I'm using my BCM943602CS in Sequoia with OCLP Modern Wi-Fi and in Tahoe with BCMC. There shouldn't be any restrictions in Sequoia? I certainly don't see any on mine (sorry, I don't mean to annoy you, of course).

[kgp]

@eSaF, what @schrup21 is telling you is, that you can use your BCM943602CS under Sequoia with OCLP and under Tahoe with BCMC 😉

[jlrycm]

1 hour ago, eSaF said:

On the contrary my friend I didn't or don't feel any annoyance by your query.

I made a fresh Tahoe installation on a test drive so I will once again test the BCMC method with the Apple Card.

 

One of the most irksome annoyance is the wrong Country Code being displayed by the Card.

I am not sure but I have read somewhere it can impact connection performance overall if the Code is wrong.

 

Are you saying you have no problem with Apple Services in Sequoia with this WIFI fix?

I will again test this as I found 'Hand off to iPhone Camera' did not work wirelessly in both Sequoia and Sonoma.

@eSaF have you tried some of the proposed solutions in the link below?

https://apple.stackexchange.com/questions/9768/change-mac-os-x-wireless-card-country-code

 

[schrup21]

4 hours ago, eSaF said:

Consequently the same WIFI limitations affecting Tahoe also affects Sequoia and Sonoma

if you set Min / Max Kernel in your KEXT config, you can use Modern WiFi in Sonoma / Sequoia and BCMC in Tahoe. BCM943602 is just as good as Fenvi, including full support of Continuity.

I‘m multi booting Mojave, Big Sur, Ventura, Sequoia and Tahoe with the same EFI - except the VTD Intel LAN issue in Tahoe, everything works fine 

 

like tis:

 

Edited October 26, 2025 by schrup21

[kgp]

@eSaF, the idea is to enable the OCLP patches in your config.plist but with the adequate min/max kernel restrictions enabled. I am using such configuration also on my multi-boot system. Also you have to set the adequate min/max kernel restrictions for the BCMC kext. By this, either the one or the other setting is used when using Tahoe or Sequoia or whatever. One just needs one EFI-Folder for all macOS versions. As an example you could also download my EFI from the bootloader section, although @schrup21 details all necessary steps explicitly above.
 

Update:

BTW.. I would set max kernel for AmfiPass.kext to 25.99.99 as it works pretty well with BCMC and you need it for the OCLP-mod AppleHDA patch under Tahoe!!!

Edited October 26, 2025 by KGP-iMacPro