Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

macOS 15 Sequoia 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.
coasterOneEightThree said:
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!
Click to expand...
Hello, same here I get the same problem since updating to 15.2beta4 and 15.2RC. I didn't find any solution. Just to let you know I have 10.3.6 partition and connecting to it, touchID worked fine. First I thought it was dead ! but it is not. Before that on 15.1.1 I had very strange behavior, no more iMessage and FaceTime impossible to connect to the iCloud account, at the same time HandOff didn't work and with Mail I had to restart the computer to open the window !!!! anymore. By deleting some Préférence files (.plist) it's working again. Then I thought that upgrading to 15.2beta4 will resolve the situation of TouchId, but no. Will wait for the final release ! JC
 
  • Like
Reactions: coasterOneEightThree
Today's 2.2.0n seems very promising. At least all issues I have reported here appears to have been fixed.
Safari favorites f.ex. Hoping it will stay stable. This is 15.1.1 on a rMBP 10,1 and a MBA 7,2. So far so good.
Fab work by devs as always!
 
  • Like
Reactions: coasterOneEightThree and MacRumors3590
Hi:
I read through a fair bit of this thread but ... dizzy with uncertainty.

I am running Mojave on an Intel i7 2.3GHz Mini with 16GB of RAM. Is it too late to update to just, say Catalina, so as not to bog down my system? Some programs are no longer supported without a more recent OS. I'm trying to hold off on a new machine for 6 months.

Or, do I need to update to Sequoia? I'm guessing that Sequoia is going to slow the machine down and create a new array of problems. A nudge toward a six month solution will be helpful.
 
I OTA installed today's RC2 on MacMini 2014 running RC1 but root patching is failing with the following: Installing Metallib: 24C100— Error Metallib installation failed. However I do see it at Github so can I dl from there and where to put it so OCLP finds it?
 
Last edited:
MacQurious said:
Hi:
I read through a fair bit of this thread but ... dizzy with uncertainty.

I am running Mojave on an Intel i7 2.3GHz Mini with 16GB of RAM. Is it too late to update to just, say Catalina, so as not to bog down my system? Some programs are no longer supported without a more recent OS. I'm trying to hold off on a new machine for 6 months.

Or, do I need to update to Sequoia? I'm guessing that Sequoia is going to slow the machine down and create a new array of problems. A nudge toward a six month solution will be helpful.
Click to expand...
I would go for Monterey.
 
  • Like
Reactions: MacQurious
nekton1 said:
I OTA installed today's RC2 on MacMini 2014 running RC1 but root patching is failing with the following: Installing Metallib: 24C100— Error Metallib installation failed. However I do see it at Github so can I dl from there and where to out it so OCLP finds it?
Click to expand...
Updated to latest nightly but still getting Metallib: 24C100 error
 
jotzet said:
Wow 🤩 - see the changelog for 2.2.0

A lot of non-metal improvements!

github.com

OpenCore-Legacy-Patcher/CHANGELOG.md at main · dortania/OpenCore-Legacy-Patcher

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

Sounds like they have possibly nailed down the iCloud sync issues that occur when connected over WiFi. Messages in iCloud, Safari Bookmarks, Safari open tabs, pedestrian Photos sync, etc.
 
  • Like
Reactions: Steve Gosselin, RogueB, luckyduke23 and 3 others
dumastudetto said:
Sounds like they have possibly nailed down the iCloud sync issues that occur when connected over WiFi. Messages in iCloud, Safari Bookmarks, Safari open tabs, pedestrian Photos sync, etc.
Click to expand...
Yes but no final 2.2.0 public release and still getting Installing Metallib: 24C100 error
 
Just FYI and to save you some time:

tried to update to the build just being released via OTA 15.2. Got stuck in the boot loop. Even in safe mode I can get past the language selection screen. It must’ve been at least 20 reboots.

In the verbose mode I can see the error message failed to bootstrap

Edit: After taking the hiccyhicup bumpy road i have made it to 24C100 eventually. A few more hardresets, PRAM resets and safe modes did it the end.

Edit 2: Patching/Downloading metallibs not possible once internet connection is active. Seemingly the libraries are not available yet. Solution: Patch without internet connection instead and update them later on.

Screenshot 2024-12-10 at 17.22.32.png
 
Last edited:
  • Like
Reactions: macpro_mid2014
amaze1499 said:
Just FYI and to save you some time:

tried to update to the build just being released via OTA 15.2. Got stuck in the boot loop. Even in safe mode I can get past the language selection screen. It must’ve been at least 20 reboots.

