macOS 12 Monterey on Unsupported Macs Thread

[thatsmeonlyme]

OCLP 3.2 latest nb. OTA update to B3 successful.

 

[gw463]

Successfully update to 12.1 (21C5039b) with OCLP 3.2N

 

[TigerA]

Not getting the OTA update to beta 3 for my iMac12,2 with the latest OCLP 0.3.2nb after trying no / minimal / moderate spoofing options and unenroll and re-enroll DeveloperSeed program. This machine was clean installed beta 2 yesterday. On the other hand, my iMac13,2 received OTA promptly and updated successfully from beta 1.
Any one any idea?

Add: After rebuilding the EFI to OCLP 0.3.1, the iMac12,2 is getting the OTA update now! It must have been related to the VMM thing, even though I still have no clear understanding of it and an unpatch did not bring any joy?

 

[JonathanX64]

Hi all!

I have MacPro4,1 flashed to 5,1 with Metal graphics card and 802.11ac Wi-Fi module. It has 48gb of RAM installed as 16gb modules in slots 1-2-3 to ensure maximum performance.

Today I've installed macOS Monterey using latest OCLP non-Nightly. Everything works fine, except...

Some RAM is missing in Monterey. When slots 1-2-3 are populated, it shows 32gb instead of 48gb. If I put RAM in slots 1-2-4, it will only show 16gb. When I boot into Big Sur, it always shows all the RAM available, there is no such bug.

Have anybody encountered this? Any idea on how it can be fixed?

Thanks.

 

[K two]

Beta 3 about 2mins left.

 

[internetzel]

Alright so Long story short, I'm dual-booting two Unsupported OS's on my Mid 2012 A1278 Macbook Pro: Big Sur and Monterey on two separate partitions. However, I keep getting an error message about some "Pipe being broken" when I try to run VMware Fusion Pro 12 to **** around with Kali Linux. I've tried all the suggested fixes, and it seems others have had this same issue and I was wondering if there has been a permanent fix or workaround figured out and established; or is it something I'll just have to wait for them to fix when the next VMware Fusion update is released?

VMWare long ago made clear that this won't be fixed, since the new engine for Fusion 12 is based on Apple Hypervisor and Apple minimum requirement for it is late-2013 Mac Pro, with older Macs not having the necessary CPU requirements.

The fix is: switch to Parallels, as VMWare >12 will never work on a MP5,1.

I've got VMWare Fusion 12.1.2 working on my first generation core i5-750 iMac (currently running Catalina 10.15.7), by manually adding the line

monitor.allowLegacyCPU = TRUE

to the .vmx configuration file contained in the VM bundle.
That way I can now run Windows 10 from its own partition where I originally had installed it natively (UEFI) - the VM does even boot via OpenCore directly from the EFI partition.
It doesn't run with great performance but good enough for some Windows only VBIOS editing tools I occasionally use.

If you need some more instructions where to add that line, feel free to ask.

 

[Tockman]

with OCLP 0.3.1.

 

[Tockman]

So I have a question/proposal to our respected OCLP developers: may be, it would have some sense to add to the main menu (or right after the volume patching finished) an option to reboot computer? The reason: it's very time-consuming to enter shortcuts or move a mouse to the right menu on unresponsive machine while proper video driver isn't installed yet

 

[Synchro]

It's not an issue with MacPro5,1, but the SSD was one of the BTO options, for all Mac Pros since mid-2010:

Oh, I never knew that, thanks! Anyway – any ideas why the Monterey update would fail with this firmware update error message?

 

[Earl Urley]

It's not an issue with MacPro5,1, but the SSD was one of the BTO options, for all Mac Pros since mid-2010:

I actually had one of those with the Apple SSD, it was a simple rebranded SATA Samsung 830 with Apple firmware and 512 GB was the only size option.

 

[junley4]

After spending almost 8 hours with 3 attempts by erasing the entire disk then install the latest Monterey 12.1 beta2 with the latest OCLP 0.3.2n, it still shows 2 Messages app in Notification. The first 2 attempts were using Time Machines after the clean install and the last one did not. What I've noticed at the very last attempt is that there was only one green Messages app icon before the Post-Install Patch being applied. Then it comes the 2nd blue Messages app icon (seem from Catalina) after applying the Patch (iMac12,2 with K3100M graphics card).
Any one has any idea??? I am really confused because it's absolutely a clean install.

If this doubled app in notification settings really bothers you, maybe you can just stay in stable release 12.0.1. We have the same machine 12,2 with k3100m, i am on 12.0.1 with OCLP 0.3.1 stable release, and I don't have that issue.

 

[TigerA]

If this doubled app in notification settings really bothers you, maybe you can just stay in stable release 12.0.1. We have the same machine 12,2 with k3100m, i am on 12.0.1 with OCLP 0.3.1 stable release, and I don't have that issue.

The reason for questioning the double Messages icon is that my Messages app crashed around every hour on my iMac12,2 with K3100M card when running 12.1 beta1. "see double" actually does not bothers me that much (I have astigmatism anyway for one eye?). Now I am running 12.1 beta3. So far the Messages app has not crashed yet: fingers crossed.

 

[junley4]

The reason for questioning the double Messages icon is that my Messages app crashed around every hour on my iMac12,2 with K3100M card when running 12.1 beta1. "see double" actually does not bothers me that much (I have astigmatism anyway for one eye?). Now I am running 12.1 beta3. So far the Messages app has not crashed yet: fingers crossed.

