Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
If you can’t say it without emoji, don’t say it. — The argument about nightly builds is superfluous. It is up to the developers to publish or not publish the access to nightly builds. And honestly, it is no-one‘s business to patronise those seeking the chance to resolve issues on their machines by using the nightly builds. Their choice, their risk to brick their machines.

And again: emojis are for girls. Would James Bond use emojis? Right. At least, use these everybody will understand, e.g. 💸 or 🗿
emojis are for girls 😂 toxic masculinity shouldn't be welcome here
 
Maybe, one solution would be to add your custom variables to config.plist. This way, NVRAM will still keep them when you boot without OCLP.
My config.plist:
Code:
	<key>NVRAM</key>
	<dict>
		<key>Add</key>
		<dict>
			<key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
			<dict>
				<key>DefaultBackgroundColor</key>
				<data>
				/39/AA==
				</data>
			</dict>
			<key>4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102</key>
			<dict>
				<key>OCLP-Settings</key>
				<string> -allow_fv</string>
				<key>OCLP-Version</key>
				<string>0.4.2</string>
			</dict>
			<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
			<dict>
				<key>boot-args2</key>
				<string>keepsyms=1 debug=0x100 -v maxmem=63488 -disable_sidecar_mac -liludbgall liludump=90 -revasset</string>
				<key>boot-args</key>
				<string>keepsyms=1 debug=0x108 -v maxmem=63488 iogdebg=-1 serial=3 msgbuf=1048576 serialbaud=115200 -disable_sidecar_mac -liludbgall liludump=90 -revasset</string>
				<key>csr-active-config</key>
				<data>
				AwoAAA==
				</data>
				<key>run-efi-updater</key>
				<string>No</string>
			</dict>
			<key>FA4CE28D-B62F-4C99-9CC3-6815686E30F9</key>
			<dict/>
		</dict>
		<key>Delete</key>
		<dict>
			<key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
			<array>
				<string>DefaultBackgroundColor</string>
			</array>
			<key>4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102</key>
			<array>
				<string>OCLP-Version</string>
				<string>OCLP-Settings</string>
				<string>revcpu</string>
				<string>revcpuname</string>
			</array>
			<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
			<array>
				<string>boot-args</string>
				<string>csr-active-config</string>
			</array>
			<key>FA4CE28D-B62F-4C99-9CC3-6815686E30F9</key>
			<array/>
		</dict>
		<key>LegacyEnable</key>
		<false/>
		<key>LegacyOverwrite</key>
		<false/>
		<key>LegacySchema</key>
		<dict/>
		<key>WriteFlash</key>
		<false/>
	</dict>
OCLP makes changes to the NVRAM when booting, so it's probably working as intended.
But it doesn't need to. It's nvram runtime services override can just choose not to write to those variables.

I'm just allowing the standard release TUI app to auto-build my EFI and System folders for the EFI partition. As I don't have any Linux OS's installed and only a Windows 10 legacy NTFS on an MBR partition (on a sep. SSD), I'm not really sure why OCLP is adding the ExFat and OpenLinux drivers for me.

However, thanks for the direction to follow. I'll remove the Linux driver as suggested. [Note: I needed to remove the reference in the config.plist UEFI/Drivers section, otherwise the reboots seemed to hang]
I think you can just change the Enabled setting to <false/>.

There is an option under OCLP's Settings/Developer Settings. Though it seems to be made for a different situation, disabling it may be useful for you?
Is that the same as the WriteFlash setting which I have set to false?

Huh? Not sure what you mean?

NV-non volatile, ie. persists until set to another value.

Once you boot OCLP EFI, its setting will be in NVRAM until you reset it.

And if you don't bypass OCLP EFI at startup, it will keep bootstrapping into NVRAM every time.

Note the instructions for removing OCLP:
1. Remove OCLP EFI
2. Reset NVRAM
Why make it non-volatile if OpenCore is going to set it again anyway the next time it boots? It doesn't need to modify nvram to have the OS see the variable setting.
 
  • Like
Reactions: TimothyR734
Does anyone else running Big Sur keep getting prompted on an unsupported Mac (in my case MBP 15 Late 2013) to upgrade to Monterey? All the time? Then when you try and follow the Notification, it doesn't show up?

Am I missing something?
A similar machine, MBP11,1 13" late 2013 didn't get Monterey notifications when running 11.6.x.

Yesterday installed 12.2.1 on it from InstallAssistant.pkg with OCLP 0.4.2, very smooth. On an external SSD for now, which got a data clone of the internal SSD with CCC before installing.
Not my machine but I'm responsible for it. It is a model which would have been bricked by an early upgrade to Big Sur; maybe Apple introduced a special handling/cure for these.
 
Last edited:
  • Like
Reactions: TimothyR734
Noticing a few more graphical issues. Nothing major but slight annoyances.

Sliders are off in control center
Screen Shot 2022-02-18 at 5.10.00 AM.png

Right clicking anything in the dock leaves a box under the menu
Screen Shot 2022-02-18 at 5.10.23 AM.png

Icons missing in random settings areas like Accessibility
Screen Shot 2022-02-18 at 5.10.52 AM.png

Nothing major, but maybe somebody has had something similar and fixed somehow? Performance wise 100% flawless (knocks on wood) so far.
 
Hi All

Im new here so apologies for this if this isn't the correct place.
I have asked on a number of forums for an answer to this problem and followed advice but nothing has worked...

If this is the wrong place to ask please direct me to the appropriate one. Ive looked on the Discord Server for OCLP and asked there and Instagram.

I'm trying to install Monterey 12.2.1 onto a Macbook Pro 9,2 mid 2012 following the Mr Macintosh guide and OCPL 0.4.2 gui version. I have two new SSD drives one is running supported version of Catalina and the other is blank and ready for Monterey. I have used OCLP to create the installer. All goes well the system reboots a couple of times then gets to the point where I would expect the assistant to start the setup. Just as I'm expecting the installer assistant to take me to Language I get the following error message "BaseSystem.dmg" could not be copied to 5BBE4E6C-DADD-45E3-9A83-7997CCD48031.

searching on the web doesn't give me an answer.
I tried to do the update on this machine to Big Sur first got the same error message, the 12.2 and 12.2.1.

MBP 9,2 i5 13" 16Gb, 2 500GB SSD
 
  • Like
Reactions: TimothyR734
Just as I'm expecting the installer assistant to take me to Language I get the following error message "BaseSystem.dmg" could not be copied to 5BBE4E6C-DADD-45E3-9A83-7997CCD48031.

searching on the web doesn't give me an answer.
I tried to do the update on this machine to Big Sur first got the same error message, the 12.2 and 12.2.1.

MBP 9,2 i5 13" 16Gb, 2 500GB SSD

What is the container size for Monterey?
Can you give, from the terminal, the returns by copy/pasting text of the command:
Code:
diskutil list
 
  • Like
Reactions: TimothyR734
I installed 2 drives one in the HDD bay and one by replacing the superdrive.
One has a supported version of Catalina on it. I'm trying to install Monterey on the second one.
I've erased and formatted it from Catalina and from the recovery screen on Monterey install. Neither works...

What has happened since I posted is that another attempt got to the recovery install screen and suggested 28 minutes remaining. That took most of the 28 minutes before rebooting. If I remember correctly that has not been the case previously. That 28 minutes has quickly been reduced to 10!

I'm assuming some failure in the copying process?
 
  • Like
Reactions: TimothyR734
Have you use this SSD before?
Can you try clone your Catalina System on this drive and boot on to validate it?
 
First, thanks to @khronokernel and all the other developers for their work on this project.

Except for two things, I pretty much haven't had any problems with any of the macOS Monterey or Big Sur betas on my 10,1 MBPr.

I installed a BCM94360CSAX Airport card and I noticed that my Wi-Fi speeds are in the 2-4 Mbps range. I have a Windows partition on the same computer where I get 15-20 Mbps on Wi-Fi.

When I build OpenCore, I see:

Found Wireless Device 14E4:43A0

Adding AirportBrcmFixup.kext 2.1.3

When I tried building OpenCore for a MacBookPro11,2 I see the same kext.

Should I be using a different Wi-Fi kext or is there another issue?

The other issue is when I try to connect the mini DisplayPort to DisplayPort on my external display, I get a black screen. I didn't find much discussion except for post 2481.

Thanks for any help.
 
Last edited:
  • Like
Reactions: TimothyR734
First, thanks to @khronokernel and all the other developers for their work on this project.

Except for two things, I pretty much haven't had any problems with any of the macOS Monterey or Big Sur betas on my 10,1 MBPr.

I installed a BCM94360CSAX Airport card and I noticed that my Wi-Fi speeds are in the 2-4 Mbps range. I have a Windows partition on the same computer where I get 15-20 Mbps on Wi-Fi

