Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
If you answer a question with another question, just don't answer at all! I have no time for this.
Sorry, I removed the question mark! :eek: Not up to me to answer for others but here is the synopsis - Discrete GPUs seem to work whereas iGPUs boot-loop.
 
Last edited:
I have finally rolled back my iMac 17,1 to Ventura (OCLP 1.2.1)
I feel it smoother, faster, no glitches in videos thumbnails, no "strange" identification of my NVME Apple SSD.
For the moment, it seems more mature and solid.
As my only requirement is to be able to run the current Xcode release, it's enough for the moment.
I will return to Sonoma if I see some improvements in OCLP or if I am forced by Xcode...
 
Because a lot of people here don´t know what they are doing
Well, it would be smart to look into the summary of the lastest commit to see what changed before just running the nightly patcher. You can find a link to the summery on top of the file list:


Bildschirmfoto 2023-11-17 um 11.24.01.png


And as of today, nothing more than a Version bump to 1.3.0 has been commited:

 
Last edited:
  • Like
Reactions: K two
Hmmm… from the Blender 4 release notes (so, it could perhaps depend both on Metal 2.2 being required and on dropped support, for Nvidia Kepler and Intel Haswell: not an OCLP issue?):

Graphics Cards

  • The minimum required OpenGL version has been increased to 4.3 for Linux and Windows. (3478093183)
  • On macOS only Metal is supported now, and the OpenGL backend has been removed. A GPU with Metal 2.2 support is required. Intel Macs without an AMD GPU require a Skylake processor or higher. (cdb8a8929c)
  • Due to driver issues, support for Intel HD4000 series GPUs has been dropped.
So, I rolled back to Blender 3.6.5, which works without problems: no Blender 4 for my machine…

 
I'm experiencing a stalled boot on my MBP 9.2 i7 running 14.1 (I think, could be 14.0) after updating to OCLP 1.2.1. I'm not sure how and where to install the kernel debug kit - or if that will sort the issue.

The instructions when opening the kernel debug pkg overestimate my general levels of understanding and I'm not needing to install from another machine as I've two seperate HDs in this one, able to boot 10.13 or Sonoma.

Otherwise, am I correct to think that re-installing the OS would sort things? Any help or pointers greatly appreciated.
 
Last edited:
I'm experiencing a stalled boot on my MBP 9.2 i7 running 14.1 (I think, could be 14.0) after updating to OCLP 1.2.1. I'm not sure how and where to install the kernel debug kit - or if that will sort the issue.

The instructions when opening the kernel debug pkg overestimate my general levels of understanding and I'm not needing to install from another machine, I've two separate HDs in this machine, one booting 10.13, the other Sonoma (think it was 14.1).

