Thanks Casey, apologies for that, I've now added it under a Spoiler.
I'd prefer Darkwakes not to happen, as I don't need the Mac to wake every hour or so to check email etc. Does that mean I should add the Bootargument Darkwake=0, even though Powernap is unchecked on Energy Saving preferences?
It contains a blue dot (do not modify the chip with the green dot)
If System Information --> Thunderbolt says No drivers are loaded, then this does not apply to you.
Benefits / Purpose:
Just as your Mac's serial number is unique and your Ethernet card's MAC address is unique, we need to assign a unique ID to the Thunderbolt controller.
Thunderbolt Ethernet Bridge and Target Disk Mode require this procedure.
Most eGPUs require this procedure.
QNAP Thunderbolt-based NAS units require this procedure.
Other Thunderbolt-based storage and NAS systems may require this procedure as well.
This procedure may improve overall compatibility with a wider set of Thunderbolt devices.
Preparation of Card:
If motherboard contains a compatible 5-pin Thunderbolt header (THB_C), connect the GC-Titan Ridge to motherboard with a Thunderbolt header cable that is supplied with the GC-Titan Ridge.
Thunderbolt DROM will be customized for you using a randomly generated Unique ID (UID) and all checksums will be auto-computed.
A complete Thunderbolt SSDT (with the new DROM) will be presented on screen and it will also be copied to the clipboard for you.
Download and run MaciASL, create new file (File --> New) and paste the clipboard.
Then save the file in ACPI Machine Language (AML) format: File --> Save As... and choose ACPI Machine Language from the pop-up menu.
Give the file an appropriate name such as: SSDT-TB3-DROM-HOTPLUG.aml.
Any name is okay as long as it begins with SSDT-
However, download SSDT-DTPG.aml from the bottom of this guide.
Both SSDT files must be copied to the CLOVER/ACPI/patched folder (for CLOVER users) or OC/ACPI folder (for OpenCore users).
Option 2: Superuser Method (credit: @joevt)
Please see this guide for advanced users.
Option 3: Manual Method
Specify a new Unique ID (UID) in the 5 green bytes below (0x11).
Replace the 5 green numbers below with 5 randomly selected hex numbers.
Now click here to visit an online CRC calculator and configure it as shown:
Copy the boldfaced bytes below (bytes 2-9 after replacing the green bytes with your own values) to clipboard and paste them into the Bytes field as shown and click CRC button:
Enter the CRC-8 checksum into the 1st byte of Thunderbolt DROM as shown in red below.
Save this into your Thunderbolt SSDT, in the NHI0._DSM method.
The attached SSDTs may be used, but they are configured for PCI0.RP05. Adapt the SSDT for the actual PCIe path for your system. If you have questions about this, just ask.
Both SSDTs should be copied to CLOVER/ACPI/patched or for OpenCore users, OC/ACPI
Optional but Highly Recommended for Add-in-Cards: Byte #2 below (between 0x88 and 0x11) represents the Thunderbolt Bus ID. If you have multiple Thunderbolt controllers, assign a different bus to each one. If you change this byte, please re-compute the CRC-8 checksum.
The first byte of ThunderboltConfig should then be changed to the same Bus ID.
"ThunderboltDROM",
Buffer (0x76)
{
0x88, 0x00, 0x11, 0x11, 0x11, 0x11, 0x11, 0x00,
0x00, 0xD9, 0xF6, 0xC7, 0xE2, 0x01, 0x69, 0x00,
0xED, 0x00, 0x07, 0xA2, 0x01, 0x01, 0x08, 0x81,
0x80, 0x02, 0x80, 0x00, 0x00, 0x00, 0x08, 0x82,
0x90, 0x01, 0x80, 0x00, 0x00, 0x00, 0x08, 0x83,
0x80, 0x04, 0x80, 0x01, 0x00, 0x00, 0x08, 0x84,
0x90, 0x03, 0x80, 0x01, 0x00, 0x00, 0x05, 0x85,
0x50, 0x00, 0x00, 0x05, 0x86, 0x50, 0x00, 0x00,
0x02, 0x87, 0x0B, 0x88, 0x20, 0x01, 0x00, 0x64,
0x00, 0x00, 0x00, 0x00, 0x00, 0x03, 0x89, 0x80,
0x05, 0x8A, 0x50, 0x40, 0x00, 0x05, 0x8B, 0x50,
0x40, 0x00, 0x0B, 0x01, 0x47, 0x49, 0x47, 0x41,
0x42, 0x59, 0x54, 0x45, 0x00, 0x11, 0x02, 0x47,
0x43, 0x2D, 0x54, 0x49, 0x54, 0x41, 0x4E, 0x20,
0x52, 0x49, 0x44, 0x47, 0x45, 0x00
},
CRITICAL WARNING:
Do not copy and paste the text above into MaciASL. Instead, copy-and-paste from the spoiler below. Failure to do so will be catastrophic.
After a mind numbing sequence of reboots, clearing Corsair registry entries, etc. and re-installing til I was totally over RGB, I realised that my SM-Bus driver wasn't displaying. After a whizz through the MB DVD, I managed to get iCue stable enough in the non software mode, instant colour, that I could actually select a colour before it crashed. I don't know what Corsair are playing at with that software; gravy on the tin, mud inside. I've sacked off their fans and replacing with Silverstone hardware/remote control. Will post my build at some point though it's Vanilla
I didn’t realize it was already. I just wanted to make sure it was available.
It would be great to get a modified version, but there’s a chance it’s the same as the Titan Ridge 1.0 50 firmware (Green chip was the same as 1.0). I would like to learn how you’re modifying it. Can you tell me which editor (program) who prefer?
If it is different from 1.0, I’d be happy to test it. Thanks for all your help for the whole community.
I didn’t realize it was already. I just wanted to make sure it was available.
It would be great to get a modified version, but there’s a chance it’s the same as the Titan Ridge 1.0 50 firmware (Green chip was the same as 1.0). I would like to learn how you’re modifying it. Can you tell me which editor (program) who prefer?
If it is different from 1.0, I’d be happy to test it. Thanks for all your help for the whole community.
The modified version was added to the Repository earlier this morning along with the DROM Micro-Guide. Please give it a try with the understanding that these modified firmwares are not perfect. It may be necessary to hot-plug devices or to warm-boot the system. And modified firmware may not play well with Windows (it may be necessary to boot macOS first and warm-boot into Windows).
In terms of the other things taken from the SleepAid, I haven't tried TCPKeepAlive or anything to do with Proximity wake, as the logs are saying it's a Darkwake (and it only wakes for less than a minute). I'm hoping this solves it!
- With the modified DROM that @CaseySJ so kindly edited for me, I get full activation on both my Mobo's built in Alpine Ridge controller AND the GC-TRv2.
- Under System Report/Thunderbolt, it now shows 4 available 40gb/s ports instead of just 2 on the GC-TRv2. (another DROM thing perhaps?)
- hot-plug/use USB-C devices behave like normal.
- Sleep/Wake works with device plugged in.
- Antelope Audio Devices still do not work - I will be seeing if any new errors pop up from verbose relating to this. My gut is telling me its going to be the same but want to double check.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.