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

[PicLock]

Some people have reported many bugs Resolve had with various hardware. The latest Resolve updates should have sorted that out (you downloaded the latest version?).

The iGPU should be inactivated, as CaseySJ indicated, as an active iGPU can make Resolve less stable.

The 475% CPU usage you report is a little bothersome. It should be more like 80 to 95% during max use. I may have missed it, but are you over-clocking? If so, perhaps lower the settings. (If at 5 GHz, maybe try 4.3 or 4.5 GHz.) And, have you set the AVX in BIOS to something like 3, rather than leaving at Auto? That might help.

In looking at the DaVinci spec requirements (here), you should be fine. In the preferences section, you can specify how much RAM is used by Revolve. I've also heard that selecting DNxHR SQ in the optimized media preferences section may help reduce CPU overhead (but at a cost rendering time and storage space).

Are you over-clocking the RAM? I've seen stability improvements by decreasing the DDR4 speed, in 200MHz steps, from the maximum rated speed. The overall loss in computer speed by the reduction is trivial vs the potential for improved stability.

Another source for Resolve crashes in inadequate file permission. Maybe give Resolve full access permission in System Preferences/Security & Privacy/Privacy/Accessibility section. And also check the permissions of the folder where files are being read and written to: highlight folder and right click for "Get Info". Then, at bottom of this window, allow "Read & Write" for all users.

@rj510
I'm back in the studio after my vacation.

I tried setting the AVX in BIOS to 3 and it's still crashes on render. I've also try setting 0 with the same result.
Sometime it crashes at 2%and other time at 50 to 80% point, very random. I also tried rendering to different codec.
When it crashes, it will lock up the machine and the only way out is to reboot.

Permission on disk is set to both read and write and I have also try rendering to other hard drive.
Resolve has full permission in System Preferences/Security & Privacy/Privacy/Accessibility section.

There's no OC on CPU and RAM.
I have 32GB of RAM and have limit Resolve memory usage to 24GB.
I'm using the Studio Version of Davinci Resolve 16.

 

[KristoferG]

Very good -- let's try the following (no guarantees, but something that should be done nevertheless):

• Copy USBInjectAll.kext to CLOVER/kexts/Other. If you don't have this, then future boot into Recovery volume may fail or a macOS update may fail.
• The open the CLOVER/ACPI/patched folder and do this:
  • Move or delete the existing file SSDT-UIAC-DESIGNARE-Z390-FD-DEFINE-R6-V2.aml
  • Replace it with the attached file SSDT-UIAC-DESIGNARE-Z390-FD-DEFINE-R6-V3-HS11-INTERNAL.aml
    • Based on your IOReg output, Bluetooth is connected to HS11 and an ITE Tech device is connected to HS12.
    • HS11 has therefore been set to Internal
    • HS12 is still set to External
  • Also copy the attached file SSDT-EC.aml to the same folder.
• Then reboot.

Again, there's no guarantee this will fix the issue with Rig Manager and USB ports, but let's give it a try.

@CaseySJ I followed all of this, and I think it made a difference: I have to push Rig manager much harder and browse through many more rigs until I get the crash.

 

[betyargabor]

Is there a motherboard that can use the same UEFI folder like Z390 Designare but still cheaper?

Hy!

Can anyone help me?
Is there any motherboard that can use the same UEFI folder like Z390 Designare but still cheaper?

 

[CaseySJ]

Hy!

Can anyone help me?
Is there any motherboard that can use the same UEFI folder like Z390 Designare but still cheaper?

Gigabyte’s Z390 AORUS Ultra is a good alternative. See post 8631 above for USB SSDT. Most of the Clover configuration will be the same as Designare Z390. Just have to replace some SSDTs — we can help you with that once you decide on a particular motherboard.

 

[CODYQX4]

Hi,

I'm glad you're trying out OpenCore. I hope the experience is teaching you a lot.

I don't let the config.plist stay minimal to any level, when I share my config.plist or entire EFI folder.
The reason is that I actually do not condone uploading EFI's for one to use. I am actually going against myself when I do it. I just feel OpenCore is a thing people should be aware of, and that might be the reason why I upload my EFI Folder, when someone asks for it.

Anyhow. I digress...

I don't keep the config.plist minimal because it actually keeps a persons learning experience less, when they don't know what the other functionalities are, despite them not being on. Because when going through the config.plist, eventually they'd have to read everything. Mustn't forget that OpenCore changes every month, and that is also why I wouldn't keep a config.plist I'd upload to a minimal level. Specially when I stand by the learning experience.

When it comes to my NVRAAM working natively. I am not sure why my NVRAM works natively. I've spoken to others with Z390, and they have NVRAM issues. As of now, according to what vit9696 said last time about NVRAM and 300 series boards. It isn't really their primary goal to have it fixed straight away. Eventually they will though, if someone else doesn't do it before them. My friend and I, we've tried every possible way to test why my NVRAM works. We've tested it so much, as if we didn't want it to work (crazy). But it can depend on various things, even your UEFI version.

Answer to your problem #1
When it comes to the time expiring, you can setup more time, or even setup having no time limit.
Your booting issue, not having the default boot is most likely because you haven't gone through scan policy. I have mentioned this in my post where I've uploaded my OpenCore EFI Folder 0.5.1. Also, you might want to read about "RequestBootVarRouting".

• Scan Policy
•RequestBootVarRouting

Answer to your Problem #2
My sleep works well, and even restart and on/off. My sleep didn't work when I first started using OpenCore. I forgot how I fixed it, but it was less to do with OpenCore. I also found that having AGPMinjector kext helped for it.

I'll come back to the sleep issue with an edit on the same post.


I don't mean any ill intent telling you this. And I apologise beforehand if I offend you. But I don't think you followed the documentation to an understanding satisfactory level. This is why I wouldn't make a config.plist I upload to be minimal, because if it was, people wouldn't see what OpenCore has to offer entirely. Especially if they don't read the documentations.

Now, this doesn't mean you didn't read it at all. Sometimes people read documentations and go through what they might think is right for their hardware, but not to a full level. And the documentations of OpenCore aren't exactly an easy OneTwoThree guide to go through, they are manuals and configurations, definitions of each function. It can be overwhelming.

I feel like you're a person who'd rather like to get the learning experience, and be able to independently hackintosh to some level. To actually know what makes your MacOS run on your third-party non Apple hardware. And that is why I feel it is important to refer to the documentations.

I will try to help with OpenCore to the best of my knowledge and effort, if I can. However, let us not forget that OpenCore is on its public beta. The OpenCore's aim is to release updates every month. It changes drastically every month. Something new comes and goes all the time. Because of this fact, I don't think OpenCore should be the main focus of this thread, other than being a hot-topic to mention from time to time, something to anticipate for when the time arises, a test topic. Just like the topic of testing a beta version of MacOS. I feel it'd be wrong to push OpenCore to the guide and its thread, simply because of where OpenCore is today.

Generally saying, when you touch something that isn't released as a final version, it is mostly on you as a person to deal with it. Though you might not find it tough to work with OpenCore, but it might be more time consuming and knowledge requiring at the moment. 

I think there is a misunderstanding. By minimal, I don't mean that I removed sections from the plist, which from the documentation means that OpenCore will use defaults. I have read it over several times carefully.

I mean that between carefully reading the documentation, and testing the effects of each option, I was able to enable the least amount of options needed to boot. There were some things you had enabled that in my case I didn't need.

I did ScanPolicy=2621699 and RequestBootVarRouting=true though it still shows the USB first. I know I can remove USB from ScanPolicy, and it will list my NVME first though. I guess I just expected a different order. Removing USB entirely means I would not be able to boot my bootable backup from the menu. I gave myself a 30 second delay on the menu so I have plenty of time to choose.

With regards to sleep, I will look into AGPMInjector kext as you suggested, as you said your fix was less to do with OpenCore itself.

EDIT: That led me down the right path. I had setup an SSDT for PluginType but had it for CPU0 which I assumed would work because that's what a real iMac19,1 has. I need PR00, so I compiled with that change. I won't be able to test until I get home, but because of this issue, I did not have X86PlatformPlugin loaded. Fixing this may take care of that, and reading about how to setup AGPMInjector requires that working as well. I'll have to test this fix later as I can't do so remotely due to the need to reboot.

 

[betyargabor]

Gigabyte’s Z390 AORUS Ultra is a good alternative. See post 8631 above for USB SSDT. Most of the Clover configuration will be the same as Designare Z390. Just have to replace some SSDTs — we can help you with that once you decide on a particular motherboard.

@CaseySJ: Thank's for you quick response. Maybe i can buy this motherboard. I come back Thank you!

 

[mango1122]

I tried this method without success. In addition, once the Bluetooth is blocked, I can't access the debug menu. I have to restart to get a working Bluetooth back.


It's not greyed out, it's just without effect, I can click on disable but nothing happens. In the Finder menu, I have a broken line on the Bluetooth icon and if I click on it, I get the message "Bluetooth not available".

If you have a Broadcom WiFi/BT card, you will need to upgrade the WiFi/Bluetooth Kexts to the ones that support Catalina. You can find the updated Kexts here:

These are a fork of RehabMans original Broadcom Kexts: https://github.com/headkaze/OS-X-BrcmPatchRAM/releases

Info on these Kexts were found here: https://www.insanelymac.com/forum/t...-catalina-broadcom-bluetooth-firmware-upload/

Remove the 2 WiFi/BT kexts that you were using for Mojave and replace them with the 3 kexts (yes, THREE) from the link above.

Once you replace them then Power off, remove power cord, press power on button a few times. Attach power cord and restart the machine.

 

[phrfpeixoto]

If the rear audio ports work, then we know that AppleALC is functioning correctly. It then becomes a matter of trying different Layout IDs to determine which layout enables front headphone and microphone ports. We use Layout ID 16 (hex 0x10) by default, but other IDs are possible, including 7 and 1. Each Layout ID has its pros and cons, so use the ID that best accommodates your preferences.

My Phanteks Evolv X is a wonderful case, but the front panel audio connector is of rather poor quality. Sound from that connector is gargantually worse than that from the green headphone jack on the rear panel. So I have completely stopped using the front panel ports. In fact, a simple USB audio jack might produce noticeably better sound quality

I have no idea how to change layouts. Could you please point me in the right direction? I've poked on Clover, but could not find it.

Also, I know this is a quite old message. I've been real busy the last couple months and I use this hackintosh for work, so I could not afford causing instabilities.

Thank you for your effort.

 

[kwalter]

@CaseySJ , or anyone else who might have an idea...

I've cloned my system a few times in the past week. Eventually at some point I start getting:
"couldn't allocate runtime area". I haven't been able to nail to cause down to anything specific at all. It just happens out of the blue, on almost every drive I have so far.
-------%<-------

I was getting this error yesterday. I found it would go away if I disabled the internal graphics in the BIOS -
However I needed the internal graphics switched on and the only way seemed to be to use OsxAptioFix2Drv-free2000.efi as you stated

 

[thrf]

Hi @CaseySJ , thank you for thhis massive guide, I hope you can help me. I'm trying to get past clover bootloader following your steps exactly as described but it fails on RandomSeed message.

My build features 9900K + 2x XFX Radeon Vega VII + 128GB 3000Mhz Corsair RAM + Samsung 970 PRO 1TB Nvme + WD Black 1TB NVMe + 3x Samsung QVO Sata3 2TB SSD.

I was able to boot using OpenCore but sleep and shutdown doesn't work.

I've Tried Using F6 and F7 BIOS, i'm using Mojave 10.14.6 installation and iMacPro 1,1 as SMBIOS, i don't want to use iGPU because of Double Radeon VII Cards.

I've also removed the stock Intel Wifi + BT Card from the motherboard.

I could upload any content you need in order to keep this build going, I want to boot using free2000 driver along slide=0 but it wont boot up. Sometimes it shows allocation error as is known, but neither boots with or without error.

I really need to get this build going soon for work. I'll be really thankful for your help ASAP.

Thanks in advance.