macOS 14 Sonoma on Unsupported Macs Thread

[MacinMan]

I just wanted to add, that if speed is a concern, to anyone who tries this, save the VM to an SSD and run it that way. That should get rid of most disk i / o lag. Also on quad core machines the VM will be limited to 2 cores. If you have more than that, you will be limited to half your physical cores so 8 core will give you 4 cores for the VM, and so on. So as I said, judge speed by that. As I mentioned above, the main lag seems to come in the for of no 3D acceleration by default for macOS guests. Older versions such as Mojave and below, aren't too bad, maybe even catalina . But Big Sur and above, you do want the AppleGPU if you have a supported host.

 

[MacinMan]

@MacinMan @rbart My preference would have been to run VMWare ESXi (Type 1 Hypervisor) to host macOS VMs. VMWare has discontinued support for ESXi on Intel Mac and has no plans for ESXi on Apple Silicon. I am using only Type 1 hypervisors (VMWare and Microsoft) and find them to yield virtually the same performance as running the OS on bare metal - very impressive. I would expect that performance in a Type 2 hypervisor (like Fusion) would suffer.

This is getting off-topic (even for me). Is there a MacRumors thread for discussing virtualization of macOS?

I haven't looked, but why are you off topic, this is like I said for running macOS on unsupported macs how you do that is up to you. People use Open Core because they want to run it directly, but a VM if set up right is also a good option. So that's why i brought the topic here after doing some testing of my own this morning and was pretty impressed with the results, and wanted to share with others how I got it to work on a supported Mac with an unsupported OS alongside the supported host OS.

 

[Sven G]

Hmmm… just discovered that the built-in FaceTime camera doesn’t work in 14.1b3 on MBP11,3: it is not even detected in System Information, so this must be a driver issue (the camera works fine when booted from Big Sur and worked fine in Sonoma 14.0, so probably it’s an incompatibility with the beta).

 

[deeveedee]

but why are you off topic

Because at the very least, we are duplicating content that is already covered in threads like this.

 

[Sven G]

@deeveedee thought you would like to see this, I got Ventura running in a VMWare Fusion 13 Pro VM on a late 2015 iMac with 3D acceleration working. Followed VMWare's instructions and added the two lines to the vmx file and here's the result!
View attachment 2294066

If only it could work also on unsupported Macs…

 

[MacinMan]

Because at the very least, we are duplicating content that is already covered in threads like this.

OK, looked at that thread briefly. Still think the two threads can work together, and share content.

 

[headlessmike]

Hmmm… just discovered that the built-in FaceTime camera doesn’t work in 14.1b3 on MBP11,3: it is not even detected in System Information, so this must be a driver issue (the camera works fine when booted from Big Sur).

The camera on my 13" 11,1 works fine in 14.0 with OCLP 1.0.1.

 

[deeveedee]

I re-patched macOS after disabling App Updates in OCLP GUI

I'm still being prompted for OCLP updates. If that's the case, I imagine that OCLP GUI is also ignoring settings like disabling Reporting

Maybe I'll need to perform a code review again.

EDIT: Until I figure out what's going on with App Updates (and Reporting), I have reverted to High Sierra which is the last natively supported macOS on my MBP6,2 (no need for OCLP). I forgot how fast this OS boots and how it flies! ... but the old Safari is not without its website compatibility issues - no surprise. Firefox in High Sierra is still getting the latest Mozilla updates.

 

[MacinMan]

Don't try to play Disney+ content from Safari in a VM either. While it has 3D acceleration enabled it hard crashed the VM, so DRM might work, but not from Disney, so some things may be hit or miss like they are with OCLP. The only difference is, the VM method is Apple supported.

 

[MacinMan]

@deeveedee : Just so I can answer your question from above, I'm doing an OTA upgrade to Sonoma in the Ventura VM as I would on a supported Mac, just to see what happens, and so I can give you at least a partial answer about running it in a VM apposed to OCLP. If it goes bad, no harm done I'll just create a fresh VM with Ventrua.

 

[cab_007]

Hmmm… just discovered that the built-in FaceTime camera doesn’t work in 14.1b3 on MBP11,3: it is not even detected in System Information, so this must be a driver issue (the camera works fine when booted from Big Sur and worked fine in Sonoma 14.0, so probably it’s an incompatibility with the beta).

Built-in camera works on my machine with 14.1b3, even the continuity capability using the iPhone camera with FaceTime on my rMBP.

 

[MacinMan]

@deeveedee : OK, here you go. I had to change a couple of smart bulbs that started having color LED fail so it took longer to get these results to you than if I had been focused on the upgrade. It did it on it's own within the VM while I was busy.

 

[K two]

I re-patched macOS after disabling App Updates in OCLP GUI
View attachment 2294149

I'm still being prompted for OCLP updates. If that's the case, I imagine that OCLP GUI is also ignoring settings like disabling Reporting
View attachment 2294150

Maybe I'll need to perform a code review again.

EDIT: Until I figure out what's going on with App Updates (and Reporting), I have reverted to High Sierra which is the last natively supported macOS on my MBP6,2 (no need for OCLP). I forgot how fast this OS boots and how it flies! ... but the old Safari is not without its website compatibility issues - no surprise. Firefox in High Sierra is still getting the latest Mozilla updates.

In Sonoma are auto-run items in the Log-in panel? ru and OpenCore-Patcher, specifically? They need to be on. 🧐

 

[deeveedee]

@K two Thanks. It seems odd that in order to disable OCLP update prompts that I would need to make sure those items are in the Log-in panel and "on", but I will check the next time I test Sonoma/OCLP. I think that I have my test environment so screwed up from multiple upgrades and reversions that it might be best for me to perform a clean install and start fresh with the latest OCLP and a new Sonoma USB installer created by OCLP.

 

[h9826790]

I'd like to report that macos sonoma on a mac pro 5,1 runs well with the exception (so far) that the calculator gives me "not a number"..needs further testing but that it so far.
Also im shocked and surprised that protools 2023.6 works along with my uad2 pcie, fabfilter, waves, plugin alliance, ssl native, oek soothe 2, native instruments and softtube plugins(this was a shocker) but none of the websites for those 3rd party apps state they work. today im a 😁 camper. no more upgrades for a year for me...View attachment 2288883

Hi, can you check if H264 / HEVC HWAccel is working on your cMP?

I've seen quite a few reports about Vega provide no HWAccel in Sonoma. I wonder if Polaris is the same.

 

[G5-Sir Mac Alot]

Hi. I need some advice. I have a iMac 13.2 that I have installed Sonoma with OCLP and its running fantastic. But I noticed my hard drive suddenly is close to full. Ive found that my System-Data is at 182gb out of nowhere. Wondering if I should do a time machine backup and re-install Sonoma onto a erased ssd or will that System-Data file come back when I try to migrate??

 

[blauesliebe7]

Hi, can you check if H264 / HEVC HWAccel is working on your cMP?

I've seen quite a few reports about Vega provide no HWAccel in Sonoma. I wonder if Polaris is the same.

Tested with both AMD Radeon RX Vega 64 8 GB and AMD Radeon RX Vega 56 8 GB with no HWAccel. I have gathered this information from the following links:
- https://github.com/dortania/OpenCore-Legacy-Patcher/commit/5df3cca616881272acdee75c4eab8b5dc2f1f2c6
- https://github.com/dortania/OpenCore-Legacy-Patcher/issues/1008
- https://github.com/dortania/OpenCor...16881272acdee75c4eab8b5dc2f1f2c6/CHANGELOG.md
- https://dortania.github.io/OpenCore-Legacy-Patcher/SONOMA-DROP.html#issues
- https://github.com/kholia/OSX-KVM/pull/207

**Expert**: Computer Systems Engineer specializing in macOS and OpenCore
**Objective**: To provide a detailed guide on enabling graphic acceleration on a Mac Pro 5,1 with an AMD Radeon RX Vega 64 8 GB graphics card using OpenCore.
**Assumptions**: You have a Mac Pro 5,1 running OpenCore and you're facing issues with graphic acceleration.

The OpenCore Legacy Patcher documentation does mention issues related to graphics support but doesn't provide a direct solution for your specific hardware configuration. However, it does indicate that the build includes both Legacy Metal and non-Metal patches for macOS Sonoma. This suggests that there might be patches available that could potentially solve your issue.

Here are the steps to potentially enable graphic acceleration:

1. **Check OpenCore Version**: Make sure you are running the latest version of OpenCore Legacy Patcher. Updates often include bug fixes and new features.

2. **Review Patches**: Go through the list of available patches in OpenCore Legacy Patcher, specifically focusing on Legacy Metal and non-Metal patches. Apply the ones that are relevant to your hardware.

3. **Edit Config.plist**: Open your `config.plist` file located in your EFI partition under `EFI/OC/`. Look for the section related to graphics and make sure it's configured to enable acceleration.

