Jump to content
388 posts in this topic

Recommended Posts

1 hour ago, Mac Hosehead said:

This doesn't appear to be a Beta issue and for me it's looking like the BCM kext will have to be disable/enabled for any installs or updates. At least in Tahoe, anyway. I think it needs internet access while making the installer.

Yeah, sounds familiar-like every time I had to disable Bluetoolfixup to get the OTA updates.

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

 

image.thumb.png.a8237626b2afffe6c3dade1fc798df2d.png

 

        Device (EGP3)
        {
            Name (_ADR, 0x00080000)  // _ADR: Address
            Device (ARPT)
            {
                Name (_ADR, Zero)  // _ADR: Address
                Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
                {
                    Local0 = Package (0x0A)
                        {
                            "built-in", 
                            Buffer (One)
                            {
                                 0x00                                             // .
                            }, 

                            "AAPL,slot-name", 
                            Buffer (0x07)
                            {
                                "Slot-3"
                            }, 

                            "device_type", 
                            Buffer (0x13)
                            {
                                "AirPort Controller"
                            }, 

                            "model", 
                            Buffer (0x43)
                            {
                                "Broadcom BCM943602CDP 802.11 a/b/g/n/ac + Bluetooth 4.1 Controller"
                            }, 

                            "name", 
                            Buffer (0x10)
                            {
                                "AirPort Extreme"
                            }
                        }
                    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                    Return (Local0)
                }
            }
        }

 

With AppleBCMWLANCompanion.kext disabled:

 

image.thumb.png.483851541d107f595acf0fa0d42c515c.png

 

With AppleBCMWLANCompanion.kext enabled:

 

image.thumb.png.5146f012925cde2a3dbfefa909fe332c.png

 

 

SSDT-X299-Slot1-Slot3-PC02-BR2A-SL05-RadeonVII-HDAU-ARPT.aml

 

Although you might be very busy with other things right now, It would be great to have your input in this thread again - your previous contributions have really set the standard for everyone working on this project. In my opinion, this thread would strongly benefit from a bit more of your guidance and support.  👍

Edited by KGP-iMacPro
  • Like 1

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

29 minutes ago, kaoskinkae said:

BCM4360 (0x14E4, 0x43A0)

BCM94360CD

Fenvi T919

BCM4360 is not possible, you would need a BCM43602 (0x14E4, 0x43BA)

These two are different, the fmac firmware for BCM43602 is not compatible with a BCM4370 chip.

 

I guess you can replace the BCM94360CD on the fenvi with a BCM943602CDP 

 

there are Fenvi like adapters for BCM943602CS too, like this one:

image.thumb.png.37ff64aabb1eb14c4b5dae0c2f28e212.png

Edited by schrup21

FYI 

Updated to 26.1 B3 and the same happened: Installer stoped (nomore SSD activity), after power off / on and turning off the WLAN adapter in the BIOS, it ran without problems.

 

Spoiler

image.thumb.png.f15754f12243ed8ddfb38bfb1cb50377.png

 

Ordered a BCM943602CS to test on an AMD system. Swapped the current BCM94360CS2 and it's not deteced even in Windows... Either my adapater doesn't work with this card or the card is DOA... I'll order another card soon.

  • Sad 1

@Shaneee Wifi requires AppleVTD to be enabled, which isn't available on AMD systems, so that there is no chance of making it work, now and in the future. Sorry, but a complete wast of money and time! 😿

 

Mieze

  • Like 6
  • Confused 1
  • Sad 2

Figured this may help some people. I had an extra Fenvi T919 laying around and decided to disassemble. Once you take the heat shield off this is a standard PCI-e card adapter. Looks like you could just swap out the original card for a 

for a BCM943602CDP or so on. Have not tried this so i cannot comment on it. But once my new card comes in i will update. 

The original card on mine is a Broadcom BCM94360CDAX

20251014_163556.jpg

20251014_163615.jpg

20251014_163635.jpg

  • Like 5
  • Thanks 1
On 10/12/2025 at 3:14 PM, 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?

 

@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.

 

image.thumb.png.03475eeb3164f2d618ea4e8231bb0afc.png  

Edited by KGP-iMacPro
3 hours ago, 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.

 

image.thumb.png.03475eeb3164f2d618ea4e8231bb0afc.png  

I did the same in my config file, added the bcmc-srom-slide property. I agree it’s better although I still experience some instances of unstable behavior such as unexpected system freezing when the display turns off (I have another challenge which is that my display is turning off after some 15/20 minutes despite the fact that I disabled all these energy /display off settings).

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

 

these two are left, no idea what can / should be entered there

Spoiler

[   21.348847]: bcmc: Object *AppleBCMWLANChipConfigurator::fetchProperty(const char *) const [Object = OSData] Error: Failed to find the device property [bcmc-chip-otp].
[   21.348855]: bcmc: Object *AppleBCMWLANChipConfigurator::fetchProperty(const char *) const [Object = OSData] Error: Failed to find the device property [bcmc-user-otp].

 

 

Spoiler

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>PciRoot(0x0)/Pci(0x1C,0x5)/Pci(0x0,0x0)</key>
    <dict>
        <key>bcmc-firmware-path</key>
        <string>/usr/local/share/firmware/wifi/brcmfmac43602-pcie_7.35.177.61.bin</string>
        <key>bcmc-firmware-hash</key>
        <data>v0z8I+6VKj2C7zOg9fh4UyAcmPG+0DSHapEPNU83hi0=</data>
        <key>bcmc-srom-slide</key>
        <data>AAAAAA==</data>
        <key>bcmc-fake-chip-number</key>
        <data>DBEAAA==</data>
        <key>bcmc-module-instance</key>
        <string>lanai</string>
        <key>#bcmc-chip-otp</key>
        <data></data>
        <key>#bcmc-user-otp</key>
        <data></data>
        <key>bcmc-sku-override</key>
        <data>MFgAAA==</data>
        <key>bcmc-default-country-code</key>
        <string>DE</string>
        <key>bcmc-enable-auto-country</key>
        <data>AA==</data>
    </dict>
</dict>
</plist>


 

3 hours ago, schrup21 said:

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

 

these two are left, no idea what can / should be entered there

  Reveal hidden contents

[   21.348847]: bcmc: Object *AppleBCMWLANChipConfigurator::fetchProperty(const char *) const [Object = OSData] Error: Failed to find the device property [bcmc-chip-otp].
[   21.348855]: bcmc: Object *AppleBCMWLANChipConfigurator::fetchProperty(const char *) const [Object = OSData] Error: Failed to find the device property [bcmc-user-otp].

 

 

  Reveal hidden contents

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>PciRoot(0x0)/Pci(0x1C,0x5)/Pci(0x0,0x0)</key>
    <dict>
        <key>bcmc-firmware-path</key>
        <string>/usr/local/share/firmware/wifi/brcmfmac43602-pcie_7.35.177.61.bin</string>
        <key>bcmc-firmware-hash</key>
        <data>v0z8I+6VKj2C7zOg9fh4UyAcmPG+0DSHapEPNU83hi0=</data>
        <key>bcmc-srom-slide</key>
        <data>AAAAAA==</data>
        <key>bcmc-fake-chip-number</key>
        <data>DBEAAA==</data>
        <key>bcmc-module-instance</key>
        <string>lanai</string>
        <key>#bcmc-chip-otp</key>
        <data></data>
        <key>#bcmc-user-otp</key>
        <data></data>
        <key>bcmc-sku-override</key>
        <data>MFgAAA==</data>
        <key>bcmc-default-country-code</key>
        <string>DE</string>
        <key>bcmc-enable-auto-country</key>
        <data>AA==</data>
    </dict>
</dict>
</plist>


 

 

@schrup21, what about Section "PCI" of "System Information"? Are all PCI devices now properly listed again or does AppleBCMWLANCompanion.kext still destroy the entire PCI device information?

@KGP-iMacPro I didn't notice there was a problem there 😅

 

When I set the Keys "AAPL,slot-name" and "compatible" in BCM's property, nothing is displayed anymore—just a message saying "Error retrieving...". Without them, the others are displayed as before. 

Spoiler

image.thumb.png.1b90c8e2ad8352fea899331f5d8e6b04.png

 

  • Like 1
10 hours ago, schrup21 said:

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

 

these two are left, no idea what can / should be entered there

  Hide contents

[   21.348847]: bcmc: Object *AppleBCMWLANChipConfigurator::fetchProperty(const char *) const [Object = OSData] Error: Failed to find the device property [bcmc-chip-otp].
[   21.348855]: bcmc: Object *AppleBCMWLANChipConfigurator::fetchProperty(const char *) const [Object = OSData] Error: Failed to find the device property [bcmc-user-otp].

 

 

  Hide contents

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>PciRoot(0x0)/Pci(0x1C,0x5)/Pci(0x0,0x0)</key>
    <dict>
        <key>bcmc-firmware-path</key>
        <string>/usr/local/share/firmware/wifi/brcmfmac43602-pcie_7.35.177.61.bin</string>
        <key>bcmc-firmware-hash</key>
        <data>v0z8I+6VKj2C7zOg9fh4UyAcmPG+0DSHapEPNU83hi0=</data>
        <key>bcmc-srom-slide</key>
        <data>AAAAAA==</data>
        <key>bcmc-fake-chip-number</key>
        <data>DBEAAA==</data>
        <key>bcmc-module-instance</key>
        <string>lanai</string>
        <key>#bcmc-chip-otp</key>
        <data></data>
        <key>#bcmc-user-otp</key>
        <data></data>
        <key>bcmc-sku-override</key>
        <data>MFgAAA==</data>
        <key>bcmc-default-country-code</key>
        <string>DE</string>
        <key>bcmc-enable-auto-country</key>
        <data>AA==</data>
    </dict>
</dict>
</plist>


 

@schrup21 this is what the GitHub repo says about device properties

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

you’ll have to test and determine which ones work /are necessary for you.

  • Like 1
2 hours ago, schrup21 said:

@KGP-iMacPro I didn't notice there was a problem there 😅

 

When I set the Keys "AAPL,slot-name" and "compatible" in BCM's property, nothing is displayed anymore—just a message saying "Error retrieving...". Without them, the others are displayed as before. 

  Reveal hidden contents

image.thumb.png.1b90c8e2ad8352fea899331f5d8e6b04.png

 

 

I now completely removed all additional ARPT PCI properties from my SSDT, but I still get just the message saying "There was an error while gathering PCI device information" under "System Information" -> "PCI" as soon AppleBCMWLANCompanion.kext is enabled in the config.plist. It is a pity that this thread continues without any further input or feedback from @Austere.J.

 

btw.. when booting in verbose mode, do you also get several times the message: "couldn´t alloc class AppleBCMWLANcompanion" ??

Edited by KGP-iMacPro
  • Like 1
On 10/13/2025 at 1:17 PM, schrup21 said:

BCM4360 is not possible, you would need a BCM43602 (0x14E4, 0x43BA)

These two are different, the fmac firmware for BCM43602 is not compatible with a BCM4370 chip.

 

I guess you can replace the BCM94360CD on the fenvi with a BCM943602CDP 

 

there are Fenvi like adapters for BCM943602CS too, like this one:

image.thumb.png.37ff64aabb1eb14c4b5dae0c2f28e212.png

@schrup21

So this one should work?

 

image.png.980e0f2d4bb46cb512ce0cad19d82b46.png

  • Like 1
2 hours ago, eSaF said:

I am still testing the connection, so far so good.

Any sleep going on?

