Attached ZIP contains two
experimental Thunderbolt SSDTs for the Z490 Vision D. The file names are:
- SSDT-TBOLT3-RP05-PORT7-DESIGNARE-Z390-WIN-AND-MAC-V1.aml
- SSDT-TBOLT3-RP05-PORT7-DESIGNARE-Z390-WIN-AND-MAC-V2.aml
Please try each one in turn, as follows:
- Add the two SSDTs to config.plist using OpenCore Configurator.
- Enable only one of them at a time (with the Enabledcheckbox).
- In the screenshot below we can see 3 different Thunderbolt SSDTs, but only one of them is enabled.
View attachment 479664
How to Test:
- ColdBoot into Windows
- Shutdown the system and flip power switch on PSU to OFF for 10 seconds (capacitors must discharge).
- Then flip it back on and boot into Windows.
- Do Thunderbolt devices connect and work?
- WarmBoot into Windows
- Boot into MacOS first and check if Thunderbolt devices connect and work
- Then reboot and choose Windows from the OpenCore Picker
- Do Thunderbolt devices connect and work?
Hi
@CaseySJ, still testing, but wanted to report back. Both appear to work well in macOS Catalina. Hotplug, sleep work etc. Hotplug of thunderbolt devices work, but not hotplug of USB3 devices. Upon hotplugging a USB-C Samsung T5 drive, it comes on, but doesn't load. This is true of all 3 .AML files (original plus two experimental). However, with original, and experimental2 aml files, USB3 devices load if connected to thunderbolt controller on cold boot.
But with both experimental .AML files, Thunderbolt does not work in windows for me, whether from cold boot or warm boot on Bios 5a on the flashed Vision D NVM 50 TB firmware. I haven't tried modifying DROM with either .AML file. The original z490-TB3 aml as per post #1 (with modified DROM) works in windows with warm boot only.
Curiously, when I boot into windows on warm boot, a message pops up saying a thunderbolt controller has experienced an error, and firmware needs to be updated before devices can connect. On warm boot, the thunderbolt device is clearly connected, but it doesn't start, and in Device Manager, there's a symbol on the attached device that it's experienced an error.
One thing you didn't specify, and I haven't tested is, when picking Windows OS at boot time, am i to pick it from Opencore, or from Vision D's F12 OS picker? I've been using the Opencore picker.
Finally one caveat: in post 869 you mentioned the following:
Comment: disable \_GPE.TINI (Zero, RPS0, RPT0, Zero)
Find: FF5C2E5F 47504554 494E4900 52505330 52505430 00
Replace : FFA3A3A3 A3A3A3A3 A3A3A3A3 A3A3A3A3 A3A3A3A3 A3
I haven't disabled this ACPI patch in my testing. Should it matter?