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

[madmax559]

In the meantime I've filed a bug report with Gigabyte Support on the BIOS display issue

I checked their support docs on the Designare z390 and their own images show an AMD gfx in slot 1, with its DP out to mobo DP in and TB out from mobo to monitor.

Since the BIOS starts up first before any OS loader, I can't think of any reason why it won't show up on the display.

 

[madmax559]

Did the following tests.

config-amd.plist -> config.plist
1. Unplugged TB & DP IN from mobo & attached monitor to AMD DP IN & set Bios Initial Display to PCI Slot 1 (AMD RX580)

1. System booted into OSX via Clover. Everything looks OK except Preview will not load images & hangs (known issue)
2. About will show OSX Mojave & AMD RX580
3. Reboot & hit F12 to get into BIOS, selected USB stick and booted OC. Now we have 2 "Machintosh HD"
4. Select the first one, hit enter and it reboots back to BIOS.
5. Hit F12 again & select 2nd entry & it shows Apple log & progress bar & is still frozen 10 min later
6. Hard reboot & back to F12 & boot from USB & select 1st "Mac HD" & this time it shows Apple Log & remains frozen

Reboot & BIOS setup & change Initial Display to iGFX & reboot.
Unplug DP cable from AMD & don't attach it to internal DP & attach TB to monitor.
Start up & BIOS can be seen (apparently it only vanishes when the AMD DP out is connected to mobo DP in).
OSX boots back from Clover & everything looks OK & preview can load images & pdf's.

About will show OSX Mojave & Intel UHD 6300.
(It will show RX580 if the AMD was connected to mobo & TB out was used, since the AMD would be an "external display".)

Made sure regular boot via clover still worked & system was OK on just the iGFX/UHD 630

config-igpu.plist -> config.plist //copy fi folder to stick etc etc

1. Boot into USB stick & OC (again it shows 2 Mac HD entries)
2. Pick first one & hit enter....... screen goes blank & it jumps to clover
3. Reset again & F12 & try again & this time Apple logo & hangs for 10 min
4. Reset again & OC & try 2nd entry & it reboot backs into Bios
5. Reset again & F12 & OC & 2nd entry & apple logo & frozen in place

Reset machine again & pull out USB stick & plug DP out back into DP in & let clover boot back into Mojave so I can type this entire thing out.

I'm beginning to think this machine is possessed.

 

[CaseySJ]

I'm running into a boot issue using USB stick with OC EFI.

Followed the 0.8.3 OC Mini Guide.
EFI was made using the config-amd.plist copied to config.plist & all values set correctly from Hackintool.

1. Shut down machine & unplugged DP in from AMD DP out. Boot back into Clover/Mojave & made sure everything was working.
This now uses the iGP so I can see the BIOS (even though the BIOS/peripherals is set to iGP for Preview to work correctly in Mojave).

2. Shutdown, plug in USB stick & hit F12 and select PNY USB partition 1 (EFI with OC on it).
3. OpenCore shows up with EFI/Macintosh HD/Macintosh HD.

This is okay because you have (a) original Mojave SSD and (b) clone of Mojave SSD. If the clone is on an external drive, OpenCore should show a different icon.

I don't know why there is a double entry since all partitions on all drives have a different volume label.
Having the list picker show device info would be useful here.

OpenCore uses a different method for obtaining the name of each macOS disk. It uses the disk's original volume name at the time macOS was first installed. The volume name is located in a file called .disk_label.ContentDetails that can only be accessed from Recovery. The procedure is described here, but this can be done later.

4. Pick 1st Mac HD results in black screen. Reboot and pick it again from OC.
The F12 BIOS boot selector is a bit iffy because even when I make a selection, it will sometime boot back into Clover/disk0s1.

5.Apple logo shows up & start of progress bar; it sits there for 10 min with no booting into Mojave.

At the OpenCore boot picker we can press and release CMD-V to enable verbose logs. Then select the macOS boot disk and you'll see the detailed boot progress.

