I think at this point it's a known issue and most likely a change in Safari and not OCLP. I've seen reports that the same thing happens in Sonoma on the latest version of Safari. After I found that out I decided to scratch my plans to downgrade back to Sonoma. Hopefully the devs will find some sort of a patch or workaround for the newer Safari or if it's an Apple bug maybe it will get fixed in another update. ATM, I am just waiting to see what happens and keeping copies of Firefox and Brave handy in case I need them although I would prefer to just use Safari for everything.
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
What are the exact issues? I stuck Ventura and Sonoma in VM(s) via VMWare Fusion with ParaVirtualization enabled. Monterey is the host OS since I need to stick with supported here to ensure all things work and the VMs are for the newer versions of apps since they aren't something that can't run without issues in a VM. I can test something in Safari in one of the two VMs, or both to see if it's OCLP, or Apple related. Running macOS in a VM on a mac is supported by Apple, and everything is a native install vs being patched, so if it's an Apple issue, it should show up in the VM as well.
I got the WebGL part, What I wasn't sure of is if it's a Safari issue, or OCLP issue so that's why I was going to test it without OCLP in the mix since no one with a supported Mac spoke up that I could see.
EDIT: Looks to be an Apple issue, not OCLP. Based on the results of going to get.webgl.org in my Sonoma VM. It worked with the spinning cube under safari 17.6 and Firefox 133.03 under Monterey, and it even says Safari 18.2 supported it, but no spinning cube. Same Results with Ventura + Safari 18.2
Attachments
Last edited:
I don't own any newer macs than the late 2015. My other Apple devices such as Apple TV and iPhone are more current in terms of supported devices. As mentioned, I decided not to use OCLP for now because the updated software I want to use doesn't require to OS to be the host OS. So I stuck with Monterey as host as it's officially the last supported OS and put Ventura, and Sonoma in VMs with ParaVirtualization enabled. Since VMware does a native install of the OS, and I had the GL issues in the VMs, looks to be an apple issue and not OCLP.
With this said, it would really help to hear from someone with an M series mac as Intel is in use here. It would be helpful in knowing since it's an Apple bug, if it's Intel only, or does it also affect M series Macs as well.
If the cube was rotating, then it means WebGL is working for you.
Indeed it was rotating. Having read the posts above, I thought I would just try it, and although I can't say why it doesn't work on supposedly supported browsers as you pointed out before, but it seems just fine here with Safari 18.2.
I'm double checking stuff here. I installed the latest Firefox into my Sonoma VM, and the WebGL site wasn't working in that either. So wondering if macOS VMs are limited, or have to change settings in the browser. Everything works in the host. Will check a Linux VM. Like I said, a macOS VM should be considered a supported config over OCLPP, but I've never looked at this particular problem before. I do know some software is limited in a macOS virtual machine, but I've only found that to be the pro apps from apple at this time.
EDIT: tried Firefox under Linux Mint in a VM just for a FYI: and it worked. So, either I encountered a limitation of macOS VMs (even with paravirtualization enabled) that I wasn't aware of, or there are bugs / configuration issues.
Attachments
Last edited:
I think you're missing the point. The whole reason I ran these tests was to clarify if this was an issue with OCLP, or Apple. My iMac doesn't support above Monterey for the host OS, but Ventura and Sonoma will run in a virtual machine which is a supported install by Apple where OCLP isn't. So, I ran the tests in VMs to see if I had the same issues as people reported on their Macs running OCLP. That's the whole context of why I got involved here.
Hi all
I have an irritating problem with Sequoia 15.2 on a Mac Pro 6,1. Was running fine with 15.1, then I decided to update to 15.2 and after the update it wouldn't boot. Eventually I worked out that when I ejected my external hdd it would boot fine. Evidently when I was installing 15.1 I accidentally installed Opencore on the external hdd, although I also seemed to have done it on the Mac Pro internal HDD as well. Consequently on boot the EFI Boot can see both a patched 15.2 system on the internal hdd and a 15.1 volume on the external hdd and that seems to be causing the hang. I can delete the Opencore files left on the data volume of the external drive but it still won't boot. That's because there is a small volume (disk4s1) on the disk which I can't get rid of. Disk utility can't see it at all - and therefore can't mount it for me to edit it. terminal diskutil can see it and lists the unwanted volume as disk4s1 and the main data volume as disk4s2. Trouble is diskutil can't mount the unwanted volume either so I can't remove the unwanted files (as suggested in the Opencore help pages). I don't want to just delete the whole unwanted partition in case that borks the whole disk.
At the moment my work around is to mount the external hdd after boot, but the problem is that when I am away if my system needs a remote reboot (or we have a power cut), then the system will hang and all those things my Mac does unattended every day will stop.
Following another thread I have used Opencore Configurator to Mount EFI and I can see that the two partitions (on my internal SSD and the external drive) are as expected - see screen shot.
When I look inside the two partitions I see the internal SSD having a file structure containing various files, whereas the external disk EFI partition just contains four folders nested inside each other with no content. So whilst I could delete this, it is hard to see how this is causing my problem - so I am a bit stumped. There doesn't seem to be the option in the configurator to delete the EFI partition.
Can anyone tell me how to get rid of this unwanted partition please?
Thanks in advance for any ideas.
Regards
Tim
I have an irritating problem with Sequoia 15.2 on a Mac Pro 6,1. Was running fine with 15.1, then I decided to update to 15.2 and after the update it wouldn't boot. Eventually I worked out that when I ejected my external hdd it would boot fine. Evidently when I was installing 15.1 I accidentally installed Opencore on the external hdd, although I also seemed to have done it on the Mac Pro internal HDD as well. Consequently on boot the EFI Boot can see both a patched 15.2 system on the internal hdd and a 15.1 volume on the external hdd and that seems to be causing the hang. I can delete the Opencore files left on the data volume of the external drive but it still won't boot. That's because there is a small volume (disk4s1) on the disk which I can't get rid of. Disk utility can't see it at all - and therefore can't mount it for me to edit it. terminal diskutil can see it and lists the unwanted volume as disk4s1 and the main data volume as disk4s2. Trouble is diskutil can't mount the unwanted volume either so I can't remove the unwanted files (as suggested in the Opencore help pages). I don't want to just delete the whole unwanted partition in case that borks the whole disk.
At the moment my work around is to mount the external hdd after boot, but the problem is that when I am away if my system needs a remote reboot (or we have a power cut), then the system will hang and all those things my Mac does unattended every day will stop.
Following another thread I have used Opencore Configurator to Mount EFI and I can see that the two partitions (on my internal SSD and the external drive) are as expected - see screen shot.
When I look inside the two partitions I see the internal SSD having a file structure containing various files, whereas the external disk EFI partition just contains four folders nested inside each other with no content. So whilst I could delete this, it is hard to see how this is causing my problem - so I am a bit stumped. There doesn't seem to be the option in the configurator to delete the EFI partition.
Can anyone tell me how to get rid of this unwanted partition please?
Thanks in advance for any ideas.
Regards
Tim
you are on the wrong thread. This is about manual Installation on a MP51, not OCLP.
post it on this thread: https://forums.macrumors.com/threads/macos-15-sequoia-on-unsupported-macs-thread.2428654/
This usually happens after an update (MacOS or OCLP) and shows that the machine is still starting very slow with the lot of background activities. Give it time to do the background work for some hours or even days. If problem still occurs do NVRAM and SMC reset.
Hi
So I have tried various things to fix this annoying boot problem. I eventually reformatted the external drive as MacOS Journaled using MBR instead of GPT, which eliminated the EFI partition. I have checked and the EFI partition is definitely gone. So now I have an external drive with just the one normal data partition. But OCLP still won't boot if the drive is attached. I can plug it in as soon as the progress bar shows normal boot, and the system then behaves fine. I have tried rebuilding Opencore and applying patches with the newly formatted drive attached but it will still only boot if I remove the drive. I guess that something in my Opencore configuration still refers to the EFI partition of the external drive, which causes the hang even though it is no longer there.
Is there any way of editing the OCLP configuration to find and remove this, please? I have hunted around in settings but can't find anything that looks as if it does this.
BTW System Settings > General > Startup Disk could only see the internal drive even before I made the changes to the external drive.
Thanks in advance for any ideas.
Tim
Some admin transferred this post, makes no sense, so.
i have wait many days... the problem still exists... nvram reset only helps once, after reboot again gray background
I have the same problem, it's been with me since the first beta, I completely reset Sequoia yesterday without any programs or anything else, there was no gray desktop, then I just imported a few programs from a backup and the problem was back,
I also installed a volume with Sonoma with the same programs etc on the same NVMe blade and there is no problem, it boots up cleanly within 20 seconds.
I also installed a volume with Sonoma with the same programs etc on the same NVMe blade and there is no problem, it boots up cleanly within 20 seconds.
Yes, as many have mentioned, there are advantages to staying on Sonoma for now and very few serious advantages to gain from updating to Sequoia, if you have issues. So again, stay on Sonoma for now if you need stability and functionality.
I just updated my 2015 11-inch AIR to Sequoia 15.2 and did the root patches on it. So far I'm not having any major issues running the current version of the new OS. I'm using OCLP 2.2.0
I'm sorry to hear that. Did you also do an SMC reset? If you have multiple user accounts, you may also want to log into the admin account first after upgrading. It is obvious that the gray background problem is caused by excessive background activity during startup. My machine used to be very laggy. But now my iMac is running perfectly smooth and fast again. So, hope dies last, whatever the reason for the slow startup is. Other signs related to the same problem are a slow progress bar after login, and once the gray background has disappeared, the icons in the top right corner of the taskbar appear slowly one after the other instead of all at once. Then it takes longer than usual for my desktop widgets to load and connect to the Internet to update.