Contribute
Register

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

Hey @CaseySJ,

I haven't been experiencing any weird finder issues at all, so it must have been an anomaly.

Recently, I switched to the special 10.14.4 build and iMac 19.1 SMBIOS. While I totally understand that you can't provide support for switching to a different SMBIOS, I just wanted to ask: What does the "SSDT-Z390-DESIGNARE-RX580-V2" provided in your post installation package do?

When I have that SSDT in my EFI folder, VideoProc shows "Graphics" as AMD RX580 (which isn't right for headless mode). When I remove the SSDT and reboot, VideoProc correctly shows Intel UHD Graphics 630. In both cases, testing HVEC and H264 produced "green" results in VideoProc. Check out the attached screenshots below.
 

Attachments

  • WITH SSDT.png
    WITH SSDT.png
    96.4 KB · Views: 155
  • WITHOUT SSDT.png
    WITHOUT SSDT.png
    98.1 KB · Views: 134
Thank you for your quick answer.

I started my build, and weird thing is happening with F5 BIOS. Every time I disable CSM support, the computer never boots again... I have to reset the BIOS. I've tried many times by isolating each BIOS setting, and it is the CSM support that does it. Wonder what happens if I leave it at Enabled.
It’s okay to enable CSM.
 
Hey @CaseySJ,

I haven't been experiencing any weird finder issues at all, so it must have been an anomaly.

Recently, I switched to the special 10.14.4 build and iMac 19.1 SMBIOS. While I totally understand that you can't provide support for switching to a different SMBIOS, I just wanted to ask: What does the "SSDT-Z390-DESIGNARE-RX580-V2" provided in your post installation package do?

When I have that SSDT in my EFI folder, VideoProc shows "Graphics" as AMD RX580 (which isn't right for headless mode). When I remove the SSDT and reboot, VideoProc correctly shows Intel UHD Graphics 630. In both cases, testing HVEC and H264 produced "green" results in VideoProc. Check out the attached screenshots below.
The purpose of the SSDT is to rename the device from “RX 580” to “AMD RX 580” so that it is alphabetically ahead of “Intel UHD 630”. This allows many pro A/V apps to prioritize the more capable AMD GPU over the weaker IGPU. The SSDT also provides information about the RX 580 in the PCI page of System Information.

In headless mode the IGPU will still be used by macOS itself and many third party apps. Different third party apps can use different combinations of GPUs. Some apps might use both, others might use only one.

So if the specific apps that you use are not performing well with the SSDT in place, you can either delete the SSDT or I can provide the previous V1 that does not rename the RX 580.
 
Casey is there a how-to on doing this? I'm looking to do this for this build with the Radeon VII and another with the GTX 1080 Ti on a Z170X-UD5. That headless utilization makes a big difference.
 
The purpose of the SSDT is to rename the device from “RX 580” to “AMD RX 580” so that it is alphabetically ahead of “Intel UHD 630”. This allows many pro A/V apps to prioritize the more capable AMD GPU over the weaker IGPU. The SSDT also provides information about the RX 580 in the PCI page of System Information.

In headless mode the IGPU will still be used by macOS itself and many third party apps. Different third party apps can use different combinations of GPUs. Some apps might use both, others might use only one.

So if the specific apps that you use are not performing well with the SSDT in place, you can either delete the SSDT or I can provide the previous V1 that does not rename the RX 580.

Ah I see, that makes a lot of sense then. With the SSDT, VideoProc would be prioritizing the RX580 instead of the UHD630.

I think I'll try running without the SSDT for now, and if things get wonky I'll add the V2 one back in. Thanks for your help.
 
Casey is there a how-to on doing this? I'm looking to do this for this build with the Radeon VII and another with the GTX 1080TI on a z170x UD5. That headless utilization makes a big difference.
There are multiple ways of naming devices or assigning device properties. SSDT is one of those ways, but it is relatively complicated. An easier approach is described in this mini-guide:
 
You should keep DP 1.2 enabled, but if your monitor has a toggle option for MST or daisy-chaining, it should be turned off.

Are you booting the system with HDMI already connected to motherboard? Or you're connecting HDMI after Mojave has been booted and logged into? Feel free to upload your config.plist with serial numbers redacted.

From the last few posts it seems MSI and Sapphire RX 580s have fan-stop firmware. Fans don't spin until temperature approaches 60C.

Thanks for your reply. The interesting thing is, that I can boot into Windows with the same displays connected, same settings and everything works as expected (both displays 4k@60Hz). As soon as I reboot into MacOS only one Display shows something. Even worse: the login screen is off - looks like its on the zombie display which is black although MacOS recognises it. Is there anything I can do? Some kext?
I made screenshots of the state when I got TWO Displays connected - MacOS show THREE Displays but only the first one shows something:

403218


403220


Regarding the HDMI-freezes: that happens when I hot-plug the HDMI-Port.

Thanks a lot!
 

Attachments

  • config.plist
    8.8 KB · Views: 179
Last edited:
@CaseySJ Help...

The system that was previously installed with the guide is perfectly compatible with Magic Mouse 2 and Magic Trackpad 2. They can be used normally without dropping.

But today I updated the things in your document above. I restarted and found that Magic Trackpad 2 failed. It appears to be frequently disconnected. Occasionally normal, occasionally invalid. I don't know where I am going wrong?

Is it because the red part of the picture below is updated? I feel the difference is only here.
403236
 
Back
Top