4. **Kernel Extensions**: Make sure you have the necessary kexts (Kernel Extensions) for your AMD Radeon RX Vega 64. These can usually be found in the `Kexts` folder in your EFI partition.

5. **Debugging**: Use OpenCore's debugging tools to check for any errors or warnings related to graphics acceleration.

6. **Reboot and Test**: After making these changes, reboot your system and test to see if graphics acceleration is working.

The commit titled "Avoid GVA downgrade on Skylake hosts" in the OpenCore Legacy Patcher repository contains several changes that could be relevant to your situation. The commit shows modifications in multiple files, including CHANGELOG.md, constants.py, defaults.py, and sys_patch_generate.py.

Here are the key takeaways:

1. GVA Downgrade Avoidance: The commit seems to remove the AppleGVA downgrade on Intel Skylake iGPUs. This is particularly relevant if you have a Skylake processor along with your AMD card.
2. AMD Vega Support: The changelog mentions resolving AMD Vega support on pre-AVX2 Macs in macOS Ventura. This could be directly related to your AMD Radeon RX Vega 64 8 GB card.
3. Code Changes: The Python code changes suggest adjustments to the patching logic, particularly for graphics. For example, the sys_patch_generate.py file has conditions that update required patches based on the graphics hardware details.

Steps to Apply the Workaround​

1. Update to Latest Version: Make sure you are using the OpenCore Legacy Patcher version that includes this commit.
2. Check Configurations: Open your config.plist and ensure that any settings related to GVA or AMD Vega are correctly configured.
3. Apply Patches: Use OpenCore Legacy Patcher to apply the relevant patches, especially those mentioned in the commit.
4. Reboot: After applying the patches and making the necessary changes, reboot your system to see if the graphic acceleration issue is resolved.

 

[Ausdauersportler]

So now the self proclaimed security expert of this thread reverts back and uses a macOS version for security reasons which neither got any security upgrades nor a firmware upgrade since late 2020. This is a bold move.

Time to pull the plug and block those annoying posts before we get enlightened by code review posts. Fortunately Discord has been sanitized a few days ago. Just in case you all admire the level of activity shown here.

 

[Ausdauersportler]

Tested with both AMD Radeon RX Vega 64 8 GB and AMD Radeon RX Vega 56 8 GB with no HWAccel. I have gathered this information from the following links:
- https://github.com/dortania/OpenCore-Legacy-Patcher/commit/5df3cca616881272acdee75c4eab8b5dc2f1f2c6
- https://github.com/dortania/OpenCore-Legacy-Patcher/issues/1008
- https://github.com/dortania/OpenCor...16881272acdee75c4eab8b5dc2f1f2c6/CHANGELOG.md
- https://dortania.github.io/OpenCore-Legacy-Patcher/SONOMA-DROP.html#issues
- https://github.com/kholia/OSX-KVM/pull/207

**Expert**: Computer Systems Engineer specializing in macOS and OpenCore
**Objective**: To provide a detailed guide on enabling graphic acceleration on a Mac Pro 5,1 with an AMD Radeon RX Vega 64 8 GB graphics card using OpenCore.
**Assumptions**: You have a Mac Pro 5,1 running OpenCore and you're facing issues with graphic acceleration.

The OpenCore Legacy Patcher documentation does mention issues related to graphics support but doesn't provide a direct solution for your specific hardware configuration. However, it does indicate that the build includes both Legacy Metal and non-Metal patches for macOS Sonoma. This suggests that there might be patches available that could potentially solve your issue.

Here are the steps to potentially enable graphic acceleration:

1. **Check OpenCore Version**: Make sure you are running the latest version of OpenCore Legacy Patcher. Updates often include bug fixes and new features.

2. **Review Patches**: Go through the list of available patches in OpenCore Legacy Patcher, specifically focusing on Legacy Metal and non-Metal patches. Apply the ones that are relevant to your hardware.

3. **Edit Config.plist**: Open your `config.plist` file located in your EFI partition under `EFI/OC/`. Look for the section related to graphics and make sure it's configured to enable acceleration.

4. **Kernel Extensions**: Make sure you have the necessary kexts (Kernel Extensions) for your AMD Radeon RX Vega 64. These can usually be found in the `Kexts` folder in your EFI partition.

5. **Debugging**: Use OpenCore's debugging tools to check for any errors or warnings related to graphics acceleration.

6. **Reboot and Test**: After making these changes, reboot your system and test to see if graphics acceleration is working.

