Gigabyte Z690 Aero G + i5-12600K + AMD RX 6800 XT

[StefanAM]

Those are two independent ACPI renames and both are needed:

• The first "MC__ to MCHC" rename takes place in DSDT only
• The second such rename takes place in IgfxSsdt SSDT only

In fact, the reason we need the second rename is because we do the first rename! If we don't do the first rename, we don't need the second rename.

But way not in all SSDT and DSDT? I have like this (I renamed all), took out MCHC from SSDT-SBUS-MCHC.aml and I have no problems.

 

[CaseySJ]

very interesting! That might explain why I'm still getting ACPI warnings! But then that would mean that at least for me, the 'change adbg to xdbg' is what has enabled resume_from_sleep to work then.

The warnings are okay; we shouldn't be seeing errors such as "X table load failures".

 

[tonben]

In Section 8 of the same Quick Reference spoiler, there is a link to HackinDROM website where we can generate a Thunderbolt SSDT. The same post is referenced here:

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

It seems harmless, but technically should not be there. Please try the following: Reset NVRAM. If not successful, perform cold boot by shutting down and flipping power switch on PSU to OFF for 10 seconds, then power back up and boot. If not successful, mount EFI partition of that disk, open it...

www.tonymacx86.com

Please give this a try. We need both Thunderbolt SSDT and SSDT-DTPG, the latter of which may already be in the EFI/OC/ACPI folder.

@CaseySJ as suggested, I attempted to generate a TB SSDT following the HackinDROM instructions while verifying RP05 with IOregistry.
I made the replacement changes and noticed the saved file (SSDT-TB3-HackinDROM) did not have a .aml extension.

I am having difficulty understanding how to generate the SSDT with the appropriate extension. All my attempts resulted in failure.

Am I to just append the .aml extension to the file???? I could not be that simple!!???

I have attached the IOregistry and the generated SSDT.

GC Titan Ridge V2 in use.

Tony...

 

[CaseySJ]

@CaseySJ as suggested, I attempted to generate a TB SSDT following the HackinDROM instructions while verifying RP05 with IOregistry.
I made the replacement changes and noticed the saved file (SSDT-TB3-HackinDROM) did not have a .aml extension.

I am having difficulty understanding how to generate the SSDT with the appropriate extension. All my attempts resulted in failure.

Am I to just append the .aml extension to the file???? I could not be that simple!!???

I have attached the IOregistry and the generated SSDT.

GC Titan Ridge V2 in use.

Tony...

This is a case of Apple trying to protect you from something you don't need to be protected from! The extension is already there; it's just hidden. To un-hide it, right-click on the file name and select Get Info. Then uncheck the Hide Extension box:

 

[StefanAM]

First, you have a curious patch on _L6F (probably an experiment in progress):
View attachment 535288

Second, You don't need to patch _L61, _L6D, _L6F on DSDT, you have an SSDT called SocGpe that include all linked SLxx methods. You only have to disable this native SSDT and create your own by including your patch.

I have patched this SSDT and named it to SSDT-SocGpePatched.aml and have attached another SSDT-TbtOnPch.aml to be used instead of current.

@Elias64Fr, unfortunately, I have same symptoms. If I boot with my TB dock, it stops before login. If hot plug, it crash in 15 sec. What can I try more?

 

[tonben]

This is a case of Apple trying to protect you from something you don't need to be protected from! The extension is already there; it's just hidden. To un-hide it, right-click on the file name and select Get Info. Then uncheck the Hide Extension box:
View attachment 535294

Got IT.

Adding to ACPI folder and config.plist.

Fingers and toes crossed...

 

[CaseySJ]

Here you go: My SSDT is attached.

It seems that Maple Ridge on macOS is very particular about the Thunderbolt device that is connected.

With your SSDT and all of mine:

• Belkin Thunderbolt 3 Dock Pro will connect and hot plug
• Apple Thunderbolt to Gigabit Ethernet adapter will not hot plug, but will work when connected before boot
• Neither of these two devices will resume after wake-from-sleep
  • The Thunderbolt controller will not connect these devices after wake-from-sleep
• But the USB controller on Maple Ridge works fine before and after sleep

If your CalDigit 10GbE wakes from sleep, then can we make any guesses as to which devices are more or less likely to wake properly?

 

[dehjomz]

It seems that Maple Ridge on macOS is very particular about the Thunderbolt device that is connected.

With your SSDT and all of mine:

• Belkin Thunderbolt 3 Dock Pro will connect and hot plug
• Apple Thunderbolt to Gigabit Ethernet adapter will not hot plug, but will work when connected before boot
• Neither of these two devices will resume after wake-from-sleep
  • The Thunderbolt controller will not connect these devices after wake-from-sleep
• But the USB controller on Maple Ridge works fine before and after sleep

If your CalDigit 10GbE wakes from sleep, then can we make any guesses as to which devices are more or less likely to wake properly?

So I have two Thunderbolt devices that I'm using to test z690 thus far: an IOCrest NVME enclosure (with the OS on an SN750 inside) and a Caldigit 10gbe. With your patches applied (particularly the adbg->xdbg) patch, wake from sleep works on multiple cycles and my devices come back from sleep.

Maple Ridge is very particular in terms of what devices work properly with it. I have an older Cable Matters 10 GbE adapter that hotplugs fine with Titan Ridge and the new TB4 controller in the M1 Max... but with Maple Ridge, it works on cold boot, but does not properly connect after wake from sleep. This has a JHL6240 controller inside and my observation is that some of the older Alpine Ridge controllers have some weird compatibility issue with Maple Ridge, particularly with hotplug / wake from sleep. The Caldigit and the IOCrest are also Alpine Ridge but they both have the JHL6340 and those work fine with Maple Ridge. Devices with Titan Ridge and Goshen Ridge such as the Titan Ridge docks and Goshen Ridge TB4 hubs (with the 3 downstream TB4 ports) work properly with Maple Ridge as well, in terms of hot plugging.

So it might seem then as you correctly observed the other day, Titan Ridge is the way to go for widest compatibility with the panoply of TB devices on the market.

The issue I was having with my flashed Titan Ridge card is that it doesn't connect Thunderbolt devices until a warm boot (a macOS warm boot that is), and since my OS is on the IOCrest, I can't boot into macOS to warm boot in the first place. Of course I could install macOS on another drive or use the NVME slots on the board to alleviate this issue. But with Maple Ridge, I have no such problems... my NVMe drive inside the IOCrest is discovered at cold boot each time.

 

[NCMacGuy]

@CaseySJ

I installed a GC-Titan Ridge v1 card I had flashed with 23.0 back when... I see this is not the recommended version for Big Sur 11.3+, but it sort of works for me.

SSDT-DTPG.aml and SSDT-TB3-HackinDROM.aml are loaded in my config.plist. There is no hot plug, but a TB3 external SSD does appear in Finder on a warm boot. USB3 external drives do work when hot plugged into the TB3 port.

I have failed in my attempts to flash a GC-Titan Ridge v2 card. I don't know whether my CH341a programmer died, or there is some other issue.

I have no current need for TB3, so I will live with what I have working.

 

[tonben]

@CaseySJ whenever time allows, would you kindly inspect my IOregistry and ThunderBolt SSDT for accuracy?

The GC Titan Ridge V2 shows within the thunderbolt/4 tab however, none of my TB devices operate.
I tried connecting prior to booting the system and tried hot-plugging.

I remember it being stated that this TB cards works.

Tony...