The artifacts thing has been around since forever, I don't think anyone has any clue how to fix it unfortunately (nor do I think anyone cares to try) I also have a late 2013 so I see it as well. Photoshop however works fine for me, have you tried reinstalling it? I'm surprised your eyes don't hurt while using Big Sur/Monterey on your late 2013 iMac, it gives me so much eye strain/discomfort and seeing as we have the same Mac I'm not sure why you're not experiencing it...
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.
macOS 12 Monterey on Unsupported Macs Thread
- Thread starter khronokernel
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Not yet as I’m still running off the flash drive for boot should that not work?
Someone can correct me if the OCLP guides work a different way from what I'm about to suggest, but if you want to upgrade the main and only OS on your machine to Monterey, rather than dual booting Monterey and Big Sur, then you could just get OC set up on your EFI system partition and booting Big Sur, even though Big Sur also runs fine natively (i.e. without OpenCore) as well on your hardware. Then, you should just be able to run the update to Monterey in place, as normal, forgetting about any USB complications. (You will, ofc, then have an OS on your machine that you can only start using OC. You can still use Internet Recovery to go back if you want to.)
Last edited:
It's sad to hear that there is no solution with the OpenCL framework. I think the interface artifacts are related to this. Photoshop works well, no problem with it. Thanks!
When the OCLP boot picker shows up, are there 2 disks having the same name? I had the same issue during last Big Sur update, because the system booted from the regular disk, not the one created by the system for the update. So I had to pick the other disk and finally the update executed regularly. I didn't encountered this problem updating from BS to Monterey, though.
If you need this level of handholding, maybe this stuff is not for you...just saying.
wow how condescending - as I have said I've used this for ages on other machines with other problems I have solved this is a new one I ask for help with and that your reaction... great community spirit
Cheers - exactly this - the first one booted about 30/% of the apple progress bar, then it rebooted and booted back in to Big Sur, are you saying you have to force it to the Big Sur partition first?
So how will your OS know it should apply your OTA update and not to load itself?
Plug out your USB, run OCLP, build EFI, install it on your destination (Monterey) partition, search for the update, let it download and begin installation, after restart it should load installed EFI, automatically mount update volume and start the process. Try not to meddle into it
Last edited:
I stand by that. Some people have insufficient technical chops...to play around with this.
I'm not an expert, so take my suggestion with a pinch of salt. Anyway since leaving the default disk to boot didn't work, you should give a try to select the other disk. For me it worked. Worst case scenario, it won't make any difference, but it shouldn't do any harm as well.
Hi All! =))
Successfully Updated my MacMini 3.1 from MacOS Monterey 12.0.1RC2 to 12.1 Beta1
OCLP - old config of OCLP 0.3.1NB with Monterand patch
System Volume patched by latest OCLP 0.3.2NB
Issues? When i reverted system patch - its breaked my 12.0.1RC2 instance - and i installed 12.1 Beta 1 from install media and recover broken MacOS.
Thanks for all contributors! Thanks Syncretic for this magic! =)
Successfully Updated my MacMini 3.1 from MacOS Monterey 12.0.1RC2 to 12.1 Beta1
OCLP - old config of OCLP 0.3.1NB with Monterand patch
System Volume patched by latest OCLP 0.3.2NB
Issues? When i reverted system patch - its breaked my 12.0.1RC2 instance - and i installed 12.1 Beta 1 from install media and recover broken MacOS.
Thanks for all contributors! Thanks Syncretic for this magic! =)
Last edited:
I don’t think it will make any difference as is set the open core usb as the default boot device, I wanted to keep it that way as I use boot camp… however I have bitten and have now created the open core partition nd installed locally and am now redoing the upgradeSo how will your OS know it should apply your OTA update and not to load itself?
Plug out your USB, run OCLP, build EFI, install it on your destination (Monterey) partition, search for the update, let it download and begin installation, after restart it should load installed EFI, automatically mount update partition and start the process. Try not to meddle into it
I resolved my issue on my own. Want to share my experience in case anybody face the same problems.
So... the root cause of my issue was due to that fact that NVIDIA Kepler dGPUs lost support. So I should have to boot in safemode (with disabled dGPU). To do this I chose EFI holding Shift button and then just chose HDD with macOS. After that boot process went further to let me set up macOS and eventually reach macOS itself. After this manipulations I should have launch the OpenCore Legacy Patcher, select Post-Install Volume Patch and Patch System Volume. After system reboot that helped me to enable both video accelerators work in normal mode, but not only safe.
Happily installing 12.1b over 12.0.1 on MBP5,2 which has a Penryn T9600 CPU.
Using the OCLP from the announcement on Discord.
I had started the installation with an OCLP without the RDRAND fix which had to fail after the first reboot. After installing the one with the fix, installation just continues ok. How easy… thanks Syncretic and OCLP team!
Installation successfully completed. Post-install patches also done with the RDRAND-fixing OCLP.
Using the OCLP from the announcement on Discord.
I had started the installation with an OCLP without the RDRAND fix which had to fail after the first reboot. After installing the one with the fix, installation just continues ok. How easy… thanks Syncretic and OCLP team!
Installation successfully completed. Post-install patches also done with the RDRAND-fixing OCLP.
Attachments
Last edited:
Re running the 12.0.1 install and, on the last reboot, ending up still on Big Sur, this happened to me a couple of times. The only solution I found was as follows:
BUT FIRST, you'd better have a couple of current backups handy from which to restore your data. If not, reboot the target BS volume and make a backup. I use TM, and also migration to an external SSD
Now boot to an external USB or external SSD, and erase the volume in question using Disk Utility, recreating it as an APFS volume (the default).
Then do a clean install. I do it from a usb or external SSD session. The Installer will ask which volume you want to install it onto, pick the empty one you just recreated. Last reboot will prompt you for Data Migration. As a data source I've successfully used TM and also the external usb>SSD drive.
There may be other ways, that's just what I would do. Installing "over the top" always seems higher risk to me, and on more than a few attempts it hasn't worked.
I can see how this method would work.
My suspicion is that there is not enough free disk space to do the in-place upgrade.
Which is why my earlier suggestion for him to do upgrade from USB installer, after clearing out ~35GB free space.
PS - There is also cruft carried across multiple OS upgrades, so yes, clean install makes sense.
I thought space might be an issue also. But I have a 1 TB drive that was way less than half full. It still would not install over the top. The only options from there that I am aware of are a clean install, or give up and stay on the status quo. The clean install worked, oh happy day.
Here's my Monterey go-live story: macOS 12 Monterey on Unsupported Macs Thread - where I say "it didn't work" that was where it came up still on BS 11.6; actually I attempted that twice, same result. I tried to keep the post brief and stay focused on what worked rather than what failed.
Here's my Monterey go-live story: macOS 12 Monterey on Unsupported Macs Thread - where I say "it didn't work" that was where it came up still on BS 11.6; actually I attempted that twice, same result. I tried to keep the post brief and stay focused on what worked rather than what failed.
Last edited:
