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

[CaseySJ]

Now I am in process of upgrading. I am following the microguide to upgrade from Mojave and when I boot from the USB and select the "upgrade from mojave" in the clover menu it goes no further and hangs with an apple logo on my screen. Any thoughts?

Have you unlocked MSR 0xE2 or installed beta BIOS F9g that disables CFG-LOCK by default?

Any time we see a hanged Apple logo during boot, the immediate response should be to reboot in verbose mode. At the Clover Boot Menu we press spacebar then use arrow keys to move down to Verbose and press spacebar to toggle it on, then Esc to return to Clover Boot Menu.

 

[vicantu]

Thanks for the reminder. The screenshots show that Link Status is always 0x101 when Thunderbolt Bus is fully activated. This is okay, but when Thunderbolt controller is powered on and ready, Link Status should change to either 0x02 or 0x07. The fact that it always stays at 0x101 indicates that the controller is not switching to the ready state.

In your "2nd attempt" the Thunderbolt bus was not really activated when Thunderbolt devices connected and worked. But Link Status was correct.

I'm wondering if the problem is due to the UGIO method that disables and reenables power to the Thunderbolt device. I've temporarily commented out the lines that dynamically disable and enable power, hence leaving power turned on at all times.

No guarantees of course that this will work, but please try the new V4 with the same two tests (Test 1 is without TB device connected during boot; Test 2 is with TB device connected during boot).

@CaseySJ , here the results using SSDT-TbtOnPCH-NUC-8-OSY86-V4-WAKE.aml and SSDT-DTPG-V3.aml

Thanks

Test 1:

• Boot system without any Thunderbolt device connected.
• Then before 30 seconds, capture screenshot of System Information --> Thunderbolt

• Quit System Information (this is necessary)
• Then after 30 seconds, open System Information --> Thunderbolt and capture another screenshot

Test 2:

• Boot system with one Thunderbolt device connected.
• Then before 30 seconds, capture screenshot of System Information --> Thunderbolt

• Quit System Information (this is necessary), but keep Thunderbolt device connected at all times
• Then after 30 seconds, open System Information --> Thunderbolt and capture another screenshot

 

[DJ4MC]

Have you unlocked MSR 0xE2 or installed beta BIOS F9g that disables CFG-LOCK by default?

Any time we see a hanged Apple logo during boot, the immediate response should be to reboot in verbose mode. At the Clover Boot Menu we press spacebar then use arrow keys to move down to Verbose and press spacebar to toggle it on, then Esc to return to Clover Boot Menu.

I am 99% certain I unlocked MSR0xE2. I ran through the installer, it booted into Catalina, went through the setup etc. THen I copied the EFI fodler over and now this... I know I will resolve it but always fun fun fun...

Jules

 

[jwpb]

Hello @jwpb,

Welcome to the forum. End randomseed is generally very easy to fix, but it may require one or both of the following:

• Confirm that only 1 memory fix driver is present in the CLOVER/drivers/UEFIfolder. If you unsure, just post a screenshot of that folder.
  • Ideally, however, we should replace OsxAptioFix2Drv-free2000 with OcQuirks/FwRuntimeServices (on Mojave). Instructions are here.
• If problem persists, then we need to perform a CMOS Reset by following the procedure in Designare owner's manual.
  • CMOS Reset will also set BIOS parameters to factory defaults so it's a good idea to either:
    • Save BIOS settings to a profile (from "Save & Exit" screen) before doing CMOS Reset, then load the profile after CMOS Reset, OR
    • Configure all BIOS parameters again starting with Load Optimized Defaults.

Thank you for your answer.
As I wrote earlier - I tried to follow your guide very carefully, so also I gave a try replacing OsxAptioFix2Drv-free2000 with OcQuirks / FwRuntimeServices and reset CMOS. (Saving BIOS profile was recommended in your post, so I did that first of course.) All of those I did about two weeks ago. I know, that "end randomseed" is very popular issue and I've decided to ask for help because all of solutions, that I found (and was able to understood at least a bit) unfortunately failed.
Below you can find a screenshot of my CLOVER/drivers/UEFI folder.

BTW: Is it good idea to post here my compressed EFI folder? (without "themes" and other unnecessary stuff of course) Or maybe just 'ACPI', 'drivers' and 'kexts' folders with 'config.plist' file? Would someone have time and will to check what stupid mistakes I have done? Please.. I can pay in good polish dumplings..

 

