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
Just to say I have now tested the FireWire ports on the backs of the Thunderbolt screens, and they are not currently working for me.
So, no USB or FireWire passthrough. But the built-in Ethernet ports on the Thunderbolt displays work just fine…
Hey guys, i just flashed my Titan Card following a tutorial i found on github:
github.com
i used the latest 0.23 firmware version from DSM2 to flash the card and all worked well. Installed it in Slot 4 and then downloaded @IndioX 's OC folder from this thread and added the SSDT to my OC current OC folder (@h9826790 's latest config from his OC thread).
I rebooted and could boot my system with no issues. I then edited the config file by adding the ACPI section like in IndioX's file.
Rebooted again but no Bootpicker showed. It just didn't boot into any system. Did a PRAM reset and it booted into Windows again without showing the Bootpicker. I selected the startvolume for OSX throu Bootcamp in Windows and reebooted again. No Bootpicker and after a couple seconds my MacPro just shut off. After pressing the powerbutton the bootsound appears but it just turns off maybe 30sec after that with nothing visible on screen.
any ideas?
thunderbolt-macpro-5-1/GC-TitanRidge.md at master · ameyrupji/thunderbolt-macpro-5-1
My story to add thunderbolt support to my Mac Pro Early 2009 (5,1) - ameyrupji/thunderbolt-macpro-5-1
github.com
I rebooted and could boot my system with no issues. I then edited the config file by adding the ACPI section like in IndioX's file.
Rebooted again but no Bootpicker showed. It just didn't boot into any system. Did a PRAM reset and it booted into Windows again without showing the Bootpicker. I selected the startvolume for OSX throu Bootcamp in Windows and reebooted again. No Bootpicker and after a couple seconds my MacPro just shut off. After pressing the powerbutton the bootsound appears but it just turns off maybe 30sec after that with nothing visible on screen.
any ideas?
Sounds like you break the config.plist, and the invalid config make OpenCore boot to nowhere. Then the cMP self shutdown after 30s.Hey guys, i just flashed my Titan Card following a tutorial i found on github:
i used the latest 0.23 firmware version from DSM2 to flash the card and all worked well. Installed it in Slot 4 and then downloaded @IndioX 's OC folder from this thread and added the SSDT to my OC current OC folder (@h9826790 's latest config from his OC thread).thunderbolt-macpro-5-1/GC-TitanRidge.md at master · ameyrupji/thunderbolt-macpro-5-1
My story to add thunderbolt support to my Mac Pro Early 2009 (5,1) - ameyrupji/thunderbolt-macpro-5-1
I rebooted and could boot my system with no issues. I then edited the config file by adding the ACPI section like in IndioX's file.
Rebooted again but no Bootpicker showed. It just didn't boot into any system. Did a PRAM reset and it booted into Windows again without showing the Bootpicker. I selected the startvolume for OSX throu Bootcamp in Windows and reebooted again. No Bootpicker and after a couple seconds my MacPro just shut off. After pressing the powerbutton the bootsound appears but it just turns off maybe 30sec after that with nothing visible on screen.
any ideas?
You should run the ocvalidate tool to check the config.plist after manually modify it. Especially if there are some big changes, but not just some true / false swap.
Since you can still boot to Windows. That will be easy to fix. You can mount the EFI partition in Windows. and fix the config.plist. Or even completely remove OpenCore. And boot back to macOS, then re-install OC again.
ok i modified the config file in windows back to its old state (i simply replaced it with the one i downloaded from your hardwareacceleration thread). Now i can boot macOS again. THANK YOU! How do i need to modify the config file to make the flashed thunderbolt card work?
Last edited:
That means the format of your config is correct, but some content is wrong.
If you want to see the error message, you can intentionally change one
false to alse, and see if the ocvalidate tool can pick it up.
When i ran it the first time, i ran it over an unedited version of your config file provided in the hardware accel thread. it showed me the same message when i ran it over my edited config which seemed to stop my mac from beeing able to boot.
the only thing i changed was i added this part to the ACPI section like so:
Code:
<key>ACPI</key>
<dict>
<key>Add</key>
<array/>
<key>Delete</key>
<array/>
Code:
<key>ACPI</key>
<dict>
<key>Add</key>
<array>
<dict>
<key>Comment</key>
<string>GC Titan Ridge HotPlug SSDT</string>
<key>Enabled</key>
<true/>
<key>Path</key>
<string>SSDT-TBOLT3.aml</string>
</dict>
</array>
<key>Block</key>
<array/>what did i do wrong?
No error in ocvalidate tool? I didn't expect that.
As you can see, the original (correct) config use the key
Delete, but you erroneously changed it to Block. ocvalidate tool can't pick that up?Also, did you actually copy SSDT-TBOLT3.aml to the ACPI folder?
Yes i did copy the .aml and i also tried it with the Delete key instead of the Block key that is used in @IndioX 's config. No luck with either and no errors in OCValidate
I just noticed that as soon as i have my Windows Drive installed it simply ignores OC and boots straight into Windows without Bootpicker. If i then chhose to reboot into Mac in the BootCamp Assistant it'll reboot and power of couple of secs after the bootchime. I seems it has nothing to do with the config edits i did since this is now also happening after i reversed all changes back to the original config i was using before. This was working all perfectly fine thou before i started with this thunderbolt stuff.
I can't even boot into recovery using cmd+r. as soon as i remove the Windows Drive i can boot into recovery and after selecting the correct bootvolume i get the bootpicker and everything works fine...
any more ideas on how to solve this issue?
SIP disabled -> boot to macOS -> mount EFI partition -> re-bless OpenCore
[automerge]1595845536[/automerge]
I am sure you did something wrong. If I replace that
Delete by Block, OCValidate tool can pick that up straight away.
Last edited:
Can you direct me to where i can get the latest version of ocvalidate? I got mine from here and its still called ConfigValidity
https://github.com/acidanthera/OpenCorePkg/releases
Did that but as soon as i install a drive with another OS it'll boot from that drive instead. I have a SSD with a Linux Install in bay3 and another SSD with Win10 in bay4. 2 regular HDDs without OS in bays 1&2. Whatever OS is first (right now linux in bay3 comes before Win10 in bay4) will be booted straight away without OC. OC is installed on a NvME Drive in a 4x4 PCI Card (same as macOS). I blessed the OC EFI twice now without any errors but situation did't change. How do i change the order the mac is looking for bootdrives upon boot? or should i put an EFI partition with OC on a drive in bay1 although thats not where macOS is?
I now tried putting the OC EFI folder on the EFI Partition of the HDD Drive in Bay1 and blessing that partition but it still boots Linux instead with no bootpicker. when i remove the Linux drive it boots windows. Only when i remove both drives it will boot OC show the bootpicker and allow me to boot macOS
Try remove all drives but only leave the macOS hard drive installed.
Then perform the 3xNVRAM reset (keep holding the keys until 4th chimes).
Then hold Command + R boot to recovery partition -> disable SIP.
Shutdown.
Re-install all drives.
If it can still boot to macOS, then the problem should be fixed.
Now boot to macOS, mount the EFI partition (on your SATA HDD), re-bless OpenCore.
[automerge]1595864993[/automerge]
My fault, ConfigValidity is correct for latest 0.5.9. ocvalidate is for 0.6 beta.
However, as you can see from your link
0.5.9 already use
Delete, but not Block, and ConfigValidity should able to pick that up.
This worked perfectly as you predicted. i can now boot into all 3 operating systems from bootpicker again. Thanks so much!
As for the TB3 PCI Thing i'm gonna leave it for now. i don't need it at the moment and everytime i mess up something in the config, it potentially costs me a day to fix.
@antonlinus
where did you see the >Block< in my config?
or it was an very old for OC 0.5.4?
where did you see the >Block< in my config?
Code:
<key>ACPI</key>
<dict>
<key>Add</key>
<array>
<dict>
<key>Comment</key>
<string>GC Titan Ridge HotPlug SSDT</string>
<key>Enabled</key>
<true/>
<key>Path</key>
<string>SSDT-TBOLT3.aml</string>
</dict>
</array>
<key>Delete</key>
<array/>
<key>Patch</key>
<array/>or it was an very old for OC 0.5.4?
Are the new cards expected to be able to have a Thunderbolt Display (XDR, 5K) displaying boot screens from Open Core or from a WFI gpu before the OS has initialized (on a MacPro5,1)? I think this is the biggest blocker for me of a Thunderbolt Display & adapter.
I'm curious about this: How does the LG UltraFine 5K display (newest version) perform with the current firmware and SSDT? Except for the first cold boot not displaying the OpenCore boot screen, is the display perfectly usable? (Is the OpenCore boot screen always visible on warm boots, do the brightness controls, speakers, microphone and camera all work reliably?)
hi all!
i'm a newbie in this thread and i already read all the posts and didn't find anything proper about the alpine ridge card
already bought one and thought it would be nice to have TB3 on my cMP
is someone who could help me to get this alive?
thanks guys!
i'm a newbie in this thread and i already read all the posts and didn't find anything proper about the alpine ridge card
already bought one and thought it would be nice to have TB3 on my cMP
is someone who could help me to get this alive?
thanks guys!
Adding to my previous query for those knowledgable about the LG UltraFine 5K: would the bootscreen show on a cold boot if DisplayPort #2 were disconnected to enable just USB-C mode (which is available on the second generation model, albeit at 4K)? Also, on a warm boot (in Thunderbolt mode), at what resolution is the bootscreen displayed?
One DisplayPort connected would still be Thunderbolt mode. If it works in macOS (4K max) then it should work for boot (maybe - I don't know for sure). Same would be true for both the old and new UltraFine 5K since they both have a Thunderbolt mode.
It's difficult to tell what the boot resolution is on an LG UltraFine 5K display since it has no on screen menu that shows the current resolution and refresh rate. On my hackintosh, I had always thought that 5K was not possible on my dual cable Dell UP2715K during boot. Recently, I thought that the hires mode must be 4K but looking at the menu showed it was 5K (in the Clover boot menu). Of course, this ability depends on the firmware of the Mac/PC and/or GPU - my hackintosh was using an Nvidia Titan X (Maxwell). The LG UltraFine 5K is just a dual cable display - except it uses Thunderbolt for the two DisplayPort connections.
My Mac mini 2018 shows no boot screen for Intel or AMD graphics when using the Dell UP2715K 5K display.
Is that because the display (the 27MD5KL-B version) only looks for DisplayPort Alternate mode if Thunderbolt mode is not available? Would using a USB-C cable (compatible for video) instead of the Thunderbolt cable force Alt mode? I'm just thinking of ways to make OpenCore visible on a cold boot (especially for FileVault)—the bootscreen is apparently available on a warm boot in Thunderbolt mode (although I'd really like further confirmation of this).
On the other hand, even in Alt mode there is no guarantee. On my 4K display (LG 27UD88-W), I can get a bootscreen when connected to my MacBook (via USB-C), yet on my Mac Pro (via USB-C with the CG-TITAN RIDGE), the display turns on (when the boot picker should appear), but the screen stays black and then goes back to sleep. An image only appears once the display drivers load. Is this because of the CG-TITAN RIDGE (or maybe its firmware as @eksu has alluded to)? Perhaps someone could confirm that OpenCore is visible with the CG-TITAN RIDGE connected to the LG UltraFine 4K.
In the case of OpenCore, the resolution as well as all available modes should be listed in the debug log. For example, this is what I get on my 4K display:
Code:
06:893 00:011 OCC: Mode 0 - 3840x2160:1
06:905 00:011 OCC: Mode 1 - 640x480:1
06:916 00:011 OCC: Mode 2 - 800x600:1
06:928 00:011 OCC: Mode 3 - 1024x768:1
06:939 00:011 OCC: Mode 4 - 1280x1024:1
06:951 00:011 OCC: Mode 5 - 1400x1050:1
06:962 00:011 OCC: Mode 6 - 1600x1200:1
06:974 00:011 OCC: Mode 7 - 1280x960:1
06:985 00:011 OCC: Setting mode 0 with 3840x2160 resolution