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.

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
iMac 2011, WX7100, stock Atheros WiFi, OCLP 0.22

Smooth installation of Beta1 and smooth update to Beta2 (unattended while having dinner). No WiFi and no BT, of course. But my shopping tour through Europe to get some BT and WiFi dongles will solve this hopefully. Will report later.
 

Attachments

  • Beta2.png
    Beta2.png
    196.7 KB · Views: 313
  • Monterey.png
    Monterey.png
    357.3 KB · Views: 157

nekton1

macrumors 65816
Apr 15, 2010
1,095
777
Asia
Thanks! Will try. I was just getting error in half of the first stage.(Failed to prepare update or something, will post screenshot if it does not start) Clean installation worked.(Migration Assistand ruined system afterwards)
When you used MA after clean Monty install, did you select to migrate JUST user account and nothing else?
 

Mac_tech

macrumors regular
Oct 7, 2020
240
194
Iowa, USA
When upgrading a Big Sur installation on a second partition on a MacBook 9,2 I get the following error during install after a minute.

29754438-AE5A-481F-B120-132FCDB13AC3.jpeg


I booted from the USB flash drive and it started the copy of the files to the internal drive and then machine rebooted to start the actual installation.


I know I have plenty of space, 99gb of free space.

I followed the instructions from Mr. Macintosh, his YouTube video to create the usb via OpenCore legacy patcher.
 

adam25255

macrumors regular
Finally installed Mac OS 12 B2 with OCLP. Had to boot my micropatched 11.5 with OCLP and start installer from user environment. Booting from USB resulted in various errors and using migration assistant on clean install resulted in kernel panic.
 

Attachments

  • Snímka obrazovky 2021-07-02 o 6.02.28.png
    Snímka obrazovky 2021-07-02 o 6.02.28.png
    132.1 KB · Views: 131

amaze1499

macrumors 65816
Oct 16, 2014
1,192
1,221
Is there anyone who performed clean install of Monterey and restored Time Machine backup? Or installing from USB over BS installation? Does that work for someone?
I got the same MBP as you do. BigSur 11.4 was installed and installed Beta2 using USB. OCP 0.2.2. It worked like charms.
 

amaze1499

macrumors 65816
Oct 16, 2014
1,192
1,221
When upgrading a Big Sur installation on a second partition on a MacBook 9,2 I get the following error during install after a minute.

View attachment 1800828

I booted from the USB flash drive and it started the copy of the files to the internal drive and then machine rebooted to start the actual installation.


I know I have plenty of space, 99gb of free space.

I followed the instructions from Mr. Macintosh, his YouTube video to create the usb via OpenCore legacy patcher.
I had a similar issue. BigSur reported 80GB free space, the installer only calculated 16GB space left. I did ran First Aid from DiskUtility and the installation went through after that. However, I did install it right on top of BigSur on the same partition. I dare to use it now as my daily driver. Works 98% of the time without major issues.

Monterey Beta seems to have similar issues with calculating disk space correctly like I saw it in BigSur Beta.
 

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,068
Just tested my previous BigSur nightshift fix (based on pikeralpha method using Catalina binary frameworks) and they still work even with the new Display prefpane in Monterey beta 2, correctly enabling night shift on non Metal GPUs (graphics framebuffer is required for nightshift).

So this should work on any ≤ Sandy Bridge Mac (Ivy Bridge or later have Monterey stock night shift feature) and mainly Penryn Core2Duo.

Just replace the CoreBrightness privateframework with this attached, you could use even BigSurmountsrw2 or any method you prefer.

And of course add "amfi_get_out_of_my_way=1" as boot args to use an ad hoc codesigned binary framework.
 

Attachments

  • Monterey beta 2 non Metal nightshift.jpg
    Monterey beta 2 non Metal nightshift.jpg
    160.1 KB · Views: 165
  • Monterey beta 2 non Metal nightshift2.jpg
    Monterey beta 2 non Metal nightshift2.jpg
    162.5 KB · Views: 172
  • Monterey 19H2 patched CoreBrightness.zip
    347.2 KB · Views: 104
  • Monterey beta 2 Arrandale night shift.png
    Monterey beta 2 Arrandale night shift.png
    867.1 KB · Views: 170

headlessmike

macrumors 65816
May 16, 2017
1,448
2,858
Just installed Monterey beta 2 on my 2013 Retina MBP (MacBookPro11,1) using OCLP and it's working well so far. This is my first experience trying OCLP (I use the micropatcher for Big Sur on the 2012 mini that is my main machine at home) and everything went smoothly even though the documentation is still a bit unclear regarding my specific model.
 

