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
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
github.com
I looked at the page and it seems like the focus on older Macs than mine, even though mine is also unsupported beyond Monterey. (iMac 17,2)
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.
Useless. In OCLP you have to reset By pressing the space bar, and you will see the option.
Thanks for the tips. There doesn't appear to be a global setting to disable Voice Recognition in the Sequoia Privacy Settings. It only offers the ability to turn it off for apps that request it. I also had previously disabled Voice Control (Accessibility) and Siri.
In any case, "localspeechrecognition" finished what it was doing around 90 minutes after the update completed, and it has been quiet since then. I've found that it is common for older OCLP Macs to take several hours to complete initial background processing tasks after a system update. Once that is done, the system tends to be fine.
Thanks again!
In any case, "localspeechrecognition" finished what it was doing around 90 minutes after the update completed, and it has been quiet since then. I've found that it is common for older OCLP Macs to take several hours to complete initial background processing tasks after a system update. Once that is done, the system tends to be fine.
Thanks again!
I posted something in another forum and a user recommended that I past my problem in this thread. Thank you for your help in advance!
Six weeks ago I made a failed attempt at updating my Late 2012 iMac to a more recent version of the OS using OCLP. I tried to do the same thing today and failed again. This time, I booted from the EFI of my external SSD and then selected Install macOS Sequoia. The next thing the computer asked me was to sign in to my account on the internal drive, which I don't think was supposed to happen. I ended up at an install Sequoia screen and after some time and some reboots, to the macOS Recovery page where I was asked to sign in screen to my account on the internal drive. When I signed in and got control of the computer again, I was still in Catalina with no sign of Sequoia.
After some investigation I discovered that during my last attempt I must have somehow installed the "macOS Install" disk on my internal drive along with OCLP on the EFI Boot. Attached you will see screen shots of my screen when I option-boot both without and with the external drive. You will also see my DiskUtility screen that shows that seems to show that there is no "macOS Install" disk present on the internal disk.
To the best of my knowledge, when I try to boot from the external disk it somehow switches me to the internal "install macOS Sequoia" and this is what causes the process to fail. But I could be terribly wrong. If anyone can help me I would be SO grateful.
Six weeks ago I made a failed attempt at updating my Late 2012 iMac to a more recent version of the OS using OCLP. I tried to do the same thing today and failed again. This time, I booted from the EFI of my external SSD and then selected Install macOS Sequoia. The next thing the computer asked me was to sign in to my account on the internal drive, which I don't think was supposed to happen. I ended up at an install Sequoia screen and after some time and some reboots, to the macOS Recovery page where I was asked to sign in screen to my account on the internal drive. When I signed in and got control of the computer again, I was still in Catalina with no sign of Sequoia.
After some investigation I discovered that during my last attempt I must have somehow installed the "macOS Install" disk on my internal drive along with OCLP on the EFI Boot. Attached you will see screen shots of my screen when I option-boot both without and with the external drive. You will also see my DiskUtility screen that shows that seems to show that there is no "macOS Install" disk present on the internal disk.
To the best of my knowledge, when I try to boot from the external disk it somehow switches me to the internal "install macOS Sequoia" and this is what causes the process to fail. But I could be terribly wrong. If anyone can help me I would be SO grateful.
Attachments
Ivy Bridge hasn't been native since Big Sur. Any GPU that requires root patching is by definition non-native.Can Safari play DRM content now on Ivy Bridge GPUs?
The support doc still says non-functional on non-native GPUs but Ivy Bridge is native right...
Legacy Metal Graphics Support and macOS Ventura - Sequoia · Issue #1008 · dortania/OpenCore-Legacy-Patcher
With the forth coming release of OpenCore Legacy Patcher v0.5.0, systems with legacy Metal GPUs will finally be able to achieve graphics acceleration in macOS Ventura! Reminder: These patches are s...
Native GPUs for Sequoia are:
- Coffee Lake (Kaby Lake spoofable to use the same driver)
- AMD Polaris or newer (except on systems that lack AVX2 like Mac Pros, requires Monterey drivers to be patched in)
Last edited:
Ah this is helpful, thanks! I thought they meant native as in integrated versus discreet.
Only now I understood the purpose and meaning of your question. Well the space bar way was the one I always used but it did not bring real progress for the first time now with 15.1 The traditional way, that I used for the first time today, however did... 🤷🏻♂️
Have a look at the Mr Macintosh installation guide?
MBP4,1 Early 2008, 17-inch OTA update macOS 15.0.1 -> 15.1 via OCLP 2.1.0n successful
Is there any further confirmation that the WhatsApp application does not work in some unsupported Macs after the upgrade to Sequoia 15.1? And have you tried using OCLP 2.1.0 Nightly? Thanks
same here om my 2015 MBP ... what app crashes
I have successfully updated my MacBook Air 2013 11 inch from macOS 15.0.1 to 15.1 using an in-place update, not a fresh install.
After the update I noticed the following:
1. A login screen was shown without any background and I gave up trying to login, the CPU fan was running, I then used the power button to power off
2. After the restart, I had no WiFi connection, I have re-applied the root patching using OCLP 2.0.2, the background was back.
3. I did reboot again, had WiFi and re-applied again the root patching, the MBA 2013 worked fine after this update.
What I noticed by the way what is not working correctly:
If I create screenshots, the rectangle that I used for cutting an area on screen remains, meaning, the area where the screenshot was taken is shown as this is the cut off and the remaining screen that I did not do the screenshot from remains darker, still visible but darker. After a reboot this is fixed.
After the update I noticed the following:
1. A login screen was shown without any background and I gave up trying to login, the CPU fan was running, I then used the power button to power off
2. After the restart, I had no WiFi connection, I have re-applied the root patching using OCLP 2.0.2, the background was back.
3. I did reboot again, had WiFi and re-applied again the root patching, the MBA 2013 worked fine after this update.
What I noticed by the way what is not working correctly:
If I create screenshots, the rectangle that I used for cutting an area on screen remains, meaning, the area where the screenshot was taken is shown as this is the cut off and the remaining screen that I did not do the screenshot from remains darker, still visible but darker. After a reboot this is fixed.
Posted on Discord lots more having issues with it.
BTW, WhatsApp crashes also on my two MBPs, with macOS Sequoia 15.1 and OCLP 2.0.2 (it probably would happen also with OCLP 2.1.0n).
… As for my previous Nvidia Kepler-related “no-license-agreement-display” issue, it’s interesting to note that it only happens with the macOS installers, whether with a full installer package or via Software Update (the license agreement is unavailable, respectively its window won’t appear and the “Update Now” button is unresponsive); for ordinary updates, license agreements appear correctly: for example, yesterday I installed the Xcode 16.1 Command Line Tools with Software Update, and everything was displayed and then updated perfectly. Quite strange glitch, anyway…
Last edited:
After 3 attempts update via OTA from 15.0.1 to 15.1 with OCLP 2.0.2 MacBook Pro 10.1 Retina Midi 2012. Like most user here, WhatsApp crashes. I'm waiting with the Update the iMac 17.1
I just installed macOS 15.1 and I confirm that the WhatsApp application does not start.
HOWEVER the WEB APP "WhatsApp WEB", which I created with Safari, WORKS fine.
NOTA: if "WhatsApp WEB", when you restart it newly, asks you to synchronise with WhatsApp on the iPhone, do not use the QRCode, but use the phone and the code that asks you to enter; so, WhatsApp WEB will no longer ask you to synchronize.
After that the WEB App of WhatsApp WEB will always restart quickly, as its application, which, instead, freezes.
[Note: even if after creating the WEB Apps you remove them from the Dock, they remain in $Your_User_HOME/Applications/]
Below I attach the report of WhatsApp's blocked Thread.
HOWEVER the WEB APP "WhatsApp WEB", which I created with Safari, WORKS fine.
NOTA: if "WhatsApp WEB", when you restart it newly, asks you to synchronise with WhatsApp on the iPhone, do not use the QRCode, but use the phone and the code that asks you to enter; so, WhatsApp WEB will no longer ask you to synchronize.
After that the WEB App of WhatsApp WEB will always restart quickly, as its application, which, instead, freezes.
[Note: even if after creating the WEB Apps you remove them from the Dock, they remain in $Your_User_HOME/Applications/]
Below I attach the report of WhatsApp's blocked Thread.
Code:
Process: WhatsApp [2593]
Path: /Applications/WhatsApp.app/Contents/MacOS/WhatsApp
Identifier: net.whatsapp.WhatsApp
Version: 24.20.79 (650900832)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2024-10-30 15:05:27.7623 +0100
OS Version: macOS 15.1 (24B83)
Report Version: 12
Anonymous UUID: 3B883EBB-C29C-0C3F-4AC0-DDA8D056CF7D
Time Awake Since Boot: 1100 seconds
System Integrity Protection: enabled
Crashed Thread: 6 Dispatch queue: com.apple.root.default-qos
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process: WhatsApp [2593]
Application Specific Information:
abort() called
—————————
(...thread ok omissis...)
—————————
Thread 6 Crashed:: Dispatch queue: com.apple.root.default-qos
0 libsystem_kernel.dylib 0x7ff81b40db52 __pthread_kill + 10
1 libsystem_pthread.dylib 0x7ff81b447f85 pthread_kill + 262
2 libsystem_c.dylib 0x7ff81b368bb9 __abort + 145
3 libsystem_c.dylib 0x7ff81b368b28 abort + 141
4 libc++abi.dylib 0x7ff81b3ff163 abort_message + 258
5 libc++abi.dylib 0x7ff81b3f00ce demangling_terminate_handler() + 266
6 libobjc.A.dylib 0x7ff81b08dd61 _objc_terminate() + 96
7 libc++abi.dylib 0x7ff81b3fe53b std::__terminate(void (*)()) + 6
8 libc++abi.dylib 0x7ff81b3fe4f6 std::terminate() + 54
9 libdispatch.dylib 0x7ff81b2a07f6 _dispatch_client_callout + 28
10 libdispatch.dylib 0x7ff81b2a306c _dispatch_queue_override_invoke + 961
11 libdispatch.dylib 0x7ff81b2afc92 _dispatch_root_queue_drain + 328
12 libdispatch.dylib 0x7ff81b2b0431 _dispatch_worker_thread2 + 147
13 libsystem_pthread.dylib 0x7ff81b444c3e _pthread_wqthread + 261
14 libsystem_pthread.dylib 0x7ff81b443bdb start_wqthread + 15Are you sure that your Mac really has no issues with Sequoia and OCLP?... ;-)
1) Have you tried to see if the Color Tools in Preview.app work well?... Is the levels graph visible or is there just its empty window? And does the "Auto Levels" button work or does the image disappear if you press it or if you move the two sliders at the ends of the graph?...
2) Have you tried to transmit a video from YouTube of your iPhone to your Mac, via AirPlay?... And does AirPlay work or does the Mac screen turn gray and a prohibition sign appear in the center?...
In my case, e.g., AirPlay works well with some YouTube videos from iPhone but, with the majority doesn't works and the same thing happens as I said above.
3) Finally, check if you are a lucky one who WhatsApp.app works. But if it doesn't work for you either, you can read my post with my suggestion to work around it, while waiting for the app problem to be solved.
@ Okonnel
Point 1
The Auto Levels work and the sliders work as well , and the graph is is visible
Point 2:
The screen is grey when i try video from the beginning with the commercials. If i just wait with commercial is finished and main video starts and than i turn on Airplay , than Airplay worked well.
Point 3 : I`m a lucky one
Point 1
The Auto Levels work and the sliders work as well , and the graph is is visible
Point 2:
The screen is grey when i try video from the beginning with the commercials. If i just wait with commercial is finished and main video starts and than i turn on Airplay , than Airplay worked well.
Point 3 : I`m a lucky one
Good evening, folks. For some time now, I've been using the following procedure for my MBP11,4. I download the full installer (15.1 Sequoia this time) from Mr MacIntosh, install it (but keep the installer for use later on an external SSD) so I have "Install macOS..." in Applications, reboot into Safety Mode, and run the Install application from the Applications Folder. I let it run until it freezes - usually on a second boot attempt, then I force quit, reboot into Safety Mode again, and leave the machine to run. Usually, the installation is completed without any hassle - a reboot to install metallib happened this time. Because I need Universal Control, I spoof to MBP15,1. OCLP 2.1n retains in memory my previous settings. It is a welcome addition. Little touches like this are a boon.
I also installed Sequoia (now 15.1) on an external SSD (to see if it was possible). It is slower, but it works. Everything is almost routine now - it takes a while (and I doze off in between). I don't do Root unpatch. I just download the whole installer and use on both SSDs in Safety mode.
Kudos as always to @khronokernel et al. Worth mentioning every time.
As others have noted, WhatsApp doesn't work. I don't know what else doesn't work, because I don't use all its potentials.
I also installed Sequoia (now 15.1) on an external SSD (to see if it was possible). It is slower, but it works. Everything is almost routine now - it takes a while (and I doze off in between). I don't do Root unpatch. I just download the whole installer and use on both SSDs in Safety mode.
Kudos as always to @khronokernel et al. Worth mentioning every time.
As others have noted, WhatsApp doesn't work. I don't know what else doesn't work, because I don't use all its potentials.
Last edited: