macOS 14 Sonoma on Unsupported Macs Thread

[Ausdauersportler]

And you confuse wisdom with arrogance (an equally cold judgment). I don't believe I've read such an arrogant statement in all the posts I've read on this forum. You must be very confident in your own abilities.

Confident enough to identify sources not worthy to listen to. It is an important ability when you gather new information and learn new things day by day and you have to separate noise from signal. It is not really complicated in this particular case.
Reading here is sometimes as painful as reading the daily news, just weather, politics, another air plane crash and sport news - really important.

 

[deeveedee]

Confident enough to identify sources not worthy to listen to. It is an important ability when you gather new information and learn new things day by day and you have to separate noise from signal. It is not really complicated in this particular case.
Reading here is sometimes as painful as reading the daily news, just weather, politics, another air plane crash and sport news - really important.

I was thinking something similar. Talking to you has been like reading the daily news with plane crashes and politics: I feel worse afterwards.

Have a great day and thanks for bringing some sunshine into this painful experience of ours. I am honored to have been blessed with your presence. Do I kiss your ring now, or is it ok if I just bow before you?

 

[Ausdauersportler]

I was thinking something similar. Talking to you has been like reading the daily news with plane crashes and politics: I feel worse afterwards.

Have a great day and thanks for bringing some sunshine into this painful experience of ours. I am honored to have been blessed with your presence. Do I kiss your ring now, or is it ok if I just bow before you?

Do me a favor and try to create a single useful constructive on topic post. Even you can achieve this.
Until you get this done other users should be warned to evaluate sources.

I guess this is only fair.

 

[David403]

Try to boot with an USB with prevuious OCLP you were using, and choose your hard drive to boot

I am having a similar (if not identical? problem) to reneroeten.

I have both Ventura 13.5.1 and Sonoma 14.0 on my 2010 macPro5,1 (as per specs in my signature file. It has the original WiFi and Bluetooth hardware). Both OSs are booting with EFI generated with OCLP 1.0.0.

Bluetooth works with Ventura but not with Sonoma.

The hardware is the same for both. The EFI from which they are booting is the same and in turn, the config sys file is of course the same for both and the list of Kexts is the same.

The difference is seen in the Bluetooth section of the System Reports for the 2 OSs. (attached below)

Ventura - says it is a third-party dongle. but it isn't it's the original hardware

Sonoma - says BMC_4350C2 - it's the original hardware

The config sys file generated by OCLP 1.0.0 for my hardware is attached.
An image for the Kext folder in EFI for macPro 5,1 generated by OCLP 1.0.0 for my hardware is attached.

Am I missing something obvious? - well obvious to everyone else but not to me.

 

[ApolloBoy]

Ain't a MacRumors thread without two random people going at it I guess.

Anyway, I just updated OCLP on my MBP11,4 and performed a Sonoma install. Right now it's going into a loop of freezing up after a second at being in the login screen, displaying a black screen and then going back into the login screen, where it freezes up again. Not sure if I messed up something or if OCLP simply glitched up.

 

[figyu]

I got a MacBook Pro 2012 Retina 15inch(10,1) with 8ram and 256ssd.
I am running a Catalina without an issue.
I am thinking to upgrade from Catalina to Sonoma.
I am wondering if it is practical to use.
I'd love to hear from anyone with the same machine.

 

[0134168]

This is simply amazing. I can´t believe it. Macbook Pro 17" 2011 Core I7, SSD 16GB.
Bluetooth, Wifi, Keys for brightnes (display and keyboard), my usb 3.0 pcmcia. And runs unbelievable smooth.

 

[Ausdauersportler]

Some general hints about Sonoma:

- New installations only via OCLP generated USB installer!

- Bluetooth fix with OCLP 1.0.1 available!

- Sometimes Bluetooth issues can be fixed with (multiple) PRAM reset(s).

- Windows server or login screen crashes can (sometimes) be fixed via safe mode boot and patching in safe mode.

- Reading the OCLP change log and OCLP docs is really helpful not only for first time users.

- Check out the OCLP Discord server, no other developer is reading here on MR for obvious reasons and community support needs some self organization to get on speed.

- Good point: The main dev manages two open issue docs on Github listing most Ventura and Sonoma problems - worth reading

 

[FabriBonaparte1]

Thank you, so much, I do work at school with my old Macbook air 2013 4gb memory and thanks to you everything is secure and working, I admire your dedication and work. Thank you from a grateful apple user.

 

