macOS 14 Sonoma on Unsupported Macs Thread

[macoda]

Sonoma 14.2 installed on an iMac 11,3 (AMD Radeon HD 5750) using OCLP 1.3.0 and Wifi won't enable for me. Also getting a blank white wallpaper, irrespective of which one I choose. I've done a 4x NVRAM reset after the install. It's installed fresh on to a new partition on a drive which has High Sierra and Monterey on separate partitions. No LittleSnitch, VPN etc. If I connect to my network over Wifi at the boot picker and boot in to Sonoma I get a black screen white apple hang. And yes, I have tried turning it on and off again, several times

 

[Macdctr]

Since OCLP 1.3.0 was released I was able to install Sonoma 14.3 Beta on the following assets without any issue:
- Mid 2015 2.8GHz i7/16GB DG 15-inch MBP
- Early 2015 3.1 GHz i7/16GB 13-inch MBP
- Early 2015 2.9GHz i5/16GB 13-inch MBP
- Early 2015 2.2GHz i7/8GB 11-inch AIR

I have one remaining computer to update which I plan to do tonight. So far with the assets I have updated, I have not had any issue while using them. Having multiple windows open, streaming multiple videos with an external display attached to my MBPs (YouTube on one display and Apple TV on the other display), having multiple apps open (Word, PowerPoint, Pages, Numbers for example), and building bootable thumbdrives. No glitches observed so far so I feel comfortable enough with using the current OCLP to update my 2012 MP. The Dev team have really done an amazing job with this version of OpenCore, thanks to everyone involved!

 

[INK1]

On my iMac 11,3 I have installed Sonoma 14.1.1 with OCLP 1.3.0. Parallels 19.2.0 is running fine with Windows 11.
On my MBP 11,5 I have installed Sonoma 14.2 with OCLP 1.3.0. MacOS is running fine, but I have problems with Parallels 19.2.0 running Windows 11. Was working fine with Ventura 13.6.1 on this machine, but now Windows 11 is without any text in menus and dropdown menus. Is there any solution? or do I have to get back to Sonoma 14.1.1 or even Ventura again?

 

[Ready-for-Apple]

Hi @Ready-for-Apple! After having downloaded and installed a new version of OCLP, of any type, official or nightly, I always restart the Mac and at the sound of the gong, holding down the Option key, I waited for the EFIBoot icon to appear and by clicking on it I load the EFIBoot into NVRAM. Otherwise, as far as I know, the Mac will continue to use the OCLP version it's already using.
Having said that, even if you want to tell me that when OCLP updates it automatically overwrites the NVRAM (which I wasn't aware of until now and I don't know where it is written), however - if you review my post in point 3) I explained that I had deleted the NVRAM. For this reason, therefore, it is necessary and essential to carry out the procedure described in point 4) otherwise the Mac will not start.
I would like to point out that I added this point to help all those who have various problems and since they are beginners discover that deleting the NVRAM can only be useful after having written many posts looking for help. Cleaning the NVRAM, after all, never hurts and only wastes a few seconds on boot...
Am I wrong?... Thanks for any corrections

So either I don't understand your explanations (maybe cause I'm no native English speaker) or you are missing EXACT step-by-step instructions instead of the 6 points.🤷‍♂️

Yes, it can help to delete the NVRAM AFTER an OCLP update and BEFORE a macOS update (supposedly you should do this 4 times in a row) by pressing the space bar when the "Volumes" appear and thus, among other things, the "Delete NVRAM" appears on the far right.




And also "yes" if you then hold down the option key while pressing the desired volume to be started has an advantage - namely that the system knows in future which of the possibly several volumes should serve as the start volume. Under the selected start volume, the arrow pointing upwards then becomes a rotating arrow.




However, this is not absolutely necessary.😉

 

[Ready-for-Apple]

I also need your help:
How can I change the name of the volume at startup?



It still shows "macOS Ventura", although I have already changed the name in Disk Utility and it is also displayed correctly on the desktop...



🙏🏻 Thank you very much for your help.

 

[K two]

I also need your help:
How can I change the name of the volume at startup?
View attachment 2324958


It still shows "macOS Ventura", although I have already changed the name in Disk Utility and it is also displayed correctly on the desktop...
View attachment 2324959


🙏🏻 Thank you very much for your help.

Re-install EFI? 🤷‍♂️

 

[MacGeekYYC]

On my MBP 11,5 I have installed Sonoma 14.2 with OCLP 1.3.0. MacOS is running fine, but I have problems with Parallels 19.2.0 running Windows 11. Was working fine with Ventura 13.6.1 on this machine, but now Windows 11 is without any text in menus and dropdown menus.

Possibly Parallels 19.2 and/or the Windows 11 graphics driver under the VM aren't handling the discrete graphics switching properly on the MBP 11,5. First thing I would check is the setting shown in this tech note.

KB Parallels: How does Parallels Desktop for Mac work with Mac video cards?

To make sure this option is enabled go to > > >

kb.parallels.com

