Thank you very much for that information. Worked like a charm. Just had to add that to my config and everything was working again without the VMM flag. Just for clarification. I am using the package from Martin Lo - maybe the VMM flag is specific to that package.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
A question regarding a NVRAM Reset. Currently I have Opencore on a USB drive. If anything goes wrong I can just unplug it. But, if I do a NVRAM reset macOS does not know anymore where to look e. g. will not boot anymore if I do a NVRAM reset. What if I had only one drive installed and Opencore would be on that drive. Would a NVRAM reset still make my Mac unusable? Most likely a very basic question but I am just not that familiar to that stuff. Thank you all in advance and have a nice day.
Did you read the announcement of OCLP 0.4.3 yesterday? OCLP development is suspended from now on, main developer is from Ukraine.
Release 0.4.3 · dortania/OpenCore-Legacy-Patcher
With today's macOS 12.3 release, I decided it would be best to release this build of OpenCore Legacy Patcher to ensure some important issues are resolved with today's release (namely Open/Save dial...github.com
OCLP is already a release below OC/this thread, OpenCorePkg still on 0.7.8.
I read in discord that he is not the only developer. Things would come out slower but project is not dead.
Don't know if it was posted here but Martin should be coming out with a new beta for his OC package soon that fixes this update so stand by!
So it seems that this is indeed the right fix. Many thanks to @khronokernel* for the kext. I've added the information to the guide (see Complete your setup).
*Mykola, thoughts and prayers your way in these difficult times.
The CMP will tend to boot from the same drive whenever NVRAM is reset. In my case, that's SATA bay 1. So if you have a drive in that bay with OC on it, the Mac will boot up fine after an NVRAM reset. You can set OC such that it will automatically 'bless' the drive it's on the first time it starts up following the reset.
Unfortunately it is not working for me. I downloaded the kext from github (version 1.0.1) and made the changes to my config.plist.
As suggested by @hwojtek I changed my AppleBootPolicy to TRUE (I had been booting with FALSE). I didn't change RequestBootVarRouting to TRUE as I'm booting from a rescueCD.
The other item that someone earlier mentioned was that if you had an "Update" Volume that needed to be deleted. My Monterey disk does have a 1.3 GB "Update" Volume.
I have attached my config.plist and would appreciate if someone could see if they can spot any mistakes/omissions that I might have made. It is fairly vanilla (based on the post #1 config.plist) - lilu, whatevergreen, and featureunlock (plus ASPP-Override) and hybridization.
My rescueCD boots Catalina fine and was booting Monterey before the 12.3 upgrade.
Thanks,
sfalatko
As suggested by @hwojtek I changed my AppleBootPolicy to TRUE (I had been booting with FALSE). I didn't change RequestBootVarRouting to TRUE as I'm booting from a rescueCD.
The other item that someone earlier mentioned was that if you had an "Update" Volume that needed to be deleted. My Monterey disk does have a 1.3 GB "Update" Volume.
I have attached my config.plist and would appreciate if someone could see if they can spot any mistakes/omissions that I might have made. It is fairly vanilla (based on the post #1 config.plist) - lilu, whatevergreen, and featureunlock (plus ASPP-Override) and hybridization.
My rescueCD boots Catalina fine and was booting Monterey before the 12.3 upgrade.
Thanks,
sfalatko
Last edited:
Opening your config with TextEdit, I'm seeing something weird with the ASPP-Override BundlePath entry:
Code:
<string>ASPP-Override.kext
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Arch</key>
<string>x86_64</string>
<key>BundlePath</key>
<string>FeatureUnlock.kext</string>
<key>Comment</key>
<string>Lilu plugin for missing features</string>
<key>Enabled</key>
<true/>
<key>ExecutablePath</key>
<string>Contents/MacOS/FeatureUnlock</string>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string></string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>
</plist>
</string>
I can see your ”Cpuid1Mask” is set to ”on”, i.e.
Code:
AAAAAAAAAAAAAACAAAAAAAI managed to boot 12.3 now, but I have no video.
Can tell that it's booted because the computer wakes and sleeps fine and I can also eject the optical disk tray.
Edit:
Forget it – it works now!
”Cpuid1Mask” set to ”off” (no ”C”) so it's not needed.
Last edited:
Plistlib Generator 1.2.6 was released with support for macOS Monterey 12.3 (see notable changes).
You will need to add the following kext into your
setup.py:
Code:
build.kexts = [
{
'project': 'ASPP-Override',
'properties': {
'ExecutablePath': '',
'MinKernel': '21.4.0'
},
'repo': 'dortania',
'version': '1.0.1'
},For some reason, the original zip file present into Dortania repo would add an empty
__MACOSX directory inside OC/Kexts directory, so I re-zipped the .kext file with a standard command. See details into README.Another release will be posted soon to fix the Python version changes and allow future OC upgrades, as Python2 is not supported anymore in macOS 12.3+.
hmm, broke my Mac trying to go to 12.3
Anyone have any ideas: My config.plist is attached
- I first upgraded OC to latest version 0.7.9, including the ASPP-Override.kext addition. I booted with that into MacOS 12.2.1, seemed fine.
- I ran Apple update, which downloaded the update and rebooted.
- Using OC boot menu, selected MacOS installer
- I wasn't watching the screen, but it did whatever it does and rebooted itself, however after that point I was not able to boot back into Monterey 12.3. It would either freeze the progress bar, at different places, or sometimes gives me that "unable to boot" error black screen message, but not always
- I did also try to boot with VMM on, and that dies even more quickly, rebooting itself every time.
Anyone have any ideas: My config.plist is attached
Just to confirm for others, the only changes I made to @cdf's default config.plist was adding the new kext, I did not changed the VMM Flag or AppleBootPolicy. RequestBootVarRouting is set to True in @cdf's suggested settings.
I'm attaching my config.plist generated with Plistlib Generator, which emulates OP configuration.
It's there on purpose, but has no effect. Changing the Cpuid1Data value to match enables VMM in this configuration.
Essentially, VMM is off but it's easy for me to remember how to turn it back on again (ie. where does the C go).
My cMP(5.1)'s startup behavior has gone haywire. I need help. I'm still on macOS 12.2.1.
I replaced it with OCLP 0.4.3 and my Mac boot time is ridiculously long. No startup failures.
I changed my video card from RX580 to GTX680 (Mac ROM) and checked the boot status. Then the progress status had changed. Previously, the startup was initiated with a white apple symbol screen on a black background. It now displays the startup disk selection screen (second level) first. At the bottom are reboot and shutdown icons and a number beginning with REL. Even USB mouse and keyboards do not respond at this time. I wait here for 30 to 40 seconds and the Mac starts up.
I downgraded to OCLP 0.4.2 because I felt very uncomfortable. And I tried booting with bare OpenCore(0.7.7 or 0.7.9) and config.plist without OCLP. At this time I'm using the reset button on the logic board to clear the PRAM as the USB mouse and keyboard are unresponsive. I will not be able to boot normally once I do this clearing. I boot the Mac while holding down the option key to bring up the boot screen. Then I select EFI Boot, which changes the boot disk icon to the black background color as shown above. The mouse and keyboard are responsive the first time, but once I enter EFI Boot they become unresponsive. Then the Mac starts booting.
And here's the weird thing. I went back to an RX580 video card. Then it changed so that the "boot disk icon" always appears at startup (I can't control anything) and the Mac starts up. Of course, before, this startup disk icon was not displayed.
*I have found that hitting the enter key repeatedly right after pressing the power button speeds up the startup slightly.
How can I go back to the way things used to be?
I replaced it with OCLP 0.4.3 and my Mac boot time is ridiculously long. No startup failures.
I changed my video card from RX580 to GTX680 (Mac ROM) and checked the boot status. Then the progress status had changed. Previously, the startup was initiated with a white apple symbol screen on a black background. It now displays the startup disk selection screen (second level) first. At the bottom are reboot and shutdown icons and a number beginning with REL. Even USB mouse and keyboards do not respond at this time. I wait here for 30 to 40 seconds and the Mac starts up.
I downgraded to OCLP 0.4.2 because I felt very uncomfortable. And I tried booting with bare OpenCore(0.7.7 or 0.7.9) and config.plist without OCLP. At this time I'm using the reset button on the logic board to clear the PRAM as the USB mouse and keyboard are unresponsive. I will not be able to boot normally once I do this clearing. I boot the Mac while holding down the option key to bring up the boot screen. Then I select EFI Boot, which changes the boot disk icon to the black background color as shown above. The mouse and keyboard are responsive the first time, but once I enter EFI Boot they become unresponsive. Then the Mac starts booting.
And here's the weird thing. I went back to an RX580 video card. Then it changed so that the "boot disk icon" always appears at startup (I can't control anything) and the Mac starts up. Of course, before, this startup disk icon was not displayed.
*I have found that hitting the enter key repeatedly right after pressing the power button speeds up the startup slightly.
How can I go back to the way things used to be?
Last edited:
No sleep issues here, my Mac goes always asleep after minutes of inactivity, as intended.
Can you follow the OP instructions step by step and post your zipped EFI? Is the only way we can see where is your issue. If you use OCLP, I suggest you reach at their support channels or Monterey for Unsupported Macs thread. Asking questions about OCLP in this thread will not get you any answers.
I'm not sure I understand what you are saying. I've noticed the GitHub repository now has an ASPP-Override-1.0.1-RELEASE.zip that, in turn, contains the relevant kext. This "1.0.1" kext is smaller than the one I originally installed (presumably version 9.9.9, a.k.a. 1.0?). Should we be using the smaller, 1.0.1, version or retain version 1.0 or whatever we call it?
Yes, there were some extraneous values in 1.0.0 which have been removed in 1.0.1 from what I can see. Both work fine, but it's best to touch as little as is necessary to resolve a problem.