In the verbose mode I can see the error message failed to bootstrap
Click to expand...
"Stuck on boot after root patching
Boot into recovery by pressing space when your disk is selected on the OCLP bootpicker (if you have it hidden, hold ESC while starting up)

  • Note: If your disk name is something else than "Macintosh HD", make sure to change the path accordingly. You can figure out your disk name by typing ls /Volumes.
Go into terminal and first mount the disk by typing

mount -uw "/Volumes/Macintosh HD"
Then revert the snapshot

bless --mount "/Volumes/Macintosh HD" --bootefi --last-sealed-snapshot
Now we're going to clean the /Library/Extensions folder from offending kexts while keeping needed ones.

Run the following and make sure to type it carefully

WARNING
If you have FileVault 2 enabled, you will need to mount the Data volume first. This can be done in Disk Utility by locating your macOS volume name, selecting its Data volume, and selecting the Mount option in the toolbar.
cd "/Volumes/Macintosh HD - Data/Library/Extensions" && ls | grep -v "HighPoint*\|SoftRAID*" | xargs rm -rf
Then restart and now your system should be restored to the unpatched snapshot and should be able to boot again."
 
  • Like
Reactions: ronton3, houser, RogueB and 1 other person
Hello to all,

Just a quick note.

iMac 13,2 (metal capable)

I was able to circumvent the “MetalLibrary download error” by mounting the EFIs from two drives (internal and external) both running Sequoia 15.2, and then copied the MetalLibrary from the EFI drive which had OCLP 2.2n from November 29th, to the EFI on internal drive where the “Failed to download” message was evident.

I then turned off WiFi and Ethernet, booted to the 15.2 (built 24C100) and initiated patching; without internet connection the patching completed without problems.

Addendum for iMac 13,2: Continuity, Air Drop, Handoff and iPhone camera functions work prfectly.


MacBook Pro 5,2. (2009) non-metal would not boot, ending with what appeared to be Kernel panic; work in
progress.

Addendum for MacBook Pro 5,2:

Booted into 15.1.1 volume (a volume separate from 15.2 installation, but same partition) following the Kernel panic noted above. Mounted EFI of the "panicked volume", removed EFI volume contents, downloaded latest OCLP 2.2, rebuild and installed OCLP onto the "failed" volume. Also, downloaded latest KDK from Apple, and manually installed it. Then, shut down MacBook Pro 5,2 and reset SMC (needed to do so anyway, since after each update it is the only way to get keyboard backlight to work). Cold booted into latest Sequoia 15.2 and reached desktop without any Kernel panics. Applied patches without issues and on reboot had full graphics acceleration.
All iWork applications, Apple store app., Apple TV and Safari function without any significant glitches. Personal HotSpot works as well. Continuity features are not functional, nor is airdrop, but that's minor issue; I'll try with low energy Bluetooth dongle.

Truly superb work by developers.

MacBook Pro 5,2.png


iMac 13,2.png
 
Last edited:
  • Like
Reactions: hvds and amaze1499
RogueB said:
Hello to all,

Just a quick note.

iMac 13,2 (metal capable)

I was able to circumvent the “MetalLibrary download error” by mounting the EFIs from two drives (internal and external) both running Sequoia 15.2. I copied the MetalLibrary from the EFI drive which had OCLP 2.2n from November 29th to the EFI on internal drive where the “Failed to download” message was evident.

I then turned off WiFi and Ethernet, booted to the 15.2 (built 24C100) and initiated patching; without internet connection the patching completed without problems.


MacBook Pro 5,2. (2009) non metal wouldn’t not boot, ending with what appeared to be Kernel panic; work in progress.

Hope this information may be of help.

View attachment 2460764
Click to expand...

An easier way is is pick opencore in applications right click show original go into Metallib folder and rename the last 15.2 folder you can download to 15.2-24C100 then run root patches use at your own risk.
 
  • Like
Reactions: RogueB, macpro_mid2014 and cab_007
OCLP 2.2.0n from today quite good on MP5,1 with X5690 Xeon 3,46 - 15.1.1 and also 15.2 24C100 so far - great work as always 🫶
 
Last edited:
TOM1211 said:
An easier way is is pick opencore in applications right click show original go into Metallib folder and rename the last 15.2 folder you can download to 15.2-24C100 then run root patches use at your own risk.
Click to expand...
Edit: Confirmed. It lets you proceed with patching. However the libs should be updated manually later on when they are available.

github.com

Releases · dortania/MetallibSupportPkg

Metal Library Patching Utilities. Contribute to dortania/MetallibSupportPkg development by creating an account on GitHub.
github.com github.com
 
Last edited:
  • Like
Reactions: RogueB, macpro_mid2014 and houser
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