Broadcom WiFi/Bluetooth [Guide]

[dclive]

@dclive try removing all the BT devices, and then reconnecting them.

The current BT connection settings may be looking for your Intel BT module. Now you have a Broadcom BT module installed, clearing all the old Intel BT settings may be the only way to get them to connect to the new Broadcom card.

This is a new (to me) machine, and I never attached anything via Intel BT.
I know it really does see the Master 3 b/c I didn't have it hooked up via BT to this machine before, and it's not tied to my Apple ID ofc.

 

[dclive]

The screenshot appears to point to an issue with a Thunderbolt ACPI address not being found, as the main cause of the kernel panic.

Are you using any thunderbolt devices?

No, I am not. Just a basic USBC dock for HDMI out and USBA and ethernet capability.

 

[pastrychef]

Same issue as before - I can see my MX Master 3 mouse, but I cannot connect to it - just shows spinny progress indicator forever.

Speedtest.net:
(Used Stats to confirm no network activity during tests)
USBC Ethernet Dock on gigabit home ethernet to gigabit provider fiber: 249/337.
DW1830 to Unifi / Ubiquiti hardware: 71/49.
DW1830 to provider's router: (paused to let ads load without a pihole): 17/27, then 7/8, then 12/34.
DW1830 to Unifi / Ubiquiti hardware (again): 62/72
I'm two American inside walls away from both WAPs.

I don't know why it's giving you problems... That's the same way I have the Bluetooth kexts set up on several different hackintoshes. I have also tested the same settings on a DW1830 and it worked.

If you hold the Option key and click on the Wi-Fi icon in the upper right corner of Finder, what do you see?

This is from a DW1560:

 

[broly]

AirportBrcmFixup.kext won’t work in any version of macOS older than Yosemite. The kext has been designed and created specifically not to work in the older versions. See the Notes section.

GitHub - acidanthera/AirportBrcmFixup: An open source kernel extension providing a set of patches required for non-native Airport Broadcom Wi-Fi cards.

An open source kernel extension providing a set of patches required for non-native Airport Broadcom Wi-Fi cards. - GitHub - acidanthera/AirportBrcmFixup: An open source kernel extension providing a...

github.com

If you have a natively supported Broadcom card you don’t need any third-party kexts for the WiFi/BT to work.

hi,

it is natively supported after yosemite. it is a BCM43xx card.

i think the issue is that the model/vendor ID aren't present in the existing kexts for 10.8/10.9.

what can i try to add my vendor ID to the existing BCM43xx driver in 10.8.5?

to be precise, it's the: BCM943602CDP pci14e4,43ba. it was supported first in yosemite.

i am hoping there is a way to get this detected as the BCM94360CD, which is pci14e4,43a0.

i did successfully inject the AirportBrcmFixup but nothing happens. i tried adding the pci14e4,43a0 string to the IO80211Family.kext/Contents/Plugins/AirPortBrcm4360.kext but that didn't seem to work.

interestingly, in mojave, both 43a0 and 43ba are referenced in the BrcmAirPortNIC.kext. i was hoping this would let me use the 4360 kext.

maybe it's because i haven't tried to inject bluetooth as well, since this is a 2 in 1 card.

 

[Edhawk]

You can try adding the BCM94360CD device-id (0x43a0) to OpenCore config.plist or to your Clover config.plist, so the card is recognised and possibly activated in an earlier version of macOS. The device-id entry might look something like the DeviceProperties entry for my Broadcom WiFi card below.



The Device Path, slot name, type and model entries can be obtained from Hackintool > PCIe tab, using the Export function. Then Copied to your system config.plist's DeviceProperties section.

The device-id and built-in entries would need to be manually added. This example is shown in an OC plist viewed in ProperTree plist editor.

You could also try adding the AirportBrcmFixup.kext boot argument to your config.plist:

brcmfx-driver=1 this enables/pushes the AirPortBrcm4360 kext for loading.

0 - AirPortBrcmNIC-MFG,​

1 - AirPortBrcm4360,​

2 - AirPortBrcmNIC,​

3 - AirPortBrcm4331​

These are the Broadcom WiFi kexts that function in Mountain Lion, Mavericks & Yosemite, with the corresponding card device id's listed against each kext.

 

[dclive]

 

[broly]

You can try adding the BCM94360CD device-id (0x43a0) to OpenCore config.plist or to your Clover config.plist, so the card is recognised and possibly activated in an earlier version of macOS. The device-id entry might look something like the DeviceProperties entry for my Broadcom WiFi card below.

View attachment 561045

The Device Path, slot name, type and model entries can be obtained from Hackintool > PCIe tab, using the Export function. Then Copied to your system config.plist's DeviceProperties section.

The device-id and built-in entries would need to be manually added. This example is shown in an OC plist viewed in ProperTree plist editor.

You could also try adding the AirportBrcmFixup.kext boot argument to your config.plist:

brcmfx-driver=1 this enables/pushes the AirPortBrcm4360 kext for loading.

0 - AirPortBrcmNIC-MFG,​

1 - AirPortBrcm4360,​

2 - AirPortBrcmNIC,​

3 - AirPortBrcm4331​

These are the Broadcom WiFi kexts that function in Mountain Lion, Mavericks & Yosemite, with the corresponding card device id's listed against each kext.

View attachment 561044

thsi is a very clever and good idea. i bet it would work.

i don't want to modify my deviceproperties entries of my plist because i run mojave on the regular.
but this is a great idea. i managed to get the PCI stuff working in mojave now too, so i don't absolutely need mountain lion.

is there a way to create a deviceproperties entry for a range of kernels, like the kext loading? probably not?

very good idea and thank you. i will keep this in mind for the future, no dobut.

 

[dclive]

Same issue as before - I can see my MX Master 3 mouse, but I cannot connect to it - just shows spinny progress indicator forever.

Speedtest.net:
(Used Stats to confirm no network activity during tests)
USBC Ethernet Dock on gigabit home ethernet to gigabit provider fiber: 249/337.
DW1830 to Unifi / Ubiquiti hardware: 71/49.
DW1830 to provider's router: (paused to let ads load without a pihole): 17/27, then 7/8, then 12/34.
DW1830 to Unifi / Ubiquiti hardware (again): 62/72
I'm two American inside walls away from both WAPs.

With near LOS (it's behind a TV) to a 802.11ax Wifi 6 Ubiquiti WAP, I get 214/135.

 

[Edhawk]

is there a way to create a deviceproperties entry for a range of kernels, like the kext loading? probably not?

No, you currently can't differentiate DeviceProperties by a range of kernels.

While that is possible with Kernel Extensions (Kexts) and Kernel Patches it is not when dealing with Device Properties.