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

[jiffyslot]

My apologies, updated and fixed. Any UAD users have any ideas for my issue? Re-quoted below for ease.

You're powering up the Apollo Thunderbolt stuff before powering up the computer? And I'm assuming you've adjusted your System Preferences:

Check your System Preferences and Ableton's audio engine preferences to make sure that it's not sneaking in a "Pro Tools Aggregate Device" kind of setup. If there's another device that's locked in a sample rate different from your session, that would be an issue. It's the most noticeable because your audio will quite noticeably degrade over several minutes, depending on the difference in sample rates. Or the "not loaded first device" simply won't connect.

I had an issue when I switched my Apollo 8 from the Mac Mini to the Hack and the back to the Mini where I had to reinstall the entire UAD-Mac-v9110 package on the Mini. It's like one system is "imprinting" onto the Thunderbolt stuff and is not willing to let it go. This does not happen between my real Mac Mini's: the 2018 and the 2x 2012's -everything is Mojave except for one of the 2012's.

LMK what happens.

 

[jiffyslot]

There is an option in the Clover preference pane to turn that feature on/off.

Thanks, P1LGRIM!
I've never had the Preference Pane -I always uncheck that option when I update Clover to keep things simple (ha ha). I'll install it and hopefully that'll fix it.

 

[manfriday]

So, last night I overcame the NVRAM hurdle with OpenCore.

At this point, I believe the only hurdle I still have to overcome is my ability to boot into Windows. When I select the Windows menu item, it blue-screens on me.

I suspect I need to manually enter the path to the Windows EFI partition, as is shown in the attached screenshot.

However, I have no idea how to find that crazy long path.
Can someone point me in the right direction? It's probably something simple that I should have learned a long time ago, but the automatic ways have typically worked for me in the past.

 

[Racke]

So, last night I overcame the NVRAM hurdle with OpenCore.
At this point, I believe the only hurdle I still have to overcome is my ability to boot into Windows.
When I select the windows menu item, it blue-screens on me.

I suspect I need to manually enter the path to the windows EFI partition, as is shown in the attached screenshot.

However, I have no idea how to find that crazy long path.
Can someone point me in the right direction? It's probably something simple that I should have learned a long time ago, but the automatic ways have typically worked for me in the past.

View attachment 445253

What did you do, to get NVRAM working?

 

[CaseySJ]

I tried both wireless and with wire! Both the same result


The mouse issue might be due to signal loss issues. Is it a wireless mouse? Does it use Bluetooth or does it use a USB transmitter (such as Logitech USB Unifying Receiver/Transmitter)?

Do you get the same problem when using this mouse on a real Mac?

 

[CaseySJ]

What did you do, to get NVRAM working?

Please see his previous post here:

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

What did you do, to get NVRAM working? Please see his previous post here: https://www.tonymacx86.com/threads/success-gigabyte-designare-z390-thunderbolt-3-i7-9700k-amd-rx-580.267551/page-1299#post-2059609 That change has now been incorporated into the OpenCore Mini-Guide.

www.tonymacx86.com

That change has now been incorporated into the OpenCore Mini-Guide.

 

[CaseySJ]

So, last night I overcame the NVRAM hurdle with OpenCore.
At this point, I believe the only hurdle I still have to overcome is my ability to boot into Windows.
When I select the windows menu item, it blue-screens on me.

I suspect I need to manually enter the path to the windows EFI partition, as is shown in the attached screenshot.

However, I have no idea how to find that crazy long path.
Can someone point me in the right direction? It's probably something simple that I should have learned a long time ago, but the automatic ways have typically worked for me in the past.

View attachment 445253

Please see this post:

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

I plan to experiment with this when I get back from vacation. Are you able to connect another Mac via a Thunderbolt 3 cable? I will try between 2 hackintosh !

www.tonymacx86.com

 

[manfriday]

Thanks! I forgot about the DSDT and SSDT for all OSs issue!

 

[CaseySJ]

Thanks! I forgot about the DSDT and SSDT for all OSs issue!

That OpenCore fork has some more juicy stuff!

 

[nifranza]

Hello @nifranza

Nice to hear from you -- and a happy new year as well!

Though I'm not experienced enough to answer the question about over clocking, I am familiar with the second issue. The ACPI error you're seeing is happening on all systems. The \_TZ device refers to Thermal Zone. If iStatMenus or HWMonitorSMC is showing CPU and other component temperatures correctly, then we can ignore this. I think this error started with Catalina, but I haven't diagnosed it any further.

Hi @CaseySJ, thanks a lot for your answer!

As I said, I don't care about overclocking that much. I was just asking in case the issue was already addressed by another user. I'll continue to experiment on the OC issue by myself and report back with some results.

Regarding the Thermal issue, I'm not experiencing any abnormality on any of my components. But due to the 32 bits app restriction going on in 10.15, I'm staying in 10.14.6 and still experiencing this issue. So I think it is safe to conclude that the ACPI error regarding \_TZ device is more related to BIOS version F9b than it is to OS version since I'm still in Mojave. Do you agree?

Cheers!