Toggle sidebar Toggle 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.
luckyduke23 said:
No, unfortunately I don't know for sure as I only run unsupported machines...
Click to expand...
Well, I posted over in the open core reddit, to see if anyone over there knows. Even before Monterey dropped support, I've been trying to find open source alternatives to mac native stuff as I like being able to use as many programs as possible, that are the same program regardless the OS it's running on. With that said, I like using the keyboard a lot more than the mouse for certain things, and little things like this keep coming up. Now a lot of this type of issue seems to be with the OS it self, regardless of being on a supported, or unsupported machine, or not.

Usually, I've been able to answer questions on my own regarding if the problem is apple related, or third party. I should also mention, that I haven't seen anyone mention this particular problem either.

Basically when I type the first letter, or two, of what I want in the file selection box, it doesn't select it like it used to in earlier versions of macOS and currently haven't found a fix. As a whole, the keyboard works fine, it's just the file selection by typing that seems to not work as it should.
 
OK, seems like I'm getting the keyboard navigation to work in the Open/ Save dialogs now. I was able to select an app by tying it's first few letters, or documents, etc.

It seems like Apple has made the file system case sensitive, which is normal for Unix /Linux, but I don't think it was case sensitive for older versions. So it must have been a fairly recent change in the last few releases.

As I've also mentioned, I've used more recent versions in VMware Fusion VMs too to eliminate Open Core in trying to see what Apple broke, and what is a result from a patched OS. Most of the time in my experience, most of the things I get irritated with have been changes Apple has made to the OS, and very few things have been related to OpenCore. At least on this mac and setup.

I also got my Epson stuff to install and work as well.

I already know I'm not going to dual boot multiple versions of macOS anymore on the same mac. It messes with icloud, even when only one is signed in. Just the dual boot can make things unhappy at times.
 
macOS 15.6b3 installed atop 15.6b2 OTA, OCLP v.2.4.0, runs as expected.
15.6b3.jpg:apple:👏
 
Last edited:
  • Like
Reactions: olad and Steve Gosselin
houser said:
Both with root patches and without has worked here, in my humble experience, as long as the source has the same status as the target in this regard. Migrating from an OCLP Mac to a supported Mac has also worked here without issues.
Click to expand...
Just to be sure I checked myself and saw the same problem; although the migration destination could boot to the account login screen, when attempting to login, it boot-looped to the migration assistant screen that normally appears at the first reboot after completing a migration, and this repeated over at each attempted login.
 
Is iMessage still a known issue for Sequoia? I just had a bunch of issues with the messages app freezing and having to force quit. I deleted the message causing it from the phone and started over fresh with that conversation,and it seems to be happier now. Still wanted to find out if it causes known issues though.
 
JedNZ said:
I believe you have to uninstall root patches in order for Migration Assistant to work. I’ve read it elsewhere here and it worked for me the only time I tried.
Click to expand...
Thank you, but do you mean uninstall root patches at the Migration Assistant destination MacBook Air or at the source or at both?
 
nekton1 said:
Thank you, but do you mean uninstall root patches at the Migration Assistant destination MacBook Air or at the source or at both?
Click to expand...
I believe you need to remove root patches on the machine that you're restoring to, and then reapply them when the restore is done.
 
Hello, since 15.3 and the last release of ocpl I have this issue :


ocpl1.png


I did a clean install and it is always the same result. I lost part of the desk and some image. With 15.1 no problem, but impossible to download 15.1. Do you know why. Thank
 
Bmld said:
With 15.1 no problem, but impossible to download 15.1. Do you know why. Thank
Click to expand...
Apple stops hosting older minor versions of each OS after some time, which means keeping the InstallAssistants is a good practice if you want to downgrade unless you want to go back to older major version. OCLP only pulls what's available from Apple and all of the downloaded OS's are official from Apple's CDN, not rehosted anywhere.

Sadly I can't help with that issue in any way.
 
  • Like
Reactions: macpro_mid2014
Neon Ball said:
Apple stops hosting older minor versions of each OS after some time, which means keeping the InstallAssistants is a good practice if you want to downgrade unless you want to go back to older major version. OCLP only pulls what's available from Apple and all of the downloaded OS's are official from Apple's CDN, not rehosted anywhere.

