macOS 14 Sonoma on Unsupported Macs Thread

[rbart]

I've kept your suggestions in mind and I opened Maps, photos, and even in Finder, I haven't observed any green thumbnails and when I opened maps to my current location, I didn't observe any of the transparency issues either.

The only real issue I had was adding the second Gmail account to apple mail, but that may be a google issue. All current existing mail accounts that were present in Monterey before the upgrade work as expected.
Here are a few screen shots of my mac running Sonoma showing the reported areas, not showing issues for me.

It's strange you don't have the same issues in Maps ...
The green thumbnails are for some video files (when they are fully downloaded)
No problem with gmail for me, I don't think it's linked to Sonoma .
The issues we can have are with patched or backported components: graphics and wifi drivers in or case. The rest is more or less stock.
I see you have an M395, I have an M390. Maybe a small difference here ...

 

[MacinMan]

I was able to confirm the Gmail issue isn't OCLP related. Just got done testing in my Sonoma VM under Monterey so the 3D acceleration worked. So must be a google issue. I put Monterey on an external drive since I mainly just need it for the remaining EFI updates Apple may issue, and for graphics compatibility such as VMware 3D acceleration support.

Everything seems to be working as expected (overall)

 

[MacinMan]

OK, I wanted to post some very differing results I've encountered since upgrading to Sonoma on my iMac 17,1 with Open core 1.3.0 and Sonoma 14.3. Some of the issues reported include 3D acceleration not working in VMs both on Fusion, and Parallels. While I can confirm this for guests such as Linux, where I have to switch to Software Rendering mode for Cinnamon, and or disable 3D in the Settings for the VM for Windows, or Linux (not running Cinnamon ) The Apple GPU seems to work fine for macOS guests. Both my Ventura and Sonoma VMs boot with 3D working.
Here is a screenshot of Sonoma running as a Guest and as host (patched by open core) on an iMac 17,1. So it must mean only certain types of 3D acceleration don't work, while others do. This was done with VMware Fusion Professional 13.5.0 on Sonoma 14.3, on OCLP 1.3.0 and an iMac 17,1 (top tier config) before going custom.

 

[MacinMan]

@amaze1499 I fixed my google issue. I changed the default browser from Safari to Chrome, then went through the setup to add the second Gmail account through the internet accounts prefpane, and it worked with Chrome, so Safari must have a setting now that prevent the process from completing correctly . Maybe it's one of the tracking or other protection settings. Anyway I try to use Safari as little as possible these days. I either use Firefox, or Chrome, or a Chromium based browser. Safari is good for the password generator in iCloud keychain.

 

[macinfo]

Apple seeded macOS 14.4 Beta (23E5180j) to developers

 

[dogen]

I've been testing Sonoma on a spare MBA for the past couple of months, starting with 14.2. The latest OTA upgrade to 14.3 went smoothly, and I'm no longer seeing an issue waking from sleep. I'm about ready to add a Sonoma volume to the second, main MacBook Air. That MBA runs Big Sur. The internal SSD, which is a Hynix Gold P31, has no partitions, with about 600GB of available space. I'm planning to use some of the available space to create a second volume, onto which I'll clean-install Sonoma 14.3. I imagine that 20GB would suffice if I leave data and apps on the original Big Sur volume, but I'll likely make it larger to accommodate a migration of settings after the installation completes

Now a question: will an APFS volume automatically resize as needed, or do I need to go to Disk Utility to change the volume size manually when I'm running low on space? It would be convenient to copy apps and data to the Sonoma volume, though it's not strictly necessary, as I've seen on the test MBA. It has both Big Sur and Sonoma and migrated settings and preferences, but apps and data are on the Big Sur side.

 

[deeveedee]

Now a question: will an APFS volume automatically resize as needed,

When you add your APFS volume, look at Size Options:

Default behavior is for APFS volumes to auto resize within the constraints of their container.

 

[K two]

macOS14.4b1, OCLPv.1.4.0n boots in Safe Mode but subsequent root-patching yields a WindowServer crash from which there is no recovery. Many of the data fields in SilentKnight are empty. Suspect a OCLP update will be forthcoming. 🤷‍♂️

Additionally, installing the appropriate KDK, just now released, made no difference. 🧐

 

[chris1111]

Patch Haswell looks like broken same here ApplekeyStore operation failled?
Or Wifi patch?

 

[cab_007]

Just a heads up that when I upgraded to 14.4 beta (published recently) with OCLP 1.4.0n (current nightly), post-root patching caused black screen upon restart and required safe mode restart to start up. I guess next update to OCLP will help resolve this.

 

[TOM1211]

Taken from a post on the opencore Discord

warning: macOS 14.4 breaks OCLP

- 3802 GPUs are no longer functioning
- Ivy Bridge
- Haswell
- NVIDIA Kepler
- 31001 GPUs are no longer functioning
- Broadwell
- Skylake
- AMD GCN1-3
- AMD GCN4-5 for non-AVX2
- WiFi patches are no longer functioning
- T1 Security Chip patches are no longer functioning
- MacBook Pros with Touch Bar from 2016-2017
- SPI Keyboards and Trackpads no longer functioning
- MacBook 2015-2017
- MacBook Pro 2016-2017

**do not update to betas.**

Had a good run of updates with no issues there till 14.4.

 

[Macdctr]

Taken from a post on the opencore Discord

warning: macOS 14.4 breaks OCLP

- 3802 GPUs are no longer functioning
- Ivy Bridge
- Haswell
- NVIDIA Kepler
- 31001 GPUs are no longer functioning
- Broadwell
- Skylake
- AMD GCN1-3
- AMD GCN4-5 for non-AVX2
- WiFi patches are no longer functioning
- T1 Security Chip patches are no longer functioning
- MacBook Pros with Touch Bar from 2016-2017
- SPI Keyboards and Trackpads no longer functioning
- MacBook 2015-2017
- MacBook Pro 2016-2017

**do not update to betas.**

Had a good run of updates with no issues there till 14.4.

I just attempted the 14.4 Developer beta release update and found the same with my 2015 13-inch i7 MBP.

DO NOT ATTEMPT THIS UPDATE . . . .

I also turned off automatic downloads/updates on my other computers as a result above so 14.4 won't be downloaded/installed onto them.

 

[rbart]

I have tried again Sonoma on my iMac 17,1
Finally I have rolled back again to Ventura which far more polished for this hardware.
There are several (non blocking) graphical glitches on Sonoma which are nonexistent on Ventura
- green videos thumbnails in Finder and Photos.app
- in Maps (and all mapkit apps), there are some transparency problems around some texts (look atstreet names and POI names in my attachment)
- it's heating in standby due to the video screensavers (better to disable to avoid fan noise)
- sometimes there are some menu bar problems after resuming from standby

For all these small reasons, I recommend to stay on Ventura on this kind of hardware, unless you are forced to upgrade for a missing feature.
I hope it will improve, but as the OCLP project seems a bit stall, I am not very confident.View attachment 2342467

I quote myself ...
Xcode is my main tool and with the coming 15.3 release, I will be forced to upgrade to Sonoma. It will be the end of the Ventura story !

 

[MacinMan]

I quote myself ...
Xcode is my main tool and with the coming 15.3 release, I will be forced to upgrade to Sonoma. It will be the end of the Ventura story !

I was curious about that, will Xcode 15.3 require Sonoma? I thought I saw something from Mr. Macintosh saying it would still work on Ventura, at least the beta, or was that 15.2? I honestly don't remember off the top of my head.

 

[deeveedee]

I quote myself ...
Xcode is my main tool and with the coming 15.3 release, I will be forced to upgrade to Sonoma. It will be the end of the Ventura story !

You are correct ... Sonoma is required for Xcode 15.3. See here.

 

[MacinMan]

You are correct ... Sonoma is required for Xcode 15.3. See here.
View attachment 2342942

Thanks for confirming that. My main use of XCode is for Homebrew, but since so many of tools I use there are natively available in Linux, that's why that's been a second option for me to Open Core. The other reason I wanted to hold onto this iMac was for Intel vs ARM because a lot of what I might want to do, or have options for are still most likely better on the X86 platform . Doesn't have to be macOS, though macOS is preferred. I've considered a new M Series Mac but I'm still not satisfied with it as a legacy game machine since a lot of my older games are still 32-Bit. So I really don't know what decision to make right now. Because my daily tasks would work just fine on an M Series Mac, but it's the more specific things I want access to, that won't.

 

[deeveedee]

... So I really don't know what decision to make right now...

For me the decision is complicated by the fact that Microsoft announced end of macOS support for Visual Studio. Looks like I'm going to be moving from Ventura to Windows. EDIT: I'll only be using macOS when I need Xcode for app publishing.

 

[MacinMan]

For me the decision is a complicated by the fact that Microsoft announced end of macOS support for Visual Studio. Looks like I'm going to be moving from Ventura to Windows.

