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

[Ploddles]

Hello Ploddles,

Thank you for responding, see attachment with the content of the patched folder, yes I do have SSD-NVRAM.aml in it.

So you have VirtualSMC.kext + the two other files both in Kexts/Other and /L/E and VirtualSMC.efi in the UEFI folder and that is working for you? Do you mind posting a screenshot of the contents of your /L/E?

The boot stops with the message HID: Legacy shim 2. CSM support in BIOS is disabled, I enabled that for testing but at the time that didn't make a difference. Do you have CSM support enabled?

I don't know tinker, I just googled it and downloaded it. Where can I find more info on how to use it in the way you just wrote to me? So after I created a bootable usb drive I copy the EFI contents of my Mojave disc to the EFI of this bootable usb drive and then...copy the files of a previously working EFI content? Sorry, newbie in this area.

Best regards

As promised, attached is my original EFI, named EFI-OldQuirks.zip

As CaseySJ has released a new version of OcQuirks.efi, OcQuirks.plist and FwRuntimeServices.efi, I did a test update with these and can confirm that all is well on my system.

As such, also attached is my new EFI, named EFI-NewQuircks.zip

 

[CaseySJ]

Hi
First of all I want to thank you a 1000 times for this impressive and awesome guide.
I have basically built the exact same system from the guide (except with i9-9900k) and it has been working flawlessly in every aspect for 2 months on Mojave 10.14.6.

However, I have now stumbled upon the very worrying statement from the maker of OsxAptioFix2Drv-free2000.efi.
It states that eventually this WILL damage your hardware.

I'm mixing a film right now so I am stressing the system pretty good. I can not afford to have it break on me right now, and I want to fix this free2000 thing right away. I'm on clover r5104.

From what I have found, I should need to simply copy the 3 files from OcQuirks Rev 15 (FwRuntimeServices.efi, OcQuirks.efi and OcQuirks.plist) from the catalina mini-guide to the drivers/UEFI folder, replacing the free2000 driver.

Is this correct?
I wanted to double check this because I really can't afford a screw-up right now. I see another user has just posted a question, my question is essentially the same because I'm also on Mojave.

Also, is there any chance that this may interfere with other stuff like shutdown, sleep, nvram... or is this pretty much done and tested safe?

Thank you very much!

Hello @habibelhabab1,

Good questions:

• OsxAptioFix2Drv-free2000 is not recommended, but it will not damage your system. The "very worrying statement from the maker" is exaggerated.
• If you're in the middle of a project, it is okay to continue using OsxAptioFix2Drv-free2000. I used it for nearly a year without any issue of any kind.
• To switch to the new recommended drivers, however, we strongly recommend making a full bootable backup of your system ahead of time.
• If you have already switched to Clover 5104 and have deleted the old drivers64UEFIfolder, then you're in good shape to switch.
  • Simply delete OsxAptioFix2Drv-free2000 and replace it with the three files in the Catalina Mini Guide.
  • Sometimes it's a good idea to perform a CMOS Reset as well to clear the memory map. This should be done in accordance with instruction in the Designare User's Manual. All BIOS parameters must then be re-configured starting with Load Optimized Defaults.

 

[HH007]

As promised, attached is my original EFI, named EFI-OldQuirks.zip

As CaseySJ has released a new version of OcQuirks.efi, OcQuirks.plist and FwRuntimeServices.efi, I did a test update with these and can confirm that all is well on my system.

As such, also attached is my new EFI, named EFI-NewQuircks.zip

View attachment 450790

Hello Ploddles,

Thank you for keeping your promise, I'll do some more testing with this info, I'm not sure when because I don't have much time at them moment but I will come back to you as soon as I have results.

Best regards

 

[Zip1]

I can not afford to have it break on me right now,

My hack system is used in a Production (editing) environment everyday.
I can not emphasize enough to NOT make ANY changes to your system in the middle of a critical project, EVER.

Its' generally accepted that the free 2000 developer's warning is more of a CYA statement and there have been no severe/verified failures with the use of OsxAptioFix2Drv-free2000.

