Contribute
Register

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

CaseySJ said:
Some things to try (with WEG 1.3.6):
  • In Boot Arguments, change shikigva=32 to shikigva=16. Make no other changes, reboot, and test.
  • In Boot Arguments, after changing shikigva, try deleting shiki-id. Reboot and test.
  • What is the power rating of your PSU? 750W or more?
Click to expand...
Hey hey. Thanks again.
Nothing seemed to work with those changes above. This was an install that’s been through a few OS versions and a major hardware change. I bit the bullet and abandoned my upgrade install and started with a fresh install that seems to be working fine now. Haven’t had any audio glitching (uad stuff working fine), or any app crashes yet so far, but need to test things a bunch more. Audio and video seems to be working great.

i followed your Catalina fresh install mini guide exactly, but was unable to boot with the quirks and fw files you had in the EFI folder. I had to replace them with aptio2000 to be able to boot. Not sure if I should try other drivers in clover or not at this point.

Going to try and test things properly and use the machine to see how things work out, but as of now it feels and acts more like it should. maybe Some gremlins in the upgrade path installation it seems. No idea what tbough .

thanks very much once again.
 
iMac 19,1
Z390 DESIGNARE |  i9 9900K |  Radeon RX 5700 XT OC 8GB
pitt1717 said:
You guys are crazy, and this is so interesting. I wish I knew how to do all this. Can I ask a question? Does this need to be done for each new BIOS?
So, Casey, if you're on f8, and I'm on f9b, as an example, and I use your DDST/SSDT, would I be missing feature, or possibly introduce issues?
Click to expand...
i have f9b firmware and it's ok for me
 
batwings said:
Thank you @CaseySJ for the excellent guide. I followed and was up and running way faster than my first hackintosh, so cheers :clap:

I used a Samsung 970 EVO for my OS drive and upon testing the speed post-installation, I noticed it was significantly slower than expected (see attachments). I can't figure out why the link width is stuck at x1. I searched this thread and saw your comment here and decided that perhaps the fact that I had the NVMe SSD installed in the M2P slot, the PCI lanes may be limited.

So, I popped the SSD out of M2P and put it into M2M, moved my SATA drives to S1/S2/S3. But this led to the issue of that drive not being recognized at all; in BIOS, there are no NVMe devices... I swapped it back to M2P and it booted back up (interestingly now it has a Link Width of x2 ‍:think: - Screenshot also attached).

Can someone help me understand why I wouldn't be able to swap the SSD from M2P to M2M? Do I need to start over with SSD installed at M2M
Click to expand...


Which firmware have you got (motherboard)
 
Last edited:
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...
@Elias64Fr

I used SSDT-HPLog.aml to try to determine the Hotplug GPE for Designare Z390 as follows:
  • Renamed all _Lxx and _Exx methods in GPE to XLxx and XExx.
  • Installed SSDT-HPLog.aml:
Code: 
/*
* Intel ACPI Component Architecture
* AML/ASL+ Disassembler version 20180427 (64-bit version)(RM)
* Copyright (c) 2000 - 2018 Intel Corporation
*
* Disassembling to non-symbolic legacy ASL operators
*
* Disassembly of iASLybUS8I.aml, Mon Jan 20 05:27:24 2020
*
* Original Table Header:
*     Signature        "SSDT"
*     Length           0x00000154 (340)
*     Revision         0x02
*     Checksum         0x29
*     OEM ID           "OSY86 "
*     OEM Table ID     "HPLog"
*     OEM Revision     0x00001000 (4096)
*     Compiler ID      "INTL"
*     Compiler Version 0x20190405 (538510341)
*/
DefinitionBlock ("", "SSDT", 2, "OSY86 ", "HPLog", 0x00001000)
{
    External (_GPE.XE17, MethodObj)    // 0 Arguments (from opcode)
    External (_GPE.XL12, MethodObj)    // 0 Arguments (from opcode)
    External (_GPE.XL61, MethodObj)    // 0 Arguments (from opcode)
    External (_GPE.XL62, MethodObj)    // 0 Arguments (from opcode)
    External (_GPE.XL66, MethodObj)    // 0 Arguments (from opcode)
    External (_GPE.XL69, MethodObj)    // 0 Arguments (from opcode)
    External (_GPE.XL6F, MethodObj)    // 0 Arguments (from opcode)
    External (RMDT.P1__, MethodObj)    // 1 Arguments (from opcode)

    Scope (_GPE)
    {
        Method (_L69, 0, Serialized)  // _Lxx: Level-Triggered GPE
        {
            \RMDT.P1 ("_L69")
            XL69 ()
        }

        Method (_L61, 0, NotSerialized)  // _Lxx: Level-Triggered GPE
        {
            \RMDT.P1 ("_L61")
            XL61 ()
        }

        Method (_L62, 0, NotSerialized)  // _Lxx: Level-Triggered GPE
        {
            \RMDT.P1 ("_L62")
            XL62 ()
        }

        Method (_L66, 0, NotSerialized)  // _Lxx: Level-Triggered GPE
        {
            \RMDT.P1 ("_L66")
            XL66 ()
        }

        Method (_L12, 0, NotSerialized)  // _Lxx: Level-Triggered GPE
        {
            \RMDT.P1 ("_L12")
            XL12 ()
        }

        Method (_L6F, 0, NotSerialized)  // _Lxx: Level-Triggered GPE
        {
            \RMDT.P1 ("_L6F")
            XL6F ()
        }

        Method (_E17, 0, NotSerialized)  // _Exx: Edge-Triggered GPE
        {
            \RMDT.P1 ("_E17")
            XE17 ()
        }
    }
}
  • Then I checked for Hotplug GPE by typing log stream --process 0 | grep ACPI three times as follows:
    1. After installing SSDT-TbtOnPch-Designare-Draft04.aml
    2. After installing the standard SSDT-Z390-DESIGNARE-TB3HP-V4.aml (where hotplug works)
    3. After deleting both of these SSDTs (no Thunderbolt SSDT used in this case)
For cases 2 and 3, I changed RP05.XINI back to RP05._INI. Unfortunately I did not see any GPE events after unplugging and replugging my Thunderbolt 3 dock.


UPDATE:
  • Hot plug GPE event _E17 was successfully logged after Case 1 (with SSDT-TbtOnPch-Designare-Draft04). See screenshot below. But system locked up after hotplug.
  • No hot plug GPE event logged after Cases 2 and 3.
Anyway, getting hot plug to work is secondary. I am providing this information in case it's helpful to understanding why the full Thunderbolt device tree, Thunderbolt Bus, and Local Node are not yet operational.

First priority is to enable Thunderbolt Bus and Local Node. Fixing Hotplug should be done afterwards.

IMG_0566_resize.jpg
 
Last edited:
digumo said:
Just posting this for anyone still running Mojave with this setup and wondering if the latest of AppleALC, Lilu and WEG caused any issues. Good news.... not on my machine. Hopefully, not on yours either.
Click to expand...


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)
 
So on my day off I figured I would do some reading and see if I can figure out how to get headless working with the iGPU. trying to familiarize myself with IORegExp, I see something a bit off and wondering if its an issue or not. can someone take a look and possibly explain?
 

Attachments

  • Screen Shot 2020-01-20 at 10.19.07 AM.png
    Screen Shot 2020-01-20 at 10.19.07 AM.png
    112.1 KB · Views: 87
pitt1717 said:
So on my day off I figured I would do some reading and see if I can figure out how to get headless working with the igpu. trying to familiarize myself with IORegExp, I see something a bit off and wondering if its an issue or not. can someone take a look and possibly explain?
Click to expand...
That is perfectly normal. Certain child nodes will be terminated and reestablished dynamically as needed. The driver in the screenshot is for AMD discrete GPU.
 
batwings said:
Thank you @CaseySJ for the excellent guide. I followed and was up and running way faster than my first hackintosh, so cheers :clap:

I used a Samsung 970 EVO for my OS drive and upon testing the speed post-installation, I noticed it was significantly slower than expected (see attachments). I can't figure out why the link width is stuck at x1. I searched this thread and saw your comment here and decided that perhaps the fact that I had the NVMe SSD installed in the M2P slot, the PCI lanes may be limited.
Click to expand...
I actually made an error in that linked post! Only the bottom long slot can be switched between CPU lanes and PCH lanes.
So, I popped the SSD out of M2P and put it into M2M, moved my SATA drives to S1/S2/S3. But this led to the issue of that drive not being recognized at all; in BIOS, there are no NVMe devices... I swapped it back to M2P and it booted back up (interestingly now it has a Link Width of x2 ‍:think: - Screenshot also attached).

Can someone help me understand why I wouldn't be able to swap the SSD from M2P to M2M? Do I need to start over with SSD installed at M2M
Click to expand...
It almost seems like a problem with the NVMe drive itself. Before returning or replacing it, please try updating its firmware using Samsung Magician in Windows.
 
CaseySJ said:
That is perfectly normal. Certain child nodes will be terminated and reestablished dynamically as needed. The driver in the screenshot is for AMD discrete GPU.
Click to expand...

thanks. I actually just noticed that regexplorer is dynamic. while reading I saw more being built while others terminated as you said.
anyway, this may be a catch 22 thing.... without the IGPU being enabled in BIOS its not going to be seen in regexplorer. but turning it on causes a panic. awesome puzzle
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top