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

[arsradu]

Hey guys,

 

First of all, a big thank you for this project. In a world without OCLP, this has come really handy.

 

Now, since this is still in testing phase, I take the opportunity to share my experience so far using this kext.

 

1. Initially I thought that there might be a drop in performance compared to using OCLP's root patches. My recent tests with Sequoia disproved this theory and looks like the performance is quite the same. However, I moved my desk, and my computer to a new room, since I'm renovating, and looks like there might be some reception issues over there. So not a kext issue, but a placement issue.
2. I did encounter some issues though, and I've recently learned at least some of them might be already known. Which is reassuring.
   One of the issues is the inability to finish the installation of incremental updates.
   Also, not sure why that is, but when my PC first reboots in order to start the upgrade, instead of automatically selecting the MacOS Installer in the boot picker, it selects some "EFI" that I have no idea where it comes from, since it doesn't usually show up.
   So, I manually have to select MacOS Installer, in order to start the installation.
   Problem is, that installation never finishes. Computer reboots and we're back at the same place, this time without the "EFI" option in the boot picker, but still with the same MacOS Installer. Selecting it again will just start the same process all over again.
   If you let it do its thing, after selecting MacOS Installer and doing its thing for a while, it reboots again, and it selects the main OS, as if the installation completed successfully and it needs to boot back into the OS to complete installation. All this time, the MacOS Installer option is still available in the boot picker. And if you do let it boot back into the OS, or if you select it manually, you'll notice the update hasn't actually been applied.
   
   So this was kind of my main issue. Disabling the kext looks like solves both the selection issue, and the installation issue.
3. When connection drops (let's say you unplug the cable on your router, or you lose power on your router and connection drops), the whole PC freezes. Not sure this is a driver issue or an OS issue...haven't tested this thoroughly, but if it is a driver issue, I hope this feedback helps to fix it.
4. Also, I haven't tested this part thoroughly yet, but I think you also get a KP after sleep. This also occurs with older kexts such as RealtekCardReader kext, with more recent versions of MacOS, so I'm guessing whatever's causing that, might also cause this. As far as I've seen, this is also a known issue, but not a priority right now. In my case, I just disabled sleep as a workaround. But it would be nice if we could find a fix for it, maybe after more important issues are getting sorted out.

 

This is my feedback so far, regarding this kext.

 

Once again, thank you so much for the initiative. To be honest, I thought we were stuck with Ethernet until OCLP finds its way to the public. So this is highly appreciated!

Edited November 1, 2025 by arsradu

[kgp]

3 hours ago, arsradu said:

Hey guys,

 

First of all, a big thank you for this project. In a world without OCLP, this has come really handy.

 

Now, since this is still in testing phase, I take the opportunity to share my experience so far using this kext.

 

1. Initially I thought that there might be a drop in performance compared to using OCLP's root patches. My recent tests with Sequoia disproved this theory and looks like the performance is quite the same. However, I moved my desk, and my computer to a new room, since I'm renovating, and looks like there might be some reception issues over there. So not a kext issue, but a placement issue.
2. I did encounter some issues though, and I've recently learned at least some of them might be already known. Which is reassuring.
   One of the issues is the inability to finish the installation of incremental updates.
   Also, not sure why that is, but when my PC first reboots in order to start the upgrade, instead of automatically selecting the MacOS Installer in the boot picker, it selects some "EFI" that I have no idea where it comes from, since it doesn't usually show up.
   So, I manually have to select MacOS Installer, in order to start the installation.
   Problem is, that installation never finishes. Computer reboots and we're back at the same place, this time without the "EFI" option in the boot picker, but still with the same MacOS Installer. Selecting it again will just start the same process all over again.
   If you let it do its thing, after selecting MacOS Installer and doing its thing for a while, it reboots again, and it selects the main OS, as if the installation completed successfully and it needs to boot back into the OS to complete installation. All this time, the MacOS Installer option is still available in the boot picker. And if you do let it boot back into the OS, or if you select it manually, you'll notice the update hasn't actually been applied.
   
   So this was kind of my main issue. Disabling the kext looks like solves both the selection issue, and the installation issue.
3. When connection drops (let's say you unplug the cable on your router, or you lose power on your router and connection drops), the whole PC freezes. Not sure this is a driver issue or an OS issue...haven't tested this thoroughly, but if it is a driver issue, I hope this feedback helps to fix it.
4. Also, I haven't tested this part thoroughly yet, but I think you also get a KP after sleep. This also occurs with older kexts such as RealtekCardReader kext, with more recent versions of MacOS, so I'm guessing whatever's causing that, might also cause this. As far as I've seen, this is also a known issue, but not a priority right now. In my case, I just disabled sleep as a workaround. But it would be nice if we could find a fix for it, maybe after more important issues are getting sorted out.

 

This is my feedback so far, regarding this kext.

 

Once again, thank you so much for the initiative. To be honest, I thought we were stuck with Ethernet until OCLP finds its way to the public. So this is highly appreciated!

 

@arsradu, concerning 2.) it rings a bell. Last time I did a clean install of Tahoe 26.0 on a USB test drive, I faced similar issues even with AppleBCMWLANCompanion.kext disabled. After reboot, I had to manually select the MacOS Installer several times and subsequently also my Tahoe disk several times to finish the installation. I thought, it might be due to the external USB drive, but what you are telling here sounds very similar to me anyway. There have been also a lot of errors during the verbose boot of the individual installation steps.  I have a queasy feeling with respect to the upcoming OTA update to 26.1 by beginning of next week. 4.) is very well known to all of us. With respect to 1.) and 3.), I never faced such issue.

 

