macOS 14 Sonoma on Unsupported Macs Thread

[davidlv]

And it is not just the Mist download. When I finally got OCLP 1.2n to successfully download what it claimed to be 23B74, OCLP 1.2n then goes on to build 23B69 as above.

Something is very amiss with your network or ISP if you can't download a macOS installer. That said, have you tried MDS? https://twocanoes.com/knowledge-base/downloading-macos-installers-with-mds/

 

[nekton1]

Just updated MacMini 7,1 from 14.0 final on OCLP 1.1 to 14.1 final on OCLP 1.2n using a FULL booter/installer USB built using OCLP 1.2n. It stalled at the last boot stage with the progress bar about 1/3rd complete. Forced a restart from the Power button with [Shift] + [Enter] keys pressed and it completed the boot to the Desktop and flashed a message about updating to OCLP 1.2n. Did the update and rebooted and it completed. Then did a final Post-install Root Patch (that I not sure was necessary) and rebooted and all seems fine.

Something is very amiss with your network or ISP if you can't download a macOS installer. That said, have you tried MDS? https://twocanoes.com/knowledge-base/downloading-macos-installers-with-mds/

There is nothing amiss with my network but there was something amiss at the Apple servers; it did finally download using 1.2n about 2 hours after the first failed tries; Mist also worked at first attempt.

 

[davidlv]

Just updated MacMini 7,1 from 14.0 final on OCLP 1.1 to 14.1 final on OCLP 1.2n using a FULL booter/installer USB built using OCLP 1.2n. It stalled at the last boot stage with the progress bar about 1/3rd complete. Forced a restart from the Power button with [Shift] + [Enter] keys pressed and it completed the boot to the Desktop and flashed a message about updating to OCLP 1.2n. Did the update and rebooted and it completed. Then did a final Post-install Root Patch (that I not sure was necessary) and rebooted and all seems fine.

There is nothing amiss with my network but there was something amiss at the Apple servers; it did finally download using 1.2n about 2 hours after the first failed tries; Mist also worked at first attempt.

Yeah, strange things can happen on the net, downloads not completing, mail getting lost in the ether, and whatnot. You previously said Mist downloaded the wrong updater. Was that wrong? I wonder if Mist is reliable?

 

[rbart]

Hey all, wanted to find out the status of 3D acceleration and VMWare under Sonoma. Right now, it's not a major deal as I still have Monterey I can go back to and have all the fine details work. However, I did hear that it was working in 1.1.0 while it was in nightly stage, and then they pulled it. Have they put it back into 1.2? I think as far as anything I'd need this would be the only thing not working as it should. However with desktop environments such as Cinnamon under Mint, I can use software rendering mode to get around this while I wait for a fix.

Anyway, does anyone know?
Thanks

This acceleration was supposed to work only on intel iGPUs
Finally they have noticed it was not working.

 

[mitch751]

Mac mini 2012 i7, upgraded from 14.0 OCLP 1.1 ... it stuck at the installation page (Apple Logo) for hours and still can't complete, created a new OS USB installer with the same result.

 

[Pachnes]

This acceleration was supposed to work only on intel iGPUs
Finally they have noticed it was not working.

Hi, what is the latest vmware-tools for darwin? I have got darwin 13.0.0 and with it i get a white background picture.

 

[PropClear]

Mac mini 2012 i7, upgraded from 14.0 OCLP 1.1 ... it stuck at the installation page (Apple Logo) for hours and still can't complete, created a new OS USB installer with the same result.

Try to simply switch off your mac and select your Sonoma Boot partition with Shift+Enter for safe mode startup, complete your 14.1 update and use OCLP to patch your system - good luck!

 

[Sven G]

Updated to 14.1 on a rMBP 10,1 2012. As others have reported, install hung at 30 % or so on last reboot.
Needed to safe boot to finish the install. All good after finishing the install in safe mode and applying patches in safe boot also.

Exactly the same here (MBP11,3)…

(BTW, safe mode finally works again in Sonoma, also after having installed the system: well, great! )

 

[Sven G]

… Looks like this is fixed in the latest 1.2.0n:

• Add new Launch Daemon for clean up on macOS updates
  • Resolves KDKless Macs failing to boot after updating from 14.0 to 14.x
  • /Library/LaunchDaemons/com.dortania.opencore-legacy-patcher.macos-update.plist

 

[davidlv]

… Looks like this is fixed in the latest 1.2.0n:

