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.
I've tried everything, even reinstalled everything (with a new SSD) same problem... probably due to the patches... or really due to Sequia. As you may have noticed above me, I am not the only one...
 
Last edited:
No, you're probably not the only one, but so far you only hear it from the OCLP corner and that Sequoia is installed on an external SSD,
you don't hear anything from people who have newer iMacs, mine is from 2017.
 
I just upgraded the MacOS on my DG 2015 15-inch MBP to OS 15.3 beta using OCLP 2.2.0. Once I performed the root patches everything came up perfectly. No issues running apps so far. Yes I need to change the name of my hard drive. I will fix this shortly . . . I will take the 14 off.

I also got MacOS 15.3 beta installed on my 2015 11-inch MBA w/8GB RAM with root patches installed. Everything running okay on this laptop as well.

54234540008_f1a85ee6d0_z.jpg
54237523757_d1f5c5a9e7_o.jpg


Awesome work by all involved in the OCLP development, thanks!!!
 
Last edited:
My MBP 15 Mid 2014 is on Sequoia 15.2 now (from Ventura). It's running normally, but most of the times, the external displays get broken during start up. I'd have to reinstall patches (even if they've already been installed and it would then run fine.

This morning, it got broken again. It froze during patching, and I had to restart in safe mode to apply the patch. I have separate SX8200 drives for testing (one for Ventura, which is now on an external enclosure, the other for Sequoia, which is installed now). Ventura was not problematic if at all, well, not that problematic. I had issues with boot up which got solved with the bless fix. I make it a point to not overwrite the current drive so I don't get disrupted if any install attempts fail, case in point.

Sequoia has been a challenge for me, 15.1.1 will install but gets stuck at boot, even with the bless fix (after migration). I only got this to work by cloning the Ventura (with current data) to the other SSD with CCC, then installing Seqouia over it. It had at least one mishap (update error), which I simply had to restart and continue the update sequence, but after that, it worked right away without having to revert root patches and to a bless fix.

It's been a couple of days, I've only shut it down a few times, and usually it boots fine. Sleep (closed lid, sleep from menu) and hibernation seems okay, everything else seems to work fine, except this issue.

Anyone else have this predicament?
 
Anyone else have this predicament?
No issue on my MacBookPro11,2 with Sequoia 15.2 + OCLP 2.2.0.

Edit: My only one "real" problem > MacOS 15.0 with OCLP 2.0.1 launch crash with Pixelmator Pro 3.69 >>

Steve Gosselin23/11/2024 14:53

Hello. Have you tried Pixelmator Pro 3.6.13 on Sequoia 15.1.1 + OCLP 2.1.2? Since this build; When launching the application, it has a popup warning that you need a Mac that supports Metal.

Works fine with Pixelmator Pro 3.6.12 / Sequoia 15.1.1 + OCLP 2.1.2.
 
Last edited:
Yesterday I realized that I can no longer update Microsoft Office on my Mac Pro 5,1, since Microsoft AutoUpdate will consistently fail. I had to use individual regular installers (not updaters) of the latest 16.92 apps to update Word, Excel, PowerPoint and Outlook (I've been unable to find the OneNote 16.92 installer.) I'm assuming this situation is caused by some incompatibility between OCLP 2.2.0 and my aging cMP 5,1 hardware. Any suggestions as to how this might be solved?
 
Yesterday I realized that I can no longer update Microsoft Office on my Mac Pro 5,1, since Microsoft AutoUpdate will consistently fail. I had to use individual regular installers (not updaters) of the latest 16.92 apps to update Word, Excel, PowerPoint and Outlook (I've been unable to find the OneNote 16.92 installer.) I'm assuming this situation is caused by some incompatibility between OCLP 2.2.0 and my aging cMP 5,1 hardware. Any suggestions as to how this might be solved?
It could be an issue. Same problem here with my MBP11,2 and MacMini7,1.
It started to happen in the beginning of December on the week I installed MSOffice on my new Mac16,11.
Because I use a Corporate License, I thought that the error was caused by Office Updater downloading the wrong version (ARM64, instead of AMD64) of MSOffice to the Intel Macs.
I will try the individual installers to see if it solves my problem too!

Thank you
 
  • Like
Reactions: olad
Did you use the usb installer on safe boot or you were able to use system preferences update?
Sorry for the late reply, I'm rarely here at the moment. OCLP was already on the rear SSD, so I was able to start the Safe Boot from the SSD using OCLP without any problems. 👍🏻
 
Create a second Apfs container on the same ssd and install Sonoma there.
🤔 Is it possible in this configuration to use the Data partition of another APFS container (main system) instead of the Data partition assigned to this APFS container (test system)?
👉🏻 I would like to use the OS in the second APFS partition but test with all data from the main partition.

Could I potentially even delete the Data partition of the test system in the second APFS container without causing issues? 🤔

I’d appreciate any personal experiences on this topic and advice on how to set it up best, as I don’t want to risk my main system – which is running perfectly 👍🏻. Thanks in advance!
 
(I've been unable to find the OneNote 16.92 installer.)
https://learn.microsoft.com/en-us/officeupdates/update-history-office-for-mac > https://officecdn.microsoft.com/pr/.../Microsoft_OneNote_16.92.24120731_Updater.pkg

Edit: Slow Microsoft AutoUpdate: root patches slow CLI commands >

boulder.audio13/11/2024 07:15

This issue also effects some GUI app like Microsoft AutoUpdate app, it's very slowly because AutoUpdate use a zsh postinstall script.
 
Last edited:
Hi, Anyone experienced frozen screen after typing password at login on Sequoia?
I am running non-metal, Mid 2100 27" iMac (12,2). It was working OK on Ventura but I created a fresh OCLP sequoia USB installer and after it was done I couldn't get past login. I can type my password but then it freezes - the multicoloured pizza comes up but doesn't even spin!
Any ideas if this is something I can fix or have I pushed a step too far and should I go back to Ventura? I have a WX4150 graphics card on order if that might help.
PS Is it better to do MacOS upgrades the apple way and then run the patcher, or is a new bootable installer the way to go when doing this?
PPS This is all on a separate volume of my SSD BTW - I can still boot to High Sierra original if that helps for any debugging...
 
Last edited:
Yesterday I realized that I can no longer update Microsoft Office on my Mac Pro 5,1, since Microsoft AutoUpdate will consistently fail. I had to use individual regular installers (not updaters) of the latest 16.92 apps to update Word, Excel, PowerPoint and Outlook (I've been unable to find the OneNote 16.92 installer.) I'm assuming this situation is caused by some incompatibility between OCLP 2.2.0 and my aging cMP 5,1 hardware. Any suggestions as to how this might be solved?
I have run into this same issue on one of my machines. If it fails, I usually just do a complete Office package install which includes OneNote, right over the top of the original and all your settings and email data remain intact... PITA but until it is fixed not that bad...
 
  • Like
Reactions: olad and hvds
Hi, Anyone experienced frozen screen after typing password at login on Sequoia?
I am running non-metal, Mid 2100 27" iMac (12,2). It was working OK on Ventura but I created a fresh OCLP sequoia USB installer and after it was done I couldn't get past login. I can type my password but then it freezes - the multicoloured pizza comes up but doesn't even spin!
Any ideas if this is something I can fix or have I pushed a step too far and should I go back to Ventura? I have a WX4150 graphics card on order if that might help.
PS Is it better to do MacOS upgrades the apple way and then run the patcher, or is a new bootable installer the way to go when doing this?
PPS This is all on a separate volume of my SSD BTW - I can still boot to High Sierra original if that helps for any debugging...

Sequoia has been problematic for me as well (Dortania has a note regarding this, see image below). A clean install was no problem, but after migration (either TM or MA), issues start to pile up. It'll get stuck on boot. I tried booting in safe mode and it will get stuck on the lock screen after log in. And this was 15.1.1.

I was only able to make it work by cloning my Ventura drive (with the complete data) and installing Sequoia (15.2) on top of that. I had an update error, which I was able to <fix> simply by restarting and continuing the update.

It's currently running okay, but my main issue is the display drivers gets broken during startup. I had to boot up in safe mode to reapply the patches.

It was okay when I started up today. I shut my MBP down when I'm not using it (when I go to sleep), to conserve the battery and save on power consumption, but at times, it'll boot up without the (3) external displays. VEntura was never this problematic after I got it to work.


Screenshot 2024-12-26 at 21.46.22.png
 
Last edited:
I've recently noticed on Sonoma, if I bounce a file in Pro Tools, whether Mov. MP3 or Wav. File.

It does let me drag the file to the USB media. It doesn't happen on Monterey. Files are not large, usually 5megs.
1735605860620.png
 
You might want to read this:

Thanks for the heads-up - I can see that there is potential for problems with different file system versions in use. This also explains why I am getting 'Incompatible Disk' warning when working in High Sierra - it obviously can't read the Seqouia volume.
I wonder what happens when I come to trying to upgrade my existing High Sierra volume to Ventura or above? How does it update the files system to a newer version? The upgraded volume is just my test rig to see what works - the plan was to eventually upgrade the main High Sierra volume - maybe this is not so straightforward...
 
  • Like
Reactions: rehkram
I've recently noticed on Sonoma, if I bounce a file in Pro Tools, whether Mov. MP3 or Wav. File.

It does let me drag the file to the USB media. It doesn't happen on Monterey. Files are not large, usually 5megs.
View attachment 2467281
That's weird. I just bounced a file in Pro Tools (.wav with 2024.10.1 on Sequoia 15.2), I can drag and copy with no issue to any usb drive or stick. I've never seen something like that... Maybe some permissions problem? Have you tried bouncing it to a different destination?
 
Thanks for the heads-up - I can see that there is potential for problems with different file system versions in use. This also explains why I am getting 'Incompatible Disk' warning when working in High Sierra - it obviously can't read the Seqouia volume.
I wonder what happens when I come to trying to upgrade my existing High Sierra volume to Ventura or above? How does it update the files system to a newer version? The upgraded volume is just my test rig to see what works - the plan was to eventually upgrade the main High Sierra volume - maybe this is not so straightforward...

Your best bet in my opinion would be to erase the entire disk and do a clean install of your mac's last supported macOS (10.13 High Sierra according to everymac.com) to the internal drive. When running macOS unsupported versions this is something all of us have to be prepared to do. It's a lot easier to contemplate doing this if you have a second, supported, Mac as your primary machine.

Once you've got it back to that last supported baseline, use the instructions on the Dortania site to install the later macOS version. Frankly, running multiple unsupported bootable versions of macOS on a non-metal Mac is more complexity than I would ever contemplate.
 
This from Discord via Dortania "it appears that Safari 18.2's JavaScript JIT requires AVX, so please avoid installing macOS 15.2 or any Safari updates on Ventura/Sonoma if you have a pre-Sandy Bridge CPU. if you've already updated and are seeing crashes, launchctl setenv JSC_useJIT false; launchctl setenv __XPC_JSC_useJIT false may allow Safari/Music/App Store to launch, but performance will be drastically reduced. we are investigating further; please be patient." 🤔
 
This from Discord via Dortania "it appears that Safari 18.2's JavaScript JIT requires AVX, so please avoid installing macOS 15.2 or any Safari updates on Ventura/Sonoma if you have a pre-Sandy Bridge CPU. if you've already updated and are seeing crashes, launchctl setenv JSC_useJIT false; launchctl setenv __XPC_JSC_useJIT false may allow Safari/Music/App Store to launch, but performance will be drastically reduced. we are investigating further; please be patient." 🤔
All working here but I guess it's because I have a 2012 cMP?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.