Not Recovery Mode, but Single User Mode.You need to go to recovery mode and set:
Code:nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00
Not Recovery Mode, but Single User Mode.You need to go to recovery mode and set:
Code:nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00
I did it from recovery.Not Recovery Mode, but Single User Mode.
Me too MacBook Pro 11,3, i reinstalled big sur ☹️Read my posts and peoples responses, I had the same issue. MacBook Pro 11,3
Why not a final release?View attachment 1899904
Great Job......
First make a backup with Time Machine;So, without looking at all the latest messages; considering all factors such as HD4000 graphics card compatibility, among other drivers on an unsupported machine; if I'm running Big Sur 11.6.1 perfectly fine, is there any reason to switch my unsupported mid 2012 A1278 Macbook Pro with 16gb RAM, a 500gb SSD drive and HD4000 graphics card to macOS Monterey? Every-time I've gone to install the post volume patch so far, it says my machine doesn't require it. I know Apple dropped support for the HD4000 graphics card in Monterey, but has there been a fix for that that makes the entire OS worth upgrading to? My concern is only that I have everything "configured" just the way I want, and if I were to install Monterey and didn't like it, the only way I know to downgrade is to wipe my OS from Recovery mode and reinstall the OS. Or, Is this where a Time Machine Backup would come into play?
I got my sorted after 3 failed attempts, watched this video:Me too MacBook Pro 11,3, i reinstalled big sur ☹️
I still had the version on HDD. The Release is yet to come.Why not a final release?
Will have to use versions of the applications prior to API Metal.Good day,
I am unable to get iMovie or any video editor to work. I have a 2011 iMac. Is it possible to get it to work? I have Monterey 12.0.1 which I got through OCLP.
keep on trying, i did that with BigSur a couple of times!I updated, my MacBook doesnt boot ?
macOS 12.1b runs way better than the early betas, even b6.View attachment 1899904
Great Job......
I fixed this issue and feel the need to post as it was very weird. I ran the upgrade which duplicated the drive names on boot in oc, and it just kept rebooting after 50% then back into big sur. tried lots of different installs of it.It seems pretty likely that it's just picking up the wrong boot entry at some point. Normally I'd expect one entry to be labelled 'Big Sur' and one to be labelled 'Install Monterey' or something like that. Since you have two that are both called 'Mackintosh HD' it doesn't help! If it was my machine, I'd actually look at installing a volume icon &/or content label on your existing OS, then you can see clearly that the one without the volume icon is the one with the update on it, and make sure to keep selecting it while it is still there.
You have to enable Firewire booting in the OCLP settings in order to be able to boot Catalina or later from a Firewire drive.Initially, I tried making the installer on a FW800 HDD, using a partition on it, but couldn't make it to the setup screen. Then I made one on a USB stick... got stuck on the black verbose screen, but finally got to the setup after a few tries.
Thanks. Yeah I figured that that was the problem, after stumbling on the boot volume settings. First time using this, so trying to figure it out as I go along. Any idea why Monterey with OCLP 0.3.2 isn't booting for me?You have to enable Firewire booting in the OCLP settings in order to be able to boot Catalina or later from a Firewire drive.
The installer will then boot from the Firewire drive and you should be able to install to a non-Firewire drive - but it will refuse to install to a Firewire drive.
Step# 3 after every OS update if no Metal. ?Just wanting to clarify, how to install updates going forward after installing 12.01. Do I need to just reinstall the post volume patch after each update? Or is there more to it? MacBook Pro 11,3
Hmm... Command-Control-Power? I tried that and it still hangs. I tried Safe-Boot as well, but apparently the patcher fails to copy. EFI must not be present in this mode? I'm able to re-patch with 0.3.1 without a cold-boot though and when I revert to that version it boots up fine. Any other suggestions?Relying to tripmusic - It does that if OCLP re-installs are not made from a cold-boot in every instance.?
I am in the same boat. I decided not to go past 11.6.1 on either of my 2012's. You can always dual boot and try it out and see if its worth it to deal with the system patch at every update. For me the ease of OCLP and 11.x was just the auto update and its like a supported Mac. I found 11.x to be very stable and fast on both machines. Apple should have supported the 2012's one more OS. Alas, they didn't and here we are tho..So, without looking at all the latest messages; considering all factors such as HD4000 graphics card compatibility, among other drivers on an unsupported machine; if I'm running Big Sur 11.6.1 perfectly fine, is there any reason to switch my unsupported mid 2012 A1278 Macbook Pro with 16gb RAM, a 500gb SSD drive and HD4000 graphics card to macOS Monterey? Every-time I've gone to install the post volume patch so far, it says my machine doesn't require it. I know Apple dropped support for the HD4000 graphics card in Monterey, but has there been a fix for that that makes the entire OS worth upgrading to? My concern is only that I have everything "configured" just the way I want, and if I were to install Monterey and didn't like it, the only way I know to downgrade is to wipe my OS from Recovery mode and reinstall the OS. Or, Is this where a Time Machine Backup would come into play?
This is to invite Apple to break the Big Sur auto update arrangement for some unsupported Macs ? However Monterey has been released to the public now and we are going to see less and less for the Big Sur updates.For me the ease of OCLP and 11.x was just the auto update and its like a supported Mac.
did you have to do anything special to get 12.1b installed.macOS 12.1b runs way better than the early betas, even b6.