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.
Calibre5 said:
Same here, neither Netflix nor DisneyPlus work with Safari or Safari Technology Preview but are ok on Chrome.
Apple TV app and Photo Booth work fine.
Click to expand...
The Disney+ issue is also present in Ventura with the latest nightly build of Open Core that I have installed.
As I personally don't use a web browser to use my streaming services with, I wouldn't even care personally. For the sake of the forum though, I did look for myself and did find the issue present here as well. Netflix, I haven't tested.

To be fair though, I have used streaming services in the browser, but mainly so I can use a keyboard to search for things, but viewing for me is typically done in the home theater so I get the multi channel audio, and other features such as HDR, or I use the mobile apps on my iPhone, but primarily TV. The other thing is, I've never cared for Safari personally, I just feel Firefox and Chrome are just better overall, especially if you want cross platform.

Hopefully the issue is resolved for those who need / want it by the official OCLP 1.0.0 release though.
 
Ultracyclist said:
Steer clear from 14.1! My paperweight is stuck on the update screen.
Will have to reverse back to 14.0.
Click to expand...
On my 13-inch MBP (see sig) everything seemed to update and when rebooting after installing the root patches, the computer remained stuck with only the apple logo showing on the screen. Strange . . .

Today I will erase the storage drive, reinstall 14.0 then I will update OCLP 0.6.9n to it's most current release and see if this changes things. I have an earlier release of 0.6.9n, not sure if there are any differences but I figure the only thing I'm wasting is time...
 
Reverted patches downloaded Sonoma 14.1 Beta came in at 1.11gb a few reboots, repatched went without issue on MacBook Pro mid 2014 camera doesn’t work if you use that says no camera available going to have the same issues as Sonoma 14.0 as mentioned by devs but overall no difference in running.
 
Last edited:
deeveedee said:
@philippemarques It looks to me like OC was upgraded to 0.9.5, but the OC config.plist still has OC-Version incorrectly set to 0.9.3. Do you know how to report this in Discord? I'd offer to report this for you, but you should get credit for the discovery.

EDIT: I should mention that this is only a comment in the OC config.plist and does not affect operation. If you look at the config.plist, you'll see that the #Revision section in the config.plist has a # at the beginning of the name of the section. Any label in the config.plist that starts with # denotes a comment.

View attachment 2283369
Click to expand...
Thank you, well :

Commit Information:
Branch: refs/heads/sonoma-development
Date: 2023-09-27T09:07:52-06:00
Booted Information:
Booted OS: XNU 23 (14.0)
Booted Patcher Version: 0.6.9
Booted OpenCore Version: REL-095-2023-09-11
Booted OpenCore Disk: disk0s1
Hardware Information:
Computer(real_model='MacBookPro8,1')

Not sure bluetooth works ie CHANGELOG :
  • Bluetooth support by switching to dynamic VMM spoofing
Maybe i'm doing something wrong.
 
@philippemarques To be certain, in terminal, run nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version. This is the info that matters, not the comment in the config.plist.

If you see OC 0.9.5 and are seeing Bluetooth issues, I have seen that some are still experiencing Bluetooth issues in Sonoma, so I can't rule out an OCLP issue that is yet to be resolved.

EDIT: I just noticed that your post shows 'Booted OpenCore Version: REL-095-2023-09-11' so you already know that you're using OC 0.9.5. Sorry I don't have more to offer.
 
Saltacharcos said:
Hello everyone,

I have a refurbished iMac which in theory is a model imac19.1 but the system marks it as AAPJ1391.1

This means that even though I could run Ventura and Sonoma wouldn't, With Ventura I "cheated" using an OpenCore generated on a macmini and it worked, with some issues, but with Sonoma I'd like to find a better solution. I tried to build OpenCore from this machine but I get this error:


Building Configuration on model: AAPJ1391,1
Creating build folder

- Adding OpenCore v0.9.2 RELEASE
- Adding config.plist for OpenCore
- Adding Lilu.kext 1.6.6
An internal error occurred while building:

Traceback (most recent call last):
File "resources/wx_gui/gui_build.py", line 123, in _build
File "resources/build/build.py", line 36, in __init__
File "resources/build/build.py", line 142, in _build_opencore
File "resources/build/build.py", line 66, in _build_efi
File "resources/build/firmware.py", line 28, in __init__
File "resources/build/firmware.py", line 40, in _build
File "resources/build/firmware.py", line 221, in _firmware_compatibility_handling
File "resources/build/firmware.py", line 295, in _dual_dp_handling
KeyError: 'AAPJ1391,1'


Does anyone know how it could be fixed?

Thank you so much
Click to expand...
If you can install the last MacOS that was supported, that might help, as that indicates that there might be a firmware issue. Test it with Silent Knight if you have not already if the firmware is correct?
 
  • Like
Reactions: olad
@deeveedee I wanted to quickly follow up with you over the Python discussion yesterday. FYI, the Python Path I was using as follows:

Last login: Thu Sep 28 06:11:37 on ttys000
tron@iFrog5Kv13 ~ % which python3
/Library/Frameworks/Python.framework/Versions/3.11/bin/python3
tron@iFrog5Kv13 ~ % which pip3
/Library/Frameworks/Python.framework/Versions/3.11/bin/pip3
tron@iFrog5Kv13 ~ %

So, when I was running the python3, and pip3 commands according to the open core instructions, that was the environment being used as listed above. That is how the python installer from python.org configured my python environment, so what you see here are the defaults according to "their" instructions.

I could try to compile again, and past the whole ordeal, but it's a lot to read through.
 
RestrictEvents.kext can impact Bluetooth and macOS OTA updates among other things. Devs have made recent changes to this kext that may or may not be captured in OCLP (I can't tell from the dates/times and honestly, didn't look hard enough). These changes are definitely not captured in the currently Released version of RestrictEvents.kext. If you're capable, download new versions of RestrictEvents.kext here. If you're not or this make no sense, wait for changes to OCLP.

EDIT: It does appear that, at the time of this post, the latest RestrictEvents.kext 1.1.3 is part of OCLP 0.6.9 Sonoma Development (commit ca4fd22), so if you're building your own OCLP from the latest OCLP 0.6.9 sonoma-development source, you have the latest RestrictEvents.kext. If you're using an older pre-built nightly OCLP or you have a hackintosh with your own OC EFI, you may want to upgrade RestrictEvents.kext.
 
Last edited:
  • Like
Reactions: m4v3r1ck and macpro_mid2014
deeveedee said:
It's very possible that this problem is more common than I realize. Hopefully the others who are experiencing this problem will offer their solution.
Click to expand...
Well, I checked the nightly link to the pre-compiled binary, it still says September 26th in the get info window.
Has the updated binary been posed yet? and I'm just using the wrong link? I'm using the link provided on the GitHub page for the open core source.
 
For some reason, the latest commit on sonoma-developement branch on GitHub is 'revert to OpenCore 0.9.3' What? Why would they do that?
 
  • Like
Reactions: deeveedee
mohkg said:
In the newest nightly and GitHub commit, opencore 0.9.5 got downgraded to 0.9.3
Click to expand...
What???

run nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version

What do you see?

You are correct! Wow.
Screen Shot 2023-09-28 at 10.59.07 AM.png


EDIT: Still building the engine while we're driving. That's the nature of Beta and is to be expected.
 
  • Like
Reactions: macpro_mid2014
deeveedee said:
What???

run nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version

What do you see?
Click to expand...
this is what I got:
Last login: Thu Sep 28 09:39:30 on ttys000
tron@iFrog5Kv13 ~ % nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:eek:pencore-version
4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:eek:pencore-version REL-093-2023-06-12
tron@iFrog5Kv13 ~ %
 
Update tried the latest nightly build that was uploaded 9:36am cst this morning my time (they downgraded the opencore version 0.9.5 to 0.9.3) everything still working great
 
Last edited:
mohkg said:
If they did downgrade 0.9.5 down to 0.9.3 expect allot of my Bluetooth doesn't work posts today
Click to expand...
Why? OC 0.9.3 -> 0.9.5 didn't affect Bluetooth. BluetoolFixup.kext and RestrictEvents.kext are the changes that mattered. The Acidanthera kexts are independent of Open Core.

EDIT: Also, changes to the OC config.plist generated by OCLP affected Bluetooth (not the OC version). Devs continue to play with VMM in ways that affect Bluetooth.
 
Last edited:
  • Like
Reactions: Rambear1998
Whatever they did doesn't seem to affect Ventura, but it did something to my test setup of Sonoma on a lateb 2013 Macbook Pro 11,1 so it no longer boots. Just looked at the downloaded binary from their link on the GitHub and it still shows the 26th of September release. I'm on CST, so maybe I should look again.
 
I've been using the link on this page to grab the pre compiled binary:
I've applied bold font to the link to draw attention. Is there a different link I should be using?
Sorry, I deleted the post as they said not to share the links and i only saw that after i copied and pasted.

So, if they don't want the links copied and shared, how am I supposed to show people what link I'm using to make sure it's the right one?
 
Last edited:
Revert to OpenCore 0.9.3
Due to regression on Skylake and newer systems, currently investigating
@khronokernel
khronokernel committed 1 hour ago

I built the revision :

Commit Information:
Branch: Running from source
Date: Not applicable
URL: N/A

Booted Information:
Booted OS: XNU 23 (14.0)
Booted Patcher Version: 0.6.9
Booted OpenCore Version: REL-093-2023-06-12
Booted OpenCore Disk: disk0s1

It doesn't solve the Bluetooth issue for MacBookPro8,1
Everything else looks pretty good.
 
  • Like
Reactions: deeveedee and perez987
MacinMan said:
I've been using the link on this page to grab the pre compiled binary:
I've applied bold font to the link to draw attention. Is there a different link I should be using?
Sorry, I deleted the post as they said not to share the links and i only saw that after i copied and pasted.

So, if they don't want the links copied and shared, how am I supposed to show people what link I'm using to make sure it's the right one?
Click to expand...
Your download link is good,there's only one, it's the automated build from Github.
 
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