Try building and installing OCLP again with Settings -> Advanced -> FeatureUnlock -> Partial.
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
I HAVE BEEN UNFAITHFUL.
For quite awhile now I have been using OCLP on a 2013 i7 MacBook Air 6,1 at home, enjoying every minute of it and very thankful for it. Things began to get a bit squirrley more recently on 3.4.1 and since I use some demanding photo editing apps, etc., I recently decided to get a 2023 M2 Mini...
After settling in with that, yesterday I decided to do a first-time-ever clean wipe of the 2013 MBA with a fresh straight install of 3.4.1. I made the OCLP flash drive on the target MBA before doing the wipe, booted from the flash drive, wiped the internal SSD, partitioned it at this point to allow for a Linux partition (400/100), why not. I did the OCLP Ventura install, no post patches needed after reboot, very nice and easy, no drama.
Then I booted from a KDE Neon flash drive, did the install on the smaller partition, and all went well – except Neon (not entirely unexpectedly) took over what seems to be the shared EFI partition and I lost macOS boot capability.
So I started over and reinstalled Ventura the same way, rebooted and got going again, then removed the Linux partition.
*Please advise how one might dual-boot under these circumstances. Not a big deal, no rush and no need really, but I was just wondering how the two OSs could coexist without too much hassle.
I'm not sure how much I would use the 2013 going forward, and I could just leave Ventura on there (with ongoing updates) for occasional Intel-app compatibility before eventually going full Linux in the future (when macOS moves too far head for OCLP).
For quite awhile now I have been using OCLP on a 2013 i7 MacBook Air 6,1 at home, enjoying every minute of it and very thankful for it. Things began to get a bit squirrley more recently on 3.4.1 and since I use some demanding photo editing apps, etc., I recently decided to get a 2023 M2 Mini...
After settling in with that, yesterday I decided to do a first-time-ever clean wipe of the 2013 MBA with a fresh straight install of 3.4.1. I made the OCLP flash drive on the target MBA before doing the wipe, booted from the flash drive, wiped the internal SSD, partitioned it at this point to allow for a Linux partition (400/100), why not. I did the OCLP Ventura install, no post patches needed after reboot, very nice and easy, no drama.
Then I booted from a KDE Neon flash drive, did the install on the smaller partition, and all went well – except Neon (not entirely unexpectedly) took over what seems to be the shared EFI partition and I lost macOS boot capability.
So I started over and reinstalled Ventura the same way, rebooted and got going again, then removed the Linux partition.
*Please advise how one might dual-boot under these circumstances. Not a big deal, no rush and no need really, but I was just wondering how the two OSs could coexist without too much hassle.
I'm not sure how much I would use the 2013 going forward, and I could just leave Ventura on there (with ongoing updates) for occasional Intel-app compatibility before eventually going full Linux in the future (when macOS moves too far head for OCLP).
Create a new partition for OCLP and let Linux, Windows or whatever own the original EFI. Works here.
I used this for Win 10, 11 and Ubuntu:
Thanks houser, I see it was right there in the RTFM! ;-)
I saved the info for later. I do already have Neon running on its own on a 2008 MacBook Pro, again, just for fun.
I have a MBP 11,4 (2015) and had photos crash weekly and freeze everything and caused me to reboot. However, since 0.6.7 and 13.3.1 (Now on 13.4.1) I don't have any problems at all. What Ventura version are you on? What version of OCLP?
I am still on old Opencore 0.6.1 with Ventura 13.2.1 and I had this problem also, by setting Partial in FeatureUnlock for OpenCore, the crashing problem does not come anymore. and I never had problem with Photos.
However I do still have problem with:
1- Copying texts sometimes does not work (example from Browser to Apple Pages), so my solution is to paste in Text edit and copy it then I can paste into Apple Pages.
2- Zooming pictures does not work sometimes (Apple Preview and in Browsers) by zooming (pinching, with two fingers) with my MacBook's trackpad and I have no idea why sometimes this happens?
Updated to Ventura RSR 13.4.1(a) OTA on a rMBP 11,3, had to reboot twice; OCLP 0.6.7 detected that root patches needed to be reapplied, so root patched again.
Everything seems to be working smoothly for now..
Everything seems to be working smoothly for now..
Found a MacBookPro10,1 (mid 2012) left behind by my son in closet.
Fully operational on Ventura 13.4.1 with OCLP 0.6.7, including WiFI and BT.
Responsive enough for causal usage.
BootCamp WIndows 11 22H2 also works with no issue. All hardwares recognised.
Even Diablo 4 runs but too slow for actual play. Likely need eGPU for game play.
Unfortunately he has gifted his eGPU to his friend.
Thus no further testing.
Fully operational on Ventura 13.4.1 with OCLP 0.6.7, including WiFI and BT.
Responsive enough for causal usage.
BootCamp WIndows 11 22H2 also works with no issue. All hardwares recognised.
Even Diablo 4 runs but too slow for actual play. Likely need eGPU for game play.
Unfortunately he has gifted his eGPU to his friend.
Thus no further testing.
Oops...
Apple earlier today released new Rapid Security Response updates for iOS 16.5.1, iPadOS 16.5.1, and macOS Ventura 13.4.1 users, but Apple has pulled the software, likely due to an issue that caused certain websites not to work after the RSRs were installed.
Apple earlier today released new Rapid Security Response updates for iOS 16.5.1, iPadOS 16.5.1, and macOS Ventura 13.4.1 users, but Apple has pulled the software, likely due to an issue that caused certain websites not to work after the RSRs were installed.
OTA update done to 22G5072a using 0.6.8n as usual without any others issues but the known: weather app spinning beachball but coming back by itself. Apple TV: no hiccups there.
Installed Ventura on MBP A1398, mid 2014 using OCLP. Everything appears to be working fine. Yesterday evening and this morning system shut down right after login then displayed low battery/connect power source icon when trying to power back on. Connected power source, booted up - battery was still at 61%. I ran diagnostics at startup, no issues found. Could this be due to OCLP patch loading at startup? Are there any cons to running Ventura using OCLP? If I stay on Big Sur, will it still be safe to use after November 2023 when it is no longer supported? I have ordered a replacement battery. I appreciate any info on this. This is my battery info and crash report:
Charge Information:
The battery’s charge is below the warning level: No
Fully Charged: No
Charging: No
Full Charge Capacity (mAh): 7072
State of Charge (%): 51
Health Information:
Cycle Count: 962
Condition: Normal
Translated Report (Full Report Below)
-------------------------------------
Process: nsattributedstringagent [813]
Path: /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/XPCServices/nsattributedstringagent.xpc/Contents/MacOS/nsattributedstringagent
Identifier: com.apple.textkit.nsattributedstringagent
Version: 1.0 (857.8)
Build Info: UIFoundation-857008000000000~221
Code Type: X86-64 (Native)
Parent Process: launchd [1]
Responsible: AboutExtension [812]
User ID: 501
Date/Time: 2023-07-12 05:55:03.0228 -0500
OS Version: macOS 13.4.1 (22F770820b)
Report Version: 12
Anonymous UUID: B12987D0-191A-8F8A-0DC2-3B3ABBE3B07C
Time Awake Since Boot: 640 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000027fab66a0
Exception Codes: 0x0000000000000001, 0x000000027fab66a0
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [813]
Charge Information:
The battery’s charge is below the warning level: No
Fully Charged: No
Charging: No
Full Charge Capacity (mAh): 7072
State of Charge (%): 51
Health Information:
Cycle Count: 962
Condition: Normal
Translated Report (Full Report Below)
-------------------------------------
Process: nsattributedstringagent [813]
Path: /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/XPCServices/nsattributedstringagent.xpc/Contents/MacOS/nsattributedstringagent
Identifier: com.apple.textkit.nsattributedstringagent
Version: 1.0 (857.8)
Build Info: UIFoundation-857008000000000~221
Code Type: X86-64 (Native)
Parent Process: launchd [1]
Responsible: AboutExtension [812]
User ID: 501
Date/Time: 2023-07-12 05:55:03.0228 -0500
OS Version: macOS 13.4.1 (22F770820b)
Report Version: 12
Anonymous UUID: B12987D0-191A-8F8A-0DC2-3B3ABBE3B07C
Time Awake Since Boot: 640 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000027fab66a0
Exception Codes: 0x0000000000000001, 0x000000027fab66a0
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [813]
I have a 2012 Retina MBP 15" (Quad 2.6GHz, 16GB, 512GB SSD) and haven't been that happy with the graphical performance since upgrading to Monterey, especially when running at higher resolutions for more desktop space.
I'm not playing any games, just emails and web browsers, messaging etc. The most graphically intensive thing is playing YouTube videos with high FPS. I'm more talking about somewhat sluggish GUI in general.
Can anyone let me know if Ventura might fare any better?
I'm not playing any games, just emails and web browsers, messaging etc. The most graphically intensive thing is playing YouTube videos with high FPS. I'm more talking about somewhat sluggish GUI in general.
Can anyone let me know if Ventura might fare any better?
Have had this issue before OCLP has been updated since then , I had success with turning off NVMe PM management in extras then building OCLP and installing can also when it’s showing the battery logo reset SMC would also usually allow a boot until battery flat then charge 100% then do it again.
Thanks for the reply. I bought this laptop pre-owned over the weekend. It was on Big Sur, ran it for two days - this issue didnt occur. I did have to try the OCLP Ventura install a few times till I got the hang of it. Do you think this may also be related to the battery? I was reading that cycle count for this model is at 1000. I am at 962 with full charge capacity at 7072. Is that high?
Thinking about reverting back to Big Sur. Will this still be supported after November 2023?
I think Big Sur will only get a serious flaw update if any and that’s probably if there’s bad press about it.
Ventura works great with same model did you use the usb installer on OCLP to install Create macOS installer option ? I would recommend this as the best option and having another go while it’s new to you also you can have Big Sur and Ventura installed so I would recommend having a partition for Big Sur (if anything goes wrong) and a partition for Ventura.
I think Ventura runs alot smoother, faster on this macbook vs Big Sur. I noticed the performance improvement right away. I ran EtreCheck Pro a few minutes ago. This is the crash from this morning:
2023-07-12 05:12:35 Kernel Panic (2 times)
Details:
panic(cpu 0 caller 0xffffff80046fb928): AppleIntelFramebuffer::setPowe
rState(0xffffffce5dfce000 : 0xffffff7f9988a8ee, 0 -> 2) timed out afte
r 45699 ms @IOServicePM.cpp:5604
Panicked task 0xffffff901a1418b8: 181 threads: pid 0: kernel_task
@TOM1211 "I had success with turning off NVMe PM management in extras then building OCLP " Did you turn this off in the OCLP builder or on the Macbook then run the build? Thinking about re-doing this one. Also, I noticed that during the install, resolution was different - small. Is this because of the two graphic cards? Did you experience this as well? It returned to normal once I got to the actual setup process of Ventura.
Yes turn off run build resolution is out because the graphics cards are no longer supported you have to run root patches after a install Mr. Macintosh does some videos on YouTube that guide you through the process.
Ok, doing that now. Found 3rd party NVMe PM in extras, turned it off. I do recall applying the video patches after install.
Ventura for the first time tried on my Mac Pro 5,1. Several hours, runs perfect.
I apologize as I know this was mentioned before...I have a zoom meeting in an hour and can't get permissions to recognize Zoom. I think there was a "dortaina" patch or something? Please advise---and I apologize.
Try AMFIpass beta4 from https://github.com/dortania/OpenCore-Legacy-Patcher/releases/tag/amfipass-beta-test