Anyone else see that USB-C devices only appear on cold boot? Warm boot the devices seem to disappear.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 testing TB3 AIC with MP 5,1
- Thread starter Flint Ironstag
- Start date
-
- Tags
- cmp egpu gigabyte mojave 10.14 tb3
- Sort by reaction score
I'm not using a flashed TB3 card. I noticed that if the USB 2.0 header of the GC-TITAN RIDGE is not connected to USB, that my USB-C 3.1 gen 2 hard drive does not mount unless I disconnect and reconnect it.
Now I have a problem where the drive is running slower than it usually does (266 MB/s write, 543 MB/s read instead of ≈900 MB/s). I can move it to my Mac mini 2018 and get the 900 MB/s there. I'm not sure what changed with my MacPro3,1. System Information.app says I'm connected at up to 10 Gbps USB speed. lspci says all my Thunderbolt 3 add-in cards are connected at PCIe 3.0 x4 and the PCIe expansion box that they are in is connected at PCIe 2.0 x16.
Now I have a problem where the drive is running slower than it usually does (266 MB/s write, 543 MB/s read instead of ≈900 MB/s). I can move it to my Mac mini 2018 and get the 900 MB/s there. I'm not sure what changed with my MacPro3,1. System Information.app says I'm connected at up to 10 Gbps USB speed. lspci says all my Thunderbolt 3 add-in cards are connected at PCIe 3.0 x4 and the PCIe expansion box that they are in is connected at PCIe 2.0 x16.
I'm back up to 970 - 985 MB/s. Works in Sierra, High Sierra, Mojave, Catalina. I'm not sure what the issue was. I re-disabled SIP using Catalina installer Terminal.app command
csrutil disable. Then modified boot-args: reduced maxmem=64512 to maxmem=63488 (63 GB down to 62 GB) , re-added debug=0x144 (for pciutils functionality). Restarted.
Using the original DSM2 firmware and OpenCore 0.5.7 with the Titan Ridge the bootscreen will NOT show on my LG UltraFine 5K display upon a cold boot but it will after a warm boot. To me it looks like the bootscreen / boot picker is being displayed before the Titan Ridge is activated. It all means that I keep my old Apple Cinema Display connected directly to the DVI output of my RX580 GPU for the purpose of cold booting.
Last edited:
Hi everybody.
I am new to this forum.
Just to add my experience with titan ridge on a 3.1 Mac pro, after hard time trying to. Make it work with dual boot with win 10, I tested it with first boot on ubuntu. Instant working. Sometimes I have to reboot a second time but sometimes it works on the first reboot.
My only problem now, like others on this forum, is that universal audio luna won't work with my 3.1. My apollo sound are works great.
If someone have an idea?
Thanks.
Have a good weekend
I am new to this forum.
Just to add my experience with titan ridge on a 3.1 Mac pro, after hard time trying to. Make it work with dual boot with win 10, I tested it with first boot on ubuntu. Instant working. Sometimes I have to reboot a second time but sometimes it works on the first reboot.
My only problem now, like others on this forum, is that universal audio luna won't work with my 3.1. My apollo sound are works great.
If someone have an idea?
Thanks.
Have a good weekend
LUNA don’t works because need AVX INSTRUCTIONS ON CPU, than cpu after 2011 ... ie i5 i7 etc etc...
From a number of different sources, I now have two different SSDT files and six different modified firmware versions for the Titan Ridge. But I'm not really sure which ones will be the best to use. The two SSDT files are named:
SSDT-TBOLT3.aml (feb. 25. 2020) (2KB)
and
SSDT-TBOLT-KND-TITAN.aml (mar. 13. 2020) (6KB)
The firmware files are:
I would be keen to hear about any experience with the second SSDT file and also the two NVM33 firmwares that anyone here would like to share. Any input as to what exactly the difference between these versions may be would be most welcome.
SSDT-TBOLT3.aml (feb. 25. 2020) (2KB)
and
SSDT-TBOLT-KND-TITAN.aml (mar. 13. 2020) (6KB)
The firmware files are:
- TitanRidgeMacOSFirmware.bin (feb. 24. 2020)
- TitanRidgeNVM23-E64Fr.bin (mar. 15. 2020)
- DESIGNARE-Z390-NVM33-Elias64Fr.bin (mar. 15. 2020)
- TitanRidgeMacOSFirmware.bin (mar. 16. 2020)
- TitanRidgeNVM43-Elias64Fr-Mod.bin (mar. 16. 2020)
- Z390-AORUS-XTREME-NVM33-Elias64Fr.bin (mar. 16. 2020)
I would be keen to hear about any experience with the second SSDT file and also the two NVM33 firmwares that anyone here would like to share. Any input as to what exactly the difference between these versions may be would be most welcome.
Last edited:
the first SSDT is the original writen by nico
the first and second firmware files come from DSM2, nico and two other persons
and are the original files for the titan ridge on a cMP
all others are modified firmware for hackintosh (PC motherboard)
the first and second firmware files come from DSM2, nico and two other persons
and are the original files for the titan ridge on a cMP
all others are modified firmware for hackintosh (PC motherboard)
Thanks for your feedback.
I was under the impression that the fourth firmware file in the list (the one with titel identical to the first one) was an updated version of the original from DSM2. But you state that this is not the case, if I understand you right?
Version 1 and 4 are the same - the original DSM2 firmwares.
2, 3, 5, 6 are all patched by Elias64 and CaseySJ from the tonymac hackintosh site (search for thunderbolt DROM micro-guide)
2 is similar to the DSM2 firmware based on firmware NVM23 which was what also worked with the windows warm boot for the titan ridge AIC. This firmware works best of the AIC versions.
5 is a patched version of the later NVM43 firmware that was released on newer titan ridge cards. It is not nearly as functional as the NVM23 release. There is also a patched version of the newest NVM50 firmware for testing but not working as well as others still.
3, 6 are both patched versions of NVM33 taken from the onboard titan ridge controller in a gigabyte designaire motherboard. Having tested all firmwares on my titan ridge AIC this is the best of them all by a long way. Both thunderbolt ports work with hot plug (complex devices that requires macOS to load drivers will still require a warm reboot) and others have reported that the display passthrough works best on this version as well.
Right now I have left my titan ridge card on this patched NVM33 firmware (3 on your list) and would recommend it over the others. USB C drives correctly work and I have no header or power cables plugged into the card either and these didn't for me on NVM23.
Properly configuring the SSDT is extremely important as well, and with a customised DROM added will enable full Thunderbolt network bridge.
I'M having the same prob as you. Mac 4.1 not seeing the PCI Thunderbolt device and in Thunderbolt showing 20 x 2. Did you manage to get a fix ?
It appears that the firmware is not identical, one is reported as 23.0 the other as 23.1
On my machine (early 2009, 4.1>5.1) the Titan Ridge firmware is reported as 23.0 and that works. I have flashed the card with the TitanRidgeNVM23-E64Fr.bin version of the firmware and have the SSDT-TBOLT3.aml (feb. 25. 2020) (2KB) installed using OpenCore 0.5.7
Posted by DSM2 but actually patched by Elias64 and taken from the development in this thread here https://www.tonymacx86.com/threads/...700k-amd-rx-580.267551/page-1640#post-2087524
I highly recommend flashing your card with the Designare NVM33 firmware!
For me NVM23 (Elias64 patching) worked fine on both ports, but at cold boot would not show any devices connected (USB-C or TB). A quick unplug and replug of the cable at desktop would then populate the thunderbolt device tree but no drivers for my TB3 dock would load until after a warm reboot (my plugable dock has a usb hub, Ethernet, headphone out which populate in the PCI list where it shows when drivers are and are not loaded). After the reboot I still needed to do the unplug / replug for devices to show in the tree but drivers would now be loaded.
With NVM33 I now have connected devices show in the tree from a cold start but still require a warm reboot to get all the drivers for my TB3 dock to correctly load. After the warm reboot I do not have to perform the unplug / replug as the device still shows as connected. NVM33 also seems far better at mounting USB C drives. All 3 of my drives will mount hot plug with this firmware and only 1 did on NVM23 (on either port) although I do not have any power cables or the USB2 header connected which could also be an issue.
Unfortunately neither of those firmware correctly remounts connected devices after the computer wakes from sleep. Doing a cable unplug / replug immediately connects the device and drivers remain loaded through the sleep / wake cycle. Other users on NVM33 have reported that it is the best firmware for video passthrough using the DP In on the titan ridge from the GPU to then drive a thunderbolt screen or use a dock.
my USB3.x devices has allways mounted (after coldboot oder hotplug)
with original 23 firmware and also with first from DSM2 and now E64FR.
TB drive need unplug/replug followed by warmboot > then allways hotplug
on my alpine no unplug/replug needed, only warmboot, but hotplug ends in a kernelpanic
with original 23 firmware and also with first from DSM2 and now E64FR.
TB drive need unplug/replug followed by warmboot > then allways hotplug
on my alpine no unplug/replug needed, only warmboot, but hotplug ends in a kernelpanic
So I just received an Alpine Ridge to test it out... I don’t mind having to boot first in Windows/Linux and then in macOS if that is required, but is there something specific i need to do to make it work?
For e.g. do i need to bridge two pins together like for Titan Ridge?
Thanks.
For e.g. do i need to bridge two pins together like for Titan Ridge?
Thanks.
i've not testet the alpine with warmboot on windows on original firmware
and yes, you need the bridge because of the missing motherboard connector
and yes, you need the bridge because of the missing motherboard connector
I use a Titan Ridge original 23 firmware with windows 10 to get warm boot then go to Mojave
How can I get thunderbolt without windows 10
How can I get thunderbolt without windows 10