Contribute
Register

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

I currently have GC-Titan Ridge v2 that appears to be running properly on MacOS 11.1. I'm running the patched NVM50 firmware. I run a 4K Ultrafine Monitor and CalDigit TS3+ dock on it. Should I look for something particular in my IOREG to see if everything is populating correctly?
Glad to know that your CalDigit is working properly. This is quite encouraging. I have two Thunderbolt docks: Belkin and OWC. The Belkin did not work, but I'll try the OWC soon.

(Un)fortunately I have two GC-Titan Ridge cards installed, both flashed, and installed in:
  • Z490 Vision D
  • Asus X99 Deluxe II
Will run some tests on both cards with different Thunderbolt devices.
 
This might be due to an audio kext. Let’s get you back to Catalina first so we can take a deeper look at the Catalina configuration.
I booted up into my Catalina back up and noticed that my main OS drive is named "Update" which leads me to believe that the update didn't complete. I'm thinking that I should just restore my main drive with Carbon Copy Cloner and try the in-place update again?

Screen Shot 2020-12-29 at 8.50.17 AM.png


Here's a screen shot of my L/E of my Catalina backup:
Screen Shot 2020-12-29 at 8.52.07 AM.png


Screenshot of my EFI folder of my Catalina backup:
Screen Shot 2020-12-29 at 8.55.58 AM.png


I've also attached my config.plist just in case with all the PlatformInfo fields removed.
 

Attachments

  • config.plist.zip
    4.4 KB · Views: 33
I booted up into my Catalina back up and noticed that my main OS drive is named "Update" which leads me to believe that the update didn't complete. I'm thinking that I should just restore my main drive with Carbon Copy Cloner and try the in-place update again?

View attachment 503000

Here's a screen shot of my L/E of my Catalina backup:
View attachment 503001

Screenshot of my EFI folder of my Catalina backup:
View attachment 503002

I've also attached my config.plist just in case with all the PlatformInfo fields removed.
One of the kernel extensions is LittleSnitch. If you're running Version 4, it's necessary to upgrade to Version 5 for Big Sur:
Screen Shot 2020-12-29 at 9.07.54 AM.png


Recommendations:
  • Restore the main drive from the backup.
  • Boot from the main drive to ensure Catalina is up and running properly.
  • Upgrade LittleSnitch to Version 5.
  • Disconnect all Thunderbolt and USB audio devices.
  • Then try the Big Sur upgrade once again.
If the same problem (kernel panic or similar) happens again, it may be necessary to remove one or more additional kernel extensions:
  • Antelope
  • Apogee
  • Motu
  • SonarWorks
  • UAD
 
One of the kernel extensions is LittleSnitch. If you're running Version 4, it's necessary to upgrade to Version 5 for Big Sur:
View attachment 503005

Recommendations:
  • Restore the main drive from the backup.
  • Boot from the main drive to ensure Catalina is up and running properly.
  • Upgrade LittleSnitch to Version 5.
  • Disconnect all Thunderbolt and USB audio devices.
  • Then try the Big Sur upgrade once again.
If the same problem (kernel panic or similar) happens again, it may be necessary to remove one or more additional kernel extensions:
  • Antelope
  • Apogee
  • Motu
  • SonarWorks
  • UAD
Good call re: Little Snitch. I have Version 5 on my laptop which is running Big Sur so I'll upgrade it on Catalina before trying the update again.

Wanted to confirm that I NEED to run the EFIClone.sh script when restoring the main drive in Carbon Copy Cloner, correct?

Screen Shot 2020-12-29 at 9.18.32 AM.png
 
Good call re: Little Snitch. I have Version 5 on my laptop which is running Big Sur so I'll upgrade it on Catalina before trying the update again.

Wanted to confirm that I NEED to run the EFIClone.sh script when restoring the main drive in Carbon Copy Cloner, correct?
The EFIClone script will copy the EFI folder. If the EFI folder on the main drive is still okay (i.e. if you do not want to change or recover that folder) then it's perfectly okay to skip the EFIClone script. In this case the EFI folders on both drives will not be touched.
 
I have some bad news for everyone with a flashed GC-Titan Ridge. Mine has been flashed with NVM 23 (GC-Titan Ridge version 1.0):
  • Both Catalina 10.15.7 and Big Sur 11.2:
    • Belkin Thunderbolt 3 Dock Pro will appear to connect, but full device tree does not materialize and the dock does not actually work.
    • Hence, the flashed GC-Titan Ridge no longer seems to work.
    • However, the flashed on-boardThunderbolt controller still works correctly.
      • Z390 Designare
      • Z490 Vision D
      • B556 Vision D
If anyone is using a flashed GC-Titan Ridge v1 or v2 with Catalina 10.15.7 or Big Sur 11.1 (or later), please let us know if the card works.

@i0ntempest: Have you tried booting the system with the Thunderbolt SSDT disabled? Please try both (a) device connection before boot, and (b) device hot plugged after boot.
With thunderbolt SSDTs disabled port link speed is locked at 20Gb/s x2 and no longer changes when I plug stuff in. But no, it's still not recognizing any of my devices (both hot plugging and plug in before boot). Also seems the shutdown problem only occurs when there's stuff connected to the card.
 
If anyone is using a flashed GC-Titan Ridge v1 or v2 with Catalina 10.15.7 or Big Sur 11.1 (or later), please let us know if the card works.
My flashed V1 GC-Titan Ridge card seems to still be working ok with Catalina 10.15.7.
 
With thunderbolt SSDTs disabled port link speed is locked at 20Gb/s x2 and no longer changes when I plug stuff in. But no, it's still not recognizing any of my devices (both hot plugging and plug in before boot). Also seems the shutdown problem only occurs when there's stuff connected to the card.
My experiences after flashing my GC-Titan Ridge cards, I recall having the TB settings in bios not sticking the first couple of boots. For example, after initial boot with installed card, I would change all the appropriate TB settings in bios to their proper parameters, save and reboot. Then go back into bios and find security settings under TB to be user authorized instead of disabled. I think I had to change this a second time before it would stick. Another finding from my experience with this card is that I get more reliability after a cold boot.
 
One of the kernel extensions is LittleSnitch. If you're running Version 4, it's necessary to upgrade to Version 5 for Big Sur:
View attachment 503005

Recommendations:
  • Restore the main drive from the backup.
  • Boot from the main drive to ensure Catalina is up and running properly.
  • Upgrade LittleSnitch to Version 5.
  • Disconnect all Thunderbolt and USB audio devices.
  • Then try the Big Sur upgrade once again.
If the same problem (kernel panic or similar) happens again, it may be necessary to remove one or more additional kernel extensions:
  • Antelope
  • Apogee
  • Motu
  • SonarWorks
  • UAD
Aside from the Little Snitch 4 issue, is there any reason why we couldn't run the above-mentioned kernel extensions from the EFI?
 
Last edited:
My experiences after flashing my GC-Titan Ridge cards, I recall having the TB settings in bios not sticking the first couple of boots. For example, after initial boot with installed card, I would change all the appropriate TB settings in bios to their proper parameters, save and reboot. Then go back into bios and find security settings under TB to be user authorized instead of disabled. I think I had to change this a second time before it would stick. Another finding from my experience with this card is that I get more reliability after a cold boot.
I've done numerous power cycles while changing thunderbolt related settings. Still, nothing. The last thing I want to try is a full bios reset, though I doubt that'll do anything.
 
Back
Top