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

[NorthAmTransAm]

Woo! It's alive! Relatively painless, for someone who has never gotten this much in the weeds before. The entire process including getting the Raspberry Pi 4 up and running, and doing the flash procedure took maybe a little over an hour. I was being extra careful. But the card/Thunderbolt bus now shows up under "Thunderbolt" in profiler. And appears to work after waking from sleep without issue.

Do I still need SSDT-DTPG, ThunderboltReset.kext, and TbtForcePower.efi??

Thanks!

I'd hang onto SSDT-DTPG unless one of your other SSDT's are providing that method. TB Reset and Forcepower aren't necessary.

I do see you have the same mobo as me. I used to keep tbforcepower.efi while experimenting with things like sleep. That is because if I broke the thunderbolt connection then I wouldn't have to shut down and unplug as the driver would take care of it. So, your choice.

 

[WhosMac]

Yes, three machines: my X299, Z370 and a real Mac (16,1). No issues during the upgrade (I use NDK's version of Opencore on the X299 and the Z370), and all upgraded perfectly - very easy upgrades. As for issues after the upgrade, and how stable and reliable 10.15.5 is, well, only time will tell.....

Thats awesome! Glad all the upgrades went smoothly! As for 10.15.5, I would agree a time will tell but I will mention that at least based on the release notes the photos bug and large data transfer bugs have been resolved. I guess ill update clover and kexts and give it a whirl.

@CaseySJ I know I already have Native NVRam but I know in the last upgrade it was necessary for 10.15.4, is it safe to assume that with it this go-around should be straight forward after
Kexts Update
Clover Update
Clone backup drive

 

[lanzaozijun]

Upgrade to macOS Catalina 10.15.5 (19F96) HDMI external display black screen!
In macOS Catalina 10.15.4, boot-args enable igfxonln = 1 igfxagdc = 0 method is invalid.
Is there any other solutions for my friends?

 

[mm2margaret]

I used the Designare NVM33 for a while. It would work very well for a week or so, then stop working. I would reset things and it would work for a couple of weeks, then stop. I'm currently running a patched version of NVM50 with minimal issues. I'm going to stick with 50 for a while to see how it goes, so far so good. My CalDigit TS3 Plus does boot and is recognized on boot into MacOS. Sometimes the dock would be recognized on boot when the "boot support" option was disabled in BIOS, but maybe 1 or 2 times out of 10. For me, what works best is the setting on "boot once", it gets recognized on every boot. You might want to check what firmware you are running on the dock itself. At some point, there was a problem with it (the dock) getting recognized when my GC-Titan Ridge firmware was upgraded to unpatched NVM43. CalDigit came out with a new firmware a couple of months after that and it got things working again.

NVM50? Interesting......would love to hear how it goes over time. I have a Titan Ridge, and was wondering if NVM50 would be of value over NVM33. Can I assume you're running NVM50 on a Titan Ridge?

 

[jiffyslot]

Anyone who would like to help me resurrect a dead (AIC) GC-Titan Ridge? 1 year ago it just stopped working. I fiddled alot with my motherboard back then, downgraded, upgraded, etc., and somewhere on the way it just died. Never flashed or anything like that, but it doesn’t connect any devices. Not even before booting, when in BIOS, my plugged devices show some connection. I already have another working GC-Titan Ridge thanks to @CaseySJ (Thank you thousand times).

But would love to have one more card.

I have a multimeter, but don’t really know where to start. This weekend I get a flashing device so I could possibly read the blue and green chip to see if anything is corrupt. Anyone who would like to guide me here round the signal path on the PCB here?

Draw lines on the photos, write instructions, anything really.

@CaseySJ @jb007

 

[hamzab]

Quick update - after 35/40 minutes or so, it finally went to sleep.

• @CaseySJ do you mind showing me what to type within Terminal so I can see what kept my machine awake for so long? I know pmset -g assertions displays what is KEEPING your Mac from sleeping, but is there any way of seeing what kept my Mac from sleeping after it's gone to sleep, like a log of all the events?
• Do you also mind if I paste the log here so we can see what keeps it awake? I'm interested to know (via the logs) what actually kept it awake, to see if the same problem transposes into 10.15.15 too.

Catalina 10.15.5 has been released. See the Release Notes. Did they know you were going to post this today?

Hahaha that is incredible! I didn't even submit any bug reports to Apple. I'm guessing others have been issues with Reminders too.

Lastly, some more noob questions (apologies):

• As I built this rig from scratch to 10.15.4, when it comes to upgrading, I've got my backup SSD just in case ready, but do we literally just download the update file from Apple's website and let it do it's thing, or do I use system preferences, update?
• Do we also need to update Clover
• I've seen you've got your hands on some shiny new Gigabyte Hardware! Please tell me you'll still continue to support the Z390? I don't think my wallet can afford another build just yet, especially with Covid uncertainty!

 

[gandem]

NVM50? Interesting......would love to hear how it goes over time. I have a Titan Ridge, and was wondering if NVM50 would be of value over NVM33. Can I assume you're running NVM50 on a Titan Ridge?

Yes, running patched NVM50 on GC-Titan Ridge. So far, so good!

 

[jb007]

@CaseySJ @jb007

Edit: I've replied to the wrong person! Doh! Sorry, @Junologue. Could you please create some pics that zoom into the three areas circled on the attached picture. I need to see if all components are intact.

Hi @jiffyslot.

I'm in the same boat. I 'killed' a GC-Titan Ridge a year or so ago when I was using the Z370 Gaming 7 motherboard, so I replaced it with a new one.

I discovered a couple of weeks ago why, like yours, the system is not seeing it. When I had it mounted in the very bottom slot of the Mobo, the fan on the Sapphire RX 580 above it (I had two of them installed) which is a very wide card (2.3 slots?), hit the components on the TB3 card and removed a surface mount resistor and a capacitor. I've checked and found okay both of the EEPROMs (green & blue) on my TB3 card, so it's most likely these components or I have 'zapped' one of the other support IC's.

I can most probably get mine going if I replace the resistor (3K Ohm) which is most likely being used as a pullup or pulldown, but the missing capacitor is so small I think I would have trouble replacing it. I believe this capacitor is just a decoupling capacitor and most probably I can get by without replacing it.

If you can shoot some high-resolution images of the back-side of the board, I can check to see if like me you are missing any, and if so, tell you what value(s) they are.

 

[fakejosh]

I'd hang onto SSDT-DTPG unless one of your other SSDT's are providing that method. TB Reset and Forcepower aren't necessary.

I do see you have the same mobo as me. I used to keep tbforcepower.efi while experimenting with things like sleep. That is because if I broke the thunderbolt connection then I wouldn't have to shut down and unplug as the driver would take care of it. So, your choice.

So this is a bit of interesting behavior. Here is the sequence.

Cold boot -- System Profiler shows Thunderbolt Bus with "Speed" as "Up to 40 Gb/s x1"
Put system to sleep, wake system, the speed is now "Up to 10 Gb/s X2"
Restart system and now speed is "Up to 0 Gb/s x2"

Anything to be concerned about here? or purely cosmetic?

Thanks!

 

[Junologue]

Plugged devices do appear in BIOS with the GC-Titan Ridge?

Just to clarify, BIOS doesn’t show them. But, when for instance my soundcard is connected to my broken Titan Ridge, the Thunderbolt indicator light at the top doesn’t light up, even when post booting. But it does on the working Titan Ridge.