macOS 14 Sonoma on Unsupported Macs Thread

[K two]

Very interesting piece with references to OCLP and Sonoma. https://aplus.rs/2024/hackintosh-almost-dead/ worth the read. FWIW 🧐

 

[deeveedee]

Very interesting piece with references to OCLP and Sonoma. https://aplus.rs/2024/hackintosh-almost-dead/ worth the read. FWIW 🧐

Very interesting. Since this is your post and it has some relevant security commentary, please feel free to also post in the OCLP Security thread if you wish. Thank you.

 

[K two]

Very interesting. Since this is your post and it has some relevant security commentary, please feel free to also post in the OCLP Security thread if you wish. Thank you.

To the best of my limited knowledge there has NEVER been an actual documented "Security Issue" directly attributed to the use of OCLP. And as previously written, prophecy is over the pay-grade, so unfounded conjecture s/b considered FUD. Since Beta testing is the interest, being the first to know, has an advantage. SilentKnight keeps the interest away from threats. 🚧 So with all respect, the request is declined.👎

 

[K two]

If your Mac evolved by way of the great dosdude1 patches, the current OCLP nightly is for you. https://github.com/dortania/OpenCore-Legacy-Patcher/blob/main/SOURCE.md and https://github.com/dortania/OpenCore-Legacy-Patcher/commit/a06b1f578ef48b388e6f16cbe6c539d5a7c43d0c 👀🧐

 

[deeveedee]

To the best of my limited knowledge there has NEVER been an actual documented "Security Issue" directly attributed to the use of OCLP. And as previously written, prophecy is over the pay-grade, so unfounded conjecture s/b considered FUD. Since Beta testing is the interest, being the first to know, has an advantage. SilentKnight keeps the interest away from threats. 🚧 So with all respect, the request is declined.👎

I was sincere in my comment when I said it was a very interesting post. When you introduced the article as mentioning OCLP and Sonoma, this is the part of the article that I thought you were referencing:

"Despite the valiant efforts of OCLP crew to make workarounds, those cards can work in Sonoma only if you seriously downgrade the macOS security." ... "Lest I forget — if macOS Ventura works for you, stay on it!"

Forgive me for misunderstanding your post and please accept my apology.

 

[OKonnel]

Safari Text Rendering Issues /w Sonoma on iMac14,2​

Anyone else is experiencing Text Rendering Issues since Sonoma when using Safari? I was getting distorted text here and there after minutes / hours (?) of usage. No matter which Update with Sonoma, or OCLP - it just does not go away. This is so frustrating!

A random visit of a page (here microsoft).
View attachment 2365471
This very page...

View attachment 2365470


Besides this I also have Issues with Metal rendering (I suppose) - but I'll post this separately here and on Discord, maybe some OCLP-angel can help!

- Java Metal (e.g when using IntelliJ Idea)
- VMWare Fusion
- most annoying: Faces detection on Apple's Photos.app is garbled

@OKonnel has a lot of experience with Nvidia Kepler Infra like iMac14,2

Thanks everyone!
Joachim

Hi @jotzet ! I just verified with my iMac using the same Microzozz page you posted and Safari works fine. I have also done other tests with positive results.
Anyway, I use OCLP 1.4.3 while I see you still have version 1.4.2. Besides, I already installed OCLP 1.5.0 Nightly last night even though I haven't rebooted the Mac to activate it yet, holding down the ALT key at the Gong sound and then pressing the BootEFI icon!
Regarding VMWare I don't know what to tell you as I prefer Parallels Desktop Pro which I purchased years ago for about $45, in subscription offer along with Parallels Tools and more. Parallels is always ahead of VMWare and other emulators and has excellent Support.

 

[htcmda]

Well I did it! Clean installed Sonoma 14.4.1 with OCLP 1.4.3. Seems pretty snappy, no issues with the install.

Now for the problem.
World of Warcraft doesn't run, so back to Monterey it is lol.

I did all the nvram reset stuff, forced the game to launch in windowed mode, forced legacy metal, dx11, dx12 you name it. Game doesn't even launch / crashes no matter what. I even pulled the backup off time machine from Monterey and tried it, still a no go.

Bootcamp was still there and available though, so that question is answered.
Thanks for answering any and all of the questions I've had thus far, maybe some games will run in the future and I'll give it another try.

 

[K two]

