Got a tip for us?
Let us know
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
- Thread starter dhinakg
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Updated to 14.5 on my MBP 9,1 using 1.5.0n. OTA update went smoothly. Nothing of note to report so far.
Note: I didn't read/understand your earlier post fully. My responses are only related to the quoted post.
The low frequency of people running into this issue is due to Apple's own self restraint in (not) releasing RSRs.
OCLP is set to auto start up, and if it detects that your system needs root patches, it will prompt you. But that can sometimes fail to detect. In the case where you know the system needs root patches but OCLP does not prompt you, you can manually open up OCLP and install the root patches.
That is correct. The bottom setting references Apple's Rapid Security Response. There were confirmed precedence where installing an RSR in an OCLP system would prevent the system from booting due to the way RSR messes with volume signing. That is to say, IF Apple releases an RSR anytime in the future and you install it, it is highly likely your system will fail to boot with OCLP. The reason why you don't see any prompts or any uninformed user complaining on forums is because Apple has only released RSR twice to the public since its introduction more than a year ago, and after the subsequent public update it would no longer be possible to receive such an update.
The low frequency of people running into this issue is due to Apple's own self restraint in (not) releasing RSRs.
MacMini 7,1 (2014) running 14.5 beta 2 with OCLP 1.50n updated to 14.5 final without update issues and just requested root patching (used new (today) 1.50n download).
If Sonoma on OCLP devices would be a movie, 14.5 is the epilogue and 14.6 will be the credits.
Will it be worth to watch the sequel?
Will it be worth to watch the sequel?
Using the RC with latest OCLP 1.5n – everything fine! Thanks OCLPdevs!
Well then this blurb from a commit from May 10 can perhaps then be indicative of the reboot
macos_install_handler.py: Add macOS 15 variant support to backend
to the OCLP expert:
"Find my" in Settings > iCloud always turns itself off. I've noticed this again and again since 14.4 (it may have been the case with previous versions).
Does anyone have any idea why this is and whether I can fix it permanently instead of turning it on again and again?
Unfortunately, I have not yet found out under what circumstances the system automatically switches it off again.
"Find my" in Settings > iCloud always turns itself off. I've noticed this again and again since 14.4 (it may have been the case with previous versions).
Does anyone have any idea why this is and whether I can fix it permanently instead of turning it on again and again?
Unfortunately, I have not yet found out under what circumstances the system automatically switches it off again.
When did the iMac Pro drop native support, was it Ventura, or Sonoma? I know they kept support a bit longer than earlier non pro iMacs, just don't remember which version.
mikelets456 said:
I'm using an MacBook Pro 11,4 on 1.4.3 OCLP---- has anyone updated to 14.5 on 1.4.3? Should I wait for 1.5.0?
@mikelets456 I just did it on my iMac (see signature)...so far no issues...
I'm using an MacBook Pro 11,4 on 1.4.3 OCLP---- has anyone updated to 14.5 on 1.4.3? Should I wait for 1.5.0?
@mikelets456 I just did it on my iMac (see signature)...so far no issues...
It's not a problem mike, was just curious. I haven't been following in real detail lately. I still read this thread to see the progress being made, but I went a different direction from OCLP regarding this iMac after Monterey runs out that will give me 32-bit support (for games and older apps) as well as giving me a current 64-bit OS as well.
Version 1.5.0 has very few changes compared to 1.4.3.
It's mainly about code cleanup, except for some Nvidia GPUs ...
Nothing specific to Sonoma 14.5
Changelog:
It's mainly about code cleanup, except for some Nvidia GPUs ...
Nothing specific to Sonoma 14.5
Changelog:
1.5.0
- Restructure project directories
- Python:
- Move logic into opencore_legacy_patcher directory
- Use relative imports for local libraries
- Documentation:
- Move images to docs/images
- Payloads:
- Remove redundant/unused files bundled in payloads.dmg
- Python:
- Resolve unpatching Nvidia Web Drivers failing to clean up /Library/Extensions
- Implement preflight code signature checks for macOS installer creation
- Ensures validity of createinstallmedia binary before execution
Legacy Mac’s updated so far OTA macOS 14.4.1 -> 14.5 with newest OCLP 1.5.0n (KDK 23F79 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 MacBookAir 6,1 MacMini 6,1 | 6,2 | 7,1
How do you get 1.5.0 OCLP?
EDIT: Oh, you just do a system update and it downloads it automatically.
Last edited:
It's a nightly update for Dev users hence the (n) after 1.X.X stating "nightly build".
For anyone having kernel panicks from "3rd party NVMe controller. PCI link down. Write. fBuiltIn=1" on Sonoma on a Mac Pro 5,1:
My system was stable with Ventura and a WD SN730 NVMe drive in a $10 "xqjtech" NVMe PCIe card from Amazon. I upgraded to Sonoma and a larger WD SN740, and I was getting these crashes randomly mutliple times a day. I finally got desperate and ordered a $25 OWC Accelsior card to try instead, and now the problem has stopped and my system is stable again. I guess even though NVMe PCIe cards are very simple devices, quality matters.
My system was stable with Ventura and a WD SN730 NVMe drive in a $10 "xqjtech" NVMe PCIe card from Amazon. I upgraded to Sonoma and a larger WD SN740, and I was getting these crashes randomly mutliple times a day. I finally got desperate and ordered a $25 OWC Accelsior card to try instead, and now the problem has stopped and my system is stable again. I guess even though NVMe PCIe cards are very simple devices, quality matters.
Upgraded my MBP6,2 from 14.4.1 -> 14.5 without issues via OTA. Applying post-install patches with OCLP 1.4.3.
I'm not a Dev (trust me, no one is happier than they are), but if I were a Dev, I'd be releasing 1.5.0 after macoS 15 is seeded.
Do you know how to edit your OC config.plist? Or maybe you could set SIP in OCLP > Settings and rebuild Open Core?
Yes, I know it. OCLP > Settings not the looking I for. I tried a couple of settings to there, e.g., I set the SIP to 0x0, which is enabling to the SIP. But when I look under the NVRAM with Terminal SIP still shows disabled. And, yes I reset the NVRAM. Still, the settings here are not what I'm looking for. I want OpenCore to not completely interfere with SIP.