macOS 14 Sonoma on Unsupported Macs Thread

[K two]

macOS 14.6.1 installed atop 14.6 OTA, OCLP 1.6n. runs as expected.👏
😎

 

[deeveedee]

Smooth upgrade from Sonoma 14.6 -> 14.6.1 on my MBP6,2 patched with OCLP 1.4.3.

 

[nekton1]

Just OTA updated a MBP 2016 (13,3) without problems, but make sure OCL detects the macOS download in progress and also downloads the latest KDK simultaneously, or you will end up with no Internet connection at the first reboot so no easy way to get the KDK patch that provides the Internet connection (aka catch 22).

 

[F1Mac]

From 14.6 to 14.6.1 without issues on my MP6,1, except a little hiccup that happens sporadically during updates, it stalls with a black screen towards the final stages, like it's unable to restart by itself and just hangs. I had to force shutdown and reboot, and then (as usual) it booted normally, and I reinstalled root patches. I wasn't really worried but still wondering what can cause this. All running fine though (OCLP 1.5).

 

[Gfrancony]

just verified for an MBP11,1 (late 2013, 13").

What type of machine do you have? Which macOS is it currently running? which OCLP version?
Who should be able to answer your question with confidence on the day 14.6.1 is released, for so many different machines.
Apple would (have to) know for Apple-supported machines and test all of them prior to release. Also they know exactly what the changes are in the OS which makes testing easier. - I guess this is one of the reasons support has to end at some point for older models - else the total effort grows and grows.

So for our Apple-unsupported (OCLP supported) machines the advice would be to: either wait until someone has proven that it works for your hardware, or try yourself in a safe environment.
That could be: an external SSD with a clone of your current system onto which you install the new macOS, leaving your working SSD untouched. Preferentially install from a full installer rather than OTA from system settings (provides a better starting point for re-installation if something goes wrong). Then the post-install patches.
If this works well, install to your working SSD and patch it. (Anyway, backup the working SSD at least before any upgrades.)

Hi, I have got an IMac late 2013 with Sonoma 14.6 and OPCL 1.6.

 

[user853]

Hi All
Macmini7.1, NVMe from a third-party manufacturer (natively worked perfectly on Monterey)
After switching to OC LP 1.5 + Sonoma, unsuccessful boots, kernel panic, multiple failures of WindowServer in an already loaded system.
It was possible to stabilize the system load only by unchecking the "3rd Party NVMe PM" parameter, enabled by default.
The booting and operation of the system have become stable.

Maybe it will help someone.


Q: Has anyone encountered this behavior of OCLP for NVMe PM?

 

[PropClear]

Legacy Mac’s updated so far OTA macOS 14.6 -> 14.6.1 with newest OCLP 1.6.0n from yesterday (KDK 23G93 when needed) without problems! MacPro 4,1 | 5,1 iMac 11,1 | 11,2 | 12,2 | 14,1 | 15,1 MacBookPro 6,2 | 10,1 | 11,1 | 12,1 | 14,1 | 14,2 MacBookAir 6,1 MacMini 6,1 | 6,2 | 7,1 👌

 

[K two]

Hi All
Macmini7.1, NVMe from a third-party manufacturer (natively worked perfectly on Monterey)
After switching to OC LP 1.5 + Sonoma, unsuccessful boots, kernel panic, multiple failures of WindowServer in an already loaded system.
It was possible to stabilize the system load only by unchecking the "3rd Party NVMe PM" parameter, enabled by default.
The booting and operation of the system have become stable.
View attachment 2404008
Maybe it will help someone.


Q: Has anyone encountered this behavior of OCLP for NVMe PM?

Nope. Maybe if the host was specified PM would work? 🤷‍♂️

 

[dogen]

Hi All
Macmini7.1, NVMe from a third-party manufacturer (natively worked perfectly on Monterey)
After switching to OC LP 1.5 + Sonoma, unsuccessful boots, kernel panic, multiple failures of WindowServer in an already loaded system.
It was possible to stabilize the system load only by unchecking the "3rd Party NVMe PM" parameter, enabled by default.
The booting and operation of the system have become stable.
View attachment 2404008
Maybe it will help someone.


Q: Has anyone encountered this behavior of OCLP for NVMe PM?

I have a Hynix P31 in a 2013 MBA running OCLP 1.5 and Sonoma 14.6 (will update to 14.6.1 soon). If I don't reboot daily I run into systemwide freezes requiring a hard reboot. Before trying the fix recommended above, may I ask how I'd get back into OCLP to reinstate the 3rd Party NVMe PM if the system fails to boot with the option unchecked?

 

[user853]

I have a Hynix P31 in a 2013 MBA running OCLP 1.5 and Sonoma 14.6 (will update to 14.6.1 soon). If I don't reboot daily I run into systemwide freezes requiring a hard reboot. Before trying the fix recommended above, may I ask how I'd get back into OCLP to reinstate the 3rd Party NVMe PM if the system fails to boot with the option unchecked?

It is enough to boot in safe mode (shift+enter) and make the necessary changes to OCLP

BUT!

At the suggestion of dear K two, in the Host Model field, I explicitly identified my macmini7.1 and turned on PM - and it seems to work in this case.
I am at a loss - this is the first time such OCLP behavior has been encountered on a host machine.

PS
Thus, the solution suitable for me is:
"Host Model" and PM off
or
explicitly specify your model from the drop-down list and PM on

 

[deeveedee]

I have a Hynix P31 in a 2013 MBA running OCLP 1.5 and Sonoma 14.6 (will update to 14.6.1 soon). If I don't reboot daily I run into systemwide freezes requiring a hard reboot. Before trying the fix recommended above, may I ask how I'd get back into OCLP to reinstate the 3rd Party NVMe PM if the system fails to boot with the option unchecked?

Hynix P31 required a firmware update to work with macOS. See this and check your SSD firmware version.

 

[TOM1211]

I have a Hynix P31 in a 2013 MBA running OCLP 1.5 and Sonoma 14.6 (will update to 14.6.1 soon). If I don't reboot daily I run into systemwide freezes requiring a hard reboot. Before trying the fix recommended above, may I ask how I'd get back into OCLP to reinstate the 3rd Party NVMe PM if the system fails to boot with the option unchecked?

I also have a Hynix P31 in a 2014 with no issues at all (i have a 2tb and a 1tb ) both fine as mentioned above update the firmware if you never have (i did mine from a windows 10 bootcamp install on the same MacBook) there’s a thread on here about unsupported drives in MacBooks if someone has the link at the time I fitted mine Hynix P31 was one of the most reliable and best to be fitted.

 

[dogen]

Hynix P31 required a firmware update to work with macOS. See this and check your SSD firmware version.

Thanks for the tip. The firmware is and has been up to date.

After updating to 10.6.1, I opened OCLP 1.5, clicked build and install OpenCore, and set the host to MBA6,2 and installed that to the EFI partition. Once rebooted, I again opened OCLP and clicked post-install root patch, then restarted again. Presumably that will customize the host model going forward. Will see if I need the daily reboot. Thanks to all for suggestions.

 

[user853]

It is enough to boot in safe mode (shift+enter) and make the necessary changes to OCLP

BUT!

At the suggestion of dear K two, in the Host Model field, I explicitly identified my macmini7.1 and turned on PM - and it seems to work in this case.
I am at a loss - this is the first time such OCLP behavior has been encountered on a host machine.

PS
Thus, the solution suitable for me is:
"Host Model" and PM off
or
explicitly specify your model from the drop-down list and PM on
View attachment 2404038 View attachment 2404039

upd
14.6 with OCLP 1.5 -> 14.6.1 OTA
the flight is normal

 

[MacRumors3590]

Same here...
14.6 with OCLP 1.5 -> 14.6.1 OTA
cMP
Thanks to the Devs!!!

 

[nekton1]

Just OTA updated a MBP 2016 (13,3) without problems, but make sure OCL detects the macOS download in progress and also downloads the latest KDK simultaneously, or you will end up with no Internet connection at the first reboot so no easy way to get the KDK patch that provides the Internet connection (aka catch 22).

Addendum, while the 14.6.1 post-update root patch was running on the MBP (2016) 13,3 I saw three lines scroll by mentioning a firmware update that I hoped would update the efi and SMC firmware but this MBP is still stuck on 499.40.2.0.0 and SMC version 2.38f12.

 

[MacinMan]

Addendum, while the 14.6.1 post-update root patch was running on the MBP (2016) 13,3 I saw three lines scroll by mentioning a firmware update that I hoped would update the efi and SMC firmware but this MBP is still stuck on 499.40.2.0.0 and SMC version 2.38f12.

You need to install the latest version of your mac's officially supported version of macOS to get the firmware updates. Make sure to reset PRAM and not boot with OpenCore, but the Apple boot loader. That's why I'm waiting until Monterey is completely done before switching OS' to make sure everything is up to date where Apple will leave it. Also, i have one or two audio apps that don't like Sonoma, and are glitchy so things are more stable on the older version for now.

 

[nekton1]

You need to install the latest version of your mac's officially supported version of macOS to get the firmware updates. Make sure to reset PRAM and not boot with OpenCore, but the Apple boot loader. That's why I'm waiting until Monterey is completely done before switching OS' to make sure everything is up to date where Apple will leave it. Also, i have one or two audio apps that don't like Sonoma, and are glitchy so things are more stable on the older version for now.

Thanks, but I am too lazy to roll back that far for the dubious merits of the latest firmware. And the real question I should have asked: What were those lines in the root patch referencing firmware updates? Was I hallucinating or was some attempt being made at firmware update?

 

[OKonnel]

Hi, I have got an IMac late 2013 with Sonoma 14.6 and OPCL 1.6.

Hi @Gfrancony,
I also have an iMac 14.2 with macOS 14.6 and OCLP 1.6.0 Nightly. This morning I think I will upgrade to 14.6.1 without any problems because when there are additional version numbers, as in this case, it can only get better.
Apple releases them so quickly to fix small but important bugs or security holes that Apple identifies after thousands of installations of the main version (in this case 14.6).
The rapid changes that follow the release of a major update, however, are almost never substantial; at least I do not recall any exceptions from Mac OS X 10.0 to the present.

EDIT
I then installed version 14.6.1 after creating a USB Installation Key using the latest OCLP 1.6.0 Nightly Build (PKG dated 08/08/2024).
Obviously everything went as expected, i.e.: good

 

[Steve Gosselin]

I strongly suspect that this problem is not related to OCLP but rather to macOS 14.6.x.

Since macOS 14.6, a web app no longer displays the window for exploring and selecting a file.

To test :

• Create a web app
• Open the web app
• Find the option on the "site" to submit a file (example: upload image -> avatar)
• If you're running macOS 14.6.x, nothing happens; if you're running macOS 14.5 and below, a window will display

 

[OKonnel]

I strongly suspect that this problem is not related to OCLP but rather to macOS 14.6.x.

Since macOS 14.6, a web app no longer displays the window for exploring and selecting a file.

To test :

• Create a web app
• Open the web app
• Find the option on the "site" to submit a file (example: upload image -> avatar)
• If you're running macOS 14.6.x, nothing happens; if you're running macOS 14.5 and below, a window will display

Thanks, @Steve Gosselin!
I have tried to create a Google Drive WEB App and I confirm what you asserted.
Thank you!!!
Personally, I would think more of a Sonoma bug than an OCLP problem.
Have you searched the WEB? I don't have time, otherwise I would do a thorough search to see if there are any other reports on this.
On the other hand, if anyone has the WEB App working fine, and if wanting to do an Upload opens the Finder window to upload files, PLEASE WRITE IT DOWN, whether they have a Mac with OCLP or an Apple-supported Mac.
Conversely, for those who this window does not open, it is unnecessary for them to add an additional message as it will burden the Forum.

 

[RAMtheSSD]

I don't understand why I did not get any help or even a comment asserting the general weirdness of my situation. I do not even know if it was merely very rare or a setting in OCLP that I should have changed in some way or if the problem once required a kext transfer but does not anymore thanks to all the amazing developers out there; I am very grateful for your efforts. In any case, power management is certainly related because last night a breaker tripped and, though it had nothing to do with the Mac Pro, suddenly, I had Bluetooth and wifi at the same time! I have zero idea as to what happened but it appears to be permanent since the update only stopped because the iPad Pro was connected to the Mac Pro; simply unplugging it caused the update to continue right from where it left off as if nothing had happened!! Previous attempts at controlled reboots or PRAM or SMC controlled resets hadn't worked where, apparently, an entirely uncontrolled shutdown and restart did. Although I thought this was in my profile, cMP 4,1-5,1 conversion with a Sapphire Pulse RX 580 card that came overclocked from factory 2 X Xeon E5620 with 32gb ram and an Inatek USB 3.2 card booting from a OWC 1TB on a PCIe card.

 

[trifero]

I don't understand why I did not get any help or even a comment asserting the general weirdness of my situation. I do not even know if it was merely very rare or a setting in OCLP that I should have changed in some way or if the problem once required a kext transfer but does not anymore thanks to all the amazing developers out there; I am very grateful for your efforts. In any case, power management is certainly related because last night a breaker tripped and, though it had nothing to do with the Mac Pro, suddenly, I had Bluetooth and wifi at the same time! I have zero idea as to what happened but it appears to be permanent since the update only stopped because the iPad Pro was connected to the Mac Pro; simply unplugging it caused the update to continue right from where it left off as if nothing had happened!! Previous attempts at controlled reboots or PRAM or SMC controlled resets hadn't worked where, apparently, an entirely uncontrolled shutdown and restart did. Although I thought this was in my profile, cMP 4,1-5,1 conversion with a Sapphire Pulse RX 580 card that came overclocked from factory 2 X Xeon E5620 with 32gb ram and an Inatek USB 3.2 card booting from a OWC 1TB on a PCIe card.

I can´t barely understand what you are talking about

 

[mikezang]

I am using 14.6, do I have to update to 14.6.1?

 

[grumpy_Garrett]

why does my macbook only connects to 1 wifi but cannot connect to other wifi network? am i the only one who's experiencing this?