Contribute
Register

Z690 Chipset Motherboards and Alder Lake CPU

Anyone replaced their Alder Lake MB built in M.2 WiFi with a bcm94360ng? I have tried this on both Alder Lake systems Gigabyte z690i and Asus Z690 DDR5 Strix e. It works just fine but on occasional wake from sleep Bluetooth will go up to 100% CPU usage. When this happens my Bluetooth function (continuity, etc.) stops working. I just have to do kill Bluetooth then it will work again.
For now I am just using sleep watcher app to just kill Bluetooth on wake and it seems to work well enough but would be nice to know what the root cause is.
I'm using bcm94360ng in my Asus ProArt Creator board. I haven't noticed any problems coming out of sleep. I'm not using any kexts.
 
Right. It looks like you're not seeing the drives or installer. Have you formatted the USB key correctly? What system are you using to build the EFI - macOS or Windows? The EFI partition of the USB stick has to be in GUID partition format, ideally using macOS HFS format.


Hello,

So I redownloaded Monterrey 11.3.1 and recreated a USB key with OPENCORE. But with your EFI Middlemen I come across this image.

PXL_20220423_013421693.jpg


But if i put my EFI, I boot on screen for choose Install Monterrey.

I have formatted the USB key with MacOs HFS format and GUI partition. I build the EFI with macOS.

Thank you very much.
 
Hello,

So I redownloaded Monterrey 11.3.1 and recreated a USB key with OPENCORE. But with your EFI Middlemen I come across this image.

View attachment 546440

But if i put my EFI, I boot on screen for choose Install Monterrey.

I have formatted the USB key with MacOs HFS format and GUI partition. I build the EFI with macOS.

Thank you very much.
I think your original EFI was the way to go, you just needed to add your Kext to your EFI. Once you're up and running you can compare EFI's.
 
I think your original EFI was the way to go, you just needed to add your Kext to your EFI. Once you're up and running you can compare EFI's.

Unfortunately even with the original EFI and the two kext CPUs, I still have the same problem...
Attached is the EFI and the KP.... I despair... long gone are the good times of a little UNIBEAST and then MULTIBEAST...:cry:
 

Attachments

  • EFI.zip
    4.1 MB · Views: 57
  • opencore-2022-04-23-153848.txt
    256 KB · Views: 23
Hello,

So I redownloaded Monterrey 11.3.1 and recreated a USB key with OPENCORE. But with your EFI Middlemen I come across this image.

View attachment 546440

But if i put my EFI, I boot on screen for choose Install Monterrey.

I have formatted the USB key with MacOs HFS format and GUI partition. I build the EFI with macOS.

Thank you very much.
Okay then. At this screen, did you select ResetNVRAM? (which is the icon right at the end on the right?).
That is the tool needed to be used whenever you make changes to the config.plist, or change the version of bootloader. This is especially apparent if you are moving over from Clover to Opencore. It may be because you've not used it hence it comes up with this error (as it normally should see it).I know because I checked the EFI I sent you - and nothing seems to be wrong with it.

Another thing to make sure is that you have the correct directories placed on the drive.
Inside the EFI partition, only one EFI folder should remain, and within that, only the BOOT and OC folders should exist ie. EFI/BOOT & EFI/OC.

Let us know if it works.
 
Unfortunately even with the original EFI and the two kext CPUs, I still have the same problem...
Attached is the EFI and the KP.... I despair... long gone are the good times of a little UNIBEAST and then MULTIBEAST...:cry:
In the EFI can you check off these and try again.

@Middleman is right as well, double check your EFI structure.

Screen Shot 2022-04-23 at 9.58.26 AM.png
 
Unfortunately even with the original EFI and the two kext CPUs, I still have the same problem...
Attached is the EFI and the KP.... I despair... long gone are the good times of a little UNIBEAST and then MULTIBEAST...:cry:
Okay I've just refreshed some files in the EFI I provided. Looks like it was an older version of OpenCanopy.efi that was in the OC/Drivers folder (plus some others) that was maybe causing the icons glitch. It should work now.
 

Attachments

  • EFI for Z690 Monterey v2.zip
    31.8 MB · Views: 40
Make sure you're using SSDT-PLUG-ALT in Alder Lake. Also a note about XHCIPortLimit--it can cause problems on this platform. I suggest using USBInjectall.kext (updated version in CaseySJ's GitHub) until you're booted. Leave all other USB kext/ssdt's alone until then.
I have followed this thread since the beginning so i know about SSDT PLUG ALT and the new way of naming cores as devices; machine boots and performs fine, and the USB map works on Monterey.

I only have issues enabling USB 3 on MOJAVE

With XHCIPORTLIMIT quirk enabled all ports work but usb2 speed.

I used usbinjectall 0.7.8 from daliansky actually

I have to test with USB LEGACY kext now, it's not documented that much but i think i can make it. Having Mojave to run 32bit apps and old but still capable audio cards that use old drivers and control panels is very useful. Apart from the USB 3 issue, the cpuid change was the only change needed
 
Last edited:
Back
Top