Now, if you insist on updating your system, be sure to follow the 3 rules below -
1. Backup your system and confirm you can boot to the backup
2. Backup your system and confirm you can boot to the backup
3. Backup your system and confirm you can boot to the backup

 

[CaseySJ]

Casey, could you clarify if this update is safe for Mojave users as well?
Thank you!

I may need a volunteer to test it on Mojave! Hint, hint.

 

[habibelhabab1]

@CaseySJ, @Zip1, Thank you VERY much for your replies.

I have a full bootable backup on a 2nd NVME SSD of my pro tools system so I can pretty much swap and continue to work. However I am going to leave it for now and test this next week. Will report back.
I don't fully understand what this driver does, so what exactly would you like me to look out for while testing it on mojave?

 

[CaseySJ]

@CaseySJ, @Zip1, Thank you VERY much for your replies.

I have a full bootable backup on a 2nd NVME SSD of my pro tools system so I can pretty much swap and continue to work. However I am going to leave it for now and test this next week. Will report back.
I don't fully understand what this driver does, so what exactly would you like me to look out for while testing it on mojave?

Good decision. The test is very simple: If the system can boot into Mojave without displaying the dreaded “couldn’t allocate runtime area” then we declare success.

 

[zipb]

Hi
First of all I want to thank you a 1000 times for this impressive and awesome guide.
I have basically built the exact same system from the guide (except with i9-9900k) and it has been working flawlessly in every aspect for 2 months on Mojave 10.14.6.

However, I have now stumbled upon the very worrying statement from the maker of OsxAptioFix2Drv-free2000.efi.
It states that eventually this WILL damage your hardware.

I'm mixing a film right now so I am stressing the system pretty good. I can not afford to have it break on me right now, and I want to fix this free2000 thing right away. I'm on clover r5104.

From what I have found, I should need to simply copy the 3 files from OcQuirks Rev 15 (FwRuntimeServices.efi, OcQuirks.efi and OcQuirks.plist) from the catalina mini-guide to the drivers/UEFI folder, replacing the free2000 driver.

Is this correct?
I wanted to double check this because I really can't afford a screw-up right now. I see another user has just posted a question, my question is essentially the same because I'm also on Mojave.

Also, is there any chance that this may interfere with other stuff like shutdown, sleep, nvram... or is this pretty much done and tested safe?

Thank you very much!

I have been using oc-quirks-4 efi and FwRuntimeServices.efi from Nov, 11 with 0 problems for months with Clover 5k.

I just tried the FwRuntimeServices.efi, OcQuirks.efi and OcQuirks.plist rev 15 (from feb, 13) and I got the forbidden sign on boot. Twice. Also after a boot with a 30 sec interruption of power. I put oc-quirks-4 efi and FwRuntimeServices.efi from Nov, 11 back and I can boot again.

So, this doesn't work for everyone.

And yes, make sure you have a spare bootable OS, and backup your EFI before you try something new.

Also, never tinker with your computer in the middle of a project with a deadline.

Mojave 10.14.6, BTW.

 

[Zip1]

I don't fully understand what this driver does, so what exactly would you like me to look out for while testing it on mojave?

Casey's reply about testing on Mojave was in regards to using the 'optional' updated OcQuirks Rev 15 instead of the tested and verified version in the Catalina Mini-guide Install files.

I certainly would NOT recommend you perform any 'testing' on your critical system.

The purpose of these files (free-2000, OcQuirks, FwRunetimeServices, etc.) is to configure the memory so MacOS can boot. If you attempt any changes, and there is a problem you will get a "...Couldn't allocate runtime area Boot failed" error and your system will refuse to boot (sounds like fun eh?)

 

[habibelhabab1]

Ah!!
Thank you very much for clarifying this!! I hadn't read the mini-guide well.
Regarding the above post by zipb, are the versions in the 'Catalina Fresh Install.zip' safe to use? Or is it better to stick to the november version (oc-quirks-4 efi and FwRuntimeServices.efi)?
As I understand so far, the fresh Install.zip version is the correct one for clover r5104 right?

Anyway, thank you all very much for your help. It may not be a good idea to test stuff right now But you can simply copy the entire EFI partition from a bootable backup in case of failure right?