• Add new Launch Daemon for clean up on macOS updates
  • Resolves KDKless Macs failing to boot after updating from 14.0 to 14.x
  • /Library/LaunchDaemons/com.dortania.opencore-legacy-patcher.macos-update.plist

The latest (for a while) OCLP v1.2.0n dated 10-26-23 12:53
perfect on my iMac 15,1 late 2014

 

[0134168]

I thought I took better notes, but apparently not. I don't remember whether my last full macOS installs were performed with OCLP-built macOS installer or "raw" installer download from Apple. I will need to test again. Thanks.

@******* Your response made me realize that we probably need to follow some loose guidelines for minimal info included when posting requests for assistance. Requests for help should probably include the following:

• OCLP Version Number (and if not release OCLP build, the date source was downloaded from GitHub and python version used to build OCLP)
• macOS Version Number
• Clean macOS install, macOS upgrade (and from the previous macOS version) or macOS install over a previous install?
• Was macOS installer downloaded from Apple or built with OCLP?
• If a macOS upgrade, was upgrade performed via OTA or via macOS installer over the previous macOS?
• Was "Build and Install Open Core" performed on the target Mac or on a different Mac?
• Target SMBIOS Model
• AMFI and Library Validation enabled or disabled

Nice advices. 👍🏻

 

[0134168]

14.1 is nhere. Gonna give a try right now

 

[Portiere]

Successfully installed 14.1/OCLP 1.2.0n (on main SSD), on internal SSD and external USB (SSD) of my main MacMini L2012.
All works fine.
Thanks to all developers.
Total time 1.h 50 m downloading assistant package, installing on both disks, OCLP built and installed (only on Crucial main SSD) without any modifications and root patches too.
Don't need any USB thumb.

 

[OKonnel]

Temporary FIX for macOS Sonoma related to Menu Bar Icons disappearing after standby.
While we wait for the OCLP Developers to fix the problem, open the Terminal and type exactly:

killall Dock

[Important: respect lowercase and uppercase letters and the space! The k in killall lowercase and the D in Dock uppercase]
Press enter and... boom; the Icons immediately return to their place without having to click individually on the Bar to make them reappear one by one.

 

[Izzy67]

The latest (for a while) OCLP v1.2.0n dated 10-26-23 12:53
perfect on my iMac 15,1 late 2014

did you had issues with Sonoma 14.0 and OCLP 1.0.1, i get stuck with login window, could not type the PW and screen turned black after a few second for a few seconds in a loop. even did a complete reinstall, had the same issue.

 

[MacinMan]

This acceleration was supposed to work only on intel iGPUs
Finally they have noticed it was not working.

What do you suggest ? As mentioned, it's not critical right now since Monterey is still supported for the next year, and there are some things I can do that don't make a difference whether, or not, 3D acceleration is on, or off for the guest OS. I guess what I'm asking is, in the long haul, is Open Core Legacy Patcher a reliable solution for someone who dep0ends on the GPU more than normal, even if it's not gaming, but stuff like video, editing, Virtual Machines, etc.

I'm just doing my best to answer these questions now, before I completely lose support for my system, and know what my best options are for my workflow / circumstances. Right now, on a scale from 1 to 10, I would give current open core an 8 1/2 in terms of satisfaction of it working for me. This score is based on all the major parts working, but some of the more fine tuned stuff needs work still.

 

[rbart]

GPU acceleration works for most activities with OCLP
But as we are using patched drivers, we can have some glitches or issues (like in VMware fusion )
OCLP developers won’t guarantee all is working perfectly
It’s reverse engineering , reuse of old drivers in a newer system
They can’t redo all Apple work
For my usage I need OCLP or put my iMac in the trash
I think it’s a valid solution for my usage

 

[lonesoul]

Guys FYI from the OCLP discord, I guess do not rush to update to 14.1...

It appears that the 14.1 update is causing kernel panics for some people; so (as always) please wait for further information before updating any machines you aren't prepared to break. (The exact problem, or existence of a problem, isn't known yet. Just a reminder!

 

[MacinMan]

GPU acceleration works for most activities with OCLP
But as we are using patched drivers, we can have some glitches or issues (like in VMware fusion )
OCLP developers won’t guarantee all is working perfectly
It’s reverse engineering , reuse of old drivers in a newer system
They can’t redo all Apple work
For my usage I need OCLP or put my iMac in the trash
I think it’s a valid solution for my usage