EDIT - it looks like there have been some issues with the AMD driver under Windows 11. Most recent release was December 5th. Next thing I would try is a running Windows update in the VM and see if it finds a new driver from Microsoft. If not, then download the latest AMD driver from their site.

 

[paalb]

So either I don't understand your explanations (maybe cause I'm no native English speaker) or you are missing EXACT step-by-step instructions instead of the 6 points.🤷‍♂️

Yes, it can help to delete the NVRAM AFTER an OCLP update and BEFORE a macOS update (supposedly you should do this 4 times in a row) by pressing the space bar when the "Volumes" appear and thus, among other things, the "Delete NVRAM" appears on the far right.

View attachment 2324953

cmd-alt-P-R is just another way of doing the same thing. The difference is that it works without OCLP too.

 

[macoda]

Sonoma 14.2 installed on an iMac 11,3 (AMD Radeon HD 5750) using OCLP 1.3.0 and Wifi won't enable for me. Also getting a blank white wallpaper, irrespective of which one I choose. I've done a 4x NVRAM reset after the install. It's installed fresh on to a new partition on a drive which has High Sierra and Monterey on separate partitions. No LittleSnitch, VPN etc. If I connect to my network over Wifi at the boot picker and boot in to Sonoma I get a black screen white apple hang. And yes, I have tried turning it on and off again, several times

Applying Root patches resolved the wifi issue. The animated wallpapers don't work but the dynamic ones do. Overall OS response is laggy. Is 12Gb RAM what's possibly tripping it up?

 

[ElSooz]

This comment is quite alarming. I have just updated my MBP 11,3 (which has an Nidia card) to Sonoma 14.2 OCLP 1.3.0 and was about to do the same for a MBP 11,4 (which has no card.) I also have iphone and ipads. What actually triggers this distressing event? How can I make sure to avoid it??

❗️DON'T try to set a Memoji cause this freezes or crashes with no chance of revert the system.
This happened to me by accident last night, as iOS 17.1+ offers "Contact Photo" and "Poster" as new features in the Contacts app. Memoji in "Contact photo" is synchronized with iCloud User pic + Mac Login pic❗️😢

After that, despite several hours of trying, nothing could be recovered and I had to reset my 15" rMBP 11,2 mid 2014.😢

 

[Macdctr]

deleted, see below post.

 

[Macdctr]

I just updated my 5,1 MP to Sonoma 14.3 Beta using OCLP 1.3.0. The update process was smooth and trouble free and I now have the most current MacOS on all my assets (see sig below). The OCLP Dev team has done amazing work to allow us to keep our computers current with OS that is still compatible with our hardware.

 

[OKonnel]

I haven’t used recently, but isn’t there an action record button that turns everything into a script eventually?

Of course @amaze1499, actions can be recorded. But the problem (at least for me…) is how to make a script or other method automatically recognize when the Mac wakes up from Sleep mode and then start a background process to give the “killall Dock” command; so the script or utility must close its window if it cannot be hidden during its execution.

 

[Sven G]

I created a small 64 GB additional volume for Ventura on my main internal Sonoma SSD, installed the latest Ventura on it, and also installed Parallels Desktop and other virtualizers on it: and, indeed, paravirtualized graphics still works perfectly in Ventura for macOS VMs, also with the latest Parallels Desktop 19.2.0. Is it known why it doesn't work in Sonoma? IIRC, some time ago, an attempt was made to make it work by downgrading some kext/framework, but it didn’t have any effect: so, will there be other ways to be able to enable paravirtualization in Sonoma…? Parallels still has quite good support for macOS VMs, so it’s a pity that they don’t work anymore in Sonoma hosts…

 

[Sven G]

On my iMac 11,3 I have installed Sonoma 14.1.1 with OCLP 1.3.0. Parallels 19.2.0 is running fine with Windows 11.
On my MBP 11,5 I have installed Sonoma 14.2 with OCLP 1.3.0. MacOS is running fine, but I have problems with Parallels 19.2.0 running Windows 11. Was working fine with Ventura 13.6.1 on this machine, but now Windows 11 is without any text in menus and dropdown menus. Is there any solution? or do I have to get back to Sonoma 14.1.1 or even Ventura again?

Sometimes, it happens that there isn’t any text in menus, etc. after resuming a Windows 11 VM: so, one can either reboot the VM, or more easily simply relaunch the Windows Explorer (can be done by opening the Task Manager, after right-clicking on the taskbar). Don’t know if this is a Parallels bug, or something related to OCLP on specific machines…

 

[StefanAM]

Hey guys! I need an IORegistry dump from macbookair7,2. Thank you!

 

[INK1]

Possibly Parallels 19.2 and/or the Windows 11 graphics driver under the VM aren't handling the discrete graphics switching properly on the MBP 11,5. First thing I would check is the setting shown in this tech note.

KB Parallels: How does Parallels Desktop for Mac work with Mac video cards?

To make sure this option is enabled go to > > >

kb.parallels.com

EDIT - it looks like there have been some issues with the AMD driver under Windows 11. Most recent release was December 5th. Next thing I would try is a running Windows update in the VM and see if it finds a new driver from Microsoft. If not, then download the latest AMD driver from their site.

