Success, after a working Bootloader OC 0.7.4 the installation worked out!
Three reboots and now Monterey is running :D
Thanks Feartech, had a backup of Big Sur on a second drive.
Ok i tried it one more time.
I used this Tool:
https://github.com/ic005k/QtOpenCoreConfig/releases/tag/20211013
And it worked so far im now running on OC 0.7.4 :lol:
What do i have to be aware off with such an old board for Monterey?
Hello everybody, i tried to update OC from 0.6.6 to 0.7.4. But i've got no success to update my config.plist to the current version.
I tried to merge them with meld.app adding in line by line from my old config.plist to Sample.plist and then saved it to a new one.
I attached the OC files and...
So, I took the abbreviation. I Installed Big Sur on my mac Book Air on an external drive and copied the OC on the EFI Volume of that drive. And surprise it worked. I could also Update the latest Version of Big Sur to 11.2.3.
iMessage works, Continuity and Hand off is working. Sleep i didn't...
Hello so right now, no news so far. I can't install Big Sur or Catalina right now. I have a cmos checksum error but after the backup kicks in the machine boots fine. This behaviour is since i put the rx580 in the machine. I tried nearly everything to resolve this but no luck. (battery, power...
Now I can reach the installation GUI. I can start the installation and it gets until the point of 12 minutes. Then there’s a quick shell popping up and the screen went black. No reboot, it simply stalls there. It seems that the installation copied ca. 12 GB of the installation to the drive and...
Ok back in. i checked against the sample.plist and now no more error reports.
Neither Sanity Check or ocvalidate.
Next up:
troubleshooting section in the guide...
Hello Pilgrim,
thank you for your quick response.
I have now a clean config.plist.
Sanity Checker says everything is green.
ocvalidate is missing 'DisableSecurityPolicy' (i ignore because you said to delete that entry)
My problem is unfortunately persistent. The system is freezing after 15...
So far so good, i fixed a lot of errors.
But this one is present:
"No schema for DisableSecurityPolicy at 0 index, context <Quirks>!"
and i didn't get the point to fix it.
I have the entry in my config.plist but the error is still present.
Btw. the boot ist freezing after 15 seconds when...
That did the trick! The installer boots now. I can choose where to install Big Sur. But unfortunately the Installer stops and it freezes at the progress bar. I tried several times. Then I recreated the installer on an internal data harddrive (optical) but it’s the same. I tried it with the...
Ok i passed the OC drives entry section and the System goes on to boot. Now i get this kernel panic shown in the pictures below.
If i interpret them correctly it has something to do with com.driver.AppleCPUPowerManagement.
How can i get around this?
Ok, i found this thread:
https://www.tonymacx86.com/threads/bug-sur-11-0-1-11-1-ich10-sata-hotplug-path.306069/post-2210966
But it didn't worked for me. I added my edited config.plist for verifying purposes:
You mean this fix you can see in the screenshot right? I don't know how to properly get it into the patches section in OC. The entries in Clover has less Key/value pairs. so i don't know how to transfer them properly... BTW. im just using ProperTree.app.
Ok good so far! I double checked your config.plist and realised that your "Drivers" structure has different "###.efi" inside. I took the five you are using. Now when it boots the OC get around that error message. But sadly when the promt shows up where i can select the drives to boot from i get...
Ok, that's a good point! I used yours as a way to go with ;) I filled the parts "replace" in your "config_sandy_bridge_Z68.plist"with my own serial etc, but its hanging before i can select the device entries in OC. Maybe you can give me a hint were i can get a good start from...
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.