EliteMacx86

Administrator
Staff member
Joined
Jul 22, 2018
Messages
2,830
Motherboard
Supermicro X11SPA-T
CPU
Intel Xeon W-3275 28 Core
Graphics
2xAMD RX 580 8GB
OS X/macOS
11.0.x
Bootloader
  1. OpenCore
Mac
  1. MacBook Pro
Mobile Phone
  1. Android
  2. iOS
How to Enable Antelope, PreSonus, Slate Digital, Focusrite and Apogee Audio Interface on macOS
An EliteMacx86 Exclusive Guide - This guide covers the implementation of Antelope, PreSonus, Slate Digital, Focusrite and Apogee Audio Interface on macOS for Thunderbolt compatible systems.

Overview


Recently, we announced that we introduced a solution for these non-working interfaces and a few other Thunderbolt devices on systems with macOS installed. And, we're very happy to announce a public release for this solution to all the users out there who can try and report the bugs for further development for this project.

For more information on the exact issue and compatibility, refer to the thread linked below.

Requirements


The requirements for having this solution are pretty much the same as Thunderbolt. A few additional requirements have been outlined below.

HardwareCompatibility
CPUVT-d Compatible
Motherboard/chipsetVT-d Compatible
ThunderboltTB2 and Later
Real Macs2012 and Later

The very first step is to verify wether you have a supported CPU and Motherboard or not. To confirm the availability of VT-d, follow the steps below.

Visit the link below and select your processor variant.

Under Advanced Technology, make sure your processor supports "Intel® Virtualization Technology for Directed I/O (VT-d)"


Enabling Audio Support for Interface
The next step is to enable Audio for these interfaces. To enable Audio Support, follow the steps below.

STEP 1: Enable Thunderbolt
The very first step is to enable Thunderbolt support for your system. To enable Thunderbolt, follow the steps below.

1. On your target machine, boot the system into BIOS.
2. Under BIOS, find Thunderbolt Settings.
3. Set Thunderbolt to Enabled.
4. Set Security Level to No Security.
5. Restart your system and boot into macOS.

For more information on Thunderbolt Settings, refer to the guide linked below.

For more information on Thunderbolt HotPlug, refer to the guide linked below.


STEP 2: Enable VT-d
The very first step is to enable VT-d support for your system. To enable VT-d, follow the steps below.

1. On your target machine, boot the system into BIOS.
2. Under BIOS, find Intel VT-d. On some machines, the name can be simply VT-d. On a few server motherboards, the option is hidden under Northbridge or Chipset Tab.
3. Set VT-d to Enabled.
4. Restart your system and boot into macOS.

STEP 3: Fix DMAR Table
The next step is to fix the DMAR Table of your system. Normally, the Antelope interfaces should work after following steps 1, 2, and step 3. However, for the systems running Big Sur and later, there is a drawback that is already stated in the OpenCore documentation.

From OpenCore manual, disableiomapper section :
Note 2: Misconfigured IOMMU in the firmware may result in broken devices such as Ethernet or Wi-Fi adapters. For instance, an Ethernet adapter may cycle in link-up link-down state infinitely and a Wi-Fi adapter may fail to discover networks. Gigabyte is one of the most common OEMs with these issues.


Such issues were seen on systems running Big Sur and Later. To overcome this issue, a user @yosoyoco came up with a fix and the idea was to fix the DMAR Table by removing the reserved memory regions from the original OEM DMAR Table, and then further dropping the OEM DMAR Table, and using the fixed DMAR Table.

This fix is required for the systems running Big Sur and Later. Although, few users have reported it on Catalina and prior too. If you have the above systems, you should implement the DMAR Fixing. To fix the DMAR Table, follow the steps below.

1. Extract your native ACPI Tables. We recommend it extracting using Clover, for the highest level of integrity. If you're not aware of how to do that, a guide is already available here.
2. Once you're done with the extraction, copy the origin folder to any working directory of your choice.
3. Open the copied origin folder
4. Locate and copy the DMAR.aml file to your working directory.
5. Download MaciASL.
6. Open the DMAR.aml file using MaciASL. You should have a similar table as the screenshot attached below.

View attachment Screen Shot 2022-01-23 at 11.40.41 AM.png


