Contribute
Register

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

I'm impressed! Thank you for lesson, Casey! Is this only for flashed TB cards, or you'll implement also for original firmware + SSDT?
We'll need beta testers who own Thunderbolt monitors, Thunderbolt NVMe SSDs, and Thunderbolt Audio Interfaces to tell us whether adding pathcr does or does not make any difference. We will need to try this on both (a) original firmware and (b) flashed firmware. Those who have original firmware should not flash the firmware. Those who already have flashed firmware should not restore the original firmware. We just need different users with different firmware.

UPDATE: Please see this post below for details on making the changes for yourself:
 
Last edited:
Okay, I see. If the problem occurs in Windows as well then there's something more fundamental. No need to install macOS on spare disk.

Instead, try re-flashing the BIOS (F9g or F9i) if you haven't tried that already. It will be necessary to configure BIOS afterwards, starting with F7 (Load Optimized Defaults).
I'd be happy to try to re-flash the BIOS. However, this issue started a long time ago. I'm not 100% sure when because at the time I was only using Win10, and I figured it was just a Win10 issue. :lolno: I didn't pay too much attention to it until I installed macOS on it. The first BIOS I flashed was F5, if I remember correctly, but I do remember this happening then as well.

Can you take a look at all my SSDTs (see attached pic) and see if there is anything in there that is not necessary per my hardware? I just want to make sure that none of those SSDTs would be causing the issue with the USB-C ports needing to be re-plugged.

Thank you!
 

Attachments

  • SSDTs.png
    SSDTs.png
    27.4 KB · Views: 58
We'll need beta testers who own Thunderbolt monitors, Thunderbolt NVMe SSDs, and Thunderbolt Audio Interfaces to tell us whether adding pathcr does or does not make any difference. We will need to try this on both (a) original firmware and (b) flashed firmware. Those who have original firmware should not flash the firmware. Those who already have flashed firmware should not restore the original firmware. We just need different users with different firmware.
When using original firmware of Titan Ridge v1, my M.2 SSD enclosure and the display work fine. The only problem is it shows nothing under system report, Thunderbolt/USB4 section and no Thunderbolt bridge function.

I just removed the `patchcr` again, see my screenshot. some of my Thunderbolt devices just go down to 20Gb/s x2, but some do not. don't know why.

Screen Shot 2021-05-01 at 2.31.18 AM.png



my motherboard is X299 Sage 10G, which supports titan ridge card and have 5 pin. if use original firmware with KGP's method to drive thunderbolt, it works like a real Mac with all my thunderbolt devices (3 Thunderbolt Displays, 2 m.2 enclosures, the docker, QNAP 10gb ethernet card)
 
We'll need beta testers who own Thunderbolt monitors, Thunderbolt NVMe SSDs, and Thunderbolt Audio Interfaces to tell us whether adding pathcr does or does not make any difference. We will need to try this on both (a) original firmware and (b) flashed firmware. Those who have original firmware should not flash the firmware. Those who already have flashed firmware should not restore the original firmware. We just need different users with different firmware.
I'm running flashed firmware (Z390-AORUS-XTREME-NVM33-Elias64Fr.bin) on GC-Titan Ridge 2.0.
I have a 4K TB UltraFine, Internal/External NVME SSD's, and CalDigit TS3 Plus dock. Let me know what to try and how to report back!
 
I'd be happy to try to re-flash the BIOS, however this issue started a long time ago, not 100% sure when because at the time I was only using Win10 and I figured it was just a win10 issue :lolno: didn't pay too much attention to it until I installed macOS on it. The first BIOS I flashed was F5 if I remember correctly, but I do remember this happening then as well.

Can you take a look at all my SSDTs (see attached pic) and see if there is anything in there that is not necessary per my hardware? I just want to make sure that none of those SSDTs would be causing the issue with the USB-C ports needing to be re-plugged.

Thank you!
The ACPI folder is correct.
 
I'm running flashed firmware (Z390-AORUS-XTREME-NVM33-Elias64Fr.bin) on GC-Titan Ridge 2.0.
I have a 4K TB UltraFine, Internal/External NVME SSD's, and CalDigit TS3 Plus dock. Let me know what to try and how to report back!
Hello @gandem,

