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
Ran into problems updating MacMini 2014 running 13.2 to 13.2.1 OTA (OCLP0.6.1).
It ran through the installer, but when booting up into the login screen, it would just keep restarting the login screen. The trackpad responded momentarily, and the keyboard too, but not long enough to get the password in. No matter how fast I was, after 2 key presses, the login page reset itself.
Tried restarting, tried external keyboard, tried unplugging second display, but it’s stuck in this loop.
Anyone else run into this?
It ran through the installer, but when booting up into the login screen, it would just keep restarting the login screen. The trackpad responded momentarily, and the keyboard too, but not long enough to get the password in. No matter how fast I was, after 2 key presses, the login page reset itself.
Tried restarting, tried external keyboard, tried unplugging second display, but it’s stuck in this loop.
Anyone else run into this?
I try different no brands memory got lucky with a USB 3.1 Kingstone 32GB and other with no brand.
Last edited:
Try booting in safe mode.
https://support.apple.com/guide/mac-help/start-up-your-mac-in-safe-mode-mh21245/mac
Have you read the last few pages? Tried the search function? This has been talked about several times recently.
Last edited:
13.2.1/0.6.1 on MBP 8,1, 9,1 and 10,2 ✔️
(On my 10,2 I had continuing errors in course of the installing process, until I used a different pen drive, which a) had 32GB instead of 16, b) was faster, c) didn't have OpenCore installed to it. One or more of these did the
trick. The process went smoothly on 8,1 and 9,1. Had the error alert once or twice when updating to 13.1 and 13.2.)
(On my 10,2 I had continuing errors in course of the installing process, until I used a different pen drive, which a) had 32GB instead of 16, b) was faster, c) didn't have OpenCore installed to it. One or more of these did the
trick. The process went smoothly on 8,1 and 9,1. Had the error alert once or twice when updating to 13.1 and 13.2.)
Last edited:
Did you notice that the Root Patches for macOS 13.2.1 Build 22D68 still use the Apple KDK for 13.2? It seems Apple hasn't released the 13.2.1 KDK yet, as far as I can see on the dev page. I wonder how much that impacts the root patches, and also how soon Apple will release a new KDK for 13.2.1. Any idea?
OCLP has been running pretty well on my MBA 7,2. Upgraded to 13.2.1 yesterday also without issue and was prompted to reinstall the root patches.
The install went fine (and my machine is working), but before it prompted me to reboot I got a system notification to do something in System Settings about having to give something permissions. When I clicked to open system settings nothing happened and nothing looks to be needing my approval, but the message was gone so now I don't know where else to check. Do I need to do anything or am I good as is?
The install went fine (and my machine is working), but before it prompted me to reboot I got a system notification to do something in System Settings about having to give something permissions. When I clicked to open system settings nothing happened and nothing looks to be needing my approval, but the message was gone so now I don't know where else to check. Do I need to do anything or am I good as is?
Well thought I’d give the latest 6.2 nightly a whirl following the success of others - but unfortunately i now have an iMac paper wieight again.
patched the boot volume with latest update - ok
installed ventura 13.2.1 over the top of a perfectly working monterey
booted into Ventura 13.2.1 fine
installed first set of post fix patches - got Wi-Fi working but no BT, using a USB2 hub with external keyboard and mouse
Working to a point, no GPU acceleration, this is an old NVIDIA GPU in this 10,1 iMac
attempted to install post fixes again - picked up legacy usb 1.1, legacy wireless (weird as this was working ish) and NVIDIA Tesla something or other.
Installed these fine, no errors, downloaded the latest KDK file etc again, no issues
rebooted and back stuck at Apple logo again with the same error in verbose mode Ive posted previously.
I keep thinking that this will just work.
Can the OCLP dev’s be made aware of this issue, happy to test any possible solutions
thanks again folks - this is still a work in progress on these old dual core iMac‘s
You were giving OCLP script permission to re-install the post-install patches (which were wiped by the 13.2.1 upgrade). You don't need to do anything else.
The 13.2.1 upgrade went well on my MBP6,2 patched with OCLP 0.6.1. Very pleased to see the hackintosh and real Mac communities jointly realizing the benefits of OpenCore.
I recommend a fresh install not leave anything from the old system to prevent some weird issues
Everything was good and two weeks of few problems, now I get a random "total freeze" when I open "photos" after a day or so with no problems. Everything freezes and I have to hold down the power button to reboot. Is anyone else experiencing this? See my setup below....
late 2015 iMac17,1 (Core i5) with AMD M395 running Ventura 13.2.1 with nightly OCLP v0.6.2 pretty smooth! Wonderful =)
kudoz to the DEVs!!
kudoz to the DEVs!!
(Same system as yours) Does playing back movies in "Photos" work? That caused a "Beach Ball" on my system. (Reverted back to Monterey).
Hello! = )
Im Using Mac Pro 2013 with Ventura 13.2. Today a weird crash happened during music production Studio one 6.
Booth monitors went black.
Something with the graphic drivers!
AMDMTLBronzeDriver
Anyone?
The log says:
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 0x0000000000000208
Exception Codes: 0x0000000000000001, 0x0000000000000208
VM Region Info: 0x208 is not in any region. Bytes before following region: 140737488113144
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
shared memory 7ffffffc5000-7ffffffc6000 [ 4K] r-x/r-x SM=SHM
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 AMDMTLBronzeDriver 0x10c2d71e5 amdMtlBronzeCopyFromTextureToTexture(BronzeMtlBlitCmdEncoder*, id<MTLTexture>, unsigned long, unsigned long, MTLOrigin, MTLSize, objc_object<MTLTexture>, unsigned long, unsigned long, id<MTLTexture>) + 119
1 AMDMTLBronzeDriver 0x10c2d7168 -[BronzeMtlBlitCmdEncoder copyFromTexture:sourceSlice:sourceLevel:sourceOrigin:sourceSize:toTexture:destinationSlice:destinationLevel:destinationOrigin:] + 94
----------
Im Using Mac Pro 2013 with Ventura 13.2. Today a weird crash happened during music production Studio one 6.
Booth monitors went black.
Something with the graphic drivers!
AMDMTLBronzeDriver
Anyone?
The log says:
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 0x0000000000000208
Exception Codes: 0x0000000000000001, 0x0000000000000208
VM Region Info: 0x208 is not in any region. Bytes before following region: 140737488113144
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
shared memory 7ffffffc5000-7ffffffc6000 [ 4K] r-x/r-x SM=SHM
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 AMDMTLBronzeDriver 0x10c2d71e5 amdMtlBronzeCopyFromTextureToTexture(BronzeMtlBlitCmdEncoder*, id<MTLTexture>, unsigned long, unsigned long, MTLOrigin, MTLSize, objc_object<MTLTexture>, unsigned long, unsigned long, id<MTLTexture>) + 119
1 AMDMTLBronzeDriver 0x10c2d7168 -[BronzeMtlBlitCmdEncoder copyFromTexture:sourceSlice:sourceLevel:sourceOrigin:sourceSize:toTexture:destinationSlice:destinationLevel:destinationOrigin:] + 94
----------
I got a message about "approving Intel 5000" or something video card/memory...I clicked okay and all was good. I never Got that message before and it was not an OCLP message. BTW, I check the hardware in system report and everything is listed correctly:
Intel Iris Pro:
Chipset Model: Intel Iris Pro
Type: GPU
Bus: Built-In
VRAM (Dynamic, Max): 1536 MB
Vendor: Intel
Device ID: 0x0d26
Revision ID: 0x0008
Metal Support: Metal 2
Displays:
Color LCD:
Display Type: Built-In Retina LCD
Resolution: 2880 x 1800 Retina
Framebuffer Depth: 24-Bit Color (ARGB8888)
Main Display: Yes
Mirror: Off
Online: Yes
Automatically Adjust Brightness: Yes
Connection Type: Internal
Last edited:
Since the KDKs seem to differ only in parts that do not prevent proper patching for now, it is not urgent to get the KDK update from Apple soon. The patcher does a good job in determining the most recent suitable KDK for the job...