[Dilli]

Just installed on my MacBook Air Mid 2011. All went smoothly. Tks to Opencore Legacy Patcher Community.

Couple of issues.
1. Maps will not work though the app launches as well as "Find My App"
1a. Stage manager too is not effective.
1b. Desktop selection in Mission Control - Hot corners does not work
2. Cmd+shift+4 creates issue
3. After entering lock screen and coming back to desktop there is error window of "login window crash". So donot use screensaver and try not to have sleep mode active.

All issues listed above is basis my Mac model. Don't know about others.
So far all works great except for above listed issues.✌️

 

[MisterAndrew]

I got a MacBook Pro 2012 Retina 15inch(10,1) with 8ram and 256ssd.
I am running a Catalina without an issue.
I am thinking to upgrade from Catalina to Sonoma.
I am wondering if it is practical to use.
I'd love to hear from anyone with the same machine.

Ventura and Sonoma still have some issues that may or may not be important to you. If you want everything to work like normal I suggest going with Monterey for now, which works very well; just as well as Big Sur for me.

Legacy Metal Graphics Support and macOS Ventura - Sequoia · Issue #1008 · dortania/OpenCore-Legacy-Patcher

With the forth coming release of OpenCore Legacy Patcher v0.5.0, systems with legacy Metal GPUs will finally be able to achieve graphics acceleration in macOS Ventura! Reminder: These patches are s...

github.com

 

[amaze1499]

On first login post-install, fans were working hard. They decreased over time, maybe two hours max. I left it powered on overnight. Logging-in this morning they haven't started up at all yet. I'll keep an eye, or ear, on it today and report back.

I did confirm in Activity Monitor yesterday that when the fans were running hardest it was doing a lot of writes to SSD. That has ceased today. I think indexing-, and/or expanding compressed objects shipped with the install package, were the likely causes but have no way (that I know of) of proving that.

BTW, I had to do a couple of discreet things to get everything stable yesterday:

1) restart bluetooth once using sudo kill -9 $(pgrep bluetoothd)
2) manually reboot twice to get YouTube playback working properly.

All good today so far.

Out of curiosity: could you check for Videorecorderservice running in the background even when the monitor is turned off? I found there is a setting in screensaver, where it’s running as video on all screens even the login screen.

Also keychain folder seems to blow up at certain points after restart, logging back in.

CGPDF services is a „new“ index service which
also takes up a cpu resource now and then.

 

[TheDebunker]

@TheDebunker If you are still listening, thank you for listening. In addition to the security warnings in the OCLP GUI and when macOS launches with OCLP post-install patches, could you please allow the user to selectively disable post-install root patches? I would feel much safer with my OCLP-patched Sonoma if I could disable Wi-Fi post-install patches and use Sonoma with wired-Ethernet only. My security concerns with OCLP didn't start until I began investigating the root patches for Wi-Fi (I'm not as much concerned about the root patches for graphics). This ability to disable Wi-Fi patches should not interfere with another's desire to keep the Wi-Fi patches enabled. Thank you!

EDIT: @TheDebunker Related to the security warnings in OCLP (GUI and at boot with post-install patches), I think that this statement in GitHub may be misleading:
View attachment 2287772
The statement says that nightly builds are not guaranteed to be safe. Wouldn't the uninformed, unaware OCLP users take this to mean that the official releases of OCLP are guaranteed to be safe? And thus wouldn't they conclude that for guaranteed safety, they should use the official OCLP releases? Just pointing this out. I think it needs to be re-worded.

We've talked about selective patching and it was ultimately decided against. Most people want full functionality on real Macs and therefore we have the root patching as single package configured per Mac model to have less confusion, after all we don't support Hackintoshes officially because of wildly varying configurations and issues that come with those. Tinkerers can still do it on Hackintosh but as you've probably heard quite a few times on the server, no real support for them.

I pitched the security warning thing to rest of the team but ultimately they decide what they want to do.

Also "not safe" in that context means the nightly builds could render the system unusable or entirely brick it. It's not really directed at information security.

 

[hanksliu]

After I upgraded to Sonoma, the camera was not working on Safari.

I installed OCLP 1.0 and upgraded my 15 inch mid-2014 MacBook Pro to macOS Sonoma. The camera works fine in Chrome and Firefox, but not in Safari browser.

Safari camera permissions couldn't be granted via tccplus with error message "Could not add Camera approval status for com.apple.Safari."

 

[rehkram]

Out of curiosity: could you check for Videorecorderservice running in the background even when the monitor is turned off? I found there is a setting in screensaver, where it’s running as video on all screens even the login screen.

Forgive me for being a little dense, but how do I check that if the the monitor is off? Are you saying check it on the rMBP's internal display? I tend to use the term 'monitor' for both internal and external displays.

 

[rehkram]

I got a MacBook Pro 2012 Retina 15inch(10,1) with 8ram and 256ssd.
I am running a Catalina without an issue.
I am thinking to upgrade from Catalina to Sonoma.
I am wondering if it is practical to use.
I'd love to hear from anyone with the same machine.

I have the same m/c, so does @houser. There are others. Sonoma is running well here using OCLP 1.0.1

 

[reneroeten]

I am having a similar (if not identical? problem) to reneroeten.

I have both Ventura 13.5.1 and Sonoma 14.0 on my 2010 macPro5,1 (as per specs in my signature file. It has the original WiFi and Bluetooth hardware). Both OSs are booting with EFI generated with OCLP 1.0.0.

Bluetooth works with Ventura but not with Sonoma.

The hardware is the same for both. The EFI from which they are booting is the same and in turn, the config sys file is of course the same for both and the list of Kexts is the same.

The difference is seen in the Bluetooth section of the System Reports for the 2 OSs. (attached below)

Ventura - says it is a third-party dongle. but it isn't it's the original hardware

Sonoma - says BMC_4350C2 - it's the original hardware

The config sys file generated by OCLP 1.0.0 for my hardware is attached.
An image for the Kext folder in EFI for macPro 5,1 generated by OCLP 1.0.0 for my hardware is attached.

Am I missing something obvious? - well obvious to everyone else but not to me.

yeah it's very strange reinstalled the OS with a USB stick but same result everyting working fine accept BT even with v.101 no luck

 

[coolio2004]

MBP5,2: 14.0 runs well with latest OCLP 1.0.1n (i.e. EFI and post-install patches). Only the show-desktop doesn't work (windows don't go away), as was already the case for earlier OCLPs.

Tried 14.1 beta on MBP5,2. Booting the USB installer hangs at an early stage. Same when using OTA, MacOS Installer hangs early while earlier phases of upgrade went well. This is the case with OCLP 0.6.9n, 1.0.0, and 1.0.1n.
I first did these trials on external USB target SSD, then plugged the same SSD to internal SATA, same behaviour.
KP logs attached.

Doesn't matter much as the existing 14.0 installation on this SSD survives the tests. Just to inform.
Thanks to developers for all the fantastic work!

Same happened to me with my MBP5,1. No chance with 14,1 beta. 14.0 works fine so lot.

 

[LuckyOldMan]

While Sonoma 14.0 Final could be installed with OCLP 0.6.9n on my cMP 5.1 2010 (now booting with OCLP 1.0.1n), Sonoma 14.1 DP1 with OCLP 1.0.1n refuses to install at all and stalls quite early on at the point shown.

Have important things changed in DP1 compared to 14.0 (DP2 has already been rolled out)?

 

[ThommiTechnik]

Same happened to me with my MBP5,1. No chance with 14,1 beta. 14.0 works fine so lot.

Is your trackpad working in Safari, to go back and forward with sites?

 

[FabriBonaparte1]

Thank you Another success, all apps working, a little slow sometimes, but i can live with that. Thank you for all your hard work and leaving the old apple alive!!!

 

[Sven G]

OCLP 1.0.1 solves many problems, but has a new bug (i.e., the macOS downloader doesn’t work):

 

[coolio2004]

Is your trackpad working in Safari, to go back and forward with sites?

no problems with trackpad going back or forward.

 

[alphascorp]

Hi all

We can't say it enough, thanks again to the developers for all their hard work.

Since OCLP version 1.0.0, in the config.plist file, it seems that the 'boot-args' -lilubetaall argument is created twice.

Nothing serious, it doesn't hinder OCLP in any way, just edit the config.plist and remove the duplicate...

 

[Sven G]

... And - a trivial bug - if you update OCLP inside the OpenCore-Patcher app, the alias in /Applications is recreated, even if it’s already present: so, then there will be two aliases (with subsequent manual deletion of one of them)…

(Edit: Seems to happen only in Ventura, while in Sonoma there was correctly only one alias after the update - strange, as usual…)