Jump to content

AirportBrcmFixup

fallen00sniper

By fallen00sniper,
in Lilu and plugins

 Share
151 posts in this topic

Recommended Posts

LockDown
LockDown
Posted
Posted (edited)
11 hours ago, lvs1974 said:

By default it is "-1", it means MFG kext will be disabled.

that was also the default before the latest commit correct?

and if it was, then i dont need that flag to boot as it is what worked for me?

Edited by ellaosx
Link to comment
Share on other sites
lvs1974
lvs1974
Posted
Posted

@fallen00sniper,

Sorry to hear that.

You can check by yourself in any hex-editor all patches - you will find a patch pattern if it is compatible.

You can save all wi-fi drivers from 10.13 DP0,  try to install 10.13.1-10.13.6, check all patch pattern, if they are incompatible -> replace all wi-fi drivers with ones from 10.13 DP0 and

continue investigation.

Also you can try to find people with the same wi-fi card and ask them what do they use (OSX version + patches/fake-id/AirportBrcmFixup).

Link to comment
Share on other sites
KristFlex
KristFlex
Posted
Posted

Hello @lvs1974,

I have a question to you. There are some more people on the web with the same problem. I have the BCM94350ZAE/DW1820A (14e4,43a3). It should be OOB supported, but it is not. Apparently, something changed in 10.11, since the 43a3 was moved from AirPortBrcm4360 to AirPortBrcmNIC. I had to install IO80211Family.kext from 10.10. The card works OBB over AirPortBrcm4360. With the original kexts from Mojave I get KP. I would continue to use the old Family.kext, but I'm getting panics because of invalid waitq, I think, just because the kext is old and not fully compatible.

Can you maybe look into it? I attached the old working one, maybe you can help me to get the card to work with the new kexts  

I'm using your AirportBrcmFixup, it works better with it and I can easily set the countrycode...

IO80211Family 10.10.kext.zip

Link to comment
Share on other sites
lvs1974
lvs1974
Posted
Posted
11 minutes ago, KristFlex said:

Hello @lvs1974,

I have a question to you. There are some more people on the web with the same problem. I have the BCM94350ZAE/DW1820A (14e4,43a3). It should be OOB supported, but it is not. Apparently, something changed in 10.11, since the 43a3 was moved from AirPortBrcm4360 to AirPortBrcmNIC. I had to install IO80211Family.kext from 10.10. The card works OBB over AirPortBrcm4360. With the original kexts from Mojave I get KP. I would continue to use the old Family.kext, but I'm getting panics because of invalid waitq, I think, just because the kext is old and not fully compatible.

Can you maybe look into it? I attached the old working one, maybe you can help me to get the card to work with the new kexts  

I'm using your AirportBrcmFixup, it works better with it and I can easily set the countrycode...

IO80211Family 10.10.kext.zip

No, it is not quite true about 43a3 and 10.11 (it was not moved):

  

10.8
AirPortBrcm4360: 43a0, IOProbeScore = 641
AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 615
10.9
AirPortBrcm4360: 43a0, IOProbeScore = 842
AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 700
10.10
AirPortBrcm4360: 43ba, 43a3, 43a0, 4331, 4353, IOProbeScore = 930
AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 900
10.11
AirPortBrcm4360: 43ba, 43a3, 43a0, 4331, 4353, IOProbeScore = 1040
AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 800
10.12
AirPortBrcm4360: 43ba, 43a3, 43a0, 4331, 4353, IOProbeScore = 1152
AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 800
10.13
AirPortBrcm4360: 4331, 4353, IOProbeScore = 1240
AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 800
AirPortBrcmNIC: 43ba, 43a3, 43a0, IOProbeScore = 1241
AirPortBrcmNIC-MFG: 43ba, 43a3, 43a0, IOProbeScore = -1000
10.14
AirPortBrcm4360: 4331, 4353, IOProbeScore = 1400
AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 800
AirPortBrcmNIC: 43ba, 43a3, 43a0, IOProbeScore = 1400
AirPortBrcmNIC-MFG: 43ba, 43a3, 43a0, IOProbeScore = -1000

 

43a3 was moved in 10.13.

So, till 10.13 it should work.

In 10.13 and higher you could try other fake-id (see this topic how to properly set fake-id).

Link to comment
Share on other sites
KristFlex
KristFlex
Posted
Posted
9 minutes ago, lvs1974 said:

No, it is not quite true about 43a3 and 10.11 (it was not moved):

  


10.8
AirPortBrcm4360: 43a0, IOProbeScore = 641
AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 615
10.9
AirPortBrcm4360: 43a0, IOProbeScore = 842
AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 700
10.10
AirPortBrcm4360: 43ba, 43a3, 43a0, 4331, 4353, IOProbeScore = 930
AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 900
10.11
AirPortBrcm4360: 43ba, 43a3, 43a0, 4331, 4353, IOProbeScore = 1040
AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 800
10.12
AirPortBrcm4360: 43ba, 43a3, 43a0, 4331, 4353, IOProbeScore = 1152
AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 800
10.13
AirPortBrcm4360: 4331, 4353, IOProbeScore = 1240
AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 800
AirPortBrcmNIC: 43ba, 43a3, 43a0, IOProbeScore = 1241
AirPortBrcmNIC-MFG: 43ba, 43a3, 43a0, IOProbeScore = -1000
10.14
AirPortBrcm4360: 4331, 4353, IOProbeScore = 1400
AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 800
AirPortBrcmNIC: 43ba, 43a3, 43a0, IOProbeScore = 1400
AirPortBrcmNIC-MFG: 43ba, 43a3, 43a0, IOProbeScore = -1000

 

43a3 was moved in 10.13.

So, till 10.13 it should work.

In 10.13 and higher you could try other fake-id (see this topic how to properly set fake-id).

Okay, I see. Some people stated it... I didn't know, since I started Hackintoshing already with High Sierra

But I actually tried to fake 4331 (in DSDT), but got KPs too. It worked once (no KP, don't know why, but when I connected to a network, Laptop became unusable)

Should I try to use your Debug version from last page with brcmfx-driver=0/2/...?

Link to comment
Share on other sites
lvs1974
lvs1974
Posted
Posted

@KristFlex,

You could try to fake using arbitrary properties in clover (you will find examples in this topic).

brcmfx-driver actually forces OSX to use only one driver, it is possible to achieve this by removing AirPortBrcmNIC or AirPortBrcmNIC-MFG.

And you always have an alternative: ask people with cards work with 10.13/10.14 and replace yours.

I can't help you if your card just incompatible with OSX for some reason.

Link to comment
Share on other sites
KristFlex
KristFlex
Posted
Posted
5 minutes ago, lvs1974 said:

@KristFlex,

You could try to fake using arbitrary properties in clover (you will find examples in this topic).

brcmfx-driver actually forces OSX to use only one driver, it is possible to achieve this by removing AirPortBrcmNIC or AirPortBrcmNIC-MFG.

And you always have an alternative: ask people with cards work with 10.13/10.14 and replace yours.

I can't help you if your card just incompatible with OSX for some reason.

Thats already my exchange card :) 

But it seems that it's like lottery. For some it works OOB, for some it works with small changes, and for some it doesn't work at all. But the card is the same, so there is something else, that prevents it from working, I assume.

Link to comment
Share on other sites
  • 2 weeks later...
  • 3 weeks later...
dloprios97
dloprios97
Posted
Posted (edited)

Hi guys.

I have the BCM94350ZAE wifi card (14e3, 43a3)

Question. Any way to load the 4360 driver on Mojave without slow the system after some minutes?

 

I've used a SSDT patch with 4354 id. after booting, it loads up the 4360 driver successfully, but after some minutes the system slows down making it unusable.
I've tried the new drivers (vanilla) and with AirportBrcmFixup 

