Contribute
Register

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

manfriday

manfriday

Joined
Jul 21, 2011
Messages
169
Motherboard
Gigabyte Z390 Designare
CPU
i9-9900K
Graphics
Vega 56
So this is new.
Dont know when exactly it happened as it didnt show status as unavailable until I did a refresh. :/
Not sure if this is an OpenCore Issue, a SSDT issue or what.



Screen Shot 2020-01-20 at 12.24.07 PM.png


My boot args are:
slide=0 keepsyms=1 dart=0 alcid=11 shikigva=16 agdpmod=pikera
 
My Build
Z390 DESIGNARE |  i9 9900K |  Vega 56 8GB
rankrotten

rankrotten

Joined
Mar 31, 2010
Messages
146
Motherboard
Gigabyte Aorus Z390 Pro
CPU
i9-9900KS
Graphics
RX 5700 XT
CODYQX4 said:
I use an i9-9900K and no problems with this build. If anything it probably is less likely to have issues as the iMac19,1 uses an i9-9900K.

I don't know about the 9900KS variant though.
Click to expand...
9900KS runs fine in my Z390 Aorus Pro. Idles at 4.1GHz 26C and turbos across all cores to 5GHz. No issues.

Thanks for the idea of doing a clear_CMOS by shorting the motherboard pins to reset the memmap as I now have the iGPU loaded consistently alongside the 5700XT
www.tonymacx86.com

[SUCCESS] blouse's "Hack Pro" :: i9-9900K + Z390 Aorus Pro + Vega 64 + TB3 + USB3 :: 100% working

Awesome Build Guide! Yet I'm still having problems. I'm hoping someone can help quickly, I'm on kind of a time crunch! I'm in the Navy, my house is in Louisiana and I'm stationed in California. The Hackintosh at issue is used as a Home Server/Plex Media Server and I'm leaving to go back to...
www.tonymacx86.com www.tonymacx86.com
 
RentColours

RentColours

Joined
Feb 25, 2019
Messages
13
Motherboard
Gigabyte Z390 Designare
CPU
i9-9900KS
Graphics
Shappire RX 5700 TX
Mac
  1. MacBook Pro
rankrotten said:
9900KS runs fine in my Z390 Aorus Pro. Idles at 4.1GHz 26C and turbos across all cores to 5GHz. No issues.
Click to expand...
Yeo, I can confirm, my i9-9900KS in both hackintosh builds works a treat.
 
Photo + Video editor (4k/6k) | I9 9900KS + 64gb ram + Shappire 8gb RX 5700 XT + 2x 2tb Samsung Evo Plus m.2
Z390 DESIGNARE |  i9 9900K |  Radeon Nitro+ RX 5700 XT 8GB
Chevron

Chevron

Joined
Dec 23, 2019
Messages
43
Motherboard
Gigabyte Z390 Designare
CPU
i9-9900KS
Graphics
RX 580
rankrotten said:
9900KS runs fine in my Z390 Aorus Pro. Idles at 4.1GHz 26C and turbos across all cores to 5GHz. No issues.
Click to expand...

What CPU cooler are you using to get an idle temp of 26C?

I can also confirm that the i9-9900KS is working well with Z390 Designare.
 
digumo

digumo

