Contribute
Register

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

WX7100 - macOS - Slot 1

RX580 - Windows - Slot 2

However, I use a secondary display connected to the RX580 in macOS. I could just move it to the WX7100 and disable the secondary gpu?
Yes, exactly.
 
@iRamon,

I also couldn't find anything wrong in the files you posted. Before you do anything further, please try this:
  • Download tbpatch (attached) to the Downloads folder and unzip.
  • In Terminal type this:
Bash:
cd ~/Downloads
chmod +x tbpatch
xattr -d com.apple.quarantine tbpatch
sudo ./tbpatch list
  • You should see something like this:
Code:
/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/RP05@1C,4/IOPP/UPSB@0/IOPP/DSB0@0/IOPP/NHI0@0/AppleThunderboltHAL/AppleThunderboltNHIType3/IOThunderboltController/IOThunderboltPort@7/IOThunderboltSwitchType3/IOThunderboltIECSNub/AppleHPMIECS/AppleHPMDevice@0
  Address : 0x00000000
  PID     : 0x2831454341
  UID     : <REDACTED>
  Version : 8
  Build   : a0566aa071c0a0cabf803a9532caee53ddd2ced5_03012018
  Device  : TPS65983 HW0030 FW0001.38.04 ZTBT1

/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG1@1,1/IOPP/UPSB@0/IOPP/DSB0@0/IOPP/NHI0@0/AppleThunderboltHAL/AppleThunderboltNHIType3/IOThunderboltController/IOThunderboltPort@7/IOThunderboltSwitchType3/IOThunderboltIECSNub/AppleHPMIECS/AppleHPMDevice@0
  Address : 0x00000000
  PID     : 0x2831454341
  UID     : <REDACTED>
  Version : 8
  Build   : 5a8f092c7306c3d9c0764d2f4f132044a8f0cedf_09042017
  Device  : TPS65983 HW0030 FW0001.38.03 ZTBT1
  • Notice the two <REDACTED> items above next to UID.
  • Copy the first UID to clipboard (CMD-C).
  • Then type this, but paste the UID as shown:
Bash:
sudo ./tbpatch dump -u paste-uid-here -o 0x4000 -s 0x400 -f TB3-Fw-Extract.bin
  • Use HexEdit to examine the resulting file TB3-Fw-Extract.bin and also post it here.
You just caught me in time! I was about to shut down my system for disassembling the motherboard and flashing the firmware ...

Thanks for the tbpatch suggestion. I just ran it, and it seems tbpatch can't find the controller device.

Output of tbpatch list:
Bash:
Invalid address: 0
Device /AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/RP05@1C,4/IOPP/UPSB@0/IOPP/DSB0@0/IOPP/NHI0@0/AppleThunderboltHAL/AppleThunderboltNHIType3/IOThunderboltController/IOThunderboltPort@7/IOThunderboltSwitchType3/IOThunderboltIECSNub/AppleHPMIECS/AppleHPMDevice@0 not added because failed to init.

Invalid address: 1
Device /AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/RP05@1C,4/IOPP/UPSB@0/IOPP/DSB0@0/IOPP/NHI0@0/AppleThunderboltHAL/AppleThunderboltNHIType3/IOThunderboltController/IOThunderboltPort@7/IOThunderboltSwitchType3/IOThunderboltIECSNub/AppleHPMIECS/AppleHPMDevice@1 not added because failed to init.

No devices found or not running as root![B]%[/B]
 
You just caught me in time! I was about to shut down my system for disassembling the motherboard and flashing the firmware ...

Thanks for the tbpatch suggestion. I just ran it, and it seems tbpatch can't find the controller device.

Output of tbpatch list:
Bash:
Invalid address: 0
Device /AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/RP05@1C,4/IOPP/UPSB@0/IOPP/DSB0@0/IOPP/NHI0@0/AppleThunderboltHAL/AppleThunderboltNHIType3/IOThunderboltController/IOThunderboltPort@7/IOThunderboltSwitchType3/IOThunderboltIECSNub/AppleHPMIECS/AppleHPMDevice@0 not added because failed to init.

Invalid address: 1
Device /AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/RP05@1C,4/IOPP/UPSB@0/IOPP/DSB0@0/IOPP/NHI0@0/AppleThunderboltHAL/AppleThunderboltNHIType3/IOThunderboltController/IOThunderboltPort@7/IOThunderboltSwitchType3/IOThunderboltIECSNub/AppleHPMIECS/AppleHPMDevice@1 not added because failed to init.

No devices found or not running as root![B]%[/B]
That pretty much confirms my suspicion. If the chip is flashed properly -- and assuming no physical or electrical damage -- then tbpatch would have worked. In fact, once chip is flashed properly, we can use tbpatch to restore the original firmware without using an external flasher. We can actually use tbpatch to make any additional modifications to the firmware as we wish.

At this point the options are limited:
  • Flash original firmware back to the chip.
  • But also look closely at the tiny surface-mount resistors/capacitors in the area. You took some exceptionally clear and close-up photos earlier. Check for any damage to those nearby components.
 
The SSDT should have fixed the fan issue it did for me at least I have an XFX Vega 64 Reference card.

Not sure why you got the panic that is kind of odd result.
My Vega 64(s) are both running at high fan if I use the KEXT. running with just the SSDT doesn't impact the fans, and does provide a performance boost on the he synthetic GB4/5 tests.
Tried the KEXT: RadeonBoost-v1-4+Vega.kext
 
