Ah fair enough my fault , still never have to change anything on the MBP11,3 .
Got a tip for us?
Let us know
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
- Thread starter flagers
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Ah fair enough my fault , still never have to change anything on the MBP11,3 .
Are there any problems with keyboards, Mine are misbehaving, it's not the keyboard, works fine on other systems or macOS versions?
Misbehaving spacebar, not always, just intermittently, misbehaving more than not, not filling space in text but seems to use the tab function instead of function of the spacebar.
This is a standaard el cheapo keyboard, worked before and in other macOs versions.
My other Apple Keyboards seem to have other problems.
Misbehaving spacebar, not always, just intermittently, misbehaving more than not, not filling space in text but seems to use the tab function instead of function of the spacebar.
This is a standaard el cheapo keyboard, worked before and in other macOs versions.
My other Apple Keyboards seem to have other problems.
I don't think the high end or low end makes much of a difference in consumer routers in terms of software function. Most consumer routers have firmware based on linux. That doesn't really differentiate things much. It really depends on the capabilities of the vendors and how they manage their development practices and respond to issues.
And of course if you load some third party firmware on it, then you likely are making more informed decisions about what you are comfortable with anyway, which would put you in a different category than the typical user.
Also, there is no brand immune to security issues. You basically just have to pick your poison and choose your priorities.
I'm assuming you built OpenCore on a different Mac? Build OpenCore again on device and restart, it should enable AMFIPass which enables the TCC permission system.
Multiple builds will just create a bigger mess both code maintainability wise and for the user, there has been so much complaints about random crashing revealed to be caused by those two that it was seen as better to disable it by default.
Good news is that settings retainment will also be shipping once 2.1.0 is out, which means no more enabling the settings over and over again after OCLP updates etc and OCLP will remember the settings status even in the GUI. It's a pretty big overhaul that should reduce overall confusion about saving settings. Which means even for FeatureUnlock, once you enable it for one time it's basically set it and forget it.
Interesting situation I found myself in, I have been using MacPorts for various programs not natively available and one such is the need to have ffmpeg+gpl2+nonfree however while it installs ok, there are errors/warnings regarding CoreImage being 1.0 instead of 1.0.1 or higher. I found that I'm not the only one based on this thread, MacPorts link and while my machine is dated (rMBP 10,1) with root patched thanks to latest OCLP, I was hoping Devs can incorporate a newer CoreImage without it breaking older machine support on Sequoia. Not sure if others here have seen this or have a workaround/solution.
Some parts of the OS have to be downgraded in some cases and dropping in newer things won't be as simple as it sounds, things have dependencies and may not even work with the legacy drivers, bringing the whole card house down. Patching graphics is a very delicate process, which is also why it always takes the longest.
Since Apple no longer makes new drivers for legacy GPUs, it can also be likely that it's impossible to use a newer version, e.g. requiring certain features only available in newer GPUs / their drivers.
It remains to be seen but it is not certain at all.
Last edited:
A little about my current situation with my mpb11,3 (Kepler) system update.
I always test the system update OTA on a few volumes on an external SSD first, make sure the update is successful without any issues, and then update the internal SSD on my mbp.
Currently the system-version(internal SSD) on my 11,3 is still on 15.0.
This is because when I tested the update to 15.0.1 on the external SSD, I had an issue on the final reboot where the whole screen would flash every few seconds at the login screen and I couldn't enter my password. Even safe mode didn't solve it.
In the end I was able to update with a clean install since I had a backup, but it looked suspicious in this state so I decided to hold off on updating the internal SSD. Luckily it's running fine on 15.0.
I always test the system update OTA on a few volumes on an external SSD first, make sure the update is successful without any issues, and then update the internal SSD on my mbp.
Currently the system-version(internal SSD) on my 11,3 is still on 15.0.
This is because when I tested the update to 15.0.1 on the external SSD, I had an issue on the final reboot where the whole screen would flash every few seconds at the login screen and I couldn't enter my password. Even safe mode didn't solve it.
In the end I was able to update with a clean install since I had a backup, but it looked suspicious in this state so I decided to hold off on updating the internal SSD. Luckily it's running fine on 15.0.
Last edited:
Hey all, quick question as I'm unclear on all the details. Which unsupported macs have the chrome issue where it turns red and doesn't render correctly? From the video I saw it in, it seems to be a Sequoia related issue, but am unclear on which macs. I have a late 2015, 27" iMac 17,1 and after the initial chrome issues were fixed, it works fine under OpenCore. So, will the recent Chrome issues affect me as well, or is it mainly for older macs?
Not my rMBP10,1
But I wouldn't touch chrome with a ten foot bargepole...
But I wouldn't touch chrome with a ten foot bargepole...
A big Google fan, eh? 🤣
By way of interest.
My Macbook Pros, 9,2 and 10,1 took to Sequoia 15.0.0 and OCLP 2.0.2 like ducks to water.
But they both won't take Sequoia 15.0.1 - I hit hte upgrade OTA button and they ignore me.
Nevermind.
Separately, my Mac Pro 5,1 is happy on Sequoia 15.0.1.
My Macbook Pros, 9,2 and 10,1 took to Sequoia 15.0.0 and OCLP 2.0.2 like ducks to water.
But they both won't take Sequoia 15.0.1 - I hit hte upgrade OTA button and they ignore me.
Nevermind.
Separately, my Mac Pro 5,1 is happy on Sequoia 15.0.1.
Hi guys - have a 2017 MacBook 12
Update all went fine on oclp latest build but it will not sleep, if I close the lid now the screen stays on when on battery. If it send it to sleep it goes to sleep but when I close the screen it wakes up! Any ideas it’s driving me nuts!
Update all went fine on oclp latest build but it will not sleep, if I close the lid now the screen stays on when on battery. If it send it to sleep it goes to sleep but when I close the screen it wakes up! Any ideas it’s driving me nuts!
Thanks, I don't use it as my main browser. I just keep it around for compatibility. When I first started using it years ago, it was for the cast function for non apple devices that didn't do airplay. Now, it's just there as an optional browser to use.
Updated OCLP Documentation recommends against performing a Migration as the last step of a macOS installation (Setup Assistant). This is because OCLP Docs assume that users have built their macOS USB installer with OCLP (instead of following Apple's instructions as I have stated in my previous post).
If you install macOS with a USB installer created by OCLP (and not using Apple's USB creation instructions), OCLP Docs recommend "Reverting" OCLP root patches from your target volume before Migrating to the target volume.
EDIT: Note that the Updated OCLP Instructions indicate that Migration to a Sequoia target volume may not work after "Reverting" OCLP root patches from the target volume. This may be a reason to install macOS using Apple's USB installer instructions.
Just for curiosity, I made my 15.0.1 from OCLP Sequoia, not uninstalling root patches. This time was ok, some other past times not ok at all. As I said before, OCLP Sequoia USB does not install root patches till the first login.
@trifero That's good to know. I was just reporting what the OCLP Devs had provided in updated documentation. I suspect that individual experiences will continue to vary depending on the Mac model (and thus the type of OCLP post-install patches). I realize that OCLP Documentation is written to apply generally to all OCLP users, so it will be up to us (in this forum) to share advice.
You can bet your ass on it. Each model is different. In fact, as I said before so many times, I use to uninstall root patches before updating. It was only an experiment. This time went fine.
My 2019 MacBook Pro has been running Sequoia just fine, until the update yesterday. Now the Lock Screen is low on the screen, with a black bar at the top maybe 2 inches of the screen. It's low enough that I cannot see the box to enter my password in. When I receive a text notification, the box slides in left from the right side of the screen, but only goes about halfway, so I can only see the first few words.
Your 2019 MBP is still supported by Apple, yes? If so you might want to post this as a new topic on the main Sequoia forum. This topic is for Sequoia on unsupported Macs.
There is a simple and cheap work around:
Revert all patches and you have a build platform as supported and expected by Apple (and Xcode and possibly all other development toolsets). A real developer uses the console (esc meta alternate caps shift - the ultimate development platform). At least you can build now all your stuff and as this is usually only done once on a normal desktop Mac it should be a reasonable way.
There is more expensive alternative work around:
Buy a more recent OCLP Mac not needing the MetallibSupportPackage if you need a working GUI to access the development tools (these patch the metallib in CoreImage and this is the only spot I could find where OCLP touches this FrameWork). I might be wrong with this, but doing only a 5 minute research through the OCLP code this is what I found out.
There is a real solution:
Do not use any unsupported and patched systems at all for development unless you have spent hours in reverse engineering OCLP and know exactly what you are doing.
Patching with OCLP does not mean to put a simply patch onto the skin to stop superficial bleeding, here it sometimes means to transplant an organ or replace some bones with more metal. Mac is still alive, but some immune suppressive will take its toll all day long. The MetallibSupportPackage has been developed to avoid all those glitches visible with Kepler/HD4000 and relatives.
You cannot have it all. And you will not get it all!
Got a bit of an issue with OCLP that I was hoping someone could give their advice on. Posted this as a separate thread but barely anybody has seen it, so thought it would be better here.
I've been tinkering with my MacPro5,1 again and decided to try Sequoia with OCLP. Did a clean install using the guide and it seems to work very nicely... except, no wifi, no Bluetooth. My guess is that it isn't expecting to deal with an upgraded card, as I installed the BCM943602CDP for native support under Monterey.
I understand there are a bunch of root patches and special sauce in OpenCore to make things work, and though I've tried disabling various related options using OpenCore Configurator the best I've managed is for Bluetooth devices to be seen, but never pair successfully. The iMacs that originally used the BCM943602CDP do seem to be supported by OCLP, so I assume there must be patches available, but my searches haven't turned up anything helpful. That probably means it's monumentally complicated, or incredibly simple and I should have figured it out myself.
Anyone managed to get this working or have any pointers? I'm guessing I will need to install the iMac root patches for wifi and Bluetooth to this Mac Pro, but I have no idea how.
I've been tinkering with my MacPro5,1 again and decided to try Sequoia with OCLP. Did a clean install using the guide and it seems to work very nicely... except, no wifi, no Bluetooth. My guess is that it isn't expecting to deal with an upgraded card, as I installed the BCM943602CDP for native support under Monterey.
I understand there are a bunch of root patches and special sauce in OpenCore to make things work, and though I've tried disabling various related options using OpenCore Configurator the best I've managed is for Bluetooth devices to be seen, but never pair successfully. The iMacs that originally used the BCM943602CDP do seem to be supported by OCLP, so I assume there must be patches available, but my searches haven't turned up anything helpful. That probably means it's monumentally complicated, or incredibly simple and I should have figured it out myself.
Anyone managed to get this working or have any pointers? I'm guessing I will need to install the iMac root patches for wifi and Bluetooth to this Mac Pro, but I have no idea how.
Having same issue for iMessages on MBP 13,3 with 15.1 b6 OCLP 2.0.2. Console logs show crash of identityservicesd. Issue persisted thru every version of Sequoia, every update of OCLP.