Only for hackintoshes.
A boot loader such as Open Core can patch ACPI tabes, no?Only for hackintoshes.
You can’t add the ACPI tables needed for MP5,1 TB intitialization to the MP5,1 EFI firmware, maybe in distant the future it will be possible with careful firmware mods, but not now or soon.
BTW, none of the public tools for compiling ACPI tables work with the EFI firmware Apple used with MP5,1 and need to be corrected and improved before anything.
A boot loader such as Open Core can patch ACPI tabes, no?
Yep, another roadblock.Anyway, it seems Apple uses an Alpine Ridge( 0x1578 ) device on Thunderbolt 3 Macs, so that confuses things a bit. We really don't have good info on how to build a proper ACPI patch for Titan Ridge.
Not going to happen anytime soon.
Windows enables the GC-TITAN RIDGE for PCIe tunnelling. This state doesn't change during a warm reboot. When macOS boots, the Thunderbolt controller acts as a normal PCIe switch and macOS can enumerate PCIe devices in the normal PCIe way using IOPCIConfigurator.After we booted in Windows 10 and the card was signed, where does the Mac save the PCI card setting. Could you save the setup via the regestry app and overwrite it?
This info is just cosmetic. There is a driver attached (as you see in IORegistryExplorer.app) but it's not enough to make it work properly.Why does it say Unknown and on the other hand does it say that there is a driver? Where can you change the entry Unknown or where is this state saved?
The GC-TITAN RIDGE and GC-ALPINE RIDGE cards have Subsystem Vendor ID 0x2222 and Subsystem ID 0x1111.on Hackintosh the same card have different Subsystem Vendor ID.
Windows enables the GC-TITAN RIDGE for PCIe tunnelling. This state doesn't change during a warm reboot. When macOS boots, the Thunderbolt controller acts as a normal PCIe switch and macOS can enumerate PCIe devices in the normal PCIe way using IOPCIConfigurator.
I suppose we can compare PCIe register values to see what is different, a register doesn't need to change value to change behaviour, and there's no way to tell how those values got that way. The thing to do here is to follow the code (whether it's in an SSDT, EFI, or kext). Some source code exists for Linux. Some source code exists for EFI (edk2).
This info is just cosmetic. There is a driver attached (as you see in IORegistryExplorer.app) but it's not enough to make it work properly.
The GC-TITAN RIDGE and GC-ALPINE RIDGE cards have Subsystem Vendor ID 0x2222 and Subsystem ID 0x1111.
I'm not sure why your Mac shows subsystem vendor ID 0x1458. That's the vendor ID for Gigabyte.
The PCIe power cables are necessary only if you want to charge a laptop connected to your computer.Are the black cables that come with Titan ridge necessary. There are no directions
Can the handshake happen with VirtuaBox?
no, nor with VMware or parallel
Possibly. It has to be installed as BIOS. The hard drive should be hybrid GPT/MBR. The MBR should have boot code that runs the boot code from the Windows partition.Thanks for that. Can you Atleast install full version of windows on a separate hard drive using virtuabox eliminating the need to burn iso?
Maybe try fresh install of Windows, and don't use Thunderbolt Control Center? Use the legacy Thunderbolt drivers.Hey y’all. Thanks for everything you’ve shared so far on this topic. After reading the entire thread and exhausting my Google Fu I’ve been unable to get the Titan Ridge card to even function properly in Windows.
After installing the card in PCI slot 1, I installed the drivers provided on the Titan Ridge support page and installed Thunderbolt Control Center. It seems like this was enough for most folks to get it working, but in my case it appears the drivers will not install. Thunderbolt Control Center reports “Thunderbolt Driver Version: N/A.” Since the UWD driver is not installed, the Titan Ridge FW update will not run.
I’ve tried manually installing various Thunderbolt Drivers by right-clicking the .inf files and choosing “Install.” Still nothing. Same result if the card is in Slot 3.
The card recognizes USB-C devices. With the Apple TB3-TB2 adapter it will wake an external TB drive, but it won’t mount.
I’ve put way too much time into this and it’s getting pretty frustrating.
Plz send halp.
Maybe try fresh install of Windows, and don't use Thunderbolt Control Center? Use the legacy Thunderbolt drivers.
Did you install the Titan Ridge firmware update? That might be a problem. Can you show screenshots from windows of firmware version and attached devices?Reinstalled Windows, installed all drivers. Thunderbolt shows up in Device Manager now and TB Control Center shows two available ports. Does not register TB drive when plugged in.
Mojave sees the PCI controller, acknowledges that drivers are loaded, but does not recognize TB2 or TB3 devices. I think this is the end of the road. Thanks for your help.
@All
i have tested the UAD ARROW Solo TB3. start in Windows and i see on THB3 the card is connected.
i warm reboot to Mac OSX and the UAD is not recognized. connected directly on TB3 slot without adaptor.
not work.
ioreg -ilw0 > ioreg.txt