i see... in my case, i havent experienced crashing in my messages app either. maybe it is because you are installing a beta. is there significant benefit for you in installing betas rather than stable releases?

 

[Vacusuck]

Where are you trying to enable Airplay exactly? Do you mean on System Preferences > Sharing? Are you booted on the internal drive?

If so, yes, same here. I just booted both versions of Monterey I have installed currently on my rMBP 10,1. The option to enable Airplay is present on the production version 12.0.1 internal drive, but not on 12.1b2 external drive. Good catch.

The obvious question to ask would be, do users with supported Macs see the same thing. Oh wait, my Mac mini 2018 has beta 2 on the internal drive, I'll check and report back.

Later, OK, on my supported Mac mini 2018 running 12.1b2, under System Preferences > Sharing, the option to enable Airplay does appear. The OCLP guys might want to take a look at this.

Maybe it just doesn't work when booted on an external drive? Seems unlikely but hey.

I'm using an internal SSD I replaced the original hard drive with. Works perfectly except for this one feature. I'm trying to Airplay to the iMac with the AirPlay receiver functionality in Monterey in the System Preferences -> Sharing. I just updated to 21C5039b with no change - still no AirPlay Receiver :-(

 

[K two]

Beta 3 is very pretty and all but it kills Firefox and Safari, Chrome works and when installed made a double entry in Notifications. EVERYTHING ELSE WORKS, overall and runs as expected. And yes, AirPlay Receiver is there. Mixed bag. OCLP_032N

 

[algernonpule]

Two disks, two EFI partitions, now two OpenCore installations. Check the OCLP docs how to de-install OpenCore from an EFI partition and get rid of the old version on the HDD and keep track where you install OpenCore. Stick with one version only.

Your Mac may have a fixed boot order, i.e. first SSD, than HDD or vice versa. So you might end up after a PRAM reset with the wrong version bootet.

Read the complete OCLP docs including the section how the booting works to understand what your doing and getting when installing this great software. First read, then dowload and install!

Ouch, but thank you! Now (at last) back with one OpenCore, and stepped back from the bleeding edge by reverting to release versions of OCLP and Monterey! Just for your information, I found MountEFI didn't work for me, but using the commands "diskutil list" (to find the EFI partitions) then "sudo diskutil mount diskXs1" (where X is the relevant drive) did, so all good now.

 

[TigerA]

i see... in my case, i havent experienced crashing in my messages app either. maybe it is because you are installing a beta. is there significant benefit for you in installing betas rather than stable releases?

Curiosity only: a wannabe bleeding edge person ?

 

[tsialex]

Oh, I never knew that, thanks! Anyway – any ideas why the Monterey update would fail with this firmware update error message?

You need to change FirmwareFeatures for Monterey.

Activate AMD hardware acceleration

The best reference for this is directly at the OC source: https://github.com/acidanthera/OpenCorePkg/commit/1cb8490fd60f6b5f983d42e5bbf08e3d2d43d8f6 Explicitly: bit 35 (FW_FEATURE_SUPPORTS_LARGE_BASESYSTEM) of FirmwareFeatures is required for the update. The minimal approach is to preserve the...

forums.macrumors.com

 

[rehkram]

I think I'll wait a while before the next upgrade ...

 

[junley4]

Curiosity only: a wannabe bleeding edge person ?

??? I've been there until I needed this 12,2 for my work so I had to stop testing betas and only install stable releases that are proven stable with OCLP. Works for me, so far so good ?

 

[HannHenne]

Hi there,

I need your help again.

As already written I have an iMac in the middle of 2010. In the meantime I have everything on the system up and running. You can get your help. The AMD graphics card worked now and with EasyRes the screen no longer flickers.

Now I want to get Photoshop running on the iMac. It can be installed. The program aborts the start. Does anyone have a solution to this?

thank you in advance

 

[maxsp97]

cMP 5,1 mid 2012 via OTA 12.1 Beta 3 with OCLP 0.3.2.

 

[TigerA]

Hi there,

I need your help again.

As already written I have an iMac in the middle of 2010. In the meantime I have everything on the system up and running. You can get your help. The AMD graphics card worked now and with EasyRes the screen no longer flickers.

Now I want to get Photoshop running on the iMac. It can be installed. The program aborts the start. Does anyone have a solution to this?

thank you in advance

It would be helpful if you can publish your system spec/configuration in the signature field, like others, so that people can provide advice accordingly.
In regard to your Photoshop, could it be too new for your system because I saw you mentioning EasyRes, which could be used for a non-metal graphics card.

 

[Ausdauersportler]

As already written I have an iMac in the middle of 2010. In the meantime I have everything on the system up and running. You can get your help. The AMD graphics card worked now and with EasyRes the screen no longer flickers.

Now I want to get Photoshop running on the iMac. It can be installed. The program aborts the start. Does anyone have a solution to this?

thank you in advance

Quite simple, change your graphics card as described on the thread linked in my signature.
The other option would be to try an older version based on OpenGL, only.

You do not get a metal emulator or full application compability just because a patcher makes it possible to install more
recent macOS versions. Some features and tied to hardware, because of this I upgraded all my iMacs with AMD metal card and with BT/WiFi BCM94360xxx cards.

Even this will not give us 100% application support, some software asks for more recent CPU models.

P.S.:
After checking the photoshop hardware requirements for macOS I figured out the CPU should be fine, but the GPU needs to be metal! In case you need help with your GPU exchange just send a PM.

 

[HannHenne]

Then I ask around with which OS would Photoshop still be running? Big sur?