macOS 14 Sonoma on Unsupported Macs Thread

[amaze1499]

System preferences pop up each time I am logging in

Check your login items in System Settings and remove that entry if it exists.

 

[mwidjaya]

I think my old iMac might have a hardware issue of some kind.

1. What is the internal disk? Fusion HDD? Third party SSD (SATA or NVMe)?

2. I assume firmware is updated?

There is no hardware reason for the random boot up issue that I can think of.
Although, I would avoid having fusion drive completely.

 

[Kevo]

There are two drives. One is nvme and the other is sata ssd. Firmware is up to date. The last time it booted reliably was on Ventura with pre 1.0 OCLP. It did boot up normally a few times after the recent downgrade and then started having issues again, worse than when it was on Sonoma. Unplugging it and plugging it back in seems to help with how many attempts it takes to boot.

I am ordering a new set of adhesive strips so I can disassemble it and test each drive individually. I plan to test the battery while I'm in there too. That looks like a fun. 😂

 

[K two]

I like your startup disk name! I think that's a song by The Knack, isn't it?

Almost. But unintended.

 

[mwidjaya]

I plan to test the battery while I'm in there too.

Just replace with new CR2032, don't even bother to test it.

There are two drives. One is nvme and the other is sata ssd.

Ok. 3rd party nvme with adapter? In which case, it can be flaky. You should use the SATA ssd as boot disk.

Also worth checking with driveDX the health of both these disks, before even opening up the iMac.

I kept the Apple blade ssd (128gb) and use that as boot disk. The SATA ssd is where my user files are on though.

 

[hvds]

Just replace with new CR2032, don't even bother to test it.

Ok. 3rd party nvme with adapter? In which case, it can be flaky. You should use the SATA ssd as boot disk.

Also worth checking with driveDX the health of both these disks, before even opening up the iMac.

I kept the Apple blade ssd (128gb) and use that as boot disk. The SATA ssd is where my user files are on though. View attachment 2382499

