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

[SuDoDmz]

On my test bench I've been using Logitech wireless keyboard and mouse with no lag/stutter either with Clover or OpenCore.

I'm planning on going back to Logitech, too. For now I'm stuck with Corsair Dark Core and K70 Mk2 (not bad either). I also found out I'm not the only one experiencing those lags, but it's kinda hard to pin down and Isolate the problem.

 

[svandive]

I would like to send you one more version that has _PS0, _PS3, and all other power methods just to see if sudo tbpatch list will work even for a few seconds. After that we can stop the experiment.

I'm absolutely good with trying anything you need. If this can one day help provide a non-hardware (flashing firmware with external flashing solution) way of implementing the Local Node I'm all for it!!

 

[evlthoma]

So the problem is fixed now?

No change. Other machines still time out trying to connect to the hackintosh. I can remote in to the same physical hardware/machine when I boot into Windows or Ubuntu

 

[CaseySJ]

No change. Other machines still time out trying to connect to the hackintosh. I can remote in to the same physical hardware/machine when I boot into Windows or Ubuntu

Have you tried a different Ethernet cable? Cat 5e or better?

 

[svandive]

No change. Other machines still time out trying to connect to the hackintosh. I can remote in to the same physical hardware/machine when I boot into Windows or Ubuntu

Sorry you probably already said this, what is the 2nd machine you are trying to Ping from (to the hackintosh)?


Also can you run the command: netstat -lan |grep LISTEN
Just let me know if the TCP port 5900 is open like in the attached example picture from my machine.

 

[svandive]

strange on my designare i realise the second ethernet port has disappear but on windows is connected

most likely a missing IntelMausi or smalltree82576 kext

 

[evlthoma]

Have you tried a different Ethernet cable? Cat 5e or better?

I have a known good CAT6 connected and get the same result

 

[evlthoma]

Sorry you probably already said this, what is the 2nd machine you are trying to Ping from (to the hackintosh)?


Also can you run the command: netstat -lan |grep LISTEN
Just let me know if the TCP port 5900 is open like in the attached example picture from my machine.

I have been primarily been testing from my MacBook Pro, but get the same results from a Windows 10 box and a MacMini

Looks like TCP port 5900 is open to me:

I can remote into the physical machine when I boot the hack into Windows 10 or Ubuntu

 

[faithie999]

I've been carrying on tinkering with the SSDT-only approach to getting a full thunderbolt tree and have got as far as the very simple attached version which works great on built-in Alpine Ridge. It's based on the great work originally done by @Elias64Fr and @CaseySJ (all credit to them) and provides a full tree with working TBT and USB-C hot plug on cold and warm boot, TBT networking and target disk mode in the client computer. I was wondering if maybe we've been over-complicating things, might this work with built-in Titan Ridge as well? If you want to test it then you'll need to do a few things:

• Change the RP05 Root Port number throughout the SSDT to whatever yours is and change the address on the first line of the MMBA method using the (PCI address * 8)+x formula. My thunderbolt RP05 is at 1C,4 so its (1C * 8)+4 = E4. There are no power methods as hot plug seems to be 100% consistent without them.
• In the bios I have Force Power and ACPI RMV method enabled in the thunderbolt section. These might be hidden and so will need to be enabled using the grub approach. Note that I've removed DSB4 and only have one XHC2 SSP port as the AsRock Z370 itx/ac motherboard only has one thunderbolt port.
• The GPE._E2C method will also need to be renamed according to the value in your system. Just dump your system DSDT using MacIASL and search for "Method (TINI, 2, Serialized)". Immediately above it you'll find the hot plug event method which will be named "_Exx".
• The RP05._INI method in your DSDT will need to be renamed RP05.XINI using your OpenCore config.plist
• The _GPE._Exx method in your DSDT will need to be renamed _GPE.XExx using your config.plist

As far as I can tell functionality is just the same as when I tried patched firmware but with the added bonus of TBT working normally with other operating systems. This approach might only work with built-in Alpine Ridge but it's worth trying...

Unfortunately, no luck.

Before following your procedure, I flashed my GC-Alpine ridge AIC back to the original firmware.
I booted the system, the full boot sequence was visible on my Apple Thunderbolt Display, and at the end of the boot the desktop appeared as expected. However, no display peripherals worked (such as the camera, "display microphone", and "display sound"). The peripherals do work with Elias's V1 patched firmware.

Then I followed your procedure.
On my motherboard, the AR AIC attaches to RP21 at 1B,4.
In your SSDT, I did a global search and replace of RP05 with RP21.
I changed the address in the GPCB method to from E4 to DC.
I extracted my DSDT with F4 from the Clover screen.
In the DSDT, I renamed RP21._INI to RP21.XINI and I renamed _GPE._E17 to _GPE.XE17.
I have Force Power enabled in my BIOS but the Aorus Pro BIOS has no setting for the RMV method.

I rebooted, and I noticed no difference from booting without your modifications.

I have tried booting with and without the SSDT that CaseySJ created to inject DROM. with/without made no difference.

When I have tried Elias's patched AR firmware, IIRC the display and its peripherals attached to DSB4. Somewhere I think you said how to patch your SSDT to account for DSB4 but I can't find the message.

Attached is a screen shot of the RP21 portion of IOReg, and of system report--PCI. Also attached are my patched DSDT and your SSDT modified.

Thanks


UPDATE--it appears from MaciASL that the modded SSDT isn't loading.

 

[jlr]

Please try the attached CLOVER folder:

• Copy serial numbers back into SMBIOS.
• Go to RtVariables and click Generate button located to the right of "ROM".

Then check if system will still boot. If so, try the supplemental update again.

I did this and while my system still boots without an issue, trying to update results in the same kernel cache problem...