I'm having the same issue with some of my Mac Pro installs here. Added in the popular Fenvi T919 that has the newer Broadcom chipset that has worked fine in the past. BT seems to work, likely because it's a separate part of the chipset - but in System Info I just see unsupported network card and no wifi support...
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 14 Sonoma on Unsupported Macs Thread
- Thread starter dhinakg
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Having High Sierra and OCLP on the same disk has never been recommended. This is an old issue primarily in the domain of non-Metal Macs and why OCLP support begins with Big Sur as OCLP disrupts SIP to function. A better and safer solution if actually neccessary is to keep High Sierra and OCLP on separate disks. 🤷♂️
It can be done and work very well. I did it on my 10,1 iMac
First clean installed Sonoma with OCLP installer, then create a new volume within the APFS container using Disk Utility.
I then used a High Sierra installer made using CreateInstallMedia and installed to the new volume.
From the boot picker I have the option to boot into either OS. No issues since I did this a few months ago.
Yes, it can be done but over time it will fail. Likely, one or the other OS will cease to boot.
This problem I posted about is when having High Sierra on separate disks.
Where do you see I had those on the same disk? I work on Mac Pros, my Test box has 4 Sata drives and one AHCI blade, the corrupted System there is on the blade, where High Sierra lives on a Sata SSD.
Another Mac Pro what was corrupted had Monterey on a Sata SSD and High sierra on another separate Sata SSD.
Again: this is not about having High Sierra on the same disk. I guess if so, the problems get even worse. Mixing old and recent APFS variants is always not a good idea.
But as the legacy people often start with an old OS - or have an old OS as a rescue disc this is really an issue, if s.i.p. is disabled.
But the cure is fast and easy, just keep in mind to set the boot-arg
-no_compat_check to get the OS booted with the wrong PlatformSupport.plist if it got replaced.Edit: added information that High Sierra was on another physical disk and High Sierra was booted natively to the linked thread.
Last edited:
It's difficult for our esteemed developers to keep track of obscure 3rd-party issues on unsupp Macs. Please post your concerns to the Paradise on Discord where it may get proper attention. https://discord.gg/rqdPgH8xSN, here.
News to me. 🤷♂️ Suggest you too post this to the Paradise on Discord to receive proper attention. https://discord.gg/rqdPgH8xSN, here.
If that happens in my set up it’s no loss. I don’t use Sonoma on the 10,1 as it is too hobbled by the non metal graphics and old Bluetooth. I only installed Sonoma to see how it ran. The machine is usually booted to HS so that I can use it in Target Display Mode with my 14,2 iMac.Yes, it can be done but over time it will fail. Likely, one or the other OS will cease to boot.
macOS 14.3 Beta 2 is now available OTA. Installed atop Beta 1. OCLP v.1.4.0n. Runs as expected 
Last edited:
MacOS 14.3b2 installs and runs nicely on my MBP 9,1 using the latest OCLP 1.4n
On my mini 2012 it never fails and all Os 's boot since 2020.Yes, it can be done but over time it will fail. Likely, one or the other OS will cease to boot.
OCLP and High Sierra are on the same SSD.
The only limitation booting with or without OCLP is a partitions on the standard Apple disk (Mountain lion-Sierra) is to remember that i have to disconnect thunderbolt devices when booting Mountain lion for cause not supported.
Hello and best wishes for the new year!
Just wondering if anyone has successfully used the OCLP multi boot Win11 instructions here lately?
Edit/update: resetting NVRAM and downgrading OCLP to 1.3.0 appears to fix it.
I have used it many times over the last few years for multi boot with Monterey, Ventura, Sonoma and OCLP, but now here it looks like something has changed with either the latest Win 11 iso or possibly something with Sonoma or perhaps more likely latest OCLP (1.3.0/1.4.0n)
It installs fine as before but the resulting Win 11 install says something is wrong and restarts.
Any hints appreciated! Many thanks.
Just wondering if anyone has successfully used the OCLP multi boot Win11 instructions here lately?
Edit/update: resetting NVRAM and downgrading OCLP to 1.3.0 appears to fix it.
Last edited:
Same here on MBP11,1 (on external SSD). Running well.macOS 14.3 Beta 2 is now available OTA. Installed atop Beta 1. OCLP v.1.4.0n. Runs as expected
View attachment 2332519
macOS 14.3 Beta 2 is now available OTA. Installed atop Beta 1. OCLP v.1.4.0n. Runs as expected
View attachment 2332519
Would you 2 please test whether you have these problems in the Photos app - with the integrated graphics?
And did you have this problem before with macOS Sonoma like I did?
I am always fascinated by people who install betas 2mn after they are available and announce 3mn after first boot that all is working perfectly ...
At the same time we all know that using OCLP patched systems bring some problems not solved (yet or never) ...
At the same time we all know that using OCLP patched systems bring some problems not solved (yet or never) ...
Last edited:
Never claimed all is working perfectly, "runs as expected" means nothing is apparently wrong. Testing for previous issues - Weather, AppleTV, Safari and Microsoft apps, Console is checked for crashes, etc. As not a collector, can't drill into Music or Photos. No reason to use the profit center, iCloud. 3rd party apps like Firefox, uTube and Prime Video work as intended. If anything wrong is observed it gets reported. This is a Mini not a MacBookPro or iMac, btw. Differences exist. Glad to fascinate you. 😉
There a lot of posts here, from the same "All working perfect" people, that some minutes later starts with "Talked too soon. My XXX does not work"... 😬
On my iMac 17,1 I have (at least) these issues:
- VMware fusion guests not working with graphics acceleration
- Safari doesn’t read DRM videos
- videos thumbnails are sometimes corrupted (green artifacts) in Photos.app and finder
- Apple TV+ not reading videos in full res
A lot of things are working, but it’s not as robust as a supported OS (it’s normal, I know that it’s not possible)
I just want to illustrate that it’s better to stay on a supported OS unless one app absolutely forces you tu updates (for me, it’s Xcode)
As a safety net, I install betas (of macOS) and nightlies (of OCLP) only on external SSD. The internal SSD holds production versions, as the MBP11,1 is really for my daily work.
Regular Time Machine and frequent CCC backups, together with a USB installer for the latest OS (14.2.1) are the other safety net which should always be present.
Trying betas gives confidence that the MBP11,1 is good for the coming release of macOS.
This is a confusing statement (for me). I think there are multiple things being confused in this statement:
- OCLP is not Open Core. OCLP installs Open Core in the EFI of a disk that is formatted with GUID partition map. OCLP is an app that runs in macOS.
- There is no problem with Open Core and High Sierra being installed on the same disk. The "old issue" is a potential conflict between High Sierra and macOS versions starting with Big Sur and newer.
OCLP is based on OpenCore, installs OpenCore, runs on OpenCore, to separate the two in this context is indeed mysterious. APFS corruptions between High Sierra APFS versions and later versions is a well-documented fact, as you point out. OCLP merely enables it to happen. 🧐