Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
OTA installation completed without issues. Applied Latest OCLP 0.6.6n (5.19.23)
There is video acceleration and YouTube plays fine, however, Apple TV will not play content; once play button is clicked Apple TV application shows dark screen with appropriate controls, then immediately reverts back to previous screen where one presses the button to "start" playing (no outright crash). Resetting PRAM made no difference.

I can also confirm other poster's report that drugging PDF document onto an open page, in Pages, causes a crash; that is true for 13.5 beta1, as it was for 13.4 OS version.
All this is exactly the same with 13.3.1 / 0.6.5
 
Hello,
Happy camper here. Just wondering if anyone is seeing and has seen and found a fix for photos crashing when attempting to click on the retouch function? Only on my rMBP 10,1 and not on the other Macs in my sig.

Edit: Unpatched with OCLP 0.6.5 and then it works. After repatching it stops working again.
Grateful for any hints. Pretty sure it attempts to switch to the Nvidia GPU when you nonsuch tasks.
Here is a short snippet of the first lines in the crashlog:
Code:
rashed Thread:        5  Dispatch queue: com.apple.root.user-initiated-qos


Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:       0x0000000000000001, 0x0000000000000000


Termination Reason:    Namespace SIGNAL, Code 4 Illegal instruction: 4
Terminating Process:   exc handler [3994]
 
Last edited:
  • Like
Reactions: rehkram
went from 13.2.1 to 13.5 beta 1 OTA no issues I know there was a post about inserting into pages pdf and images also doesn't seem to be a issue on mid 2014 MacBook Pro yes have to use parallels instead of vm fusion but works amazingly well so far with latest nightly OCLP can't test Apple TV currently although previews work.
 
The GPU issues are with AMD GPUs in Ventura. The macs that don't natively support Ventura don't have updated drivers making certain functions not work correctly making certain software that rely on those functions not work correctly.

............... If you read through the thread, there are multiple Mac models with AMD GPUs affected by problems I've outlined. They are also documented under the known issues section for the OCLP project.
It's called "teething" or "growing pains", dude! The first year that Monterey was released, there were a bazillion problems with OCLP and Monterey, and then after about a year, when Monterey reached maturity, it just became smooth sailing for users of OCLP and Monterey.

Ventura is going through its first year of existence, and even for people using Ventura on a supported Mac, it can be buggy and weird the first year. That's macOS.
 
  • Like
Reactions: Larsvonhier
i appreciate your suggestion but i think ill pass. i have all my needed apps in a folder on 3 different externals so i could easily access it. i also have 3 macos that have all the necessary apps loaded, mojave/big sur/monterey, any one of them falter i just boot into to another macos and its ready to go...and if the machine falters then i have another mac pro ready to boot up..😆 i am not messing around, i got options😁✌️
Here's the bullet proof way to use CCC.

 
It's called "teething" or "growing pains", dude! The first year that Monterey was released, there were a bazillion problems with OCLP and Monterey, and then after about a year, when Monterey reached maturity, it just became smooth sailing for users of OCLP and Monterey.

Ventura is going through its first year of existence, and even for people using Ventura on a supported Mac, it can be buggy and weird the first year. That's macOS.
I get the the teething part, my main concern would be going forward for unsupported Macs, if they can't get these issues resolved how good is the OCLP project going to be in the future. The developers of OCLP even state that if you rely on the mac for production to stick to an official release. For now, I can do that without problems with Monterey, but after that I'll need to answer the question, if I want to stay with Apple for desktop computing, or switch to something else. Mobile devices such as the iPhone, iPad, and even the Apple TV, I'm currently fine with.

So, to be up front with you, I'm well aware of first year problems with any OS, even on supported hardware, my comments strictly target moving forward with unsupported hardware after Monterey is out of support.
 
This is just a curiosity question and not a big deal: I am running Big Sur 11.7.7, Monterey 12.6.6 and Ventura 13.4 all patched with OCLP 0.6.6n (17 May 2023). When running Monterey, I'm prompted to upgrade to Ventura, but when running Big Sur, no updates are available (not prompted to upgrade to Ventura). Do others see the Ventura upgrade prompt in OCLP-patched Big Sur? Again, not a big deal - just curious.

Screen Shot 2023-05-20 at 12.04.11 PM.png
 
This is just a curiosity question and not a big deal: I am running Big Sur 11.7.7, Monterey 12.6.6 and Ventura 13.4 all patched with OCLP 0.6.6n (17 May 2023). When running Monterey, I'm prompted to upgrade to Ventura, but when running Big Sur, no updates are available (not prompted to upgrade to Ventura). Do others see the Ventura upgrade prompt in OCLP-patched Big Sur? Again, not a big deal - just curious.

