macOS 15 Sequoia on Unsupported Macs Thread

[NordicHoffer]

The slowdown in the progress bar at bootup is probably normal. Happens on my machine, 2012 non-retina, as well.

I don't have issues with the long delayed bouncing, but it sounds like you could still be experiencing the general slowness that occurs from indexing and other processes that run after a fresh update/install. If you don't have 16GB of RAM and an SSD instead of a spinning disk, that will contribute to slowness with the newer OSes as well.

If you haven't reset NVRAM and the SMC you might want to do that also. Old firmware could be an issue as well if the machine never ran the last Apple supported version of MacOS.

Thanks for the suggestion. I had reset the SMC and NVRAM, but that didn’t help either. The machine has 16GB of RAM and an SSD. Spotlight is not indexing as far as I can tell.

 

[Kevo]

Thanks for the suggestion. I had reset the SMC and NVRAM, but that didn’t help either. The machine has 16GB of RAM and an SSD. Spotlight is not indexing as far as I can tell.

On my machine the general sluggishness lasted a handful of hours or so. My timemachine backups were slower than usual for a couple of days as well (I only have it run at night). Other than that it's not much difference from Sonoma. Runs quite well. Only problems I've noticed so far is levels in Preview doesn't work and Messages gets sluggish it you type a lot of text in a single message.

 

[MacinMan]

Successfully Installed Sequoia on an MBP 11,1 and I may have done it different than most.

I had Big Sur on the machine, built and installed Open Core and install Monterey, as it doesn't require any patches on this machine. Then upgraded to Sequoia through software update as I would on a supported Mac (delta update used) than ran the root patches, and everything looks good. So, no USB installer was required here.

 

[Ghosthengst77]

MacBook Pro 14,3 dosen't work perfect with the latest OCLP 2.1.1 because the T1 Chip don't work and the KDK for 15.2 beta 2 still missing. Maybe that's the Problem why they don't work with the Password or T1. Or is it an another issue!?

 

[josehill]

Hi, it seems that localspeechrecognition is broken on some unsupported Macs, such as the 2012 MacBook Pro with older CPUs.
Does localspeechrecognition work for you?

I haven't looked up the symptoms that others have encountered, but yes, speech recognition is not working correctly on my MBP9,2. For example, if I try to use dictation in TextEdit.app, it will enter the word "pet" repeatedly, regardless of what I say.

Since I don't actually use the feature, I have disabled it.

 

[olad]

He is part of the OCLP team but not as publicly active. Reason why he started the thread is not for honours but to have someone who is in the team to make the first post with factual information and have the team being able to edit it as needed. The main post has been edited on Oct 1.

The issues are still ongoing, unfortunately.

My bad. Apologies to @flagers.

 

[PropClear]

OCLP 2.1.2 final is released - and fixed my mentioned bugs - great work as always 😍

 

[MacRumors3590]

OCLP 2.1.2 final is released - seems to fix my mentioned bugs - great work as always 😍

Great!!

 

[trifero]

I updated OCLP to 2.1.1 and Sequoia to 15.1 on my 2016 MBP 13" 4-port thunderbolt 3, and in screen settings it gives me the flag on 1440 x 900 (default) while in information it gives me 2560 x 1600 which is the native resolution of my retina display, if I try to move the flag in screen settings to 2560 x 1600 everything becomes small, icons, text, etc. Does this happen to others too?

That resolution is not intended to work with native macOS, though it appears in Windows native if installed.

 

[ronton3]

I have a new, to me, late 2015 27 Imac. I wanted to start over and put everything on an external drive, for one thing I tired of constantly seeing the top message appear. I searched the Imac and deleted the dortania files, I am now on the latest Monterey. I have reset NVRAM and SMC.

I downloaded the latest OCLP from 11 hours ago, and again up popped the annoying message about booted 2.1.0, installed 2.1.2. I have not installed 2.1.2. or any other OCLP I just downloaded and opened 2.1.2 then the top message appeared again. On this clean install of Monterey I thought I had erased all previous traces of OCLP so I could start over. What else do I need to do to stop the top message from appearing. Thanks for the help.

 

[mwidjaya]

What else do I need to do to stop the top message from appearing. Thanks for the help.

Download the uninstaller package on the release page.

Releases · dortania/OpenCore-Legacy-Patcher

Experience macOS just like before. Contribute to dortania/OpenCore-Legacy-Patcher development by creating an account on GitHub.

github.com

 

[ronton3]

Download the uninstaller package on the release page.

Releases · dortania/OpenCore-Legacy-Patcher

Experience macOS just like before. Contribute to dortania/OpenCore-Legacy-Patcher development by creating an account on GitHub.

github.com

Thank you so much, it worked.

 

[grzegorz9141]

OCLP 2.1.0/1/2, iMac 11.3 with metal Nvidia, macOS 15.2.b2 safari, appstore and appletv crashes, with macOS15.1 all working perfect.

 

[kral84]

The slowdown in the progress bar at bootup is probably normal. Happens on my machine, 2012 non-retina, as well.

I don't have issues with the long delayed bouncing, but it sounds like you could still be experiencing the general slowness that occurs from indexing and other processes that run after a fresh update/install. If you don't have 16GB of RAM and an SSD instead of a spinning disk, that will contribute to slowness with the newer OSes as well.

If you haven't reset NVRAM and the SMC you might want to do that also. Old firmware could be an issue as well if the machine never ran the last Apple supported version of MacOS.

same problem on imac 12,2 ... have you try apfs trim disable and enable to test it? ... i try wekend new format and resinstall apfs ssd..

 

[Sven G]

Does anyone with FileVault enabled have the glitch that - seemingly randomly - the boot process requires the password to be entered two times…? Initially, as it should be with FileVault enabled; but also, frequently, again before login (which should not happen)…

 

[Sven G]

Another glitch that could perhaps (?) be related with OCLP, in Homebrew, with brew doctor:

Doctor: "Warning: No Cask quarantine support available: unknown reason" · Homebrew · Discussion #5482

Output of brew config HOMEBREW_VERSION: 4.3.9 ORIGIN: https://github.com/Homebrew/brew HEAD: 1c98a33a376e5b35ebc801d0f7d6ba7b9eb118ac Last commit: 3 days ago Core tap JSON: 10 Jul 16:17 UTC Core ca...

github.com

 

[buch2]

That resolution is not intended to work with native macOS, though it appears in Windows native if installed.

you are right, I got confused, in fact in my other laptop (Zenbook 14 Oled touch) the resolution 2880 x 1800 works natively

 

[coasterOneEightThree]

Does anyone already have experience with a MacPro3.1, OCLP and Sequoia? As is known, this configuration can currently only be operated in single socket mode, i.e. with 4 cores. OCLP has an option to set this accordingly so that this Mac does not crash at startup.

I have already tried this on my MacPro3.1, which is still running Sonoma. The general performance suffers significantly, you can already notice the difference in the Finder.

I wonder if that would be better in Sequoia ...

Thanks in advance for any helpful feedback!

 

[ronton3]

Using OI recovery I wiped every thing, installed Monterey, used Time Machine, uninstalled
OCLP to get rid of a repeated annoyance, (thanks Mwidjaya), installed 2.1.2, OTA installed 15.2 from software update, patched. Everything seems fine.

 

[MacinMan]

Another glitch that could perhaps (?) be related with OCLP, in Homebrew, with brew doctor:

Warning: No Cask quarantine support available: unknown reason​

Doctor: "Warning: No Cask quarantine support available: unknown reason" · Homebrew · Discussion #5482

Output of brew config HOMEBREW_VERSION: 4.3.9 ORIGIN: https://github.com/Homebrew/brew HEAD: 1c98a33a376e5b35ebc801d0f7d6ba7b9eb118ac Last commit: 3 days ago Core tap JSON: 10 Jul 16:17 UTC Core ca...

github.com

After reading through that thread, it seems like it's not OpenCore specific even though there are OpenCore users there. Someone on a Native M3 Machine reported the same issue.

 

[peppolone]

Since I installed Sequoia, starting with version 15, I've encountered a minor bug that only happens in Safari. Randomly, the menu becomes blurred. However, if I switch to another app and come back to Safari, or if I close and reopen Safari, the issue resolves itself. Has anyone else experienced this?

 

[thegdn]

Groovy
Dev's are great!
mbp 11,1 currently updating to same
🤞

 

[roronl]

Hello nice people,
Please help me with this almost off-topic question;

Tomorrow we will probably receive a new M4 imac at home as a new companion of the existing Macbook Pro 2015 running on OCLP and MacOS 15.2.

Can I safely use the Migration Assistant-app on the new iMac to switch from this OCLP installed MacBook to M4?
Or will I definitely cause problems with this?

Many thanks for the help from Amsterdam.

 

[Sevenfeet]

Does anyone already have experience with a MacPro3.1, OCLP and Sequoia? As is known, this configuration can currently only be operated in single socket mode, i.e. with 4 cores. OCLP has an option to set this accordingly so that this Mac does not crash at startup.

I have already tried this on my MacPro3.1, which is still running Sonoma. The general performance suffers significantly, you can already notice the difference in the Finder.

I wonder if that would be better in Sequoia ...

Thanks in advance for any helpful feedback!

Ive seen this too where if my machine is limited to four cores instead of eight, the performance drops significantly, even for just normal housekeeping things. As a result, my Mac 3,1 is the only aging Mac in the house still running Sonoma instead of Sequoia.

 

[OKonnel]

Does anyone with FileVault enabled have the glitch that - seemingly randomly - the boot process requires the password to be entered two times…? Initially, as it should be with FileVault enabled; but also, frequently, again before login (which should not happen)…

Hi @Sven G ! On my iMac (see in the signature) I have enabled FileVault from Catalina all the way to Sequoia and this is the first time I've heard of this oddity.
Usually, with past Mac OS Xs, all you had to do was delete the Preferences files.
You can try searching the System (e.g., in the root’s Library, in the $Home’s Library and in /etc/) and see if you notice any files that you can remove so that the System, then, recreates them the right way.
I know it's not simple, but as a simple Nerd that's what I would try before giving up and reinstalling everything; of course first normally, i.e. rewriting just macOS and then reinstalling everything from scratch if the problem doesn't resolve.