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

[luispedroemf]

Some questions:

• When you say "macOS Welcome Screen" do you mean the macOS Installer screen?
• Which video port are you using (HDMI or DisplayPort) on the Asus RX 5700 XT?
• When you attempted to install macOS using iGPU, were you using HDMI port or DisplayPort?
  • And was the Asus RX 5700 XT installed or fully removed?
• Which version of Clover do you have? Clover version number will appear at the bottom of the Clover Boot Menu. If you don't see version number, just press F1 at the same Clover Boot Menu.

Please answer all of these questions.

-So, macOS welcome screen, the screen where you can input your username, iCloud , etc. - I think that's the screen that it's trying to show - because I already went to the installation process (i think)
-I'm using the HDMI port. If I try to use the DisplayPort, only the 4th port works, and it shows a grey screen - but, oddly enough, the sound works. (I can hear a chime when I press any key on the keyboard.)
-I installed two times, one with the GPU, and this last one with the iGPU. (The GPU was always installed but I disabled the GPU in the BIOS.)
-The version of Clover is 4934.

And thanks for giving feedback so fast!

 

[delicious]

Does this happen when the machine has been asleep for a long time (several hours)? If so, some folks have seen improvement when using the "300-series RTC Bug" patch.

Please have a look here:

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

I think there are far to much USB Ports I suppose you are mislead by screenshot, as Hackintool doesn't show on initial view actual configuration but all ports for currents system you can configure. I used this screenshot to figure out, which ports have devices connected.

www.tonymacx86.com

Thanks for the reply Casey. Yes it's during overnight sleep. Are you sure that's the right page? I couldn't find anything related there. Also of note is that I have a Gigabyte Z370N and after a brief google of the 300-series RTC Bug patch it seems to be for Z390 only.

 

[CaseySJ]

Oh, my bad. OK on PCI. I'm only seeing the iGPU. I'm guessing there is supposed to be more there.

Yes there should! Can you please post screenshot of your CLOVER/ACPI/patched folder?

 

[Badf1sh]

Yes there should! Can you please post screenshot of your CLOVER/ACPI/patched folder?

It looks like in my earlier tinkering I reverted my EFI folder to a previous version where the display was working. I copied the files back into the patched folder. Now this is what I'm getting. Everything shows up now, but I can't hot plug. I'm not sure if that's just an Apollo thing.

 

[Badf1sh]

It looks like in my earlier tinkering I reverted my EFI folder to a previous version where the display was working. I copied the files back into the patched folder. Now this is what I'm getting. Everything shows up now, but I can't hot plug. I'm not sure if that's just an Apollo thing.

I'm not sure if its worth noting. I don't have a drivers64uefi folder, just a drivers folder and inside is a folder UEFI.

 

[Ploddles]

I'm not sure if its worth noting. I don't have a drivers64uefi folder, just a drivers folder and inside is a folder UEFI.

driver64uefi disappear when Clover was updated to 5xxx. Drivers\UEFI is the new layout.

 

[CaseySJ]

It looks like in my earlier tinkering I reverted my EFI folder to a previous version where the display was working. I copied the files back into the patched folder. Now this is what I'm getting. Everything shows up now, but I can't hot plug. I'm not sure if that's just an Apollo thing.

@jiffyslot,

Can you address the UAD Apollo hot-plug question above?

 

[genzai]

** Confirmed: Native NVRAM in Clover **​

Just wanted to chime in and say this worked perfectly. thanks for your continued in-depth hacking and guidance!

Also, I have been working on and off with some very smart folks on getting Tthunderbolt native working on some older systems, and we have had some important success though some work remains. I would just suggest that in our tests, it is imperative to have the Tthunderbolt controller set to force GPIO power and to not have it in legacy mode. I think we use SL1. I am also available to help with these tests if that's something that would be helpful. I have a bunch of Thunderbolt devices. I also have TB3 add-in cards as well as, of course, the Z390 Designare with its built-in ports and some other systems available to test with. I also have access to most modern Macs.

cheers,
g\

 

[CaseySJ]

Also, I have been working on and off with some very smart folks on getting Tthunderbolt native working on some older systems, and we have had some important success though some work remains. I would just suggest that in our tests, it is imperative to have the Tthunderbolt controller set to force GPIO power and to not have it in legacy mode. I think we use SL1. I am also available to help with these tests if that's something that would be helpful. I have a bunch of Thunderbolt devices. I also have TB3 add-in cards as well as, of course, the Z390 Designare with its built-in ports and some other systems available to test with. I also have access to most modern Macs.

cheers,
g\

We would welcome your involvement and any insight you can provide from the similar work you've been doing. Perhaps you can give us a quick summary of your status? How far have you gotten? Has the Thunderbolt Bus and Thunderbolt Local Node appeared for you? When you say "older" systems, are you referring to older Thunderbolt controllers? Thunderbolt 2?

As you can tell from this thread, we've disabled GPIO3 Force Power because we can enable it via SSDT. Some motherboards do not have an explicit BIOS option for this (e.g. ASRock) so a software/SSDT-based solution becomes valuable when applying this to other systems.

Let me also alert @Elias64Fr to this post.

 

[Spail]

Used this guide to select MultiBeast options right after finishing installation, but I’m stuck on “Currently Installing” screen (while installing Bootloaders > Clover UEFI Boot Mode + Emulated NVRAM. Couldn’t google this issue, any ideas?