Please let me know what Info you need!!! If you do a search for my posts here, you can find the log files I have posted for when the unit attempts to connect.
My main observation is:
There is a DMA error which happens causing a timeout between talking to the device. The system will see it fine, it shows all the correct device info, but the DMA error with the driver causes the driver to fail and the unit to not be seen as a useable device by macOS.
@CaseySJ @qthegaijin
Hello guys!
"Good News" I have a correctly connect via Thunderbolt to the Antelope device.
Let me explain, I have an
Asus X299 Prime Deluxe (current from 2019) This Mobo have been working fine with my 9960X from the starts. I have an music studio and the main studio interface that actually use is my
Antelope Zen Tour.
Some months ago I had "completed" my final setup, buying a MSI AMD Vega Radeon VII.
The problem was, that after adding this card, my Antelope Zen Tour , started to disconnect USB minutes after playing audio and having audio glitches. For example when you go into folders, scrolling Safari and similar interactions.
Was very frustrating to have a warhorse build with an amazing CPU , 2000$ of Audio interface and everything.... working bad xDDD
I had recorded a video to show you:
After some research, I have found somewhere that my Mobo had audio problems when using VII, so, i decided to buy a new one from Amazon and if that doesn't solved the problems. Well, I could send it back to Amazon.
My try was the
Gigabyte X299X Aorus Master. OK, expensive, well built, compatible with my Titan Ridge Card... Good...
When I had it mounted, I have found the post of
@dolgarrenan who mounted similar "new chipset version" mobo .
So, after of use it, I had found a lot of problems with random BIOS Resets after going into Clover Boot screen.
I'm not new in hackintosh. I have mounted a lot of them in the last 6 years, and I know that X299 is difficult to get a good stable system...
Reading his post, I have got amazed that
@CaseyCZ with some users , had discovered a complete Thunderbolt implementation, so that day I ordered to Amazon es the USB Flasher Tool.
In the meantime, I was testing Antelope Zen Tour (Via USB ) with this new mobo, and I didn't found
apparently random disconnections. But I still had drops, glitches and audio problems, so with the booting problems. I decided to send in these days the Mobo back to Amazon. I have 30 days, so I still have it because of the thing that I'm going to explain now (for tests if needs).
With the Thunderbolt Firmware flashed, I decided to just test in the Gigabyte X299X system inside with an
Belkin Thunderbolt 2 Dock and the Antelope Zen Tour via Thunderbolt 2 + Apple Adapter.
Nothing in ACPI added. just flashed and plugged. All the DSDT and configurations had plans to add it after of this boot (because also I had plan to dissemble and mount back my X299 ASUS).
So, I had booted first with the Belkin Dock, and was detected in "Thunderbolt Devices" inside system report, but any audio device connects (it has as name "USB AUDIO CODEC") and any Ethernet device....
Then I powered off the computer and connected the Antelope Zen Tour.
After booting, Voila!, it was recognized in Thunderbolt devices in system report and also in audio devices as just "
Zen Tour". I oppened my Tidal (like Spotify but lossless) and
it had played sound. 10-20 segs after it disconnected.
So, wow! It's a good beginning to get it. I was thinking "OK, I don't have it completely configured. So, It will work fine after completing the tutorial and everything"
Then, I dismounted the Mobo, and mounted back my Asus X299 Deluxe. When I plugged everything, Belkin Dock was working fine and recognized in Audio, Ethernet and in Thunderbolt devices. But Antelope was showing in Thunderbolt devices also and nothing in audio devices.
So this is the point where we are.
I'm totally avalible guys to test this, and, if we can do something that could make Antelope work, amazing. And, if not, maybe we could find exactly the problem, and send all the reports and results to Antelope team, where I have totally in contact with RMA and develope team.
As I have said in my other message, they want to fix the problem. But its driver use a server connection with the computer. So now that we have a possibility of have completely recognized Thunderbolt in hackintosh, they could just "change" the values that make a problem in the connection... Its just an hypothesis.
I have some other components, also some other Thunderbolt cards. So I can mount parallel the Gigabyte X299X that I have and test in this system that "worked".
Also I have a Gigabyte Z390 Gaming X with i9-9900K and some more computers. all of them with Titan/Alpine cards .
Regards Guys!!