It works well here on Mac 2017, I believe it is due to the hardware that has similarities with officially supported 2018 models, and from that model onwards the processor has support for the h.265 codec and graphics with support for Metal 3.
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 15 Sequoia on Unsupported Macs Thread
- Thread starter flagers
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Well in talking to someone who was a former apple repair person, or maybe he's still certified now. He said that macOS 15 will be the latest OCLP compatible version, as macOS 16 will require the T2 chip.
We need to wait for the new version to confirm. If confirmed, there will be 2 years of support left for Sequoia.
UPDATE - I have aborted this as updating OCLP boot to 2.3.2 as it suggested made by 15.4.1 not boot anymore. I will stay with 2.3.1 boot EFI for now. As a side note OCLP usually intercepts the OS update with a KDK message, but it failed to do so this time (Patcher 2.3.2)?
- - - --
*CROSS POST*
I have just successfully updated to 15.4.1 (OCLP 2.3.2) and OCLP wants to update my bootloader. However I had the bluetooth partial loss of function problem when I switched from DIY OpenCore to OCLP because I wanted to run Sequoia. I finally figured out the issue after struggling a lot (wish I'd seen this post then!) and tracked it down to the "AirportBrcmFixup.kext" which I knew was not needed having done the OC configs myself up to then, following Martin Lo and then @cdf. Once that config entry was manually edited out and the associated kext(s) deleted I was good to go again with BT working properly (I have an updated Wifi card).
Now OC has "identified 2.3.1 vs 2.3.2" in EFI and wants to update and re-write the bootloader stuff and insists on including "Adding AirportBrcmFixup.kext 2.1.9" which IMO is a bug - i.e. its not identifying my hardware properly and doing this will break BT again. How can I override this auto decision in OCLP Patcher? Or do I have to install it and manually reconfigure OC manually by mounting the EFI afterwards again. Its a bit annoying and long winded to do that and have OCLP just overwrite everything again at some point.
I tried to report this when I found the problem but I am not a member of github and frankly don't consider myself very expert here.
So, anyone know how I can configure OCLP patcher in terms of what it automatically (but wrongly) decides is needed for my hardware?
TIA
- - - --
*CROSS POST*
I have just successfully updated to 15.4.1 (OCLP 2.3.2) and OCLP wants to update my bootloader. However I had the bluetooth partial loss of function problem when I switched from DIY OpenCore to OCLP because I wanted to run Sequoia. I finally figured out the issue after struggling a lot (wish I'd seen this post then!) and tracked it down to the "AirportBrcmFixup.kext" which I knew was not needed having done the OC configs myself up to then, following Martin Lo and then @cdf. Once that config entry was manually edited out and the associated kext(s) deleted I was good to go again with BT working properly (I have an updated Wifi card).
Now OC has "identified 2.3.1 vs 2.3.2" in EFI and wants to update and re-write the bootloader stuff and insists on including "Adding AirportBrcmFixup.kext 2.1.9" which IMO is a bug - i.e. its not identifying my hardware properly and doing this will break BT again. How can I override this auto decision in OCLP Patcher? Or do I have to install it and manually reconfigure OC manually by mounting the EFI afterwards again. Its a bit annoying and long winded to do that and have OCLP just overwrite everything again at some point.
I tried to report this when I found the problem but I am not a member of github and frankly don't consider myself very expert here.
So, anyone know how I can configure OCLP patcher in terms of what it automatically (but wrongly) decides is needed for my hardware?
TIA
Last edited:
Please refrain from ridiculing my post. I have good reasons to say that.
Since the day they have introduced AI into MacOS and iOS many features I use on a daily are pretty much broken. At least from my point of view. Look at translation and AutoCorrection, dictation. Syncing to iCloud. Photos. Music. It’s reproducible every time. And it’s unlikely it has to do anything with OCLP.
It has become so inefficient to use, I would not buy anything new from Apple for the time being. Apple really needs to have another Snow Leopard moment across the board.
However, I’m prepared to be wrong and always open for suggestions.
I don't think anyone was ridiculing your post. However, had you given the above reasons for the 'effing' mess, folks would have understood why - which I suspect was why @houser asked for elaboration. I found your use of 'effing' funny; but the post itself was solid; subsequently you provided reasons why you think Sequoia is a mess.
No ridiculing in any way shape or form was intended. Perhaps I should have phrased my question more clearly.
I have three Intel Macs running Sequoia with and without OCLP and see none of the issues you mention so was just curious. Retired, so no professional requirements anymore
Last edited:
So your trusted source is saying that Apple will be supporting Intel in macOS 16? That's great news. What kind of coin did they flip to make that prediction?
Several websites claim that macOS 16 is Apple Silicon only, while others claim the opposite.
1: macOS 16 is going to drop support for all Intel Macs
4: Making Sense of Those macOS 16 Rumors
8: macOS 16: Rumors, features, release date, supported devices, more
3: When will Apple stop supporting Intel Macs?
8: Got an Intel Mac? Here’s the deal so far, and possible future scenarios
2: Apple T2
Today, there are only rumors, and Tim Cook probably doesn't even know whether macOS 16 "Cheer" will work with an Intel computer (T2 or not).
Several websites claim that macOS 16 is Apple Silicon only, while others claim the opposite.
View attachment 2503172
1: macOS 16 is going to drop support for all Intel Macs
4: Making Sense of Those macOS 16 Rumors
8: macOS 16: Rumors, features, release date, supported devices, more
View attachment 2503171
3: When will Apple stop supporting Intel Macs?
8: Got an Intel Mac? Here’s the deal so far, and possible future scenarios
View attachment 2503175
2: Apple T2
Today, there are only rumors, and Tim Cook probably doesn't even know whether macOS 16 "Cheer" will work with an Intel computer (T2 or not).
Any information out there “already” if OCLP supports it ?
He said intel, but T-2 so that rules out open core macs because none of them have a T-2. So his exact words will be only currently supported intel Macs with a T-2. He even said, he wasn't sure if Apple was going to cut off the 2018 intel Mini, or not. So it sounds like if it supports intel, it will be very limited.
2018 Mac mini is now considered vintage product so more than likely it will be cut off.
Obtaining service for your Apple product after an expired warranty - Apple Support
Learn about your options for getting service and parts for Apple devices that are past their warranty period.
That's what I thought and why he said macOS 16 is going to be T-2 and Apple silicon only. It sounded like the 2018 Mini was the last intel mac not to have a T-2. 2019 and later, have a T-2.2018 Mac mini is now considered vintage product so more than likely it will be cut off.
Obtaining service for your Apple product after an expired warranty - Apple Support
Learn about your options for getting service and parts for Apple devices that are past their warranty period.support.apple.com