Contribute
Register

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

mm2margaret said:
So, almost everything working now, mostly thanks to you (!!)

So now I have been booting regularly, except when I enable Thunderbolt, and then I get a OCB Image failure. That's okay, as I just don't use TB on this machine much (actually almost never).

At one point, ALL of my USB drives would not work (with the exception of the ASMedia ones). I recreated a new USB Map from Hackintool, which was just a guess, because none of my builtin USB drives would respond at one point, so I couldn't do the "insert a USB 2 drive into each port...." because they were all just dead.

On the Insanely site, I am seeing a lot of folks having trouble with USB ports which they claim are being fixed by upgrading to new releases of OC 074....Hmm....

So, here's my current EFI, which is working and pretty close to final, which might be of use to someone......thanks again!
Click to expand...

Cool!

Yes, as I mentioned earlier, another user was having issues with USBInjectAll causing kernel panics during boot. I don't know why, but it's one of the first things I look for if someone is having issues. Using Hackintool to create USBPorts.kext works.
 
pastrychef said:
You have USBMap.kext and USBPower.kext. They are both trying to do the same thing. Just use one of them, whichever one was made for your motherboard.
Click to expand...
Ok, so I followed your suggestion and Monterey PB6 seems to work well and ports are recognized BUT........

if I try with the same EFI folder to start from a USB drive it crashes.

If I try to upgrade to Public beta 7 it will restart from the "Macintosh HD" to install but then it crashes here.
It seems to me that there isa problem with USB ports but I cannot figure out how to fix it.
I tried disconnecting all USB except keyboard auto no avail.

Is there a way to use USBInjectAll.kext to start from scratch? Should that help?

IMG_0215.jpg
 

Attachments

  • EFI.zip
    19.2 MB · Views: 35
bruttonero said:
Ok, so I followed your suggestion and Monterey PB6 seems to work well and ports are recognized BUT........

if I try with the same EFI folder to start from a USB drive it crashes.

If I try to upgrade to Public beta 7 it will restart from the "Macintosh HD" to install but then it crashes here.
It seems to me that there isa problem with USB ports but I cannot figure out how to fix it.
I tried disconnecting all USB except keyboard auto no avail.

Is there a way to use USBInjectAll.kext to start from scratch? Should that help?

View attachment 529679
Click to expand...

Yeah, your USB ports kext still doesn't look right. You might be able to boot if you connect your USB flash drive to one of the ASMedia USB 3.1 gen 2 ports...

To re-do the USB ports kext, you should boot with USBInjectAll and config.plist > Kernel > XhciPortLimit Enabled. However, at least one person was having Kernel Panics when trying to boot with USBInjectAll. You may need to try using OpenCore 0.7.4 beta.
 
Clover EFI updated to r5140.1.

This will likely be the minimum version of Clover we will need if we want to update to Monterey.

All kexts updated to latest release versions.

Remember to test with USB flash drive before deleing your existing/working EFI.
 
OpenCore EFI updated to version 0.7.4.

All kexts updated to latest release versions.
Made appropriate additions to enable AppleVTD. (make sure VT-d is enabled in BIOS)

This will likely be the minimum version of OpenCore we will need if we want to update to Monterey.

Remember to test the new EFI on a USB flash drive before deleing your existing/working EFI.
 
So, hey, just one more question: On my Z370 I have two boot drives. One is Monterey, but the other is an old production drive that runs Mojave (which still looks great and works great).

It was running OC 069 and it was booting fine. I tried the "new" EFI on the Mojave drive, and it wouldn't boot. It stopped at "end setconsolemode". I then changed the SecureBoot parameter from default to disabled, and it booted. I don't think that's a problem, but I thought I would at least ask...any reason why running the separate Mojave install with this parameter set this way would create a problem?

Note that I boot manually, meaning I boot from the Bios menu each time I boot. I don't use one unified OC boot menu the way most folks attempt to use it.
 
Last edited:
mm2margaret said:
So, hey, just one more question: On my Z370 I have two boot drives. One is Monterey, but the other is an old production drive that runs Mojave (which still looks great and works great).

It was running OC 069 and it was booting fine. I tried the "new" EFI on the Mojave drive, and it wouldn't boot. It stopped at "end setconsolemode". I then changed the SecureBoot parameter from default to disabled, and it booted. I don't think that's a problem, but I thought I would at least ask...any reason why running the separate Mojave install with this parameter set this way would create a problem?
Click to expand...

My understanding is that there were changes with the macOS secure boot with Big Sur (and newer). This required that SecureBootModel in OpenCore to be set to depending on the system definition used because of how newer Mac models have the T2 chip. The setting can have consequences when trying to boot from certain disk images.

It is explained far better in the link below:

Apple Secure Boot | OpenCore Post-Install

dortania.github.io
 
So, on this machine, I boot from the Bios, so as long as I do that (and I've been doing that for a long long time), it sounds like it should be fine.

I boot Windows 11 from the Bios, Monterey from the Bios and Mojave from the Bios, and so far they all work fine. Sounds like this is going to work.

Thanks for the URL reference on Apple Secure Boot in OpenCore.
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top