Is your external NVMe plugged into a Thunderbolt NVMe enclosure or a Thunderbolt expansion chassis that has an on-board NVMe M.2 slot?

Please try the following modification if you're comfortable making changes to SSDT:
  • In the NHI0 --> _DSM method of your Thunderbolt SSDT, add the following item somewhere before the last entry.
  • Then empty the Package count.
  • See the screenshots below.
Code:
"pathcr",
Buffer (0x50)
{
/* 0000 */ 0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // ........
/* 0008 */ 0x00, 0x00, 0x07, 0x00, 0x10, 0x00, 0x10, 0x00, // ........
/* 0010 */ 0x05, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // ........
/* 0018 */ 0x00, 0x00, 0x07, 0x00, 0x10, 0x00, 0x10, 0x00, // ........
/* 0020 */ 0x01, 0x00, 0x00, 0x00, 0x0B, 0x00, 0x0E, 0x00, // ........
/* 0028 */ 0x0E, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // ........
/* 0030 */ 0x02, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // ........
/* 0038 */ 0x00, 0x00, 0x04, 0x00, 0x02, 0x00, 0x01, 0x00, // ........
/* 0040 */ 0x03, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // ........
/* 0048 */ 0x00, 0x00, 0x07, 0x00, 0x02, 0x00, 0x01, 0x00 // ........
},
  • Here's the original file opened with MaciASL. Notice we are in the NHI0 --> _DSM method:
Screen Shot 2021-04-30 at 12.59.35 PM.png

  • These are the changes to be made:
Screen Shot 2021-04-30 at 1.01.35 PM.png

  • After saving the file, quitting MaciASL, and reopening the file we will see these automatic fixes:
Screen Shot 2021-04-30 at 1.04.17 PM.png
 
Testing Titan-Ridge card:
Devices to try: LG5k2 OWCTH4HUB ORICONvME SONNET10Gbe eGPU

Card 1 Titan-Ridge V2: Original NVM50 ------Detected & funcional OWCTH4HUB
Card 2 Titan-Ridge V2: Mod NVM50 ----------Not working OWCTH4HUB

Similar speed (20x2)
Captura de pantalla 2021-04-30 a las 22.06.54.png
 
Testing Titan-Ridge card:
Devices to try: LG5k2 OWCTH4HUB ORICONvME SONNET10Gbe eGPU

Card 1 Titan-Ridge V2: Original NVM50 ------Detected & funcional OWCTH4HUB
Card 2 Titan-Ridge V2: Mod NVM50 ----------Not working OWCTH4HUB

Similar speed (20x2)View attachment 517073
To All:

If you try the pathcr experiment (and we hope you will), please state your test conditions and results very clearly...
  • If you post a result after making the change, please label it as such.
  • If you post a result before making the change, please label it as such.
  • Both of the results should be posted (before the change and after the change).
  • Also describe any operational differences, if any. Does a feature of the device suddenly work after the change? Or does it stop working after the change?
 
Last edited:
When the process gets stuck at the Apple logo and you do a hard reboot, do you still see "Macintosh HD" as a boot option in OpenCore Picker? If so, select it and see if it goes through.
No, it doesnt go through.

I decided to do a fresh Catalina install, but I am stuck here as well. After creating the USB install stick and copying my working EFI (Updated with Hackindrom app from 0.6.0 to 0.6.8) to it, I get only "EFI-SAM-80M" and the actual SSD named "Catalina" as an option in the OC Picker when choosing to boot from the USB Stick. There should be an "Install BIG Sur" or similar though. Choosing the "EFI-SAM-80M" doesn't do anything.

Running out of ideas, ATM.
 
No, it doesnt go through.

I decided to do a fresh Catalina install, but I am stuck here as well. After creating the USB install stick and copying my working EFI (Updated with Hackindrom app from 0.6.0 to 0.6.8) to it, I get only "EFI-SAM-80M" and the actual SSD named "Catalina" as an option in the OC Picker when choosing to boot from the USB Stick. There should be an "Install BIG Sur" or similar though. Choosing the "EFI-SAM-80M" doesn't do anything.

Running out of ideas, ATM.
How did you create the USB install disk? Did you use GibMacOS to download the Catalina installer and run createinstallmedia in Terminal:
 
Back
Top