Because you're using config-AMD-GPU.plist as the starting point for config.plist, simply connect an HDMI or DP cable from the AMD GPU directly to the monitor. Some Thunderbolt monitors support Alt-Mode in which we can use a DP-to-USB C cable directly from the AMD GPU to the monitor (no need for DP-In and Thunderbolt-Out).

It may be good to try connecting a USB-C to DP cable directly between the AMD GPU and Thunderbolt monitor.

6. Also dropped into UEFI shell & checked devices and everything looks OK and lists correctly.

Now, I have a couple of options here, but want a second opinion.

1. I can recreate the EFI above by copying the config-iGPU.plist to config.plist and see if that works.
This quirk of the BIOS not showing up when AMD DP out is plugged into DP in on mobo and TB out to monitor.
Plain TB out to monitor shows the BIOS every single time and the BIOS is set to iGPU. So the AMD being plugged into mobo shouldnt matter.

Sure, this is a viable option.

2. When the USB OC EFI kicks in & picks up disk0/s1 (Mac HD), I assume it's not loading any of the Clover kexts as I have not altered any caches/kexts/prefs on Mojave at the moment and simply booting up in OC via USB and starting up Mojave from HDD (SSD 970) just to make sure everything is stable per the guide above.

The "Hackintosh kexts" that are installed in the clone of Mojave (/Library/Extensions) need to be deleted. The kernel caches need to be rebuilt. This can be done by booting the clone via Clover. Please see Step 2 of the Clover-to-OpenCore guide.

OpenCore will fail to boot the system if those Hackintosh kexts are still installed in /L/E.

 

[schlosrat]

Hi, I'm trying to update my Z390 AORUS PRO WIFI / i9 9900K / RX 580 Pulse 8GB system from Clover/Catalina (10.15.4) to OC/Monterey (12.6). My system has two boot drives in it, a 240GB SSD, and a 500GB NVMe (WSD500). Both started with Clover/10.15.4, but now I've got Clover/12.6 (sort of) on the WSD500. That's not what I want, and it doesn't boot that way, I'm just a bit stuck in the end phase of this process.

Successes so far:
1. Re-flashed the Z390 AORUS PRO WIFI to the latest (2021) FW (F.12)
a. Configured BIOS to default optimizations and confirmed this boots my SSD/WSD500 copies of 10.15.4
2. Created OC Monterey install media (USB) following Dortania's guide. I've got about the least stuff in there I think I can, using all DEBUG versions for OC and kexts
ACPI: SSDT-AWAC, SSDT-EC-USBX-DESKTOP, SSDT-PLUG-DRTNIA, SSDT-PMC (all for Coffee Lake, all prebuilt)
Drivers: HfsPlus, OpenRuntime, ResetNvramEntry
Kexts: AppleALC, Lilu, USBToolBox, VirtualSMC, WhateverGreen
3. Built config.plist with propertree per Dortania's guide
4. Boot OC Install USB and cleared NVRAM

I was stuck for a bit at https://dortania.github.io/OpenCore...rnel-issues.html#stuck-on-eb-log-exitbs-start, then made the following changes to my BIOS settings to free up ram, which got me a bit further

CSM Support: [Enabled] -> [Disabled]
Above 4G Decoding: [Disabled] -> [Enabled]
Software Guard Extensions (SGX): [Software Controlled] -> [Disabled]
LEDs in System Power On State: [On] -> [Off]
Legacy USB Support: [Enabled] -> [Disabled]
Internal Graphics: [Auto] -> [Disabled]

That got me through a 5 boot cycle of installing Monterey on a freshly erased WSD500 stuck at https://dortania.github.io/OpenCore...rozen-in-the-macos-installer-after-30-seconds. On the plus side it was seeing my wifi card and network! On the minus side, no matter what I did I couldn't get far before it would freeze.

Turning back to the troubleshooting guide again I found that, although I didn't have a NullCPUPowerManagement kext to remove, I did see Kernel -> Force -> Emulate was set to False, so I switched that to True and gave it another go.