Well I did it! Clean installed Sonoma 14.4.1 with OCLP 1.4.3. Seems pretty snappy, no issues with the install.

Now for the problem.
World of Warcraft doesn't run, so back to Monterey it is lol.

I did all the nvram reset stuff, forced the game to launch in windowed mode, forced legacy metal, dx11, dx12 you name it. Game doesn't even launch / crashes no matter what. I even pulled the backup off time machine from Monterey and tried it, still a no go.

Bootcamp was still there and available though, so that question is answered.
Thanks for answering any and all of the questions I've had thus far, maybe some games will run in the future and I'll give it another try.

Which Mac? 🤷‍♂️

 

[OKonnel]

Hello everyone! Finally, armed with courage, I successfully upgraded my 13" MacBook Pro 7,1 (Mid 2010) to Sonoma.
I started out from macOS High Sierra and to install Sonoma I used a USB Key created via OCLP 1.5.0 Nightly .

I REPORT AN ERROR NOT TO MAKE
I created the USB Key with my iMac (14,2 27-inch, late 2013, with Sonoma 14.4.1 & OCLP 1.5.0n) but forgot to select that the Mac to be simulated was the MBP 7.1.
Therefore, at the end of the installation, I recreated the EFIBoot and redid the Post Install Patch from the MBP itself, indicating well that I wanted to create the EFIBoot for the MacBook Pro 7.1

FIRST problem I encountered after the installation was with the WiFi not connecting which, after several attempts, I solved this way:
- I turned off the Mac, turned it back on, and held down the three ALT P R keys, until I heard the Chime sound (Gong!) FOUR TIMES, in order to clear the NVRAM.
- after which, holding down only ALT, I selected the EFIBoot icon to reload OCLP.
- after logging in and rebooting, I disassociated the Network with the automatic connection that was in the list of my WiFi connections
- I connected an Ethernet cable to the Router
- I connected by re-choosing the Network from the list and entering the Password
CAUTION since it is apparently the issue resolving to have, initially, an Ethernet connection although I don't understand why.

PROBLEM
The fans are almost always running.
Can anyone tell me if this is normal?
Mainly it happens if I use Internet connections with updates, downloads, browser use while the fan slows down or seems to turn off while using applications, even heavy ones.

 

[rehkram]

Which Mac? 🤷‍♂️

@htcmda mentions it here: https://forums.macrumors.com/thread....2391630/page-244?post=33054337#post-33054337

 

[trifero]

@htcmda mentions it here: https://forums.macrumors.com/thread....2391630/page-244?post=33054337#post-33054337

It really is of help if it was mentioned in the same post.

 

[thegdn]

gave in and updated...
14.4.1 runs just fine.
Devs... 👍

 

[OKonnel]