Otherwise, am I correct to think that re-installing the OS would sort things? Any help or pointers greatly appreciated.
The KDK package will install the necessary files to the /Library/Developer on the disk where OCLP is installed. Since you can't boot from that disk, you could run the KDK installer while booted up from your other disk, which will install the files on that "other" disk, and then copy them to the same location on the non-booting disk. However, I don't think that will solve the non-booting issue as the KDK files are used during the root patching process after the OS boots (which gets stalled, as you said).
You can try reinstalling the OS from a Sonoma USB install disk, preferably the latest version 14.1.1. That may work, but no guarantee on that, as we don't know why the previous OS install is getting stalled.
How did you update to OCLP 1.2.1? Did you copy the OCLP app to the /Library/Application Support/Dortania folder (with an alias in the Applications folder? You probably should have run the OCLP 1.2.1 app and used the BUild and Install Open Core option, rebooted and reverted the previous Root patches before rebooting after the first reboot.
 
  • Like
Reactions: roronl and K two
I'm experiencing a stalled boot on my MBP 9.2 i7 running 14.1 (I think, could be 14.0) after updating to OCLP 1.2.1. I'm not sure how and where to install the kernel debug kit - or if that will sort the issue.

The instructions when opening the kernel debug pkg overestimate my general levels of understanding and I'm not needing to install from another machine as I've two seperate HDs in this one, able to boot 10.13 or Sonoma.

Otherwise, am I correct to think that re-installing the OS would sort things? Any help or pointers greatly appreciated.
Restart in safe mode. Hold Shift during boot. Then repatch. However, be aware of the boot loop issue on this model. I can't recommend to update neither to 14.1.1 or 14.2b using 1.2.1 until that's sorted with (fingers crossed) 1.3.0

Installing the KDK did not solve the issue on my 9,2 whatsoever.
 
How did you update to OCLP 1.2.1? Did you copy the OCLP app to the /Library/Application Support/Dortania folder (with an alias in the Applications folder? You probably should have run the OCLP 1.2.1 app and used the BUild and Install Open Core option, rebooted and reverted the previous Root patches before rebooting after the first reboot.

There was a prompt to update to 1.2.1 and I simply followed the instructions... there is an alias in the Applications folder to the Dortania folder where you suggest it should be.

I can't remember now in what order things were done - reverting to the previous Root patches wasn't carried out. I'm guessing from what you say, that would have prevented the problem?

Thanks for the help, it's much appreciated.
 
Restart in safe mode. Hold Shift during boot. Then repatch. However, be aware of the boot loop issue on this model. I can't recommend to update neither to 14.1.1 or 14.2b using 1.2.1 until that's sorted with (fingers crossed) 1.3.0

Installing the KDK did not solve the issue on my 9,2 whatsoever.

Thanks, I tried safe mode, couldn't get it to work, so now will proceed with a reinstall of the OS. Will update when sorted.
 
  • Like
Reactions: amaze1499
@Tickled

Safe mode only works if the system does not rely on any patched files to boot. Under normal conditions, it's possible to revert root patches during "normal" operation mode. This restores the untouched macOS snapshot and then you can start over. In my experience the KDK is downloaded automatically the first time you attend patching the system.

But since you opted for a new clean install, I would stay on 14.1.1 for now.

So far, I've noticed these issues In 14.2 beta 3:
  • The WindowServer crashes after Root patching Intel HD 4000 so you will be thrown back to the Logon Screen
  • Intel Power Gadget no longer works in 14.2 beta 3. Once the EnergyDriver.kext is loaded, all cores run at 100%. That's quite nasty. I suggest anybody to uninstall it prior to updating/upgrading.
 
about the face scanning problem on MBP 11,3 (14.1 with OCLP 1.2.1)
I think the problem photos didn't scan faces is, because with OCLP 1.2.1 photos app is forced to us NVIDIA Force GT 750M when MBP is charching (maybe because of memory is crashing with Intel Iris). And in my opinion face scanning (photoanalysisd) is only working when MBP is charching and using the Intel Iris Pro... as in earlier OCLP versions....
anyone else can confirm this?
 
  • Like
Reactions: jotzet
Thanks, I tried safe mode, couldn't get it to work, so now will proceed with a reinstall of the OS. Will update when sorted.
Anytime a version of OCLP is updated, rebuilding NVRAM is necessary. As soon as OCLP (OpenCanopy) appears on a restart from a cold boot, hit the Spacebar, index the selector to the far right and rebuild NVRAM from there. A wired KB is not required, btw. 🧐
 
[…] photos app is forced to us NVIDIA Force GT 750M when MBP is charching.

I've looked into the config.plist for the MBP11,3 and it does not contain any settings (DeviceProperties or boot-arguments) that indicate that it disables the iGPU. According to Apple, macOS switches between iGPU and dGPU automatically on the MBP11,3. In this case it's something that can be influenced via the EFI/config.

You could try to disable the GPU via the config.plist, then run Photos so it's using the iGPU to do the face scanning and then re-enable th GPU afterwards again.

There are several ways to disable the GPU:

  • Blocking the GPU driver from loading (not recommended)
  • Using Whatevergreen.kext and adding boot-arg -wegnoegpu to your config.plist disable it. (simple)
In any case: you should create a backup of your working EFI folder stored on a FAT32 formatted USB flash drive just in case something goes wrong. Because I don't know if Whatevergreen has negative side-effects when used on a real Mac, since it's a kext from the Hackintosh world.
 
  • Like
Reactions: amaze1499
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.