Now it seems I get even less far, and I get stuck with the Apple logo and the progress bar a bit more than 1/2 way across. Is this possibly the https://dortania.github.io/OpenCore...e-issues.html#macos-frozen-right-before-login issue? I'm running a Coffee Lake CPU on a fairly modern MB with 2021 FW, so it seems unlikely, but maybe?

Another theory is perhaps I need to erase my NVRAM again from the OC Picker. What I've been doing is booting from my SSD (which has Clover and the working copy of 10.15.4 I'm using now to write this), researching the issues and making changes to the /EFI on the USB, then booting from the OC Install USB and picking WSD500 to try to get Monterey to run. Am I hosing my NMRAM each time I boot with Clover to a working system?

Also, Clover is still in the /EFI for both the SSD and the WSD500 drives. Should I copy the /EFI folder from the OC Install USB to the WSD500's /EFI? I think if I do that I'd still be able to use BIOS to pick the SSD and get the system up to a working state while I pound on the config.plist, etc. to get things working on WSD500.

 

[CaseySJ]

@schlosrat,

Although you have a Z390 AORUS Pro and not the Designare, you can still try using the OpenCore 0.8.3 EFI folder from this post.

Do you have any Hackintosh kexts installed in Catalina's /Library/Extensions folder? Those will interfere with OpenCore.

 

[loghound]

Hi All

I upgraded to Ventura yesterday -- It was amazingly easy (upgrade to OC 8.5 and, prepare a flash stick and install) and pretty much everything seems to be working except for DRM. (I had this problem in Ventura also.)

I have the stock setup @CaseySJ recommends except my video card is a Vega 56, and I have a i9 with iGPU.

In looking through forum posts it seems like there is not a definitive way to enable DRM (for things like Apple Music and Apple TV+) in Ventura. Is that true?

 

[CaseySJ]

Hi All

I upgraded to Ventura yesterday -- It was amazingly easy (upgrade to OC 8.5 and, prepare a flash stick and install) and pretty much everything seems to be working except for DRM. (I had this problem in Ventura also.)

I have the stock setup @CaseySJ recommends except my video card is a Vega 56, and I have a i9 with iGPU.

In looking through forum posts it seems like there is not a definitive way to enable DRM (for things like Apple Music and Apple TV+) in Ventura. Is that true?

With iMac19,1 we have a problem with DRM. But with MacPro7,1 it works fine. Some things to consider:

• MacPro7,1
  • tv+ and Music app (DRM) both work fine
  • Requires RestrictEvents.kext to avoid lots of unnecessary notifications
  • Sidecar will not work; if you don't use this, then no worries
• iMac19,1
  • tv+ and Music app (DRM) will not work (but if you subscribe to music, it will work)
  • Sidecar works with iGPU

 

[schlosrat]

@schlosrat,

Although you have a Z390 AORUS Pro and not the Designare, you can still try using the OpenCore 0.8.3 EFI folder from this post.

Do you have any Hackintosh kexts installed in Catalina's /Library/Extensions folder? Those will interfere with OpenCore.

Thanks @CaseySJ! That's a great looking guide!

I assume there are not Hackintosh kexts in the /L/E foler since I did a clean install wiping the drive with Disk Utility prior to installing. I think all that would be in /L/E is whatever the Monterey installer put there, and when I ran that it was after booting from an OC USB, so probably no Hackintosh kexts! Could I be wrong about this?

Can I use the latest version of OCC (2.63.0.0) with OC 0.8.5 and your guide? I assume if I copy EFI folder I'll be getting OC 0.8.3 with your OpenCore.efi file. This might be two questions. Can I use OCC 2.63.0, and can I replace the 0.8.3 OC efi with the 0.8.5 efi?

Using OCC 2.63.0, the only options I've got are for OC 0.8.5 Release and 0.8.6 Development, so I went with 0.8.5 Release and replaced the drivers with the corresponding 0.8.5 versions. Ditto for tools that shipped with 0.8.5.