One more thing that might be interesting for all of us: What about your ethernet connection with AppleVTD enabled under Tahoe? In my case, ethernet under Tahoe with AppleVTD enabled works with Apple's native DEXT Driver, however there are issues with IntelLucy.kext. Which NICs and driver are you employing and what is your general solution for ethernet under Tahoe so far?

 

Cheers,

 

KGP 👍

  

 

  

Edited November 1, 2025 by KGP-iMacPro

[jlrycm]

21 minutes ago, eSaF said:

Bro I too can voice about that issue, the clean installation was flawless with the AppleBCMWLANCompanion.kext disabled but the OTA update was problematic with continued reboots to the previous installation volume.

The way I got past that stage after suffering about 4 reboots that resulted into nothing, I used a previous Tahoe Installation USB Drive that contained no BCMC files and the update was completed.

 

So what you and @arsradu are saying is even though the constant reboots looks like nothing is happening, eventually the installation goes on to completion??!!

If that is the case then there was no need to swop out the installation USB Drive.

 

In my case, the bcmc kext will not allow OTA or full installation to finish unless I disable it. I tried multiple times and it was always getting stuck after the second stage.

[kgp]

17 minutes ago, eSaF said:

Bro I too can voice about that issue, the clean installation was flawless with the AppleBCMWLANCompanion.kext disabled but the OTA update was problematic with continued reboots to the previous installation volume.

The way I got past that stage after suffering about 4 reboots that resulted into nothing, I used a previous Tahoe Installation USB Drive that contained no BCMC files and the update was completed.

 

So what you and @arsradu are saying is even though the constant reboots looks like nothing is happening, eventually the installation goes on to completion??!!

If that is the case then there was no need to swop out the installation USB Drive.

 

 

Exactly, Bro! For my clean install,  I had to manually select the MacOS Installer and Tahoe disk after each reboot, as the OC Boot Picker always pointed to some EFI. When booting in verbose mode I witnessed a lot of errors during installation. Such errors have been also revealed when booting the finished clean install of Tahoe. I guess for the upcoming OTA Update next week, I will use a backup EFI without any traces of BCMC on it, which I have in the EFI partition on another disk of my system. I'm even thinking on physically removing the BCM943602CDP from my system for the update, as there will be OTA updates for Tahoe and Sequoia.    

2 minutes ago, jlrycm said:

In my case, the bcmc kext will not allow OTA or full installation to finish unless I disable it. I tried multiple times and it was always getting stuck after the second stage.

 

The problems I am reporting above occurred with the BCMC kext disabled!

[arsradu]

If I’m not mistaken, the issue with the installation not being able to finish (tried 3 times in a row, I think that’s enough to get a feeling whether or not it’s ever going to finish), doesn’t occur when you’re using the full installer. With the full installer, yes, you get a couple of reboots but it finishes after that. With incremental, as far as I could see, it never does. So this only occurs with incremental (I think they call them “delta”) updates.
 

Also, when disabling BCMC (including the device properties changes), it only went through that step once. So clearly something was wrong before. 
Maybe disabling the kext is not enough to ensure a smooth installation from start to finish…? I don’t know. In my opinion, it shouldn’t happen in the first place. :))

For Ethernet, I’m using a Realtek 8111 chip (Mieze’s driver) and it always worked flawlessly for me (including with Tahoe). Can’t use Ethernet right now since I’m pretty far away from my router and don’t have a long enough cable. This is just a temporary setup while I’m renovating. So for now, I’m either using this kext for WiFi or an Android device with USB tethering enabled. 
 

 

[kgp]

10 hours ago, arsradu said:

If I’m not mistaken, the issue with the installation not being able to finish (tried 3 times in a row, I think that’s enough to get a feeling whether or not it’s ever going to finish), doesn’t occur when you’re using the full installer. With the full installer, yes, you get a couple of reboots but it finishes after that. With incremental, as far as I could see, it never does. So this only occurs with incremental (I think they call them “delta”) updates.
 

Also, when disabling BCMC (including the device properties changes), it only went through that step once. So clearly something was wrong before. 
Maybe disabling the kext is not enough to ensure a smooth installation from start to finish…? I don’t know. In my opinion, it shouldn’t happen in the first place. :))

For Ethernet, I’m using a Realtek 8111 chip (Mieze’s driver) and it always worked flawlessly for me (including with Tahoe). Can’t use Ethernet right now since I’m pretty far away from my router and don’t have a long enough cable. This is just a temporary setup while I’m renovating. So for now, I’m either using this kext for WiFi or an Android device with USB tethering enabled. 
 

 

 

What I’m still curious about is whether @Mieze’s RealtekRTL8111.kext works under macOS Tahoe with AppleVTD enabled (DisableIOMapper = False). If it doesn’t, I’d like to know whether there’s a native macOS driver that could take over when RealtekRTL8111.kext is disabled in the config.plist. Up to my knowledge there does not exist any..😉

Edited November 2, 2025 by KGP-iMacPro

[arsradu]

45 minutes ago, KGP-iMacPro said:

 

What I’m still curious about is whether @Mieze’s RealtekRTL8111.kext works under macOS Tahoe with AppleVTD enabled (DisableIOMapper = False). If it doesn’t, I’d like to know whether there’s a native macOS driver that could take over when RealtekRTL8111.kext is disabled in the config.plist. 😉

Hmmm.... I mean, I haven't tested that in particular. And I can't test it right now since I don't have a way to connect to my router via Ethernet. I didn't know there were issues with that. Previously it was set to Enabled. I don't think I ever tried it with it disabled. Now it's set to disabled because BCMC needs it (if I got it right). But now I can't test Ethernet anymore. :)) So...the answer is a definite maybe. Will try it whenever I get a chance. But so far, "I can neither confirm nor deny" it working. :)) 

[kgp]

Ethernet AppleVTD Incompatibility under macOS 26 (Tahoe)

 

All network drivers — including IntelLucy.kext, LucyRTL8125Ethernet.kext, and RTL8111Ethernet.kext — work correctly under Sequoia and Sonoma with AppleVTD enabled. However, under macOS 26 (Tahoe), all Lucy-based drivers currently fail when AppleVTD is active. 

 

Quote

"The NIC needs to access two areas in RAM: descriptor rings (still mapped correctly) and packet buffers (no longer mapped by the kernel under Tahoe). As a result, the NIC can’t access packet buffers anymore, which leads to empty RX/TX operations although descriptors are processed correctly." — Mieze, October 2025.

 

| Kext                     | Vendor                | Native macOS Alternative  | Notes AppleVTD (Tahoe) |
|---------------------------|--------------------  |---------------------------|-------|
| IntelMausiEthernet.kext   | Intel I21x/I219      | —                         | Fails |
| RealtekRTL8111.kext       | Realtek 8111         | —                         | Fails |
| LucyRTL8125Ethernet.kext  | Realtek 8125         | AppleEthernetRL.kext      | Fails; native Skywalk driver fails with onbard NICs (KP); |
| IntelLucy.kext            | Intel X520/X540/X550 | AppleEthernetIXGBE.dext   | Fails; native DEXT works |

 

A fix by the author is on it's way and will be provided soon 👍

Edited November 12, 2025 by KGP-iMacPro

[dracon]

On 9/21/2025 at 1:36 PM, Austere.J said:

That really depends on the type of chip. If it's a FullMAC chip, then theoretically, it can be supported.

I am interested in exploring other FullMAC chips, including those with 802.11ax support, so we don't have to stick with these old 802.11ac cards.

 

On the 802.11ax topic, I did a little digging to see to try and find a compatible chipset/adapter that could be used and found the BCM43752 chipset which appears to be a FullMAC chipset (uses the brcmfmac driver). Couldn't find many cards that actually used that chipset as most were custom design, but came across a couple standard M2 and Mini PCI-E cards from SparkLAN. Would any of these possibly work?

 

https://wikidevi.wi-cat.ru/SparkLAN

WNFB-265AXI(BT) • WiFi 6 + BT 5.0 Combo, 802.11ax M.2 2230 (E Key), 2T2R
WPEB-265AXI(BT) [B33]/[R33] • WiFi 6 + BT 5.0, 802.11ax Half Size Mini PCIe, 2T2R

 

If so, willing to accept a donation to the project? 😃 I wouldn't mind getting a card or two for you to test with. I think while getting these older 802.11ac cards working would be nice. I think being able to support a more modern chipset (802.11ax and BT 5.x) would be an ever better end goal since Tahoe is likely the last macOS version we'll ever be able to use. 

[BALDY_MAN]

12 minutes ago, dracon said:

 

On the 802.11ax topic, I did a little digging to see to try and find a compatible chipset/adapter that could be used and found the BCM43752 chipset which appears to be a FullMAC chipset (uses the brcmfmac driver). Couldn't find many cards that actually used that chipset as most were custom design, but came across a couple standard M2 and Mini PCI-E cards from SparkLAN. Would any of these possibly work?

 

https://wikidevi.wi-cat.ru/SparkLAN

WNFB-265AXI(BT) • WiFi 6 + BT 5.0 Combo, 802.11ax M.2 2230 (E Key), 2T2R
WPEB-265AXI(BT) [B33]/[R33] • WiFi 6 + BT 5.0, 802.11ax Half Size Mini PCIe, 2T2R

 

If so, willing to accept a donation to the project? 😃 I wouldn't mind getting a card or two for you to test with. I think while getting these older 802.11ac cards working would be nice. I think being able to support a more modern chipset (802.11ax and BT 5.x) would be an ever better end goal since Tahoe is likely the last macOS version we'll ever be able to use. 

 

There you go

https://www.bcdatlantik.shop/products/sparklan-wnfb-265axibt-industrial-grade-m-2-module/28944000007947070?srsltid=AfmBOore_pBJru6PB5m3rXzpHW3axL5peptCRmEfT2W2QIQdGGazbVSm

[dracon]

3 minutes ago, BALDY_MAN said:

There you go

https://www.bcdatlantik.shop/products/sparklan-wnfb-265axibt-industrial-grade-m-2-module/28944000007947070?srsltid=AfmBOore_pBJru6PB5m3rXzpHW3axL5peptCRmEfT2W2QIQdGGazbVSm

 

I found the SparkLAN adapters to purchase easily. What I meant was when I initially was trying to find adapters using the BCM43752 chipset, most of them were implementations of the chipset on custom boards/connectors.

[sanigo]

With the companion kext enabled, the 26.1 update could be installed, the install progress will always crash. And can not boot into recovery mode.

I have disable the kext to install 26.1. And then enable it again after the installation.

[schrup21]

4 hours ago, sanigo said:

I have disable the kext to install 26.1. And then enable it again after the installation.

this is a already known issue - another workaround would be to turn off WiFi (if you have such a toggle e.g in BIOS)

[sanigo]

6 hours ago, schrup21 said:

this is a already known issue - another workaround would be to turn off WiFi (if you have such a toggle e.g in BIOS)

Sure. So I would like to live with this currently. Thanks.

[Jessy Lou]

I'je just bought the BCM943602CS as I read this card is supported, to replace my TP-Link Archer T9E based on a BCM4360 (with USB dongle to get BT 4 with BCM20702).
The issue I have: Hackintool in its latest version running on Sequoia is providing me with the following values:

Vendor ID: 0x14EA
Device ID: 0x430

My Sequoia config.plist is using these kext:
Lilu.kext
VirtualSMC.kext
WhateverGreen.kext
AppleALC.kext
USBPort.kext
SMCProcessor.kext
IntelMausi.kext
RestrictEvents.kext
IOSkywalkFamily.kext
IO80211FamilyLegacy.kext and IO80211FamilyLegacy.kext/Contents/PlugIns/AirPortBrcmNIC.kext
AMFIPass.kext

AirportBrcmFixup.kext
AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcmNIC_Injector.kext
BrcmFirmwareData.kext
BrcmPatchRAM3.kext
BlueToolFixup.kext

I don't have that much knowledge as you guys, therefore I would appreciate any help and advices.

I have to tell that everything is working like a charm under Sequoia based on that configuration. Before going to work with what is necessary to get WiFi on Tahoe, I wanted to be sure about the real device I have installed.

[kgp]

3 hours ago, Jessy Lou said:

I'je just bought the BCM943602CS as I read this card is supported, to replace my TP-Link Archer T9E based on a BCM4360 (with USB dongle to get BT 4 with BCM20702).
The issue I have: Hackintool in its latest version running on Sequoia is providing me with the following values:

Vendor ID: 0x14EA
Device ID: 0x430

My Sequoia config.plist is using these kext:
Lilu.kext
VirtualSMC.kext
WhateverGreen.kext
AppleALC.kext
USBPort.kext
SMCProcessor.kext
IntelMausi.kext
RestrictEvents.kext
IOSkywalkFamily.kext
IO80211FamilyLegacy.kext and IO80211FamilyLegacy.kext/Contents/PlugIns/AirPortBrcmNIC.kext
AMFIPass.kext

AirportBrcmFixup.kext
AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcmNIC_Injector.kext
BrcmFirmwareData.kext
BrcmPatchRAM3.kext
BlueToolFixup.kext

I don't have that much knowledge as you guys, therefore I would appreciate any help and advices.

I have to tell that everything is working like a charm under Sequoia based on that configuration. Before going to work with what is necessary to get WiFi on Tahoe, I wanted to be sure about the real device I have installed.

 

I would suggest to remove:  AirportBrcmFixup.kext, AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcmNIC_Injector.kext, BrcmFirmwareData.kext, BrcmPatchRAM3.kext and  BlueToolFixup.kext from your config.plist and EFI-Folder. None if these kexts is required by BCM943602CS! 

 

Subsequently, you can post a screenshot of Hackintool's PCIe Section that is related with BCM943602CS. BTW.. do you use any additional device properties or SSDT for Bluetooth/WIFI? In case you would need further help, please upload your EFI or config.plist. 

 

To start with, you could also have a look to my EFI-Folder as baseline:

 

 

Edited November 11, 2025 by KGP-iMacPro

[kgp]

28 minutes ago, eSaF said:

Hi, this -https://github.com/0xFireWolf/AppleBCMWLANCompanion/blob/main/Documentation/GettingStarted.md- is obviously the best place to start.

Read carefully then if you're stuck or have a query, you'll hopefully be guided by other members.

 

Actually for a simple to understand process, @KGP-iMacPro outside of @Austere.J is the member that will have all the answers at hand for you.

Apart from being quite clued up of what the process entails, he is very willing to walk you through the whole process.

 

Good luck.

Cheers.

 

Thanks for the flowers, Bro!  but indeed I am willing to help, as long the support is not provided directly by the author..  

[kgp]

2 hours ago, eSaF said:

No worries Bro, I am more than happy to give credit when it is due all based on the help I received. 

As a matter of fact, on reflection, I wondered if I did the right thing by the nomination with the possibility of increasing your work load.

 

I am happy that you took it in the spirit it is intended instead of a burden.

Thank you.

 

Bro, no worries at all! I rather feel honoured by your nomination and I am very willing to help others, whenever I am at home and have time.. That's what Hackintosh is all about, isn't it? 😉

 

All the best  and a great day to you,

 

KGP 👍💫

Edited November 11, 2025 by KGP-iMacPro

[Jessy Lou]

Thank you very much for your quick advices KGP-iMacPro and eSaF.
I'm going to dive deeper by tomorrow and let you know the outcome.

 

[Jessy Lou]

@eSaF: I started reading a couple of times the documentation provided by the author. I got stuck, therefore the doubt about the device came up. This is why I want to ensure the card I ordered is really the right one, despite I'm very happy about the benefits compared to the TP-Link on Sequoia.

@KGP-iMacPro: it's now done! I removed all the unnecessary kext from the config.plist.
I also had a look at your universal EFI.

As requested here is the screen shot from Hackintool on which I still see the same Device ID:

 

I didn't reset NVRAM, maybe I should have done it.

I'm also attaching my config.plist so that you can see (if I'm not mistaken, that I have no device properties or SSDT for Bluetooth/WIFI.

