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

[brousseau6933]

Ok, saw this reply from you CaseySJ in another thread, do you think it is related to USB-C not being recognized at cold boot on TB3?
https://www.tonymacx86.com/threads/...om-ssdt-discussion.293279/page-8#post-2083782

 

[kromuh]

*** WARNING: Before Updating to Catalina 10.15.1 ***​

As @rondark pointed out, it is in fact necessary to update WhateverGreen to version 1.3.4 or newer before installing Catalina 10.15.1. This means:

• Downloading WhateverGreen 1.3.4 from the acidanthera GitHub site.
• Copy the kext to:
  • CLOVER/kexts/Other
  • /Library/Extensions and then run Kext Utility to rebuild the kernel cache
  • Also disable or remove any AGDP patch from Kernel and Kext Patches.

Failure to perform these steps will result in an empty screen just before the login window would have appeared.

---

View attachment 433441​

Hey @CaseySJ!
I'm looking to upgrade to Catalina today as I solved some Ableton issues that kept me from moving past Mojave.

I followed the instructions from this post - updating WhateverGreen to 1.3.4, but I cant seem to get "Boot macOS Install from Mojave" to boot after from clover after Install macOS Catalina.app installation and restart.

Here is where the booting freezes:

And here is my EFI folder:

Any ideas why I'm unable to boot all the way through to the update?

 

[Inqnuam]

Hello @CaseySJ
I got this after updated to OC 0.6.1

I think it was already there before the update but the transition from GIGABYTE logo to OpenCanopy was much faster so I did not have the time to take a pic.
With 0.6.1 it appears for something like 4 seconds
Tried cold boot & NVRAM reset.

I can still boot macOS like before, no difference.

 

[Inqnuam]

Hey @CaseySJ!
I'm looking to upgrade to Catalina today as I solved some Ableton issues that kept me from moving past Mojave.
I followed the instructions from this post - updating WhateverGreen to 1.3.4, but I cant seem to get "Boot macOS Install from Mojave" to boot after from clover after Install macOS Catalina.app installation and restart.
Here is where the booting freezes:
Any ideas why I'm unable to boot all the way through to the update?

Hello
You don't want to try to boot with OpenCore?

 

[CaseySJ]

Apple Seeds New Public Beta of macOS Big Sur to Public Beta Testers

Apple today seeded a new beta of the upcoming macOS 11 Big Sur update to its public beta testing group, allowing non-developers to give the software...

www.macrumors.com

 

[brousseau6933]

If I reboot but hit Delete to access BIOS and restart from there, it’s ok, more weirdness! Still a warm boot but going through BIOS menu!

Fortunately, drives recognized after wake up, just tested to be sure.

Just to add to my confusion: doing Ctrl-Alt-Del on Clover Boot menu and choosing MacOS as usual does the trick too!! USB-C drives mounts ok. It's just that a normal restart doesn't initiate correctly USB-C stack on TB3. Should stop completely, goes through BIOS or Ctrl-Alt-Del...

Even tried Clover 5119 but same result. I don't know what to think...

 

[CaseySJ]

Worked on windows as separate monitor. Now when booting osx with just onboard cable I get this @CaseySJ

Please try a cold start and disconnect the Apollo UAD when booting.

 

[CaseySJ]

Another « interesting » discovery Master Casey:

If I plug the T5 or the USB-C enclosure on TB3 port while MacOS is already booted, the drives mounts correctly. However, after a restart, they do not mount anymore. They have to be unplugged/plugged again to be recognized.

If the drives are already attached before power up on the TB3 ports, they mount correctly though...

This behavior appears with any TB3 SSDT’s and with any USB mapping method (USBPorts.kext or SSDT based).

Normal or not for the USB part of the Titan Ridge controller?

Anyone else noticed this behavior with USB-C drives and TB3 ports?

I guess I’m in the minority using TB3 ports to test USB-C compatibility...

To resume: warm boot, USB-C drives disappear. Cold boot, it’s ok.

I'll check this on my Z390 Test Bench shortly and will update this post...

Update: Confirmed the same behavior as you reported. USB-C devices will work (a) with hot-plug, (b) with cold boot, and other resets such as (a) entering/exiting BIOS Setup and (b) CTRL-ALT-DEL at Clover Boot Menu.

 

[CaseySJ]

Hey @CaseySJ!
I'm looking to upgrade to Catalina today as I solved some Ableton issues that kept me from moving past Mojave.

I followed the instructions from this post - updating WhateverGreen to 1.3.4, but I cant seem to get "Boot macOS Install from Mojave" to boot after from clover after Install macOS Catalina.app installation and restart.

Here is where the booting freezes:

View attachment 487380

And here is my EFI folder:

View attachment 487381View attachment 487382

Any ideas why I'm unable to boot all the way through to the update?

Hello @kromuh

Because Mojave is already installed, we would not select "Install macOS Mojave" again. The guide for upgrading from Mojave to Catalina is provided here:

Feel free to report any issues or ask any questions when following that guide.

 

[CaseySJ]

Hello @CaseySJ
I got this after updated to OC 0.6.1
View attachment 487384

I think it was already there before the update but the transition from GIGABYTE logo to OpenCanopy was much faster so I did not have the time to take a pic.
With 0.6.1 it appears for something like 4 seconds
Tried cold boot & NVRAM reset.

I can still boot macOS like before, no difference.

There seems to be a (minor) problem with OpenCore 0.6.1. The release notes describe the new Booter Quirk DisableLinkeditJettison, but when we include that field in config.plist we get the warning (not error):

OCS: No schema for DisableLinkeditJettison at 2 Index, context <Quirks>!

This means that the OpenCore parser does not recognize the keyword "DisableLinkeditJettison" and skips over it. The phrase 2 Index refers to the index within the <Quirks> section. Index numbers begin with 0, and we can see from the screenshot below that "DisableLinkeditJettison" is Index 2.

This will probably be fixed in the next release, but for now we can simply remove that line or prefix it with a hash mark to disable it, as follows:

As for me, I've decided to leave it alone and wait for next release of OpenCore.

This is another reminder that OpenCore is still Beta and the version number begins with 0.

---

*** UPDATE ***
Thanks to @CODYQX4 we now know that the problem is with OpenCore Configurator 2.12.0.0, which is inserting this field into Booter Quirks when it should be inserted into Kernel Quirks. I will fix the OC 0.6.1 EFI once this problem is fixed in OpenCore Configurator because any use of this version will break the config.plist.