macOS 12 Monterey on Unsupported Macs Thread

[Ausdauersportler]

Thank you. But not talking about OC folder. It’s a Apple folder inside EFI. Could be delete? I think it’s a kind of problem that affect to recognaise others bootable drivers plugged

This is slightly off topic, it is normal macOS system administration and not so much about Monterey:

The Apple folder contains after (supported) macOS updates sometimes SMC and firmware update files. You can safely delete it as the next boot into a (the same supported) macOS will restore these files until your firmware has been updated to the latest and greatest known version.

If your system is no longer supported by Apple with any current macOS versions (like Macs from 2011 and older) you can safely delete the contents of this folder in any case. You will not get an firmware update for your vintage system.

Please add your hardware to your signature. The signature can be edited in your account settings.

 

[LuisN]

Which is fixed by MacPostFactor to run El Capitan.

MacPostFactor replaces EFI with a 32 bit version. AFAIK that doesn't work with Mac OS versions newer than El Capitan ...and you still have the incompatible processor problem.
It's basically the same problem that exists with MacPro 1,1 and 2,1

 

[alfon_sico]

This is slightly off topic, it is normal macOS system administration and not so much about Monterey:

The Apple folder contains after supported macOS updates sometimes SMC and firmware update files. You can safely delete it as the next boot into a supported macOS will restore these files until your firmware has been updated to the latest and greatest known version.

If your system is no longer supported by Apple with any current macOS versions (like Macs from 2011 and older) you can safely delete the contents of this folder in any case. You will not get an firmware update for your vintage system.

Please add your hardware to your signature. The signature can be edited in your account settings.

Sorry for continuing off topic, I delete every file in EFI, reset PRAM and the first boot "ALT" I can select every drive connect to USB but in the next one everything is hide except Principal SSD and SD with macOS Installer. I'm going crazy

 

[Larsvonhier]

Same here. I assume its because of the graphics card specs, non retina screens etc.

Also here on metal GT630 Kepler card and "older" beta, external FullHD screen. But did not notice it before reading the OP. ;-)

 

[alfon_sico]

The Apple folder contains after supported macOS updates sometimes SMC and firmware update files. You can safely delete it as the next boot into a supported macOS will restore these files until your firmware has been updated to the latest and greatest known version.

Looking for documentation of this but not lucky
I confirm that the files is again in my EFI partition "EXTENSIONS/FIRMWARE.ACAP"
How do I update manually the firmware?
Do you think is it the thing that solve Startup manager issues?

 

[beruanges]

.

 

[macpro_mid2014]

Looking for documentation of this but not lucky
I confirm that the files is again in my EFI partition "EXTENSIONS/FIRMWARE.ACAP"
How do I update manually the firmware?
Do you think is it the thing that solve Startup manager issues?

Why don't you install Monterey on an external drive without using OCLP.

 

[DerTschnig]

Monterey works on MBP2012 13 with Open Core and PatchHD4000 fine.

Only VMware Fusion with Monterey is brocken.

I think its a GPU 4000 problem.

With the MBP2012 15 and the changed GPU, it works....

 

[amaze1499]

Monterey works on MBP2012 13 with Open Core and PatchHD4000 fine.

Only VMware Fusion with Monterey is brocken.

I think its a GPU 4000 problem.

With the MBP2012 15 and the changed GPU, it works....

You are not alone. This is an out of box issue. Seemingly not limited to Monterey, from what I saw in different forums.

 

[thienluong89]

Same here. I assume its because of the graphics card specs, non retina screens etc.

Me too, same problem. It happened on control center, widget and some another area.

 

[Larsvonhier]

Monty Beta 9 running here without major issues here on:

- MacBook Pro 4,1 (highres, non metal Nvidia): sleep does not turn off CPU but just the screen, USB does not hotplug detect HID after booting, just memory sticks. Additional expressCard USB 3.0 works fine.
- Mac Pro 3,1 (GT630 Kepler - metal patched, upgraded Wifi/BT card). Both external screens (DVI and DP) work, switching from 1 to 2 screens at login produces short interval (perhaps 300ms) of pixel noise onscreen, then all is fine.

Regarding the issue with SIP always on despite settings in OCLP: Version 0.2.5 seems to do it right, v.0.3.0 always results in SIP reportedly on, no matter what.

 

[vysecurity]

How can I force an update? I've redownloaded the mac beta thing, but I'm still stuck on circa beta 5.

 

[Larsvonhier]

How can I force an update? I've redownloaded the mac beta thing, but I'm still stuck on circa beta 5.

i.e. via the tool gibmacos master. See github for it. Lets you download all the recent versions of macOS and betas.

 

[jackluke]

Monterey works on MBP2012 13 with Open Core and PatchHD4000 fine.

Only VMware Fusion with Monterey is brocken.

I think its a GPU 4000 problem.

With the MBP2012 15 and the changed GPU, it works....

