Sidebar Sidebar
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

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
BuffyzDead said:
Rats !!!

Late 2009 iMac (10,1) is running Sonoma 14.0 (23A344) without any real issues. I am always just hoping, that the very minimal graphic gremlins, keep improving with each OCLP release.

So, ....I updated OCLP from v1.0.1 to v1.1.0, on a Late 2009 iMac (10,1), installing it to the booting SSD EFI, and then applying post install patches and NOW:

Photos continually crashes when launching?

Anyone else? ...should I revert the OCLP install from v1.1.0 back to 1.0.1?
Click to expand...
Might be something needs to be set in the OCLP Settings (preferences) before the Build and Install step. Have you looked carefully in there? Edit: for something different than in your previous install?
 
Last edited:
  • Like
Reactions: K two
@davidlv I fixed it, I did what @houser said inside the open core boot picker, I hit control+enter with the Sonoma drive selecterd. It remembered it this time. It's not a big deal manually selecting it for me, but this way if I reboot and have to step away and I want Sonoma to boot it will now automatically vs booting from Monterey.

Thanks again.
 
  • Like
Reactions: Larsvonhier, houser and INK1
MacinMan said:
Question, I am able to select open core to show the boot picker on startup without having the option key held every time. The issue seems to be, that Open core wants to boot my native install over Monterey by default instead of Sonoma, and the Open core boot loader is on the Sonoma drive since Monterey doesn't need it to run on this iMac. How do I set Sonoma as the default open core selection?
Click to expand...
Try setting the boot disk from the macOS C/P>General>Startup Disk. 🧐
 
  • Like
Reactions: roronl
davidlv said:
Yeah, a separate disk is good indeed for HS. I had it installed in a different Volume and it constantly issued "Incompatible disk" error messages.
BTW, when you can find the time, could you update the links in your signature, now that the nightly is for version 1.2.0 and the release is 1.1.0?
Click to expand...
I get the "Incompatible Disk" error message also when I boot in High Sierra. I believe i't trying to read the Sonoma disk which is APFS. I don't believe APFS was supported natively on HS. It doesn't cause me issues, so I don't question it 🤷‍♂️

My sig is fine. Those link direct to the main pages, not specific versions.

The version posted is what my machine is currently on, not what's available. Where's this 1.2.0 you speak of? Refreshed page. 👍
 
ChrisOSX said:
I get the "Incompatible Disk" error message also when I boot in High Sierra. I believe i't trying to read the Sonoma disk which is APFS. I don't believe APFS was supported natively on HS. It doesn't cause me issues, so I don't question it 🤷‍♂️

My sig is fine. Those link direct to the main pages, not specific versions.

The version posted is what my machine is currently on, not what's available. Where's this 1.2.0 you speak of? Refreshed page. 👍
Click to expand...
Re: "I don't believe APFS was supported natively on HS", no, HS was the first macOS that supported APFS, but evidently that version changed quickly with Mojave and then again with Big Sur (don't know about Catalina). I have never seen that error message using a mix of Big Sur, Monterey, Ventura, or Sonoma, But Mojave is also questionable. I do not know the specifics about the changes in the APFS protocol, just that I have never seen that error message with various OS installs (Big Sur, Monterey, Ventura, or Sonoma) on an external disk.
 
  • Like
Reactions: K two and ChrisOSX
******* said:
Nop. The last time I saw that was in Monterey. In Ventura and Sonoma, even during the last step of installation Migration Assistantant dont work. Al least, for me.
Click to expand...
No issues using MA with Sonoma 14.0 after building macOS installer with OCLP 1.0.1. My full specs are below. The steps I followed are:
  1. Connect Mac to wired Ethernet and leave connected during entire macOS installation and MA
  2. Create Sonoma 14.0 installer with OCLP 1.0.1. Allow OCLP to download new macOS installer (not use existing). I didn't test use of existing installer, but I don't know why it would be different.
  3. After OCLP creates installer USB, allow OCLP to "Build and Install Open Core" to USB. I ran OCLP on the target Mac running Ventura 13.6.
  4. Reboot Mac and boot from installer USB created in Step 2 with EFI in Step 3
  5. After macOS Sonoma 14.0 installation is almost complete, macOS installer prompts to migrate data/apps/settings. I chose my Ventura 13.6 Volume as my source volume and allowed MA to transfer.
  6. After MA finished, rebooted. All good with Sonoma 14.0. No issues. Did not need to apply post install patches, so I assume they were applied during the installer creation and macOS installation, but they did not interfere with MA. Note that the source Ventura 13.6 Volume is patched with OCLP 0.6.8. I did not need to revert any OCLP post-install patches on the source or destination volumes.
System Specs:
  • OCLP 1.0.1
  • Clean installation of macOS Sonoma 14.0 in newly added APFS Volume (added to existing APFS container)
  • macOS Sonoma 14.0 Installer USB created with OCLP 1.0.1
  • macOS Sonoma 14.0 Installer and Open Core EFI built on Target Mac in Ventura 13.6
  • SMBIOS: MBP6,2 (Graphics: non-metal NVidia Tesla)
  • AMFI and Library Validation fully enabled (check boxes unchecked in OCLP GUI before "Build and Install Open Core")
EDIT: Just to be sure the post-install patches were already applied following complete macOS Sonoma 14.0 install and MA, I ran OCLP and selected post-install patcher. Patches were already applied.

EDIT2: Be careful when you migrate from a volume with Time Machine configured. The new macOS volume will have the same Time Machine configuration. If you alternately boot the old and new macOS volumes, they can both clobber the same Time Machine backup volume (filling it more quickly).
 
Last edited:
  • Like
Reactions: hvds and perez987
BuffyzDead said:
Rats !!!

Late 2009 iMac (10,1) is running Sonoma 14.0 (23A344) without any real issues. I am always just hoping, that the very minimal graphic gremlins, keep improving with each OCLP release.

So, ....I updated OCLP from v1.0.1 to v1.1.0, on a Late 2009 iMac (10,1), installing it to the booting SSD EFI, and then applying post install patches and NOW:

Photos continually crashes when launching?

Anyone else? ...should I revert the OCLP install from v1.1.0 back to 1.0.1?
Click to expand...
I have had this issue since Apple released the 23A344 KDK, regardless the OCLP version you are using. It seems specific to non metal machines.
 
  • Like
Reactions: hvds
@davidlv @deeveedee @air.man
Photos was working perfectly under OCLP v1.0.1

The only thing that changed was updating OCLP to v1.1.0

Should I revert back to OCLP v1.0.1? Or wait for the release of Sonoma v14.1?
(all in reference to a Late 2009 iMac 10,1. Running Sonoma 14.0)
 
Last edited:
I stand corrected. If others are using Photos on non-metal Macs, then that's great.

EDIT: Just launched Photos on my MBP6,2 (non-metal Nvidia Tesla) patched with OCLP 1.0.1. Photos launches without crashing. I don't use it (and thus don't have any photos to play with), but the app doesn't crash when opening (not much of a test).
 
