Contribute
Register

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

Interesting. I don't have a monitor but changing to gaming mode and turning off something else increased the UHD 630 to 31mb and included 3840x2160. Still shows display as 61” even though its a 49”, but still its a start. This is also with the original config.plist.
The original config.plist is not enabling the accelerated graphics driver. Instead, it is using the default VESA driver that is used for booting purposes. This default VESA driver:
  • Does not provide accelerated video
  • Does not show the full 1536MB VRAM
  • Does not produce HDMI audio
The only way to enable HDMI Audio through the iGPU is to configure the system so that the AppleIntelFramebuffer gets attached, instead of the default VESA driver.

The reason you are getting a black screen is because:
  • The AppleIntelFramebuffer is being attached with the new config.plist.
  • This video driver might be attempting to negotiate a resolution and frequency that your TV is not capable of producing. Therefore, you get the black screen.
    • Please see Page 22 and Page 105 of the Samsung owner's manual.
  • You may need to manually select a supported resolution from System Preferences --> Displays. The list of supported resolutions starts on Page 105.
  • You may also need a certified HDMI 1.4b or 2.0 cable if you wish to use full 4K UHD resolution. See Page 22 for HDMI cable criteria.
 
@sidhellman pretty please would you be willing to help us out and execute this command and upload the file?. You're the only one I know that got the new 2019 LG Ultrafine 5k and a Hackitosh with the Designare motherboard.

With your help we could find out if the monitor is using 1x DP1.4 or 2x DP1.2 streams. Thanks a lot!
Surely ! Will do, sorry had been late to respond. I am currently out traveling on work, will run this as soon as I return.
 
Hi guys,

Just updated to latest version of VirtualSMC 1.07, but system goes black at boot after the following:

busy timeout (60s): 'AppleACPICPU'

going back to VirtualSMC 1.06 works as usual

Thanks for your input!!

Hi,

Same here!

Installed only in de EFI partition.

1.06 is working
1.07 is not!

Is my older version of Clover the issue? I have 4934.
 
The AORUS Z370 Gaming 5 may map its USB ports differently from the Designare Z390. While I think you will find similarities between them, we cannot assume that the USB SSDT from one motherboard will work on another. I expect that the changes will be minimal, but because the chipset (Z370) is different from the Designare (Z390), the USB XHC controller ID might also be different. Fortunately, the process of creating a new USB SSDT is much simpler now and I recommend this easy and fun guide:
As for the RX 580 SSDT, it should be removed at the first sign of a problem. When updating from Clover 4xxx to Clover 5xxx, we must manually copy all the drivers from drivers64UEFI to drivers/UEFI. I am also experiencing similar fan behavior -- fans spin up a little bit past 50C. Fortunately I have three 140mm intake fans and three 140mm exhaust fans to keep the air flowing nicely inside the case. That's one way of dealing with this somewhat aggressive fan curve on the AMD GPU. But as long as the fans spin up a little bit past 50C, then no worries.
Removing the RX580 SSDT did not change the overheating problem. :(
 
Hi @CaseySJ,
Your guide has been awesome, thank you! Trying to wrap up post-installation stuff and for some reason running into two problems (might be related, might not):
-My TB3/USB-C connections are slow! Blackmagic Disk says my USB-C SSD connected to the Designare's USB-C connection is around 84mb/s write, 58.8mb/s read, which seems really slow! I've also attached a TB2 SSD via an adapter and gotten similar slow speeds;
-Both internal HDMI on the mobo and hdmi via USB-C doc is acting funky

Any ideas? I think I followed your instructions to the letter, but I must have missed something! Thanks again.
 

Attachments

  • config.plist
    9.6 KB · Views: 79
The original config.plist is not enabling the accelerated graphics driver. Instead, it is using the default VESA driver that is used for booting purposes. This default VESA driver:
  • Does not provide accelerated video
  • Does not show the full 1536MB VRAM
  • Does not produce HDMI audio
The only way to enable HDMI Audio through the iGPU is to configure the system so that the AppleIntelFramebuffer gets attached, instead of the default VESA driver.

The reason you are getting a black screen is because:
  • The AppleIntelFramebuffer is being attached with the new config.plist.
  • This video driver might be attempting to negotiate a resolution and frequency that your TV is not capable of producing. Therefore, you get the black screen.
    • Please see Page 22 and Page 105 of the Samsung owner's manual.
  • You may need to manually select a supported resolution from System Preferences --> Displays. The list of supported resolutions starts on Page 105.
  • You may also need a certified HDMI 1.4b or 2.0 cable if you wish to use full 4K UHD resolution. See Page 22 for HDMI cable criteria.
IT WORKS, AUDIO, ALL RESOLUTIONS, uhd 630 1536mb
THANK YOU!
I reset the TV setting to only gaming mode. turned off UHD color mode on the TV, and the Clover boot screen was scaled in 4K. I booted your config.plist, which you sent, and it booted right up with sound and all.

All week I've been trying long nights lol. USB dosen't work anymore but I think I may have to re map them. Not a big issue. Anyone with a Samsung TV qled from 2017/2018 that has this issue needs to turn gaming mode on and UHD color mode off.
 
IT WORKS, AUDIO, ALL RESOLUTIONS, uhd 630 1536mb
THANK YOU!
I reset the TV setting to only gaming mode. turned off UHD color mode on the TV, and the Clover boot screen was scaled in 4K. I booted your config.plist, which you sent, and it booted right up with sound and all. All week I've been trying long nights lol.
Glad to hear it! So it was HDMI Ultra Deep Color that confused the Mac. Samsung calls it UHD Color Mode, so it seems there's no standard term for it.
USB dosen't work anymore but I think I may have to re map them. Not a big issue. Anyone with a Samsung TV qled from 2017/2018 that has this issue needs to turn gaming mode on and UHD color mode off.
The brief amount of time spent creating a custom USB SSDT will pay off for years to come! Guide:
 
Last edited:
Glad to hear it! So it was HDM Ultra Deep Color that confused the Mac. Samsung calls it UHD Color Mode, so it seems there's no standard term for it.

The brief amount of time spent creating a custom USB SSDT will pay off for years to come! Guide:
B5640BD9-0A2B-4911-886C-19C3FFC88D68.jpeg
This is HDMI UHD color.
IDK why, but it was throwing everything off.
But USB still works after my SSDT which I created a couple days ago. It's just my TimeMachine backup drive I had made I'm assuming is dead.
 
I have the AIO cooler mounted on the front of the case blowing through the radiator into the case. Maybe the cooler should be mounted on the top blowing out?

So your moving outside air across the radiator into the case? That's crazy!
Push the heat from the radiator OUT of the case, either out the front or top
 
It's only necessary to change RP05 to RP21. All child-node names must remain unchanged. However, this has less than 0.00000001% chance of fixing Thunderbolt 1 issues!! :) Because if that problem is due to Legacy Mode being disabled on Titan Ridge, then changing device ID won't help.


Are you using the GC-Titan Ridge or GC-Alpine Ridge card on your motherboard?

GC-Alpine Ridge may actually work with Thunderbolt 1 devices.

As for your UAD Apollo 8 Quad, in my experience motherboards with built-in Thunderbolt seem to be most reliable in the hot swap department.

Gah! It just occurred to me that perhaps I should remove the Titan Ridge TB card and put the Alpine Ridge Card back in to see if I can repower the Apollo 8 Thunderbolt 2 device: Former, pre-hack Thunderbolt device chain:
Mac Mini 2012 [Thunderbolt 10 Gb/s x2] ↔︎ BMD MultiDock (4x SSD) Thunderbolt 2 ↔︎ UAD Apollo 8 Quad Thunderbolt 2. -daisy chained; the UAD is at the end.

I could try this and see if the round trip latency in Pro Tools is the same as when the devices are on separate Thunderbolt ports (using two Apple TB2 ➝ TB 3 dongles.) as the Titan Ridge card. My prediction is that since the outboard devices are both Thunderbolt 2, I may never saturate the bus. Please bump this if you feel it is OT, but I'm in the market for this very build of yours.
 
Back
Top