Contribute
Register

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

Here's another question about SIP status on this build using OpenCore 0.5.9, 10.14.6, and Filevault:
When I poll the SIP status in Terminal with csrutil status I get this:

View attachment 480702

Is this a "normal" reading of SIP being enabled? Or do I need to monkey around in Recovery<Terminal for more work?
Yup, boilerplate text. Nothing to worry about, but future versions of macOS may require SIP in some form.
 
Consider switching to 0x3E9B0007 temporarily. Have you searched this site or Google for Luna on Hackintosh?
Casey, I am just simply amazed at your knowledge and even 'intuition'. Just changed the platform ID to 07009B3E and it worked. Thank you once again for lending a hand. Now I am no longer running "headless". Although my Hackintool tells me VDA decoding is fully supported, I am not sure how this ID might impact video performance in regards to QuickSync or DRM issues. I will have to run some tests tonight, but if you have any insight, let me know.

Once again, you are such a gift to this community. THANK YOU!
 
OK. Now Luna is being driven by built-in graphics and when I launch any video intensive app such as zoom or OBS, it tears and artifacts. And because of my configuration, when I use the head mode, my Final Cut Pro will not start. Will have to figure out how to go headless without losing the Luna connection. I did search this site and found one person who had success with Luna Display successfully by using SSDT-UIAC-DESIGNARE-Z390-V7B.aml. I think you helped him out. This hobby is fun and frustrating at the same time. :)
 
Last edited:
Hopefully your interest only extends to reading about it unless you want to head into the storm after a respit of smooth sailing. Catalina seems like a heap of unnecessary trouble for audio users. It seems to have in some way brutalized every fellow DAW person I know who upgraded. I'm going to wait it out until some really essential piece of SW I use won't work anymore on Mojave.
Agreed. I’ve been using DAWS since the mid 90s and have never had so much trouble just getting a stable machine working reliably. I’ve rolled back to Mojave also, and am biding my time there.
 
Agreed. I’ve been using DAWS since the mid 90s and have never had so much trouble just getting a stable machine working reliably. I’ve rolled back to Mojave also, and am biding my time there.
@FormerUser-50757 - what are you running OpenCore or Clover and which versions?
 
Agreed. I’ve been using DAWS since the mid 90s and have never had so much trouble just getting a stable machine working reliably. I’ve rolled back to Mojave also, and am biding my time there.

I have stayed behind in Mojave too. I do tinkering on a separate Catalina SSD. At some point I will have to upgrade, but not yet.
 
Agreed. I’ve been using DAWS since the mid 90s and have never had so much trouble just getting a stable machine working reliably. I’ve rolled back to Mojave also, and am biding my time there.

After 2 weeks of my life wasted trouble shooting Catalina issues I went back to my old and reliable Mojave backup,

So if you deal with pro music/audio apps, my advice it's to do a clean install of Catalina and use only the apps and plugins really updated, don't waste your time upgrading straight from Mojave.
 
** Best Practices Guide for USB 2.0 Devices **
Please do not quote this guide in its entirety. Post a link instead.
Credit: @ziggenpuss @bmoney @kellymac12 @jleahy2

The 10.15.6 release information mentions a fix for USB-related issues (see below). Although the description does not match the USB-freezes reported here in this thread, I'm hoping this will fix those nasty USB-freezes several of you are struggling with.

View attachment 480554

@ziggenpuss @bmoney @kellymac12 @jleahy2 and all others suffering from USB-freezes on Catalina,

Macrumors is reporting that the Catalina 10.15.6 update has fixed usb-freezes for many (real Mac) users.

From the article:
Apple in the release notes for the macOS Catalina 10.15.6 update said that the update "resolves an issue where certain USB mouse and trackpads may lose connection," .... Though Apple's release notes mention mice and trackpads, the problem affected all kinds of devices, including keyboards and other accessories, though it appeared to be limited to USB 2.0 devices rather than USB 3.0 or 3.1 accessories.

Problems included lost connections, freezes, and a failure to work entirely, and those affected were unable to find any kind of fix with methods like SMC resets, safe mode, Disk Utility repairs, and more. The only suitable fix was using a more expensive Thunderbolt 3 hub instead of a USB-C hub.

There have been numerous reports from those who were experiencing the issue that confirm macOS 10.15.6 addresses the issue for all kinds of accessories.

Sounds hopeful!

Although I have the 10.15.6 update installed and it's working properly, I can't verify if it fixes USB-freezes as the problem did not manifest itself on my system (only experienced it once).

Perhaps one of you affected most can install the update (optionally on a bootable backup) to validate it fixes your USB-freezes?

Hope 10.15.6 will put an end to the USB-misery you've been experiencing.
 
Just a small warning from my side, I just updated clover to v5120, but it screwed up my EFI and was unable to boot. I already updated it to 10.15.6 (which is working perfect), and after that, I wanted to update the just released Clover V5120. I placed my Clover V5119 backup back and it works again. I'm not sure why it screws up my EFI, but I'm willing to support with that if someone requires it. @CaseySJ perhaps?

EDIT: I initially updated via de Clover Taskbar Menu app, but now I updated with the PKG file it works fine. I recommend to use the PKG file if you wish to update Clover.
 

Attachments

  • 2020-07-17_15-30-51.png
    2020-07-17_15-30-51.png
    89.9 KB · Views: 65
Last edited:
Just a small warning from my side, I just updated clover to v5120, but it screwed up my EFI and was unable to boot. I already updated it to 10.15.6 (which is working perfect), and after that, I wanted to update the just released Clover V5120. I placed my Clover V5119 backup back and it works again. I'm not sure why it screws up my EFI, but I'm willing to support with that if someone requires it. @CaseySJ perhaps?

EDIT: I initially updated via de Clover Taskbar Menu app, but now I updated with the PKG file it works fine. I recommend to use the PKG file if you wish to update Clover.
Good to know! Interesting that Clover 5120 now includes OcQuirks/OpenRuntime, and integrates "booter quirks" directly into the Clover config.plist. We may need to wait for an update to Clover Configurator.


Screen Shot 2020-07-17 at 7.04.39 AM.png
 
Back
Top