7. Find the Memory Regions and delete them. In our case, the Memory region starts from line 70 and ends at line 101.
Screen Shot 2022-01-23 at 10.24.32 AM.png

Upon deleting the Memory Regions, the DMAR Table should look similar to the screenshot attached below.

Screen Shot 2022-01-23 at 10.28.20 AM.png

As you can see, it's very clear that now, the memory regions have been deleted. Which is the essence ;)

8. Click on Compile button.
9. Go to File Menu and select Save As option. Make sure to select ACPI Machine Language Binary in the File Format selection.

STEP 4: Required Configuration Changes
The next step is to add the required changes by editing your config.plist. The changes are supported by both bootloaders, i.e OpenCore and Clover.

For OpenCore

ACPI

This section is for loading, blocking, and patching the ACPI tables. The sub-sections are explained below.

Add
This section is for adding the DSDT and SSDT files for your system. This basically includes USB and CPU Power Management SSDT.

The required settings include:

Path*ValueNotes
SSDT-DMARYES
  • This SSDT removes the reserved memory region blocks.
  • This SSDT is required for fixing network adapters with an infinite link cycle loop.

Delete
This section allows blocking the ACPI tables from loading.

The required settings include:

Table Signature*OemTableIdTableLengthCommentAllEnabledNotes
DMARDrop OEM DMAR TableYES
  • This patch drops OEM DMAR table.
  • Mandatory for all systems using Step 3.

Booter

This section is used for booting and provides firmware fixes in relation to boot.efi. The sub-sections are explained below.

Quirks
This section allows to apply certain Booter quirks.

The required settings include:

QuirksValueNotes
ProtectMemoryRegionsYES
  • Protect memory regions from incorrect access.
  • Use this quirk if you have freezes when implementing the DMAR fix.

Kernel

This section is for adding and blocking kexts. The sub-sections are explained below.

Quirks
This section allows to apply certain Kernel quirks. It provides settings related to Kernel and several other options related to BIOS/UEFI and USB ports.

The required settings include:

QuirksValueNotes
DisableIoMapperNO
  • Disables IOMapper support in XNU (VT-d), which may conflict with the firmware implementation.
  • This option is a preferred alternative to deleting DMAR ACPI table and disabling VT-d in firmware preferences, which does not break VT-d support in other systems in case they need it.
  • Enable this quirk if you cannot disable VT-d in BIOS/UEFI.

Note:
The Value NO means it will be unchecked.
The above configuration changes are in addition to your current config.plist changes.

For Clover


ACPI


This section is for loading, blocking, and patching the ACPI tables. The sub-sections are explained below.

Drop Tables
This section allows blocking the ACPI tables from loading.

The required settings include:

Signature*Type/KeyString[Tabled]Number[Length]DropForAllOSNotes
DMAR
  • This patch drops OEM DMAR table.
  • Mandatory for all systems using Step 3.

SSDT
This section is for adding the DSDT and SSDT files for your system when using a Sorted Order. If you're using Full patched DSDT+SSDT, set Drop OEM to true. When using this option, you also need to use Sorted Order. See Sorted Order information below.

SortedOrder
This section is for adding the DSDT and SSDT files for your system when using a Sorted Order. If you're using a Sorted Order configuration, add SSDT-DMAR.aml to the list. If you're using


Quirks

This section allows to apply certain Kernel quirks. It provides settings related to Kernel and several other options related to BIOS/UEFI and USB ports.

The required settings include:

QuirksValueNotes
DisableIoMapperNO
  • Disables IOMapper support in XNU (VT-d), which may conflict with the firmware implementation.
  • This option is a preferred alternative to deleting DMAR ACPI table and disabling VT-d in firmware preferences, which does not break VT-d support in other systems in case they need it.
  • Enable this quirk if you cannot disable VT-d in BIOS/UEFI.
ProtectMemoryRegionsYES
  • Protect memory regions from incorrect access.
  • Use this quirk if you have freezes when implementing the DMAR fix.

Note:
The Value NO means it will be unchecked.
The above configuration changes are in addition to your current config.plist changes.



STEP 5: Modifying the EFI Configuration

