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'm sorry, this is my first time posting on this forum. I have the 0.6.8 version of OCLP and 13.6 of Ventura. I tried almost every method I could find online. I created a new user and it worked for 5 seconds then it kicked me out again. I even reinstalled the OS. I used to be on Catalina before and it worked fine. I saw some information about changing the serial number but I don't know if that is only available for Hackintosh.
Use the one printed on the computer’s chassis provided that the logic board hasn’t been replaced.
Isn't this fixed in 0.6.8 for Kepler?
0.6.8 Changelog
………
Add configuration to use media analysis
- On systems that are the primary storage for iCloud Photo Library, media analysis may become unstable if there are a large number of raw faces.
- Applicable to 3802 based GPUs (i.e. Intel Ivy Bridge and Haswell GPUs, Nvidia Kepler GPUs)
I’ve deleted Ventura already so I can’t tell. Seems to be working on Monterey, though
I have a 2015 11,4 running 13.4.1 no problems and a 2009 MBP 5,5 running Monterrey and it's smooth and quick (except maps). I didn't even try Ventura on my 5,5----However, I do have 8 GB RAM and a SSD HD on my 2009. That makes it much faster. Could you upgrade RAM or your HDD?
Very cool! Thank you. That takes the definition of user-upgradable to a whole new level. 😂
Reminds me of my first Mac memory upgrades. I bought many of the initial 128K Macs, upgraded them to 512K and resold them as "Fat Macs" at a decent profit. The upgrade procedure was published in Dr. Dobbs Journal and involved desoldering memory chips, soldering new memory chips and adding a resistor or two and a capacitor. There was more than one time when my newly upgraded Mac booted to a sad face, requiring me to desolder and resolder all memory chips. I was very lucky that all upgraded ultimately worked. This was before surface mounted components, so a much easier job than the MBA upgrade.
Apparently not completely. Live text doesn't work on images for me, only in video and PDF's. We have the exact same imac, does it work on yours?
Was just prompted for an OTA upgrade to Ventura 13.5.2 on my MBP6,2 patched with OCLP 0.6.8. And it's not an RSR.
Interesting. What's the correlation between Apple's release of 13.5.2 and the Devs' release of 0.6.9? (Although I agree that the release of 0.6.9 "soon" is a safe prediction with or without 13.5.2).
rMBP mid 2012 10,1 with 13.5.1 & OCLP 0.6.8 updated OTA to 13.5.2 22G91. It took a long time with several auto-reboots. No issues other than it took a long time, maybe 2 hours?
After logging-in OCLP auto-prompted to reapply post install patches and restart. All seems to be working so far.
After logging-in OCLP auto-prompted to reapply post install patches and restart. All seems to be working so far.
Same smooth upgrade experience on my MBP6,2 (OCLP 0.6.8). Total upgrade was 30-45 minutes with a full installer downloaded via OTA. Maybe the upgrade time difference has something to do with network speed? MY MBP6,2 has an old Arrandale i7 with 8GB DDR3 RAM.
We're on fiber here so unlikely. It felt like watching paint dry, but maybe it just seemed like 2 hours. I didn't actually time it.
edit, later: I realized what happened. Usually I do the updates after it's already silently downloaded and prepped them since that's how I've set it up to handle updates in the Advanced window. Because this update only hit today it hadn't had time to do that, hence it ran much longer than I'd gotten used to.
Last edited:
I know this is weird, but I am having an issue that's supposed to be unrelated, but is a little suspicious. I can't attach to any applications using lldb debugger. I've tried everything until I stumbled upon this thread after searching for "LC_SEGMENT_64 has a fileoff" which is reported by the debugger. I'm able to run and attach GDB to other applications without issue so it seems to be lldb specific.
Interestingly, I'm also running Ventura (13.5, release 22G74) on a MBP 2015 via OCLP 0.6.8, which makes me wonder if this issue is related. I hope this isn't something serious as the log message suggests lldb thinks thinks the dynamic libraries are corrupted.
Other than this issue, my machine is running fine overall with one exception. A few weeks ago, I had problems with FaceTime where I couldn't answer any calls. The Window would hang and clicking on the buttons would do nothing. I had to force quit the application to get things to work again. The FaceTime issue has resolved itself, but I'm completely clueless as to how it resolved itself. Perhaps, it was fixed via an automatic update.
Below is a shortened log:
Interestingly, I'm also running Ventura (13.5, release 22G74) on a MBP 2015 via OCLP 0.6.8, which makes me wonder if this issue is related. I hope this isn't something serious as the log message suggests lldb thinks thinks the dynamic libraries are corrupted.
Other than this issue, my machine is running fine overall with one exception. A few weeks ago, I had problems with FaceTime where I couldn't answer any calls. The Window would hang and clicking on the buttons would do nothing. I had to force quit the application to get things to work again. The FaceTime issue has resolved itself, but I'm completely clueless as to how it resolved itself. Perhaps, it was fixed via an automatic update.
Below is a shortened log:
warning: (x86_64) /System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/31001/Libraries/libGPUCompilerUtils.dylib load command 1 LC_SEGMENT_64 has a fileoff (0x3afca000) that extends beyond the end of the file (0xa9a0), ignoring this section
warning: (x86_64) /System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/31001/Libraries/libGPUCompilerUtils.dylib load command 2 LC_SEGMENT_64 has a fileoff (0x79a98000) that extends beyond the end of the file (0xa9a0), ignoring this section
E+00008.789: Code injection into PID=9654 failed:
Traceback (most recent call last):
File "/Users/bobbrainerd/.vscode/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/adapter/../../debugpy/../debugpy/server/cli.py", line 391, in attach_to_pid
add_code_to_python_process.run_python_code(
File "/Users/bobbrainerd/.vscode/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/pydevd_attach_to_process/add_code_to_python_process.py", line 528, in run_python_code_mac
subprocess.check_call(' '.join(cmd), shell=True, env=env)
File "/usr/local/Cellar/python@3.11/3.11.5/Frameworks/Python.framework/Versions/3.11/lib/python3.11/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command 'lldb --no-lldbinit --script-language Python -o 'process attach --pid 9654' -o 'command..
warning: (x86_64) /System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/31001/Libraries/libGPUCompilerUtils.dylib load command 2 LC_SEGMENT_64 has a fileoff (0x79a98000) that extends beyond the end of the file (0xa9a0), ignoring this section
E+00008.789: Code injection into PID=9654 failed:
Traceback (most recent call last):
File "/Users/bobbrainerd/.vscode/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/adapter/../../debugpy/../debugpy/server/cli.py", line 391, in attach_to_pid
add_code_to_python_process.run_python_code(
File "/Users/bobbrainerd/.vscode/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/pydevd_attach_to_process/add_code_to_python_process.py", line 528, in run_python_code_mac
subprocess.check_call(' '.join(cmd), shell=True, env=env)
File "/usr/local/Cellar/python@3.11/3.11.5/Frameworks/Python.framework/Versions/3.11/lib/python3.11/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command 'lldb --no-lldbinit --script-language Python -o 'process attach --pid 9654' -o 'command..