I realize it's not a perfect solution, and I never expected it to be, and that's why having an Intel based Mac gives me more options on which OS to run. I'm just trying to decide which that will be, and wanted to give open core a reasonable chance. I would like to find a good Linux on Mac community, but that's been tough to find. However, that's the other option I'm looking at. I've considered Windows, but Intel Macs don't meet Windows 11 requirements, and Windows 10 only has a couple more years of support.

 

[hvds]

… Looks like this is fixed in the latest 1.2.0n:

• Add new Launch Daemon for clean up on macOS updates
  • Resolves KDKless Macs failing to boot after updating from 14.0 to 14.x
  • /Library/LaunchDaemons/com.dortania.opencore-legacy-patcher.macos-update.plist

MBP11,1: now running 14.1. All fine when using latest 1.2.0n.

As explained in the OCLP commits:
It is a "KDK-less" Mac so after installation, booting first failed due to some outdated kexts in /Library/Extensions. The first two in the attached screenshot are the culprits. Removing them manually lets the system boot, as does usage of the latest 1.2.0n.

Now latest 1.2.0n in EFI and used for root-patches. Root-patching then installed the proper kexts to /L/E.

Have observed possible negative effects of old files in /L/E before OCLP times already.

Thanks to the developers for the super-quick response!

 

[JedNZ]

Successfully installed macOS 14.1 over my Ventura install (which I've only used for testing) on my cMP 4,1>5,1 (with BootROM reconstruction by way of @tsialex ). See sig for my hardware setup.

OCLP 1.1 – MyBootMgr 0.9.5a – macOS 14.1 Sonoma

The steps I took (may help those using RefindPlus|OpenCore systems (MyBootMgr):

1. Booted into my Mojave SSD drive.
2. Created Sonoma USB stick with OCLP.
3. Copied the OC folder on the Sonoma USB stick>EFI partition to my EFI>EFI>OC_EXT directory - changed LauncherOption to "Disabled", and did the same on my Sonoma USB stick.
4. Booted into Ventura and uninstalled OCLP post install patches.
5. On the Desktop,I double clicked on Install macOS Sonoma.app of my Sonoma USB stick and upgraded to Sonoma over the top of Ventura.
6. Couple of restarts. Love how OCLP picks up and offers to install the patches.
7. Boom. macOS Sonoma 14.1 on this 14 year old cMP.

No Bluetooth. Reset NVRAM (three restarts) but no dice with the BT (BCM94360CD) upgrade (works fine in everything from Ventura and earlier macOS's). OCLP instructions suggest a couple of restarts and it might come right. Will try that.

But man, Sonoma is silky smooth and buttery slick. Haven't installed my normal suite of apps yet. I assume I can migrate (using MA) my Monterey apps across and it doesn't change (or delete) anything on my production Monterey drive? Will give it a go unless there's advice not to.

 

[m4v3r1ck]

Some more insights about the macOS Sonoma 14.1 update:

4 Reasons Not to Install macOS Sonoma 14.1 & 11 Reasons You Should

 

[luckyduke23]

Temporary FIX for macOS Sonoma related to Menu Bar Icons disappearing after standby.
While we wait for the OCLP Developers to fix the problem, open the Terminal and type exactly:

killall Dock

[Important: respect lowercase and uppercase letters and the space]
Press enter and... boom; the Icons immediately return to their place without having to click individually on the Bar to make them reappear one by one.

Thanks for this advice. You seem to have a similar machine like me. Did you also face other graphic issues after standby mode (no window shadows in light mode, blinking login screen, etc.). I just updated to 14.1. and don't know yet if the problem persists. Earlier update to OCLP 1.1.0 did not solve it. But it was impossible anyway to determine which issues were related to OCLP and which to the new MacOS 14. Graphic issues however most likely are caused by OCLP.

 

[luckyduke23]

As some of you may know, it is not yet possible to change the Sonoma login screen wallpaper - that ugly Sonoma vineyard image - while Filevault is active. If anyone comes across a solution, it would be greatly appreciated if it could be posted here. Thanks in advance.

 

[PoloHofer]

First did an OTA update, but hung on login. Right KDK was missing. Then did an Update with an USB Stick. Now all fine when using latest 1.2.0n. No crash in Photo Memories, Continuity Camera works as expected.
All works fine.
Thanks to all developers.

MacintoshPro 11,5