The next step is to modify the configuration. To modify, follow the steps below.

For OpenCore
If you're using OpenCore, follow the steps below.

1. Mount your ESP.
2. Go to EFI/OC/ directory and open your config.plist.
3. Implement the changes as described in STEP 4.
4. Go to NVRAM section and select "7C436110-AB2A-4BBB-A880-FE41995C9F82" under UUID list.
5. From Boot args, remove "dart=0."
6. Save your config.plist.

For Clover
If you're using Clover, follow the steps below.

1. Mount your ESP.
2. Go to EFI/OC/ directory and open your config.plist.
3. Go to Boot Tab and under boot args, remove "dart=0."
4. Implement the changes as described in STEP 4.
5. Save your config.plist.

STEP 6: Set Up Drivers for your Audio Interface
The next step is to set up drivers for your Audio Interface. To set up the drivers, follow the steps below.

1. Remove the preinstalled launchers and drivers.
2. Visit your Interface manufacturer's website and download the appropriate drivers for your Audio Interface.
3. Install the required drivers for your Audio Interface.

STEP 7: Set up Audio Interface
The next step is to set up Audio Interface. To set up your Audio Interface, follow the steps below.

1. Reset your Audio Interface twice.
2. Shut down your Audio Interface.
3. Connect it to your System.
4. Restart the System.

Now the installation is complete!

Enjoy your Audio Interface on your system :)

Notes:
  • For some manufacturers, you may need to signup for an account to access the downloads.
  • For some Audio interfaces, you need to download Launcher and Drivers. In case, if the Launcher has an option to install the drivers, just download the launcher.
  • For Big Sur and Later, you may need to allow the loading of drivers from System Preferences>Security & Privacy.
  • Use the latest drivers for your Audio Interface.
  • A proper Thunderbolt Hotplug is required for better functionality.

Project Status, Bugs, and Further Development

As stated previously, we were supposed to bring the solution to the public and with the release of this solution, there are a few bugs that have been outlined below.

Bug #1
With some motherboards, when enabling VT-d, the entire Network feature is disabled such as Ethernet and WiFi. However, this issue is only limited to Big Sur. A current workaround is to use Catalina or any USB-based WiFi/Ethernet Adapter. Another issue is on some motherboards, the USB ports are broken. We're still testing the project under several environments and hoping to make it more reliable for the users.

Solution: Implement STEP 3.
Status: Resolved

Bug #2
Implementing DMAR fix served the purpose, but interestingly, we noticed another side effect which was random freezes under load, and while Antelope was detected and Network behaved well, Antelope was unable to bind in the Control Panel. It could also not perform administrator related tasks such as updating the firmware to the interface.

Solution
To overcome this issue, another solution was approached by the EliteMacx86 team which was to use ProtectMemoryRegions quirk. The fix has been described in STEP 4, under quirks section.

Solution: Implement STEP 4, ProtectMemoryRegions qurik.
Status: Resolved

Unresolved
The old Unsupported Macs, i.e Macs from 2011 and below, which does not feature VT-d, are still not supported by this solution, and the only workaround as of now is to use macOS Sierra and the same is applicable for other machines which do not supports VT-d function.

AMD CPUs are still not supported by this solution and to overcome this issue, the second workaround is what works as of now.

Contribution
If you can consider a contribution towards the forum for bringing this solution to you, a donation is more than welcome to support this project and help developers to keep the development in progress.

Regards,
EliteMacx86
 
Last edited:

melodyjj

New member
Joined
Jun 3, 2021
Messages
12
Motherboard
GIGABYTE-Z390-GAMING X
CPU
I7-9700K
Graphics
AMD-R9 280X
OS X/macOS
11.0.x
Bootloader
  1. OpenCore
Mac
  1. iMac
Mobile Phone
  1. iOS
Does this method need to flash the custom firmware on the Thunderbolt card first?
 

EliteMacx86

Administrator
Staff member
Joined
Jul 22, 2018
Messages
2,830
Motherboard
Supermicro X11SPA-T
CPU
Intel Xeon W-3275 28 Core
Graphics
2xAMD RX 580 8GB
OS X/macOS
11.0.x
Bootloader
  1. OpenCore