config-JessyLou.plist

Since I switched from Clover to OpenCore years ago I've learned a lot, but I still miss too many things. Your help is therefore very appreciated.

 

[Jessy Lou]

Just did twice NVRAM reset (just in case): same outcome with Hackintool.

[kgp]

2 hours ago, Jessy Lou said:

@eSaF: I started reading a couple of times the documentation provided by the author. I got stuck, therefore the doubt about the device came up. This is why I want to ensure the card I ordered is really the right one, despite I'm very happy about the benefits compared to the TP-Link on Sequoia.

@KGP-iMacPro: it's now done! I removed all the unnecessary kext from the config.plist.
I also had a look at your universal EFI.

As requested here is the screen shot from Hackintool on which I still see the same Device ID:

 

I didn't reset NVRAM, maybe I should have done it.

I'm also attaching my config.plist so that you can see (if I'm not mistaken, that I have no device properties or SSDT for Bluetooth/WIFI.

config-JessyLou.plist

Since I switched from Clover to OpenCore years ago I've learned a lot, but I still miss too many things. Your help is therefore very appreciated.

 

Your device ID seems 0x43A0 instead of 0x43BA. Check if your card is really a BCM943602CS. As soon I am at home, I will revise your config.plist. Give me 2 hours from now. Talk to you soon. 

Edited November 11, 2025 by KGP-iMacPro

[kgp]

@Jessy Lou, you did not prepare anything BCMC related in your config.plist! 🧐 To go ahead,  at least I need to know your country and the device path from Hackintool (not visible in your screenshot)! BTW.. Hackintool says BCM4360!!!!!! Please check and verify if you did not buy a BCM4360CS instead of a BCM43602CS!!!

 

Update: 

 

Well.. attached the modified config.plist, which is now universal for all recent macOS version including Sonoma, Sequoia and Tahoe.

 

Remaining discrepancies:  Your USBMap.kext has MinKernel 24.0.0. Thus it would just work with Sequoia and Tahoe. No idea what this MinKernel is for, I would remove it! No idea also what is USBPorts4iMac202.kext, which is also enabled!

 

What you have to do, once you really have a BCM43602CS or even better BCM43602CDP, which could fit into your adapter:

 

1.) Copy (sudo cp with root permission) brcmfmac43602-pcie_7.35.177.61.bin to /usr/local/share/firmware/wifi/

2.) Under Device Properties change PciRoot(0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x0) to your Device Path provided by Hackintool for your BCM43602CS (copy and paste) and change bcmc-default-country-code from DE to your country code.

3.) Download and copy AppleBCMWLANCompanion.kext to /EFI/OC/Kexts/ and enable AppleBCMWLANCompanion.kext in your config.plist under Kernel/Add. 

 

Everything else has been already implemented by myself such, that you should have OCLP working under Sonoma/Sequoia and BCMC under Tahoe, by using the same EFI-Folder.

 

Good luck,

 

KGP  👍 

 

P.S: Also check reason for:

a.) Lilu.kext MinKernel 10.0.0

b.) VirtualSMC.kext MinKernel 10.0.0

c.) WhateverGreen.kext MinKernel 12.0.0

d.) AppleALC.kext MinKernel 12.0.0

e.) IntelMausi.kext MinKernel 13.0.0

I would remove all these minKernel settings. 

  

Finally you could also do me a favour: Can you check and confirm that IntelMausi.kext really works under Tahoe with DisableIOMapper= false, i.e. AppleVTD enabled? 😉   

  

config-JessyLou-modified-KGP.plist

Edited November 12, 2025 by KGP-iMacPro

[BALDY_MAN]

 Jessy Lou. as a  vender id 0x14e4. Device id 0x43a0 = BMC4360. Which IS NOT SUPPORTED. 

Should be.          vender id 0X14e4 Device id 0x43ba =BMC43602

[Mac Hosehead]

1 hour ago, KGP-iMacPro said:

What you have to do, once you really have a BCM43602CS or even better BCM43602CDP, which could fit into your adapter

Actually, the BCM43602CDP has different size antenna connections so it will not work in the same card adapter.

 

Some things about the photo: If the shield really says BCM43602CS then a different card has been put in the adapter. I assume it can be swapped with the right card. Another thing is that the photo shows no wires hooked up to the antenna connections on the card. I don't know how that is supposed to work. Kinda screwy all around.