Contribute
Register

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

On this motherboard we should only use one of the following:
  1. OcQuirks-4.efi + FwRuntimeServices.efi (for Mojave)
    • Available from here.
  2. OcQuirks.efi + OcQuirks.plist + FwRuntimeServices.efi (for Catalina)
    • Available from ZIP file in Catalina Mini-Guide.
  3. OsxAptioFix2drv-free2000.efi (either Mojave or Catalina)
    • Available from bottom of Post #1
Items 1 and 2 are strongly recommended. Item 3 can be used if nothing else works.

SSDT-NVRAM.aml is a requirement for native NVRAM.

Hello,
I use Mojave but have option 2. installed. On the surface this seems to be working ok, although I have the issue that after installing VirtualSmc I can’t boot (I still have to do some testing). So what kind of issues can option 2. cause on Mojave?

Thanks
 
Hello,
I use Mojave but have option 2. installed. On the surface this seems to be working ok, although I have the issue that after installing VirtualSmc I can’t boot (I still have to do some testing). So what kind of issues can option 2. cause on Mojave?

Thanks
me too! I was wondering for the same question
 
Hello @ralphonz,

Have you also updated Clover to 51xx? We should update Clover and all kexts while still running Mojave in order to verify that the updates are working. After that we can perform the in-place upgrade to Catalina through System Preferences --> Software Update.

When updating Clover, be sure to check that all needed EFI drivers are in the new CLOVER/drivers/UEFI folder and that the old CLOVER/drivers64UEFI folder is deleted.

Hi, thanks for the response Casey. Yeah I'm running Clover 5103. Have been for a little while.

I just managed to get into my incredibly slow backup and edit the config.plist for my SSD Install. I removed shikigva=60 and -raddvi, added MATS to drop tables - and now I can boot into Catalina! (WEG 1.3.6 and Lilu 1.4.1) Hurray!

One issue though:
After login I'm greeted with some crazy black lines across one monitor (connected to HDMI) and the other (connected to USB-C/Displayport) flashing between completely black and crazy-lines! This behaviour stops if I either disconnect the HDMI monitor and plug it back in, or if I sleep then wake again - This wasn't the case with Mojave.

I'm not sure what the best solution is for here, any advice would be appreciated.
 
Alright, it's debug time!

@edunon, I've attached a debug-version of the EFIClone script to this post. If you'd be so kind as to run this modified version directly via the terminal and upload both the EFIClone.log file as well as the entire output from the Terminal itself.
I have castrated this version such that it will never, under any circumstances, actually touch any of your files on disk, so it is safe to run it.

You can run the script by directly referencing it like so:
Code:
sudo /Users/<your_username>/Downloads/EFIClone-v4-DEBUG.sh / "/Volumes/Mac OS BK" 0 ""
I've grabbed the name of your backup volume from the original log file. If this is not correct, please adjust it to the one you actually want. Otherwise, simply run the script.
Also, please fill in the actual username of your account on this machine where I've indicated the placeholder.

Additionally, please provide the output of the following two commands:
Code:
diskutil list

Code:
diskutil apfs list

Thank you very much @CaseySJ and @byteminer for your fast reply and action!
I've run the script you sent and the result is attached to this post as well as the output from the two diskutil commands.
I didn't get any EFIClone.log from the debug script.

I'm using a NVME drive as Boot drive, an SSD as Home folder, two HDDs set as Raid1 and another HDD.
The backup drive I use has 3 partitions to accommodate the Boot, Home and Raid1 backups.

Thanks again for your help!
 

Attachments

  • Screenshot 2020-02-28 at 15.32.08.png
    Screenshot 2020-02-28 at 15.32.08.png
    63.3 KB · Views: 80
  • Screenshot 2020-02-28 at 15.35.47.png
    Screenshot 2020-02-28 at 15.35.47.png
    292.3 KB · Views: 69
  • Screenshot 2020-02-28 at 15.40.28.png
    Screenshot 2020-02-28 at 15.40.28.png
    478.1 KB · Views: 79
Hi, thanks for the response Casey. Yeah I'm running Clover 5103. Have been for a little while.

I just managed to get into my incredibly slow backup and edit the config.plist for my SSD Install. I removed shikigva=60 and -raddvi, added MATS to drop tables - and now I can boot into Catalina! (WEG 1.3.6 and Lilu 1.4.1) Hurray!

One issue though:
After login I'm greeted with some crazy black lines across one monitor (connected to HDMI) and the other (connected to USB-C/Displayport) flashing between completely black and crazy-lines! This behaviour stops if I either disconnect the HDMI monitor and plug it back in, or if I sleep then wake again - This wasn't the case with Mojave.

I'm not sure what the best solution is for here, any advice would be appreciated.
Regarding the video weirdness:
  • What are the makes/models of the two monitors?
  • If the same monitors worked normally under Mojave, has anything changed in the frame buffer settings located here:
    • Clover Configurator --> Devices --> Properties --> PciRoot(0x0)/Pci(0x2,0x0)
 
Thank you very much @CaseySJ and @byteminer for your fast reply and action!
I've run the script you sent and the result is attached to this post as well as the output from the two diskutil commands.
I didn't get any EFIClone.log from the debug script.

I'm using a NVME drive as Boot drive, an SSD as Home folder, two HDDs set as Raid1 and another HDD.
The backup drive I use has 3 partitions to accommodate the Boot, Home and Raid1 backups.

Thanks again for your help!

The debug script positions its log file in /Users/Shared/EFIClone.log, so maybe check there.
Additionally, it would be extremely beneficial if you'd be able to supply the entirety of the terminal output as a text file.
 
I have to check but I think I'm using the items 2 for Mojave... without any problem
Hello,
I use Mojave but have option 2. installed. On the surface this seems to be working ok, although I have the issue that after installing VirtualSmc I can’t boot (I still have to do some testing). So what kind of issues can option 2. cause on Mojave?

Thanks
me too! I was wondering for the same question
It's okay to use Option 2 on either Catalina or Mojave, so I've updated the post accordingly. Some folks have reported problems with Option 2 on Mojave. If Option 2 works under Mojave, it's perfectly okay to keep using it.
 
OK thank you, in the meantime I'm reinstalling studio one with SIP enabled to see if it stop to crash at startup...
Please backup your existing CLOVER folder and try the modified one attached here. Copy serial numbers back into SMBIOS prior to use. No guarantees this will fix all issues, but it should be a step in the right direction. Also, I've replaced OsxAptioFix2Drv-free2000.efi with OcQuirks-4.efi and FwRuntimeServices.efi. Should you encounter the dreaded Couldn't allocate runtime area error upon boot (or the no-entry symbol), please perform a CMOS Reset according to the Designare Owner's Manual then configure BIOS parameters again and finally boot back into macOS.
 

Attachments

  • CLOVER.zip
    7.4 MB · Views: 70
The debug script positions its log file in /Users/Shared/EFIClone.log, so maybe check there.
Additionally, it would be extremely beneficial if you'd be able to supply the entirety of the terminal output as a text file.

Got it, Thanks! I've edited the username as it was my full name.

Edit: Forgot to add the terminal output as a text file.
 

Attachments

  • EFIClone.log.zip
    591 bytes · Views: 69
  • TerminalOutput.zip
    3 KB · Views: 57
Last edited:
Back
Top