Joined
Aug 2, 2019
Messages
112
Motherboard
Gigabyte Z390 Designare
CPU
i9-9900K
Graphics
Radeon VII
mobi said:
No issues here in Mojave with latest updates, my only gripe was with USBinjectAll 074 messed my system ( seems it was a bogus release it's not available anymore)
Click to expand...

For those who are interested, my update routine is to take things in stages. Since I've been reading this thread you see so many issues which can be tied to one specific thing. So, being a developer, you only test one thing at at time. I start with updating just Lilu and Weg, then restart. Then repeat the process with AppleALC and then do it with VirtualSMC.

The last thing I try is something like USBInjectAll. The reason for this is that either Lilu or Weg are more likely to have updates that might impact your machine. For things like USB mapping @CaseySJ has pretty much solved that for this board. So, unless there is something in the docs of the release which gives you good reason to update it, I hold off.

So, now you're wondering, where do I see the docs for the new release of each kext. Hackintool is your friend!

Go to the Installed section then right-click on the URL section. You can then look at the release notes on the Github page for each release. Hope this helps with those learning.
 

Attachments

  • Hackintool Kext Release Info.png
    Hackintool Kext Release Info.png
    244.8 KB · Views: 63
RentColours

RentColours

Joined
Feb 25, 2019
Messages
13
Motherboard
Gigabyte Z390 Designare
CPU
i9-9900KS
Graphics
Shappire RX 5700 TX
Mac
  1. MacBook Pro
Chevron said:
What CPU cooler are you using to get an idle temp of 26C?

I can also confirm that the 9900ks is working well with Z390 Designare.
Click to expand...
I use the Fractal Celsius S36, and it rules.
 
Photo + Video editor (4k/6k) | I9 9900KS + 64gb ram + Shappire 8gb RX 5700 XT + 2x 2tb Samsung Evo Plus m.2
Z390 DESIGNARE |  i9 9900K |  Radeon Nitro+ RX 5700 XT 8GB
JayShay

JayShay

Joined
Jun 1, 2018
Messages
50
Motherboard
Designare
CPU
9900K
Graphics
Radeon VII
Hey Guys,

I reinstalled my system with Catalina and everything works fine except IGPU on the designare. Although I have a Radeon VII, I have 2 LG 4K's and 1 LG 5K, and I cannot get the third one working through the Alpine Ridge add on card reliably. I want to run one of them off the intel IGPU but it is not detected anywhere and nothing works when it's plugged in. I have latest WEG and lilu. Before, I just remember turning on IGPU in bios, and injecting intel. Is there something I'm missing to get iGPU working?

Thanks
 

Attachments

  • Screen Shot 2020-01-20 at 11.31.19 AM.png
    Screen Shot 2020-01-20 at 11.31.19 AM.png
    527.9 KB · Views: 58
  • Screen Shot 2020-01-20 at 11.32.40 AM.png
    Screen Shot 2020-01-20 at 11.32.40 AM.png
    679.5 KB · Views: 54
  • Screen Shot 2020-01-20 at 11.31.27 AM.png
    Screen Shot 2020-01-20 at 11.31.27 AM.png
    538.6 KB · Views: 58
Elias64Fr

Elias64Fr

Joined
Jan 1, 2020
Messages
324
Motherboard
Gigabyte Z390 Designare
CPU
i5-9600K
Graphics
RX 5700 XT
Mac
  1. iMac
  2. MacBook Pro
  3. Mac mini
Mobile Phone
  1. Android
CaseySJ said:
Much better result now!!
Code: 
e*)> ACPIDebug: Version 0.1.4 starting on OS X Darwin 19.2
ACPIDebug: 0x40039854
ACPIDebug: 0xe00e4000
ACPIDebug: 0xe0800000
ACPIDebug: 0xe0900000
ACPIDebug: 0xe0908000
ACPIDebug: 0xe0910000
ACPIDebug: 0xe0920000
ACPIDebug: 0xe0a00000
ACPIDebug: "_INI Root Port"
ACPIDebug: "ICMBoot"
ACPIDebug: "Tbt TWIN set to One"
ACPIDebug: "Tbt Force Power with FPG0"
ACPIDebug: "Up Stream VID/DID =0000000015EA8086"
ACPIDebug: "Delay to appear = 184 us"
ACPIDebug: "ICMS"
ACPIDebug: "ICME_0="
ACPIDebug: 0xffffffff
ACPIDebug: "Configure NHI called"
ACPIDebug: "Configure NHI RP OK!"
ACPIDebug: "Configure NHI UPSB OK!"
ACPIDebug: "Configure NHI Dp 0 done"
ACPIDebug: "Configure NHI Dp 3 done"
ACPIDebug: "Configure NHI Dp 4 done"
ACPIDebug: "Configure NHI Dp 5 done"
ACPIDebug: "Configure NHI DPs done"
ACPIDebug: "Configure NHI0 all done"
ACPIDebug: "Configure NHI End"
ACPIDebug: "ICME_1="
ACPIDebug: 0x800001a7
ACPIDebug: "ICME_2="
ACPIDebug: 0x800001a7
ACPIDebug: "ICME_3="
ACPIDebug: 0x800001a7
ACPIDebug: 0x800003f0
ACPIDebug: "ICME_4="
ACPIDebug: 0x800001a7
ACPIDebug: "ISTA="
ACPIDebug: 0x800003f0
ACPIDebug: "Configuration delay = 1004 ms"
ACPIDebug: "_PS0 RP05"
ACPIDebug: "PCEU RP05"
ACPIDebug: "PCEU RP05- Put upstream bridge back into D0 "
ACPIDebug: "_PS0 UPSB"
ACPIDebug: "PCED UPSB"
ACPIDebug: "PCED - enable GPIO"
ACPIDebug: "UGIO - PCI wants on"
ACPIDebug: "UGIO - NHI wants on"
ACPIDebug: "UGIO - XHCI wants on"
ACPIDebug: "UGIO - TBT forced on"
ACPIDebug: "RTPC NHI0 called with arg: 0000000000000000"
ACPIDebug: "_PS3 NHI0, Nothing to do!"
ACPIDebug: "_PS3 DSB0"
ACPIDebug: "PCDA DSB0"
ACPIDebug: "POFF DSB0"
ACPIDebug: "PCDA DSB0- Put upstream bridge into D3"
ACPIDebug: "PCDA DSB0- Set link disable on upstream bridg
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- Wait for link to drop..."
ACPIDebug: "PCDA DSB0- disable GPIO"
ACPIDebug: "UGIO - PCI wants on"
ACPIDebug: "UGIO - NHI wants off"
ACPIDebug: "UGIO - XHCI wants on"
ACPIDebug: "UGIO - TBT allows off"
ACPIDebug: "UGIO - USB forced on"
ACPIDebug: "UGIO - TBT GPIO should be off"
ACPIDebug: "UGIO - USB GPIO should be on"
ACPIDebug: "UGIO - Make sure TBT & USBC is on"
Here's the RP05 output (no Thunderbolt Local Node yet!)...
View attachment 445756

