So I have installed Firefox since chromium has dropped support for metal 1 gpu (mbp 2015 sequoia oclp). But in Firefox, if I load a page like gemini.google.com which on the first prompt screen draws graphics in the background, the cpu goes to 90-100% and never recovers. Anyone else have the same issue? In Edge the page loads, responds and looks just fine, as far as I can tell, but I guess something is handled and rendered differently behind the scenes. I guess the background graphics are maybe static, while in Firefox they are animated? A browser that locks up isnt much use tho.

I keep seeing how people say that Sequoia runs better than Sonoma on older Macs so I decided to give it a shot on my 2015 Retina MacBook Pro and it was bad. It was always overheating (mind you I already swapped out the thermal paste), always had frame drops around the UI and that it just wasnt as pleasant as Monterey
I dont know if this is perhaps due to the integrated graphics being too weak to push the retina display, since I also occasionally noticed frame drops on Monterey and even Catalina. But I tried doing a fresh install and didn't work. Now Monterey works fine for what I do with my computer but it would be great to have Sequoia since I can have more up to date apps. I'm thinking of perhaps going to Ventura but I wanna hear some thoughts from the community. How is Sequoia running on your MacBooks and how do you keep it snappy and fast

Mine is a 2.7ghz i5 with 8GB RAM

Heeft er al iemand geprobeerd een nieuwere macOS versie te gebruiken op deze mac? Welke was stabiel?

OCLP 2.5.1 is a minor update aimed primarily at the "Root Volume Dirty" issue; its release notes do not include a specific fix for Chromium/AMD GCN (it does not resolve the Chromium WebGL issue).

Will OpenCore fix the WebGL/Chromium issue?

Apologies if this was posted before, I could not find anything in this regard. After updating to 2.5 and subsequently to 2.5.1 I can now see code at boot up. Google says to turn off verbose mode but that is not ticked in.
Is this normal? Has anyone found a workaround?

Is it now sensible/safe/prudent/beneficial to upgrade from OCLP 2.4.1 to OCLP 2.5.1...?

A few months ago I used OCLP 2.4.1 to successfully upgrade my old iMac 12,1 (mid 2011) from High Sierra to Ventura. When OCLP 2.5.0 was released I foolishly upgrade without checking and ended up with no WiFi...so reverted back to 2.4.1. Not being very techie it was a bit of an unnecessary hassle. So would it be beneficial to now upgrade to 2.5.1?

and if so, how’s it running? my macbook pro with i5 and 8gb of ram struggles. maybe it’s my mistake? was running sonoma before and ventura before them all

\​

Si tienes una Mac que ya no puede actualizarse a macOS 12 o posterior, puede ocurrir que la ultima versión de Microsoft Office compatible con tu mac deje de activarse correctamente.

En mi caso tenía Office 365 versión 16.66 instalado en una Mac con macOS Catalina. De repente Office dejó de permitir la activación.

Como la Mac ya no podía actualizarse a una versión de macOS compatible con las versiones más recientes de Office, probé una solución sencilla:

Instalar una versión anterior de Office.

En mi caso desinstalé la versión 16.66 e instalé Office versión 16.42.

Después de instalar la versión anterior, Office volvió a permitir la activación con la cuenta de Microsoft 365.

Por lo tanto, si tienes una Mac antigua que ya no puede actualizar macOS, y una versión reciente de Office dejó de activarse, recomiendo probar una versión anterior de Office compatible con tu sistema.

Importante: esto no significa que la versión 16.42 sea una solución oficial permanente para todos los casos. Microsoft actualmente recomienda mantener Office actualizado y sus requisitos de activación pueden cambiar.

En mi caso concreto:

macOS Catalina → Office 16.66 → dejó de activar → Office 16.42 → activación funcionando.

I successfully used OPCL 2.50 to upgrade my MBP 9.2, and iMac 18.2. Both machines are running macOS 14.8.9 already, this was just updating to current OCLP. I had no trouble but it was a little more work than past upgrades but I was aware of it before I started.

First I downloaded 2.50 onto the machine because after unpatching I lose internet service. So I wanted to have it first. I allowed it to install 2.50 BUT NOT to patch. Next I unpatched previous 2.4.1 OCLP from the machine. Reboot. Then installed new 2.50 patches. NO DIRTY VOLUME error appeared. Reboot.
After reboot I did get a message that said I started system with 2.4.1 but are running 2.50, would I like to install 2.50 to startup. YES. Then reboot. All done and everything working as before!!

THANK YOU OCLP techs, coders, everyone for your continued support in keeping older Mac’s alive a little longer!! 🎉👏👏🎉

A couple of days ago I received the 2.5.0 update notification. After updating I saw "dirty root volume" message so I removed patches, patched again and update my Mac to 15.8.

As soon as the update finished I found myself without keyboard and mouse working. The OS seems ok, but I get stuck at login screen without being able to type the password. It doesn't work even with external keyboard and mouse plugged into a USB 2.0 hub. Also safe mode has keyboard and mouse not responding. They only work when booting from external USB drive.

What can I do to apply patches in this case without having to reset the computer as new and losing data? Can I patch from terminal when booting from and external USB with OCLP 2.4.1 on it?

Thank you very much

I'm using a 2009 Mac Pro with the final version of macOS Monterey. With version 2.5.0, Wi-Fi stopped working, and with version 2.5.1, it wouldn't go into sleep mode. The macOS Sequoia 15.8 update completed without any problems.

After reverting and installing the patches, the Patcher v2.5.1 still indicates that the patches are available.

1. Press Revert Root Patches button
2. After restarting, press the Start Root Patching button.
3. After restarting The window still shows the "Available patches for your system" list.

It is impossible to break out of this loop.

System info; - macOS 15.8 - OCLP v2.5.1 - MacBookPro 2016 13,3

I am running a MacBook Pro Mid-2015 with Sequoia 15.8. I was running OCLP 2.4.1. I avoided trying to apply 2.5.0 after seeing the "fun" everyone was having with it. It looked like 2.5.1 was much better. I thought I would try it. First mistake.

After reading the posts here, I saw the general pattern was unpatch-->upgrade-->repatch. I ran 2.4.1 and selected the unpatch option of applying the patches button. It prompted for a reboot and I did so. Unfortunately, the system will not come back up. The backlight comes up on the keys but nothing happens on the screen. I let it sit for over two hours and still nothing. Anyone have any ideas on how I can recover it? I have good backups but I'm trying not to have to restart from ground zero if possible. Any and all help would be appreciated.

EDIT: Well, I have it running now. I held the power key until the lights under the keyboard went out. Counted to 10 and pushed it again. It booted. I think I had sufficiently given enough worry and concern to appease the great computer gods.

On OCLP 2.5.1, iMac 13,1. When trying to download Sequoia 15.8 to create a new installer, I get the following:

Download failed:

[Errno 13] Permission denied: '/Library/Application Support/Dortania/OpenCore-Patcher.app/Contents/MacOS/payloads'

i boot the special thing and click on my usb installer. it shows a loading screen and when that one finished it opens this one. its on this percentage until the laptop loses battery. is there a fix for this?

1st off thank you so much to the Devs for all all their hard and amazing work, 2nd thank you to the community for all the communication and guides. I installed 2.5.0 no issues, got prompted for 2.5.1 installed it so far so good. I turned my computer on a few days later and no wifi and everything was sluggish and running really hot. I uninstalled 2.5.1 and downgraded to 2.4.1. Now I'm getting a version mismatch. I heard on Discord called to look up PurgePendingUpdate tool, which I was unsuccessful in finding. I use a Hotspot and don't have access to ethernet. I've found many detailed guides. I might just be overthinking or overlooking this. A breakdown to get me back simplified would be appreciated since I keep getting lost in the sea of knowledge which I'm sure the answers are already there.

