Jump to content

AirportBrcmFixup


fallen00sniper
 Share

151 posts in this topic

Recommended Posts

8 minutes ago, ellaosx said:

@lvs1974

missing probably are:

frdWst's pci patch

Neo.aka.Darkman patch (not sure if you have it already)

 

sherlocks iovar as you mentioned. But since sherlocks discontinued the project, i gathered all his and the rest of the dev's patches and I verified the hex exists.

 

Sending you the attachment in PM.

frdWst's and Neo.aka.Darkman are already in place, otherwise it would not work for many people.

What is iovar and powerstate problem?

Link to comment
Share on other sites

[mention=980913]Sherlocks[/mention], what is power state problem (iovar)?
What do these patches:
BCM4352-Airport-Extreme, (credit skvo)com.apple.driver.AirPort.Brcm43606b100000 750d6b100000 909010.13.xBCM4352-Airport-Extreme, (credit Sherlocks based on skvo original)com.apple.driver.AirPort.BrcmNIC6b100000 750d6b100000 9090BCM4352-fvco, (credit Sherlocks based on the-darkvoid original)com.apple.driver.AirPort.BrcmNIC81f952aa 000074bf 81f952aa 00006690 BCM4352-iovar, (credit Sherlocks)com.apple.driver.AirPort.BrcmNIC85db4c8b 65c87971 85db4c8b 65c8eb71 BCM4352-iovar, (credit Sherlocks)com.apple.driver.AirPort.BrcmNIC4883c410 89c385db 79464883c410 89c385db eb46

 
AirPortBrcmNIC

as i rememeber, i need to disabled iovar log. because log related in iovar flood state in high sierra. it causes system slow. because log floods. except iovar, seems other patches already included in your kext.
now i don't know that iovar patch actually need or not.

나의 LG-F800S 의 Tapatalk에서 보냄

Link to comment
Share on other sites

17 hours ago, ellaosx said:

@lvs1974

missing probably are:

frdWst's pci patch

Neo.aka.Darkman patch (not sure if you have it already)

 

sherlocks iovar as you mentioned. But since sherlocks discontinued the project, i gathered all his and the rest of the dev's patches and I verified the hex exists.

 

Sending you the attachment in PM.

 

would any of these patches help me?

Link to comment
Share on other sites

2 hours ago, fallen00sniper said:

@lvs1974

 

Just used this on my laptop with azurewave bcm4352hmb and it worked flawlessly.

 

i think I’m missing a power state patch for my desktop.

Sherlock has already replied to this question: all critical patches are implemented in AirportBrcmFixup.

iovar /power state patch - it is only about possible logging issues.

So, if you have some binary patch which works for you - let me know which exactly.

You can combine AirportBrcmFixup and missed binary patch in clover.

If it works - I will have a look at this patch and try to add it into AiportBrcmFixup.

Link to comment
Share on other sites

@lvs1974

 

I have patches that I used with Sierra.

 

No idea how to convert them to working with Mojave or if it’s possible, but they don’t work now and the first patch AirportBrcmFixup takes care of just fine.

 

KextsToPatch

  1. Name: AirPortBrcm4360
    Find: 306B100000750D
    Replace: 306B1000009090
    Comment: Change Asus PCE-AC66 ID to AirPort Extreme (0x14E4, 0x854F)
     
  2. Name: AirPortBrcm4360
    1. Find: 4183fcff 742c48
    2. Replace: 66c70655 53eb2b
    3. Comment: Enable 5Ghz
  3. Name: AirPortBrcm4360
    1. Find: 4d61632d 43364546 41363339 36324643 36454130
    2. Replace: 4d61632d 32374144 42423742 34434545 38453631
    3. Comment: Add PCE-AC66 to whitelist


the second and third patch were found here
http://www.iatkosx86.tk/2017/04/enabling-5ghz-networking-for-bcm4360-in.html

Link to comment
Share on other sites

@fallen00sniper,

I have checked, and all three patches are implemented in AirportBrcmFixup.

I added some additional logging into kext, could you boot whit attached debug kext, get kernel log and put it in this topic? 

Also would be nice to know an output of terminal command: kextstat | grep -i airport

1.1.6 (DEBUG).zip

Edited by lvs1974
  • Like 1
Link to comment
Share on other sites

@lvs1974

 

the kext is causing a boot loop to kernel panic and your system was restarted, repeat.

 

without the kext com.apple.driver.Airport.BrcmNIC loads.

 

with the previous version of 1.16 kext

 

as.lvs1974.AirportBrcmFixup

com.apple.driver.Airport.BrcmNIC

com.apple.driver.Airport.BrcmNIC-MFG

 

when you find the issue and upload again, I’ll get a kernel log with it.

Edited by fallen00sniper
Link to comment
Share on other sites

@fallen00sniper

 

Boot loop - it is very strange.

Could you temporarily move AirPortBrcmNIC.kext from /S/L/E/IO812Family.kext/Contents/Plugin into ~/Desktop and try to boot?

And after - put it back and move /S/L/E/AirPortBrcmNIC-MFG.kext into ~/Desktop and try to boot again?

Edited by lvs1974
  • Like 1
Link to comment
Share on other sites

@fallen00sniper,

 

I modified the kext, so now you can use boot-arg to specify which airport driver should be used:

brcmfx-driver=0, com.apple.driver.AirPort.BrcmNIC-MFG

brcmfx-driver=1, com.apple.driver.AirPort.Brcm4360

brcmfx-driver=2, com.apple.driver.AirPort.BrcmNIC

 

Could you try this kext with  brcmfx-driver=0 and brcmfx-driver=2, and put logs for both cases?

1.1.6 (DEBUG).zip

Edited by lvs1974
Link to comment
Share on other sites

@lvs1974

 

attaching logs for all three possible options, thought it wouldn't hurt to do 1 as well.

 

in all tests "no wifi hardware installed" icon.

AirportBrcmFixup-Debug-Logs.zip

 

my config is based on one I found online, but usually I use csractiveconfig 0x67, this one has been using 0x3E7... could that be a problem?

Edited by fallen00sniper
Link to comment
Share on other sites

@ellaosx

 

it's interesting my bcm94352hmb worked fine without fixairport being checked, installed the RehabMan kexts for BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext, did the fake wifi injection and boom bluetooth works, my hackbook pro is being so much easier than my hp z420 (E5-1650 v1) when it comes to wifi and other fixes and I had to get the bios modded for whitelist removal to get a compatible card in place.

 

for me that was easier than fixing my hackintoshes lol

 

wish the patches that I had found way back in Sierra worked still.

 

good you got your issue fixed. :)

Edited by fallen00sniper
Link to comment
Share on other sites

@fallen00sniper

I don't see anything from AirportBrcmFixup in logs, 

  1. did you check that it is loaded: kextstat | grep -i airport?
  2. did you add boot-arg -brcmfxdbg?

 

In the next time please check (before put logs here) that there are occurrences of string AirportBrcmFixup in your logs.

Edited by lvs1974
  • Like 1
Link to comment
Share on other sites

@fallen00sniper

 

I discovered a bug in the latest debug AirportBrcmFixup.kext, but it doesn't explain why there are no any strings like "AirportBrcmFixup" in your logs.

Could you try a kext attached in this post with boot-args:

brcmfx-driver=0 -brcmfxdbg

brcmfx-driver=2 -brcmfxdbg

 

Please fetch kernel logs for both cases and put in this topic.

1.1.6 (DEBUG).zip

Edited by lvs1974
Link to comment
Share on other sites

sorry I followed directions incorrectly and removed the -brcmfxdbg, added it back.

 

here are the new kernel logs for all 3 settings, brcmfx-driver=2 is the only one that did not show "no wifi hardware installed".

 

the log for brcmfx-driver=2 also has the most mentions of AirportBrcmFixup.

 

I kind of wonder if spoofing(FakeID) my card as a Apple BCM943602CS(DevID: 14e4:43ba) would just make it work, it is what I have in my main hackintosh.

debug kernel log.zip

Link to comment
Share on other sites

@fallen00sniper,

 

I think it worth to try:

brcmfx-driver=0, fake IDs: 

43ba, 43a3

brcmfx-driver=1, fake IDs:

4331, 4353

brcmfx-driver=2, fake IDs:

43ba, 43a3

 

And 43a0 - it is your original device-id, and it does not work with all drivers....

And what else I would try (with your original device-id and 43ba, 43a3):

move kext /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcmNIC.kext to ~/Desktop,

set brcmfx-driver=0 and put logs here...

Edited by lvs1974
Link to comment
Share on other sites

I woke up early and tried

FakeID 0x043ba14e4

 

add properties

wifi device-id 043ba14e4 string

 

the kext still patched, without the fix up it didn’t fake anything.

 

I’m doing it wrong, can you advise how to fake the id?

 

i didn’t see the rest of your reply until I opened it on IM site and will test more when I get home.

Link to comment
Share on other sites

@lvs1974

 

Hoping this is correct, from iojones SLT1@0 > pcidebug : 07:00:00... going to have to make an educated(sort of) guess that is the pci address.

 

I can't get this to work, I get a KP when this is set. I can only guess 07:00:00 is not the pci address of this or I did it wrong since it goes to KP while loading airport stuff.

 

Untitled.png.42991b2ffaa73a2ca9e71bcf948faf4e.png

Edited by fallen00sniper
Link to comment
Share on other sites

I tried 0 and 2, I tried 43ba and 43a3 separately, if I removed fixup and used fakeid instead, it would boot with no change.

 

when it had a kp, I tried 43a0 and still had kp.

 

keepsyms wasn’t enabled.

 

I may have done something wrong, I am using clover configurator global, it set string as the value type by default.

Link to comment
Share on other sites

@fallen00sniper

 

To use fake-id feature you need arbitrary properties in clover and AirportBrcmFixup, without AirportBrcmFixup it won't work (since AirportBrcmFixup implements PCI fake-id).

And remove FakePCIID.kext (broadcom wi-fi injector) just in case if you use it (to avoid any possible conflicts).

Try to set in Arbitrary only compatible property (without device-id).

Into boot-args add keepsyms=1 and put here a panic report.

Edited by lvs1974
Link to comment
Share on other sites

 Share

×
×
  • Create New...