No problems with a 3rd party NVME SSD (Aura Pro X2, 480GB) in my MBP11,1 (13", late 2013) which I use since 7 months. It has the right pinout for the Apple motherboard, no adapter needed. It replaces the original Apple SSD of 256GB which was too small for my purpose.

 

[nekton1]

The 1.50 final seems a long time coming after the 14.5 release. Is there a special reason other than overworked volumteers and shortage of resources holding it up?

 

[rbart]

The 1.50 final seems a long time coming after the 14.5 release. Is there a special reason other than overworked volumteers and shortage of resources holding it up?

because 1.5.0 doesn't have any specific feature for 14.5. No need to push it.
1.4.3 is working perfectly with 14.5

 

[nekton1]

Seems like a good reason.

 

[avro707]

Updated cMP 5,1 2012 OTA from 14.4.1 to 14.5 RC, OCLP 1.5.0n, no issues detected yet.
Awesome work from the Devs.

The only thing to mention on the 14.5 front (which may or may not affect here) is the known and bad Apple fault affecting those of us with 7,1 machines and NVME storage on PCI-E cards.

The drives drop out all the time. Very annoying. Apparently Sonnet has reported this to Apple. It’s very frustrating and wouldn’t surprise me if people here are caught by it.

This came along in Sonoma, didn’t exist before that.

 

[osxfr33k]

cMP 5,1 2012 MSI RX560 latest OCLP install of Sonoma. Ran into an issue that I didn’t go through the logic more carefully. I started out with the AMD HD 5770 then replaced with RX560. The OCLP was only patching USB 1.1 and Legacy WIFI but not Legacy AMD Polaris. What I realized is that it needs the KDK package to be able to do the rest of the patching correctly but without Internet the complete patching doesn’t happen, so I basically had to run the patcher one more time after I had Internet. Since most current installs need to patch WIFI if on later MacOS’s isn’t it just better to grab the KDK package for the MacOS you intend to install and place it on the USB flash and install that first then the patcher so all devices are patched at once.

 

[nikita-727]

OK. My only other suggestion would then be to rebuild OCLP and redo the patches as that has solved some niggling issues here over time. Should not hurt at least. YMMV.

I have tried both, nothing helped.

 

[houser]

I have tried both, nothing helped.

Ok, I'm afraid that's all I've got for now, assuming you checked the other suggestion you got about any remaining login items in settings or in your libraries. Good luck regardless. I'll take a guess that this has nothing to do with OCLP though.

 

[nikita-727]

Check your login items in System Settings and remove that entry if it exists.

I have checked it, there is no such entry.

 

[macpro_mid2014]

I have checked it, there is no such entry.

If you have space, create a new volume and clean install Sonoma 14.5 on it and patch with OCLP 1.4.3.
Do not forget to do a PRAM Reset when you boot.
If the problem persists I would suspect a defective hardware.

Edit: I remember having this issue with a Bluetooth Apple keyboard on a Mini late 2014. The keyboard was defective.

 

[PropClear]

Just for information newest nightly 1.5.0n is not working for me at the moment (both the deprecated .zip and new .pkg) binaries did not work for the time beeing in my case on test MP5,1 so be careful & fingers crossed for the upcoming builds (.pkg installer looks nice so far ;-)

Update: latest nightly is working fine again as expected - that was fast, great work and .pkg install without issues (also via RemoteDesktop ;-)...

 

[thegdn]

Just for information newest nightly 1.5.0n is not working for me at the moment (both the deprecated .zip and new .pkg) binaries did not work for the time beeing in my case on test MP5,1 so be careful & fingers crossed for the upcoming builds (.pkg installer looks nice so far ;-) View attachment 2383140

try new download

 

[rbart]

I think it's not the best time to use nightly.
They have completely remade the install process and use PKG install + privileged tool helper.
The work is not finished yet and they are pushing new commits very often.
This version doesn't improve patches, drivers ... It won't give improvements to your Mac (yet). It's just an improved way to install and manage OCLP.
You should stay to 1.4.3 for now until this change is stabilized.

 

[nekton1]

Well, it did not work. I prepared a full Monterey (latest version) boot disk on an external SSD and the MBA 9.1 boots from it fine but no firmware update runs. Looking online Monterey seems fussy about not having an Apple-branded boot disk when trying to update firmware and some people have forced it using teminal to load/run the correct firmware file from the OS installer. Seems like a lot of hassle so I'll just be happy with 526.0.0.0.0 for the time being.

So I decided to nuke and pave the SSD in this 12" MacBook running Sonona 14.5 and install a standard supported Monterey to update the firmware to the latest version, which went OK and the firmware is now 529.0.0.0.0. However, now I cannot install either Ventura or Sonoma using either OCLP 1.4.3 or 1.5n to either a completely formatted disk using DU from the installer USB or over a clean Monterey. In all possible cases (Ventura with OCLP 1.4.3 or 1.5n with empty formatted SDD or SSD with clean Monterey, and Sonoma with OCLP 1.4.3 or 1.5n with empty formatted SDD or SSD with clean Monterey) the install proceeds to the 20 minutes remaining and then the MBA shuts down. If I power it up and let the install proceed again, it starts again from 29 minutes remaining and counts down to 20 minutes remaining and powers down. I've gone so far as to try 10 restarts and the same thing over. I've tried resetting the NVRAM and using different USB sticks, all with the same result.
Any ideas very welcome.

 

[thegdn]

I think it's not the best time to use nightly.
They have completely remade the install process and use PKG install + privileged tool helper.
The work is not finished yet and they are pushing new commits very often.
This version doesn't improve patches, drivers ... It won't give improvements to your Mac (yet). It's just an improved way to install and manage OCLP.
You should stay to 1.4.3 for now until this change is stabilized.

I hear you and can see what you're saying.
I've just been running with scissors for more than a couple of decades. 27 years since first install of Linux.
First beta of OSX I was installing.
I am prepared for disaster. Expect it and am relieved when it does not happen.
This is what I do.

 

[coasterOneEightThree]

I use my Mac with the DJ software rekordbox 6, which has just been upgraded to version 7.
However, this version does not launch and closes immediately after starting.

I read in forums that this may be due to the lack of AVX2 support with certain older Intel processors.

I'm not a programmer, but since the great OCLP developers have also managed to get Sonoma to run on non-Metal capable Macs, I'm hoping for a possibility regarding AVX2.

Hence my question: Would it be possible to emulate AVX2 support with OCLP?

Here are the system requirements for rekordbox 7:

Download for free | rekordbox – DJ software

Download rekordbox for free! Start DJing today. DJ software for all levels of expertise!

rekordbox.com

(on the page in the right column: "You'll need an AVX2 compatible CPU")

For comparison rekordbox 6:

rekordbox update (ver. 6.0.1) brings enhanced functions

Industry-first AI tech shows positions of vocals in tracks and Beatsource LINK is now supported

rekordbox.com

"... you'll need an AVX compatible CPU."

My MacPro3,1 has INTEL XEON 5400 processors ("Harpertown") and they only seem to support AVX.

Thanks in advance for any comments in this regard.

 

[paalb]

Hence my question: Would it be possible to emulate AVX2 support with OCLP?

Today the status is no. Maybe in the future, but do not count on it.

 

[Soroka]

Hi, cMP 5,1 Radeon RX580. OCLP 1.5.0n. I recently changed the graphic card and when I try to update Post Install Root Patches to enable graphic acceleration it says me this:

- Unable to build new kernel cache
Subprocess failed.
Command: ['/Library/PrivilegedHelperTools/com.dortania.opencore-legacy-patcher.privileged-helper', '/usr/bin/kmutil', 'create', '--volume-root', '/System/Volumes/Update/mnt1', '--update-all', '--variant-suffix', 'release', '--allow-missing-kdk']
Return Code: 71
Standard Output:
Error Domain=KMErrorDomain Code=71 "Unable to resolve dependencies: 'com.apple.kext.AMDRadeonX4000' names a dependency on 'com.apple.iokit.IOAcceleratorFamily2', which was not found." UserInfo={NSLocalizedDescription=Unable to resolve dependencies: 'com.apple.kext.AMDRadeonX4000' names a dependency on 'com.apple.iokit.IOAcceleratorFamily2', which was not found.}
checking collections...
Warning: com.apple.driver.KextExcludeList was not found!
updated kernel binaries (Mach-O UUID changed from <unknown> to <unknown>)
rebuilding release collections:
boot kernel collection
system kext collection
failed to build release collection:
Unable to resolve dependencies: 'com.apple.kext.AMDRadeonX4000' names a dependency on 'com.apple.iokit.IOAcceleratorFamily2', which was not found.
Standard Error:
None

I have tried to return the previous AMD Graphic Card wich is a TeraScale 1 but if I revert the root patches and then install the RX 580 it never gave me signal after select disk. If I install root patcher for the other graphic card and then I try to install patches for RX 580 it says me this previos message.
Is there something I can do for avoid reinstall the whole Sonoma again and delete the hard drive?

 

[PropClear]

Hi, cMP 5,1 Radeon RX580. OCLP 1.5.0n. I recently changed the graphic card and when I try to update Post Install Root Patches to enable graphic acceleration it says me this:

- Unable to build new kernel cache
Subprocess failed.
Command: ['/Library/PrivilegedHelperTools/com.dortania.opencore-legacy-patcher.privileged-helper', '/usr/bin/kmutil', 'create', '--volume-root', '/System/Volumes/Update/mnt1', '--update-all', '--variant-suffix', 'release', '--allow-missing-kdk']
Return Code: 71
Standard Output:
Error Domain=KMErrorDomain Code=71 "Unable to resolve dependencies: 'com.apple.kext.AMDRadeonX4000' names a dependency on 'com.apple.iokit.IOAcceleratorFamily2', which was not found." UserInfo={NSLocalizedDescription=Unable to resolve dependencies: 'com.apple.kext.AMDRadeonX4000' names a dependency on 'com.apple.iokit.IOAcceleratorFamily2', which was not found.}
checking collections...
Warning: com.apple.driver.KextExcludeList was not found!
updated kernel binaries (Mach-O UUID changed from <unknown> to <unknown>)
rebuilding release collections:
boot kernel collection
system kext collection
failed to build release collection:
Unable to resolve dependencies: 'com.apple.kext.AMDRadeonX4000' names a dependency on 'com.apple.iokit.IOAcceleratorFamily2', which was not found.
Standard Error:
None

I have tried to return the previous AMD Graphic Card wich is a TeraScale 1 but if I revert the root patches and then install the RX 580 it never gave me signal after select disk. If I install root patcher for the other graphic card and then I try to install patches for RX 580 it says me this previos message.
Is there something I can do for avoid reinstall the whole Sonoma again and delete the hard drive?

Try an NVRam reset (SpceBar and right Shell Icon) if you haven't already tried ;-) may safeboot afterwards (shift klick on boot volume) and root patches!

 

[K two]

The current Nightly eliminates the need to install OCLP manually and runs as expected. 👏