Contribute
Register

[Success] ASRock Z390 Phantom Gaming-ITX + TB3 + iGPU + Mojave + SFF Build

Joined
Jun 8, 2019
Messages
99
Motherboard
Z490 Vision D
CPU
i9-10900K
Graphics
Sapphire RX Vega64
Mac
  1. MacBook Pro
The cause of this could be this - I have noticed that with the SSDT method, the System information under Thunderbolt shows - no device connected after a random amount of time. The TB dock connected to the port continues to work. Even the tbpatch command shows no device connected which makes me believe something is wrong.
Anyways I read through OSY's page on the Thunderbolt saga, and I realize that hardware patching method should deliver the best results. I am going to revert to that over the weekend and see how it goes. With that method - I would not be able to see any devices behind the dock after waking from sleep - lets see if that persists.

@mango1122 I see. I plan on running the same combination tests on the native firmware over the next few days. Curious to know your results!

QQ => Can I use tbpatch to flash back to the native firmware using the same patch.plist, but with the restore command?
 
Joined
May 23, 2019
Messages
243
Motherboard
ASRock Z390 Phantom
CPU
i9-9900K
Graphics
UHD 630
Mac
  1. Mac Pro
Mobile Phone
  1. iOS
@mango1122 I see. I plan on running the same combination tests on the native firmware over the next few days. Curious to know your results!

QQ => Can I use tbpatch to flash back to the native firmware using the same patch.plist, but with the restore command?

You can use the tbpatch to flash between the native firmware and the modified firmware. Use this to patch the native firmware to a modified one. After flashing - don't forget to remove the SSDT, _E2C patch and add the TBROM-SSDT.
P.S - This is not a recommended method - keep a USB flasher handy in case something bad happens.
 

Attachments

  • patch.plist
    2.1 KB · Views: 29
Joined
May 17, 2012
Messages
52
Motherboard
ASRock Z390 Phantom Gaming-ITX
CPU
i5-9600K
Graphics
RX 580
Mac
  1. iMac
  2. MacBook Pro
I can confirm that this has been happening to my machine too. After a period of time - it does not recognise the device connected to the TB port - but the devices themselves seem to work. I think this is one of the drawbacks of the SSDT method.
I'm beginning to suspect an actual hardware issue (not awful, just a design/implementation issue). Reason being is that I had lost TB connectivity and TB altogether even when loading into windows directly. It also happened in bios where my bootable SSD was not recognized in BIOS nor Clover. If it was simply an SSDT, this would only be an OS X issue.

A power down with discharge solved it immediately and then TB was recognized in BIOS, Windows and OS X again.
 
Joined
May 23, 2019
Messages
243
Motherboard
ASRock Z390 Phantom
CPU
i9-9900K
Graphics
UHD 630
Mac
  1. Mac Pro
Mobile Phone
  1. iOS
I'm beginning to suspect an actual hardware issue (not awful, just a design/implementation issue). Reason being is that I had lost TB connectivity and TB altogether even when loading into Windows directly. It also happened in bios where my bootable SSD was not recognized in BIOS nor Clover. If it was simply an SSDT, this would only be an OS X issue.

A power down with discharge solved it immediately and then TB was recognized in BIOS, Windows and OS X again.
No it’s a SSDT issue. Because you warm booted into windows you saw the same behavior. This is a documented behavior.
 
Joined
May 23, 2019
Messages
243
Motherboard
ASRock Z390 Phantom
CPU
i9-9900K
Graphics
UHD 630
Mac
  1. Mac Pro
Mobile Phone
  1. iOS
@mango1122 I see. I plan on running the same combination tests on the native firmware over the next few days. Curious to know your results!

QQ => Can I use tbpatch to flash back to the native firmware using the same patch.plist, but with the restore command?

So back on native firmware and the TB devices don’t connect after a sleep wake. Not very exciting news. I don’t suppose anyone has solved it yet.
 
Joined
May 17, 2012
Messages
52
Motherboard
ASRock Z390 Phantom Gaming-ITX
CPU
i5-9600K
Graphics
RX 580
Mac
  1. iMac
  2. MacBook Pro
No it’s a SSDT issue. Because you warm booted into windows you saw the same behaviour. This is a documented behaviour.
A cold boot (from powered down) directly into Windows when selecting my Windows NVMe drive from the UEFI boot loader produced the same TB issue.
 
Joined
Sep 23, 2019
Messages
47
Motherboard
Asrock Z390 Phantom Gaming ITX
CPU
i9-9900K
Graphics
RX 580
So back on native firmware and the TB devices don’t connect after a sleep wake. Not very exciting news. I don’t suppose anyone has solved it yet.
Fwiw on native firmware NVM20, old skool not using the new SSDT, so long as I keep my TB device (UAD Satellite Octo via Apple TB3>TB2) powered on, its detected fine on sleep/wake.
 
Joined
Dec 29, 2010
Messages
226
Motherboard
GA-Z97N-Gaming 5
CPU
Core i7 4790K
Graphics
Nvidia GTX 760
Mac
Classic Mac
Mobile Phone
I've noticed another issue with this SSDT. If I try to boot into Windows from OpenCore with this SSDT enabled I receive an ACPI error. If I boot into Windows from the Windows 10 boot loader there's no issue.

Has anyone else seen this issue? I'm using an older version of OpenCore.
 
Joined
Sep 3, 2017
Messages
65
Motherboard
Asrock Z390 phantom gaming
CPU
i7-8700K
Graphics
RX590
The cause of this could be this - I have noticed that with the SSDT method, the System information under Thunderbolt shows - no device connected after a random amount of time. The TB dock connected to the port continues to work. Even the tbpatch command shows no device connected which makes me believe something is wrong.
Anyways I read through OSY's page on the Thunderbolt saga, and I realize that hardware patching method should deliver the best results. I am going to revert to that over the weekend and see how it goes. With that method - I would not be able to see any devices behind the dock after waking from sleep - lets see if that persists.

I do not see any TB3 connected under system report, but my TB3 audio interface is still working.
 
Joined
Jun 8, 2019
Messages
99
Motherboard
Z490 Vision D
CPU
i9-10900K
Graphics
Sapphire RX Vega64
Mac
  1. MacBook Pro
So back on native firmware and the TB devices don’t connect after a sleep wake. Not very exciting news. I don’t suppose anyone has solved it yet.

Even I'm back to the native firmware. For me though, TB just dies after sleep & wake (TB link status changes to 0xe00002eb from 0x07/0x01). This is with all the combinations of iGPU vs iGPU & DGPU. I switched back so I could use my 5700 XT w/o kernel panics. I'll have to give up sleep :( but even if I put the device to sleep, I can restart gracefully.

I'll give the SSDT only approach a try again in a few weeks. I'll post my experience over in the Designare thread. Maybe @CaseySJ and others will have some insights.
 
Top