Sidebar Sidebar
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

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
deeveedee said:
it was vanilla install via OCLP
Click to expand...
Hi @deeveedee

What you meant was “clean install” instead of “vanilla”.

Sorry to play with words but if the installation uses OCLP it can't be vanilla because a vanilla installation is a clean installation of the latest system supported by a Mac without any modification of the system files.

I wanted to clarify this for novice readers who might learn the wrong terms, so as not to mislead the experienced users who would be helping them.
 
@alphascorp When you find the universally accepted definition of "vanilla" please let me know. The way that I interpreted the Reddit post, the key point of the Reddit post was not "vanilla" but was "no migrated apps."

EDIT: The Reddit post says "... no migrated apps. My suspicion is the dev tools and XCode parts I had were the root cause of it" which I interpreted to mean that an upgrade from a previous macOS version (keeping the installed apps) is the suspected cause of the problem. Thus my interpretation and recommendation to perform a "clean" installation.
 
Last edited:
deeveedee said:
If it helps, I love vanilla ice cream.
Click to expand...
Me too!!!

A quick AI search will give this answer:

A vanilla install of macOS refers to installing the operating system using the official macOS installation media without any modifications or additional software. This means the OS remains in its original form, untouched by customizations or updates applied by third parties.

For example, installing macOS using the vanilla method would involve booting from the official macOS installer and proceeding with the installation as Apple intended, without incorporating any unofficial patches or modifications.
 
@alphascorp In the hackintosh community, the term "vanilla" has almost as many interpretations as there are hackers. In the ice cream community, vanilla is a term used to describe a flavor that is derived naturally or artificially. Both communities argue about the definition of "vanilla." I will defer to you and trust that "vanilla" does have a definition accepted by a plurality in each community. :)

But we're way OT... I hope the OP attempts a fresh/clean/virgin installation of macOS (no app migration) and reports back.
 
To whom it may concern: successfully installed 14.7.5 via OCLP 2.3.2 on MacMini3,1 & MacBook5,1
 
Bye, bye Ventura - Hello Windows 95!
Just joking - upgraded to Sonoma 14.7.5 via USB - running well. Had to update Safari to 18.4 as v17.?? would open but not render the front page or load any pages.
 
Minghold said:
That's the way to do it with iMacs: APFS OS on an external SSD, and Mojave HFS+ on the internal rotationa or Fusion).
Click to expand...
I have the internal non-fusion drive formatted as APFS (first tested OpenCore there) and have Catalina installed. I rarely ever boot into it, use it primarily as a file organization area before off to the archive disk. I found High Sierra to be the last snappy late 10.x.x release, omg Catalina is a dog. One day I might install a light weight Linux distro on the HD.
 
  • Like
Reactions: Minghold
LookingOut said:
I have the internal non-fusion drive formatted as APFS (first tested OpenCore there) and have Catalina installed. I rarely ever boot into it, use it primarily as a file organization area before off to the archive disk. I found High Sierra to be the last snappy late 10.x.x release, omg Catalina is a dog. One day I might install a light weight Linux distro on the HD.
Click to expand...
Mojave bug-fixes a lot of High Sierra problems relative to 2012+ machines (albeit at the expense of dropping pre-2012 support) -- but the trick is that you have to clone it from its default install APFS partition to a MacOS Extended-journaled partion, and disable SIP, MRT, MDS_stores, Report Crash, and Spotlight Indexing. (You should do that on all Mac OSes.)
 
I've used OCLP 2.3.2 to install Sonoma on my Mac Pro 3,1.

It' boots ok, but I cannot update get to update Safari to 18.4.

And there is some weird stuff showing up in my Login apps.

There is a "rm" background task. HUH? Is that supposed to be there?
 
cb4ii said:
To whom it may concern: successfully installed 14.7.5 via OCLP 2.3.2 on MacMini3,1 & MacBook5,1
Click to expand...
Thank you for the report. However, the fact that the installation was successful does not mean that the Mac will work well and give satisfaction in use.
I speak from experience and from repeated attempts over the years with both the MacBook 5,1 Aluminium and the MBP 7,1 mid 2010.

Slowness and jerks aside, all 'Metal' programmes, such as iMovie, PowerPoint, etc., doesn’t will work in the MB 5,1. True, you can remedy this by searching Intel for older 'non-metal' versions, but at some point you will be induced to give up and try go back to Catalina with Dosdude1's Post Install Patch instead.
So, you will also only have to use 'non-metal' programmes, but at least, after you have made some special optimisations, the Mac will allow you to work quite comfortably.
 
OKonnel said:
Thank you for the report. However, the fact that the installation was successful does not mean that the Mac will work well and give satisfaction in use.
(...)

Slowness and jerks aside, all 'Metal' programmes, such as iMovie, PowerPoint, etc., doesn’t will work in the MB 5,1.
Click to expand...

My MacMini 3,1 is just a TimeMachine slave for all the Macs in my home. So for me it works very satisfactory.

The MacBook 5,1 is seldomly in use. So my post was more or less only a proof of concept for others who might be interested.

For "real" work I choose between a MacPro 6,1 (via OCLP on Sequoia) or my MacBookPro 2020 M1.
 
  • Like
Reactions: OKonnel
Riot Nrrrd said:
What happens if you run softwareupdate from the command line in Terminal.app?
Click to expand...
I get a lot of verbiage....what command arguments do I need to add?

P.S. I have added an NVMe drive and PCIe adapter to this old 3,1. Moving along! :)
 
I think, I had been able to use Brave after updating to 14.7.5/OCLP2.3.2. But now the app crashes every single time I start it on my MBA6,2...
 
Last edited:
makra said:
I think, I had been able to use Brave after updating to 14.7.5/OCLP2.3.2. But now the app crashes every single time I start it on my MBA6,2...
Click to expand...
Resolved: Other browsers behaved only slightly better, further glitches (e. g. missing menu elements) began. I tried to reapply root patches, which didn't work: "SystemVersion.plist build version mismatch: found 15.4.1 (24E263), expected 14.7.5 (23H527)" Apparently, a Sequoia update had started unintentionally in the background. So I gave in and updated to Sequioa properly. Now everything works fine again.
 
  • Like
Reactions: Ausdauersportler and Riot Nrrrd
makra said:
Resolved: Other browsers behaved only slightly better, further glitches (e. g. missing menu elements) began. I tried to reapply root patches, which didn't work: "SystemVersion.plist build version mismatch: found 15.4.1 (24E263), expected 14.7.5 (23H527)" Apparently, a Sequoia update had started unintentionally in the background. So I gave in and updated to Sequioa properly. Now everything works fine again.
Click to expand...
I’ve had that same problem twice. There is a program (a Mac binary) on the OCLP Discord server’s Support channel called “PurgePendingUpdate” that you can run which will remove the APFS snapshot containing the offending downloaded OS update. I had to run it a couple of times for it to ‘take’. But once that was done, I was able to run the root patches.

Obviously you solved this in a different way :) I’m still a bit hesitant to move from my (relatively stable) Sonoma installs to Sequoia …
 
Riot Nrrrd said:
I’ve had that same problem twice. There is a program (a Mac binary) on the OCLP Discord server’s Support channel called “PurgePendingUpdate” that you can run which will remove the APFS snapshot containing the offending downloaded OS update. I had to run it a couple of times for it to ‘take’. But once that was done, I was able to run the root patches.

Obviously you solved this in a different way :) I’m still a bit hesitant to move from my (relatively stable) Sonoma installs to Sequoia …
Click to expand...
Usually in April/May my favorite soccer team gets unstable whereas current macOS versions don't surprise the OCLP team quite as much as in February/March... ;)
 
  • Haha
Reactions: winxmac and Riot Nrrrd
ksec said:
I guess Safari is still having problems. Given on Sequoia, MacBook Pro early 2015 ( I guess that is non -metal ) doesn't work on Cloudflare site protection captcha . ( Which is a lot of site ) I am wondering if anyone could test it out on Sonoma?

Linux Hardware Reviews & Performance Benchmarks, Open-Source News - Phoronix

www.phoronix.com www.phoronix.com

and

Grok.com both uses it.
Click to expand...
From what I've seen there was some version of Safari that broke webgl and the cloudflare captcha. If you upgrade to that version or later on Ventura, Sonoma, or Sequoia it will be broken. I think it was sometime around the 18.0 or 18.1 timeframe. I believe the exact version was posted on these forums somewhere, but I forgot what it was.

If you want to use safari you either have to stick with the working version and not upgrade past it, or you can run an older Tech Preview version of Safari. That's what I do. I posted about it earlier in this thread.

Maybe we'll get lucky at some point and it will start working again in a future update, but at this point I think it's low probability. So we either have to stick with older versions, use and alternate browser, or use the older tech preview.
 
  • Like
Reactions: ksec
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back