Macbook Air mid 2012. Everything works perfectly! Thanks!
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
It "sounds like" you simply want to update Safari to the most current version.
If so, bookmark this site, and update away!
macOS Safari Full Installer Database. Download Directly from Apple!
Download macOS Safari app full installers with one click straight from Apple! Every version of Safari for Monterey, Big Sur & Catalina!mrmacintosh.com
Sort of... I appreciate the link, that is helpful to have. Ideally, I would like the safari updates to still pop up through system updates while ignoring any major OS updates. It seems like this isn't possible. I tried changing my SMBIOS to one that is only capable of running up to 12.6.x but OCLP seems to ignore that limit. I guess I'm not 100% sure what OpenCore spoofs to give the latest updates, I thought that was the purpose of changing the SMBIOS.
Thank you. I know you can defer for 90 days, but ultimately, I'm looking to prevent OCLP from finding any major updates in the future without having to redo the deferment every 3 months.
Liking the black background and dark mode there might have to change my wallpaper lol.
Noticed macOS 14.3 updated the EFI firmware to 483.0.0.0.0 from 481.0.0.0.0 on the Mini7,1. No adverse effects observed. 
Just updated the MacBook Pro mid 2015 11,5 model to 14.3 via OCLP v1.3.0:
-No problems during Install, just wait patiently.
-Apply Patches and reboot.
(-and firmware is updated to 486.0000)
-No problems during Install, just wait patiently.
-Apply Patches and reboot.
(-and firmware is updated to 486.0000)
Last edited:
Did the same. Updated my MacBook Pro mid 2015 11,5 to 14.3 (OTA) with OCLP 1.3.0.
No problems during install and root patches.
However still facing problems with Win11 running in Parallels 19.2.1 (se attachment) No text visible. Changed HypervisorType from 1 to 0 and back in config.pvs in package for pvm file (Thanks to TommesPommes)
No problems during install and root patches.
However still facing problems with Win11 running in Parallels 19.2.1 (se attachment) No text visible. Changed HypervisorType from 1 to 0 and back in config.pvs in package for pvm file (Thanks to TommesPommes)
Attachments
Had the same problem with Sonoma and MacBookPro mid 2015 11.5.
Solution:
Add the following line to boot flags setting in Parallels Windows-VM settings:
"video.metal=0"
This can be found under VM configuration/Hardware/Boot sequence/Extended...
I've reported this Calc solution before, but so far I think it seems only to work for me on my MBP6,2 (non-metal Nvidia Tesla). It requires many steps, so only worth it if you need to use Calc for a while after applying the temporary fix:
- Open Calc
- Attempt a simple calculation (e.g., 2 + 2 =) and observe NaN. (C)lear the result.
- Switch to Scientific mode
- Perform simple calculation from step 2, observe NaN and (C)lear result
- Perform another simple calculation and observe good result
- Switch back to Basic mode
For similar bluetooth problems,
This is what I did to get bluetooth back.
Download Ben Baker's Hackintool.app. Use the app to edit NVRam (in tool bar) directly.
Look for the entries:
bluetoothExternalDongleFailed
bluetoothActiveControllerInfo
bluetoothInternalControllerinfo
Delete (using minus button at the bottom of the window) all the entries, and wait for the NVRam to refresh itself. At least one of the entries (bluetoothExternalDongleFailed) should come back with value of <00>. If not, repeat deleting the entries.
For me bluetooth worked again when I performed the above steps, bluetooth settings will show all previously paired devices, and auto connect to them just as before the update.
No Restart Needed.
Just updated my 12" MacBook 2017 to 14.3 using OCLP 1.3.0 - works perfectly. Had to redo root patches after the update, but that's normal. Huzzah!
ive been cycling thru the problems for 3 months now, i just downloaded another free calculator. end of problem
I AINT GOT TIME OR THE PATIENCE FOR ALL OF THAT!!!🤣
Out of curiosity: can you reproduce the issue after logged in to a new user and a different keyboard?
How is the machine connected to the internet?
How much space is available on the volume concerned?
Last edited:
Update on my smooth 14.3 update. Still smooth but it appears the power management functions are broken?
I went through and re-selected the number of minutes for screensaver and turn display off, but it doesn't seem to work. Even manually putting it to sleep last night (3 hours ago) and woke up to it on 🤷♂️
Thoughts? Solutions? Thank You.
Update:
Re-applying root patches in safe boot may have solved the issue? Time will tell, but looks promising.
I went through and re-selected the number of minutes for screensaver and turn display off, but it doesn't seem to work. Even manually putting it to sleep last night (3 hours ago) and woke up to it on 🤷♂️
Thoughts? Solutions? Thank You.
Update:
Re-applying root patches in safe boot may have solved the issue? Time will tell, but looks promising.
Last edited:
How is Sonoma 14.3 with OCLP v 1.3.0? I would be using it with an iMac 17,1. I know most people here seem to have much older macs so that's why I'm checking back. I thought the initial OCLP plan was to release updates when Apple did so should I wait for 1.4.0? Thanks
There is nothing blocking with 1.3.0.
1.4.0 is mainly a fix for restore partition, no new driver or new patch.
I have also the same iMac as you, on Ventura.
It's working pretty well except minor glitches (DRM video content in Safari, VMWare 3D acceleration)...
I know that Sonoma brings another glitch: some video files thumbnails appear with green artifacts in Finder and Photos.app (at least).
It's not blocking, just cosmetic.
Ventura was just 1 step after the last supported OS, Sonoma is 2 steps, the gap is bigger and there are more chances to discover some issues.
I use it on a separate volume, it's not bad, but a bit less polished (and a little slower I think) than Ventura for this kind of hardware.
1.4.0 is mainly a fix for restore partition, no new driver or new patch.
I have also the same iMac as you, on Ventura.
It's working pretty well except minor glitches (DRM video content in Safari, VMWare 3D acceleration)...
I know that Sonoma brings another glitch: some video files thumbnails appear with green artifacts in Finder and Photos.app (at least).
It's not blocking, just cosmetic.
Ventura was just 1 step after the last supported OS, Sonoma is 2 steps, the gap is bigger and there are more chances to discover some issues.
I use it on a separate volume, it's not bad, but a bit less polished (and a little slower I think) than Ventura for this kind of hardware.
make sure check your network connection Wifi/LAN is enabled and connected to internet.
I wouldn't say daily but random and periodically. If I put my machine to sleep at night and wake it up in the morning, it goes a while but again just random strike. After the power off/on bandaid, it'll go for a while leveraging sleep/wake.
Hello, I had a similar message : impossible to install Sonoma on my SSD (It work correctly with Ventura) I erase my SSD without results so I put a new SSD and it was possible to install Sonoma. My old SSD work always like an external SSD.
OK, good to know, I wasn't sure if 1.4.0 added anything necessary in terms of driver(s), or other fixes. I'll probably go with Sonoma over Ventura at this stage to avoid the red badge on system settings indicating an update, and since when I tried Sonoma a while back and had very few issues with it, it makes more sense to just do that. What I'll probably do is upgrade the main Fusion drive so I can have the speed, and then put Monterey on an external for VM, and Bios firmware updates, since that's all I'd need to keep it around for.
Yeah, I remember you have the same iMac model as me, however, in general most of the macs here are much older, or at least a couple years older. It would be nice if someone divided the unsupported threads into non metal vs metal support so it's easier to sort through. The metal supported machines tend not othave as many issues as the older non metal ones.