It´s a great great computer. Had one and its already working like a charm in the hands of my brother.
Last edited:
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 14 Sonoma on Unsupported Macs Thread
- Thread starter dhinakg
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
It´s a great great computer. Had one and its already working like a charm in the hands of my brother.
I have a couple of ideas for you but some of it depends on what step you're in for the install.
If you're just installing for the first pass, try resetting your NVRAM. If it's an intel machine, it will be
Turn it all the way off, hold down Option-Command-P-R until you hear startup sound a second time and then release.
Please note that this requires a wired keyboard (not a bluetooth keyboard) to accomplish this. It needs to be plugged into the Mac Mini via usb.
If you're just installing for the first pass, try resetting your NVRAM. If it's an intel machine, it will be
Turn it all the way off, hold down Option-Command-P-R until you hear startup sound a second time and then release.
Please note that this requires a wired keyboard (not a bluetooth keyboard) to accomplish this. It needs to be plugged into the Mac Mini via usb.
I'd do safe mode install after you've tried once the NVRAM has been reset. There's a defined blessed boot in the NVRAM so once you reset and boot up from the USB install stick it will reset the EFI bless boot.
If that doesn't work then try this:
boot up as usual except into safe mode or recovery mode, click on the top to open utilities and terminal
Look on the list from ‘diskutil list’ to find the disk listing with the ventura and find the number corresponding to the EFI listing (typically like 1 or 2) and note which disk it is under (e.g. disk1 or disk2, etc.)
1) type the following in the terminal window replacing ‘X’ and ’N’ with the above disk and EFI numbers (e.g disk1s1). Hit return after typing the following command and there would be a response ‘Volume EFI on disk1s1 mounted’
diskutil mount diskXsN
2) now type the ‘bless’ command to make this the default option for startup. This will not produce any output.
bless --mount /Volumes/EFI --setBoot --file /Volumes/EFI/System/Library/CoreServices/boot.efi
Now restart from scratch and the NVRAM has the 'blessed' EFI boot listing so it should find your boot up stick.
If that doesn't work then try this:
boot up as usual except into safe mode or recovery mode, click on the top to open utilities and terminal
Look on the list from ‘diskutil list’ to find the disk listing with the ventura and find the number corresponding to the EFI listing (typically like 1 or 2) and note which disk it is under (e.g. disk1 or disk2, etc.)
1) type the following in the terminal window replacing ‘X’ and ’N’ with the above disk and EFI numbers (e.g disk1s1). Hit return after typing the following command and there would be a response ‘Volume EFI on disk1s1 mounted’
diskutil mount diskXsN
2) now type the ‘bless’ command to make this the default option for startup. This will not produce any output.
bless --mount /Volumes/EFI --setBoot --file /Volumes/EFI/System/Library/CoreServices/boot.efi
Now restart from scratch and the NVRAM has the 'blessed' EFI boot listing so it should find your boot up stick.
probably if you have the corresponding keys. I think on windows the <alt> key is the command key but not certain. You'll know pretty quick if it works or not because as you hold the keys down it will chime and restart and then chime again. If it's the wrong keys it won't chime and just keep going to the same old boot cycle.
Microsoft PC accessories help & learning
Get help, training, and support for your PC accessories.
| Windows | Macintosh |
|---|---|
| CONTROL | COMMAND (for most shortcuts) or CONTROL |
| ALT | OPTION |
| Windows/Start | COMMAND/Apple |
| BACKSPACE | DELETE |
| DELETE | DEL |
| SHIFT | SHIFT |
| ENTER | RETURN |
You can add Ivy Bridge to this theory. I am on a 9,2 here. Same issue. Btw, no crashes without 1.2.1 patches installed. Normal boot.
Patched with 1.0.1 and 1.3.0n as of today. Issue could be reproduced.
Error log:
Crashed Thread: 3 Dispatch queue: com.apple.coreanimation.pipelines
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: Namespace COREANIMATION, Code 4
spec=PBGRABsovXb_TimgXc_IsrcFmbN3Oc3mtc4nl
Downgrade failed with error: Compiler encountered an internal error
Last edited:
I used to use a Window keyboard on my Mac. Alt was Option and the Window key was Command. The annoying thing was that alt-win are in the opposite order of opt-cmd on most keyboards.
Hi everyone. Can anyone tell me which version of Sonoma and OCLP is more stable with iMac 27" 14.2 late 2013? Thanks.
In this period I am forced to rarely follow the Forum, since I go out often, but today I went back to use my Mac of work and not I want to create problems since I have little time and I couldn't fix.
Reading the last pages, I seem to understand that the best solution (even for everyone) is to stay with Sonoma 14.1 and OCLP 1.2.0. Is this correct?
I wanted to install Sonoma 14.2 beta with the sole aim of running Finder again after logging in as root and also hoping to see Continuity Camera working...,
but I can give up.
Thanks
In this period I am forced to rarely follow the Forum, since I go out often, but today I went back to use my Mac of work and not I want to create problems since I have little time and I couldn't fix.
Reading the last pages, I seem to understand that the best solution (even for everyone) is to stay with Sonoma 14.1 and OCLP 1.2.0. Is this correct?
I wanted to install Sonoma 14.2 beta with the sole aim of running Finder again after logging in as root and also hoping to see Continuity Camera working...,
but I can give up.Thanks
same machine like yours here...14.1.1 runs with no difference to 14.1 but stay away from Betas if it's your workstation...Hi everyone. Can anyone tell me which version of Sonoma and OCLP is more stable with iMac 27" 14.2 late 2013? Thanks.
In this period I am forced to rarely follow the Forum, since I go out often, but today I went back to use my Mac of work and not I want to create problems since I have little time and I couldn't fix.
Reading the last pages, I seem to understand that the best solution (even for everyone) is to stay with Sonoma 14.1 and OCLP 1.2.0. Is this correct?
I wanted to install Sonoma 14.2 beta with the sole aim of running Finder again after logging in as root and also hoping to see Continuity Camera working...,
Thanks
yep, I've stayed with OCLP 1.2 and Ventura 13.6.1
Not interested in riding the bleeding edge only to slide into a pool of rubbing alcohol!
Not interested in riding the bleeding edge only to slide into a pool of rubbing alcohol!
That is what I am doing, 14.1 + OCLP 1.2.1
OCLP 1.2.1 seems to be working well for me (better than 1.2.0) so I would recommend it.
So far as I can determine 14.1.1 only contains a minor fix to the BMW / Car Play issue so not applicable to me.
Re. betas, tried installing 14.2 beta 1 and wasted a lot of time, see my post here. So I agree with @luckyduke23, stay away from betas at the moment unless you're feeling very lucky.
I've also switched to using Firefox for the time being. Safari was causing the fans to run continuously.
Last edited:
Just a little general report to confirm that OCLP can probably get corrupted sometimes. When I shut down my machine last night, it took unusually long and the hard drive was busy. When I booted the machine today, the boot process took longer than usual, and during the installer process at the beginning my desktop was gray instead of showing my regular custom wallpaper, which only came up with a delay. It then took longer than usual for all background applications to start. Working with the machine then seemed normal until I noticed that I could not play videos anywhere (WhatsApp, Youtube, etc.). So I repeated the post-patch, but after a reboot there was no progress. Next, I did a new OCLP build and install, and that got my machine back to healthy behavior after the reboot.
Woh , Sonoma 14.1.1 and Carplay. I thought Carplay works only with IOS.
One can also hit the Space key as soon as OCLP (OpenCanopy) starts and move to the far right entry and do it from there.
My config so far: 4,1 -> 5,1, using OCLP 1.2.1, macOS Sonoma 14.1.1 installed on NVMe Samsung 970
EVO 500GB, rest of the config is on the screenshot.
GPU is Sapphire Radeon RX 580 8GB Pulse (2xHDMI, 2xDP, DVI).
Mac firmware is flashed with EnableGOP 1.4 and it enabled full gray boot screen as you can see.
Also, VideoProc 1.6.1 reports fully supported H.264 and HEVC acceleration.
Its stable and fast. I only wish I can have faster NVMe speed.
EVO 500GB, rest of the config is on the screenshot.
GPU is Sapphire Radeon RX 580 8GB Pulse (2xHDMI, 2xDP, DVI).
Mac firmware is flashed with EnableGOP 1.4 and it enabled full gray boot screen as you can see.
Also, VideoProc 1.6.1 reports fully supported H.264 and HEVC acceleration.
Its stable and fast. I only wish I can have faster NVMe speed.
Attachments
Last edited:
2014 5k iMac ... I think that's iMac 15,1 in OCLP terminology: Sonoma 14.1.1 booted fine after install, then OCLP offered to reinstall root patches. Next reboot hangs 1/2 way through the boot. I've tried clearing NVRAM. I'm building a new OCLP installer now to see if I can fix it that way. Otherwise, is there a way to remove the root patches so I can at least get into the OS to do a backup? Failing that I guess I'll try target disk mode and back it up from my laptop...
Yep, Sonoma on the internal Apple SSD blade (left over from the original Fusion drive, and Ventura 13.6.3 on an external Crucial 512GB MX500 SDD. Using OCLP 1.2.1 release version on the internal SSD. iMac 15,1 i5 from late 2014, Haswell CPU 3.5GHz, AMD R9 M290X 2GB GPU.Is this the same iMac from your Ventura post #7,535??
View attachment 2312142 Hmmm?? Nice iMac, tho.
Last edited:
Haswell is intel, not AMD. Just discussed the issue with an OCLP developer who wrote that AMD GPUs are free of the intel Ivy Bridge and Haswell issues. Your iMac confirms that fact.
Last edited: