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 13 Ventura on Unsupported Macs Thread
- Thread starter 0xCUBE
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Similarly OpenCore 1.3.0 has rendered my MacBook Pro mid 2012 unbootable. Was running the latest Ventura 13.6 and wasn't have any issues with OCLP 1.2.1
Don't know where/how else to get the word out (not possible for me to raise the alarm on their github), but I'd strongly advise not downloading and installing 1.3.0
Don't know where/how else to get the word out (not possible for me to raise the alarm on their github), but I'd strongly advise not downloading and installing 1.3.0
Please, be kind respecting the developers. There are so many factors that can fail in every single case. In my experience, a high porcentage due to the user.
OCLP 1.3.0 is an state of art. Full stop.
When did reporting potential issues become "unkind?" I am still applying Ventura 13.6.3 post-install patches with OCLP 0.6.8 and I look for posts with positive and negative experiences. Posting issues is not disrespectful and not unkind. If the negative experience of another saves me some trouble, it's valuable.
I fully support scrutiny of a post and challenging its technical validity, but blasting a post because it's "unkind" or not "respecting" the developers simply because it suggests there's a software issue? - not helpful.
If the post was derogatory or unprofessional, I'd agree with you. In this case, I have to disagree with you and think the poster was perfectly within their right to post this.
Thank you for your response-- not just for being supportive, but also for mentioning that you are using 0.6.8 for post-install patching because that might be very relevant for me later tonight when I can get back to working on my system
To the person responding to my initial post, I wasn't sure if your response was sarcastic because I didn't think I was being disrespectful to the developers at all (to anyone working on OCLP: you guys rock!), rather I'm just trying to bring something to attention that may be relevant for users with a similar setup. I was indirectly responding to the post above mine which also reported a serious issue.
Sure human error could be at play, and it could just as well be something buggy in the new version; crap happens, and it happened to me this morning after I downloaded/installed/ran 1.3.0
Since I have multiple versions of macOS running on my MBP6,2, I generate my Open Core EFI with OCLP 1.3.0 (booting all versions of macOS with the same OC EFI) and I patch each macOS volume with different OCLP versions. See here.... you are using 0.6.8 for post-install patching because that might be very relevant for me later tonight when I can get back to working on my system
A word to the wise, the vast majority of unexpected issues seen with OCLP can be overcome by a correct SMC reset and/or a NVRAM reset from OpenCanopy applying the Space bar at boot and indexing all the way to the right and selecting or using a wired KB and mouse following the Apple-mandated method until three (3) chimes occur. Before reporting problems, please use the resets to prevent misinformation and undo concern. Thank you. 🙏
Last edited:
Of course everyone can raise a potential issue in a specific case…
But saying that « he strongly not advises to download and install » a software based on a personal experience is a bit extreme !
Maybe the OP should have included a few emojis in their post. That seems to be the popular technique for posting critical content. Following your logic, "a word to the wise" implies that that someone is the opposite of wise.
I'm sure if we look hard enough, we could find many more reasons to be offended when no offense was intended.
How about if we all just give each other the benefit of the doubt and start with the assumption that our intentions are good.
emojis in their post. That seems to be the popular technique for posting critical content. Following your logic, "a word to the wise" implies that that someone is the opposite of wise. I'm sure if we look hard enough, we could find many more reasons to be offended when no offense was intended.
How about if we all just give each other the benefit of the doubt and start with the assumption that our intentions are good.
"A word to the wise," is merely a colloquial expression implying no offense to anyone, whatsoever. Quibbling over sound advice is confusing to newbies and the elderly, alike. 😉Maybe the OP should have included a few
I'm sure if we look hard enough, we could find many more reasons to be offended when no offense was intended.
How about if we all just give each other the benefit of the doubt and start with the assumption that our intentions are good.
If you follow all recommendations and bug reports, you never install anything
Basic question: running OCLP 1.2.1. Will reverting to 0.6.8 change anything in the post-install root patches (Mini4,1)? Thinking of doing this because of some current funkiness with the 13.6.1, and wondering if this might resolve some of those issues.
Unless someone knows with certainty, you'd have to examine the commits to determine whether any post-install patch changes may affect your Mini4,1.
I have gone back and forth between 1.2.x and 0.6.8 post-install patches without issues on my MBP6,2 (but behavior on one MacModel does not imply anything on another model). The safest way to experiment is to add an APFS volume, install 13.6.1 in the new volume, Migrate from your original 13.6.1 (before applying root-patches to the new APFS volume) and then apply OCLP 0.6.8 post-install patches.
And what is wrong? With my comment I brought my opponent’s statement to its logical conclusion.
(By the way, explain what OT is?)