AirportBrcmFixup

[lvs1974]

@fallen00sniper

 

What was the last OSX version where your card worked properly?

Here http://dosdude1.com/mojave/ there is a list of unsupported cards in Mojave.

My card: Card Type: AirPort Extreme  (0x14E4, 0x2123),

What is yours?

[fallen00sniper]

@lvs1974

 

mine just says Third-Party Wireless Card with nothing else that i remember, but with AirportBrcmFixup it says 0x14E4, 0x854F or something similar.

 

it does show the MAC address, channels, airdrop is supported, airdrop channel 6, status off.

Edited November 3, 2018 by fallen00sniper

[fallen00sniper]

@lvs1974

 

well I suppose this card may be a lost cause, but maybe I am going about fixing it wrong.

 

I'll get those logs for you tomorrow morning, maybe there will be something in them that is the missing piece to get it working properly.

[lvs1974]

@fallen00sniper

 

Could you try the attached version?

On the screenshot you will find the working example how to fake id to 43ba (my original is 43b1).

I don't have any additional patches/settings in config.plist for Wi-Fi.

I also can choose a driver: brcmfx-driver=0, and in IOReg I see AirPort_BrcmNIC-MFG,

brcmfx-driver=2, and in IOReg I see AirPort_BrcmNIC.

In logs I can see that 43b1 is replaced with 43ba.

 

If you can't get this card working in Mojave, may be it worth to try with 10.13.6...

1.1.6 (DEBUG).zip

Edited November 4, 2018 by lvs1974

[fallen00sniper]

@lvs1974

 

it wasn’t booting before because I did not see you were using data on property 0 and CCG defaults to string.

 

booted this time set as 43a3 and the results in io jones are reporting as 43a3.

 

43a3

brcmfx-driver=2

still goes to the hollow WiFi icon at scan.

 

brcmfx-driver=0

reacts the same.

 

43ba

brcmfx-driver=2

still goes to the hollow WiFi icon at scan.

 

brcmfx-driver=0

Hollow icon at boot

 

I will attach attach logs from my main and update this post.

 

also should I be using these custom properties for my hackbook pro? WiFi works right away with fixup and Bluetooth with fakeid.

brcmfx-debug-logs.zip

Edited November 4, 2018 by fallen00sniper

[lvs1974]

@fallen00sniper

 

I had a look into your latest logs and discovered one strange thing:

In all 4 logs I see this string: "AirportBrcmFixup:  BRCMFX @ (DBG) probe: disable service AirPort_BrcmNIC_MFG".

It means there is a trouble with argument brcmfx-driver, since AirPort_BrcmNIC_MFG is disabled: by default (there is no boot-arg brcmfx-driver) and when brcmfx-driver is not zero. But for brcmfx-driver=0 this string must be different (disable service AirPort_BrcmNIC).

Could you post here your config.plist just to check it?

Edited November 4, 2018 by lvs1974

[fallen00sniper]

@lvs1974

 

here is my entire clover, REDACTED the serials and uuid of course.

 

config, kexts minus changes I've been making and DSDT by @MaLd0n

SSDT by ssdtgenpr (piker alpha)

CLOVER.zip

[lvs1974]

@fallen00sniper

 

Ok, now I see a mistake:

You have: 

Quote

-brcmfx-driver=2 npci=0x2000 dart=0 keepsyms=1 -brcmfxdbg -v

But it should be:

Quote

brcmfx-driver=0 npci=0x2000 dart=0 keepsyms=1 -brcmfxdbg -v

 

In macOS if you use "=" -> minus is never used.

So, just remove minus and set brcmfx-driver=0 to try MFG driver, I think this is a last chance.

Also please add boot-args wl_msg_level=0xff wl_msg_level2=0xff bcom.logging=0xff (to get more output in log from apple Broadcom driver).

Edited November 4, 2018 by lvs1974

[fallen00sniper]

@lvs1974

 

ah, guess it was a typo previously in one of the posts I saw from you.

 

fixed that and booted with 43BA and 43A3 with both driver=0 and driver=2.

 

no real change, but maybe now you will see something of value in my logs and think up a way to fix it or maybe there is a card I should be telling macOS I am using that is different than what I am?

 

hope you do find a way to fix it.

brcmfx-debug-logs-2.zip

[lvs1974]

@fallen00sniper

 

I checked all my posts, there was no typo anywhere, in every post brcmfx-driver mentioned without minus.

I also checked all logs, and unfortunately our goal is not reached: MFG driver is not loaded (because of race condition).

I will try to fix it in AirportBrcmFixup (and hopefully MFG will be loaded), but I am not sure if it really helps you.

Just to be sure: what do yo mean by hollow WiFi icon at scan? How does it look like?

You see the icon and you can scan networks, but there are no any networks?

Edited November 5, 2018 by lvs1974

[lvs1974]

@fallen00sniper

 

Could you try this version with brcmfx-driver=0?

1.1.7 (DEBUG).zip

[fallen00sniper]

@lvs1974

 

I’ll try when I get home, I see a normal WiFi icon, when I click on it it says looking for networks, then it becomes empty and changes from turn WiFi off to turn WiFi on and is empty or just an outline of the icon.

 

with some tests at login it was empty.

 

if I don’t use brcmfx-driver boot arg MFG loads and I have seen it load with previous attempts to get it working, @Pavo

Got it to load by jumping things like whitelist check in the binary with kext to patch and still didn’t have WiFi, but that was with letting fixup handle normally.

[lvs1974]

@fallen00sniper

 

I mean you should see AirPort_BrcmNIC-MFG in ioreg if MFG-driver is used. Did you see it without brcmfx-driver?

Edited November 5, 2018 by lvs1974

[fallen00sniper]

 

@lvs1974

I’ve seen it loaded in kextstat, one of my previous posts had it shown, ioreg I don’t remember seeing it.

 

I'm seeing it in iojones, zip also has screen grabs.

brcmfx-debug-logs-3.zip

Edited November 6, 2018 by fallen00sniper
added zip

[lvs1974]

@fallen00sniper

 

Now I see that AirportBrcmFixup worked properly, and it managed to load AirPortBrcmNIC-MFG and AirPortBrcmNIC depending on brcmdx-driver.

BTW: if you see kext in kextstat, it does not necessarily mean it is started, it also can be a case that it was loaded and tried to start, but was stopped. Only class name in ioreg tells the true about which driver exactly is started.

 

Regarding your logs:

(AirPortBrcmNIC-MFG) ARPT: 17.625159: AirPort_Brcm43xx::setPowerCycleInProgress: state [0] -> [1], name['wl_fatal_error'] id[31664]
(AirPortBrcmNIC-MFG) ARPT: 17.757917: Fatal Error - Initiate powercycle
(AirPortBrcmNIC-MFG) ARPT: 17.757924: wl_fault_powercycle: thread_call_enter1 - Power Thread scheduled

(AirPortBrcmNIC) ARPT: 15.511240: AirPort_Brcm43xx::setPowerCycleInProgress: state [0] -> [1], name['wl_fatal_error'] id[31664]
(AirPortBrcmNIC) ARPT: 15.623120: Fatal Error - Initiate powercycle
(AirPortBrcmNIC) ARPT: 15.623128: wl_fault_powercycle: thread_call_enter1 - Power Thread scheduled

I can see the both drivers got this fatal error when try to turn on power for this board.
And both drivers tried to do this many times.

 

I am not good in hardware, but could it mean some hardware issues?

Do you have any other OS installed on this desktop pc, does this broardcom card work?

 

I would suggest you to run Sierra 10.12.6 and check whether this card still works.

If it works, you can try to install High Sierra DP1 and apply these Sherlock's patches in clover (and boot system without AirportBrcmFixup):

BCM4352-Airport-Extreme, (credit skvo)
com.apple.driver.AirPort.Brcm4360
6b100000 750d
6b100000 9090
10.13.x