Attachments

  • Screen Shot 2021-07-02 at 4.05.56 PM.png
    Screen Shot 2021-07-02 at 4.05.56 PM.png
    358.7 KB · Views: 107
  • Like
Reactions: olad and Tuli

hvds

macrumors 6502a
Sep 1, 2017
852
2,032
Switzerland
Just tested my previous BigSur nightshift fix (based on pikeralpha method using Catalina binary frameworks) and they still work even with the new Display prefpane in Monterey beta 2, correctly enabling night shift on non Metal GPUs (graphics framebuffer is required for nightshift).

So this should work on any ≤ Sandy Bridge Mac (Ivy Bridge or later have Monterey stock night shift feature) and mainly Penryn Core2Duo.

Just replace the CoreBrightness privateframework with this attached, you could use even BigSurmountsrw2 or any method you prefer.

And of course add "amfi_get_out_of_my_way=1" as boot args to use an ad hoc codesigned binary framework.
Confirmed on MBP5,2 - after replacing CoreBrightness.framework in /S/L/PrivateFrameworks, night shift works.

I used BigSurmountsrw2 from BS to modify my Monterey beta2 installation which is on a USB SSD. It is a clean installation made with jackluke's fix/fix2. No migration done.

I was using disable-animations.sh provided at the time by micropatcher to make life easier for the system without graphics acceleration, and also reduced transparency. Quite usable so far, if only for testing.

I'm writing from Safari Version 15.0 (17612.1.18.1.3) on this installation. Problems seen with Safari when using bookmarks pulldown menu, otherwise OK.

I'm also doing an installation with OCLP 0.2.2 to another partition on the same SSD. Already proceeded to the setup screens.
 

Attachments

  • Bildschirmfoto 2021-07-02 um 18.18.54.png
    Bildschirmfoto 2021-07-02 um 18.18.54.png
    117.2 KB · Views: 127
  • Like
Reactions: jackluke

Mac_tech

macrumors regular
Oct 7, 2020
240
194
Iowa, USA
I had a similar issue. BigSur reported 80GB free space, the installer only calculated 16GB space left. I did ran First Aid from DiskUtility and the installation went through after that. However, I did install it right on top of BigSur on the same partition. I dare to use it now as my daily driver. Works 98% of the time without major issues.

Monterey Beta seems to have similar issues with calculating disk space correctly like I saw it in BigSur Beta.
Ah, interesting about the storage calculation issue and remember the same issue in the Big Sur beta as well. Yeah I did an upgrade of my Big Sur install on a second partition just in case anything happens but got the error twice. Perhaps I should hold off a while until beta 3 or 4 maybe.

Could you take a look at my other post as I get the prohibitory symbol when I try to boot.

Thanks
 

adam25255

macrumors regular
When you used MA after clean Monty install, did you select to migrate JUST user account and nothing else?
This is already solved. I started installation from running micropatched BS when I booted it with OCLP.

And I needed to migrate everything, it works now.(so I have Monterey TM backup that will work)
OCLP is better than I thought.
 

Attachments

  • 21A081D2-58FE-4987-AE7E-64BE1301998D.png
    21A081D2-58FE-4987-AE7E-64BE1301998D.png
    126.1 KB · Views: 93
Last edited:

hvds

macrumors 6502a
Sep 1, 2017
852
2,032
Switzerland
Confirmed on MBP5,2 - after replacing CoreBrightness.framework in /S/L/PrivateFrameworks, night shift works.

I used BigSurmountsrw2 from BS to modify my Monterey beta2 installation which is on a USB SSD. It is a clean installation made with jackluke's fix/fix2. No migration done.

I was using disable-animations.sh provided at the time by micropatcher to make life easier for the system without graphics acceleration, and also reduced transparency. Quite usable so far, if only for testing.

I'm writing from Safari Version 15.0 (17612.1.18.1.3) on this installation. Problems seen with Safari when using bookmarks pulldown menu, otherwise OK.

I'm also doing an installation with OCLP 0.2.2 to another partition on the same SSD. Already proceeded to the setup screens.
... beta2, installed with OCLP 0.2.2, now also running. No migration done yet.

Writing this from this installation with Safari 15.0. I had observed the above problem with pulldown menus also here. Then applied a suggestion jackluke made earlier (defaults write com.apple.coremedia hardwareVideoDecoder -string disable) and it helps also on MBP5,2 with the Nvidia Geforce 9600M GT: no more pulldown problem.
 
  • Like
Reactions: jackluke

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,068
... beta2, installed with OCLP 0.2.2, now also running. No migration done yet.

Writing this from this installation with Safari 15.0. I had observed the above problem with pulldown menus also here. Then applied a suggestion jackluke made earlier (defaults write com.apple.coremedia hardwareVideoDecoder -string disable) and it helps also on MBP5,2 with the Nvidia Geforce 9600M GT: no more pulldown problem.