View attachment 2204871
On my 5,5 when I was on Big Sur I never received an update notice. But on Monterrey I get notice to update to Ventura
 
  • Like
Reactions: deeveedee
It's called "teething" or "growing pains", dude! The first year that Monterey was released, there were a bazillion problems with OCLP and Monterey, and then after about a year, when Monterey reached maturity, it just became smooth sailing for users of OCLP and Monterey.

Ventura is going through its first year of existence, and even for people using Ventura on a supported Mac, it can be buggy and weird the first year. That's macOS.
Never had any issues on my unsupported Mac mini 2012 with official macOS releases (and OCLP), and on my supported mini 2018(no OCLP).....Only on beta releases so I stopped using betas.
I never had any virtual software (Parallels VMware) so I don't have an opinion on that.
I don't any webcam so I don't even know what happens with continuity camera and similar.
Apple TV, air play, blender, Premiere, Final Cut, Alfred, Powerpoint, word and excel work fine
No problems with you tube videos, jpeg, pdf or others import.
All those issues I read I don't know from where they arrive. Never seen
The only thing I imagine is that all issues are related to non native Apple software adapted to it.
 
Last edited:
I get the the teething part, my main concern would be going forward for unsupported Macs, if they can't get these issues resolved how good is the OCLP project going to be in the future. The developers of OCLP even state that if you rely on the mac for production to stick to an official release. For now, I can do that without problems with Monterey, but after that I'll need to answer the question, if I want to stay with Apple for desktop computing, or switch to something else. Mobile devices such as the iPhone, iPad, and even the Apple TV, I'm currently fine with.

So, to be up front with you, I'm well aware of first year problems with any OS, even on supported hardware, my comments strictly target moving forward with unsupported hardware after Monterey is out of support.
I doubt if @roysterdoyster cares very much where unsupported hardware is going, considering how glad he(?) is that his MBP4,1 is - still - capable of running Ventura. We will be there when macOS 14 rolls in. Many of us (I was tempted to say most) are here for the fun of being able to run the newest software on old hardware - it isn't as if we are doing some mission-critical assignments on them. At least I am not. I own a MBP11,4 and a MBA10,1 (courtesy of my children). I will own a MB7,1 soon (by arm-twisting & begging for discarded Macs), and I am looking forward to it. I didn't feel this way about my Dells and HPs in the past. When one gets involved with Macs (MBPs, MBAs, MBs, whatever), it tends to be a love affair. I love my Macs even if I know they are not perfect.
TLDR, if you want to stay with Apple for DT computing, the problems - which, btw, everyone here knows something of - won't deter you. If not, there is plenty to like in Linux (e.g. LinuxMint, Fedora, and my favourite, MX Linux and good old Ubuntu), or even Windows 11 (not to be sniffed at, believe me). It depends on how much your desktop environment matter.
Apologies for the longish opinion piece.
 
Yesterday, I installed the latest beta.
Not much difference but...

Warning
Safari seems to have a "serious" bug.
A couple of hours ago I used Command/W to close the tab I was in, instead of closing the tab it closed the whole Window.
After restarting Safari it ended up with 1 empty Window (I had 3 open Windows), next, I used the menu item
"reopen all windows from last session" and the three windows open but not the window (so I thought) with
all my other tabs, I then wanted to close the window and got a warning, if I wanted to close the window with
31 Tabs....HUH, there is no window with 31 Tabs.
So, again I restarted Safari, same thing, seems Safari has them open, but, where.
Yes, all tabs are always shown in all windows.
 
  • Like
Reactions: olad
Hello,
Happy camper here. Just wondering if anyone is seeing and has seen and found a fix for photos crashing when attempting to click on the retouch function? Only on my rMBP 10,1 and not on the other Macs in my sig. Could be library based I guess but I have repaired the library and it happens on new images. A well. Same with 0.6.5 and 0.6.6n today.
Grateful for any hints.
I don't use the retouch function but found it and clicked on it. It did not crash, just gave me the option to resize the selected pic
 
How do I stop this crap?
This does not work (sudo launchctl stop /System/Library/LaunchAgents/com.apple.contactsd.plist)
...........................(sudo launchctl stop /System/Library/LaunchAgents/com.apple.suggestd.plist)
These processes always use lots of CPU Time/%
And then there's Photoanalysisd, that one crashes a lot, also lots of CPU %

Screenshot 2023-05-20 at 19.16.55.png


