Contribute
Register

[HELP] BCM94352Z Bluetooth works Wifi don't on big sur

Status
Not open for further replies.
nice pic...

remove that kext that is highlighted
 
Yea I forgot bout that mb. But I'm glad you figured it! GG
Sadly Clover-Configurator cannot handle this entry and seems to overwrite it on manual save...
Is there another option of placing this fix?

EDIT: however it seems to work without the .plist-entry now - strange...
 
Last edited:
Thank you, finally figured it to work!

So to sum up what I did

Removed:
Code:
<key>PciRoot(0x0)/Pci(0x1c,0x1)/Pci(0x0,0x0)</key>
            <dict>
                <key>AAPL,slot-name</key>
                <string>WLAN</string>
                <key>compatible</key>
                <string>pci14e4,4353</string>
                <key>device_type</key>
                <string>Airport Extreme</string>
                <key>model</key>
                <string>DW1560 (BCM4352) 802.11ac Wireless</string>
                <key>name</key>
                <string>Airport</string>
            </dict>

Updated AirportBRCMFixup.kext to latest version
Removed AirPortBrcm4360_Injector.kext from plugins folder of AirportBRCMFixup kext
and added entry
Code:
<dict>
                <key>Arch</key>
                <string>Any</string>
                <key>BundlePath</key>
                <string>AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcmNIC_Injector.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string></string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
Can you share your config.plist, I'm same issue with wifi, the entry in witch section shoud be added. Thank's in advance
 
yes, those amendments have made it work as now the system is loading the module to make your wifi work :)

glad it is all sorted!
Hey @Feartech , I have the same BCM4352Z as Miszel but can't make wifi to work, only bluetooth.
Have enabled all kexts needed, but still no success.
Attached my Opencore 0.66 Folder.
macOS 11.2 Big Sur
Note: there are some patches regarding IC2 Trackpad debuging.
Thanks
 

Attachments

  • BCM4352Z Debug Folder.zip
    5 MB · Views: 140
Hey @Feartech , I have the same BCM4352Z as Miszel but can't make wifi to work, only bluetooth.
Have enabled all kexts needed, but still no success.
Attached my Opencore 0.66 Folder.
macOS 11.2 Big Sur
Note: there are some patches regarding IC2 Trackpad debuging.
Thanks

missing AirportBrcmFixup.kext in your kexts folder

also add brcmfx-driver=2 to boot arguments
 
missing AirportBrcmFixup.kext in your kexts folder

also add brcmfx-driver=2 to boot arguments
I deleted the AirportBrcmFixup.kext somehow before send you the files but it is there for sure.
Added the brcmfx-driver=2 boot argument but still nothing. (Also tried brcmfx-alldrv boot argument.)

I used itlwm kext before, for Intel wifi. Could it messed up my network configurations? There is no wifi on my network preferences.

Already tried to reset my network configurations but not sure if Big Sur used a backup to reload the old config.

And another strange thing: DPCI Manager can't find the Broadcom device on the PCI list.
 
I deleted the AirportBrcmFixup.kext somehow before send you the files but it is there for sure.
Added the brcmfx-driver=2 boot argument but still nothing. (Also tried brcmfx-alldrv boot argument.)

I used itlwm kext before, for Intel wifi. Could it messed up my network configurations? There is no wifi on my network preferences.

Already tried to reset my network configurations but not sure if Big Sur used a backup to reload the old config.

And another strange thing: DPCI Manager can't find the Broadcom device on the PCI list.
upload new files
 
upload new files
I made a revision of the applied patches before send you new files. I don't exactly why it happens, but the brcmfx-driver=2 boot argument seems to be not saved on the config.plist file at the first time. (I suspect a NVRAM issue.)

So, I did ensure the boot argument was applied and rebooted the system. At the first reboot, the wifi icon on the top right started to flash, like looking for a network, altough find nothing. At this point, there was no wifi on the network configurations and it keep flashing even turning wifi off.

From the second reboot and so on, the icon didn't flash anymore. For now, I reset NVRAM at every opencore reboot.

The attached config.plist has both brcmfx-driver=2 and brcmfx-alldrv boot arguments, but I tried each one at a time.

The zip file also has a copy of my ioreg.
 

Attachments

  • BCM4352Z Debug Folder 2.zip
    5.6 MB · Views: 51
I made a revision of the applied patches before send you new files. I don't exactly why it happens, but the brcmfx-driver=2 boot argument seems to be not saved on the config.plist file at the first time. (I suspect a NVRAM issue.)

So, I did ensure the boot argument was applied and rebooted the system. At the first reboot, the wifi icon on the top right started to flash, like looking for a network, altough find nothing. At this point, there was no wifi on the network configurations and it keep flashing even turning wifi off.

From the second reboot and so on, the icon didn't flash anymore. For now, I reset NVRAM at every opencore reboot.

The attached config.plist has both brcmfx-driver=2 and brcmfx-alldrv boot arguments, but I tried each one at a time.

The zip file also has a copy of my ioreg.
try putting them in the correct order:
Code:
<dict>
                <key>Arch</key>
                <string>x86_64</string>
                <key>BundlePath</key>
                <string>AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcmNIC_Injector.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string></string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string>19.0.0</string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
            <dict>
                <key>Arch</key>
                <string>x86_64</string>
                <key>BundlePath</key>
                <string>AirportBrcmFixup.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/AirportBrcmFixup</string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string>19.0.0</string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>

remove brcmfx-alldrv boot argument

remove this garbage:
Code:
<key>######boot-args</key>
                <string>igfxonln=1 -igfxlspcon</string>
                <key>#####boot-args</key>
                <string>-igfxfbdump -igfxdump</string>
                <key>#boot-args</key>
                <string>-v keepsyms=1</string>
                <key>#prev-lang:kbd</key>
                <data>
                cnUtUlU6MjUy
                </data>

what does -noDC9 boot argument do?
 
try putting them in the correct order:
Code:
<dict>
                <key>Arch</key>
                <string>x86_64</string>
                <key>BundlePath</key>
                <string>AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcmNIC_Injector.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string></string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string>19.0.0</string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
            <dict>
                <key>Arch</key>
                <string>x86_64</string>
                <key>BundlePath</key>
                <string>AirportBrcmFixup.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/AirportBrcmFixup</string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string>19.0.0</string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
Do you mean putting AirPortBrcmNIC_Injector.kext BEFORE AirportBrcmFixup.kext?

remove brcmfx-alldrv boot argument


remove this garbage:
Code:
<key>######boot-args</key>
                <string>igfxonln=1 -igfxlspcon</string>
                <key>#####boot-args</key>
                <string>-igfxfbdump -igfxdump</string>
                <key>#boot-args</key>
                <string>-v keepsyms=1</string>
                <key>#prev-lang:kbd</key>
                <data>
                cnUtUlU6MjUy
                </data>

what does -noDC9 boot argument do?
It's about power management/sleep kernel panics on some Ice Lake laptops (like mine). See here.
 
Status
Not open for further replies.
Back
Top