I copied config-AMD-GPU.plist to config.plist since I've got an AMD GPU.

I populated screens per your guide, choosing Default for SecureBootModel, and 0 for SetApfsTrimTimeout since I've got a Samsung NVMe SSD. For my system product name I went with an iMac19,1 since that corresponds to my i9 processor. This gave me a ProcessorType of 4105.

With all that in there, I was suprised how quickly it booted and got to the OpenCanopy GUI. I selected my WSD500, and then it hung at an apple logo with no progress bar.

I'm going to try next with the 0.8.3 drivers and files in your EFI, SecureBootModel = Disabled, but still using OCC 2.63.0 and the iMac19,1 setting.

Can I use an iMacPro1,1 setting like you have when my CPU is not a Xeon?

 

[CaseySJ]

Thanks @CaseySJ! That's a great looking guide!

I assume there are not Hackintosh kexts in the /L/E foler since I did a clean install wiping the drive with Disk Utility prior to installing. I think all that would be in /L/E is whatever the Monterey installer put there, and when I ran that it was after booting from an OC USB, so probably no Hackintosh kexts! Could I be wrong about this?

You're right. On a fresh install of Monterey there's nothing to worry about!

Can I use the latest version of OCC (2.63.0.0) with OC 0.8.5 and your guide? I assume if I copy EFI folder I'll be getting OC 0.8.3 with your OpenCore.efi file. This might be two questions. Can I use OCC 2.63.0, and can I replace the 0.8.3 OC efi with the 0.8.5 efi?

Using OCC 2.63.0, the only options I've got are for OC 0.8.5 Release and 0.8.6 Development, so I went with 0.8.5 Release and replaced the drivers with the corresponding 0.8.5 versions. Ditto for tools that shipped with 0.8.5.

Yes this is also okay. Simply download the 0.8.3 EFI folder and replace both (a) OpenCore.efi and (b) BOOTx64.efi with those from 0.8.5. Then you can use OpenCore Configurator 2.63.0.0 set to 0.8.5 Release Version.

I copied config-AMD-GPU.plist to config.plist since I've got an AMD GPU.

I populated screens per your guide, choosing Default for SecureBootModel, and 0 for SetApfsTrimTimeout since I've got a Samsung NVMe SSD. For my system product name I went with an iMac19,1 since that corresponds to my i9 processor. This gave me a ProcessorType of 4105.

With all that in there, I was suprised how quickly it booted and got to the OpenCanopy GUI. I selected my WSD500, and then it hung at an apple logo with no progress bar.

At OpenCore boot picker we can press and release CMD-V to enable verbose logs. Then select the macOS installer. Note that CFG-Lock in BIOS must be disabled.

I'm going to try next with the 0.8.3 drivers and files in your EFI, SecureBootModel = Disabled, but still using OCC 2.63.0 and the iMac19,1 setting.

Can I use an iMacPro1,1 setting like you have when my CPU is not a Xeon?

Yes, no problem. But in that case, add RestrictEvents.kext.

 

[schlosrat]

You're right. On a fresh install of Monterey there's nothing to worry about!


Yes this is also okay. Simply download the 0.8.3 EFI folder and replace both (a) OpenCore.efi and (b) BOOTx64.efi with those from 0.8.5. Then you can use OpenCore Configurator 2.63.0.0 set to 0.8.5 Release Version.


At OpenCore boot picker we can press and release CMD-V to enable verbose logs. Then select the macOS installer. Note that CFG-Lock in BIOS must be disabled.


Yes, no problem. But in that case, add RestrictEvents.kext.

Got it, so use RestrictEvents.kext if set System Product Name is MacPro1,1.

Is the advantage to that product name just about tv+ and Music app (DRM), like you mentioned above for MacPro7,1? Just wondering what the advantages may be to going that route, but first I need it to boot all the way through an install!