macOS 14 Sonoma on Unsupported Macs Thread

[rbart]

Not working for me. It's a minor glitch.
It was OK with beta 7

 

[0134168]

Out of curiosity: Did this work running older macOS versions with your current setup (Which versions?)?

The DCC pages is not really conclusive (to me) which connector setup (only dual miniDP, not single miniDP?) supports it fully. At the very end of this page there is a list of several macOS tools to enabled brightness control with displays (and connections) capable to achieve it.

Unfortunately I own only a single (miniDP) connected external display which never supported native brightness control with 2009-2011 iMacs running High Sierra natively or later (OCLP).

Of course. In Monterey works like a charm. Two 30" apple displays and RX 570.

 

[0134168]

Hi @*******
To control brightness with RX580 on cMP5,1 I'm using MonitorControl, allows to use F1 & F2 keyboard keys.
Works perfectly on BigSur, Monterey and Ventura, should also work with Sonoma but I haven't yet found the time to install Sonoma on cMP5.1...

Not good. can control the brightness, but the max level of brightness is so low. But thanks!

 

[deeveedee]

for those who have broadcom bcm4352HMB problems in sonoma this is the solution download the zip text instructions then download opencore legacy patches 0.6.9 nightly and modify in resources-sys_patch-sy_patch_detect.py there I leave the sy_patch_detect.py.zip already modified alone replace it with the original if you want to modify it with textedit or IDLE editor just change self.modern_wifi from false to true and save then run Build-Binary.command wait for it to finish and run OpenCore-Patcher-GUI.command very important you must install in efi kext O80211FamilyLegacy.kext and IOSkywalkFamily.kext that this first IOSkywalkFamily.kext also in config.plist in kernel there I leave the kexts You must also put in config.plist kernel block identifier-com.apple.iokit.IOSkywalkFamily in comment-Allow IOSkywalk Downgrade minkernel-23.0.0 strategy exclude and enable there I leave the config.plist just copy and paste to your config.plist also kernel kext O80211FamilyLegacy.kext minkernel 23.0.0 as well as IOSkywalkFamily.kext good luck

It's not a native Apple Wi-Fi card, so OCLP does not recognize its IOName. If you don't want to modify OCLP code every time you download a new OCLP, simply spoof your Wi-Fi IOName to "pci14e4,43a3" using an ACPI patch and all is good. Since this ACPI patch does not affect Wi-Fi behavior, it can be a "permanent" ACPI patch that remains in place during normal operation. Once this patch is in place, OCLP will "natively" recognize your Wi-Fi without any code changes.

 

[Macdctr]

Updated to Beta 7 without problem. If could control the brightness with my RX 590 it would be perfect.

I downloaded the app "MonitorControl" which allows you to control brightness of your display monitor. I have two connected to my Radeon GPU and can now adjust brightness using this app. Once installed it shows up on the top menu as a lit lightbulb icon.

 

[stefanwa]

Latest Sonoma OCL with Dev Beta 7 here and my MBP late 2016 doesn’t wake up when closing and opening the screen again. Is it a common issue and may there be a workaround? Thanks
Steve

 

[cab_007]

I have the same 10,1 rMBP as you and am not seeing that issue at all.
My machine however runs the fans a bit. May I ask if you are seeing that too?
Still early-ish with the betas and power management tends to be fixed later in the beta cycle in my experience.
Ah well.

The fans do fire up when anything graphics dependent shows, especially the new animated wall papers (nice, but not essential).

The Devs have done great and continue to impress!!!

 

[joevt]

Not good. can control the brightness, but the max level of brightness is so low. But thanks!

See here https://forums.macrumors.com/thread...0-anyone-got-it-working.2276122/post-31777358

 

[0134168]

See here https://forums.macrumors.com/thread...0-anyone-got-it-working.2276122/post-31777358

Thank you so much, sir. At the end I have used the same app I have installed on my Mac Studio, and it works like a charm. Now I con control the brightness via sliders or direct keys.

Lunar - The defacto app for controlling monitor brightness

Control monitor brightness, adapt using the ambient light sensor, adjust volume, switch inputs and turn off displays without fiddling with clunky buttons.

lunar.fyi

 

[0134168]

I downloaded the app "MonitorControl" which allows you to control brightness of your display monitor. I have two connected to my Radeon GPU and can now adjust brightness using this app. Once installed it shows up on the top menu as a lit lightbulb icon.

Thank you so much, sir.

 

[deeveedee]

An unattended upgrade to Sonoma 14.0 Beta 7 from Beta 5 completed without issues on my MBP6,2. Following the upgrade, OCLP 0.6.9n (09.01.23) automatically prompted to apply post install patches for NVidia Tesla and Wi-Fi. As expected, non-metal NVidia Tesla is not operating with full graphics acceleration, so I am posting this with Firefox.

EDIT: I performed the update via OTA. I did not make any effort to revert root patches before the update, so OTA downloaded the full installer (12.75GB). Performing upgrades with the full installer has worked well for me on my MBP6,2 and I see no reason to change this (for me).

 

[eikic1]

help., im trying to install on macbook md103 (2012) 15inci
but after process install 29minute restart and stuck logo, progress stuck
with beta 7

what wrong ??
im using OCLP 0.6.8

 

[deeveedee]

help., im trying to install on macbook md103 (2012) 15inci
but after process install 29minute restart and stuck logo, progress stuck
with beta 7

what wrong ??
im using OCLP 0.6.8

You must use OCLP 0.6.9 nightly builds for Sonoma.

 

[eikic1]

You must use OCLP 0.6.9 nightly builds for Sonoma.

ok thanks

 

[David403]

Updated with September 1st's 0.6.9 nightly to Beta 7 on my macPro 5,1 (specs in signature file) with original WiFi and Bluetooth.

Mainly works fine with the following exceptions: -

1. After logging on I get the following message from the OC Patcher app:

"OpenCore Legacy Patcher has detected that you are booting an outdated OpenCore build

• Booted: 0.6.8
• Installed: 0.6.9

Would you like to update the OpenCore bootloader?"

when I apply the update and reboot I get the same message. What am I doing wrong?

2. Homesharing disconnects after several hours. It was stable in Ventura and Monterey previously/

3. The keyboard and trackpad disconnect after several hours (using a USB hub) - I must hard-reboot to do anything.

 

[deeveedee]

• Booted: 0.6.8
• Installed: 0.6.9

This happens when your OC EFI is created with OCLP 0.6.8 and you applied post install patches with OCLP 0.6.9. Did you 'Build and Install OpenCore' with OCLP 0.6.9?

Never apply post install patches with one version of OCLP and 'Build and Install OpenCore' with another version of OCLP.

If you think you did create a new OC EFI with OCLP 0.6.9, is it possible that you have multiple disks, each with an OpenCore EFI and you are not booting from the OC EFI you think you are? If that's the case, you should have only one OpenCore EFI.

 

[David403]

This happens when your OC EFI is created with OCLP 0.6.8 and you applied post install patches with OCLP 0.6.9. Did you 'Build and Install OpenCore' with OCLP 0.6.9?

Yes

Never apply post install patches with one version of OCLP and 'Build and Install OpenCore' with another version of OCLP.

I know this and it is not what I did.

If you think you did create a new OC EFI with OCLP 0.6.9, is it possible that you have multiple disks,

I only have one disk with Opencore EFI - I check each time I update using Terminal and diskutil list.

each with an OpenCore EFI and you are not booting from the OC EFI you think you are? If that's the case, you should have only one OpenCore EFI.

I only have one disk with an OpenCore EFI. It is on a 3Tb HDD with two1.5 Tb partitions (and of course the hidden EFI Partition) I named it "OC - Software & Video" to ensure that is always know where I place the OC EFI)

I have checked each of the EFIs on the multiple disks I have in and attached to my macPro I only have the one EFI with OpenCore. I deleted it and I have run the OCLP app. 'Build and Install OpenCore' with OCLP 0.6.9. ...will report back after it has rebooted.

I'll reinstall OCLP


EDIT:

Deleting the contents of the one and only OpenCore EFI on the machine and then reinstalling a new one on the same disk with the OCLP app has fixed the message from the OC Patcher app:

"OpenCore Legacy Patcher has detected that you are booting an outdated OpenCore build

• Booted: 0.6.8
• Installed: 0.6.9"

Thankfully this no longer pops up so I am correctly booting with 0.6.9 now.

... keeping my fingers crossed that it may also fix the other issues ???

 

[deeveedee]

Thankfully this no longer pops up so I am correctly booting with 0.6.9 now.

... keeping my fingers crossed that it may also fix the other issues ???

Your expectations of a Beta OS with a Beta OCLP are much higher than mine.

 

[chris1111]

beta 7 install on macbook pro late 2013 but I find the appearance of Item, folders and files very long when opening the session

 

[stcm]

I successfully installed beta7 on xserve 2009 using OCLP0.6.9n.
However, the root patch cannot be applied yet, so metal cannot be used.
At this stage, there're drawing issues that Sonoma wallpaper and multiple UI.
But I'm looking forward to the official release!

 

[K two]

Comparing both fully-supported and OCLP069n hack performance on comparable MacMini's with Beta 7, the differences are slight. Dortania and crew have performed a truly amazing feat! When an organization saves many thousands of Mac users large amounts of cash, is it not fair to donate?!!🧐

😎

 

[coasterOneEightThree]

Just now I wanted to install the latest Sonoma Beta (23A5337a) for a MacBookPro14,2, that currently still runs natively with Ventura – first on an external test drive.

I was able to prepare the USB-C installation stick regarding the Sonoma Beta with the current OC Patcher 0.69n, but installing OC on the EFI of the installation stick is not possible, because the button "Build and Install OpenCore" in the main window of the Patcher is greyed out and therefore not active. What can be done? Thanks in advance for helpful hints!

 

[deeveedee]

...because the button "Build and Install OpenCore" in the main window of the Patcher is greyed out and therefore not active. What can be done? Thanks in advance for helpful hints!

Strange. If you open OCLP > Settings, change the Target Model to MBP14,2 and press the "Return" button, is the "Build and Install OpenCore" option available?

 

[coasterOneEightThree]

Strange. If you open OCLP > Settings, change the Target Model to MBP14,2 and press the "Return" button, is the "Build and Install OpenCore" option available?

View attachment 2254828

You have led me in the right direction.

The MacBookPro14,2 is not yet on the menu list in the ⚙️ Settings for the Target Model because it is currently still running natively with Ventura.

So I guess I'll have to wait.

Thanks a lot! 👍

 

[coasterOneEightThree]

I got it right after all!

I selected any available Mac model in the ⚙️ Settings and then selected Host Model again. After returning to the main window, the button was suddenly active and I could patch the installation stick. This now works.

Nevertheless: The MacBookPro14,2 is still not on the Target Model list in the selection menu of the OC Patcher.