The commit titled "Avoid GVA downgrade on Skylake hosts" in the OpenCore Legacy Patcher repository contains several changes that could be relevant to your situation. The commit shows modifications in multiple files, including CHANGELOG.md, constants.py, defaults.py, and sys_patch_generate.py.

Here are the key takeaways:

1. GVA Downgrade Avoidance: The commit seems to remove the AppleGVA downgrade on Intel Skylake iGPUs. This is particularly relevant if you have a Skylake processor along with your AMD card.
2. AMD Vega Support: The changelog mentions resolving AMD Vega support on pre-AVX2 Macs in macOS Ventura. This could be directly related to your AMD Radeon RX Vega 64 8 GB card.
3. Code Changes: The Python code changes suggest adjustments to the patching logic, particularly for graphics. For example, the sys_patch_generate.py file has conditions that update required patches based on the graphics hardware details.

Steps to Apply the Workaround​

1. Update to Latest Version: Make sure you are using the OpenCore Legacy Patcher version that includes this commit.
2. Check Configurations: Open your config.plist and ensure that any settings related to GVA or AMD Vega are correctly configured.
3. Apply Patches: Use OpenCore Legacy Patcher to apply the relevant patches, especially those mentioned in the commit.
4. Reboot: After applying the patches and making the necessary changes, reboot your system to see if the graphic acceleration issue is resolved.

You cannot selectively apply patches you like or believe to need for your particular hardware using the OCLP app. OLCP supports real Macs with (mostly) fixed hardware configurations, the tool has nevertheless a nice logic to auto-detect modded hardware like GPU, USB, BT/WiFI and creates and applies a patch package accordingly.

The OLCP team does not support any manually changed or enhanced configurations. It does not support self compiled and changed OCLP apps. If you truly believe to have found a new enhancement or patch make a pull request or suggest one on Discord. Issues and requests are limited to a few users (guess why) and will go through a code review before being added.

So the complete process comes down to:

- check the OLCP updates publishd
- update in case your particular system got a fix or enhancement

Use in any case the OCLP documentation to perform initial installations and OCLP updates. If you are not satisfied with the docs propose an enhancement or a change - but you have to work it out yourself. It is a community supported process. The complete doc set has been created this way. We will not write your docs. You have to do it yourself.

 

[DJMeat]

Can anyone help...

I have a 7,1 mini that's spoofing to show as an 8,1, but Universal Control just isn't reliable for me. At all. Firstly, it seems to only work when my iPad is connected - which isn't a massive problem - but more often than not, it just isn't available as an option at all. Sidecar works perfectly every time, but Universal Control comes and goes for no reason I can pin down.

A restart might fix it, but more likely it won't. Then suddenly it's available again, and it's driving me mad!

Of course, only working over the cable means that controlling both my mini and my M2 Air is out of the question.

The only other issues I have is that 95% of the time it won't unlock with my Watch, and it has a really hard time connecting to wifi, so I'm wondering whether there's something up with the wireless card - although my keyboard and trackpad work flawlessly, so 🤷🏻‍♂️

 

[Sven G]

Hi. I need some advice. I have a iMac 13.2 that I have installed Sonoma with OCLP and its running fantastic. But I noticed my hard drive suddenly is close to full. Ive found that my System-Data is at 182gb out of nowhere. Wondering if I should do a time machine backup and re-install Sonoma onto a erased ssd or will that System-Data file come back when I try to migrate??

Have you tried deleting Time Machine local snapshots (which can tend to fill the drive)…? It can be done from within Disk Utility, Carbon Copy Cloner or the Terminal…

 

[G5-Sir Mac Alot]

Have you tried deleting Time Machine local snapshots (which can tend to fill the drive)…? It can be done from within Disk Utility, Carbon Copy Cloner or the Terminal…

Shouldn't have any. Unless it does it automatically. I do my backups onto an external drive.

 

[houser]

deleted. not my place.

 

[houser]

Shouldn't have any. Unless it does it automatically. I do my backups onto an external drive.

It does it automatically for various practical reasons.. Can be switched off in the terminal

 

[Tockman]

Hi. I need some advice. I have a iMac 13.2 that I have installed Sonoma with OCLP and its running fantastic. But I noticed my hard drive suddenly is close to full. Ive found that my System-Data is at 182gb out of nowhere. Wondering if I should do a time machine backup and re-install Sonoma onto a erased ssd or will that System-Data file come back when I try to migrate??

Check up for /cores folder in the root of your system volume.