Last edited:
I was going to ask, is the photos problems mainly regarding non metal macs? I used it a bit ago today under Sonoma 14.0, and Open Core 1.1.0 on my late 2015, 27" iMac and had no issues cleaning up some photos taken by mistake and deleting them.
 
rehkram said:
Do you recall which version of Catalina you were running at that point? The last version was 10.15.7. This may be significant because it contained, for the rMBP10,1 and some other models anyway, a firmware update.

If you want to check whether the firmware is up to date on your Mac I highly recommend using SilentKnight - if you don't have it here's the link to the download selection page: https://eclecticlight.co/lockrattler-systhist/
Click to expand...

It was definitely the final version. I've managed to reinstall and fully update Catalina. Much obliged with the SilentKnight recommendation. Here's the info:
siOQ7BH.png

From what I can see, the firmware is up to date. When I erased the drive and used Internet Recovery to restore the OS, Mountain Lion was installed. I allowed the Mac to sleep for a prolonged period and it didn't freeze on me upon resuming - which has bolstered my suspicions that this is an issue caused by more recent versions of macOS.
 
  • Like
Reactions: rehkram
Anyone having any luck getting into Safe Mode with oclp 1.1.0 Release and Sonoma 14.1 Beta 3?
"Shift+ Enter" does not work.
After applying root patches my cMP wont boot...
My way out for now is reinstalling 14.1 again lol.
Is the answer amfi?
Or is there a way to Revert root patches when you can't boot!
Cheers!
 
Last edited:
MacRumors3590 said:
Anyone having any luck getting into Safe Mode with oclp 1.1.0 Release and Sonoma 14.1 Beta 3?
"Shift+ Enter" does not work.
After applying root patches my cMP wont boot...
My way out for now is reinstalling 14.1 again lol.
Is the answer amfi?
Or is there a way to Revert root patches when you can't boot!
Cheers!
Click to expand...
Does this help? Haven't tried to do this and certainly haven't tried it in single user mode, but maybe you can.

CleanLE-Improved.png


Alternatively, you might be able to add an APFS volume, perform a clean macOS install and migrate from the unbootable macOS.
 
  • Like
Reactions: MacRumors3590
BuffyzDead said:
@davidlv @deeveedee @air.man
Photos was working perfectly under OCLP v1.0.1

The only thing that changed was updating OCLP to v1.1.0

Should I revert back to OCLP v1.0.1? Or wait for the release of Sonoma v14.1?
(all in reference to a Late 2009 iMac 10,1. Running Sonoma 14.0)
Click to expand...
True Photos no long work with OCLP 1.1.0. It was was working previously with 1.0.1. Ther Error Report says

"Namespace SIGNAL, Code 4 Illegal instruction: 4"
 
Last edited:
  • Like
Reactions: Kent W and deeveedee
FYI: 23B73 and 1.1.0 work as expected without issues on this 9,2. Overall the setup feels reliable.


Minor, non important/urgent reproducible issue: Photos crashes when trying to use Memories
Crashed Thread: 3 Dispatch queue: com.apple.photos.metalrenderer-compile
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)


Thank you very much for your hard work!
 
Last edited:
  • Like
Reactions: deeveedee
I have got a question ...
My Mac is still supported by Monterey. I have installed Sonoma with OCLP and it works pretty well but I am wondering about the way to continue to get some firmware updates. Monterey will continue to be supported this year and Apple could issue some security firmware updates.
To get them, do I need to have a Monterey volume on my internal drive ?
Is it possible to get firmware updates if I have a Monterey volume on an external thunderbolt drive ?
Is there another way to get firmware updates without keeping a Monterey OS on my Mac ?
 
Neutral Singh said:
Is Touch-bar working in MBP 13 & 15 2016 / 2017 models after upgrading to OCLP 1.1.0 with a clean install?
Click to expand...
Touch Bar & Touch ID working ok on my 2016 MacBook Pro 13,2 running 14.1 RC and OCLP 1.1.0 Release, though it was an OTA update from 14.0.
 
Last edited:
  • Like
Reactions: deeveedee
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back