UPDATE:
The list above shows that devices connected to the various USB and Ethernet ports are not being activated (no child nodes in the tree above). The complete set of devices (will all child nodes) should look like this (OWC 14-Port Thunderbolt 3 Dock):

View attachment 445804 View attachment 445805

We're getting closer!!
Click to expand...
Hi CaseySJ

On ACPIDebug log, it seem to work until "UGIO - TBT forced on" , after we shall have just after "UGIO - USB forced on" but nothing !
"RTPC NHI0 called with arg: 0000000000000000" is probably called by NHI driver few time later in order to request PowerState ..

First, after viewing iMac19,1 SSDT-TbtOnPch which has TitanRidge 15EA/15EB, many methods like PCED, PCDA, TRPE are very different. I have update testing file (SSDT-TbtOnPch-Designare_Draft04.aml) and you can test it.

In second time, I have simplified my SSDT-TbtOnPch to the maximum by removing all _PS3, _PS0, PCED and PCDA and ... on Asus Maximus, Thunderbolt device is correctly detected after Cold boot and Hot boot and ... full view of thunderbolt NHI tree appear ! :headbang: ... ICMB, ICMS, CNHI, UPCK and UTLC to WTDL are required for this.
I have creating another file (SSDT-TbtOnPch-Designare_Simplified_Draft01.aml) to be tested.

About all devices not detected, I don't know, probably due to inappropriate methods from Alpine ridge device or XHC2 RHUB to be modified for Designare board (HSS1, HSS2, SSP1 and SSP2 address and configuration) ...

UPDATE: Also add the following device properties for NHI configuration on CLOVER 'extracted from iMac19,1 IoReg :

Device : PciRoot(0x0)/Pci(0x1c,0x4)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)
List of properties (Data type):
  1. TBTDPLowToHigh = 01000000
  2. TBTFlags = 03000000
  3. ThunderboltConfig = 00021c0002000503010004000503020003000503010000000303020001000200
  4. linkDetails = 0800000003000000
  5. pathcr = 0400000000000000000007001000100005000000000000000000070010001000010000000b000e000e000000000000000200000000000000000004000200010003000000000000000000070002000100
I have all of them (from iMac18,3) with custom ThunderboltUUID, this one is currently not required .. maybe for Thunderbolt ethernet function on another chapter :mrgreen:
 

Attachments

  • SSDT-TbtOnPch-Designare_Draft04.aml
    22.4 KB · Views: 87
  • SSDT-TbtOnPch-Designare_Simplified_Draft01.aml
    12.1 KB · Views: 68
Last edited:
CaseySJ

CaseySJ

Moderator
Joined
Nov 11, 2018
Messages
13,468
Motherboard
Gigabyte Z490 Vision D
CPU
i5-10400
Graphics
RX 580
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac Pro
Classic Mac
  1. Quadra
Mobile Phone
  1. iOS
JayShay said:
Hey Guys,

I reinstalled my system with Catalina and everything works fine except IGPU on the designare. Although I have a Radeon VII, I have 2 LG 4K's and 1 LG 5K, and I cannot get the third one working through the Alpine Ridge add on card reliably. I want to run one of them off the intel IGPU but it is not detected anywhere and nothing works when it's plugged in. I have latest WEG and lilu. Before, I just remember turning on IGPU in bios, and injecting intel. Is there something I'm missing to get iGPU working?