Sadly I can't help with that issue in any way.
Click to expand...
In my experience, the only version of macOS, I can't directly get from Apple today is Mavericks. However, the iMac is too new to run it, so that doesn't matter in this case. I can still get just about any other supported OS for this iMac though. I typically stay between Monterey, and Mojave for a supported OS. Mojave, because it's the last to support 32-bit apps. Monterey, as it's the latest officially supported OS.

With that said, I do have a USB installer for Mojave, and Monterey, as well as Sonoma, and Sequoia.
This iMac has official support from El Capitan through Monterey.
 
Last edited:
MacinMan said:
In my experience, the only version of macOS, I can't directly get from Apple today is Mavericks.
Click to expand...
Yeah, those are the major versions. You can get the major versions of macOS long into the past but they come packaged with later updates (point releases) and the older point releases get removed from the catalogue after some time, leaving you with mostly the latest updates (and couple older) for each version.

Oldest available version of Sequoia is 15.3.1, Sonoma 14.7.2 and Ventura 13.7.2. You won't be able to get 15.1, 14.1 or 13.1 anymore for example because Apple is no longer hosting them.
 
Neon Ball said:
Yeah, those are the major versions. You can get the major versions of macOS long into the past but they come packaged with later updates (point releases) and the older point releases get removed from the catalogue after some time, leaving you with mostly the latest updates for each version. For Sequoia the oldest available is 15.3.1, for Sonoma it's 14.7.2 and for Ventura 13.7.2. You won't be able to get 15.1, 14.1 or 13.1 anymore for example because Apple is no longer hosting them.
Click to expand...
I remember this being the case for quite a while now. Anyway, I've been trying to pick through the bugs I've been having with Sequoia, and trying to figure out which are Apple bugs, and which are related to an unsupported OS install. Do you happen to know if iMessage still has known issues of freezing and hanging under Sequoia? I'm currently running 15.5 on a late 2015 27" iMac, with OCLP 2.4.0, and last night, I had one particular conversation in iMessage that was causing nothing but crashes. As stated in an above post, I deleted the conversation from the iPhone so it would also delete from the Mac, and things seem OK now, so something could have gone wrong with the sync process, and clearing the message history completely fixed it. However, because Messages is a key reason that I keep macOS at all these days, I would like to know if I should be using something other than Sequoia to ensure things like this remain stable.

Thanks
 
Finally got round to install Sequoia on my MBP 9,1. All fine but for the brightness control keys, which don't have any effect. I found some older posts from back in 2024 reporting this. All my other machines work fine. Is this still an issue for some models? Is there a workaround? (OCLP 2.4.0, macOS 15.5)
 
makra said:
Finally got round to install Sequoia on my MBP 9,1. All fine but for the brightness control keys, which don't have any effect. I found some older posts from back in 2024 reporting this. All my other machines work fine. Is this still an issue for some models? Is there a workaround? (OCLP 2.4.0, macOS 15.5)
Click to expand...
Also on a MBP9,1 (OCLP 2.4.0 and macOS 15.5) and brightness control keys on the keyboard do work fine here.
 
Last edited:
  • Like
Reactions: makra
makra said:
Finally got round to install Sequoia on my MBP 9,1. All fine but for the brightness control keys, which don't have any effect. I found some older posts from back in 2024 reporting this. All my other machines work fine. Is this still an issue for some models? Is there a workaround? (OCLP 2.4.0, macOS 15.5)
Click to expand...
Reboot in safe mode, reapply patches with default settings, restart and report the findings please.

Additionally and probably foremost: do the buttons work with a good known system?
 
makra said:
No effect.

The keys work flawlessly under HighSierra – and: The display scale in the Sequioa control center doesn't respond either.

Thanks anyway.
Click to expand...
Are the F1/F2 recognized at all, i.e. can you see them being responsive using the keyboard viewer?
If so, you might want to add/reinject BrightnessKeys.kext to EFI/OC/Kexts to remap the keys.
 
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