This also does not work, it should, the command is right, just think I can't use it, bit sick how Apple F'ed up the System.
sudo launchctl disable gui/501/com.apple.contactsd
 
Last edited:
Yesterday, I installed the latest beta.
Not much difference but...

Warning
Safari seems to have a "serious" bug.
A couple of hours ago I used Command/W to close the tab I was in, instead of closing the tab it closed the whole Window.
After restarting Safari it ended up with 1 empty Window (I had 3 open Windows), next, I used the menu item
"reopen all windows from last session" and the three windows open but not the window (so I thought) with
all my other tabs, I then wanted to close the window and got a warning, if I wanted to close the window with
31 Tabs....HUH, there is no window with 31 Tabs.
So, again I restarted Safari, same thing, seems Safari has them open, but, where.
Yes, all tabs are always shown in all windows.
Are you running a hackintosh or a real Mac? What you've described doesn't occur on my Mac. If I hit command-w with only a single tab open the whole window goes away, logical enough. If I hit command-w with more than one tab open, the one I was looking at closes and one of the others comes up.
 
  • Like
Reactions: deeveedee
Are you running a hackintosh or a real Mac? What you've described doesn't occur on my Mac. If I hit command-w with only a single tab open the whole window goes away, logical enough. If I hit command-w with more than one tab open, the one I was looking at closes and one of the others comes up.
No , real Mac, a 2012 Mac Mini.
That's why I said it's a bug, it never happened before.
It happened once, that's the weird part, it still says 31 tabs open, see screenshot.
Yes, I am aware how CMD/W works, I had lots of tabs open in 1 window, probably 32, closed the Tab with CMD/W and boom, all gone, but now it says that I have 31 Tabs open...Where...?
Screenshot 2023-05-20 at 19.36.43.png


Update
I found out what the 31 Tabs where, had nothing to do with the issue, they where saved Tabs in the same window,
There was a "box" with Saved Tabs on the left of the URL Bar, besides was a < , clicked on it and it showed the Tabs, but now I can't get back the 5-6 open tabs I was in, they were not important though.

100% sure I clicked the CMD/W to close the tab, but then...yeah, closed all tabs...sucks.
No 1 hour Backup, only 24 Hours.
Wish Safari makes backups every time you open/close a tab, kind of a broader History Data base.
 
Last edited:
I doubt if @roysterdoyster cares very much where unsupported hardware is going, considering how glad he(?) is that his MBP4,1 is - still - capable of running Ventura. We will be there when macOS 14 rolls in. Many of us (I was tempted to say most) are here for the fun of being able to run the newest software on old hardware - it isn't as if we are doing some mission-critical assignments on them. At least I am not. I own a MBP11,4 and a MBA10,1 (courtesy of my children). I will own a MB7,1 soon (by arm-twisting & begging for discarded Macs), and I am looking forward to it. I didn't feel this way about my Dells and HPs in the past. When one gets involved with Macs (MBPs, MBAs, MBs, whatever), it tends to be a love affair. I love my Macs even if I know they are not perfect.
TLDR, if you want to stay with Apple for DT computing, the problems - which, btw, everyone here knows something of - won't deter you. If not, there is plenty to like in Linux (e.g. LinuxMint, Fedora, and my favourite, MX Linux and good old Ubuntu), or even Windows 11 (not to be sniffed at, believe me). It depends on how much your desktop environment matter.
Apologies for the longish opinion piece.
Oh I get what you're saying, and I do have late 2013 13" rMBP that Ventura works well on, I just wanted to make the point that, what matters to me right now is, that my late 2015, 27" iMac is my main and only computer right now, so it needs to stay stable for the time being, so the best choices right now would be staying with Monterey (supported by Apple), or switching to Linux, as right now, I don't currently have a budget for a new Mac, or even want one from Apple's current lineup. I want to stay with X86_64 for right now, because it's still the best option for third party support. With that said, I do like having the options of tinkering with the OS and changing things. Many Years ago, Mac OS X, and Classic MacOS were great options for this, now, Linux, or BSD seems to be the platforms to go to for that flexibility. The other point I wanted to make is, I'm not happy with the way Closed source proprietary platforms such as Apple, and Microsoft are going. Years back, I was "All Apple" it didn't matter what people said. I wanted my Apple stuff, and nothing else. Now, after giving the other platforms a fair chance to prove themselves and listening to people in those communities, I can understand why they encourage people to change to Linux (if they can.) Sometimes it's rough finding replacements / alternatives in the platform you're looking to switch to. That's been my biggest challenge looking from Apple to Linux, or even Windows. Now it's not as hard as it was a few years ago. While I still some macOS native software, I've been switching more and more to cross platform open source solutions while I still have a Mac, so when I do switch, it will be much easier. One more thing, I feel like while Steve Jobs was still alive, and he was running Apple, Apple as a company targeted people like me more, when it comes to power users / professionals, or anyone who really understood how computers worked, and wanted the freedom to tinker under the hood (within reason.) Now it's not so much that way anymore.