When I build OpenCore, I see:

Found Wireless Device 14E4:43A0

Adding AirportBrcmFixup.kext 2.1.3

Should I be using a different Wi-Fi kext?
Download the latest OCLP version and rebuild/reinstall OC whenever you change the hardware.
The other issue is when I try to connect the mini DisplayPort to DisplayPort on my external display, I get a black screen. I didn't find much discussion except for post 2481.
Depending on the used spoofing level (minimal) you can try to add to the boot-args agdpmod=vit9696.
Thanks for any help.
You surely do not use OCLP 0.0.9 any longer?
 
  • Like
Reactions: TimothyR734
Macbook Pro 15 Retina Late-2012 model. Was running perfectly fine on 12.2 with OCLP installed. Upgraded to newest MacOS update 12.2.1, ran "Build and Install OpenCore" and then "Post Install Root Patch" and then restarted and now the display is something like this... any advice other than doing a fresh install? Thank you
 

Attachments

  • 273891164_1351135028669021_1628074757473228427_n.jpg
    273891164_1351135028669021_1628074757473228427_n.jpg
    120.4 KB · Views: 94
  • Like
Reactions: TimothyR734
Download the latest OCLP version and rebuild/reinstall OC whenever you change the hardware.

Depending on the used spoofing level (minimal) you can try to add to the boot-args agdpmod=vit9696.

You surely do not use OCLP 0.0.9 any longer?
Thanks @Ausdauersportler. I always check to see that I am using the latest version of OCLP when there is a new beta. I used OpenCore 0.4.2 when I did the latest update to 12.3 beta 3 (21E5212f).

I will try agdpmod=vit9696 in the boot-args.
 
  • Like
Reactions: TimothyR734
Noticing a few more graphical issues. Nothing major but slight annoyances.

Sliders are off in control center
View attachment 1960640

Right clicking anything in the dock leaves a box under the menu
View attachment 1960642

Icons missing in random settings areas like Accessibility
View attachment 1960641

Nothing major, but maybe somebody has had something similar and fixed somehow? Performance wise 100% flawless (knocks on wood) so far.
So after reading more of the ref doc to fix Broken Background Blurs, I was able to fix 2 of my graphic issues.
  • Mouse hover issue is no longer there, even after re-enabling transparency.
  • Right-click box is no longer present.
Accessibility icons flash but then hide, I dk why. CC Display bars are still offset.

I went with the recommended 30px, looks good so I'm not messing with it.
Screen Shot 2022-02-19 at 4.40.38 AM.png

New issue is, since applying this, My Clock has turned invert
Screen Shot 2022-02-19 at 4.49.58 AM.png
Update:
So I thought there was a bug. I replicated it by Option click the time. But this is a shortcut to enable and disable Focus. Focus is what's causing the time to Dim. Is that a feature? Regardless, I enabled to show the Focus icon in the menu bar. Now it doesn't matter if it's on or off. Color remains unchanged.
Screen Shot 2022-02-19 at 5.45.11 AM.png
 
Last edited:
  • Like
Reactions: hvds
Hi, I'd like to install Monterey on a late 2011 15-inch MBP (Macbook Pro 8,2) with the HD3000/Radeon 6750M GPU's.

2.2 Ghz i7, 16 GB RAM, both GPU's still working (I'd really like to restrict to the Intel iGPU though - is gfxcardstatus working on Monterey?) and I'd be getting a brand new SSD to set this up.

Does anybody have experience with this setup?
 
Noticing a few more graphical issues. Nothing major but slight annoyances.

Sliders are off in control center
View attachment 1960640

Right clicking anything in the dock leaves a box under the menu
View attachment 1960642

Icons missing in random settings areas like Accessibility
View attachment 1960641

Nothing major, but maybe somebody has had something similar and fixed somehow? Performance wise 100% flawless (knocks on wood) so far.
Apparently these will be fixed in the upcoming 0.4.3 release of OCLP :)
 
Macbook Pro 15 Retina Late-2012 model. Was running perfectly fine on 12.2 with OCLP installed. Upgraded to newest MacOS update 12.2.1, ran "Build and Install OpenCore" and then "Post Install Root Patch" and then restarted and now the display is something like this... any advice other than doing a fresh install? Thank you

[RESOLVED] So, this strange issues was resovled by creating a new administrator user. I have no idea why it happened. But now the macbook is running perfectly on 12.2.1. Thanks
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.