AirPortBrcmNIC-MFG and 
AirPortBrcmNIC

And the performance is worse as you know.

Thanks in advance.

Edited by dloprios97
Link to comment
Share on other sites
dloprios97
dloprios97
Posted
Posted

@TheRacerMaster

I know how to force it. The problem is that after the driver is loaded it works perfectly for a couple of minutes, but then, slows down the system making it unusable. 
And the new drivers (the right ones) "AirportBrcmNIC and MFG wont work at all.
While booting with those the error message is "wl0:fatal error, reinitializing, total count of reinit's (##) @wlc_ol_down:1589" or "AirPort_Brcm4xx::syncPowerState:WWEN(disabled)"

 

As someone stated above, the only driver that works perfectly after booting is 4360 from 10.10. 

Link to comment
Share on other sites
  • 4 weeks later...
  • 1 month later...
rooney08
rooney08
Posted
Posted

Hi, I created another post about this but there were no responses so I deleted it. I'm hoping that AirportBrcmFixup.kext may be what I need to solve my issue, but so far I'm running out of ideas:

Here's what I had posted, with some new additions:

 

Hello, I recently added a Fenvi FV-T919 PCI-E card to my system (Gigabyte Z390 Aorus Pro, Mojave 10.14.3) because it was supposed to work "out of the box".

Indeed, bluetooth worked perfectly with no other modifications, but there were some issues with wifi. I assumed this card wouldn't require AirportBrcmFixup, but since it didn't work I tried installing AirportBrcmFixup.kext (version 1.19) into /Library/Extensions

Lilu (version 1.3.4) is also in /Library/Extensions. I am not using any airport/wifi fixes or fakeids in clover's config.plist

 

With AirportBrcmFixup installed the wifi is working, but there is a problem: the Wifi seems to be working fine when I first boot the system and it continues to work indefinitely, but if I ever turn the wifi off from the menu bar or the system preferences, I cannot get the WiFi to power on again without rebooting the system (bluetooth power on/off works perfectly)

 

I have tried switching the card to the other PCIE X1 slot on my board - same problem.

 

The device ID for this card is 14E4:43BA and it appears as BCM43602 802.11ac Wireless LAN SoC in DPCIManager

According to IOReg it appears to load the BrcmNIC driver and the AirportBrcmFixup kext is definitely loading.

 

I filtered the system logs on 'airport' and this is what I'm seeing

  

<-- THIS IS WHEN I POWER DOWN THE WIFI -->
default	10:45:52.589030 -0500	kernel	AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving). 
default	10:45:52.590187 -0500	kernel	AirPort: Link Down on awdl0. Reason 1 (Unspecified).
default	10:45:52.590451 -0500	kernel	AirPort_BrcmNIC::getSSIDData(): Get failure: APPLE80211_IOC_SSID: 6
default	10:45:52.590551 -0500	kernel	ARPT: 78.512460: AirPort_Brcm43xx::syncPowerState: WWEN[disabled]
default	10:45:52.591841 -0500	airportd	_handleLinkEvent: WiFi is not powered. Resetting state variables.
default	10:45:52.613019 -0500	kernel	com.apple.p2p: IO80211AWDLPeerManager::updateLocalRequests: Deleting PTR:._wifid._tcp.local. service PTR browse from airportd (pid 145)
default	10:45:52.725087 -0500	airportd	_processIPv4Changes: ARP/NDP offloads disabled, not programming the offload
default	10:45:52.742662 -0500	airportd	_processIPv4Changes: ARP/NDP offloads disabled, not programming the offload
                                                                                                                         