[CaseySJ]

Thank you for your answer.
As I wrote earlier - I tried to follow your guide very carefully, so also I gave a try replacing OsxAptioFix2Drv-free2000 with OcQuirks / FwRuntimeServices and reset CMOS. (Saving BIOS profile was recommended in your post, so I did that first of course.) All of those I did about two weeks ago. I know, that "end randomseed" is very popular issue and I've decided to ask for help because all of solutions, that I found (and was able to understood at least a bit) unfortunately failed.
Below you can find a screenshot of my CLOVER/drivers/UEFI folder.

BTW: Is it good idea to post here my compressed EFI folder? (without "themes" and other unnecessary stuff of course) Or maybe just 'ACPI', 'drivers' and 'kexts' folders with 'config.plist' file? Would someone have time and will to check what stupid mistakes I have done? Please.. I can pay in good polish dumplings..

Please try the CMOS Reset option mentioned in the last reply. If that does not work, then simply compress and upload your CLOVER folder.

 

[CaseySJ]

I am 99% certain I unlocked MSR0xE2. I ran through the installer, it booted into Catalina, went through the setup etc. THen I copied the EFI fodler over and now this... I know I will resolve it but always fun fun fun...

Jules

Are you able to boot into Catalina with the USB boot disk, but not with the internal macOS SSD?

Although I've not seen those two errors before, we can try replacing OcQuirks/OpenRuntime with the earlier OcQuirks-4/FwRuntimeServices found here.

If the problem persists, feel free to compress and upload the CLOVER folder from USB boot disk.

 

[InsomnIaHackintosh]

@CaseySJ Thanks a lot for your fab guide to patch the Titan Ridge! djlild7hina guided me to your great posts and I'm happy I managed to get so far so thank you both! It worked flashing, It's loading up and all working great including the hotplug.

I was really hoping with this patching would do some magic to help my obsession )
I have a CalDigit connected and another OWC 5Bay raid hooked trough the CalDigit. I want these devices to cold boot with the machine. Instead I have to unplug and plug back in to load each time I power on.

Any idea what chances are to make this work? For example if I connect the CalDigit dock with the drive in my MBP it starts from the cold boot as soon as the os reaches 50% of the boot.

BTW, if anyone has my hardware or same MB, this Open Core works great! I've cleared SN so just need to replace those.

Thanks!

 

[tonben]

Good Evening to all,

I have a fresh install of Catalina (as per CaseySJ’s mini-guide) on a system comprising of a Z390 Designare, an i9-9900K and a RX580 Gpu among other components.

OS: 10.15.4
Clover_r5117
May 2020 Update files

This installation was done a little over one week ago and performed extremely stable during daily usage.
Successful Hot-Plug capabilities for UA devices without having flashed thunderbolt.

I had the realization today that in my mindless haste, I neglected to install Multibeast as part of the post installation process. I previously always included Multibeast.

Is Multibeast 12.1.0 installation absolutely necessary for this mini-guide task?
As I pointed The system is purring along. Zero issues. So, do I poke the proverbial Bear????
Suggestions?
Tony….

 

[DJ4MC]

Are you able to boot into Catalina with the USB boot disk, but not with the internal macOS SSD?

Although I've not seen those two errors before, we can try replacing OcQuirks/OpenRuntime with the earlier OcQuirks-4/FwRuntimeServices found here.

If the problem persists, feel free to compress and upload the CLOVER folder from USB boot disk.

Thanks Casey. I'll pick this up tomorrow and inspect/scrub the EFI folder. Thanks again for a fantastic thread -- over 2000 posts on it! Amazing. I will persevere on this one.

Jules

 

[kseel89]

This is a strange time because of the pending transition from Z390 to Z490. However if you can find other Gigabyte Z390 boards, you can use a Thunderbolt add-in-card. But even these add-in-cards are becoming hard to find because the next generation is about to launch.

Anything from the Gigabyte Z390 AORUS series should work. On the high end there is Gigabyte Z390 AORUS Xtreme which also has built-in Thunderbolt.

Thanks. I've got an order in for this board actually with Amazon, it is back-ordered but showing that it should ship to me June 5th, now. That may be more like June 20th, which is what Amazon originally quoted for delivery date, we'll see.

Now I'm just working on choosing and buying all the other components...