Oh didnt know. I just went with the latest and the string you posted
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
Oh didnt know. I just went with the latest and the string you posted
@DSM2.Hackintosh I'm happily following along and will be practicing on an Alpine Ridge card until I can afford a GC-Titan Ridge. I was just working in a studio with a MP 5,1 and they asked for help when they learned that I use a stable hackintosh so this couldn't possibly come at a better time.
Is there a world where there is a guide to patching firmware so I can get my Alpine Ridge to behave this way? I can find my way around the firmware but it's a shot in the dark as to what needs to be patched.
Anyways, thanks for your contribution. You're a monster!
Anyways, thanks for your contribution. You're a monster!
Last edited:
Another observation I have, which hopefully can add some insight, is the difference in TB kexts between versions 10.12.2, 10.12.6, and 10.14.6.
The only reason I can see Antelope Audio devices not working under the same Built-In Alpine Ridge config with just an OS update (when previous OS updates were fine) has to do with how Apple implemented their Alpine Ridge and Titan Ridge drivers. For example, 10.12.2 DOES NOT SEE the modified TR card AT ALL as being part of the system, which I assume is because TR support was never written into those drivers...but 10.12.6 DOES see the card as attached and populates the Thunderbolt drivers tab, leading me to believe that TR was implemented in either 10.12.5 or 10.12.6 in a security update.
I will be doing more tests on the Mac Pro 5,1 at my work with the antelope stuff to see if it behaves the same as on the hackintosh.
The only reason I can see Antelope Audio devices not working under the same Built-In Alpine Ridge config with just an OS update (when previous OS updates were fine) has to do with how Apple implemented their Alpine Ridge and Titan Ridge drivers. For example, 10.12.2 DOES NOT SEE the modified TR card AT ALL as being part of the system, which I assume is because TR support was never written into those drivers...but 10.12.6 DOES see the card as attached and populates the Thunderbolt drivers tab, leading me to believe that TR was implemented in either 10.12.5 or 10.12.6 in a security update.
I will be doing more tests on the Mac Pro 5,1 at my work with the antelope stuff to see if it behaves the same as on the hackintosh.
Last edited:
Would adding this help? Back when I was just on KGP Hotplug I added it so I could avoid the cold boot problems.
Give a google for Tbtforcepower.efi
Last edited:
For me first boot is showing thunderbolt but apollo doesn’t initialize, then I get kernel restart. After this restart apollo initializes. I wonder if these kernel restart can damage?
The Alpine Ridge doesn't appear to have fully working Thunderbolt (missing all the stuff after IOThunderboltController - missing "PCI-Thunderbolt" property, no SSDT?). Strange that the driver works better in that case.
An IOAudioEngineUserClient is only created when a user app connects to the driver. In the case of the Alpine Ridge, the user app has process id 171 which is the core audio daemon (check in Activity Monitor.app).
I believe the problem is with their driver. Once the pci device appears in ioreg, there's nothing left on the Thunderbolt side that should be required. Maybe they're making a Thunderbolt related assumption that doesn't work with your Hackintosh. Their driver would be more compatible if they did not look outside their PCIe device in ioreg. You could try talking to their support - but they might be the lazy kind that says they only support Macs that come with Thunderbolt.
Restart the computer. Then check the log. Compare the working and non-working case:
Code:
log show --last boot --style compact --predicate 'senderImagePath contains "AntelopeUnifiedDriver"' --info --debugI don't think we should discuss this further in this thread, since you're not using a classic Mac Pro. Consider making a new thread at https://www.tonymacx86.com . I think there's already some threads there about Antelope drivers.
You did talk about MacPro5,1 in your original post here, but you haven't posted any ioreg or log about that setup.
I am testing the MAC PRO 5,1 today in about 3 hours during my downtime at work. It is not at my house so my late night tests cant be done there. ? I will post the ioreg etc of that guy to confirm that it is a driver issue and not specific to hackintosh and present that information to them. I have sent them info before and they were supposed to have "fixed" it with their latest update but it does not seem to be the case.
I sincerely appreciate all the help you have given, once I get everything running on the 5,1 it will probably confirm the driver suspicions.
Last edited:
Kernel Restart used to happen well after login but now they happen at the end of Apple progress bar during booting. I think it’s because I stopped using the “hotplug” string in config from nico last EFI upload ( I didn’t use his EFI just that config injection) not sure. I know only two things changed. Will check late tonight
Last edited:
sorry, i get an newer from him last week - dit not use the EFI he posted
i do some tests for him and sent the IOreg files
I don't believe that the SN18 works without anything,
and apart from haruo saitoh no one else has confirmed this!
@joevt
Installed fresh High Sierra only to be greeted with the current GFX card in the 5,1 not being metal capable. So I ordered an AMD RX 560 to be able to update to Catalina with Opencore.
On a fresh system, with no Opencore:
When I went into system info, loaded up the thunderbolt tab, and the Titan Ridge card is seen.
The antelope orion on the other hand, has the same exact issues as the hackintosh. It is seen by the card but not seen by the system as an audio interface (I want to say it is similar to the issues many hackintosh users were having with the Slate VRS-8).
I tried to get pciutils installed on this system but everytime i try to run it I get this error:
SIP is disabled and I am running it as root.
Here are the driver debug readouts for the Antelope Drivers on the Mac Pro 5,1 and the working one from 10.12.2.
WORKING:
NOT WORKING MAC PRO 5,1:
I have attached the IOreg files for the Mac Pro 5,1 on High Sierra. Once I am up on Catalina I will try there as well.
Installed fresh High Sierra only to be greeted with the current GFX card in the 5,1 not being metal capable. So I ordered an AMD RX 560 to be able to update to Catalina with Opencore.
On a fresh system, with no Opencore:
When I went into system info, loaded up the thunderbolt tab, and the Titan Ridge card is seen.
The antelope orion on the other hand, has the same exact issues as the hackintosh. It is seen by the card but not seen by the system as an audio interface (I want to say it is similar to the issues many hackintosh users were having with the Slate VRS-8).
I tried to get pciutils installed on this system but everytime i try to run it I get this error:
SIP is disabled and I am running it as root.
Here are the driver debug readouts for the Antelope Drivers on the Mac Pro 5,1 and the working one from 10.12.2.
WORKING:
Code:
Timestamp Thread Type Activity PID
2020-03-06 18:25:12.606386-0800 0x110 Default 0x0 0 kernel: (AntelopeUnifiedDriver) Antelope Thunderbolt Audio (Version:3.30 Build:901dc5c 2019-07-30/11:27): starting for device 1d4b a140
2020-03-06 18:25:12.914444-0800 0x110 Default 0x0 0 kernel: (AntelopeUnifiedDriver) AntelopeAudioDevice::setPluginPartition() -- partition 0 32 32 --> 00000000
2020-03-06 18:25:18.337492-0800 0x1d0 Default 0x0 0 kernel: (AntelopeUnifiedDriver) AntelopeTBAudioDevice/247: warning: user-client failed to start
2020-03-06 18:25:37.767099-0800 0x113 Default 0x0 0 kernel: (AntelopeUnifiedDriver) AntelopeTBUserClient/331: error: user-client send message 0000000a failed e00002db (once)NOT WORKING MAC PRO 5,1:
Code:
Timestamp Ty Process[PID:TID]
2020-03-06 17:26:02.124 Df kernel[0:197] (AntelopeUnifiedDriver) Antelope Thunderbolt Audio (Version:3.30 Build:901dc5c 2019-07-30/11:27): starting for device 1d4b a140
2020-03-06 17:26:02.327 Df kernel[0:1de] (AntelopeUnifiedDriver) AntelopeTBMessageChannel: max DMA stall 25
2020-03-06 17:26:02.327 Df kernel[0:1de] (AntelopeUnifiedDriver) AntelopeTBMessageChannel/207: error: Timeout waiting for DMA completion
(once)
2020-03-06 17:26:02.327 Df kernel[0:1de] (AntelopeUnifiedDriver) AntelopeTBMessageChannel/440: error: Timeout waiting for DMA message header
(once)
2020-03-06 17:26:05.040 Df kernel[0:197] (AntelopeUnifiedDriver) AntelopeTBAudioDevice/882: error: error getting device info
2020-03-06 17:26:05.040 Df kernel[0:197] (AntelopeUnifiedDriver) AntelopeTBAudioDevice/785: error: failed to read device info
2020-03-06 17:26:10.041 Df kernel[0:197] (AntelopeUnifiedDriver) AntelopeTBAudioDevice/924: error: no reply getting channel info
2020-03-06 17:26:10.041 Df kernel[0:197] (AntelopeUnifiedDriver) AntelopeTBAudioDevice/791: error: failed to read channel info
2020-03-06 17:26:10.041 Df kernel[0:197] (AntelopeUnifiedDriver) AntelopeAudioDevice::setPluginPartition() -- partition 0 -1 -1 --> 00000000
2020-03-06 17:26:15.041 Df kernel[0:197] (AntelopeUnifiedDriver) AntelopeTBAudioDevice/1011: error: device failed to return sample rates
2020-03-06 17:26:15.041 Df kernel[0:197] (AntelopeUnifiedDriver) AntelopeTBAudioDevice/800: error: failed to read sample rate ranges
2020-03-06 17:26:20.175 Df kernel[0:954] (AntelopeUnifiedDriver) AntelopeTBAudioDevice/705: error: error getting sample rate 0x0 0 0
2020-03-06 17:26:20.176 Df kernel[0:954] (AntelopeUnifiedDriver) AntelopeTBEngine/856: error: failed to set format <private> -> e00002c2
2020-03-06 17:26:20.176 Df kernel[0:954] (AntelopeUnifiedDriver) AntelopeTBEngine/856: error: failed to set format <private> -> e00002c2I have attached the IOreg files for the Mac Pro 5,1 on High Sierra. Once I am up on Catalina I will try there as well.
Last edited:
Ah what do you make of the video? The satellite is different from the Apollo twin; or the Apollo twin is mk1 and we are mk2?
I think you need help from antelope tech support to find out what the problem is. I wonder if there's a problem with communicating with Thunderbolt 1 devices from GC-TITAN RIDGE. I don't think so because the PCIe device is visible. Maybe add an Alpine Ridge device to the chain.
com_antelopeaudio_driver_AntelopeTBMessageChannel::waitForValidBlock(unsigned int) const is waiting 25 times (2 ms each) before reporting an error AntelopeTBMessageChannel: max DMA stall %u\n. Maybe you can change it to allow more retries, but that probably is not the problem.Check current boot-args
nvram boot-argsChange the current boot-args
sudo nvram "boot-args=-no_compat_check debug=0x144" (include contents of old boot-args and add new boot-args)Use the -G option to get verbose output which might show problem more clearly
sudo lspci -G
Cool, thank you for the insight. I sent in all the error messages to Antelope support so we shall see if I get forwarded to the right people. Whats strange is this device is supposed to be TB2, not TB1. I have also tried connecting it through a dock that has an Alpine Ridge controller on it and still the same error messages, both on Mac Pro 5,1 and Hackintosh. I will hopefully also have access to a new Macbook Pro (and possibly trashcan MP) to also see what happens on a full native system. I just hate having to unrack the Antelope unit to travel, so waiting to see what my best options are. @joevt I will gladly shoot you over a few $$ for your troubles and to help fund your research process, i just did so for @DSM2.Hackintosh and would like to thank you for your help with this. You have given more insight into this issue than Antelope support themselves.
My thought process has been that since the apparent goal of this project is to get full TB3 support on a 5,1 tower, then it needs to be able to do what a real mac is capable of doing...without having to ask devs to modify their drivers.
I won't be at work today to try the 5,1 out but should hopefully have time tomorrow to try out those boot args.
@DSM2.Hackintosh , I shot you a little bit of $$ on PayPal for your efforts and your testing fund. I really appreciate everything you and your team are doing for the community.
Last edited:
removed comments and files.. having issues with system related hardware, not flashed firmware.
Last edited:
Hi, Thanks for all this DSM. Very impressive. Thanks for sharing this. I was very curious to see this work in my 5,1 so I acquired a TitanRidge as well as a 134a programmer. I did the voltage mod outlined in this thread and flashed the TR bios. I Installed OC following the steps listed here: https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/
and used your OC that you also graciously shared. After booting into 10.14.6 I confirmed that OC is running in NV as well as the VMM flag is set. But when I check the system report the thunderbolt section says no drivers installed. Am I missing a step? Thanks for any help with this.
and used your OC that you also graciously shared. After booting into 10.14.6 I confirmed that OC is running in NV as well as the VMM flag is set. But when I check the system report the thunderbolt section says no drivers installed. Am I missing a step? Thanks for any help with this.
removed comments and files.. having issues with system related hardware, not flashed firmware.
Last edited:
Another observation...
I am now able to boot 2x with OC only (no option key req'd on 1st boot) by using SSDT-TB3_PXSX_RP21.aml posted by juantrix on tonymacx86.com (follow link on post #684)
[In progress] SSDT for Thunderbolt 3 Hotplug
I am posting in hopes someone might be able to offer some advise. I am running Mojave 10.14.6 on a GA-X99-Designare EX mobo with a Gc titan ridge flashed with DSM2's firmware. My issue I believe it has to do with the pci bridges on this board. Thunderbolt functions but no hotswap when I try to...www.tonymacx86.com
I modified the file to update the ACPI path correctly per LeleTuratti's "Extra" instructions (tonymac post #1):
[In progress] SSDT for Thunderbolt 3 Hotplug
Overview The Thunderbolt hotplug is a problem that has existed for many years, and until now the only way to have working TB devices is to connect them and turn them on before boot. Finally after a long time some progress has been made. This is not a guide! But a starting point for further...www.tonymacx86.com
I have no idea what is different between files as I am new to OC and have no prior experience with understanding SSDT's. Again, hope this helps in debugging efforts.
I have included modified SSDT and my current EFI folder if anyone is interested in testing.
View attachment 897992 View attachment 897993 View attachment 897994
Why use that one when the one supplied by Dsm2 is 2x boot as well?
For the system log, --last boot is used to get messages starting from the last time the computer was booted, which means it's most useful to use the command right after a reboot.
Since there is a daemon component, the daemon should probably be added to the predicate or just look for "Antelope" since both the kext and the daemon contain that name:
log show --last boot --style compact --predicate 'senderImagePath contains "Antelope"' --info --debugAccording to Wikipedia and pci-ids, 8086:1549 is Port Ridge or Cactus Ridge which is TB1.
I look forward to what you find. A comparison of the log after reboot would be interesting.
True. But we could use the help of the devs to find out why the hack is not good enough. Or maybe our hack reveals a problem in their driver that could affect other or future systems (USB4 compatibility?).