macOS 15 Sequoia on Unsupported Macs Thread

[MacinMan]

I’ve had no problems running Onyx in fact it got rid of the grey screen we used you get before the desktop background loads in . Using safari 26.1 or betas I’ve found OSXDaily website crashes it every time (mind you I only went there from a google link) I’d say it does about 80% of things without issue . (Could be plugin issues mind you.)

Thanks, which automations did you run in Onyx, I don't need everything. However, I am curious which tolls you used so I can do the specifics that might effect slow login. For the most part login isn't too bad here. Will test OSXDaily here to see if I get a crash.

 

[MacinMan]

@TOM1211 No issues here, with your reported site. I got a momentary beac

hball, but then things resumed without issue.

 

[MacinMan]

I just reinstalled Homebrew after not using it for about a year, or so. When running "brew doctor" they've added this new warning.

tron@iFrog5K ~ % brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: You have booted macOS using OpenCore Legacy Patcher.
We do not provide support for this configuration.

This is a Tier 2 configuration:
https://docs.brew.sh/Support-Tiers#tier-2
You can report Tier 2 unrelated issues to Homebrew/* repositories!
Read the above document before opening any issues or PRs.

tron@iFrog5K ~ %

I read the site given in the warning for details, and was curious if anyone has run into any issues separate from a fully supported install? It never used to warn about open core when I used to use it a while back.

I mainly use Homebrew for command line tools like TCL, ffmpeg, etc, and have never had issues with those, on any install. I haven't seen this mentioned on the threads either, so I was curious about it, and how long it's been this way.

 

[Kevo]

@TOM1211 No issues here, with your reported site.

I think it just affects the machines with the older pre AVX2 CPUs. That site and a handful of others I've run across crash Safari for me as well.

Homebrew has been fine for me, but there are some packages that also trip up on the old CPU issue also. I've run into a couple of those. For the most part it doesn't cause too much grief, but I have several development workarounds now that are pushing me toward a new machine. I'm trying to stubbornly hold out until the next MBP redesign if I can. I figure I can either get the redesigned machine if it's compelling or get a decent deal on the old design if it's not.

 

[MacinMan]

I think it just affects the machines with the older pre AVX2 CPUs. That site and a handful of others I've run across crash Safari for me as well.

Homebrew has been fine for me, but there are some packages that also trip up on the old CPU issue also. I've run into a couple of those. For the most part it doesn't cause too much grief, but I have several development workarounds now that are pushing me toward a new machine. I'm trying to stubbornly hold out until the next MBP redesign if I can. I figure I can either get the redesigned machine if it's compelling or get a decent deal on the old design if it's not.

Homebrew doesn't make sense to me as to why it would care about OpenCore, or not. It's open source and it's a package manager primarily for installing stuff you'd find in Linux, or FreeBSD. If it was mac native stuff, then I could understand better. Just for installing command line tools, that are mostly open source anyway, it just doesn't make sense as to why they'd care. It never used to. Like I said, the message I pasted from the terminal is recent. The main issue(s) I've had when dealing with installing this type of software is Apple being good at not putting things in the usual place they're expected, or using different versions, or different tools / libraries, et, than what's expected. Homebrew makes it somewhat easier to deal with.

 

[Kevo]

Homebrew doesn't make sense to me as to why it would care about OpenCore, or not. It's open source and it's a package manager primarily for installing stuff you'd find in Linux, or FreeBSD.

If you had to respond to all the people that use it and want help then you might care more. Supporting software, open source or not, is quite a challenge at times. Having to support software that is running on unsupported software itself is likely more work than they want to commit to.

 

[Bigwaff]

Homebrew doesn't make sense to me as to why it would care about OpenCore, or not. It's open source and it's a package manager primarily for installing stuff you'd find in Linux, or FreeBSD. If it was mac native stuff, then I could understand better. Just for installing command line tools, that are mostly open source anyway, it just doesn't make sense as to why they'd care.

Some Homebrew formulae are built/compiled during install and may fail to do so on unsupported hardware for various reasons. Homebrew team doesn’t want to waste time and energy to chase down these issues. That’s why they care.

 

[MacinMan]

@Kevo and @Bigwaff I get the point, and I also find it odd that certain Linux configurations are also mentioned on the same page as the macOS info, and configurations considered Tier 2. I understand why they would care. It just didn't make sense at first why the boot loader would make a difference to matter. Most of what breaks in packages is OS level stuff like libraries, locations of heads, does a certain package even exist on macOS vs Linux, things like that. Then there are kernel level stuff too, but there again, whenever I'd had issues, it's OS level stuff, not the boot loader. Granted, I, as I have said, haven't used Homebrew in quite a while, so a lot has changed. I've also never maintained a package for it either.

Also, what I've done, is if I only need a couple packages, I just download the source and compile by hand, hence why I keep Xcode around for the command line tools, not to write Mac native software. When I reinstalled Homebrew today, wanted to see what's changed, and if it would be happy with my Xcode install, etc.

But yes, I understand the points made.

 

[borp99]

I just upgraded my cMP5,1 to 15.7.2 and now can't seem to do a 'live mount' anymore - which I do to change my generic system folder icon to a far less bright blue version (by swapping out the Assets.car file in the '/S/L/PrivateFrameworks/IconFoundation.framework/Versions/A/Resources' folder.

The string I've previously used successfully, incl. 15.7.0, was 'sudo mount -o nobrowse -t apfs /dev/disk2s2 /Users/xxxxxx/livemount', obviously with my correct user name and mount partition base numbers inserted

Can anyone suggest an altered Terminal string to make 'live mount' work for me under 15.7.2?

[If necessary, I can book into Recovery mode and swap over the icon file that way but it's been so much easier doing this with 'live mount' and then creating a new system snapshot point afterwards]

 

[Bigwaff]

I get the point, and I also find it odd that certain Linux configurations are also mentioned on the same page as the macOS info, and configurations considered Tier 2

Can you share link to the page you are referring to? I honestly don’t know the context here. Thanks.

 

[MacinMan]

Can you share link to the page you are referring to? I honestly don’t know the context here. Thanks.

@Bigwaff the link is here: https://docs.brew.sh/Support-Tiers#tier-2 it was part of the message I copied and pasted in the original post.

 

[Bigwaff]

@Bigwaff the link is here: https://docs.brew.sh/Support-Tiers#tier-2 it was part of the message I copied and pasted in the original post.

Thank you. Hadn’t read this before. Very specific and very interesting.

 

[MacinMan]

Thank you. Hadn’t read this before. Very specific and very interesting.

You're welcome. Usually when I comment on something here, it's usually because it's because there is a typical response to specific things, and when it's different, it doesn't always make sense. Also to remind people in general here I treat macOS as a proprietary Unix install. What I mean by that is I typically use it like I would Linux, or a FreeBSD install, except for those elements that requirement me to treat it differently in specific ways.

An example of this would be, instead of using Open Core Legacy Patcher, I'd take Monterey, as an example, and have the base system with all the supported drivers and encryption, e.g. sealed snapshots, and SIP, and take it and update the libraries with the open source ones, the way one would with any Nix based OS. Then in the case of programs, use the mac native ones I can, but then replace the others with open source cross platform alternatives / versions, so basically doing a custom OS. Base install for Apple specific features, and open source for everything else. I never really followed up with this though, because I don't think you can modify macOS like this, and have it reliably work. However, if I had the option, and the ability to do this, it would be my preferred method. That way I'd have the hardware fully supported, and then the main work would be keeping software up to date in terms of user land stuff.

 

[MacMorrison]

I just got a warning from OCLP:

"OpenCore Legacy Patcher has detected that a macOS update is being downloaded: 26.1 (25b78)"

It then offered to run post-install patches after the update. I declined the offer by clicking on Cancel.

I think it's a false alarm - clearly, macOS got some kind of signal that it was downloading macOS Tahoe's update (26.1) in the background (because I was checking Software Update in System Settings), which triggered the OCLP 2.4.1 notification.

 

[MacinMan]

I just got a warning from OCLP:

"OpenCore Legacy Patcher has detected that a macOS update is being downloaded: 26.1 (25b78)"

It then offered to run post-install patches after the update. I declined the offer by clicking on Cancel.

I think it's a false alarm - clearly, macOS got some kind of signal that it was downloading macOS Tahoe's update (26.1) in the background (because I was checking Software Update in System Settings), which triggered the OCLP 2.4.1 notification.

I'd still check to make sure, because I've never gotten a notification from the patcher from simply checking for updates. When I install other updates such as Safari, I ALWAYS make sure to uncheck the Tahoe update in the list. Never had an issue with it, so you might end up with an issue.

 

[phuklok1]

Hi All,
I am running Sequoia on a late 2013 I7 16GB Macbook Pro. Overall, it quite works well (THANK YOU OCLP!), but has anyone noticed that when the system is resumed from sleep, kernel_task goes from normally taking about 1-3% CPU usage to a persistent 10-14%? This was not the case in Sonoma. Everything else seems to work correctly after resume, but the only thing that will clear the high kernel_task usage is an OS restart.

I've been hoping for an update that might resolve this, so as a workaround I just go through a full shutdown/startup each time, but I do really miss the quick wake from sleep.

 

[ronton3]

I just got a warning from OCLP:

"OpenCore Legacy Patcher has detected that a macOS update is being downloaded: 26.1 (25b78)"

It then offered to run post-install patches after the update. I declined the offer by clicking on Cancel.

I think it's a false alarm - clearly, macOS got some kind of signal that it was downloading macOS Tahoe's update (26.1) in the background (because I was checking Software Update in System Settings), which triggered the OCLP 2.4.1 notification.

OCLP downloads the KDK matching the update, that is what it is asking to do. Say yes.

 

[PeterHolbrook]

I just got a warning from OCLP:

"OpenCore Legacy Patcher has detected that a macOS update is being downloaded: 26.1 (25b78)"

It then offered to run post-install patches after the update. I declined the offer by clicking on Cancel.

I think it's a false alarm - clearly, macOS got some kind of signal that it was downloading macOS Tahoe's update (26.1) in the background (because I was checking Software Update in System Settings), which triggered the OCLP 2.4.1 notification.

The same exact thing happened to me, although I let OCLP 2.4.1 continue downloading the new KDK. No worries. Tahoe has NOT been installed, God forbid!

 

[alphascorp]

I just upgraded my cMP5,1 to 15.7.2 and now can't seem to do a 'live mount' anymore - which I do to change my generic system folder icon to a far less bright blue version (by swapping out the Assets.car file in the '/S/L/PrivateFrameworks/IconFoundation.framework/Versions/A/Resources' folder.

The string I've previously used successfully, incl. 15.7.0, was 'sudo mount -o nobrowse -t apfs /dev/disk2s2 /Users/xxxxxx/livemount', obviously with my correct user name and mount partition base numbers inserted

Can anyone suggest an altered Terminal string to make 'live mount' work for me under 15.7.2?

[If necessary, I can book into Recovery mode and swap over the icon file that way but it's been so much easier doing this with 'live mount' and then creating a new system snapshot point afterwards]

Hi @borp99
The command “sudo mount -o nobrowse -t apfs /dev/disk2s2 /Users/xxxxxx/livemount” that you are using seems correct.

I also use this command so that I can manually change the trash can icons (in /S/L/CoreServices/Dock.app/ Contents/Resources) and disks icons (in /S/L/Extensions/IOStorageFamily.kext/Contents/Resources) and (in /S/L/Extensions/IOSCSIArchitectureModelFamily.kext/Contents/Resources).

SIP and SSV must be disabled. To do this, I modify the config.plist NVRAM > Add > 7C436110-AB2A-4BBB-A880-FE41995C9F82 > csr-active-config > fwgAAA== (instead of AwgAAA==).

Also check the permissions for your “/Users/xxxxxx/livemount” folder. I've had cases where I created this folder with the command “mkdir /Users/xxxxxx/livemount” but mounting the snapshot didn't work, so I deleted it and recreated the “livemount” folder directly with Finder.

That said, I haven't updated to 15.7.2 yet, but I used this command last week on 15.7.1 and it worked fine.

 

[MacinMan]

OCLP downloads the KDK matching the update, that is what it is asking to do. Say yes.

Which KDK is it downloading? If I go back and reapply root patches, I could trigger it as well, but nothing newer for Sequoia shows up on the Dortania Github mirror over 15.6 when I check for new releases.

 

[ronton3]

15.7.3 OTW, OTA.

 

[MacinMan]

When installing formulas from Homebrew, I've noticed they've been identified as Sonoma, vs Sequoia, even with a clean install of Homebrew on Sequoia. Is this normal, or is something not as it should be? When I used Homebrew in the past the formula identifier usually matched the current macOS version.

 

[MacinMan]

I've really just got a big kick out Sequoia performance on this iMac, 17,1. After doing some reading on Reddit, I have turned off a few things in the OS, I don't use, and 1 thing I didn't realize made a difference, and things are almost instant now, and login is a lot faster too on reboot.

What I disabled was:
Siri (i don't use Siri on the Mac)
Animate opening Applications (didn't think this would help, but apps open faster)
Reduce Motion (even removing the little animations, makes things run faster, I was so used to it, that I was surprised when I saw the difference.)
Use iPhone Widgets (up there with I don't use desktop widgets, and I just use the phone widgets on the phone.)
Show Widgets on Desktop and Stage Manager (I don't use desktop widgets), I keep them in the notification center where they've always been prior to Sonoma.
I tried Reduce transparency, but I didn't make a difference for me in performance, and it makes the dock look tacky. So, I left that on.

Now, I'm going to investigate Telemetry. Not because I have issues sending data that can help improve things, but to see if it makes a difference with performance.

Here is the Reddit link I've been reading, and got these suggestions from:

https://www.reddit.com/r/OpenCoreLegacyPatcher/comments/1jc4wax/some_tips_and_learnings_from_a_guy_whos_set_up_20

 

[alphascorp]

I've really just got a big kick out Sequoia performance on this iMac, 17,1. After doing some reading on Reddit, I have turned off a few things in the OS, I don't use, and 1 thing I didn't realize made a difference, and things are almost instant now, and login is a lot faster too on reboot.

What I disabled was:
Siri (i don't use Siri on the Mac)
Animate opening Applications (didn't think this would help, but apps open faster)
Reduce Motion (even removing the little animations, makes things run faster, I was so used to it, that I was surprised when I saw the difference.)
Use iPhone Widgets (up there with I don't use desktop widgets, and I just use the phone widgets on the phone.)
Show Widgets on Desktop and Stage Manager (I don't use desktop widgets), I keep them in the notification center where they've always been prior to Sonoma.
I tried Reduce transparency, but I didn't make a difference for me in performance, and it makes the dock look tacky. So, I left that on.

Now, I'm going to investigate Telemetry. Not because I have issues sending data that can help improve things, but to see if it makes a difference with performance.

Here is the Reddit link I've been reading, and got these suggestions from:

https://www.reddit.com/r/OpenCoreLegacyPatcher/comments/1jc4wax/some_tips_and_learnings_from_a_guy_whos_set_up_20

Hi @MacinMan

To reduce telemetry and crash reporting, you can execute the following two commands:

sudo defaults write /Library/Preferences/com.apple.SubmitDiagInfo AutoSubmit -bool false

defaults write com.apple.CrashReporter DialogType none

 

[MacinMan]

Hi @MacinMan

To reduce telemetry and crash reporting, you can execute the following two commands:

sudo defaults write /Library/Preferences/com.apple.SubmitDiagInfo AutoSubmit -bool false

defaults write com.apple.CrashReporter DialogType none

Thanks, that really wasn't the type I was thinking of though. I was thinking more of the analytics settings. However, I'm pretty happy with the changes I've made in terms of boosting performance.

You know the term, de-googling android?, I wish there was a way to de-Apple macOS, so it was more of regular unix OS, that just happened to have the mac desktop.