All Activity

Further to troubleshooting made with @robi62 here, cards that require device id injection and/or binary patching of the IO80211FamilyLegacy PlugIn AirPortBrcmNIC like BCM4352-based DW1560, a new version v2.1.9 of Acidanthera's AirportBrcmFixup is under development but not officially released yet. This new version is being updated for Sequoia. Pre-release versions are available here. Downloads are only available to people who log in with their GitHub account. Here's a copy of the latest version at time of writing: AirportBrcmFixup-2.1.9-RELEASE.zip Just add the kext to your injected kexts folder and you'll be good to go with the above OCLP process. OpenCore users only need to select the AirPortBrcmNIC injector in their config file, AirPortBrcm4360 injector being irrelevant since Big Sur.

Important note about BCM4352 cards (eg: DW1560), given that these are not supported OOB. Injection of the device id or injection of compatibility statement was always required so that it could be activated through AirPortBrcm4360 (older OS X/macOS versions up to Catalina) or AirPortBrcmNIC (Big Sur & later) kexts. In addition, a binary patch of the drivers was required to obtain operation on 5Ghz networks. Injecting the property "compatible pci14e4,43a0 STRING" only provides operation on 2,4GHz networks. In Sonoma, BCM4352 cards can be fully activated with the above process + injection of Acidanthera's AirportBrcmFixup v2.1.8. With OpenCore, only the AirportBrcmNIC injector needs to be specified for loading in the config, AirportBrcm4360 injector being irrelevant (target kext not present). The injector does exactly what its name implies: it injects the missing device id (eg: 14e4:43b1 for the DW1560) in the AirPortBrcmNIC PlugIn of IO802FamilyLegacy kext. The binary/executable module of the kext handles the binary patch required to obtain operation on 5GHz networks. For BCM4350 cards (eg: DW1820a), no changes to what was required with previous macOS versions. It's a simple matter of applying the above process is + injecting the property "compatible pci14e4,43a0 STRING". No need of AirportBrcmFixup.

Got it, so AirportBrcmFixup injects the required id into the relevant wireless kext (AirPortBrcmNIC here) and I guess the binary/executable module applies the binary patch required for 5Ghz operation. Thanks.

All kext are loaded this is a pic of my config

For the benefits of others, would you care to explain how you met success? It looks like you use what I guess is a Sequoia-specific, yet unpublished version 2.1.9 of AirportBrcmFixup.

Got it working

Never seen this KP on "watchdog" before; that's a first. Can't see any obvious mistake in your setup arrangements or config file. Nothing wrong with the patched ACPI tables or the injected kexts. So, I'd say the issue is somewhere in your OC config, maybe the quirks. I'm not too convinced by those boot args: agdpmod=vit9696 (isn't this for external GPU?) gfxfcms=1 (that's invalid, it's igfxfcms=1) and igfxdvmt (it's for Ice Lake platforms). I don't believe you need any of those at all. You would need to read the Whatevergreen documentation: https://github.com/acidanthera/WhateverGreen/tree/master https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md Regarding the properties you inject for HD530, faked KBL device id and injected KBL framebuffer layout id look Ok to me. Not so sure about the injected HDMI 2.0 properties but I can't see them do any harm. Re: quirks, a few suggestions: Booter: enable "SyncRuntimePermissions" Kernel: I think you can disable "AppleXcpmCfgLock" UEFI: not sure if you really need "RequestBootVarRouting" Kernel -> Scheme set to Fuzzy match. Do you really need this? Pretty sure you can also leave KernelArch to auto.

Thats problem! EFI.zip

So you: inject the property "compatible pci14e4,43a0 STRING" against your card's location/address in your config? block/exclude vanilla IOSkywalkFamily in your config? inject IO802FamilyLegacy + replacement IOSkywalkFamily kexts? apply OCLP "modern wireless networking*" root patching? What about AirportBrcmFixup kext? I wouldn't use it to begin with. Injecting the compatibility statement normally removes the need for it. What is showing in SysInfo->Software->Extensions as injected kexts? Can you post a new IOReg extract? Edit: Oh, I had forgotten that, for 5GHz networks, as stated in the old BCM4352 thread I linked above, DW1560 used to require to binary patch AirportBrcm4360, then AirportBrcmNIC PlugIn kexts. I guess this is most likely still required. AirportBrcmFixup used to take care of that but I don't know how things operate now with OCLP. Maybe the patcher handles it all. https://www.insanelymac.com/forum/topic/292542-airport-pcie-half-mini/ https://github.com/acidanthera/AirportBrcmFixup

Hi I adjusted card info in dp but now when I boot no wifi and no card installed

already have it and done it but still the same error comes up most rest config.plist added config.plist.zip

I really don't know how you managed to obtain working wifi considering I'm seeing a significant error in the property you inject which makes it invalid : You need to fix this and, ideally, describe the actions you took, the settings you applied. You probably got by thanks to AirportBrcmFixup which I now see injected. NB: to avoid scoring out personal info in your PrefPane screenshot, just scroll down the menu on the left before taking the shot!

hi I manage to make it work some how but only 2.4 ghz not 5??? Cannot find my 5g wifi??? I enclose ioreg MacBook 2.zip

DW1560 never was supported (OOB) with its native BCM4352 device id. See this very old thread going back to the good old days... So, you need to fake the device id of a BCM4360 chipset, i.e. inject the following additional device property in your config: compatible pci14e4,43a0 STRING If it still does not work, try injecting the following kexts in that order: AirPortBrcmNIC_Injector.kext + AirportBrcmFixup but I doubt you'd need this today. Remember that, before Apple decided to drop all the Broadcom legacy cards in Sonoma, the only remaining Broadcom cards still supported in Big Sur, Monterey and Ventura were: <key>IONameMatch</key> <array> <string>pci14e4,43ba</string> <string>pci14e4,43a3</string> <string>pci14e4,43a0</string> </array> i.e., BCM43602, BCM4350 and BCM4360 chipsets. That's all that the IO80211FamilyLegacy kext you inject supports.

Hi I use last kext amfipass which you dont need to specify it on boot args I have never had it working in Sonoma which I have too Ill post my ioreg later

-> moved to Sequoia beta section. As clearly indicated, no support requests in our Technical Info threads please. I don't understand that screenshot. Just how do you run Sequoia beta here? Or is it a screenshot of a screenshot? Did you apply OCLP 1.6.0 root patching? What did the app show in terms of patches when you ran it? Basically, if you were able to patch Sonoma for that DW1560 and obtain wireless + Bluetooth services, it's the exact same process and with the exact same parameters + add-on kexts for Sequoia beta. See this thread on the matter. I noticed in your config that you inject AMFIPass kext but that you do not use the -amfipassbeta boot arg as expected and stated in Jake's guide for Sonoma. Is that deliberate? Strange that the card shows in SysInfo but not in Hackintool. What do you see in SysInfo->Software->Extensions for the injected kexts? What about in IOReg?

Hi Im trying to make dw 1560 work in Sequoia on my hp 1030 g1 but no joy wifi does not start.. any ideas?? I attach my config file config.plist.zip

Make sure to reset NVRAM at OC Picker when you reboot after all config changes.

i tried to add that but for some reason it wont do it it goes straight to ocb starimage failed aborting and that back to selection screen even tried in boot args -no_compat_check still same

Do you boot in verbose mode (-v boot flag)? If so, where does it hang or fail? What are the last messages?

Released July 23rd, 2024. Build 24A5298h. Smooth update on Hackintosh, as usual. OCLP root patching required afterwards, as usual also. Same Clover r5159 setup for my Dell Latitude E7270 as used with initial beta3 version and posted here.

No CPU PM or incorrectly configured maybe? What are you using? Any power management SSDT in your ACPI folder? You had 2 in the EFI you previously posted ! Are they suitable for a 10th gen platform? What's in your OC config? Please make a habit of providing troubleshooting material when you ask for support.

Hi Harve Hervé, My hack is getting too hot just for using an hour only, on Windows it doesnt heat up at all, is there a FAN issue with Hackintosh.. if so, any way around to handle this. my hack : Lenovo X390, i7 10th Gen, Inetl 620 UHD, Opencore 1.0 with Sequoia MacOS

i might stop trying cant get it to boot big sur installer with the files from that tread tried multiple config plist files given there also even teh oc fix by you and jake didnt boot it bit out of luck and ideas