Exactly because even without GL (or MTL) driver loaded, just with graphics framebuffer the GPU VADriver is there and maybe called from appleapps, infact that also fixed many issues on unsupported IntelHD4000 .

I use a pre copied com.apple.coremedia on ~ library preferences that's why I don't noticed much issues on non Metal GPUs.

@ASentientBot do you tried to disable Nvidia VADriver for your Monterey non metal acceleration trials ?

Or maybe this earlier your finding from HighSierra: https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-28052672
 

nekton1

macrumors 65816
Apr 15, 2010
1,095
777
Asia
BT in a cMP 3,1 (upgraded BT4 LE with Wifi) that was working fine on Big Sur 11.5 with OCLP has become very unstable on Monterey beta 2. Sometimes it cannot be toggled on and sometimes it has gone off after a hard restart.
 
  • Like
Reactions: Project Alice

hvds

macrumors 6502a
Sep 1, 2017
852
2,032
Switzerland
... beta2, installed with OCLP 0.2.2, now also running. No migration done yet.

Writing this from this installation with Safari 15.0. I had observed the above problem with pulldown menus also here. Then applied a suggestion jackluke made earlier (defaults write com.apple.coremedia hardwareVideoDecoder -string disable) and it helps also on MBP5,2 with the Nvidia Geforce 9600M GT: no more pulldown problem.
Now used the migration assistant from the running 12.0b2, located on a USB SSD, after complete setup and after playing with the system a bit.
Used the internal SSD with BS 11.4 as source. Everything selected for transfer except applications where I copied by hand a subset needed right now.
There were no problems with this migration. Now I have a system like I'm used to from BS (slow of course until graphics acceleration may become available, but usable). Writing this from Safari 15.0 of my MBP5,2 without problems.

Using an Ethernet cable for networking. No BT, no WIFI. Internal audio and internal camera working fine with FaceTime and with zoom (didn't need tccplus, probably migration did the settings).

Thank you OCLP team and jackluke!
 
Last edited:

hvds

macrumors 6502a
Sep 1, 2017
852
2,032
Switzerland
Photos app (7.0) with 12.0b2 on non-Metal MBP5,2:

Works for must functionality but sometimes crashes, seen it when navigating Albums.
The log seems to indicate the use of Metal (com.apple.photos.metalrenderer-compile) causing this. It would not be surprising if Photos were now more Metal dependent. But maybe there is still a fix.

Tried to run BigSur's Photos (6.0) on Monterey but can't.
 

Attachments

  • Bildschirmfoto 2021-07-03 um 20.04.51.png
    Bildschirmfoto 2021-07-03 um 20.04.51.png
    38.5 KB · Views: 78
  • photos7crash.txt.zip
    12 KB · Views: 62

ragz01

macrumors newbie
Jul 3, 2021
1
0
I've been trying to do this on a mid 2014 MBP (11.3). Following the method suggested by MrMacintosh.

Have tried with Beta 2 and Beta 1 using OCLP 0.2.2 Keep running into the same error whilst trying to instal Monterey - gets halfway then says "The installer is damaged. Download the installer again and retry"

Have tried changing system time in case it was an expired certificate without success. Have tried downloading again without success.

Any ideas?
 

Bravo2zero

macrumors regular
Jun 1, 2013
125
42
Sheffield
Got this working on my lads 9,1 iMac however lack of GPU support ( at this time, Geforce 9400 256mb ) made it kinda laggy as hell so dropped it back to Big Sur.
 

thegdn

macrumors member
Jun 20, 2021
70
101
I've been trying to do this on a mid 2014 MBP (11.3). Following the method suggested by MrMacintosh.

Have tried with Beta 2 and Beta 1 using OCLP 0.2.2 Keep running into the same error whilst trying to instal Monterey - gets halfway then says "The installer is damaged. Download the installer again and retry"

Have tried changing system time in case it was an expired certificate without success. Have tried downloading again without success.

Any ideas?
was running 11.4 on my MBP11,2 applied at the time OCLP 1.9 then installed dev profile and rebooted.
then the update to Monterey came through.
I've had zero issues.
Also on cMP3,1... not as easy. and dual-boots with Fedora 34.
 

Attachments

  • Screen Shot 2021-07-04 at 04.19.50.png
    Screen Shot 2021-07-04 at 04.19.50.png
    130 KB · Views: 106
  • Screen Shot 2021-06-29 at 6.36.57 PM.png
    Screen Shot 2021-06-29 at 6.36.57 PM.png
    87.5 KB · Views: 112
Last edited:
  • Like
Reactions: PG7
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.