Contribute
Register

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

Ahhh... I see the problem. The Vision D is currently not up on GB's USA site.


Thanks @Ploddles
 
I don't understand why there is a need to have the hotplug with sound cards.
I am a professional music producer, and I never and I say never used sleep or hotplug.
Especially with a hackintosh ...
Software like Protools doesn't like it.

I don't get it either. For Pro Tools sleep should be turned off according to Avid, and Cubase turns sleep of by itself, just the screen will sleep.
Hot swapping an interface is just weird. Like switching a hardware analog mixer on half way in the recording session.

On the other hand, I will sometimes walk away or get distracted for a while, and if sleep would work properly even with a DAW running, this would lower the electricity bill somewhat.

Cubase/ULN-8/PSI-17m's with a serious project loaded: 270W. My desk with Hack sleeping: 19W.
 
@CaseySJ Thanks so much for the Thunderbolt DROM Micro-Guide for the ASRock Z390 ITX => https://www.tonymacx86.com/threads/...olt-3-i7-9700k-amd-rx-580.267551/post-2092146

Thanks to the work done by you, @Elias64Fr and @mango1122 (along with many others), I was able to flash the patched TB3 firmware and get native/local Thunderbolt activated.

Cold-Plug, Hot-plug etc all work fine and really well. However, I lose TB3 connectivity after sleep/wake :( Sleep/Wake itself seems to work but TB3 doesn't until I reboot again.

From what you've seen, is this an issue with USB or TB3 SSDT (I'm using the one you attached in the guide with the DROM bytes changed) or could it be that my TB3 flash somehow wasn't as perfect as I thought it was? I'm happy to attach all the relevant files if that helps but figured I'd ask you first if you knew which direction I should go digging.
Hello @sffjawsh,

Unfortunately not all of the modified firmware works equally well. Restoring Thunderbolt connections after wake-from-sleep is an issue in many cases. One option, and admittedly far from ideal, is to modify System Preferences --> Energy settings to only put the display to sleep, but not the computer. At the end of the workday the computer itself can be powered down.

We may look for a solution to this problem, but it could take some time.
 
ok:)...It seems like model is fine...So them my input in device
properties should be correct...do you have any other idea perhaps?

Edit: Video Proc doesnt support AMD HW Acceleration at the moment...So not a problem, a missing feature...Was stated here:
Video Proc no AMD support at the moment
Good post by @jiffyslot. Let me link it here for VideoProc users:
 
Ahhh... I see the problem. The Vision D is currently not up on GB's USA site.
...
Correct -- it's quite annoying. Intentional? Maybe it's delayed...
 
** Micro-Guide: Radeon Speed Boost **
for Vega 56/64, Radeon VII, RX 5500/XT, RX 5700/XT
Please do not quote this micro-guide in its entirely. Post a link instead.​


Why does it need to be in Slot 1 or 2? If I modify the SSDT can I use whatever slot instead (this is for a different motherboard). Thanks!
 
Hi @CaseySJ, I'm back with news regarding my random freezes. I was in my Windows partition for a gaming session and after I got bored I wanted to give a shot to the new native Bluethoot kext. So I restarted the computer, as usual, and aftere selecting the Mac SSD boot drive in Clover I was greeted with another freeze immediately after log-in. It happened 3 times in a row. The only thing that I did differently when I was able to log in was to remove the 2.4ghz usb dongle from my Trust USB Wireless Mouse. I also have my UAD Apollo Twin connected but it's switched off and it was off during the whole time.

Thanks to the Native NVRAM when I eventually logged in I was able to get the Panic Report message attached below.

LE: I attached the first and the last KP reports here as zipped files. Also, the usb dongle disconnected didn't had an impact since I had 4 more times since I wrote this post.
 

Attachments

  • Panic Report.rtf.zip
    5.3 KB · Views: 57
  • Panic Report 2.zip
    4.3 KB · Views: 62
Last edited:
@CaseySJ, when following your Mojave>Catalina guide, you mentioned deleted some Kexts in Library/Extentions, but I don't have an extensions folder, but I see some of those kexts in EFI/CLOVER/drivers64UEFI. Should I delete them from this folder instead?
 
@CaseySJ, when following your Mojave>Catalina guide, you mentioned deleted some Kexts in Library/Extentions, but I don't have an extensions folder, but I see some of those kexts in EFI/CLOVER/drivers64UEFI. Should I delete them from this folder instead?
you shouldn't have any kexts in drivers64UEFI folder, only efi files :)

kexts will go in clover/kexts/other

used to have 3rd party kexts in /Library/Extensions but best with Catalina to keep them in clover
 
Back
Top