Contribute
Register

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

@CaseySJ
thank you for answering so quickly
I did what you asked me and it does not go.I place IOregistryExplorer as a result.
I just checked all sections of Clover configurator and everything is empty (ACPI, Boot, Boot Graphics, Devices etc etc until SMBIOS):eek::eek:
 

Attachments

  • Mac’s iMac.ioreg
    23 MB · Views: 90
@CaseySJ
thank you for answering so quickly
I did what you asked me and it does not go.I place IOregistryExplorer as a result.
I just checked all sections of Clover configurator and everything is empty (ACPI, Boot, Boot Graphics, Devices etc etc until SMBIOS):eek::eek:
Did you mount the EFI partition of your macOS SSD and then open your config.plist file in Clover Configurator? In any case, IOReg shows that your USB ports are configured correctly. EC device is present.

Please connect the Apple SuperDrive into a blue USB 3 port and then:
  • Open System Information --> USB
  • Select the SuperDrive from the list under USB Device Tree
  • Then grab screenshot of the window (CMD-Shift-5).
 
Last edited:
@CaseySJ
Thanks for the instructions. Yes, it's OK for Clover Configurator, I got it wrong.
See a screenshot you asked me.
Super drive.png
 
@CaseySJ FINALLY the solution to get rid of the "evil" OsxAptioFix2Drv-free2000.efi is here! :) EDIT: Please test if it works reliably. It works great on my system and on some others’ who have tried it, too.
You can try using the combination of "FwRuntimeServices.efi" and "OcQuirks.efi" instead of "OsxAptioFix2Drv-free2000.efi". It’s important to build OcQuirks.efi with the option "DevirtualiseMmio" set to "True" or it won’t work. But never mind, I have attached the already correctly built file here. The "slide=0" boot argument is still needed.
So: Just delete "OsxAptioFix2Drv-free2000.efi" from EFI/CLOVER/drivers/UEFI and place the two attached files there instead.
EmuVariableUefi.efi is required for it to work.
I hope this works for your system as well. Mine is a Vanilla build, but I don’t think this will make a difference here.
Thanks so much to user "karacho" from the German Hackintosh forum for telling me about OcQuirks! We were talking about OpenCore and then I thought I’ll give this a try with Clover.
 

Attachments

  • FwRuntimeServices.efi
    5.1 KB · Views: 100
  • OcQuirks.efi
    25.6 KB · Views: 95
Last edited:
@CaseySJ FINALLY the solution to get rid of the "evil" OsxAptioFix2Drv-free2000.efi is here! :)
Instead you can use the combination of "FwRuntimeServices.efi" and "OcQuirks.efi". It’s important to build OcQuirks.efi with the option "DevirtualiseMmio" set to "True" or it won’t work. But never mind, I have attached the already correctly built file here. The "slide=0" boot argument is still needed.
So: Just delete "OsxAptioFix2Drv-free2000.efi" from EFI/CLOVER/drivers/UEFI and place the two attached files there instead.
I hope this works for your system as well. Mine is a Vanilla build, but I don’t think this will make a difference here.
Thanks so much to user "karacho" from the German Hackintosh forum for telling me about OcQuirks! We were talking about OpenCore and then I thought I’ll give this a try with Clover.


Cant boot with it, seems to behave like AptioMemoryFix.efi
 
Oh, that’s a pity. It works great here. Did you do a NVRAM reset in the Clover boot menu (by pressing F11) after replacing the files?
 
Hey,

Thanks for this awesome guide. I have completed it successfully and have my hackintosh running.

Just wondering how you can boot the hackintosh without the USB drive?

Thank you.
 
Oh, that’s a pity. It works great here. Did you do a NVRAM reset in the Clover boot menu (by pressing F11) after replacing the files?

Will test with NVRAM reset, thanks for the tip!

just did the NVRAM reset, no change, same behavior as AptioMemoryFix.efi
 
Last edited:
Hi @CaseySJ so as promised, an update about the dropping Bluetooth connection. Unfortunately, it's still recurring. And I'm not sure if I'm being paranoid but I think it's gotten more frequently. Anyway, I'm thinking that maybe it's just a hardware problem (maybe I got a lemon Fenvi card or something). And I'm willing to just buy another one if it's really the case. The only thing stopping me is what if it's not the card and something else? So I would just like to ask if you encountered a similar problem from any of your fellows here? It's becoming really frustrating and affecting work more and more. Please help. Anyone? :crazy:
 
Will test with NVRAM reset, thanks for the tip!

just did the NVRAM reset, no change, same behavior as AptioMemoryFix.efi
OK, but thank you very much for testing! I have edited my post.
 
Back
Top