Well, if I was a hard core Gamer, the decision to go to Windows would be easier as Windows is the mainstream game platform, and the mac is. Even Linux gaming is probably better than the Mac at this point as well because of Proton and other. projects. What makes it harder for me, is I do a Mix, the daily tasks as mentioned would carry over to an M Series Mac without issues, it's the more unique and specific stuff I like to have access to that would not.

Actually the best solution to keep my environment fairly functional the way I'd like would be to run Mojave, but that's probably worse today trying to maintain than Open Core .

 

[macpro_mid2014]

For me the decision is complicated by the fact that Microsoft announced end of macOS support for Visual Studio. Looks like I'm going to be moving from Ventura to Windows. EDIT: I'll only be using macOS when I need Xcode for app publishing.

I would upgrade to the new M3 Pro MPB and run the ARM version of W11+VS on a VM, unless you don't want to upgrade your hardware!

 

[MacinMan]

I would upgrade to the new M3 Pro MPB and run the ARM version of W11+VS on a VM, unless you don't want to upgrade your hardware!

I've considered that myself because Windows 11 is supported in VMware on the new macs as the Arm platform, but when I've asked about 32-bit X86 options such as older games / apps that I might want to use, the response is typically all that is gone with the new hardware. So as I've said in my above post, sticking with Apple only would work with a new Mac, but the whole reason I have a Mac is for Apple+ 3rd party support in one physical machine so I wouldn't have to concern myself with space for multiple machines. That's why it's making it a hard call for me at this point.

EDIT: I wanted to add that, While I'm aware that while I run Monterey, or above on this Mac (Monterey last official supported by Apple) I always have the option Of running Mojave on this iMac for 32 bit Mac support, or even a Linux Distro. Going to an M Series Mac would remove the backward compatibility even more (even from within the host OS.)

 

[philk34]

Hello,
The OTA update of my CMP 3.1 from Sonoma 14->14.3 failed.
I revert the OCLP patches to download a lighter update and launch the update.
I've always done it like this and it's always worked. But here I have an error message in the preparation of this update ?
Some indications please

 

[Jazzzny]

Hello,
The OTA update of my CMP 3.1 from Sonoma 14->14.3 failed.
I revert the OCLP patches to download a lighter update and launch the update.
I've always done it like this and it's always worked. But here I have an error message in the preparation of this update ?
Some indications please

This has not worked since Monterey. You need to download the full update as the smaller "delta" update does not contain the Rosetta cryptex needed to boot the machine.

 

[friendofdogs]

I don't want to steer you in a direction that is beyond your knowledge. Since you upgraded from a previous version of macOS and you are experiencing problems, you should try to perform a clean installation of Sonoma.

EDIT: Make sure you have a way to recover your system/data before you start experimenting. I don't know your risk tolerance, but I would suggest that you have a backup using your preferred backup mechanism before you start experimenting.

Thanks for your advice. The morning after posting this my mac was just turning on to a white screen and it looks like the SSD was corrupt beyond repair. I got a new SSD, clean installed Sonoma and have just restored my data from a backup. Working fine for a couple of hours and then I come back to it having crashed again. I can post the crash report if helpful. I was deleting a load of old files from my backup hard drive so maybe it was just that that caused the crash and not the previous problems.

 

[mikelets456]

Thanks for your advice. The morning after posting this my mac was just turning on to a white screen and it looks like the SSD was corrupt beyond repair. I got a new SSD, clean installed Sonoma and have just restored my data from a backup. Working fine for a couple of hours and then I come back to it having crashed again. I can post the crash report if helpful. I was deleting a load of old files from my backup hard drive so maybe it was just that that caused the crash and not the previous problems.

I wonder if you have a bad motherboard? Did you have problems with the install? Also, what SSD are you using and is the SSD installed with an adapter?
What’s your set up?

Did you format the drive correctly?

Some of these questions have obvious answers but trying to rule out the obvious.

 

[friendofdogs]

I wonder if you have a bad motherboard? Did you have problems with the install? Also, what SSD are you using and is the SSD installed with an adapter?
What’s your set up?

Did you format the drive correctly?

Some of these questions have obvious answers but trying to rule out the obvious.

The only problem was some sort of update assistant error that came up halfway through. I just rebooted and went back to EFI and the installation looked like it carried on where it left off.

I'm using an MX500, same as I was using before, it goes into the normal SATA cable.

My setup is mid 2012 MBP 9,1 with 16 GB 1600 MHz DDR3 ram and 1tb SSD.

Drive was formatted GUID APFS.

I get an error when trying to run the hardware test but I've just seen that pressing option-D can run the hardware test from the internet so I will see if that works when I get a second.