fallen00sniper Posted October 22, 2018 Share Posted October 22, 2018 (edited) @vit9696 I'm using this kext to try and get my card working, but I keep getting the dreaded turn wifi on button. my card id is 14e4,43a0 and it is a Asus pce-ac66, it has worked previously under Sierra. @Pavo and I have been trying all day to get this card to work, but it continues to not work. Attaching a kernel log. kernel_log.txt.zip Edited October 22, 2018 by fallen00sniper Link to comment Share on other sites More sharing options...
LockDown Posted October 22, 2018 Share Posted October 22, 2018 (edited) oopss i deleted my reply hahahaha... @lvs1974 i think airportbrmfixup is missing some patches for HighSierra. if i use, sherlocks's kextstopatch, it works fine. but i have to change the target kext from: com.apple.driver.AirPort.BrcmNIC-MFG to: com.apple.driver.AirPort.BrcmNIC Edited October 22, 2018 by ellaosx Link to comment Share on other sites More sharing options...
lvs1974 Posted October 22, 2018 Share Posted October 22, 2018 Hi, To investigate an issue I need a kernel log from osx running with debug-version of AirportBrcmFixup.kext and boot-arg -brcmfxdbg. BTW: 14e4,43a0 - is a natively supported wi-fi card, why do you need to use AirportBrcmFixup.kext? 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 1 Link to comment Share on other sites More sharing options...
LockDown Posted October 22, 2018 Share Posted October 22, 2018 (edited) intermittent drop. i think it has something to do with one of the patches in kextstopatch that fixes it. ( the iovar patch) Edited October 22, 2018 by ellaosx Link to comment Share on other sites More sharing options...
fallen00sniper Posted October 23, 2018 Author Share Posted October 23, 2018 (edited) 15 hours ago, lvs1974 said: Hi, To investigate an issue I need a kernel log from osx running with debug-version of AirportBrcmFixup.kext and boot-arg -brcmfxdbg. BTW: 14e4,43a0 - is a natively supported wi-fi card, why do you need to use AirportBrcmFixup.kext? 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 @lvs1974 I attached the kernel log in the original post did not have the debug version in... so i'll swap it out and upload a new log, this is for mojave and though it may be natively supported this is a asus pce-ac66 card. It has always needed patches to get wifi to work, the kexts load and i get stuck with an indefinite holo wifi icon and cannot "turn wifi on". Others had this issue on Sierra as well, the only way to get it working was a whitelist patch, setting country code for 5Ghz and fake id of a airport extreme card, which AirPortBrcmFixUp does fake the card. Mojave shows in AirPortBrcm4360.kext>info.plist only shows 2 pci14e4,xxxx id's and mine is in AirPortBrcmNIC or AirPortBrcmNIC-MFG kext. Though as I said, it does not work as expected, the moment it scans for wifi macOS disables it with turn wifi on and holo icon with or without the fixup kext, though without fixup shows as unsupported wifi module. kernel_log.txt.zip Edited October 23, 2018 by fallen00sniper added kernel log with debug kext. Link to comment Share on other sites More sharing options...
LockDown Posted October 23, 2018 Share Posted October 23, 2018 @lvs1974 does AirportBrcmFixup includes Sherlocks's iovar patch for AirPort.BrcmNIC & AirPortBrcmNIC-MFG? Link to comment Share on other sites More sharing options...
lvs1974 Posted October 23, 2018 Share Posted October 23, 2018 (edited) @ellaosx, no, it does not. More over, AirportBrcmFixup blocks loading of AirPortBrcmNIC-MFG (it is a bad driver, Bluetooth Handoff doesn't work). @Sherlocks, could you explain what is iovar patch doing, what methods are patched. Usually I don't use binary patches, I am trying to implement them in a different way. And I need to understand the purpose of patch. Edited October 23, 2018 by lvs1974 1 Link to comment Share on other sites More sharing options...
lvs1974 Posted October 23, 2018 Share Posted October 23, 2018 @fallen00sniper, according to your last kernel log AirportBrcmFixup is not loaded at all... I don't see any lines containing "BRCMFX". You can check whether is is loaded in terminal: kextstat | grep -i fixup Link to comment Share on other sites More sharing options...
LockDown Posted October 23, 2018 Share Posted October 23, 2018 @fallen00sniper are you experiencing the intermittent drop before it goes to the wifi ON button? Link to comment Share on other sites More sharing options...
LockDown Posted October 23, 2018 Share Posted October 23, 2018 4 hours ago, lvs1974 said: @ellaosxAirportBrcmFixup blocks loading of AirPortBrcmNIC-MFG (it is a bad driver, Oh ok. so what about AirportBrcmNIC, does it block too? if it does, then are you saying that we need to use fakeid/dsdt and use one of supported id that is found in AirportBrm4360 (even i dont use handoff)? Link to comment Share on other sites More sharing options...
lvs1974 Posted October 23, 2018 Share Posted October 23, 2018 AirportBrcmFixup blocks only AirPortBrcmNIC-MFG. Link to comment Share on other sites More sharing options...
LockDown Posted October 23, 2018 Share Posted October 23, 2018 thats good i can't send you the debug log until friday though. i hope @fallen00sniper can resend a proper one, as we have similar issue. Link to comment Share on other sites More sharing options...
fallen00sniper Posted October 23, 2018 Author Share Posted October 23, 2018 (edited) 17 hours ago, lvs1974 said: @fallen00sniper, according to your last kernel log AirportBrcmFixup is not loaded at all... I don't see any lines containing "BRCMFX". You can check whether is is loaded in terminal: kextstat | grep -i fixup The debug kext is in my clover kexts folder, when I get home I’ll run kext stat. @lvs1974 zip attached below and included system information window. this is a clean Mojave install, no upgrade/updates. 17 hours ago, ellaosx said: @fallen00sniper are you experiencing the intermittent drop before it goes to the wifi ON button? No, mine goes either directly to that problem or when I click on the finder bar icon to connect to a access point, it starts to scan and then goes to the hollow icon with turn WiFi on. kernel_log-kextstat.zip Edited October 23, 2018 by fallen00sniper attached file Link to comment Share on other sites More sharing options...
lvs1974 Posted October 24, 2018 Share Posted October 24, 2018 (edited) @fallen00sniper, I don't see any signs of AirportBrcmFixup in the latest kernel log, did you add "-brcmfxdbg" into boot-arg? Edited October 24, 2018 by lvs1974 Link to comment Share on other sites More sharing options...
fallen00sniper Posted October 24, 2018 Author Share Posted October 24, 2018 @lvs1974 no, no fix up boot args being used. just the kext once @Pavo noticed it not loading properly. Link to comment Share on other sites More sharing options...
LockDown Posted October 25, 2018 Share Posted October 25, 2018 (edited) @fallen00sniper @lvs1974 is asking you to boot with "-brcmfxdbg" and save the log, he is the dev of AirportBrcmFixup. download AirportBrcmfixup again and put it either in OTHERS or /L/E until it shows up in kextstat, then grab the log. Edited October 25, 2018 by ellaosx Link to comment Share on other sites More sharing options...
fallen00sniper Posted October 25, 2018 Author Share Posted October 25, 2018 @lvs1974 @ellaosx didn't know it needed that. the kext has been showing up in kextstat, but not in the kernel log as loaded or properly loaded? any how, thanks and here is the new log and the terminal showing the kext is loaded. kernel_log.zip Link to comment Share on other sites More sharing options...
LockDown Posted October 25, 2018 Share Posted October 25, 2018 (edited) @fallen00sniper BRCMFX is now in the log. also make sure you dont have anything related to airportbrcm in your config's kextstopatch Edited October 25, 2018 by ellaosx Link to comment Share on other sites More sharing options...
fallen00sniper Posted October 25, 2018 Author Share Posted October 25, 2018 @ellaosx only thing there is port limit patch @Pavo made. 1 Link to comment Share on other sites More sharing options...
LockDown Posted October 25, 2018 Share Posted October 25, 2018 @lvs1974, question... On 10/23/2018 at 6:43 PM, lvs1974 said: AirportBrcmFixup blocks only AirPortBrcmNIC-MFG. why the need to block it? I mean, AirPortBrcmNIC & AirPortBrcmNIC-MFG has the same supported ID's , but AirPortBrcmNIC has precedence over AirPortBrcmNIC-MFG because it has higher IOProbeScore Link to comment Share on other sites More sharing options...
lvs1974 Posted October 25, 2018 Share Posted October 25, 2018 36 minutes ago, ellaosx said: @lvs1974, question... why the need to block it? I mean, AirPortBrcmNIC & AirPortBrcmNIC-MFG has the same supported ID's , but AirPortBrcmNIC has precedence over AirPortBrcmNIC-MFG because it has higher IOProbeScore Since bluetooth Handoff doesn't work with AirPortBrcmNIC-MFG. It is still experimental version... Lower IOProbeScore does not always prevent kext loading, I saw system where AirPortBrcmNIC or AirPortBrcmNIC-MFG were loaded randomly. 1 Link to comment Share on other sites More sharing options...
lvs1974 Posted October 25, 2018 Share Posted October 25, 2018 2 hours ago, fallen00sniper said: @lvs1974 @ellaosx didn't know it needed that. the kext has been showing up in kextstat, but not in the kernel log as loaded or properly loaded? any how, thanks and here is the new log and the terminal showing the kext is loaded. kernel_log.zip I see now, and everything looks fine, AirportBrcmFixup callbacks were called (wlc_set_countrycode_rev, newVendorString. start in AirPort_BrcmNIC). May be some patches are missing in AirportBrcmFixup, but in my system this kext works perfectly with 10.13.6 and 10.14.1 (0x43b1). Some functionality in AirPortBrcmNIC depends on device-id. @Sherlocks, could you describe all required patches for 10.13 and 10.14 in details? 1 Link to comment Share on other sites More sharing options...
Sherlocks Posted October 25, 2018 Share Posted October 25, 2018 I see now, and everything looks fine, AirportBrcmFixup callbacks were called (wlc_set_countrycode_rev, newVendorString. start in AirPort_BrcmNIC). May be some patches are missing in AirportBrcmFixup, but in my system this kext works perfectly with 10.13.6 and 10.14.1 (0x43b1). Some functionality in AirPortBrcmNIC depends on device-id. [mention=980913]Sherlocks[/mention], could you describe all required patches for 10.13 and 10.14 in details?hi. what is patch? i discontinued research of patches since i use your kext. i don't have a issue.나의 LG-F800S 의 Tapatalk에서 보냄 Since bluetooth Handoff doesn't work with AirPortBrcmNIC-MFG. It is still experimental version... Lower IOProbeScore does not always prevent kext loading, I saw system where AirPortBrcmNIC or AirPortBrcmNIC-MFG were loaded randomly.what is best kext for handoff?나의 LG-F800S 의 Tapatalk에서 보냄 Link to comment Share on other sites More sharing options...
lvs1974 Posted October 25, 2018 Share Posted October 25, 2018 @Sherlocks, what is power state problem (iovar)? What do these patches: 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 15 minutes ago, Sherlocks said: what is best kext for handoff? AirPortBrcmNIC 1 Link to comment Share on other sites More sharing options...
LockDown Posted October 25, 2018 Share Posted October 25, 2018 (edited) @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. Edited October 25, 2018 by ellaosx Link to comment Share on other sites More sharing options...
Recommended Posts