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

[sjoseph]

@CaseySJ
Yes I understood specification difference in each hardwares. I was also thinking the same way because this only happen with particular brands. Is it possible to patch the asrock thunderbolt firmware? I have original BIN file.
Thank you

 

[CaseySJ]

I'm putting back all my previous messages so you can have a clear view of my situation :

Informations I have to provide :
- I‘m using the last version of OpenCore Configurator (2.14.0.0)
- I deleted all the kext in /Library/Extensions/, used Kext Utility to rebuild, but then I had problems that seems to be related to cached kext, so I found in this thread the commands to rebuild the extensions:
sudo mount -uw /
sudo touch /System/Library/Extensions
sudo touch /Library/Extensions
My Clover based system is still working smoothly with the removal of those.
- I have the bios F9g thingy that enables the CFG_unlock by default
- I followed the last mini guide for OpenCore 6.1
- Native VRAM is enabled

My problem
When I’m trying to boot, the system freeze. I’m joining two pictures of the verbose booting where it is freezing (not at the same lines apparently), and also my OC config.plist without my serial IDs for privacy reason.

Then you asked me those informations :

• Catalina:
  • /Library/Extensions
  • kextstat | grep -v apple
• Clover:
  • CLOVER/kexts/Other
  • CLOVER/drivers64/UEFI
• OpenCore:
  • OC/Kexts
  • OC/Drivers

I'm also putting them as joint screenshots. The previous library extensions is what my L/E/ folder was before I removed all the non native kexts (following the guide to switch to OC).
I put them back so my main drive can work fully.

I already have a fully bootable backup that I can work on instead of the main drive.

Thanks for repeating this, but I reviewed the history of this case earlier this morning.

Because you had switched back to Clover successfully, my interpretation was that the case was closed. And the only open issue was slow WiFi after waking from sleep.

There’s nothing wrong in the screenshots. However, if you still want to switch to OpenCore, then please enable verbose, reboot, then Reset NVRAM at the OpenCore picker (to make sure new boot arguments take effect), and then finally try to boot macOS.

 

[CaseySJ]

@CaseySJ
Yes I understood specification difference in each hardwares. I was also thinking the same way because this only happen with particular brands. Is it possible to patch the asrock thunderbolt firmware? I have original BIN file.
Thank you

Here’s why I might appear a bit frustrated by such questions:

I have spent months along with Elias and others to find solutions to these idiosyncrasies. But we don’t have the technical reference materials for Thunderbolt, we don’t have the macOS source code for Apple’s Thunderbolt drivers (they are not published on Apple open source website), and we don’t have access to the BIOS code for each Asus or Gigabyte or MSI or ASRock motherboard.

So all we can do is punch keys randomly on a keyboard and hope that eventually the script for Hamlet or Macbeth comes out.

So for the time being we dismiss all such idiosyncrasies with the (not very nice) statement that “you get what you get”.

 

[Mattioo]

Thanks for repeating this, but I reviewed the history of this case earlier this morning.

Because you had switched back to Clover successfully, my interpretation was that the case was closed. And the only open issue was slow WiFi after waking from sleep.

There’s nothing wrong in the screenshots. However, if you still want to switch to OpenCore, then please enable verbose, reboot, then Reset NVRAM at the OpenCore picker (to make sure new boot arguments take effect), and then finally try to boot macOS.

Ok I understand now, communication problems ahah no big deal
I'm off the computer now, I will try that next week, I keep you updated ! Thanks for your time again

 

[vitilius]

1. What is the make/model of your monitor?
2. Are you using HDMI or DisplayPort?
3. Are you installing Mojave or Catalina?
4. Are you using Clover or OpenCore?
5. What is the make/model of the NVMe SSD?

1. ProLite x2380HS
2. HDMI
3. Mojave
4. Clover
5. WDS500G3X0C-00SJG0

@CaseySJ Should i make any updates in the config file regarding the hardware?

 

[CaseySJ]

1. ProLite x2380HS
2. HDMI
3. Mojave
4. Clover
5. WDS500G3X0C-00SJG0

@CaseySJ Should i make any updates in the config file regarding the hardware?