macOS 14.4.1 Sonoma runs well in the mid-2010 13-inch MacBook Pro and is also very smooth but, unfortunately, iMovie does not work and neither does Final Cut Pro.
With Catalina (installed with dosdude1's patch) it was enough to install the old "NO Metal" versions of iMovie and Final Cut Pro, but in Sonoma these versions don't work and their icons appear with a ban sign.
Is there any solution? I seem to have read that in OCLP configuration you can enable or disable some options.
Also, my Apple TV movies start up fine, but then they close right away.
Thanks for help!!!

[Note. The strange thing is that the new Powerpoint works in presentation mode while with Catalina it did not work and you had to use an older "No Metal" version].

 

[htcmda]

It really is of help if it was mentioned in the same post.

Yea sorry, I've updated my info and put it in my signature.

 

[deeveedee]

macOS 14.4.1 Sonoma runs well in the mid-2010 13-inch MacBook Pro and is also very smooth but, unfortunately, iMovie does not work ...
With Catalina (installed with dosdude1's patch) it was enough to install the old "NO Metal" versions of iMovie ...

[Note. The strange thing is that the new Powerpoint works in presentation mode while with Catalina it did not work and you had to use an older "No Metal" version].

I experienced the same on my MBP6,2 (non-metal NVidia Tesla). I tried a few tricks that I found posted, but while I was able to install iMovie and launch it. iMovie crashes when creating a new project. I tested as far back as Big Sur.

 

[Serqetry]

Anyone having issues with 1.4.0n and a Sintech adapter+3rd party NVMe? I bumped up my daily MBA to 1.4.0 a week or so ago and have been running into panic'd lockup several times a day, including sometimes immediately on reboot. I went back to 1.3.0 and seem to be stable for the past few hours.

Panic example below:

Spoiler

panic(cpu 2 caller 0xffffff80100c843e): nvme: "3rd party NVMe controller. Command timeout. Write. fBuiltIn=1 MODEL=Sabrent FW=RKT303.3 CSTS=0xffffffff US[1]=0x0 US[0]=0x7b VID=0x1987 DID=0x5012 CRITICAL_WARNING=0x0.\n" @IONVMeController.cpp:6147
Panicked task 0xffffff94e7f4adf8: 193 threads: pid 0: kernel_task
Backtrace (CPU 2), panicked thread: 0xffffff8682ae0b30, Frame : Return Address
0xffffffff00bdba80 : 0xffffff800e036c41 mach_kernel : _handle_debugger_trap + 0x4b1
0xffffffff00bdbad0 : 0xffffff800e1955c0 mach_kernel : _kdp_i386_trap + 0x110
0xffffffff00bdbb10 : 0xffffff800e184d0c mach_kernel : _kernel_trap + 0x55c
0xffffffff00bdbb90 : 0xffffff800dfd3971 mach_kernel : _return_from_trap + 0xc1
0xffffffff00bdbbb0 : 0xffffff800e036f2d mach_kernel : _DebuggerTrapWithState + 0x5d
0xffffffff00bdbca0 : 0xffffff800e0365d3 mach_kernel : _panic_trap_to_debugger + 0x1e3
0xffffffff00bdbd00 : 0xffffff800e7d8d0b mach_kernel : _panic + 0x84
0xffffffff00bdbdf0 : 0xffffff80100c843e com.apple.iokit.IONVMeFamily : __ZN16IONVMeController18RequestAsyncEventsEj
0xffffffff00bdbe20 : 0xffffff800e713b9c mach_kernel : __ZN18IOTimerEventSource15timeoutSignaledEPvS0_ + 0x8c
0xffffffff00bdbe70 : 0xffffff800e713ab6 mach_kernel : __ZN18IOTimerEventSource17timeoutAndReleaseEPvS0_ + 0xc6
0xffffffff00bdbea0 : 0xffffff800e090638 mach_kernel : _thread_call_delayed_timer + 0x508
0xffffffff00bdbee0 : 0xffffff800e0916c8 mach_kernel : _thread_call_delayed_timer + 0x1598
0xffffffff00bdbfa0 : 0xffffff800dfd319e mach_kernel : _call_continuation + 0x2e
     Kernel Extensions in backtrace:
        com.apple.iokit.IONVMeFamily(2.1)[5985F50F-0A7D-3A4B-88B3-9D4C9EC4E43B]@0xffffff80100c1000->0xffffff80100ebfff
           dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[07852425-8607-3C1A-B273-92FC0221EC02]@0xffffff800f69e000->0xffffff800f6d4fff
           dependency: com.apple.iokit.IOPCIFamily(2.9)[1B194276-D13F-32DD-8B6D-4751C1C73603]@0xffffff8010355000->0xffffff8010386fff
           dependency: com.apple.iokit.IOReportFamily(47)[7EE0B816-0F22-3141-992C-ECEA9CA4B021]@0xffffff8010397000->0xffffff8010399fff
           dependency: com.apple.iokit.IOStorageFamily(2.1)[A96D850A-038F-31D7-9F3D-A6775064548E]@0xffffff801048d000->0xffffff80104a4fff

I just upgraded my Ventura Mac Pro 5,1 to Sonoma 14.4.1 and I am getting those same NVMe controller crashes every day or so. Anyone know if there is a solution? I am using a WD SN740 512gb blade in a "xqjtech" PCIe 3.0 4x card from Amazon. Was working fine with Ventura.

I notice on the NVMeFix github page it says:
NOTE: NVMeFix supports up to macOS Sonoma (14), but some features might not be available on newer versions as of now, like the timeout panic fix.

And then there is a boot-arg parameter:
nand-io-timeoutms: Timeout for NVMe requests in ms, 35 s by default

I wonder if changing this would help... or if that note means 14.4.1 no longer works with this "timeout panic fix".

 

[Pachnes]

as always Devs...
Thanks muchly. Wonderful work.
macOS 14.5 oclp 1.5.0 n

...and now the 2012 Mini

Does the Macmini 2012 work with Sonoma 14.5 Beta 1?

 

[thegdn]

Does the Macmini 2012 work with Sonoma 14.5 Beta 1?

indeed.

 

[Larsvonhier]

macOS 14.4.1 Sonoma runs well in the mid-2010 13-inch MacBook Pro and is also very smooth but, unfortunately, iMovie does not work and neither does Final Cut Pro.
With Catalina (installed with dosdude1's patch) it was enough to install the old "NO Metal" versions of iMovie and Final Cut Pro, but in Sonoma these versions don't work and their icons appear with a ban sign.
Is there any solution? I seem to have read that in OCLP configuration you can enable or disable some options.
Also, my Apple TV movies start up fine, but then they close right away.
Thanks for help!!!

[Note. The strange thing is that the new Powerpoint works in presentation mode while with Catalina it did not work and you had to use an older "No Metal" version].

A couple of months back we had similar peculiarities with M$ products, namely Word not displaying selected blocks of texts (just garbled pixel mud). A few M$ Office updates later it worked again as before (no changes in machine or patches on them, so clearly a bug fix in the application).
As for the older iMovie "no Metal" version, I´d guess it is time to contact the author of the tool "Retroactive" to get it running again on our non-metal machines. Another candidate would be the non-metal Maps app, I tried to port things over from El Capitan, but I´m not experienced enough to resolve all the library dependencies involved with it...

 

[Larsvonhier]

MacBook Pro 4,1 (17" glossy HD version) updated to 14.4.1 with OCLP 1.4.3 successfully. Just took a bit longer in one of the reboot-phases without seemingly any progress. Had to be patient...

 

[Larsvonhier]

gave in and updated...
14.4.1 runs just fine.
Devs... 👍

You might already know that your 3,1 accepts 800MHz RAM instead of the 667MHz (formerly the max. on 1,1 and 2,1 machines). Around 20% speed increase with memory dependent apps then...

 

[madmind]

I've recently realized that the latest OCLP root patches are causing an issue with my MOTU M6 Audio interface. I run a dual Boot Monterey/ Sonoma setup on my Mac Pro 5,1 and when the root patches are applied to my Sonoma install, the M6 does NOT show up as an output or an input in my sound drop down menu (although the M6 DOES show up in the system report under the audio and USB Panes). When the root patches are applied to my Monterey install it DOES show up. When I revert the patches in Sonoma the inputs and outputs return, but then I'm left with no WIFI, Bluetooth, or Graphics Acceleration. Ive also noticed that even though the M6 is connected directly to the Mac Pro the system report shows that it's connected to a hub. Is anyone else experiencing this issue or does anyone have a solution?

 

[thegdn]

You might already know that your 3,1 accepts 800MHz RAM instead of the 667MHz (formerly the max. on 1,1 and 2,1 machines). Around 20% speed increase with memory dependent apps then...

Thanks. It’s on my list. Couple of bad 4gb sticks showing as 2gb randomly. 32gb installed showing as 28gb. Then no boot with said memory board installed. Time for another small investment.

 

[PropClear]

I've recently realized that the latest OCLP root patches are causing an issue with my MOTU M6 Audio interface. I run a dual Boot Monterey/ Sonoma setup on my Mac Pro 5,1 and when the root patches are applied to my Sonoma install, the M6 does NOT show up as an output or an input in my sound drop down menu (although the M6 DOES show up in the system report under the audio and USB Panes). When the root patches are applied to my Monterey install it DOES show up. When I revert the patches in Sonoma the inputs and outputs return, but then I'm left with no WIFI, Bluetooth, or Graphics Acceleration. Ive also noticed that even though the M6 is connected directly to the Mac Pro the system report shows that it's connected to a hub. Is anyone else experiencing this issue or does anyone have a solution?

Is your interface linked to internal usb or pcie usb 3 card?

 

[amaze1499]

Just in case someone else also struggles with the issue MagicMouse or perhaps other devices disconnecting from Sonoma repeatedly:

Since the option "Reset Bluetooth module" is not available anymore in Sonoma and pulling all plist files from all the places did not solve the issue in my case, I booted up an old iMac running HighSierra paired and reset my MagicMouse using factory reset all connected Apple devices via Click Bluetooth Shift Option in Menubar.

Suddenly the mouse is recognized without any issues and works like charm.

Hope this helps.