Exactly, on BigSur host the same iGPU HD4000 works correctly with VMware allowing also the "Apple Paravirtualized Graphics Device" , that is Metal 3D acceleration on virtual machine this requires vmtools installed (kext approval is prompted) and this: https://kb.vmware.com/s/article/81657

to exploit this feature I patched also the target guest vm disk with IntelHD4000 GPUs drivers (even if I guess are not strictly required, sufficient only patching the host machine), attached an example picture where from a BigSur 11.4 host is running a Monterey beta 6 guest (on purpose I used this version because still embeds the Nvidia Kepler).

I simply cloned a small Monterey container to a compressed dmg, then shared this on external USB drive, attached to VM and restored to an empty APFS formatted virtual disk.

I guess instead when running Vmware directly from Monterey "Transport (VMDB) error -14: Pipe connection has been broken" is not a graphics issue because even if you make a very simple vm just to enter the BIOS that error shows anyway.

Other VM software (as VirtualBox) work but without paravirtualized GPU.

 

[cab_007]

Monterey works on MBP2012 13 with Open Core and PatchHD4000 fine.

Only VMware Fusion with Monterey is brocken.

I think its a GPU 4000 problem.

With the MBP2012 15 and the changed GPU, it works....

I had a similar problem, however I was able to overcome this issue with forcing discrete graphics and then running Fusion. gFxCardStatus, https://gfx.io

 

[Jordillav22]

macOS 12 Beta 10 installed on iMac late 2012, installed since Software Update.

At the moment everything works just as well as beta 9.

OpenCore 0.3.0

 

[sinbad21]

Monterey works on MBP2012 13 with Open Core and PatchHD4000 fine.

Only VMware Fusion with Monterey is brocken.

I think its a GPU 4000 problem.

With the MBP2012 15 and the changed GPU, it works....

There is a way, use gfxCardStatus and force on the dedicated card. This is explained in the compatibility notes here.

 

[Bravo2zero]

macOS 12 Beta 10 installed on iMac late 2012, installed since Software Update.

At the moment everything works just as well as beta 9.

OpenCore 0.3.0

OC 0.2.5 didn't install B10 on my 2012 so running it again with 0.3.0 nightly.

 

[jackluke]

I had a similar problem, however I was able to overcome this issue with forcing discrete graphics and then running Fusion. gFxCardStatus, https://gfx.io

On which Monterey version (I guess build 21A5506j beta 6 where Kepler dGPU is still stock) are you using any VMware virtual machine, because on beta 9 even forcing dGPU still get unable to start vm , currently I can only start any VM correctly from Big Sur.

But I understand that on BigSur that are still stock IntelHD4000 drivers that's why for me paravirtualization worked, while on Monterey are used BigSur binaries and AppleGVA* frameworks exec from Catalina, from Monterey beta 7 also Nvidia Kepler Geforce binaries from BigSur.

 

[K two]

Does Beta 10 fix the cascading lockout feature introduced in Beta 7?

 

[Tockman]

OC 0.2.5 didn't install B10 on my 2012 so running it again with 0.3.0 nightly.

So what kind of error did you get?

 

[Rob1n]

Hi all,
Monterey Beta 9 fully working on MacBook Pro 9,1 15" Mid 2012 (non-retina)
Just one question. Control Center looks a bit weird, probably non-hidpi related as it is non-retina screen.
Any chance to make these corners look smooth? With HD4000 it looks even worse.

https://www.reddit.com/r/MontereyPatcher/comments/ocsz02

Hi, I have been having this issue for a while now on my Mac Pro 3,1 with a metal gpu on Big Sur, so this is not a Monterey issue but I don't know how to fix it. As it is not a big issue for me I have just been ignoring it until I saw your post here. I have posted about this issue before in the Big Sur thread but at the time no one knew how to fix it.

macOS 11 Big Sur on Unsupported Macs Thread

Hi! I have been using big sur for a while now on my mac pro 2008 and noticed these little white corners/edges in control center. This is not an issue for me but I wanted to ask if there was any way to fix this or if this is normal? The gpu I have is a mac flashed gtx 680 2gb. It is metal...

forums.macrumors.com

 

[MacRumors3590]

B10
I just want to thank everyone again who is involved with getting my unsupported macs running the latest macOS.
YOU GUYS ROCK!!!!!!!!!!

 

[m1ndless]

Been having problems installing Beta 9 and Beta 10 on my 5,1 CMP. Downloads ok but installer just keeps restarting and then changes reboot disk goes back to the old monterey install disk. If i force to boot the installer partition via OC boot picker it just loads for a bit and then restarts. I already have VMM turned on via OC. Previous monterey versions have installed no problem only started happened with beta 9

2012 CMP
OC 0.7.4 with SurPlus

 

[maxsp97]

cMP 5,1 mid 2012 OTA successfully installed Beta 10.
BT / WIFI are working.