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

pitt1717 · Jan 16, 2020

manfriday said:
OK! I emulated NVRAM to work with OC.
I rebuilt my config.plist from scratch after reading the config manual found at the github repository.
I think the culprit was ACPI->Quirks->DisableVariableWrite
That needs to be set to NO.

I think I tried that as I found it in a post on another forum, and it didn't work. But again, I may have missed a step. I may just make a fresh USB and retry again.
qq, are you doing this using the USB stick or did you remove the Clover rEFI from your drive and replace it with the OC EFI Folder?

yapiyapo · Jan 16, 2020

CaseySJ said:
Have you tried moving Dock 2 to a different USB port? Does it work in some ports (such as the red or yellow ones) but not in other ports?

i tested in yellow and red and blue...everything indicates that this dock was also broken but in macbook works correctly....

manfriday · Jan 16, 2020

pitt1717 said:
I think I tried that as I found it in a post on another forum, and it didn't work. But again, I may have missed a step. I may just make a fresh USB and retry again.
qq, are you doing this using the USB stick or did you remove the Clover rEFI from your drive and replace it with the OC EFI Folder?

I started out on a USB stick until I got to the NVRAM part.. then I removed Clover, etc.

galisrule · Jan 16, 2020

n-d-k fork of OpenCore is awesome

CaseySJ · Jan 16, 2020

FlyinBurritoMan said:
@CaseySJ Thank you for this thread and the guides you have compiled. I have successfully used the Catalina Clover mini guide to set up my Hackintosh. So far, everything seems to work (knock on wood). I kept the Bios to my Designare to F6 (came that way). I'm using a NXZT 4-port internal USB splitter to connect my FV-T919 network card. I'm still setting everything up and will be back it anything goes astray. Honestly, I both was excited for a new hackintosh, but dreaded the install process from my previous Hack. This one is going so much beer than before, all to the thanks of your guides!
I do have two question though, 1.) going forward are Hacks leaning towards OpenCore over Clover? The reason I went with Clover was because the OpenCore guide had the warning of "this is still in beta" and "only for experience Hackintosher" (I'm paraphrasing). And 2.) why would I need two ethernet ports? Do I plug them both in to get twice the network speed? Honestly I don't know.
Thanks!

Hello @FlyinBurritoMan

Glad to hear the build is going well (knock on wood indeed)!

Going forward, my personal belief is that Clover and OpenCore will both continue to be developed. Competition is good. Eventually one might provide a compelling advantage over the other and thereby incite a mass migration. But we as end-users need not worry because this thread will support both Clover and OpenCore. At this time I still wholeheartedly recommend Clover for everyone, and OpenCore for those who wish to experiment mostly on their own.
Two Ethernet ports can have various benefits:
- You may connect one port to Network A, and the other to Network B. This is more applicable in office environments.
- You may connect both ports to Network A, but you won't get twice the speed.
- You may connect both ports to a managed hub or switch on Network A that support 802.11ad Link Aggregation Control Protocol (LACP). This, in theory, will double your network speed, but only when the other end of the connection is also using LACP.
  - Unfortunately, the Intel i211 Ethernet driver (SmallTreeIntel82576.kext) does not support LACP, so this point is moot (for now).
- You can connect one port to Network A and the other port directly to another computer or another Ethernet device for peer-to-peer networking (and self-assigned IPs).

pitt1717 · Jan 16, 2020

CaseySJ said:
Awesome.

By the way, does anyone have a preference between standard OpenCore (acidanthera) or the n-d-k fork of OpenCore?

I plan to update the OpenCore Mini-Guide this weekend, and have been debating whether or not to switch to the n-d-k fork.

the ndk seems to introduce some nice things at boot as you mentioned a few pages back. all I would be concerned with at this point is long term support of the fork. things may change between the two to the point that if becomes depreciated and moving back may be some work...food for thought.

As you can already tell by my posts I haven't really dove deep into all of this. normally I just follow guides and get things running. But now that OC is new and people are sharing info, this may be the time I start digging in. couple of questions...
where/how do you get dsdt's and ssdts? do you have any good links to read, notes to share?
do you have any notes on building open core?
for either of the above, any solid videos to watch?

***all that aside, do you think with the interest of OC now growing, we should split the thread up? its getting quite confusing and hard to look through clover/oc posts

ThomasVJ · Jan 16, 2020

All the parts for this build arrived today including the Saphire RX 580 Pulse.

Let me start with the good news: My Apollo Twin Solo MK1 does seem to work fine through Thunderbolt. The Thunderbolt chain goes through a LG 34UM95 display and further on to the Apollo. I even have USB support on the LG.
Don't put this in the successful Thunderbolt devices list yet, as I haven't done a thorough test yet.

I installed Mojave 10.14.6 using the guide on Page 1. (Catalina is out of the question for the time being because 64bit.)
BIOS is the latest F9B. I did install the OsxAptioFix2Drv-free2000 and will be replacing it with the OcQuirks files tomorrow.

I have one major issue for now: I have hardware acceleration as long as I just use the LG display. As soon as I connect another HDMI display to the RX 580 I loose hardware acceleration on the LG and the HDMI display goes black. Mojave does see the HDMI in About this Mac -> Displays. During boot I see the verbose output on both displays but the HDMI display goes black before the apple logo shows up. Mojave puts the login screen on the HDMI display as well, so I have to log in in the dark.
I actually plan to use two HDMI displays along with the LG display, so if someone could guide me in the direction for solving this HDMI issue, that would make me happy!

I will be posting details about my setup tomorrow but now I really need to sleep.

pitt1717 · Jan 16, 2020

manfriday said:
OK! I emulated NVRAM to work with OC.
I rebuilt my config.plist from scratch after reading the config manual found at the github repository.
I think the culprit was ACPI->Quirks->DisableVariableWrite
That needs to be set to NO.

Are you sure its under ACPI? I see it under booter--quirks.

I'm also getting when running nvram -c as sudo
nvram: Error clearing firmware variables: (iokit/common) not permitted

I guess the error doesn't matter, and I'm not sure what changed from my original folder to the new one. Now get the output when greping nvram. So it looks like it works now.

CaseySJ · Jan 16, 2020

galisrule said:
n-d-k fork of OpenCore is awesome

pitt1717 said:
the ndk seems to introduce some nice things at boot as you mentioned a few pages back. all I would be concerned with at this point is long term support of the fork. things may change between the two to the point that if becomes depreciated and moving back may be some work...food for thought.
...

That's the dilemma: (a) cool and useful new features versus (b) possible dead-ending of the fork. It's also possible that standard OpenCore will, in time, adopt some or all of the new features that are present in the fork.

Those running both macOS and Windows may benefit from the n-d-k fork right now.

So perhaps we should switch to the n-d-k fork now, and once standard OpenCore incorporates all of the critical features that are in the fork, we can switch back to standard OpenCore.

CaseySJ · Jan 16, 2020

pitt1717 said:
...
where/how do you get dsdt's and ssdts? do you have any good links to read, notes to share?

Please see the 4th bullet in this post: