Contribute
Register

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

@Inqnuam I have also crashed with the latest version. One clicked on the icon, the window popups up and crashes.
Previous versions worked for you ?

Please Open Terminal
Bash:
diskutil list -plist > Desktop/HD_Rep_EFI.plist
and post the HD_Rep_EFI.plist from your Desktop
 
Hello all,
I follow this forum and this thread since I started, but i decided to join in cause i reported a very annoying bug and I hope someone (maybe Caseyj - you're a genius man!) can help me. I read everything on the argument, and it's a known problem with Thunderbolt 3 port on my Z490 Vision D. I did everything you all suggest, flashed the firmware, do the "supplemental procedure" assigning Drom unique id and finally my device (the HATED Antelope Orion Studio Synergy Core - I know, it's an Antelope...) is shown correctly on the "Thunderbolt" section of the System Info. It supports hotplug, it never crashes BUT... Antelope Launcher is unable to detect it in any way.
Any suggestions? Please, could you remind me what info do you need? Ioreg, config.plist, anything you need and I'll provide them immediately.
Many many MANY thanks in advance. I am exhausted after days spent trying to fix the problem without bothering anyone.
Hello @Cellubab,

Welcome to the forum. I wish I had good news for the "HATED" Antelope audio interface, but, unfortunately, there is still no solution. Antelope itself needs to improve/modify their drivers otherwise everyone will buy UAD products and no one will care about Antelope. We need to bring pressure on Antelope to support their customers even if those customers use Hackintosh.
 
Hello @Cellubab,

Welcome to the forum. I wish I had good news for the "HATED" Antelope audio interface, but, unfortunately, there is still no solution. Antelope itself needs to improve/modify their drivers otherwise everyone will buy UAD products and no one will care about Antelope. We need to bring pressure on Antelope to support their customers even if those customers use Hackintosh.
I knew there would be few chances but hey, I tried. I will never get a Mac Pro that is priced as a SUV, I will stick to a Mini and use it to pass the processed channels. I don't like UAD, and I don't like to spend 12k euros for an overpriced piece of junk. Geez, Antelope. You really suck at writing drivers. No hackintosh. No windows. The any way to use it properly is to pay fees to Apple. I am really disapponted. We are WAAAAYYY better in building computer.
 
To answer your questions:
  • There is an inconsistency between the file name and the method name, but that is fine. It's just a typo probably made by KGP that has stuck ever since. It's completely benign and can be ignored.
    • File name: SSDT-DTGP.aml
    • Method name: DTPG
  • DSB0 (DownStream Bridge 0) is where the Thunderbolt Native Host Interface (NHI) attaches.
  • DSB1 (DownStream Bridge 1) is where Thunderbolt devices connect when you plug them in to Port 1.
  • DSB2 (DownStream Bridge 2) is where the Thunderbolt USB Controller (XHC) attaches to manage USB devices connected to Ports 1 and 2.
  • DSB4 (DownStream Bridge 4) is where Thunderbolt devices connect when you plug them into Port 2.
    • There is no DSB3.
  • It's okay for DSB1 to omit _DSM method.
  • PCI-Thunderbolt property is technically needed by UPSB only (UpStream Bridge).
  • PCIHotplugCapable property is technically needed by DSB0 only.
Thanks for the clarification.
What can I do to help improve this this SSDT?

At the moment its not suitable for use. It's very unstable, and drops connection often – especially when there's a custom USB SSDT in place...


edit: I see that HackinDROM is the new method, but it doesn't work with my MoBo (KP's on boot)
 
Last edited:
I knew there would be few chances but hey, I tried. I will never get a Mac Pro that is priced as a SUV, I will stick to a Mini and use it to pass the processed channels. I don't like UAD, and I don't like to spend 12k euros for an overpriced piece of junk. Geez, Antelope. You really suck at writing drivers. No hackintosh. No windows. The any way to use it properly is to pay fees to Apple. I am really disapponted. We are WAAAAYYY better in building computer.
Regarding the UAD, had it not been for the work of @Elias64Fr @CaseySJ and others, I would have abandoned my Thunderbolt devices and made peace with my Digi 003R (Firewire 400). I was very close to purchasing one of the Antelope TB devices from ~2015 after returning a Focusrite unit. When my 2018 Z370 build wouldn't hotplug/powerswap on the UAD Apollo, I eventually gave up and bought the high spec CTO 2018 Mini. When I was pulled back in with the Z390 and this @CaseySJ build, I regretted buying the Mini since I already have a couple of the 2012 "white whale" Mini's.

I wonder how you would like a used RME interface. At this point, I wouldn't be shocked if Avid was blocking our builds with their Carbon interfaces.
 
Thanks for the clarification.
What can I do to help improve this this SSDT?
The SSDT is okay.

At the moment its not suitable for use. It's very unstable, and drops connection often – especially when there's a custom USB SSDT in place...


edit: I see that HackinDROM is the new method, but it doesn't work with my MoBo (KP's on boot)
Please remind me:
  • Are you using a Thunderbolt add-in-card such as GC-Titan Ridge?
  • What Thunderbolt device(s) are you using?
  • When you say "drops connection often", what do you mean?
 
Regarding the UAD, had it not been for the work of @Elias64Fr @CaseySJ and others, I would have abandoned my Thunderbolt devices and made peace with my Digi 003R (Firewire 400). I was very close to purchasing one of the Antelope TB devices from ~2015 after returning a Focusrite unit. When my 2018 Z370 build wouldn't hotplug/powerswap on the UAD Apollo, I eventually gave up and bought the high spec CTO 2018 Mini. When I was pulled back in with the Z390 and this @CaseySJ build, I regretted buying the Mini since I already have a couple of the 2012 "white whale" Mini's.

I wonder how you would like a used RME interface. At this point, I wouldn't be shocked if Avid was blocking our builds with their Carbon interfaces.
Avid is not blocking hackingtosh. My carbon works flawless in Catalina hackintosh on this mobo, but like I posted in my earlier thread apple to ethernet adapter is not showing in network devices in big sur and this is the exact reason I am reaching out for support to find a solution to get apple to ethernet adapter working in Big Sur to use carbon(when its becomes supported). I am not technical enough to figure this out. The guys here defiantly are.

Also I have a ufx+ working fine in big sur in case your wondering on my 370 mobo. :) That uses the alphine ridge 1 tb controller. i switch back and forth from windows. My uad card works fine in big sur as well(thats pci) The hd driver should be working in big sur if you have hd native card and something like a mtrx should work(again when its support in theory)
that should give u a idea what works at this point, never tried antelope
 
Last edited:
Regarding the UAD, had it not been for the work of @Elias64Fr @CaseySJ and others, I would have abandoned my Thunderbolt devices and made peace with my Digi 003R (Firewire 400). I was very close to purchasing one of the Antelope TB devices from ~2015 after returning a Focusrite unit. When my 2018 Z370 build wouldn't hotplug/powerswap on the UAD Apollo, I eventually gave up and bought the high spec CTO 2018 Mini. When I was pulled back in with the Z390 and this @CaseySJ build, I regretted buying the Mini since I already have a couple of the 2012 "white whale" Mini's.

I wonder how you would like a used RME interface. At this point, I wouldn't be shocked if Avid was blocking our builds with their Carbon interfaces.
It sucks being so close and give up for a lack of the driver...nearly 3k euros for an interface half developed. I had an rme interface, I bought the Antelope to step up my converters. I tried plugging it in my 2017 iMac and as guess what? It works perfectly. What a shame.
 
@CaseySJ

I just wanted to drop a message here to say thank you - so, so very much. This thread is an actual goldmine. I just discovered it on my renewed search to improve the thunderbolt on my GA-z170x-UD5 TH. Little did I know you'd put together a guide in these pages for that very board and I now have fully native thunderbolt 3, something I've only dreamed of for years. I really can't overstate how delighted I am about this, thank you so much.

I have to note btw - the discoveries on this thread are pretty under-documented elsewhere online. I very nearly never discovered the page regarding my board for example. Are there any plans to transcribe the contents of this thread to an easily searchable and indexable website? If not - would you be interested in such a thing? I could try to put something together, of course crediting all involved in full.

D

EDIT: Quick question - Do I need to do the hackinDROM thing on this board? I've already done everything in your guide here - https://www.tonymacx86.com/threads/...700k-amd-rx-580.267551/page-2102#post-2122559
As far as I can tell everything works absolutely perfectly. I'm getting the correct reading on port 5 too. But i tried uploading the SSDT for this board to the hackinDROM thing, which then gave me a massive SSDT with blank values and i got scared and closed the tab.
 
Last edited:
Back
Top