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

[Elias64Fr]

Some updates:

• My previous tests were done with modified DSDT and OpenCore.
• But now I switched to standard DSDT and Clover.
• ThunderboltReset.kext is not used now.
• In Clover I added the following renames:
  • Change _INI to XINI
  • Change _E17 to XE17
• With TbtOnPch-Draft02, all tables are successfully loaded, but there are several ACPI Errors.
• Please see attached boot log.

---

View attachment 445732

"In Clover I added the following renames:

• Change _INI to XINI"

This change will rename all _INI on the DSDT ?! You should renamed it only for RP05 on DSDT but I don't know how it is possible on Clover.

On your Log file, many other errors ... related to OSDW .. I have this method on my DSDT but I think it is not required: Using modified SSDT and DSDT is only for macOS >> I have added OSDW method on the following draft

 

[r0mps]

This is specifically for people that are doing a fresh install of Catalina and wanting to install UAD software for a recording studio workstation:

After doing a successful direct install of Catalina, I spent a good 8 hours trying to figure out how to get my UAD device to work. At first I thought it was an issue with me not having the TB3 ports set up correctly, but it was fine. I learned that if you've installed UAD on Mojave already and are just updating to Catalina, than you are 100% fine. The problem was with the new security that Catalina enforces that prevents UAD Software from altering your system audio. I went through all the posts in this thread and saw a couple people had the same issue as me, but no solution other than installing Mojave first, then install UAD, and then upgrade to Catalina... If you are in looking to install Catalina fresh using the mini guide, the trick to get UAD software installed is below.

1. Boot into Recovery mode, load up Terminal, and type: csrutil disable (this disables SIP System Integrity Protection)
2. Boot back into the normal macOS partition run Terminal again and disable GateKeeper by typing: Sudo spctl --master-disable
3. Install UAD Software make sure its the most recent build
4. Boot back into Recovery mode and re-enable SIP through terminal
5. Re-enable GateKeeper

 

[Elias64Fr]

@Elias64Fr

After creating a dummy OSDW method like this...

View attachment 445736
...there are no more ACPI errors. Thunderbolt gets activated. I have a 14-port OWC Dock connected, but only a partial set of devices in the dock are recognized (no Thunderbolt bus yet):

View attachment 445737

Attached are the files I'm using:

• SSDT-TbtOnPch-Draft02
• SSDT-DTPG.aml-- this provides:
  • DTGP method
  • OSDW method
  • RMDT methods

Nice, now the SSDT file is loaded and thunderbolt device are correctly named. Can you add ACPIDebug.kext from Rehabman in order to have log information from our SSDT-TbtOnPch-Draft03.

Remember for the first test to cold boot your PC and remove all connected thunderbolt devices... on Apple boot screen, boot progress bar should slowing in the beginning during 2 or 3 seconds no more and should accelerate for normal boot.
In this case, we know that Thunderbolt device is correctly configured.

I'm waiting for your ACPIDebug boot log to understand what happen.

 

[cylsfar]

This is specifically for people that are doing a fresh install of Catalina and wanting to install UAD software for a recording studio workstation:

After doing a successful direct install of Catalina, I spent a good 8 hours trying to figure out how to get my UAD device to work. At first I thought it was an issue with me not having the TB3 ports set up correctly, but it was fine. I learned that if you've installed UAD on mojave already and are just updating to catalina, than you are 100% fine. The problem was with the new security that Catalina enforces that prevents UAD Software from altering your system audio. I went through all the posts in this thread and saw a couple people had the same issue as me, but no solution other than installing mojave first, then install uad, and then upgrade to catalina... If you are in looking to install catalina fresh using the mini guide, the trick to get UAD software installed is below.

1. Boot into recovery mode, load up terminal, and type: csrutil disable (this disables SIP System Integrity Protection)
2. Boot back into the normal mac os partition run terminal again and disable GateKeeper by typing: Sudo spctl --master-disable
3. Install UAD Software make sure its the most recent build
4. Boot back into recovery mode and re-enable SIP through terminal
5. Re-enable gatekeeper

Hi! I have do nothing of that.

I have install Catalina with mini guide, and I install UAD without TB3 actived.
I had to re install 5 times because the drivers who didn't want to work.

Last installation of drivers is good.

And with help of this thread I can use TB3.
And my UAD TB2 with adapter TB3 works fine.

 

[CaseySJ]

Nice, now the SSDT file is loaded and thunderbolt device are correctly named. Can you add ACPIDebug.kext from Rehabman in order to have log information from our SSDT-TbtOnPch-Draft03.

Remember for the first test to cold boot your PC and remove all connected thunderbolt devices... on Apple boot screen, boot progress bar should slowing in the beginning during 2 or 3 seconds no more and should accelerate for normal boot.
In this case, we know that Thunderbolt device is correctly configured.

I'm waiting for your ACPIDebug boot log to understand what happen.

Update:

• I dumped the original DSDT and changed only RP05._INI to RP05.XINI. Also changed _E17 to XE17.
• Copied TbtOnPch-Designare-Draft03 to the CLOVER/ACPI/patched folder.
• Copied ACPIDebug.kext to /Library/Extensions.
• Shutdown the system. Disconnected all Thunderbolt devices. Flipped power switch to OFF for 10 seconds.
  • This is a cold start.
• Restarted the system with no Thunderbolt devices.
• The modified DSDT and all SSDTs loaded with no problem. 16 ACPI tables successfully loaded.
• ACPIDebug log looks like this:
  
• RP05 looks like this:
  

EDIT: Thunderbolt devices do not seem to connect on boot or by hot-plug.

 

[Elias64Fr]

Update:

• I dumped the original DSDT and changed only RP05._INI to RP05.XINI. Also changed _E17 to XE17.
• Copied TbtOnPch-Designare-Draft03 to the CLOVER/ACPI/patched folder.
• Copied ACPIDebug.kext to /Library/Extensions.
• Shutdown the system. Disconnected all Thunderbolt devices. Flipped power switch to OFF for 10 seconds.
  • This is a cold start.
• Restarted the system with no Thunderbolt devices.
• The modified DSDT and all SSDTs loaded with no problem. 16 ACPI tables successfully loaded.
• ACPIDebug log looks like this:
  View attachment 445744
• RP05 looks like this:
  View attachment 445745

GREAT !

I have similar log data :

But I don't see all data on ur log with CIOR, COIR CIOR and CRMW ..can you send me TXT boot file.

Added: and reboot one time

Seem to be a great step for Titan ridge full view !

 

[CaseySJ]

GREAT !

I have similar log data :

View attachment 445747

But I don't see all data on ur log with CIOR, COIR and CRMW ..can you send me TXT boot file.

Seem to be a great step for Titan ridge full view !

Sure, please see attached. My log does not contain "Put upstream bridge back into D0". This log is after one reboot.

 

[CaseySJ]

@Elias64Fr

Are you an ACPI or Firmware engineer? You seem to be very knowledgeable about this!

 

[pitt1717]

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?

 

[digumo]

you guys are crazy and this is so interesting. wish I knew how to do all this..... can I ask a qq? Does this need to be done for each new bios?
so Casey, if your 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?

I'm no hardware engineer, and I also binge consume this thread more than I do a Netflix series, but, if I had to guess, hardware is hardware in terms of it's addresses, and the changes they are making is independent of BIOS since ACPI seeks to give control to the operating system. Read up about ACPI here.

But, I'm sure I'll be corrected if I'm wrong...