Mac
  1. MacBook Pro
Mobile Phone
  1. Android
  2. iOS
Does this method need to flash the custom firmware on the Thunderbolt card first?
No, that's only needed for special features.
 

BDRStudio

New member
Joined
Jun 11, 2021
Messages
2
Motherboard
Asus Prime z-270a
CPU
Intel i7 7700k
Graphics
Nvidia GT710
OS X/macOS
10.15.x
Bootloader
  1. OpenCore
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
Hello, i'm having problems enabling vt-d, my hackintosh boots up but and everything seems normal except all the usb ports don't work, this only after i enable vt-d. Is this an issue that can be fixed easily?

Thanks
 

EliteMacx86

Administrator
Staff member
Joined
Jul 22, 2018
Messages
2,830
Motherboard
Supermicro X11SPA-T
CPU
Intel Xeon W-3275 28 Core
Graphics
2xAMD RX 580 8GB
OS X/macOS
11.0.x
Bootloader
  1. OpenCore
Mac
  1. MacBook Pro
Mobile Phone
  1. Android
  2. iOS
Hello, i'm having problems enabling vt-d, my hackintosh boots up but and everything seems normal except all the usb ports don't work, this only after i enable vt-d. Is this an issue that can be fixed easily?

Thanks
This is a bug which still needs to be fixed. Create a separate thread to debug the issue and track your progress.
 

melodyjj

New member
Joined
Jun 3, 2021
Messages
12
Motherboard
GIGABYTE-Z390-GAMING X
CPU
I7-9700K
Graphics
AMD-R9 280X
OS X/macOS
11.0.x
Bootloader
  1. OpenCore
Mac
  1. iMac
Mobile Phone
  1. iOS
[With some motherboards, when enabling VT-d, the entire Network feature is disabled such as Ethernet and WiFi. However, this issue is only limited to Big Sur. A current workaround is to use Catalina or any USB based WiFi/Ethernet Adapter.]. ----- 8G 16G 24G memory everything is normal. ----The entire network function of 32G memory is disabled. Ask for help
 

EliteMacx86

Administrator
Staff member
Joined
Jul 22, 2018
Messages
2,830
Motherboard
Supermicro X11SPA-T
CPU
Intel Xeon W-3275 28 Core
Graphics
2xAMD RX 580 8GB
OS X/macOS
11.0.x
Bootloader
  1. OpenCore
Mac
  1. MacBook Pro
Mobile Phone
  1. Android
  2. iOS
[With some motherboards, when enabling VT-d, the entire Network feature is disabled such as Ethernet and WiFi. However, this issue is only limited to Big Sur. A current workaround is to use Catalina or any USB based WiFi/Ethernet Adapter.]. ----- 8G 16G 24G memory everything is normal. ----The entire network function of 32G memory is disabled. Ask for help
With Catalina, there is no such issue. What macOS version are you using?
 

melodyjj

New member
Joined
Jun 3, 2021
Messages
12
Motherboard
GIGABYTE-Z390-GAMING X
CPU
I7-9700K
Graphics
AMD-R9 280X
OS X/macOS
11.0.x
Bootloader
  1. OpenCore
Mac
  1. iMac
Mobile Phone
  1. iOS

EliteMacx86

Administrator
Staff member
Joined
Jul 22, 2018
Messages
2,830
Motherboard
Supermicro X11SPA-T
CPU
Intel Xeon W-3275 28 Core
Graphics
2xAMD RX 580 8GB
OS X/macOS
11.0.x
Bootloader
  1. OpenCore
Mac
  1. MacBook Pro
Mobile Phone
  1. Android
  2. iOS

melodyjj

New member
Joined
Jun 3, 2021
Messages
12
Motherboard
GIGABYTE-Z390-GAMING X
CPU
I7-9700K
Graphics
AMD-R9 280X
OS X/macOS
11.0.x
Bootloader
  1. OpenCore
Mac
  1. iMac
Mobile Phone
  1. iOS
Gigabyte GC-Titan Ridge v2.0 cannot run on win10 after flashing the firmware. After flashing the firmware, it can run normally on the mac
 

Forum statistics

Threads
575
Messages
5,847
Members
5,104
Latest member
lushpen