Contribute
Register

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

** OpenCore 0.7.3 EFI for Designare Z390 **
Supports Mojave, Catalina, Big Sur, and Monterey
Please do not quote this post in its entirely. Use a link instead.


Update 9 Sep 2021:
HackinDROM 2.0.0 Beta (click here) can be used to update to OpenCore 0.7.3.



** NOTE **
Mojave and Catalina Users: Please see "Post-Update Procedure" below.


If making manual changes to OpenCore config.plist, please ensure that OpenCore Configurator is set to 0.7.3 Release Version (do not use OpenCore Configurator 2.48.1.0 or earlier)​


This update includes:

1. OpenCore 0.7.3
2. VirtualSMC 1.2.7
3. AppleALC 1.6.4
4. Lilu 1.5.6
5. WhateverGreen 1.5.3
6. RestrictEvents 1.0.4
7. CpuTscSync 1.0.4 (to see if it helps avoid crashes from certain wake-from-sleep scenarios)

Changes to config.plist:
  • Support for AppleVTD:
    • Enabling AppleVTD allows greater number of Thunderbolt devices to connect, including (a) Antelope Audio Devices, (b) Apple Thunderbolt-to-Gigabit Ethernet adapter, etc.
    • DisableIoMapper kernel quirk has been disabled.
    • Standard DMAR table is being deleted and replaced with modified DMAR.
  • Your Action: You can still choose to enable to disable AppleVTD by following the steps in this post.
  • UEFI --> Drivers format has changed from simple array to dict. Please do not use OpenCore Configurator 2.48.1.0 or earlier as it will corrupt the config.plist.
  • PlatformInfo --> UpdateSMBIOSMode has been changed from Create to Custom. Additionally, kernel quirk CustomSMBIOSGuid has been enabled. This allows Windows to use the computer name you specified. Thanks to @Ploddles for the tip.
Reminder:
  • Radeon VII users must disable boot argument agdpmod=pikera. Vega users may need to do the same.
If using OpenCore Configurator, please ensure it is set to 0.7.3 Release Version (not 0.7.3 Development Version).


WARNING: Until OpenCore Configurator 2.48.2.0 is released, we can only use a Plist Editor or text editor such as BBEdit and follow the procedure below:
  1. Download the ZIP file
  2. It will downloaded into a folder called OC-073-DESIGNARE-Z390
    • Rename this top level folder to EFI
  3. Choose appropriate config.plist as follows:
    • If using AMD GPU, rename config-AMD-GPU.plist to config.plist
    • If you do not have a discrete GPU, rename config-Intel-iGPU.plist to config.plist
  4. Edit the new config.plist in a Plist Editor or text editor such as BBEdit
  5. Open your current config.plist in the same editor
  6. Copy the selected section from current config.plist and paste it into new config.plist
    Screen Shot 2021-09-07 at 7.44.11 AM.png
  7. Save the new config.plist
  8. WARNING: If you have customized your config.plist, it may be best to wait until OpenCore Configurator 2.48.2.0 or newer is released that supports 0.7.3 Release Version (not 0.7.3 Development Version)
  9. Copy the new EFI folder to the EFI partition of a USB flash drive
  10. Boot the system from the USB flash drive by pressing F12 at Gigabyte Splash Screen and selecting the USB flash disk
  11. When OpenCore Picker GUI appears, check that bottom right corner says REL-073-...
  12. If macOS boots and runs properly, then copy the new EFI folder to the EFI partition of the internal macOS SSD


For manual update purposes, the ZIP files are attached below.
  • File on left is for Broadcom WiFi/BT (5.8 MB).
  • File on right is for Intel WiFi/BT (65.5 MB).


Post-Update Procedure: Mojave and Catalina users only.
  • If you're using OpenIntelWireless drivers for WiFi and BT, please change Misc --> Security --> SecureBootModel --> j137 otherwise Catalina will not boot


Updates:
  • 7 Sept 2021: First version
 

Attachments

  • OC-073-DESIGNARE-Z390.zip
    5.8 MB · Views: 281
  • OC-073-DESIGNARE-Z390-INTEL-WIRELESS.zip
    65.5 MB · Views: 259
Last edited:
I saw no boot arguments for RestrictEvents in your Z390 AMD EFI/OC/config.plist file. Will it be the same for my Asus Z370 and Asus ProArt Z490 Creator systems?

BTW, will your EFI AMD work for me with the my Asus Z370? I ask because I want to reduce my time updating when you generously provide your EFIs.
 
I saw no boot arguments for RestrictEvents in your Z390 AMD EFI/OC/config.plist file. Will it be the same for my Asus Z370 and Asus ProArt Z490 Creator systems?
I have included RestrictEvents, but not enabled it. It's used for two purposes:
  • To prevent spurious memory and other notifications with SMBIOS MacPro7,1
  • To change CPU name in About this Mac
    • Boot arguments are primarily for changing CPU name
    • We could never get this to work before, but I may try again because they've finally improved the documentation
BTW, will your EFI AMD work for me with the my Asus Z370? I ask because I want to reduce my time updating when you generously provide your EFIs.
My EFI folder most likely won't work on Asus Z370, but...
  • A new version of OpenCore Configurator should be available tomorrow or day after. That should greatly simplify the update process.
  • In the meantime if you have an EFI folder that needs to be upgraded to OpenCore 0.7.3, feel free to let me know. PM might be best.
 
I have included RestrictEvents, but not enabled it. It's used for two purposes:
  • To prevent spurious memory and other notifications with SMBIOS MacPro7,1
  • To change CPU name in About this Mac
    • Boot arguments are primarily for changing CPU name
    • We could never get this to work before, but I may try again because they've finally improved the documentation

My EFI folder most likely won't work on Asus Z370, but...
  • A new version of OpenCore Configurator should be available tomorrow or day after. That should greatly simplify the update process.
  • In the meantime if you have an EFI folder that needs to be upgraded to OpenCore 0.7.3, feel free to let me know. PM might be best.
I did get it to work in the past, but had to use nvram args, not boot-args to rename. I'm not even sure how you'd do the rename with boot-args since any way I could think of to escape the spaces didn't work.
 
Hi @CaseySJ,
some time ago I installed on my Gigabyte Z390 Designare based system macOS Big Sur following Your Guide in a multiboot configuration on separate disks. So I would like to ask a few questions:
- after installation, the APFS volume dedicated to Big Sur on the system drive is represented as in the image:
Schermata 2021-09-08 alle 15.24.47.png

Is this OK?
- Using the installation pendrive to start the system, the OpenCore menu at reboot kept the memory of the last system booted while now, after removing the previous Clover EFI folder from the EFI partition and copying the OpenCore EFI folder, the OpenCore menu no longer holds the memory of the last booted system. I tried using ResetNVRAM but it didn't fix the problem.
Is a solution possible for this problem?
- With the update to the latest version of OpenCore (0.7.3) following Your guide will it still be possible to manage both macOS Catalina and macOS Big Sur on my system disk as it is currently?
Thanks in advance for your help?
 
I did get it to work in the past, but had to use nvram args, not boot-args to rename. I'm not even sure how you'd do the rename with boot-args since any way I could think of to escape the spaces didn't work.
We were using the terms “boot args” and “nvram” interchangeably. Not technically prudent or accurate, but space efficient. ;) The point being that RestrictEvents can be used to change CPU name for both AMD and Intel processors — irrespective of the exact manner in which that’s done.
 
** OpenCore 0.7.3 EFI for Designare Z390 **
Supports Mojave, Catalina, Big Sur, and Monterey
Please do not quote this post in its entirely. Use a link instead.


** NOTE **
Mojave and Catalina Users: Please see "Post-Update Procedure" below.

Possibly jumping the gun here, but is this still planned to be uploaded to hackindrom? Looks like this isn't available yet.

Screenshot 2021-09-08 at 17.56.19.png

Screenshot 2021-09-08 at 17.59.18.png
 
Possibly jumping the gun here, but is this still planned to be uploaded to hackindrom? Looks like this isn't available yet.

View attachment 528547
View attachment 528546
Oh yes, the elephant in the room -- or rather the elephant absent from the room! :)

OpenCore's config.plist is an XML file with a specific "schema" or syntax. For EFI drivers located in the OC/Drivers folder, the schema or syntax changed in a significant way from 0.7.2 to 0.7.3.

This is why OpenCore Configurator 2.48.1.0 is not compatible and we must wait until an update is released.

This is also why I believe HackinDROM is not compatible and will corrupt the config.plist until it too is updated.

@Inqnuam, are you aware of the change made to UEFI drivers section in OpenCore 0.7.3? That section in config.plist now uses dict array instead of a simple array.

Screen Shot 2021-09-08 at 10.23.03 AM.png
Screen Shot 2021-09-08 at 10.23.06 AM.png
 
Last edited:
Hi @CaseySJ,
some time ago I installed on my Gigabyte Z390 Designare based system macOS Big Sur following Your Guide in a multiboot configuration on separate disks. So I would like to ask a few questions:
- after installation, the APFS volume dedicated to Big Sur on the system drive is represented as in the image:
View attachment 528536
Is this OK?
- Using the installation pendrive to start the system, the OpenCore menu at reboot kept the memory of the last system booted while now, after removing the previous Clover EFI folder from the EFI partition and copying the OpenCore EFI folder, the OpenCore menu no longer holds the memory of the last booted system. I tried using ResetNVRAM but it didn't fix the problem.
Is a solution possible for this problem?
- With the update to the latest version of OpenCore (0.7.3) following Your guide will it still be possible to manage both macOS Catalina and macOS Big Sur on my system disk as it is currently?
Thanks in advance for your help?
Hello @SardusX,

With OpenCore we have 2 ways to specify the default boot volume:
  • Easy Way:
    • At the OpenCore GUI (called OpenCanopy), press and hold CTRL key when clicking the disk you want to boot. That disk becomes the new default.
  • Alternative Way:
    • In macOS we can do this: System Preferences --> Startup Disk --> select the new startup disk
Here are some more tips for OpenCanopy:
 
Oh yes, the elephant in the room -- or rather the elephant absent from the room! :)

OpenCore's config.plist is an XML file with a specific "schema" or syntax. For EFI drivers located in the OC/Drivers folder, the schema or syntax changed in a significant way from 0.7.2 to 0.7.3.

This is why OpenCore Configurator 2.48.1.0 is not compatible and we must wait until an update is released.

This is also why I believe HackinDROM is not compatible and will corrupt the config.plist until it too is updated.

@Inqnuam, are you aware of the change made to UEFI drivers section in OpenCore 0.7.3? That section in config.plist now uses dict array instead of a simple array.
We can safely Update its all ok
But I dont think Reinstall OC will work properly, it will maybe crash the app


GUI issue crashs the app after you have uploaded latest plists.
Will release a fix soon, a cup coffee is needed
 
Last edited:
Back
Top