@CaseySJ and others:
I need some help.

I flashed my AR AIC with EliasFr v1 Alpine Rdge ROM. The Apple Thunderbolt Display is connected via an Apple TB3 to TB2 dongle. The display, including the camera and mic, worked, but, when I tried to wake from sleep, the fans spun up but the display didn't light up. I used screen sharing, and, for about 30 sec after I woke the system the mouse was responsive, but after about a minute the screen sharing froze. I repeated this setup several times, to make sure it was a repeatable problem.

I went back to the ROM repository and decided to try NorthAmTransAm's flashed AR NVM21. I have a secondary monitor attached via DVI from my RX590, and a DP out from the 590 connected to DPin 1 on the AR. TB display is connected to TB1.

At the end of the boot, the secondary screen shows the desktop but the TB monitor remains black. Strangely, though, system report shows a fully populated TB bus, including showing the attached TB monitor. IOReg shows a fully populated tree on RP21, showing the monitor, FaceTime camera, and display audio on DSB1. So everything I know to check looks in order except for a black screen on the TB.

I am using the BIOS settings as you directed on page 1. (I have tried internal GFX enabled and disabled.) I am on BIOS 12d, which is the latest.

Attached is a screen shot of System Report--Thunderbolt and Graphics/Displays, IOReg, and my Clover folder. I've also attached the original AR ROM I extracted before I loaded the first modded ROM, in case it is slightly different than the one that Elias or NATA started with.

Thanks in advance.

Edit--the kexts in .../Clover/kexts/other/ folder are older than what are loaded from /L/E/ folder. But I just got religion and moved the kexts from /L/E/ to Clover and updated Lilu, WEG, and AppleALC. Still the same TB situation.

Edit 2--the camera, microphone, ethernet, and the speaker in the TB monitor all work. just not the video.

@faithie999

I decided to swap my flashed GC-Titan Ridge AIC with my flashed GC-Alpine Ridge AIC and swap the SSDTs for TB in my Z390 Aorus Pro to see if it duplicates your problems.

As you found the Apple TB Display was shown in Sys Info - Thunderbolt, but was never shown under Sys Info - Graphics/Displays. The built-in camera, USB, and Ethernet ports were active.

The GC-TR AIC uses 2x6 pin power plugs, while the GC-AR has none. Perhaps the Apple TB Display needs some extra power through the TB connector to display video?

I've reached a dead end on this issue. In my opinion it's just a compatibility issue with the GC-Alpine Ridge AIC.

I guess your best solution is to grab a Designare mobo while they are still available.

Good luck!
 
That pretty much confirms my suspicion. If the chip is flashed properly -- and assuming no physical or electrical damage -- then tbpatch would have worked. In fact, once chip is flashed properly, we can use tbpatch to restore the original firmware without using an external flasher. We can actually use tbpatch to make any additional modifications to the firmware as we wish.

At this point the options are limited:
  • Flash original firmware back to the chip.
  • But also look closely at the tiny surface-mount resistors/capacitors in the area. You took some exceptionally clear and close-up photos earlier. Check for any damage to those nearby components.
Ok, thanks! It's good (relatively speaking) to know the flash chip is at fault here.

I already had a gut feeling about the miniscule surface mounted components. They are so closely located to the chip that when closing the SOIC8 clip, the clip would scrape against them.

I'll disassemble my motherboard again and try flashing the original firmware back to the chip. And make pictures to spot possible damage to the surface mounted components ... they're too small for my eyes to see.

Let's see how this goes, I'll report back when I'm done.
 
I'm actually running dual LG 27 inch 4k on 10.15.4 with 5700 xt Pulse no problem. Have not had a single freeze or crash so far after disable 1.2 DP on my monitor setting. Both connected through DP.
So, were you having freezing issues with DP 1.2 or 1.4? Now you have it set to DP 1.1?
 
@gandem

Attached is the OC EFI. But keep in mind, the latest 0.5.7 has a bug, which can not boot Windows installed on same esp. The developers have fixed this, but I didn't upgrade yet.

Thank you for the info about RadeonBoast. This is huge improvement~~

截屏2020-04-27 01.18.25.png
 

Attachments

  • oc.zip
    3.4 MB · Views: 96
Last edited:
Because you have a Vega, it's necessary to copy the special version of Radeon Boost driver: RadeonBoost-v1-4+Vega.kext

Copy this into CLOVER/kexts/Other and reboot.
okay, did another run on tests and with RadeonBoost-v1-4+Vega.kext I got the following results:

GB4 no kext
Single and Multi 6207 / 37159
Open CL 165680
Metal :158214

GB5 no Kext
Single and Multi 1234 / 8885
Open CL 54625
Metal 62858

GB4 kext On
Single and Multi 6208 / 37319
Open CL 175920

GB5 Kext On
Single and Multi 1236 / 8902
Open CL 63114
Metal 71252
 
Is it normal for a system with a flashed motherboard and GC-Titan-Ridge add in card to only show the internal thunderbolt bus on a cold boot, but both busses on a warm boot? I consistently have that behavior and also a little system instability, so before I start simplifying the system to troubleshoot, thought I would ask in case the GC-Titan-Ridge configuration is still not 100%.
 
Back
Top