I've recently upgraded MBP mid-2012 to Monterey and it works really well. Except for the permission to use Automation/Microphone/Webcam in TCC. The app installation process doesn't add itself to the TCC database so I have to add it manually via SQLite cli. However, I wasn't able to add permission for Google Chrome to use Microphone and Webcam despite the same process works for Skype/Zoom and other applications.
OpenCore Legacy Patcher – Use new macOS versions on old hardware
11–20 of 86 posts
Re: OpenCore Legacy Patcher – Use new macOS versions on old hardware
#12The fact that simply patching the O.S. can be enough to make it work on older hardware is a testament on how Apple could make it work on it too, if they wanted, and without much effort.
Which in my book reads as an artificial way to cut support for otherwise perfectly working machines. Forcing people to upgrade, buy more hardware, and discard the older one, even when they wouldn't otherwise have needed to do it (like when it isn't really crawling and too slow for your needs). Doesn't matter the years, if your 10-12 years old computer still works fine for you, and the needed changes for them are just a couple of driver adjustments, I don't buy the justification for not doing so.
This doesn't feel like "well the gap between how our new software and old hardware work is so big that it isn't even remotely practical to keep them together any more". But more like "well we toggled a boolean and now your're out".
So long for reducing the amount of e-waste in our polluted world!
Re: OpenCore Legacy Patcher – Use new macOS versions on old hardware
#13I have a 2015 iMac, that I spec'ed up as a custom build from Apple, so annoying they don't reconize the power of these machines still and cut support.
I have an 4ghz i7, 32gb ram and a Radeon 395x graphics card, but support is cut.
The machine still runs beautifully on Monterey, so I am hesitant to use the OpenCore legacy patcher, but may have to one day if apps i use drop support.
I love my iMac, but in future, I think i shall need to got he Mac Mini + Monitor route, Mac minis are reasonably cheap and i wouldn't feel so annoyed ditching my machine when it still works well.
Re: OpenCore Legacy Patcher – Use new macOS versions on old hardware
#14The fact that simply patching the O.S. can be enough to make it work on older hardware is a testament on how Apple could make it work on it too, if they wanted, and without much effort. Which in my book reads as an artificial way to cut support for otherwise perfectly working machines. Forcing people to upgrade, buy more hardware, and discard the older one, even when they wouldn't otherwise have needed to do it (like…
They've been doing this for a while. MacOS Tiger included "Built-in FireWire ports" as a system requirement which led to some weird things like the 2000 366MHz iBook and the 1999 B&W 300MHz PowerMac G3 being supported but not the 2000 350MHz iMac G3.
Re: OpenCore Legacy Patcher – Use new macOS versions on old hardware
#15This is amazing! however for my iMac there are still some issues like the GPU Acceleration in Public Beta, see current issue #108. Hopefully someone will finish this issue, I have no ideia how to code this GPU issue.
Re: OpenCore Legacy Patcher – Use new macOS versions on old hardware
#16I have a 2015 iMac, that I spec'ed up as a custom build from Apple, so annoying they don't reconize the power of these machines still and cut support. I have an 4ghz i7, 32gb ram and a Radeon 395x graphics card, but support is cut. The machine still runs beautifully on Monterey, so I am hesitant to use the OpenCore legacy patcher, but may have to one day if apps i use drop support. I love my iMac, but in future, I th…
That's exactly my step, beautiful iMac, however I'm stuck with some GPU issues #108 how did you managed to get it to work?
Re: OpenCore Legacy Patcher – Use new macOS versions on old hardware
#17Catalina was the last supported OS for my 2012 MBA, and the following Big Sur upgrade worked well with OCLP because it only had to patch in WiFi support during the boot process. After that, macOS Monterey also dropped support for my Ivy Bridge GPU, and OCLP had to rely on persistent patches to my system volume to enable 3D acceleration again. These root patches caused some weird issues with 3D acceleration in certain…
Does the T2 break Linux somehow?
https://wiki.t2linux.org/state/
Before these T2 chips, Intel Macs were very close to regular PC hardware. That's why I suspected better Linux support on those older models. The list of still open issues on that wiki seems to confirm this.
Re: OpenCore Legacy Patcher – Use new macOS versions on old hardware
#18Catalina was the last supported OS for my 2012 MBA, and the following Big Sur upgrade worked well with OCLP because it only had to patch in WiFi support during the boot process. After that, macOS Monterey also dropped support for my Ivy Bridge GPU, and OCLP had to rely on persistent patches to my system volume to enable 3D acceleration again. These root patches caused some weird issues with 3D acceleration in certain…
Does the T2 break Linux somehow?
Yes. The T2 is in charge of a lot, keyboard/trackpad input on laptops, the SSD, etc. To get keyboard/trackpad input working you need a custom kernel as drivers still aren't in the mainline kernel.
Re: OpenCore Legacy Patcher – Use new macOS versions on old hardware
#19The fact that simply patching the O.S. can be enough to make it work on older hardware is a testament on how Apple could make it work on it too, if they wanted, and without much effort. Which in my book reads as an artificial way to cut support for otherwise perfectly working machines. Forcing people to upgrade, buy more hardware, and discard the older one, even when they wouldn't otherwise have needed to do it (like…
Supporting old hardware costs money because you need to write more tests. Of course there aren't technical limitations for any but the lowest specced Macs.
Things have changed the past few years but for a while upgrades to CPU performance weren't that meaningful between generations. A CPU that's over ten years old will still perform fine for light desktop use, because that's honestly all you need in most cases. All you need is a RAM upgrade and an SSD!
There are some specific Mac downsides for using older models (the insufficient cooling solution in some laptop models, for example) that will impact long term usability, but the hardware still has a ways to go.
With how much performance you can get out of an older laptop that cost a third of a Mac from the same era by installing an OS like Linux, it's a shame that Apple is abandoning these devices. The same is true for many smartphones; all the modern advancements are nice to haves, very different from the turbulent smartphone era around the late 00s.
Apple needs to sell hardware to make the money needed to fund development but they exclusively focus on very expensive high-end devices, which naturally have a very long life span if it weren't for the software. I wouldn't be surprised if the higher end M1 Macs still be perfectly usable around the time when the 2k38 bug will wreak havoc across the world.
Re: OpenCore Legacy Patcher – Use new macOS versions on old hardware
#20The fact that simply patching the O.S. can be enough to make it work on older hardware is a testament on how Apple could make it work on it too, if they wanted, and without much effort. Which in my book reads as an artificial way to cut support for otherwise perfectly working machines. Forcing people to upgrade, buy more hardware, and discard the older one, even when they wouldn't otherwise have needed to do it (like…
Supporting old hardware costs money because you need to write more tests. Of course there aren't technical limitations for any but the lowest specced Macs. Things have changed the past few years but for a while upgrades to CPU performance weren't that meaningful between generations. A CPU that's over ten years old will still perform fine for light desktop use, because that's honestly all you need in most cases. All y…
>Supporting old hardware costs money because you need to write more tests.
Not supporting old hardware has major costs too: ewaste pollution. But of course those costs are 'externalized' and not borne by Apple, but by everyone else.