Contribute
Register

pastrychef's Asus ROG Strix Z370-G Gaming (WI-FI AC) build w/ i9-9900K + AMD 6600 XT

Hi @pastrychef

don't get angry :think: ... in the last release of OpenCore 0.5.4 I think this string should be deleted because USBInjectAll.kext is not present in the Kext folder.

View attachment 446333

I'm trying to use VegaTab_56.kext with OpenCore, I tried this way, but I'm not sure if it works or not.
I deleted the ExecutablePath string because this Kext doesn't have an executable.

View attachment 446335

Ugh... I guess I forgot to add back USBInjectAll.kext when I was testing other USB fixes... I'll correct the OpenCore EFI a little later.

Yes. Delete the ExecutablePath if none exists. That's the correct way to do it.
 
Thanks for that. I had no luck with disabling IGPU. I did get the rash of purple lines from days gone by, followed by the same endless stream of AppleUSBHostPort enumeration failures... and it ended as it always has so far, unfortunately.

I did notice that your config has ten DSDT Patches in it. My config for Mojave does not have a Patches section. One of yours is "change GFX0 to IGPU". Could any of this have an effect?

-----edit
Well, shoot. I can no longer access my BIOS. The main boot screen never shows up. I've got to track this down, and will come back online when things are working again.

Remember to add back the USB 15 port limit KextsToPatch if you don't have one of the proper USB fixes applied.

 
Remember to add back the USB 15 port limit KextsToPatch if you don't have one of the proper USB fixes applied.

Yep. I did forget to add back the USBPorts.kext, which I created by going thru the SSDT process and saved as a kext. Does that need to be replaced or recreated?
---
Been snooping around the Font of All Wisdom (aka internet) and found one place saying that FWRuntimeServices.efi was only for OpenCore, not Clover (https://www.insanelymac.com/forum/topic/339807-aptiomemoryfixefi-name-changed/).
Correct? (I use OsxAptioFix2Drv-64.efi under Mojave.)

Notice you have both OcQuirks-4.efi and FWRuntimeServices.efi in your drivers folder. Are these both replacements for aptiomemoryfix.efi (and/or OsxAptioFix2Drv-64.efi)?

Hurt anything to remove them and insert the older efi's?
-----
Also noticed that VoodooPS2Controller.kext is for Microsoft products. Is this something unique to your build?

Still hanging in there! :)
 
Yep. I did forget to add back the USBPorts.kext, which I created by going thru the SSDT process and saved as a kext. Does that need to be replaced or recreated?
---
Been snooping around the Font of All Wisdom (aka internet) and found one place saying that FWRuntimeServices.efi was only for OpenCore, not Clover (https://www.insanelymac.com/forum/topic/339807-aptiomemoryfixefi-name-changed/).
Correct? (I use OsxAptioFix2Drv-64.efi under Mojave.)

Notice you have both OcQuirks-4.efi and FWRuntimeServices.efi in your drivers folder. Are these both replacements for aptiomemoryfix.efi (and/or OsxAptioFix2Drv-64.efi)?

Hurt anything to remove them and insert the older efi's?
-----
Also noticed that VoodooPS2Controller.kext is for Microsoft products. Is this something unique to your build?

Still hanging in there! :)

If you have USBPorts.kext, just put it in /EFI/CLOVER/kexts/Other/. No need to redo it.

FWRuntimeServices.efi works in conjunction with OcQuirks as an Aptio fix. Yes, these can be replacements for other Aptio fixes.

I don't know how well the NVRAM fix will work with other Aptio fixes. I only tested with this combination.

VoodooPS2Controller.kext enables your PS/2 port. I have it in there because I use an old school PS/2 mechanical keyboard.
 
OMG... I'm sending this from Catalina! :)
I pulled and swapped a bunch of things, which I'll report by showing the current contents of Drivers and Kexts:

Drivers:

ApfsDriverLoader.efi
AppleGenericInput.efi
AppleUiSupport.efi
EmuVariableUefi.efi
HFSPlus.efi
OsxAptioFix2Drv-64.efi
VirtualSmc.efi

Kexts:

AppleALC.kext
IntelMausiEthernet.kext
Lilu.kext
USBInjectAll.kext
VirtualSMC.kext
WhateverGreen.kext

You'll notice that along with all the other changes, I replaced my USBPorts.kext with USBInjectAll.kext. (I added the patches in config.plist of course.)

So, while I'm excited about this, of course, and delighted by pastrychef's unflagging and courteous help, I still have some basic issues...

First, I need to test with my "normal" boot BIOS, to make sure it's not getting trapped on Nvme issue as it did initially.

Next: a question - if you were in my shoes at exactly this point, what sanity checks would you perform? I have verified the PHotoshop and FCPX are both working.

That is: before I take the BIG step of cloning all this over to my Mojave Nvme, and hopefully making Catalina my new boot, and besides making a gazillion backups of everything (already underway), what suggestions have you got for me?

Once everything works, I'll be happy to contribute my EFI folder, if anyone wants it.

Thanks again, PC.
 
OMG... I'm sending this from Catalina! :)
I pulled and swapped a bunch of things, which I'll report by showing the current contents of Drivers and Kexts:

Drivers:

ApfsDriverLoader.efi
AppleGenericInput.efi
AppleUiSupport.efi
EmuVariableUefi.efi
HFSPlus.efi
OsxAptioFix2Drv-64.efi
VirtualSmc.efi

Kexts:

AppleALC.kext
IntelMausiEthernet.kext
Lilu.kext
USBInjectAll.kext
VirtualSMC.kext
WhateverGreen.kext

You'll notice that along with all the other changes, I replaced my USBPorts.kext with USBInjectAll.kext. (I added the patches in config.plist of course.)

So, while I'm excited about this, of course, and delighted by pastrychef's unflagging and courteous help, I still have some basic issues...

First, I need to test with my "normal" boot BIOS, to make sure it's not getting trapped on Nvme issue as it did initially.

Next: a question - if you were in my shoes at exactly this point, what sanity checks would you perform? I have verified the PHotoshop and FCPX are both working.

That is: before I take the BIG step of cloning all this over to my Mojave Nvme, and hopefully making Catalina my new boot, and besides making a gazillion backups of everything (already underway), what suggestions have you got for me?

Once everything works, I'll be happy to contribute my EFI folder, if anyone wants it.

Thanks again, PC.

So was FWRuntimeServices and OcQuirks the problem? Were those the drivers that prevented you from booting?

Have you tried AptioMemoryFix in place of OsxAptioFix2Drv + EmuVariablUefi?

With OsxAptioFix2Drv, NVRAM won't be working...

It's unlikely that USBPorts.kext prevented booting.
 
Not sure about FWRuntimeServices and OcQuirks...
Have not tried AptioMemoryFix, since back when I got this machine and installed Mojave, AptioMemoryFix was problematic on this hardware. When I installed Clover 5102+Emu, it installed the configuration you see now, although in the package (as I recall) it also had AptioMemoryFix, so apparently chose my combination.

NVRAM is working. I just did the helloworld test.

Unless you can think of some reason not to do this, I'll move the EFI to the Nvme, and use CCC to clone this test drive back over to it as well. See if I can get a real, working Catalina again.
 
Not sure about FWRuntimeServices and OcQuirks...
Have not tried AptioMemoryFix, since back when I got this machine and installed Mojave, AptioMemoryFix was problematic on this hardware. When I installed Clover 5102+Emu, it installed the configuration you see now, although in the package (as I recall) it also had AptioMemoryFix, so apparently chose my combination.

NVRAM is working. I just did the helloworld test.

Unless you can think of some reason not to do this, I'll move the EFI to the Nvme, and use CCC to clone this test drive back over to it as well. See if I can get a real, working Catalina again.

Your NVRAM is emulated because you have EmuVariableUefi installed. Also, as far as I know, OsxAptioFix2Drv never had support for native NVRAM.

If you still have /EFI/CLOVER/ACPI/patched/SSDT-PMC.aml, you can try FwRuntimeServices + OcQuirks or AptioMemoryFix in place of OsxAptioFix2Drv + EmuVariableUefi. Either of these should give you native NVRAM support.
 
I'll be happy to give that a try. However, I just noticed that the 5102 - EMU clover package does NOT include AptioMemoryFix at all. It only offers OsxAptioFix3Drv + EmuVariableUefi. (I see they offer v3 not v2, so I'll try that however. I'll have to hunt around to find AptioMemoryFix, although I'll admit that if the Clover folks don't use it in their latest install, I'm reluctant to consider it...

Back soon!
 
Back
Top