With the new AppleGB.kext reportedly working, I decided to try and update to Ventura from Big Sur but not before I do a clean install on a test drive. So I created a Ventura USB boot drive, however I can't even boot the installer. I get stuck seconds into the boot at this:
No, Ventura doesn't need any special kexts or boot args compared to Big Sur.
Saying that, you should be using the latest version of all the kexts in your /OC/Kexts folder, that is a given whenever you update a major release of macOS.
If I remember correctly there was an issue with the older versions of AMDRyzenCPUPowerManagement.kext, which was fixed in the most recent release 0.7.1.
You should also be using the latest version of OpenCore along with the newest AMD Kernel Patches.
Ventura gained support in OpenCore from release 0.8.4. So you need to be using OC 0.8.4 as a minimum for Ventura to boot.
Post a copy of your updated EFI, so we can see what you are using.
Have you changed/disabled the OC config.plist SetupVirtualMap quirk? Your board may require this quirk to be disabled, while other boards boot with it enabled.
Have you tried this quirk enabled and disabled, does it make any difference?
Did you use the ResetNvramEntry.efi from the OC Boot screen, to clear the old settings before booting with the new?
Tried Reset NVRAM, tried enabling SetupVirtualMap. Still the same hangup. I even tried installing Monterey to see maybe if I can simply update to Ventura from system prefs and it hangs here:
Installing Big Sur is not an issue. Most frustrating.
You are using an old version of the AMD Kernel Patches, which don't include the options for Ventura.
You have Kernel > Quirks > XhciPortLimit set as True, this stopped working with Big Sur 11.3 or newer.
You have Misc > Security > SecureBootModel set as Disabled, this should be set as Default when using iMacPro1,1 or MacPro7,1 SMBIOS.
You have NVRAM > Add > 7C436110-AB2A-4BBB-A880-FE41995C9F82 > csr-active-config set as <67000000>
This is an actually old entry from Clover, which was used to disable SIP. It is not going to work in any new version of macOS or with OpenCore. Is this why you have SecureBootModel set as Disabled?
You may want to have a read of this part of the OC Troubleshooting guide if your intention is to disable SIP.
csr-active-config has been set as < 00000000> Sip enabled.
A number of placeholder entries have been removed/deleted
You need to add your SMBIOS data to the revised config.plist before you use it. I would also recommend you use the ResetNvramEntry.efi tool from the OC boot screen, before you boot with this EFI.
You have NVRAM > Add > 7C436110-AB2A-4BBB-A880-FE41995C9F82 > csr-active-config set as <67000000>
This is an actually old entry from Clover, which was used to disable SIP. It is not going to work in any new version of macOS or with OpenCore. Is this why you have SecureBootModel set as Disabled?
You may want to have a read of this part of the OC Troubleshooting guide if your intention is to disable SIP.
As for the quote snippet, I was simply following a guide when I moved from Clover to OpenCore back in the day, hence why I had some outdated entries; I have no active reason to have SIP disabled. After adding my SMBIO info I transferred the new EFI to my test drive and it booted fine, so I copied it to my main boot and switched to AppleGB.kext which so far seems to be working A-OK!
Anyway, as for installing Ventura I have gotten much further in the boot but it still hangs (in the same spot as if I try Monterey). Tried reseting the NVRAM between boots and still the same. So close yet something is causing a snag.
@CaseySJ Thanks for your help, but still a no go. Same result, however, I was literally about to say f-it because if you and @Edhawk can't get things figured out I'm probably S.O.L. until I had a thought... what about AppleMCEReporterDisabler.kext? I don't know why that came to mind but the universe spoke to me. I added that to my EFI and BAM, success! I am typing this from Ventura with AppleGB.kext seemingly working flawlessly! The only issue (thus far) is that my CPU is now reported as Intel Xeon W in About This Mac/System Info.
@CaseySJ Thanks for your help, but still a no go. Same result, however, I was literally about to say f-it because if you and @Edhawk can't get things figured out I'm probably S.O.L. until I had a thought... what about AppleMCEReporterDisabler.kext? I don't know why that came to mind but the universe spoke to me. I added that to my EFI and BAM, success! I am typing this from Ventura with AppleGB.kext seemingly working flawlessly! The only issue (thus far) is that my CPU is now reported as Intel Xeon W in About This Mac/System Info.
.............. ok then! It seems some how I completely missed #8! Ok I know how, by hitting End and scrolling up to the top of post #9. Whoops! Wow, don't I feel the fool, it was right there.
No worries, happens to all of us. I saw post #8 before downloading and modifying the config.plist, but assumed the kext had been added. So I also did not check on it.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.
