Contribute
Register

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

Hello,

I've been happily running this build since 2018. I'd like to update it with all the latest improvements discovered along the way, and also move from Clover to OpenCore. I've found the OpenCore Mini Guide, but wanted to know if it's worth the work now, or better to wait until the process is more stable?.

How has been the process and results for those that did the switch?
The switch was seamless and only took a few minutes for me. My system has been noticeably more stable since.
 
Did you tried the trick in the first post: https://www.tonymacx86.com/threads/...olt-3-i7-9700k-amd-rx-580.267551/post-2118036

«Disabling wake from USB». Only wake by power button.

@brousseau6933, Thx a lot!!
It works for me!!

At least my first tries, I force going to Sleep and hopefully all fans and lights go OFF!
For waking up, as expected, only works the power button, but it's not a main concern!

I have just ordered another wifi card, a true Fenvi T919 (not the MQUPIN Fenvi) and will try other methods, but if not, it's OK for me.
Thank you again!
 
I have a monitor with a bunch of usb ports and I needed to connect an i1Display Pro directly to the monitor, plus I want to connect phones and stuff since those ports are easy to access. I was gonna come here to ask for help with getting usb 2.0 devices to work through the Designare's TB3 ports, but I figured it out on my own and thought I'd share the solution for others who might need usb 2.0 through usb-c/TB3.

I remapped the usb ports by editing SSDT-UIAC-DESIGNARE-Z390-V7.aml using MaciASL. Since my case doesn't have a front usb-c port I removed SS01 and added HS13 (which is the lower of the two TB3 ports). That means removing:

C++:
"SS01",
                    Package (0x04)
                    {
                        "UsbConnector",
                        0x09,
                        "port",
                        Buffer (0x04)
                        {
                             0x11, 0x00, 0x00, 0x00                           // ....
                        }
                    },

And adding:

C++:
"HS13",
                    Package (0x04)
                    {
                        "UsbConnector",
                        0x09,
                        "port",
                        Buffer (0x04)
                        {
                             0x0D, 0x00, 0x00, 0x00                           // ....
                        }
                    },

I also removed SS05 since I use HS05 for a logitech dongle (bad reception if I put it in the back) and added HS08 so both TB3 ports work with usb 2.0 devices.
 
Hi @CaseySJ ,

Do you know if any body has tried Antelope Audio with flashed TB bus? I 'm about to buy one Antelope Audio Zen Studio+ but saw the in the 1st post that Antelope has some issues with non-flash TB.

Also if I flash a Alpine ridge card on post 16393, Thunderbolt Bus/Local Node is enabled right? Like on Z390.

Thanks,
 
Hi @CaseySJ ,

Do you know if any body has tried Antelope Audio with flashed TB bus? I 'm about to buy one Antelope Audio Zen Studio+ but saw the in the 1st post that Antelope has some issues with non-flash TB.

Also if I flash a Alpine ridge card on post 16393, Thunderbolt Bus/Local Node is enabled right? Like on Z390.

Thanks,
Unfortunately, Antelope Audio Thunderbolt devices will not work with Mojave or Catalina regardless of flashed or unflashed Thunderbolt firmware.

Feel free to search this thread for posts by @qthegaijin to see for yourself...
 
Thanks! Found the post #17565.

Looks like I have to go with UAD box. Thanks!

Unfortunately, Antelope Audio Thunderbolt devices will not work with Mojave or Catalina regardless of flashed or unflashed Thunderbolt firmware.

Feel free to search this thread for posts by @qthegaijin to see for yourself...
 
Thanks for the reply @jiffyslot but I was referring to the TB Titan Ridge flash for the onboard thunderbolt controller. I think I going to attempt anyway as this is the best way to run TB devices.

Sure thing. For some odd reason, I have full "Thunderswap" for my Apollo 8 without the onboard TB chip flash. I can't recall if I added the Apollo's UUID, but I finally got it to work back in the early days of the 'rona. It works with Clover and with OC. Weird but wonderful.
Thanks! Found the post #17565.

Looks like I have to go with UAD box. Thanks!

FWIW, they just released a new box.
 
Hi everyone, I am having an interesting issue with my Designaire and am looking for some advice on how to troubleshoot/isolate the problem before I proceed down the path of simplifying my system materially.

I have updated my Designaire to boot OC and am running the latest Catalina. I am using two displays, one of which is connected to a TB2 ATEN switch and then to my Designaire. When using Zoom and on a video call using the TB attached monitor, the screen will blank out after a minute or two and then return when I wiggle the trackpad. Interestingly, this does not happen when I move the Zoom window to the direct attached monitor. I do not have this problem when not using Zoom.

Do you have any advice on how I can confirm via logs or other artifacts what is causing this problem? In parallel I am going to rebuild a simplified system to see if this occurs on a vanilla install running only Zoom.

Thanks in advance for any suggestions!
 
Ops, sorry. I thought the forum would do that automatically.
I've given the following advice a few times recently, and it applies here as well:
  • If wake-from-sleep was working prior to Clover 5120, and shutdown was occurring within a short time, then it's best to re-validate that by booting from the previous EFI folder as follows:
    • Connect your bootable backup disk
    • Reboot and press F12 at the Gigabyte splash screen to open the BIOS Boot Menu (not Clover Boot Menu)
    • Select the bootable backup disk
    • When the old version of Clover appears, select the internal macOS SSD
  • Does wake-from-sleep work properly? Does the system shut down rapidly?
  • If both answers are 'yes' then begin comparing each of the following folders between the old and new versions of Clover because the Clover 5120 installer may have installed additional files that you might not have noticed:
    • Compare the CLOVER/Kexts/Other folders. Are the old and new folders identical?
    • Compare the CLOVER/drivers/UEFI folders.
    • Compare the CLOVER/ACPI/patched folders.
 
Back
Top