<-- THIS IS WHEN I ATTEMPT TO POWER IT BACK ON -->                                                                                                                         
default	10:46:06.646298 -0500	kernel	ARPT: 92.568205: VendorID check failed! vendorId[ffff] != 14e4  
default	10:46:06.847028 -0500	kernel	ARPT: 92.768936: wl0: fatal error, reinitializing, total count of reinit's[1], @'wlc_verify_d3_exit':47967
default	10:46:06.847160 -0500	kernel	ARPT: 92.769068: SMC['MSWo']: rdData[0x00] rcrd[132]
default	10:46:06.847996 -0500	kernel	ARPT: 92.769905: wl_dump_all_hw_regs - hw_up[0] Starting dumps...
default	10:46:06.870114 -0500	kernel	ARPT: 92.792022: wl0: fatal error, reinitializing, total count of reinit's[2], @'wl_nocard_war':4815
default	10:46:06.870660 -0500	kernel	ARPT: 92.792569: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]
default	10:46:06.870906 -0500	kernel	ARPT: 92.792815: AirPort_Brcm43xx::syncPowerState: WWEN[disabled]
default	10:46:06.870927 -0500	kernel	ARPT: 92.792836: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]
default	10:46:06.870944 -0500	kernel	ARPT: 92.792854: Clear UC AER: ffffffff
default	10:46:06.870952 -0500	kernel	ARPT: 92.792862: Clear Corr AER: ffffffff
default	10:46:06.870959 -0500	kernel	ARPT: 92.792868: Clear DEV_STS: ffffffff
default	10:46:06.870966 -0500	kernel	ARPT: 92.792875: Clear CFG_STAT:     ffff
default	10:46:07.181711 -0500	kernel	ARPT: 93.103618: VendorID check failed! vendorId[ffff] != 14e4
default	10:46:07.383097 -0500	kernel	ARPT: 93.305004: wl0: fatal error, reinitializing, total count of reinit's[3], @'wlc_verify_d3_exit':47967
default	10:46:07.383165 -0500	kernel	ARPT: 93.305074: wl0: fatal error, reinitializing, total count of reinit's[4], @'wl_nocard_war':4815
default	10:46:07.385700 -0500	kernel	ARPT: 93.307608: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]
default	10:46:07.387212 -0500	kernel	ARPT: 93.309120: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]
default	10:46:07.822684 -0500	kernel	ARPT: 93.744591: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]
default	10:46:07.826216 -0500	kernel	ARPT: 93.748123: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]
default	10:52:30.045773 -0500	kernel	ARPT: 475.967679: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]

 

thank you for any ideas

Link to comment
Share on other sites
rooney08
rooney08
Posted
Posted (edited)
17 hours ago, lvs1974 said:

@rooney08, it is hardware issue, your device is turned off.

You should try to isolate one or two pins on you card, please read here:

https://gsid.in/using-old-mini-pcie-wlan-cards-in-modern-laptops/

 

Yes, when I boot Mojave, it powers up fine. If I turn the power to the wifi off at any time while using the system, it turns off, but then I cannot turn it back on again unless I reboot Mojave again. This is a PCI-E adapter card with the wifi module integrated. Would it power up at all if it were a pinout issue? 

 

ADXZ_131747445023097354WfRguY7HVV.jpg

Edited by rooney08
Link to comment
Share on other sites
rooney08
rooney08
Posted
Posted
20 hours ago, lvs1974 said:

@rooney08, it is hardware issue, your device is turned off.

You should try to isolate one or two pins on you card, please read here:

https://gsid.in/using-old-mini-pcie-wlan-cards-in-modern-laptops/

Thank you for your suggestions.

 

I pulled this card out of my system and I noticed that the RF shield is soldered around the Broadcom card so before attempting to remove the shielding I tried installing it in one of my older systems which is running High Sierra 10.13.6.

 

In this system, the card worked perfectly "out of the box". I was able to turn the wifi on and off as expected, the bluetooth was working fine as well. No kexts or any clover configs required, so I don't think there's any hardware issue with this card.

 

To me, this indicates that it could be a Mojave issue or something specific (software or hardware) to the newer Z390 system that I've build.

 

 

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...