- Joined
- Jul 12, 2016
- Messages
- 3,092
- Motherboard
- Gigabyte Z370 Gaming 5
- CPU
- i9-9900K
- Graphics
- RX 6900 XT
- Mac
- Mobile Phone
( i surrounded with scotch tape before plug it )
Last edited:
( i surrounded with scotch tape before plug it )
Thanks! That's looking much better with this updated DROM! Screenshot attached
Why does changing the vendor/device name and the buffer size (the 0x65) have that effect?
BumpingHi, is there any special procedure to update from 10.15.3 to 10.15.4?
I checked the original tutorial and could not find anything.
Bumping
Our own firmware flashing escapades were inspired by that thread on MacRumors! The GC-Titan Ridge NVM 23 firmware posted here in our Repository may work nicely on the Mac Pro 5,1, but with the SSDT posted by DSM2 (post #725) on Mac Rumors.@CaseySJ, FYI. I have been following the MacRumor's testing TB3 AIC with MP 5,1 thread and saw this post. I didn't know if you've seen it or have it bookmarked. Whatcha think?
I have a Mac Pro 5,1 that I'd like to add TB3 to it so as to share peripherals. (I'm still trying to get my ASUS Z170 working with the EX3 and may have to burn the mod'd f/w on the EX3.)
These Gigabyte Titan Ridge card f/w mods are starting to confuse me WRT whose doing what with the f/w mods.
After flashing the GC-Titan Ridge with NVM 23 from the Repository and installing it into your system (with pins 3 and 5 jumpered together), please download and run IORegistryExplorer and select File --> Save As... to save the IOReg file. Then post that file.I am ready @CaseySJ
pls send to me hot plug SSDT and EFI folder for
My PC :
MB : Gigabyte Aorus Z390 Pro WiFi (F12c) | CPU : i9-9900K (@3.60 GHz) | GPU : Sapphire RX 580 8GB | RAM : Kingston HyperX RGB (64 GB) | SSD : Samsung SSD 970 Pro (1TB) Bluetooth & Wifi : ABWB 802.11AC WI-FI With Bluetooth 4.0 PCI-Express (PCI-E) BCM94360CS2 Combo Card | Thunderbolt 3 : GC-Titan Ridge | OS : OSX 10.15.4
Thank you very much for help us
All the best
Hello @phrfpeixotoBumping
Vendor and Device names are cosmetic. There are, however, more meaningful differences in the preceding bytes...Thanks! That's looking much better with this updated DROM! Screenshot attached
Why does changing the vendor/device name and the buffer size (the 0x65) have that effect?