????
But then again, it's actually quite smart, better than sticking tape onto the display, maybe an idea for an invention.
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
But then again, it's actually quite smart, better than sticking tape onto the display, maybe an idea for an invention.
dude, they asked if their mac/gpu supported metal and i answered. stop interpreting posts the way it suits you as you have been doing for the last several pages and start reading what has been actually written.
It might be a "pump and dump" scheme. I have shares in Home Depot, who cleverly designed the pencil to roll off your workbench several times a day. I got tired of picking it up off the floor. It works great for this purpose.????
But then again, it's actually quite smart, better than sticking tape onto the display, maybe an idea for an invention.
I had that occur once and performed a power down, option-key powered up, booted up to OCLP EFI and then let it boot normally.Just following up re. rMBP10,1 Monterey beta 7, external display not working. I ran the OCLP 0.2.4 post install HD4000 patches. The OCLP process ran OK, so time to reboot.
Boot went OK for a little while then stopped. "Maybe it's running slowly or doing a backup" I thought. 45 mins elapsed so I deployed my "MacOS Boot Stall-O-Meter" ™ (a cocktail stick stuck into a pencil eraser, see attachment). I came back an hour later and the progress bar hadn't moved. Forced a power-off and restarted. Same thing, same place (I'd left the pointer in place so I know).
Next step is Recovery Mode
Thanks for that cab_007, no joy though. Option-booted into OCLP EFI, selected the beta volume, hung at the same point. I did that twice, then tried a normal boot to the beta volume without the option key, same thing.
Powered off again and rebooted to the Big Sur volume on my SSD, BS booted normally. Feels like a bug in Monterey beta 7 to me.
Powered off again and rebooted to the Big Sur volume on my SSD, BS booted normally. Feels like a bug in Monterey beta 7 to me.
Hello my friends. I had installed Big Sur 11.6 using OCLP 0.3.0 in my cMP5,1 (2009), but the machine was freezing after some minutes of use. So I returned to Catalina using dosdude1 patcher. Maybe Monterey B8 would be a better choice than Big Sur 11.6? The machine runs perfectly with Catalina 10.15.7, so I don't believe in hardware problems as a cause of Big Sur didn't run...
Ok update on the 09 Mac Pro. Keep in mind I’ve used OCLP 0.2.5 and 0.3.0 both and they both act the same.
When I make an installer (Big Sur or Monterey,) the installer either gets through the first half and then can’t verify my firmware, or crashes on boot.
When carbon cloning from a supported Mac and then patching with OCLP, the hard disk is completely unreadable. Like won’t even boot.
Im at wits end. Bout to say screw it and stick with Catalina but I hated it when it came out. What am I doing wrong?
When I make an installer (Big Sur or Monterey,) the installer either gets through the first half and then can’t verify my firmware, or crashes on boot.
When carbon cloning from a supported Mac and then patching with OCLP, the hard disk is completely unreadable. Like won’t even boot.
Im at wits end. Bout to say screw it and stick with Catalina but I hated it when it came out. What am I doing wrong?
Big Sur 11.6 runs like a charm in Mac Pro 5,1. Monterey beta 6 also. Beta 8 is very problematic.
Believe it or not, a shutdown is different than a restart, I had the same happen to me, I restarted, held the Option key, this did not work, a complete shutdown and then the Option key did.....happened twice, so there must be a difference, I suspect OCLP might be the issue here.
A restart/reboot different from a shutdown, something I would have never expected to be the case.
Note: There's more to it, this was just a short explanation of what happened, problems with bootpicker and so on.
Monterey beta8 now work fine on macpro 3,1 with OCLP..i've upgraded it from Catalina and finger cross...
You are definitely correct, and I would like to understand the differences between a cold boot and a reboot. In my testing yesterday the only way to get out of the boot hangs was to force power down each time.
Booting OpenCore and macOS
Now we finally get to boot OpenCore!
Reboot machine while holding Option to select the EFI Boot entry with the OpenCore icon (holding the Control key will make this the default boot entry):
- This will be the Mac Boot Picker
Thanks K2, I have read all the OCLP documentation and review it for updates fairly often. That was not what I was wondering about. My interest is in understanding the differences between a cold boot and a warm boot (regardless of OCLP) in order to better understand the system flow.
After a couple of days with 21A5534d on MBP9,2 16GB Ram:
Up until now pretty much each build was snappy, easy to use. This one a different story: It become literally unusable.
Bluetooth audio stuttering, mouse comes on goes away literally 10 times a minute, copy rates between internal sdds became horribly slow. Safari is a nightmare. Takes up huge amounts of RAM without having even a page open. Sometimes the whole system seems to freeze up for minutes.
This build is definitely not ready for prime time.
Up until now pretty much each build was snappy, easy to use. This one a different story: It become literally unusable.
Bluetooth audio stuttering, mouse comes on goes away literally 10 times a minute, copy rates between internal sdds became horribly slow. Safari is a nightmare. Takes up huge amounts of RAM without having even a page open. Sometimes the whole system seems to freeze up for minutes.
This build is definitely not ready for prime time.
Last edited:
Not with me: my 5,1 on beta 8 (specs below and with SurPlus) is running fine. No problems at all Booting warm or cold and running apps.
Last edited:
Thank you @trifero!
Maybe my error was erasing the SSD as APFS volume before installing? I would format as macOS Extended (HFS+) with a GUID partition map...? Or maybe SIP was enabled? Or both... Idk... I will try to install Big Sur 11.6 in a couple weeks or wait for Monterey final release when it comes.
Explains it better than I, here: https://medium.com/@mannantirmizi/how-cold-boot-is-different-from-warm-boot-35d6f2229ff0 ?
Thanks, that's a good overview. I'd like to drill down to the nuts and bolts a bit more but it gives me some idea of the terrain.
BTW my technical major is the IBM 'midrange' 64 bit m/c's, a.k.a. System I, iSeries, AS/400, and the first one, System/38.
I hope you don't mind the question: Does switching back and forth between your nVidia GeForce 9400M and the discrete 9600M GT via gfxCardStatus work now with OCLP 0.3.0n?
You may want to attempt a Disk First Aid on your Monterey volumes before attempting to boot from there. You can also do a full B8 reinstall. I had lots of problems pre-OCLP 0.2.5 and the malformed B7 installer. So far, B8 has been nice on my 10,1 with post-install patch.
I had to remove OS12 from the 9,1 iMac as it started to go into a standby loop where it kept going to add password Lock Screen then major lag then lock screen again. I've now dropped it back to Big Sur which works perfectly.
As an update to this, which I tried when installing b8. Hit the same problem where the desktop would never display, verified again that the OS was actually running by logging in with screen sharing. Another workaround, provided you have Windows installed with Boot Camp, is booting into Windows and switching the gmux chip forcefully to the iGPU using the scripts from this GitHub repo: https://github.com/0xbb/gpu-switch Rebooting (graphics will work fine via the iGPU), and then doing the post-install patches.
Upon further investigation, it appears without the Kepler kexts installed, the gmux defaults to dGPU when booting Monterey, and without the kexts, the display isn't correctly detected (macOS thinks an external display is connected to the dGPU). This would explain the lack of graphics output after update. It may be possible to use gfxCardStatus to flip to iGPU in macOS before updating as well but as far as I can tell it doesn't work on Monterey. I also am not sure if compiling gpu-switch from the above repo for macOS will work either; the readme on the repo seems to indicate it hasn't worked since Sierra. However, I have not tried it.
Edit: gfxCardStatus appears to work, provided its used while Kepler kexts are installed. So try forcing it to iGPU before running an update, in order to be able to boot and install the post-install root volume patches. It won't work while the system thinks an external display is plugged in.
Last edited:
After some consideration I've decided to wait until Apple have all their ducks in a row and release another beta with fixes to the known problems. I don't think it's worth the time debugging problems that should disappear in the next release. I can live without having a slightly broken beta to play with.
I did run first aid on both volumes from Big Sur. Problems found included a corrupt snapshot which will "disappear when the snapshot is deleted"
and a couple of other warm fuzzy messages. Ended with exit code 0, which probably means "don't worry about a thing"
Last edited: