Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
BetaWiki says Release Candidate. Installed and running OK on a supported Mac mini 8,1 2018

I will wait until it goes final and Dortania have had time to test against it and issue a new public release of OCLP before installing it on an unsupported rMBP 10,1 2012. That seems to be the safest workflow, for me anyway.

I always get impatient though...
MBP11,1 (late 2013): just installed the RC OTA, external SSD for now, using OCLP 2.1.2. Behaves well.
 
FYI: Update done to 24C98 via OTA using 2.2.0n. The usual hiccups during installation at least on this machine:

1 kernel panic solved by forced restart, 2 more stalls during early boot, forced restart, installation went through eventually using safe mode. Reapplied patches. First boot with patches no bluetooth available.

Applied a second time, downloaded the metal libs update successfully. Patching itself took unusually long like 10 min ish. Restarted. Lots of processes kept the cpu busy for 45 more min ish. After that all was as expected. Bluetooth came back online.

Safari still doesnt behave with some pages as it's expected to. A few websites simply wont load. However Safari Technology Preview does the job for now. This one feels like a solid release.
 
Last edited:
Just updated my MBP 11,5 (2015) from Sonoma 14.7.1 to Sequoia 15.1.1

I am just getting started updating my MBP 11,5 to Sequoia from Monterey 12.7.6.

Could you please suggest a helpful Youtube or macrumors thread to walk me through the process.

Many thanks!
 
I am just getting started updating my MBP 11,5 to Sequoia from Monterey 12.7.6.

Could you please suggest a helpful Youtube or macrumors thread to walk me through the process.

Many thanks!
What version of OCLP are you currently running? Generally speaking I would recommend updating OCLP to the latest version (if it isn't already). Do this before starting the macOS update.
 
  • Like
Reactions: olad and INK1
While not entirely related to this thread (maybe) , fitted a new battery in my MacBook Pro 2014 (doubt I’ll get 10 years out of a third party one) has fixed my boot log in and immediately shut down issue on Sequoia issue although the old battery reported normal health .
 
Haven’t noticed any slow downs on wi-fi at all (but I don’t have the best broadband either so hasn’t been a issue for me could only dream of 70mb +) but it’s stable for me at my speed. iCloud might not sync bookmarks but iCloud Tabs works perfectly being the latest set of websites I’ve been to so could bookmark it from there also you could use a app like raindrop.io to bookmark and that works almost instantly between iPhone and Mac.
Is Wi-Fi speed a known issue with Sequoia and or OCLP? I have noticed on one machine a lot of variability and not due to network issues. It can go from 400 mbps down to 6 mbps in a few minutes. Only a restart fixes it, temporarily. This is on 15.1.1 and OCLP 2.1.2
I've been experiencing these Wi-Fi degradations since Sonoma. Initially, I thought it was due to the distance between my MBP and the router.
I used Wifi Explorer and noticed that the speed degradation is because the Wifi standard drops from 802.11ac (at 5GHz - 80MHz) to 802.11n (at 2.4GHz - 20MHz). The former speeds were sustained for a while, but then it dropped to the latter and never recovered, unless I boot the MBP.
Since a couple of weeks ago, on the same desk I have my MBP, now I've been using a MacMini running Sequoia natively for more than two weeks and there is no drop in Wifi speeds so far. The Wifi runs at 802.11ac (5GHz - 80MHz) steady.
 
  • Like
Reactions: hvds and TOM1211
FYI: Update done to 24C98 via OTA using 2.2.0n. The usual hiccups during installation at least on this machine:

1 kernel panic solved by forced restart, 2 more stalls during early boot, forced restart, installation went through eventually using safe mode. Reapplied patches. First boot with patches no bluetooth available.

Applied a second time, downloaded the metal libs update successfully. Patching itself took unusually long like 10 min ish. Restarted. Lots of processes kept the cpu busy for 45 more min ish. After that all was as expected. Bluetooth came back online.

Safari still doesnt behave with some pages as it's expected to. A few websites simply wont load. However Safari Technology Preview does the job for now. This one feels like a solid release.
OTA updated MacBook 9,1 (12-inch 2016) running OCLP 2.2.0n with 8 GB RAM to 15.2 RC without issues but required USB-C Ethernet adapter to do final root patch b/c Wi-Fi disabled after install. Seems stable.
 
While not entirely related to this thread (maybe) , fitted a new battery in my MacBook Pro 2014 (doubt I’ll get 10 years out of a third party one) has fixed my boot log in and immediately shut down issue on Sequoia issue although the old battery reported normal health .
I have a MBP 2014 and changed the battery too for the third time, I suggest to read this post :
 
I have a MBP 2014 and changed the battery too for the third time, I suggest to read this post :

interesting I did think a higher voltage at boot was something the original battery could no longer handle why it turns off I currently have no issues at all but in terms of this thread we are a long way from Big Sur on MacBook Pro 2014 as well as third party batteries , third party adapters and nvmes Apple didn’t make them with this in mind and my Nvme is twice as big as the original storage that could be bought for the machine.
 
Please don't look at my signature, this post is about my MacBookPro14,2 with OCLP 2.1.2, which has been having problems with Touch ID since the update to the release candidate macOS 15.2 (24C98). Touch ID is no longer offered to me in the usual situations (installation, unlocking the computer, etc.). The Touch ID & Password system settings can no longer be called up or only appear after a very long time. Then no more fingerprints can be created or previous ones deleted. Resetting Touch ID via the terminal in recovery mode was also unsuccessful, except that fingerprints are no longer stored and new ones can no longer be created. I think I will wait for the official release of macOS 15.2 before I completely reinstall the system.

Has anyone else had this experience? Thanks!
 
Last edited:
Please don't look at my signature, this post is about my MacBookPro14,2 with OCLP 2.1.2, which has been having problems with Touch ID since the update to the release candidate macOS 15.2 (24C98). Touch ID is no longer offered to me in the usual situations (installation, unlocking the computer, etc.). The Touch ID & Password system settings can no longer be called up or only appear after a very long time. Then no more fingerprints can be created or previous ones deleted. Resetting Touch ID via the terminal in recovery mode was also unsuccessful, except that fingerprints are no longer stored and new ones can no longer be created. I think I will wait for the official release of macOS 15.2 before I completely reinstall the system.

Has anyone else had this experience? Thanks!
I've noticed the same problem since the 15.2 beta on my MacBook Pro 14,3 (2017) But not with OCLP 2.1.2 nor with 2.2.0n. I hope that the problem will be solved soon. The function of the maps is also limited and some apps do not respond to the 15.2 RC.
 
Does anyone know if there is any news regarding the AVX2 issue? And anyway, in my opinion, 5.1 reached its end with Monterey.
No AVX2 for the cMP. A couple of projects talked about doing something but technologically I don't see how that could work.

So Yes, Monterey is the end of the line for a stable OS (using OpenCore to boot) on the cMP.

With OCLP you can run up to Sequoia but if your work flow requires software that uses AVX2 it won't work. OCLP root patches the cMP to work around the AVX/AVX2 requirements primarily in the graphics drivers so many users have been successful with Sequoia but ...
 
Talking about batteries… anyone has the glitch that Battery Health is only accessible after searching for it in System Settings (and is displayed in a standalone window), and not in the main Battery pane (as it should be)…? And often, especially after resetting NVRAM/SMC, all the battery entries in the System Settings search field suddenly disappear, and thus also Battery Health isn’t accessible anymore. Probably nothing to worry about: but rather strange (as usual)…

Screenshot 2024-12-09 alle 11.38.59.jpeg


Screenshot 2024-12-09 alle 11.39.22.jpeg
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.