Well some good news Tedyun. I retried your EFI you made based on pastrychef's EFI.
I reset the CMOS this time by shorting the jumper - and reset the NVRAM after and it did work! Maybe I wasn't resetting the CMOS correctly?
I ran VDADecoderChecker and it came back showing Hardware Acceleration was enabled. I then rebooted and restarted the computer 7-10 times and no prohibition sign! Only issue was the longer boot times, but that might be down to the EFI folder being a bit bloated.
Anyway I had a look through the config.plist and compared to mine there are lots of additional drivers, kexts etc. My EFI folder is very vanilla - literally the latest required drivers and kexts and SSDT's straight from the official source.
So I cleaned up both the folder and the config.plist, popped in my SSDT's which are just the standard vanilla ones from the official OpenCore guide, popped in my USBPorts.kext as well as my kexts and drivers.
Restarted the computer - sadly prohibition sign!
Cleared the CMOS and NVRAM again - but no luck this time - prohibition sign again.
I have ensured the Framebuffer patch remained in DeviceProperties exactly as you had put it in. All I removed was the additional devices listed as I have never added them before. Maybe this is causing the issue?
Or perhaps its the boot-args? I did replace the boot-args with mine. Did go back and re add igfxonln=1 but still no luck.
I wonder what it is?
Well some good news Tedyun. I retried your EFI you made based on pastrychef's EFI.
I reset the CMOS this time by shorting the jumper - and reset the NVRAM after and it did work! Maybe I wasn't resetting the CMOS correctly?
I ran VDADecoderChecker and it came back showing Hardware Acceleration was enabled. I then rebooted and restarted the computer 7-10 times and no prohibition sign! Only issue was the longer boot times, but that might be down to the EFI folder being a bit bloated.
Anyway I had a look through the config.plist and compared to mine there are lots of additional drivers, kexts etc. My EFI folder is very vanilla - literally the latest required drivers and kexts and SSDT's straight from the official source.
So I cleaned up both the folder and the config.plist, popped in my SSDT's which are just the standard vanilla ones from the official OpenCore guide, popped in my USBPorts.kext as well as my kexts and drivers.
Restarted the computer - sadly prohibition sign!
Cleared the CMOS and NVRAM again - but no luck this time - prohibition sign again.
I have ensured the Framebuffer patch remained in DeviceProperties exactly as you had put it in. All I removed was the additional devices listed as I have never added them before. Maybe this is causing the issue?
Or perhaps its the boot-args? I did replace the boot-args with mine. Did go back and re add igfxonln=1 but still no luck.
I wonder what it is?
Hello @tedyun,@BillyBoy7 : Well, I went through pastrychef's most recent OC 0.6.0 EFI and I deleted, one by one, each of the Device Properties and.....nothing happened! It booted fine! I'm really perplexed. Anyway, I went ahead and made a minimal version here for you. I just deleted:
Root > PlatformInfo > DataHub
Root > PlatformInfo > PlatformNVRAM
Root > PlatformInfo > SMBIOS
So add these values back from your rig.
I also changed the Sysdef to iMac19,1, added the USBPorts.kext (you should substitute for your own map) and added the framebuffer patch into the DeviceProperties.
You can play around with this to see if you can strip out anything else and see what breaks it. I'd be interested to find out!
Hi @thepawnHello @tedyun,
I'm really learning a lot from you, but I'm still quite new to the hackintosh world.
I own a system with the Gigabyte Z390 Gaming X, 9700K processor, RX 570 graphic card.
I went through the original guide "UniBeast: Install macOS Catalina on Any Supported Intel-based PC" and many other guides, and I managed to get a running Catalina.
Problem is, I get the "stop" sign every now, and then, with the red error "Already started returned from AptioMemoryFix.efi".
I was wondering if you can help:
- did you find out what is causing that error?
- which BIOS version are you running ATM?
- in MultiBeast, on a fresh install, would you go for the emulated VRAM or not?
- do you prefer Clover or OC?
- which EFI folder that you posted would you use with my configuration?
- can you maybe share a recent EFI? Maybe during last year you reached perfection.
Thank you so much for your help.
Hi tedyun
For more than a week I have encountered a serious problem on my hackintosh which happens to be almost identical to your build 3
z390 gaming x - i9 9900k - RX580 - 16GB (2x8GB) 3600MHz.
Liquid Cooling System AORUS 360
So, my hack started to restart for no reason without any action on my part not having created a backup I decided to do a clean installation
the installation goes well until 12 minutes before the end the hack restarts
Then after restarting it tells me 29min remaining, 23min from the end the hack restarts again so impossible to install any macOS system
can you take a look at my EFI file and tell me what you think about it and possibly a solution to a problem
(for info I tried with your EFI file I had the same problem)
thanks for your help
@rudayeHi tedyun
For more than a week I have encountered a serious problem on my hackintosh which happens to be almost identical to your build 3
z390 gaming x - i9 9900k - RX580 - 16GB (2x8GB) 3600MHz.
Liquid Cooling System AORUS 360
So, my hack started to restart for no reason without any action on my part not having created a backup I decided to do a clean installation
the installation goes well until 12 minutes before the end the hack restarts
Then after restarting it tells me 29min remaining, 23min from the end the hack restarts again so impossible to install any macOS system
can you take a look at my EFI file and tell me what you think about it and possibly a solution to a problem
(for info I tried with your EFI file I had the same problem)
thanks for your help
There are two ways you can unlock the MSR. The first is to use the beta F10g BIOS for the Z390 Gaming X.
@tedyun
Where can may download F10g beta?
and is F10i have ability for unlock MSR? or if check it with upgrade to F10i, is there to downgrade to default firmware in case of it didnt exist?