Thanks
Click to expand...
The iGPU is configured for headless operation (platform ID 0x3E980003) where it will not drive a display monitor. However, we can change platform ID to 0x3E9B0007 to enable the on-board video ports:
  • Thunderbolt port #1 (USB-C) can be used directly to drive a DisplayPort monitor.
  • Thunderbolt port #2 (USB-C) can be used directly to drive a DisplayPort monitor.
  • HDMI port. This requires additional framebuffer patching.
To drive a DisplayPort monitor, we can use a USB-C to DisplayPort cable such as this one.
To drive a HDMI monitor, I can modify your config.plist if you provide it here (you may remove serial numbers from SMBIOS).
 
CaseySJ

CaseySJ

Moderator
Joined
Nov 11, 2018
Messages
13,468
Motherboard
Gigabyte Z490 Vision D
CPU
i5-10400
Graphics
RX 580
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac Pro
Classic Mac
  1. Quadra
Mobile Phone
  1. iOS
Elias64Fr said:
Hi CaseySJ

On ACPIDebug log, it seem to work until "UGIO - TBT forced on" , after we shall have just after "UGIO - USB forced on" but nothing !
"RTPC NHI0 called with arg: 0000000000000000" is probably called by NHI driver few time later in order to request PowerState ..

First, after viewing iMac19,1 SSDT-TbtOnPch which has TitanRidge 15EA/15EB, many methods like PCED, PCDA, TRPE are very different. I have update testing file (SSDT-TbtOnPch-Designare_Draft04.aml) and you can test it.

In second time, I have simplified my SSDT-TbtOnPch to the maximum by removing all _PS3, _PS0, PCED and PCDA and ... on Asus Maximus, Thunderbolt device is correctly detected after Cold boot and Hot boot and ... full view of thunderbolt NHI tree appear ! :headbang: ... ICMB, ICMS, CNHI, UPCK and UTLC to WTDL are required for this.
I have creating another file (SSDT-TbtOnPch-Designare_Simplified_Draft01.aml) to be tested.

About all devices not detected, I don't know, probably due to inappropriate methods from Alpine ridge device or XHC2 RHUB to be modified for Designare board (HSS1, HSS2, SSP1 and SSP2 address and configuration) ...
Click to expand...
Hello @Elias64Fr

Thank you again for the updated files and the support you are providing!

I'll test the changes this evening when I return home. Some questions / comments:
  • You are right -- the ACPIDebug log seems to work until UGIO - TBT forced on, but after that we don't see UGIO - USB forced on.
  • In BIOS, I have Thunderbolt --> GPIO3 Force Power --> Enabled. Do you think this should be disabled?
  • By removing _PS3, _PS0, PCED, and PCDA we lose RTPC (Run Time Power Conservation). This is not a big deal because we don't have it right now anyway. But it would be nice to enable this feature eventually... (not a priority at this time).
  • Should I perform a cold boot with no Thunderbolt device connected when testing the new TbtOnPch SSDT? And then hot plug a Thunderbolt device?
  • Usually I perform a warm boot with my OWC 14-port Thunderbolt dock connected.
  • Also, I'm curious why PCIHotplugCapable is "Zero" instead of "One"...
  • Screen Shot 2020-01-20 at 12.37.49 PM.png
One thing to note about Apple computers with Titan Ridge controllers:
  • Apple's Titan Ridge Macs contain both a Titan Ridge controller and an Alpine Ridge controller.
  • I believe UPSB is Alpine Ridge and DSB0 (and everything under DSB0) is Titan Ridge.
  • This allows Apple to provide backward compatibility with Thunderbolt 1 devices (i.e. due to Alpine Ridge).
  • My understanding (which could be wrong) is that these Macs have a special MUX (multiplexer) that directs certain Thunderbolt traffic to either Alpine Ridge or Titan Ridge.
So if we look at Thunderbolt SSDT for a Titan Ridge Mac, it might contain some ACPI methods and fields that are related to the special MUX. Again, my understanding of this is limited, but I think it's important to at least mention this unique feature of real Macs.

UPDATE: I'll add these properties to NHI0:
  1. TBTDPLowToHigh
  2. TBTFlags
  3. ThunderboltConfig
  4. linkDetails
  5. pathcr
 
Last edited:
You must log in or register to reply here.
Copyright © 2010 - 2021 tonymacx86 LLC
Top