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

[StefanAM]

@genzai, it's well worth trying this approach as it works a treat in my system (built-in AR). Here's a quick summary of the approach (all credit to @Elias64Fr and @CaseySJ for their original work)

1. Use the attached SSDT as a base
2. Change RootPort (RPnn) number to correct value for the motherboard (in my case RP05)
3. Change the address in the first line of the MMBA method to the correct value. If the RootPort PCI address is 1x,n, the correct value is (1x *8)+n. So for my RP05@1c,4 its (1c*8)+4 = E4
4. Adjust the UPSB section as required. My mobo only has 1 TB port so no DSB4 device and only one XHC2 SSP/HS port pair. If you have two TB ports then add DSB4 and a second pair of XHC2 devices
5. Adjust the _GPE.E2C hotplug method to the correct values for the motherboard. In a DSDT dumped directly from the bios there is a method under _GPE called YTBT. In a booted system the name of this method changes to _Exx where xx is a hex number. So in my system Method (YTBT) becomes Method(_E2C). Also change the XE2C value to XExx
6. In the ACPI section of your config.plist add search and replace values to rename RPnn._INI to RPnn.XINI and _Exx to XExx (see attached config.plist from OpenCore for an example). These changes ensure the original ACPI code is used for operating systems other than macOS.
7. Inject the ThunderboltDROM value from the unpatched AR firmware via Device Properties in your boot loader config.plist, using gfxutil to find the correct DevicePath for NHI0. The two byte sequence for IOThunderboltPort5 (02C3) needs to be changed to 0283 so the port is activated. Note that your byte values here might be different but the C needs to be changed to an 8. This will cause a CRC32 error and cause the DROM not to be processed correctly by macOS. Fortunately a Hackintool > Logs > System search for 'DROM' will show you the correct CRC32 value so byte-reverse it and replace the existing CRC32 bytes (bytes 10 to 13). So in my case:

75                                                CRC8
00 00 00 00 00 00 49 18                Thunderbolt UID
74 20 31 2B                                  CRC32
01 51 00 49 18 04 00 66 04
08 81 80 02 80 00 00 00
08 82 80 02 80 00 00 00
02 83                                            BYTES TO ACTIVATE IOTHUNDERBOLTPORT@5
0B 84 20 01 00 3C 00 00 00 00 00
05 85 50 00 00...

I hope this helps...

Hi! I'm really interested in this procedure. I have Alpine Ridge flashed and it's working perfect with my devices. But I'd like to use it also in other OS's. It's hard for me to follow points 4 and 5 from your guide. If you are so kind and give me a hand........ Thank you!

 

[scottkendall]

You may be right about the IGPU being the problem. That’s an easy one to test, and I completely overlooked it. I don’t think I have video pass thru as an option. You have that under TB security settings in BIOS?

Here is the BIOS screen:

 

[faithie999]

@faithie999 It's best not to mix and match from other sources just stick to the ThunderboltDROM from your unpatched firmware. I changed 2C5 in the DROM to 285 to activate IOThundernboltPort5 but this will cause a CRC32 checksum error which needs to be fixed. If you look in the sleep/wake working IOreg you'll see that the ThunderboltDROM property isn't there under NHI0, which means it hasn't been loaded. I think you'll find that when you check the correct log it will show that there was an error with loading the DROM from IORegistry. Upload the output of the 'DROM' System log search when you've had time to do it, along with the relevant section of your Clover config.plist... Don't give up!!

in Hackintool, Logs--System was blank. that's why I thought logs--boot was the correct log. sorry.
I just discovered that I needed to hit the reload icon at the bottom of the system log page.
I rebooted and in the Hackintool system log there is no occurrence of DROM. the file is attached.

the Devices portion of my config.list is attached.
also attached it an IOReg output that I just saved.

I haven't altered your SSDT other than to make the changes directed in your guide.

even though the display and peripherals (and wake) seem to be working when I have the display attached to TB port 2 on the AR card, it would be great to figure out the DROM checksum issue.

another question--your guide said to use gfxutil to check for the proper address for NHI0. I believe mine is at 1B,4. should I change the devices property address from 1C,4 to 1B,4? when I have tried that, I get some boots resulting in display and peripherals working properly, and other boots with display working/peripherals not working, or display not working/peripherals working. attached is gfxutil output.

thanks for your continued help!!!

 

[RuleBreaker01]

Hello. I have a problem I can not read the chip the mainboard Z390 Designer LED yellow lights.
i have programmer software 1.29

I chose 25/26 spi flash winbond with the name I do not know what to set

 

[SuDoDmz]

I blame that you have IGPU enabled but that's just my opinion, if their was a Anti-IGPU club I would be the president.

Now you're being harsh on the iGPU (though I must agree, that there would've been better ways to solve this). My Aorus Xtreme can drive DP through TB3 just over iGPU (no DP-Ins unfortunately). Lets say, for the time being, it's a necessary evil.

 

[RuleBreaker01]

okay with w25q128fw i could par data is that correct?

 

[scottkendall]

Now you're being harsh on the iGPU (though I must agree, that there would've been better ways to solve this). My Aorus Xtreme can drive DP through TB3 just over iGPU (no DP-Ins unfortunately). Lets say, for the time being, it's a necessary evil.

Yes no DP-in is unfortunate, for a while I thought about getting a designare board but when I found out that one of the ports had to be driven from the IGPU it made me reconsider and since firmware patching has began I have even less reason now. I am really happy with how this system is running, and how the Thunderbolt 3 AIC is working with my devices.

 

[karambit]

I finally received my new FCPX bundle and am able to post some quick benchmarks for @CaseySJ Logs....

Bruce Trail: H264~ 11 seconds, ProRes 422~ 6.90 seconds.

System: Z390 Designare w/i7 8700K cpu, Sapphire Radeon VII[Latest BIOS and Software], Crucial Ballistix Sport Ram- 32 gb(2666Mhz)DDR4 Ram, Catalina drive- Samsung 960 EVO (500Gb)

 

[gandem]

Here is the BIOS screen:

View attachment 468864

Ok, so here is the latest... First off, I do in fact have the DP pass-thru option under TB security. Alas, it made no difference when attempting to boot. Disabling iGPU also made no difference as I would still get the 5 beeps from the motherboard telling me there is no display. The only thing that did work was using the DP from the GPU to my UHD monitor. Then using TB from TR to 4K UltraFine then looped out to my TS3 Plus dock. I tested without WEG, but I was only able to get the UHD DP (GPU) monitor to activate. I also tested this with the Pike R black screen patch, but it was still a no go. TB bus was always detected along with the UltraFine monitor, but it would not activate without WEG. I can live with this configuration, but my quest still remains... all video over TB. For my machine, it does not matter what I have plugged into the Titan Ridge card, if there's no monitor plugged directly in to the GPU, the Aorus Master does not detect a display. Again, this is not the behavior with non-patched Titan Ridge firmware. I can run everything over TB without issue.

 

[WhosMac]

Try reseating all PCIe devices and reconnecting all cables.

If that doesn't help, try removing all PCIe devices one by one. We can even more GPU and set Platform ID to 0x3E9B0007 and connect monitor to on-board HDMI or Thunderbolt port.

View attachment 468791

After reseating all PCIe and RAM sticks, I’m back to booting to bios however I set up my BIOS on f9b again and made all necc changes to bios, however when I attempt to boot into macOS my verbose just reads

++++++++++++++++++_

searching thru the thread I came to your post @CaseySJ mentioning to unlock the MSR again since I had native NVRam, I went thru and unlocked again successfully but when attempting to boot I’m still sitting at

++++++++++++++++++_

And won’t proceed forward