BCM4352-Airport-Extreme, (credit Sherlocks based on skvo original)
com.apple.driver.AirPort.BrcmNIC
6b100000 750d
6b100000 9090

BCM4352-fvco, (credit Sherlocks based on the-darkvoid original)
com.apple.driver.AirPort.BrcmNIC
81f952aa 000074bf 
81f952aa 00006690 

BCM4352-iovar, (credit Sherlocks)
com.apple.driver.AirPort.BrcmNIC
85db4c8b 65c87971 
85db4c8b 65c8eb71 

BCM4352-iovar, (credit Sherlocks)
com.apple.driver.AirPort.BrcmNIC
4883c410 89c385db 7946
4883c410 89c385db eb46


BCM4352-Airport-Extreme, (credit Sherlocks based on skvo original)
com.apple.driver.AirPort.BrcmNIC-MFG
6b100000 750d
6b100000 9090

BCM4352-fvco, (credit Sherlocks based on the-darkvoid original)
com.apple.driver.AirPort.BrcmNIC-MFG
81ff52aa 000074c4 
81ff52aa 00006690 

BCM4352-iovar, (credit Sherlocks)
com.apple.driver.AirPort.BrcmNIC-MFG
0f896201 0000
0f886201 0000

BCM4352-iovar, (credit Sherlocks)
com.apple.driver.AirPort.BrcmNIC-MFG
4883c410 89c385db 7944
4883c410 89c385db eb44

 

If High Sierra DP1 works with these patches, try to turn them off in clover and boot with AirportBrcmFixup.

If it does not work with AirportBrcmFixup: turn on these patches one-by-one and try to find out which patch is critical for working Wi-Fi.

 

I think this is the only way to find out something, and most probably you fill wind the missing patch.

You can also try to fake-id to AirportBrcm4360 (brcmfx-driver=1), but I don't expect this can work.

And you can also try to post one of these logs in linux forum about Brcm43xx, and ask why could it happen (power issues).

Edited November 6, 2018 by lvs1974

[LockDown]

does your laptop have a switch toggle for the wifi?

[fallen00sniper]

@ellaosx

It’s a desktop.

 

@lvs1974

I’ll look into that, I can boot with Linux and I’m sure the card will work. Fairly confident it’s macos blocking the card.

 

with the Broadcom Linux sta driver it is working fine on xubuntu 18.04 or 18.10.

 

i can test high Sierra 10.13.6, I do not have an installer available for anything older.

Edited November 7, 2018 by fallen00sniper
New info to add and image

[fallen00sniper]

@lvs1974

 

i got 10.13 dp1, installed, tried to use the first patch only and get a kernel panic once it tries to load the login screen.

 

should i remove fixup and try again?

[lvs1974]

@fallen00sniper

Yes, that was my idea - first of all to try these patches, without AirportBrcmFixup.

Once you get Wi-Fi working, we need to find a critical patch. 

Edited November 11, 2018 by lvs1974

[fallen00sniper]

@lvs1974

 

it continues to reboot, patches are disabled and fixup is removed.

 

its only booted once to desktop and since then it will no longer boot.

 

i would say it seems to not like my dsdt, but it wasn’t an issue before.

 

I’ve tried booting in safe mode as well, Mojave is still installed on the other drive that it has.

 

Edited November 11, 2018 by fallen00sniper

[LockDown]

Hi @fallen00sniper

try with npci=0x2000

[lvs1974]

@fallen00sniper

Anyway, it would make sense to fix DSDT issues.

[LockDown]

@lvs1974

with your latest commit, which one is the default?

boot-arg brcmfx-driver=[0|1|2]

[lvs1974]

44 minutes ago, ellaosx said:

@lvs1974

with your latest commit, which one is the default?

boot-arg brcmfx-driver=[0|1|2]

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

[fallen00sniper]

@lvs1974

 

i think its because my dsdt was made for Mojave specifically.

 

i will try reinstalling over the install.

 

@ellaosx

 

already have that checked by default or I cannot boot.

Edited November 12, 2018 by fallen00sniper