Contribute
Register

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

The guide for this is located here:
Another way to check:
  • Run IORegistryExplorer and find GFX0 under PEG0 or PEG1. Click on GFX0.
  • On the right you'll find a large VBIOS dump so scroll all the way down.
  • You should see something like this:
View attachment 435564

Awesome, so I guess things are all "Ok" since the model is reporting as AMD Radeon VII (the same as in About this Mac). But I'm still going to study up on SSDTs and such. ;)
 

Attachments

  • GFX0 IOReg.png
    GFX0 IOReg.png
    674.1 KB · Views: 49
Please try again after adding the following entries to Clover Configurator --> Boot Arguments:
Code:
shikigva=32
shiki-id=Mac-7BA5B2D9E42DDD94
View attachment 435567

That did the trick! Thank you. Videoproc said h.264 acceleration is enabled now and FCPX is running better. HEVC still doesn't work - is there anyway to fix that? I think I read somewhere that only the imac pro sysprofile works for that??
 
That did the trick! Thank you. Videoproc said h.264 acceleration is enabled now and FCPX is running better. HEVC still doesn't work - is there anyway to fix that? I think I read somewhere that only the imac pro sysprofile works for that??

This is the same thing I'm dealing with. Switching from 19,1 to iMacPro1,1 with the iGPU enabled to get HVEC support but still have a fast editing experience in FCP timeline. I think the answer is that you have to switch to iMacPro1,1.
 
@Jrad07

Once post-installation is done (starting with MultiBeast and then fine-tuning manually) as described in the Guide, the system will be bootable without the USB flash disk. If the macOS SSD is not the default boot disk, you can enter BIOS Setup and set the correct boot order. You can also try pressing F12 at the BIOS Splash Screen and checking whether the macOS SSD is among the boot options listed.
Thank you for the info :)
 
This is the same thing I'm dealing with. Switching from 19,1 to iMacPro1,1 with the iGPU enabled to get HVEC support but still have a fast editing experience in FCP timeline. I think the answer is that you have to switch to iMacPro1,1.

Does switching to imacpro 1,1 cause any issues?
 
The guide for this is located here:
Another way to check:
  • Run IORegistryExplorer and find GFX0 under PEG0 or PEG1. Click on GFX0.
  • On the right you'll find a large VBIOS dump so scroll all the way down.
  • You should see something like this:
View attachment 435564

Success!!! Thank you SOOOOO!!! much @CaseySJ and @djx8605 and @JimSalabim. I think I have FINALLY gotten things working optimally using iMac 19,1. It turned out that it was a naming issue for my Radeon VII. Since I had never gotten around to RTFM from the quoted resource above by CaseySJ for renaming devices, I'd been using this Hackintosh since August without the iGPU.

Well, I've now got the iGPU working along with the dGPU. Both iGPU and dGPU show up now in System Information -> PCI (see image). FCP does, in fact, now choose the dGPU for timeline rendering. Both H.264 and HEVC are now hardware based and I'm able to bump up my DVMT thanks to FwRuntimeServices.efi and OcQuirks.efi. I still need to evaluate if FCP/Compressor are using the iGPU or the dGPU. It seems like the dGPU so far. My win is that the iGPU is enabled and the dGPU is being used for timeline editing.

While I had never used Darwin dumper, it was @djx8605 who clued me into what I would consider to be the easiest process for renaming devices if you have Hackintool available. I've outlined the steps in the images below.

I love this learning process and I'm grateful to those who are helping to share the information! I hope this helps others learn more too. My preferred Plist editor can be purchased alone or as part of a nice bundle on the App Store. It comes with a CSV and JSON editor too. All of them are really clean and great for a developer like myself.
 

Attachments

  • dGPU before iGPU.png
    dGPU before iGPU.png
    694.4 KB · Views: 114
  • Step 1 & 2 - Find dGPU Device.png
    Step 1 & 2 - Find dGPU Device.png
    821.6 KB · Views: 101
  • Step 3 - Copy Device Entry.png
    Step 3 - Copy Device Entry.png
    332.7 KB · Views: 90
  • Step 4 - Paste & Rename.png
    Step 4 - Paste & Rename.png
    273.6 KB · Views: 96
Hi @kwalter it's good to know this is not an isolated case. What mistake did you do? Perhaps I've done it too unknowingly. And what did you do differently on the fresh build? I might be able to relate it to how I do mine as well that might have caused the problem. Thanks!
Oh the mistake was nothing to do with Bluetooth. My backup had become corrupted due to sleep not Ejecting my backup drive correctly, while testing the theory that Catalina had resolved the problem. It hadn’t so I set my memory speed back to 2666
 
Test 3 has been added to the Experiment. Unfortunately, another failure when booting from PCIe NVMe. Booting from USB, SATA, and Thunderbolt dock is okay.

Test 3 works for me with the same conditions in my other tests. I might try to compile OcQuirks down to as few options as needed on my machine. I didn't need very many on OpenCore, although no combination on OpenCore let me boot with iGPU unless I reset NVRAM, and then eventually I'd end up not being able to boot with iGPU anyway.

Are you able to install this EFI setup on a USB drive and then boot an NVME drive, or does NVME fail to boot no matter where Clover is booted from?
 
Back
Top