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

[jiffyslot]

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

@CaseySJ Ok, education time for me. So in the EFI we have a disabled SAT0>SATA and in the DSDT.aml I can search for SATA. The questions I have are: Do you pull your system DSDT via whatever method you like (Maciasl I assume) and do a find/replace? If not, did you enable the name change in the...

www.tonymacx86.com

Okay, the procedure for the edit went fine, but the USB stick won't boot via F12. Every time I select it, the screen goes dark for a moment and goes back to the F12 boot-option page.

 

[CaseySJ]

Thanks @CaseySJ. I assume this is 0.5.4 compiled by yourself?

Please see the 7th bullet.

I’m not yet sold on OpenCore for Designare Z390, primarily because we cannot enable IGPU. Additionally it lacks the polish and flexibility of Clover. But these things will happen in time...

 

[CaseySJ]

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

hi @CaseySJ (OcQuirks.efi Fw RuntimeServices.efi) Is there a conflict with AptioMemoryFix.efi ？ :crazy::crazy::crazy:I found that the previous method to solve the black screen failed in the case of (Shut down-Unplug power-Plug in power-Turn on)

www.tonymacx86.com

Okay, the procedure ffor the edit went fine, but the USB stick won't boot via F12. Every time I select it, the screen goes dark for a moment and re-dispalys back to the F12 option page.

Can you please identify the root cause and let me know what went wrong? I don’t expect to provide much support for this right now. The experiment is for volunteers who can help to fine tune and debug the procedure.

 

[NorthAmTransAm]

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

hi @CaseySJ (OcQuirks.efi Fw RuntimeServices.efi) Is there a conflict with AptioMemoryFix.efi ？ :crazy::crazy::crazy:I found that the previous method to solve the black screen failed in the case of (Shut down-Unplug power-Plug in power-Turn on)

www.tonymacx86.com

@CaseySJ Ok, education time for me.

So in the EFI we have a disabled SAT0>SATA and in the DSDT.aml I can search for SATA. The questions I have are:

Do you pull your system DSDT via whatever method you like (Maciasl I assume) and do a find/replace?

If not, did you enable the name change in the config, boot, then grab the DSDT, place it in the EFI ACPI folder, disable the name change, reboot, check your work?

edit: fixed link and tag

 

[jiffyslot]

Can you please identify the root cause and let me know what went wrong? I don’t expect to provide much support for this right now. The experiment is for volunteers who can help to fine tune and debug the procedure.

I was wondering if it's because the EFI is on a GUID/Mac OS volume instead of MBR/FAT 32 or whatever we would normally use for emergency "Get Out of Jail Free" EFI stick.

Let me monkey with it and see if it makes a difference...

UPDATE: It booted after copied the contents out, reformatted the USB stick to MBT/FAT32 and dragged the Open Core test stuff back in. I had a few boot options listed in the upper left hand corner as 1, 2, 3, etc. When I press 3 for my Mojave SSD, I got many scrolling pages of what looked like "dump errors" and then it booted into the Mojave SSD. The system still freezes when running Cinebench (spinning beachball bench) and restart still goes into a semi-wakefulness state, which forces me to hit the reset switch.

I've attached a zip of the Cinebench 20 crash report if it's of any use.

 

[totototo]

Please see the 7th bullet.

I’m not yet sold on OpenCore for Designare Z390, primarily because we cannot enable IGPU. Additionally it lacks the polish and flexibility of Clover. But these things will happen in time...

Missed that bullet line, sorry. Are you able to use OPT key to show boot options with picker menu hidden by default. I think UsbKbDxe.efi is not working with my setup (both OC 0.5.3 and your 0.5.4 compilation).

 

[CaseySJ]

All, please do not quote the mini-guides in their entirety. Simply post a link.

 

[NorthAmTransAm]

All, please do not quote the mini-guides in their entirety. Simply post a link.

fixed

 

[hylkepylke]

Thanks @CaseySJ. I assume this is 0.5.4 compiled by yourself?
Just wanted to add that I am running really smoothly 0.5.3 with DSDT from @hylkepylke with iMacPro1,1 SMBIOS and everything works great with exception of booting Win10 from OC boot menu.
So far it's been a superior experience to the CLOVER method for me. I do not use a sidecar - I don't own an iPad.

I'm now also experimenting with booting Windows via OC, as that seems neater that booting via BIOS boot selection. So far, when I try to boot either Win 10 or the Win USB installer I get a BSOD and "ACPI_BIOS_ERROR". I want to find out today why that happens.
UPDATE: it's related to the DSDT. If I boot without custom DSDT, everything is fine, I can boot Windows via OC. But with DSDT (which is required for proper macOS), Windows give a BSOD with "ACPI_BIOS_ERROR". Anyone have any experiences with this?

 

[CaseySJ]

@CaseySJ Ok, education time for me.

So in the EFI we have a disabled SAT0>SATA and in the DSDT.aml I can search for SATA. The questions I have are:

Do you pull your system DSDT via whatever method you like (Maciasl I assume) and do a find/replace?

If not, did you enable the name change in the config, boot, then grab the DSDT, place it in the EFI ACPI folder, disable the name change, reboot, check your work?

edit: fixed link and tag

The EFI was originally configured for use with the standard DSDT. After the modified version was posted by @hylkepylke all of those SSDTs became unnecessary except for Thunderbolt. (By the way I’m not sure if Thunderbolt hot plug works. It needs to be tested.)

ACPI name changes are happening inside the modified DSDT. The new DSDT does not actually rename the devices. Instead, it names the ACPI devices correctly from the beginning, hence no renaming needed.

The modified DSDT does not need any further modification — unless a different USB port configuration is needed. It’s just plug and play.

This DSDT is for macOS and may not work under Windows or Linux.