Thank you for answering me. I have tried the different settings without luck. As it was working in Ventura, I am more inclined to think something has changed in Sonoma. Strange enough an old Windows 7 program is working fine.
The start menu shows up with all icons, but without any text.

 

[INK1]

Sometimes, it happens that there isn’t any text in menus, etc. after resuming a Windows 11 VM: so, one can either reboot the VM, or more easily simply relaunch the Windows Explorer (can be done by opening the Task Manager, after right-clicking on the taskbar). Don’t know if this is a Parallels bug, or something related to OCLP on specific machines…

Thank you for answering. I have tried rebooting. Also reinstallation of Parallels and new installation of Windows 11. Still the same problem. My old iMac 11,3 is working fine with Sonoma 14.1.1 and I do not dare to go to 14.2 . Hope to hear from somebody with same MBP 11,5

 

[Ausdauersportler]

Applying Root patches resolved the wifi issue. The animated wallpapers don't work but the dynamic ones do. Overall OS response is laggy. Is 12Gb RAM what's possibly tripping it up?

No, it is most likely the non-metal graphics card which kills overall performance. In order to get a really fully supported Monterey feeling on this kind of machine get an SSD, a metal GPU and replace the WiFi and BT with a BCM94360xx combo card.

Doing all this avoids any post install patching. Non metal Big Sur+ is more or less a proof of concept, not a platform to use on a daily basis without problems.

 

[Ready-for-Apple]

This comment is quite alarming. I have just updated my MBP 11,3 (which has an Nidia card) to Sonoma 14.2 OCLP 1.3.0 and was about to do the same for a MBP 11,4 (which has no card.) I also have iphone and ipads. What actually triggers this distressing event? How can I make sure to avoid it??

@ElSooz
❗️If you wanna avoid that stress than just AVOID using Memoji as your iCloud/Adress book/Login Picture on ALL devices. I'm using a FOTO of my Memoji as solution.

@All
This happens to all Intel Ivy, Haswell iGPUs and Nvidia Kepler GPUs
👉🏻 https://github.com/dortania/OpenCore-Legacy-Patcher/issues/1008

 

[houser]

I also need your help:
How can I change the name of the volume at startup?
It still shows "macOS Ventura", although I have already changed the name in Disk Utility and it is also displayed correctly on the desktop...

It will update next time you do a system update. There might be workarounds but I have not seen any.

 

[amaze1499]

Of course @amaze1499, actions can be recorded. But the problem (at least for me…) is how to make a script or other method automatically recognize when the Mac wakes up from Sleep mode and then start a background process to give the “killall Dock” command; so the script or utility must close its window if it cannot be hidden during its execution.

This might help: https://www.bernhard-baehr.de/sleepwatcher_2.2.1.tgz

SleepWatcher 2.2.1 (running with Mac OS X 10.5 and above, source code included) is a command line tool (daemon) for macOS that monitors sleep, wakeup and idleness of a Mac. It can be used to execute a Unix command when the Mac or the display of the Mac goes to sleep mode or wakes up, after a given time without user interaction or when the user resumes activity after a break or when the power supply of a Mac notebook is attached or detached. It also can send the Mac to sleep mode or retrieve the time since last user activity.

 

[Mark Meretz]

Good news, the problem with sleep where the Macbook simply restarted when opened after a long sleep process seems to have been resolved with macOS 14.2 and OCLP 1.3.0.

Macbook Pro 13.2 with HibernationMode 3

The Macbook has now been waking up perfectly for several days and sleep cycles.

​

​

coasterOneEightThree​

 

[Sven G]

I created a small 64 GB additional volume for Ventura on my main internal Sonoma SSD, installed the latest Ventura on it, and also installed Parallels Desktop and other virtualizers on it: and, indeed, paravirtualized graphics still works perfectly in Ventura for macOS VMs, also with the latest Parallels Desktop 19.2.0. Is it known why it doesn't work in Sonoma? IIRC, some time ago, an attempt was made to make it work by downgrading some kext/framework, but it didn’t have any effect: so, will there be other ways to be able to enable paravirtualization in Sonoma…? Parallels still has quite good support for macOS VMs, so it’s a pity that they don’t work anymore in Sonoma hosts…

Hmmm… Spoke too soon: on a Ventura 13.6.3 host, actually only a macOS 11 VM seems to work reliably in Parallels 19.0.2, with paravirtualization on; while macOS 12, 13 and 14 VMs have freezes and other problems: so, modern macOS virtualization almost seems to be a lost cause on Intel, now, sadly…

 

[Sven G]

… And it could maybe also be that Parallels Desktop is partly responsible for those macOS 12+ VMs not working anymore with paravirtualization, on Ventura: who knows, difficult to say…

(Edit: Oooops! Had forgotten that, on my machine, Parallels macOS 12+ VMs require only the iGPU to be enabled on a Ventura host; anyway, it still doesn’t work in any way on Sonoma, so far: where there is only a black screen, with any i/dGPU combination.)