Contribute
Register

Z690 Chipset Motherboards and Alder Lake CPU

Backup your EFI folder and run it.

So far, so good.

Also, could you maybe update/populate the options for the list boxes in the Build Signature form webpage:

1. For Z690 chipset - add Manufacturer and Board options, add CPU option for 12700K

And slightly off-topic - while you are there:

2. For Z370 chipset - add Board option for my Prime Z370M Plus II (not TUF - might interest OPs with this board).

TIA
 
Last edited:
Hello @CaseySJ
Hoping you can help me out, or anyone else on here.

When I first mounted my EFI and updated/saved my config.plist in OCC 0.8.1 I got the error message: OC: Driver ResetNvramEntry.efi at 7 cannot be found! Halting on critical error. Doing a quick Google search this was due to having options selected in OCC/config but not having the drivers in the actual folder.

So I checked and noted I had two discrepancies; ResetNvramEntry.efi and ToggleSipEntry.efi. I added those from the OCC drivers folder for 0.8.1 from dortania.

I then tried to boot from it on my new pc again and got this error- BEP: Invalid revision 2 (!=1) in loaded driver. Halting on critical error.

Is there something I have setup incorrectly? How would I go about checking? I was not able to find much online on this specific error message.
I'm having this error currently how did u fix it
 
Please attach your EFI folder (without OC/config.plist/Platforminfo/Generic info) and OC version (0.8.3?)
so i have 2 and i named them, one works but not really the other that i made fresh doesn't boot and gives me BEP: Invalid revision 2 (!=1) in loaded driver.Halting on critical error. i checked the drivers in folders and and bunch of other things

the other that does work and boots but has some sort of panic and restarts after login. i start getting mds store and mds worker going crazy in the task manager.

let me know what u find
 

Attachments

  • EFI that ive built from scratch but it doesnt boot.zip
    36.6 MB · Views: 24
  • EFI that works but glitches and restarts.zip
    44.5 MB · Views: 23
let me know what u find
As before, these EFi folders seem to be mixture of OC 0.8.0 plus some newer kexts.

Suggest you check out the attached Debug version of a OC 0.8.3 EFI folder from a repo on Github for Alder Lake:

This EFI loads fine on systems like yours:

Prime Z690-P Wi-Fi
Comet Alder Lake CPU
Radeon RX 580, RX 6000

For App Store, iMessage, etc., you will need to add your MLB, ROM (copy MAC address in Network/Ethernet/Hardware and remove all ":") plus SystemSerialNumber and SystemUUID. Note that the SystemProductName is set for MacPro7,1 and the RestrictEvents kext (memory issues) is included under OC/kexts.

Install this EFI folder in the EFI partition of your Monterey drive and check it out. From there you can upgrade to Monterey 12.6, etc.

One last thing - be sure you are booting this EFI - restart -> Delete -> BIOS EZ Mode - Boot Menu -> select correct UEFI drive, etc.

let us know how it goes...
 

Attachments

  • EFI.zip
    12 MB · Views: 63
Last edited:
Please attach your EFI folder (without OC/config.plist/Platforminfo/Generic info) and indicate OC version (0.8.3?)

As before, these EFi folders seem to be mixture of OC 0.8.0 plus some newer kexts.

Suggest you check out the attached Debug version of a OC 0.8.3 EFI folder from a repo on Github for Alder Lake:

This EFI loads fine on systems like yours:

Prime Z690-P Wi-Fi
Comet Alder Lake CPU
Radeon RX 580, RX 6000

For App Store, iMessage, etc., you will need to add your MLB, ROM (copy MAC address in Network/Ethernet/Hardware and remove all ":") plus SystemSerialNumber and SystemUUID. Note that the SystemProductName is set for MacPro7,1 and the RestrictEvents kext (memory issues) is included under OC/kexts.

Install this EFI in the EFI folder of your Monterey drive and check it out. From there you can upgrade to Monterey 12.6, etc.

One last thing - be sure you are booting this EFI - restart -> Delete -> BIOS EZ Mode - Boot Menu -> select correct UEFI drive, etc.

let us know how it goes...
Um yeah I tried your file and filled in the platform info in the EFI you provided and it did a preboot before the apple boot that I've never seen before the code kept running and at the line that I assumed to the towards the end before login it gave me the apple lock. How much more configing do I have to do to that EFI file.

Are you telling me to remove the restrictevents kext? Is there a problem with using Mac pro 7.1 info?

I also noticed on previous EFI that worked the rom/mlb info was Missing and when I filled it in I didn't get any error messages on boot it did boot and then restarted immediately on login. I feel like I got closer with the last one
 
Are you telling me to remove the restrictevents kext? Is there a problem with using Mac pro 7.1 info?

No. The restrictevents kext is required for SMBIOS = Macpro7,1 - this SMBIOS seems to work fine for Alder Lake.

As mentioned, the PlatformInfo/Generic info is required for App Store, etc. System will boot without it.
 
How much more configing do I have to do to that EFI file.

No further configuration is needed unless you want to switch off the debug code.

The EFI folder (not a file) is configured for debugging that displays the code indicating any errors.

If the code runs cleanly you can expect to see the Apple logo then the progress bar and then a login.

If you don't have macOS installed then you'll see a menu with Restore, Install, Safari, Disk Utility.
 
Last edited:
If the code runs cleanly you can expect to see the Apple logo then the progress bar and then a login.

Using the Debug EFI (post #2,537 above) expect 3 - 5 seconds delay between the Apple logo and the progress bar.

If you don't have macOS installed then you'll see a menu with Restore, Install, Safari, Disk Utility.

Installing Monterey 12.4 requires many reboots before the Setup screen - be patient, it's working fine:

1664769845583.jpeg
 
Last edited:
Back
Top