• Do you have an AMD GPU? The Intel iGPU is not recommended. Various audio, video, and photo applications will not run. You may experience graphics glitches. Web pages in Safari may not render correctly. AMD GPU is strongly recommended.
• The Ilyama ProLite x2380HS is an older generation monitor with only HDMI, DVI, and VGA. I regularly suggest the use of current generation monitors that support HDMI 1.4+ and DisplayPort 1.1+.
  • You can still use the ProLite, but let's see how far we can go with it.

If you are installing Mojave with just the Intel iGPU, then:

• Suggestion 1:
  • On-board HDMI port of the motherboard will not work unless you apply frame buffer patches to the config.plist as explained in Post #1:
    
    
• Suggestion 2:
  • If it's too difficult to add the framebuffer patch as described above, a simpler alternative is to use USB-C to HDMI cable. Plug the USB-C end into either of the two Thunderbolt ports on the rear IO panel. The HDMI end of course goes to the monitor.

For both suggestions, the ig-platform-id must be 0x3E9B0007, which we enter in reverse byte order into Clover's Devices --> Properties section as: 07009B3E. If unsure about this, please post your config.plist.

 

[vitilius]

• Do you have an AMD GPU? The Intel iGPU is not recommended. Various audio, video, and photo applications will not run. You may experience graphics glitches. Web pages in Safari may not render correctly. AMD GPU is strongly recommended.
• The Ilyama ProLite x2380HS is an older generation monitor with only HDMI, DVI, and VGA. I regularly suggest the use of current generation monitors that support HDMI 1.4+ and DisplayPort 1.1+.
  • You can still use the ProLite, but let's see how far we can go with it.

If you are installing Mojave with just the Intel iGPU, then:

• Suggestion 1:
  • On-board HDMI port of the motherboard will not work unless you apply frame buffer patches to the config.plist as explained in Post #1:
    View attachment 490413
• Suggestion 2:
  • If it's too difficult to add the framebuffer patch as described above, a simpler alternative is to use USB-C to HDMI cable. Plug the USB-C end into either of the two Thunderbolt ports on the rear IO panel. The HDMI end of course goes to the monitor.

For both suggestions, the ig-platform-id must be 0x3E9B0007, which we enter in reverse byte order into Clover's Devices --> Properties section as: 07009B3E. If unsure about this, please post your config.plist.

Unfortunately i don't have discrete graphic card, because I use this hack only to work with audio, so I don't have any hard graphic tasks. I will try the instruction you advised and let you know if the problem is solved.

Thank you for your time, have a great weekend!

 

[CODYQX4]

I just tried OpenCore and everything seems to be working well. I wanted to share my experience just to get more anecdotes into the thread in case that's useful, and then I have a couple of questions.

Background
I am on macOS 10.15.4 and this computer has only ever been Catalina through Clover using the guides here. (Again thanks @CaseySJ for all the work maintaining these).

I had avoided doing the CFG Lock MSR 0xE2 patch, since that development came just after I had everything working fairly well, and I didn't need real nvram at the time for anything in particular.

I had this computer unplugged for a couple of months, and before doing that I had turned on FileVault. At the time it worked fine, restarts worked, could boot into the preboot thing and it all was great. However after turning this back on, the preboot would just be a black screen, and doing a verbose boot, the messages didn't reveal anything useful. So I had to decrypt the volume from the Recovery Terminal. I'm not sure what went wrong, and simply not using it for 2 months isn't a satisfying cause, but whatever. This was the second time that FileVault stopped working on me with Clover, and also I'm now several point releases behind, and I heard both updates and FileVault are smoother on OpenCore so I figured now's the time.

Here is the procedure for manually decrypting that worked for me for posterity:

Spoiler: terminal commands

# find apfs disk name/identifier (eg "disk3s1")
diskutil apfs list
# get UUID for user account that has access
# if logged in `fdesetup list` if not,

# get Local Open Directory User from
diskutil apfs listcryptousers /dev/<apfs volume id like disk3s1>

# then
diskutil apfs decryptVolume /dev/<apfs volume id like disk3s1>
# if you get error "APFS volume must be unlocked"
diskutil apfs unlockVolume <apfs volume id>


# or to use the personal recovery key, get the
# Personal Recovery User uuid from lystcroptusers
# then
diskutil apfs decryptVolume /dev/<apfs volume id like disk3s1> -passphrase <recovery key>

Trying OpenCore
I saw that you need the native NVRAM, so I found from this thread the Public Beta firmware F9g, and put that on. When I rebooted, it went straight into Windows. I do not have the NVMe drives in the correct slots (I have macOS on the top one and Windows on the bottom, and I believe the recommended setup is reverse from me), but it had not been a problem for me up until now.

I tried deleting the Windows EFI folder, but that did not bring Clover back. I then realized that upon updating the firmware, that all of the settings were erased. I followed the thread here again to get all of the BIOS settings correct, saved them and restarted, and then the screen stayed black and wouldn't display anything. I had figured that it was something with the onboard iGPU vs the card GPU. So I tried every combination of display port, HDMI, onboard, card, and nothing worked. Then I put it back to how it was (card + DisplayPort), and it was fine. No clue what the issue was there. But with the boot setting to be "other operating system" it went back to Clover and everything seemed good with the new beta bios.

I downloaded the OpenCore 0.6.1 from this post https://www.tonymacx86.com/threads/...700k-amd-rx-580.267551/page-2424#post-2158315 , went with the GPU config, and copied over my settings to a USB stick, and booted form there and that worked first try.

This is where I'm at now. I plan to try it out for a few days, then replace the EFI on the SSD if everything continues to go well. Then update to the latest macOS point release. Then try filevault again, in that order.

Questions
Is there any cleanup from Clover I'll need to do? I never used the native NVRAM, so I didn't do the step 12 "reset c", and that seems OK. Also since this was a newer Clover, I don’t think I have any of the kexts on the non-EFI file system (which seems like it was the older way to do things?). I do have the `/etc/rc.*/` files mentioned at https://dortania.github.io/OpenCore-Install-Guide/clover-conversion/ so I imagine I should remove those once I'm settled on OpenCore.

On the OpenCore Configurator tool Config Checker, almost everything checks out (thank you!) but there were a couple of things. I trust your work more than an automated tool, but in case here are the ones that weren't green:

EnableWriteUnprotector = Yes but should normally be No
ProtectUefiServices = Yes but should normally be No
AAPL,ig-platform-id = 0300983e - iGPU may not be set correctly. Please read the [DeviceProperties Docs]
DisableLinkeditJettison = No but should normally be Yes
PollAppleHotKeys = Yes but should normally be No
PickerMode = External but should normally be Builtin
HideAuxiliary = Yes but should normally be No
AppleDebug = No but should normally be Yes
ApplePanic = No but should normally be Yes
You can remove the tool EFIs here
CrScreenshotDxe.efi should not be here!

The last was the only red one.

There were a couple that mention filevault. I assume they're telling the truth? Are there any filevault OpenCore mini guides in this thread?

AppleSmcIo = No If you plan to use FileVault2, please enable this
FirmwareVolume = No If you plan to use FileVault2, please enable this
HashServices = No If you plan to use FileVault2, please enable this

Thank you for all the work in this thread. It's been a great resource!

Last I checked I've only ever needed AppleSmcIo to make FileVault 2 work. I don't even know if I still need it but I definitely don't need FirmwareVolume and HashServices. Other boards may need them but I've never needed these on Z390 Designare.

 

[telicha]

For this issue please see Quick Reference spoiler in Post 1, Section 3 (Customization), 3rd bullet from the end.

Works beautifully! Thanks so much!

 

[PJonez]

We should not rely on the iGPU to drive the monitor. Instead, any AMD GPU is strongly recommended, even a low cost RX 480 or RX 580. These GPUs are very Mac-compatible.

Is there no way I can get this working. Where I live all the ideal GPUs are gone. I'm gonna have to wait 3-4 weeks to get a GPU card.

Can't I have just the UHD 630 Working with acceleration for now?

It just keeps saying : No Kext Loaded. Seen as 7MB VRAM

Help Please