Unfortunately, for MBP 8.1 (2011 no Metal) performance has not improved as expected despite various MacOS and OCLP releases. So today I decided to revert to Sonoma with a clean install (14.7.6). The other two MBPs (2012 and 2015), both with Metal, seem to be fine with Sequoia.
Unfortunate or not, it's not a secret Tahoe will take considerably more GPU power in order to render the liquid effect alone. That OS is being built with Apple M Class chips in mind. Either there is a way to turn that effect off or one needs to accept the trade off in terms of performance loss. The first M1 products will be obsolete be the end of next year. Two years later the M2 will be retired.
I agree with all you say. Seriously. But one of the things that keeps me going is the sheer ingenuity of folks when it comes to computers - in this instance, Apple's macOS. Tahoe is the declared end run. But I won't be surprised if whatever it is that succeeds Tahoe finds some ingenous mod from the Hackingtosh guys, or elsewhere. If I am still around in 2 years, I will be checking MacRumors for "Unsupported Macs...", and not M1 or M2, but some 'ancient' Intel! We should be proud of what all of us - users and developers - achieved.
I have the same MacBook and similar bug, but with version 15.5. I saw from the log that it crashes because it fails to render the favicons of certain websites, and that causes the crash. So as long as those sites were open previously, you'll keep having this issue, and if you reopen the last session, it will keep happening. Luckily, it happens very rarely for me.
Finally opted for erasing the HD and instaing Sequoia from scratch. This worked all fine. Then made sure the root patches were removed and tried to restore all my data (including apps ad setting) from my TM backup from about a month ago (when Sequoia still worked well for me). Got stuck in the migration restart loop which I escaped by quitting the Migration Assistant only to find out that none of my data was restored from the backup. I read somewhere in this thread about 6-7 months ago that restoring from TM doesn‘t work uin Sequoia. Has this been fixed since or is it still an issue? Didn‘t find any hints that it stil is…
OCLP docs suggest it has not been fixed as of yet. Recommendation is to restore on Sonoma or earlier and then upgrade to Sequoia.
Thanks for the pointer. I‘ll go down the Sonoma route then, maybe stay with that for a while before updating to Sequoia.
I also have macbook pro 2014 with nvidea 750gt. Could you tell me , everything work fine with Sequoia? the most important for me is how nvidea work with final cut?
I am sorry I didn't follow up on this. I should have. No, everything isn't working fine.
Thanks, so TCC isn't supposed to show a version. I could have booted back into Monterey, since that's the officially supported OS, but figured I'd ask instead. So it looks like my system is functioning normally for both installs then.
Because your Mac requires root patching, these are the minimum requirements. If you enable any one of them, root patching is not going to work properly or even be installed.
I've read up on things before, I was mainly asking in regards to the improvements to OCLP if things have changed. I was going to run csrutil disable, just to have a standard disabled config, will that work just to turn sip off completely ?
Yes but use OCLP GUI to turn SIP off by selecting all SIP settings. Check indicates setting off. Rebuild OC and copy EFI to disk. Otherwise, OCLP will override your session csrutil settings on next boot in order to protect you from borking things.
OK, and yes I remember having to go through OCLP to do it. The reason I'm curious about permissions is because When I initially installed my Epson software, for the printer, and scanner(s) I have, under Sequoia, it installed but took a long time, compared to Monterey where it was faster. The other difference was, under Sequoia, the particular Epson pkg files would bring up the install for all users option, where Monterey did not. So, I'm not sure if this was a difference between the two versions of macOS and this software, of if having a custom SIP config messed things up a bit. So looking at just turning off sip completely for open core, as all on, or all off seems to be more of a standard configuration.
I was curious, does SilentKnight behave differently on Apple Silicon vs Intel? I know the M4, is going to be a native install, and no OCLP. However, when I booted back into Monterey after resetting PRAM, I get a TCC version, so I was a bit confused. Screenshot below:
