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

[moffia]

Hi @CaseySJ,

I have build Z390 Gigabyte Designare, i9-9900k, Sapphire RX 580 all works fairly well. How ever I also have an Apollo Twin x quad core and when I run my system as an iMac19,1 and do a metal test it restarts. If I use iMacPro1,1 I'm able to complete a test, how ever I have a lot of noise in the audio and while running a metal test my usb devices drop. Do you have any suggestions?

Thank you kindly,

Jim

 

[CaseySJ]

Hey @CaseySJ

I just did the OC upgrade from 0.5.7 to 0.5.8. OC 0.5.8 made some changes such as integrated apfs to OC so we don't need apfs driver anymore. Changed Protocol to ProtocolOverrides ..etc
I made some changes to the config.plist according to OC 0.5.8 sample.plist and tweaked it according to our Designare board. I did the sanity check and everything are greenchecked. I've attached the config file. Please take a look to see if it is ok and maybe you can update the config.plist file on the guide.

Hello @hyperx136,

Good points:

• I've posted a revised version of the 0.5.8 ZIP that removes ApfsDriverLoader from UEFI-->Drivers and instead checks-on the new APFS --> EnableJumpstart and APFS-->HideVerbose options.
• For the sake of completeness, the new config.plist also includes a ReservedMemory section.

Have you tried the 0.5.8 NDK version of OpenCore? I'm unable to enable the GUI picker.

 

[CaseySJ]

Hi Again @CaseySJ

As I have said I have direct contact with the Antelope guys. I have direct mail with RMA and Develop team.
Could be possible if we try to adapt or know what really happens? in my x299 in verbose seems to be detected but the communication seems to be wrong. Failing in sample rate.
If I could help with all the hackintosh that I have and my interfaces (I have some here Apogee, Focusrite,...) could be amazing to solve the situation. Or try to send the reports and problems to these guys. If we report exactly the problem they could fix in future versions...

Yes that could be a game changer!

If you are in contact with the people at Antelope Audio, I think @qthegaijin would be able to provide lots of details on the problem. We can help to collect the information that Antelope engineers will need.

Perhaps @qthegaijin can start with a summary of the problem and the observations?

I have the titan card flashed, lets test it

Yes let's do that! We can help you to collect the right information to give to Antelope. Have you already started testing with the flashed GC-Titan Ridge?

 

[CaseySJ]

Hi @CaseySJ,

I have build Z390 Gigabyte Designare, i9-9900k, Sapphire RX 580 all works fairly well. How ever I also have an Apollo Twin x quad core and when I run my system as an iMac19,1 and do a metal test it restarts. If I use iMacPro1,1 I'm able to complete a test, how ever I have a lot of noise in the audio and while running a metal test my usb devices drop. Do you have any suggestions?

Thank you kindly,

Jim

Hi @moffia,

Let me see if @jiffyslot or any other UAD Apollo owners can help. Is the Apollo Twin "bus powered" (i.e. it gets its power from the Thunderbolt cable) or does it have its own power plug?

 

[hyperx136]

Hello @hyperx136,

Good points:

• I've posted a revised version of the 0.5.8 ZIP that removes ApfsDriverLoader from UEFI-->Drivers and instead checks-on the new APFS --> EnableJumpstart and APFS-->HideVerbose options.
• For the sake of completeness, the new config.plist also includes a ReservedMemory section.

Have you tried the 0.5.8 NDK version of OpenCore? I'm unable to enable the GUI picker.

I have not tried it. I did use NDK 0.5.7 for a little while but changed to the standard version since I saw no benefit outside of the GUI. But with the new OC 0.5.8, opencanopy now is working properly with timeout option. Not sure if it is really necessary for most people to use NDK version anymore. I also tried to boot into windows through opencanopy picker and it worked perfectly. Backups, recovery options are working properly as well.

I'm not sure if you are using it already but I did find something neat called OC-tool. It can build OC EFI folder from OC config.plist. Should be useful for different situations.

GitHub - rusty-bits/OC-tool: POSIX shell script that builds an OpenCore EFI folder from an OpenCore config.plist

POSIX shell script that builds an OpenCore EFI folder from an OpenCore config.plist - GitHub - rusty-bits/OC-tool: POSIX shell script that builds an OpenCore EFI folder from an OpenCore config.plist

github.com

 

[NorthAmTransAm]

Hi @moffia,

Let me see if @jiffyslot or any other UAD Apollo owners can help. Is the Apollo Twin "bus powered" (i.e. it gets its power from the Thunderbolt cable) or does it have its own power plug?

Other user here, the Apollo Twin is not bus powered. The only UAD Apollo device that is bus powered is the Arrow. Cheers!

 

[moffia]

Other user here, the Apollo Twin is not bus powered. The only UAD Apollo device that is bus powered is the Arrow. Cheers!

The Apollow twin x has its own power adapter. I'm wondering if it could be my PSU possibly. I think its only a 500w thermal tech and its a about 4 or so years old. Also is there any flags you recommend for using running headless? Trying that option now.

 

[jiffyslot]

Hi @CaseySJ,

I have build Z390 Gigabyte Designare, i9-9900k, Sapphire RX 580 all works fairly well. How ever I also have an Apollo Twin x quad core and when I run my system as an iMac19,1 and do a metal test it restarts. If I use iMacPro1,1 I'm able to complete a test, how ever I have a lot of noise in the audio and while running a metal test my usb devices drop. Do you have any suggestions?

Thank you kindly,

Jim

Hey there Jim,

To be precise, did you mean "x" as in a multiplier for an earlier Twin?
Or capital X as in the Apollo Twin X? Or is it the Apollo Twin X Quad? They're all a little different and the firmware has to be updated for the latest UAD driver release. It won't show up if it's plugged into a USB-C port, yet seems to be working. It needs to get into that Thunderbolt PCI-based goodness to work right: All of the devices in the attached image require a Thunderbolt connection, not a USB-C connection. Hope this is helpful. I'm assuming nothing. I'm mostly familiar with the Apollo 8 (TB2 + dongle)...

The other issue might be that the GB5 test is dragging down the power. What's your CPU vCore at?

 

[jiffyslot]

Yes that could be a game changer!

If you are in contact with the people at Antelope Audio, I think @qthegaijin would be able to provide lots of details on the problem. We can help to collect the information that Antelope engineers will need.

Perhaps @qthegaijin can start with a summary of the problem and the observations?

Yes let's do that! We can help you to collect the right information to give to Antelope. Have you already started testing with the flashed GC-Titan Ridge?

@CaseySJ -Can "Instruments" from Xcode be used to measure changes in the system along a timeline, giving clues as to how problematic drivers are interacting (conflicting, really) with the OS environment? I can run a "recording" sequence in Xcode/Instruments, but IDK how to read the data. I think I suggested this a year ago in relation to measuring Thunderbolt interactions. Again, IDK what I'm doing with this tool...

 

[lambusser]

The post on Insanely Mac could be adapted, but it will disable all USB ports on a particular controller. If we do this to XHC on Designare Z390, we'll lose the ability to wake using even a USB keyboard or mouse. Even a Bluetooth device will fail to wake the system because Bluetooth also operates over USB.

So that leaves us with this:

• Disable the USB port (HS11 or HS12) to which the Corsair is connected. Corsair will still work, but will not be monitor-able from macOS. Windows can still monitor/control the device.
  • If you know that the Corsair is attached to HS11, for example, then simply add uia_exclude=HS11 to Boot Arguments in Clover Configurator.

Hi @CaseySJ,

I removed the HS11/HS12 and rebooted and it still wakes immediately from sleep. I've pulled another 3 or 4 USB connections and it is still doing the same. Here's the log:

2020-05-04 21:05:01.299382-0700 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: XDCI CNVW
2020-05-04 21:05:01.299383-0700 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: XDCI CNVW
2020-05-04 21:05:09.448636-0700 localhost powerd[76]: [powerd:sleepWake] Wake reason: "<private>" identity: "<private>"
2020-05-04 21:05:09.961199-0700 localhost kernel[0]: (AppleTopCaseHIDEventDriver) [HID] [ATC] AppleDeviceManagementHIDEventService:rocessWakeReason Wake reason: Host (0x01)
2020-05-04 21:05:10.129843-0700 localhost kernel[0]: (AppleTopCaseHIDEventDriver) [HID] [ATC] AppleDeviceManagementHIDEventService:rocessWakeReason Wake reason: Host (0x01)

Any idea what could be waking it immediately after it goes to sleep?

Thanks!

Lam