Contribute
Register

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

Hi CaseySJ,
I have followed your guide up until the post installation part but my system report is very different from yours. The only difference from your build is that I don't have the Broadcom module installed yet and my CPU is 9900k. Also I can't see iGPU in the graphics/displays section. Please see the attached photos
 

Attachments

  • Screen Shot 2019-04-22 at 12.39.40 PM.png
    Screen Shot 2019-04-22 at 12.39.40 PM.png
    383.9 KB · Views: 91
  • Screen Shot 2019-04-22 at 12.39.54 PM.png
    Screen Shot 2019-04-22 at 12.39.54 PM.png
    324.3 KB · Views: 105
  • Screen Shot 2019-04-22 at 12.40.13 PM.png
    Screen Shot 2019-04-22 at 12.40.13 PM.png
    347.1 KB · Views: 92
  • Screen Shot 2019-04-22 at 12.40.53 PM.png
    Screen Shot 2019-04-22 at 12.40.53 PM.png
    396.5 KB · Views: 105
  • Screen Shot 2019-04-22 at 12.41.17 PM.png
    Screen Shot 2019-04-22 at 12.41.17 PM.png
    455.6 KB · Views: 88
  • Screen Shot 2019-04-22 at 12.41.43 PM.png
    Screen Shot 2019-04-22 at 12.41.43 PM.png
    456.7 KB · Views: 100
Last edited:
Knowing Apple, the new rumored 6K Thunderbolt Display will likely merit the very definition of ‘sticker shock’! It should, however, include fairly good speakers, a FaceTime camera, a USB hub, Thunderbolt daisy chaining port, and ability to charge a connected device — all via a single TB3 cable.

Since you are using osxAptioFix2Drv-free2000 for example (and not the usual AptioMemoryFix) and also a lot SSDTs are necessary, do you think the board is future proof, at least as far as it’s possible for a hackintosh?
 
Hi CaseySJ,
I have followed your guide up until the post installation part but my system report is very different from yours. The only difference from your build is that I don't have the Broadcom module installed yet and my CPU is 9900k. Also I can't see iGPU in the graphics/displays section. Please see the attached photos
Hello ahmadno,

Your screenshots are correct. The iGPU will not appear in Graphics/Displays once “Inject Intel” is unchecked (as it should be). The preferred way to check iGPU working status is by running IORegistryExplorer, scrolling the device tree until you see “IGPU” and seeing whether “AppleIntelFramebuffer...” appears as a child node.
 
Hello ahmadno,

Your screenshots are correct. The iGPU will not appear in Graphics/Displays once “Inject Intel” is unchecked (as it should be). The preferred way to check iGPU working status is by running IORegistryExplorer, scrolling the device tree until you see “IGPU” and seeing whether “AppleIntelFramebuffer...” appears as a child node.

Thanks, from the attached screen shot it looks like it's working.

I have another question: in my previous builds I used to be able to monitor fan speed for the gpu and motherboard fans using either istat menus or hwmonitor. If I recall correctly one of the FakeSMC sensor kexts is responsible for reporting these values but for some reason it's not working with this build.

Also, I'm able to read GPU statistics using the following command
ioreg -l |grep \"PerformanceStatistics\" | cut -d '{' -f 2 | tr '|' ',' | tr -d '}' | tr ',' '\n'|grep 'Temp\|Fan\|Clock'
"Fan Speed(%)"=17

"Core Clock(MHz)"=725

"Memory Clock(MHz)"=2000

"Fan Speed(RPM)"=797

"Temperature(C)"=48


Thanks again!
 

Attachments

  • Screen Shot 2019-04-22 at 5.11.46 PM.png
    Screen Shot 2019-04-22 at 5.11.46 PM.png
    905.9 KB · Views: 56
Since you are using osxAptioFix2Drv-free2000 for example (and not the usual AptioMemoryFix) and also a lot SSDTs are necessary, do you think the board is future proof, at least as far as it’s possible for a hackintosh?
There are two not-necessarily-true assumptions underlying your question:
  • Use of OsxAptioFix2Drv-free2000 is not necessarily a future bottleneck. AptioMemoryFix simply doesn’t work on this motherboard once PCIe cards are installed, which speaks volumes about the robustness of that driver. Despite the shortcomings of OsxAptioFix2Drv-free2000, it is the only memory fix driver that works on this motherboard at the moment. We’ll test future versions of AptioMemoryFix (and others) and switch to the best available driver at the appropriate time.
  • Having multiple SSDTs is also immaterial to future bottlenecking. There is one SSDT for Thunderbolt hot-plug, one generic SSDT-DTPG to copy Apple’s own implementation, a USB SSDT, an RX 580 informational SSDT, and a SSDT to disable the incompatible built-in Intel CNVi WiFi/BT card. None presents an impediment to the system’s longevity.
But nothing has infinite longevity. The real question is whether this system can remain current for a number of years. Apple can always make it harder to install future updates of MacOS, but barring software lockdowns, the hardware is ready for the long haul.
 
Hey Guys,

An initial test (20 minutes of recording) worked on the Presonus Quantum via the Apple Thunderbolt 3/2 Adapter straight to the TB3 connector on the Designare...
May it work Whit Titan Ridge Add-on Pcie card and the DSDT?
 
May it work Whit Titan Ridge Add-on Pcie card and the DSDT?
There's a very good chance that it will work with GC-Titan Ridge add-in-card. Note, however, that Thunderbolt add-in-cards require Windows for initiation from a full power-down state, meaning:
  • Run Windows and install Thunderbolt driver to initialize the card.
  • Now you can reboot into MacOS and use the card.
  • You can shutdown and restart MacOS and still use the card.
  • But if you do a full power-down (pull power cable from the wall or flip the power switch on power supply) you will need to run Windows again to initialize the card.
 
There's a very good chance that it will work with GC-Titan Ridge add-in-card. Note, however, that Thunderbolt add-in-cards require Windows for initiation from a full power-down state, meaning:
  • Run Windows and install Thunderbolt driver to initialize the card.
  • Now you can reboot into MacOS and use the card.
  • You can shutdown and restart MacOS and still use the card.
  • But if you do a full power-down (pull power cable from the wall or flip the power switch on power supply) you will need to run Windows again to initialize the card.
Thats very strange, im using titan ridge Pcie, and on a full power down, whit the DSDT it gets reconized on System, but i cant say it works, because i got an atelope orion studio rev2017 TB, and antelope doesent works whit hakintosh, but even whit a Full Power Down Antelope Thunderbolt Still gets reconized on IORegistryEsplorer, i will try with Full Power Down to se if the antelope Interface gets fully regonized on the Panel System, (Sorry About my English i am Brazilian)
 
Hi CaseySJ
i actually had a weird issue today. I started to install different software and preparing this new PC for being my main one and i had to restart the computer in order to finish a software installation.
When the computer restarted, i was presented a different Clover (Grey background, small icons). but still with the same option, start from Mojave drive, start from preebot, etc.. i don't remember exactly which option but anyway i choosed "Start from Mojave" but i got a crossed white circle. Every other option available produced the same result.
So i restarted from the USB stick i used for the installation and was presented an other Clover page (similar to the one i saw when doing the installation), chose "Start from Mojave" and then it worked.

So it look like i did something wrong. I tried to Inject Audio 16 by copying the XML above the <key>USB</key> but i messed up i guess. i then re-opened my config.plist to delete it, and now it boot correctly.
Lesson learned, i have to be very careful when editing such things... so if you can maybe give me a screenshot about how this Audio 16 xml should look like?
 
Hi CaseySJ
i actually had a weird issue today. I started to install different software and preparing this new PC for being my main one and i had to restart the computer in order to finish a software installation.
When the computer restarted, i was presented a different Clover (Grey background, small icons). but still with the same option, start from Mojave drive, start from preebot, etc.. i don't remember exactly which option but anyway i choosed "Start from Mojave" but i got a crossed white circle. Every other option available produced the same result.
So i restarted from the USB stick i used for the installation and was presented an other Clover page (similar to the one i saw when doing the installation), chose "Start from Mojave" and then it worked.

So it look like i did something wrong. I tried to Inject Audio 16 by copying the XML above the <key>USB</key> but i messed up i guess. i then re-opened my config.plist to delete it, and now it boot correctly.
Lesson learned, i have to be very careful when editing such things... so if you can maybe give me a screenshot about how this Audio 16 xml should look like?
When we run the standalone Clover installer, it applies the "embedded" theme instead of the "tonymacx86" theme. The "embedded" theme has the gray background and small icons. We can always change the theme in Clover Configurator --> GUI by specifying the name of the preferred theme.

Yes we have to be very careful about modifying config.plist directly. After any manual edit, it's a good idea to open the file in Clover Configurator. If there are any errors, Clover Configurator will inform you right away. If you like you may post your config.plist (remove serial numbers from SMBIOS) and I can edit it for you.
 
Back
Top