2 hours ago, eSaF said:

As reported AirDrop is not available,

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

@Mac Hosehead, have a look about the current limitations. System Information -> Wifi says that airdrop is available, but it's simply not working!  

 

https://github.com/0xFireWolf/AppleBCMWLANCompanion/blob/main/Documentation/Issues.md#apple-wireless-direct-link-awdl

 

 

Limitations and Known Issues

Apple Wireless Direct Link (AWDL)

AWDL is not currently available on Wi-Fi cards supported by BCMC. Unlike the legacy Broadcom Wi-Fi driver, 
which handled AWDL entirely in software, the current Wi-Fi driver now offloads this functionality to the firmware. 
As such, all Continuity features (e.g., AirDrop) that rely on AWDL are not working at this moment. You can use 
LocalSend as an alternative, or wait for OpenCore Legacy Patcher to add support for macOS Tahoe.

Internet Sharing

Sharing the Internet to the Wi-Fi adapter might not be working properly.

Power Management

Putting your computer to sleep or waking it up might trigger a kernel panic.

 

Edited by KGP-iMacPro
16 minutes ago, eSaF said:

For some reason I cannot boot into Sequoia or Sonoma (using one EFI Folder for all)

 

Probably because you applied the Root patch,
youI should try to rehabilitate what's needed to run OCLP AmfiPass.kext and everything else... I don't know if this conflicts with the Austere method, though. ( in Tahoe )

Edited by Anto65
  • Like 2
23 minutes ago, Anto65 said:

 

Probably because you applied the Root patch,
youI should try to rehabilitate what's needed to run OCLP AmfiPass.kext and everything else... I don't know if this conflicts with the Austere method, though.

 

There is no conflict of BCMC with AmfiPass.kext, SIP 03080000 or OCLP-mod AppleHDA root patch. However, one must certainly revert the Broadcom WIFI OCLP root patch in Sequoia and disable the respective com.apple.iokit.IOSkywalkFamily replacement in the config.plist. I am using the same EFI-Folder for Tahoe and Sequoia. No problems with booting both Systems.  Did not try to run my BCM943602CPD with Windows though.. 

 

 

 

 

Edited by KGP-iMacPro
  • Like 1
10 minutes ago, eSaF said:

I do run Tahoe, Sequoia and Sonoma off one EFI Folder that resides on the Tahoe EFI Partition.

I have to admit the OCLP patching is still in place on Sequoia and Sonoma so that is the possibility or cause boot failure on those two.

 

Still not happy with the lack of Sleep on machine. Cheers.

 

 

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.   

Edited by KGP-iMacPro
54 minutes ago, eSaF said:

Well I guess or one would hope  he is busy in the lab formulating a new WIFI update to present to us.

With all the bugs ironed out plus Lan and WIFI connection, this would be an awesome finale Intel Tahoe hack parting gift.

 

I still haven't removed this card in favour of the Fenvi as yet.

Maybe I will hold off for a few more days hoping a new development will happen or a new update.

 

My other bug bear is lack of Drivers in Windows although I have Ethernet connection on there.

Still busy searching for Drivers that would work.

 

So, for Windows with my Broadcom Wireless adapter (its a BCM43602), I used the Bootcamp drivers, as they are available but somewhat buried in that file.  The driver I installed dates back to 2012, but it works and it works at full speed.  Something to try at least.

 

I have some of those older Bootcamp files, but you might have an easier time just downloading them (Macupdate might have them), and you might be able to find them on Apples' site as well.

 

Just a thought.....

Broadcom for Windows.png

Edited by meg2014
  • Like 1
1 hour ago, eSaF said:

My other bug bear is lack of Drivers in Windows although I have Ethernet connection on there.

Still busy searching for Drivers that would work.

here you are 😉

WiFi_Broadcom_v7.77.119.0.zip

BluetoothBroadcom64.zip

Edited by schrup21
  • Like 3
×
×
  • Create New...