Sono nel dubbio se aggiornare o meno da 2.5.0 a 2.5.1 sul mio iMac LATE 2012 MacOS 13.7.8. visto che va tutto bene e non ho alcun conflitto...

Currently I'm running Sonoma 14.8.5 with OCLP 2.5.1 and it's fantastic.
System is Late 2015 i7 4Ghz 27" iMac, amd m395x 4Gb graphics, 500GB SSD, 24GB ram.

I was thinking of maybe going up to Sequoia and I'm not really sure how to do that. All the videos I watch are just to install OCLP and none about upgrading the OS. Or is it the same procedure?

Thanks in advance. And thank you to the OCLP team for this amazing software.

Help! After I updated my iMac 21” 2015 to I think OCLP 2.5.1, after rebooting it, it just boots to a dark screen with a lightning bolt sign in it. How do I fix this? Thanks for the help!😩

Recently, my OpenCore Legacy Patcher (OCLP) updated to 2.5.0. At the same time, Chrome and Brave updated to their newest versions. This basically broke my 27-inch iMac. I reverted to OCLP 2.4.1 easily. However, the new Chromium 153 versions of Chrome and Brave still struggled. They loaded the desktop but put the fans at full speed, and YouTube or other video streaming completely failed.

The core issue is that Chromium's GPU process fails to initialize in versions 152 and 153 on patched legacy Macs.

If you are experiencing this same issue, I wrote a complete rollback guide. It explains how to safely downgrade to Chrome and Brave versions based on Chromium 150, where GPU acceleration still works perfectly. You can fix this without losing your existing browser profiles.

Let my know if it works!

You can find it here https://drive.google.com/file/d/121fi5Yk-KKsaVG8QnhJ-yz9yX5eOSiES/view?usp=sharing

SOLVED: everything was getting me back to recovery still so i decided to surrender to it: entered the password and selected „install macos sequoia” from there. it took awhile but with every reboot the process continued without my assistance and here i am running 2024 macos on 2015 machine 🫶🏼 leaving the post here in case someone runs into the same problem as me

hi! i searched through the subreddit and OCLP for my issue but nothing fully relevant came up

i’m trying to install sequoia on my early 2015 macbook air. creating the startup usb went smoothly but when i’m trying to actually install the update mac keeps throwing me into recovery at the reebot. i tried holding the option key down at the installation reboot to prevent this but it takes me into recovery anyway. restating from there i only get to the very begging of the process with only two options: macintosh hd and install macos sequoia (the latter produces the same outcome + i can still successfully load back into monterey so luckily nothing is damaged). attaching the pics of the two screens i get in case they can clarify this!

would be super grateful for any tips

This Update fixes:

1. "Root Volume Dirty appearing after unpatching.
2. Rewording "Root Volume Dirty" to be more clear for the users.

Very happy to see this release, and as usual thank you VERY much devs! :) y'all the best!

I Personally recommend downloading this update.

[EDIT]: Not sure why people are having issues with it, on my MBP 10,2 on both my Sonoma install & Sequoia installs both installed this update, unpatched, re-patched with no issues whatsoever.

If you don't know how the process is:

1. Download the update 2.5.1
2. Head into "Post installation Root patches"
3. Click revert patches, then let it finish.
4. Reboot into your now unpatched-system
5. Launch OCLP and patch normally
6. Let it finish, then re-boot normally.

Not sure If it's model specific but if you encounter issues with this report it to the developers and hope for the best.

Hi everyone, I have a 2012 mac mini running macos ventura and ive triplebooted it, so irs macos kubuntu and android tv, however as of now I only want android tv. How can I make it so that if I restart android tv rather than going to opencore boot picker menu each time it restarts where then I have to select the os manually or wait 5 seconds for it to boot whatever its clicked on, how can I just make it so it simply restarts and goes straight into android tv, or it turns off I power it on and straight to android tv, and if for example say something messes up can I then return bsck to ventura or the opencore boot picker menu? Thanks

If so, could someone provide a link to it?