Just some thoughts to consider from someone who has been with Apple many years. (through the 80's and forward.)
 
Last edited:
Are you running a hackintosh or a real Mac? What you've described doesn't occur on my Mac. If I hit command-w with only a single tab open the whole window goes away, logical enough. If I hit command-w with more than one tab open, the one I was looking at closes and one of the others comes up.
I LOVE that you asked justperry if he's running a hack or real Mac! LMAO (I'm sure justperry is, too). On my HackBookPro6,2, command-w works perfectly in Safari 16.5 / Ventura 13.4 patched with OCLP 0.6.6n (17 May 2023).
 
MBP4,1
Update attempt from 13.3.1 to 13.4 unsuccessful: EFI partition (with Build/Install OCLP 0.6.6n) gone from Boot Picker. What can be done?
Tried in Terminal diskutil repairVolune disk0s1 and diskutil mount disk0s1, as it was unmounted, EFI boot still won‘t show up upon Restart with Alt-key.
 
My apologies. It was just that you appreciated your old MBP4,1 so much (and I had one long ago), and - as I wrote - glad that it was working with macOS 13.4, and beyond. I was just referencing your happiness. I'm sorry if it offended you.
No worries, mate. I just did not understand , that‘s all. Indeed I do love my MBP4,1 17-inch running on the latest OSes for years now. Seems 13.4 update killed it, though
 
MBP4,1
Update attempt from 13.3.1 to 13.4 unsuccessful: EFI partition (with Build/Install OCLP 0.6.6n) gone from Boot Picker. What can be done?
Tried in Terminal diskutil repairVolune disk0s1 and diskutil mount disk0s1, as it was unmounted, EFI boot still won‘t show up upon Restart with Alt-key.
Can you create a bootable USB on another Mac? If so, use OCLP on the other Mac to build/install a MBP4,1 OC EFI to the USB and then you may be able to boot your MBP4,1 from the USB. If booting your MBP4,1 from the USB works, you have multiple options to rebuild the MBP4,1 EFI on your SSD.

Note that I'm suggesting that you boot Ventura on your MBP4,1's SSD using the OC EFI installed on a USB.
 
Edit: Unpatched with OCLP 0.6.5 and then it works. After repatching it stops working again.
Grateful for any hints. Pretty sure it attempts to switch to the Nvidia GPU when you nonsuch tasks.
Here is a short snippet of the first lines in the crashlog:
I have both internal- and discrete GPUs enabled, haven't had any problems with switching so far. My main test for dGPU is firing up Sketchup 2017, which always comes up using the Nvidia card at first startup.

It's pretty difficult to catch which GPU is processing when an app may start on the internal GPU and then switch dynamically on demand from the app software or the OS (I assume). In my case, with your example, it seems to function as designed, whichever GPU it was using at that time.

Hope this helps just a little bit. Let me know if you want me to test something, since we have the same machine maybe I can help isolate the problem, or at least maybe eliminate some possibilities.
 
Last edited:
  • Like
Reactions: houser
How do I stop this crap?
This does not work (sudo launchctl stop /System/Library/LaunchAgents/com.apple.contactsd.plist)
...........................(sudo launchctl stop /System/Library/LaunchAgents/com.apple.suggestd.plist)
These processes always use lots of CPU Time/%
And then there's Photoanalysisd, that one crashes a lot, also lots of CPU %

This also does not work, it should, the command is right, just think I can't use it, bit sick how Apple F'ed up the System.
sudo launchctl disable gui/501/com.apple.contactsd
Maybe try this:
sudo launchctl remove com.apple.suggestd.plist
It may reappear the next time you boot.

MBP4,1
Update attempt from 13.3.1 to 13.4 unsuccessful: EFI partition (with Build/Install OCLP 0.6.6n) gone from Boot Picker. What can be done?
Tried in Terminal diskutil repairVolune disk0s1 and diskutil mount disk0s1, as it was unmounted, EFI boot still won‘t show up upon Restart with Alt-key.
Look at the EFI partitions and see what files are missing?

You can use OCLP to build an EFI stored in a temporary folder so you can do the compare.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.