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

[Hackintoshron]

I was using HWMonitorSMC2 v2.4.9, but just upgraded to v2.6.1 from CloverHackyColor (click here). This version is even better. Not only does it display iGPU and AMD GPU statistics, but it also displays comprehensive voltages for Designare Z390:

View attachment 466611

• Are you using any non-standard DSDT?
• Feel free to compress and upload your CLOVER folder, but remove serial numbers from SMBIOS section of config.plist.
• Also post a screenshot of the /Library/Extensions folder.

OK. Here are my aml and extensions folder pix as well as the EFI.

 

[scottkendall]

super weird. But time flies, it’s not been a few months but over a year since i built this.
Thanks a lot for your help!
Just ordered a new gpu, i’ll see if that was the problem mid week

edit: is it possible that somehow it’s gone bad so fast cuz i had it in the pciex2 slot instead of pciex1? I know the bandwidth is remarkably lower...

No that would make the card work less hard and run cooler thus extending its life. Besides 1 year old system should not be having a GPU blow up maybe you got some manufacture warrantee still at around 1 year.

 

[BerndVP]

Hi,
I probably asked this in the past, but can't find it anymore.
Is there a way to create a SSDT for PCI Information injection instead of using the Clover -> Devices -> Arbitrary injection ?

 

[jiffyslot]

First choice for me would be a Shure SM7b but that is way over budget

Check out the Rode NT1a. Professional level quality at a really affordable price especially considering it comes with and XLR cable, shock mount and pop shield!

https://www.sweetwater.com/store/detail/NT1AAnniv--rode-nt1-a-large-diaphragm-condenser-microphone

@CaseySJ Sorry I spaced on this.

Yeah, ditto on the SM7b and the NT1a. I wanted to ask you if the mic would be close or far; can it be in the shot? If close is okay, and it's just spoken word, for your budget I'd also consider the tried and true Shure SM57. Dynamic mics are really forgiving for voice work, and the 57 is built like a hammer. Most NLE's and DAWs will have a couple good voice compressors. You may also be able to pick one up used in your area. Try it out. Lots of reference online for further setups. YMMV...

 

[jiffyslot]

Have you flashed your firmware? I do not remember if you said you did or you weren't convinced yet that it would work for you. I would think it would since it seems I have everything I did on my Mac mini working.

I have not flashed my firmware. I also using the original, unpatched, non-native NVRAM. I'm using Clover and Mojave, but no system sleep because It's a Pro Tools setup. Somehow, Thunderbolt reconnects to the Apollo 8 TB2 after power-cycling the interface. IDK what sorcery this is, but getting to this stage took a lot of work and even more time. I know better than to take another card when I have a pair of kings.

 

[dgsga]

Okay, @dgsga here's my SystemDSDT, but I have questions:

First Bullet Point...

I don't find any _GPE._Exx, there are a lot _GPE. listings, can't post them all......

For bullet points 3,4 and 5 it sounds like they are just ACPI renames, yes? So, in OC, they would be patched under root -> ACPI -> patch? You don't have a sample, do you?

@mm2margaret , you found all the right bits, good job. All the changes that need to be made are done in the SSDT-TbtOnPCH file, not the system DSDT. The _GPE hot-plug method you need is indeed _E4C. So all you need to do is change _E2C in the SSDT to _E4C and XE2C to XE4C as per the attached file. Don't mess with your DSDT and remember to have Force Power enabled in the thunderbolt configuration section of your bios. Then use the config.plist ACPI patches I've also attached

 

[Qres]

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:

• Adjust the Root Port number and change the GPCB method changed 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.

Great job dgsga , my MB is Asrock Z390 phantom gaming itx/ac, after update to BIOS 4.40C, provided by Asrock, I can enable GPIO3 Force Power from BIOS. After that, the thunderbolt node showed up. However, after I modified your SSDT and applied on OC, nothing changed. Could you help me to check my files ? Thanks!

 

[dgsga]

Great job dgsga , my MB is Asrock Z390 phantom gaming itx/ac, after update to BIOS 4.40C, provided by Asrock, I can enable GPIO3 Force Power from BIOS. After that, the thunderbolt node showed up. However, after I modified your SSDT and applied on OC, nothing changed. Could you help me to check my files ? Thanks!

Thanks! The DSDT and SSDT are fine. Have you added the config.plist ACPI patches in OC? If you don't the SSDT won't load (see attached)

 

[scottkendall]

I have not flashed my firmware. I also using the original, unpatched, non-native NVRAM. I'm using Clover and Mojave, but no system sleep because It's a Pro Tools setup. Somehow, Thunderbolt reconnects to the Apollo 8 TB2 after power-cycling the interface. IDK what sorcery this is, but getting to this stage took a lot of work and even more time. I know better than to take another card when I have a pair of kings.

Fair enough, I wasted a lot of time and got nowhere so I guess I had nothing to lose with updating firmware. But I can tell what I gained from doing it was more then I ever expected.

 

[CaseySJ]

Hi @CaseySJ

There's one final thing I've LOVE to get working on my system and that's sleep by make some SSDT changes so only the power button can wake the system.

I found this posting:

How to disable wake from USB?

Hi, I always had aapl-clock-id set to disable wake from USB, i.e. my computer only woke up when pressing the power button. Now with all that changed USB handling in El Capitan, this does not seem to work anymore. Strangely, I also have wakereason "?" when waking from keyboard or mouse. Is there a...

www.insanelymac.com

but it's 4 years old. Is there something that could easily be done to your "SSDT-UIAC-DESIGNARE-Z390-V7.aml" in order to make this happen?

Thanks!
Lam

I know

It’s just because of all my Corsair items connected internally to HS11/HS12. It would be great to have the option to not have to worry about any USB device waking the system and only having the power button do the waking

Lam

The post on Insanely Mac could be adapted, but it will disable all USB ports on a particular controller. If we do this to XHC on Designare Z390, we'll lose the ability to wake using even a USB keyboard or mouse. Even a Bluetooth device will fail to wake the system because Bluetooth also operates over USB.

So that leaves us with this:

• Disable the USB port (HS11 or HS12) to which the Corsair is connected. Corsair will still work, but will not be monitor-able from macOS. Windows can still monitor/control the device.
  • If you know that the Corsair is attached to HS11, for example, then simply add uia_exclude=HS11 to Boot Arguments in Clover Configurator.