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.
I tried with Geekbench 5 (both the free trial and the Mac App Store version): buy sadly, on my machine, while booted into Monterey that test doesn’t seem to work (the test window briefly opens with a “Gathering information…” text, but then immediately closes); while on Big Sur it works as it should. Sorry for that…
This is really helpful information for systems with NVIDIA dGPU running Monterey:
  1. OpenCL is still broken in general (whatever this means for other third party apps)
  2. Photoshop is working...(again)
 
  • Love
  • Like
Reactions: OKonnel and Sven G
Could this OpenCL problem perhaps be fixed, in a future OCLP release…? That would be really cool (and it also seems to be the only not fully working thing remaining, on the MBP11,3)…
 
  • Like
Reactions: OKonnel
Could this OpenCL problem perhaps be fixed, in a future OCLP release…? That would be really cool (and it also seems to be the only not fully working thing remaining, on the MBP11,3)…
Never say never, but currently no developer has such a system and the using usual suspects when it comes to patching, just look up my former issue link, failed.

Currently I have not much hope unless somebody donates a Kepler based Mac to the core developer (team). Unfortunately with the upcoming macOS 13 announcement focus will change to this release, but any solution would/could be back ported easily.
 
  • Like
Reactions: Sven G
If it can be useful, here is the output of /Applications/Geekbench\ 5.app/Contents/Resources/geekbench_x86_64 --compute --verbose from the Terminal on the MBP11,3, in Monterey:
Code:
% /Applications/Geekbench\ 5.app/Contents/Resources/geekbench_x86_64 --compute --verbose
[…]
  Running Gathering system information
[0605/164153:WARNING:src/halogen/cl/exception.h(36)] halogen::RuntimeError: clGetDeviceInfo(object_, info_name, 0, 0, &info_size) returned -59
[0605/164153:WARNING:src/halogen/cl/exception.h(36)] halogen::RuntimeError: clGetDeviceInfo(object_, info_name, 0, 0, &info_size) returned -59
System Information
  Operating System              macOS 12.4 (Build 21F79)
  Model                         MacBook Pro (15-inch Retina Late 2013)
  Model ID                      MacBookPro11,3
  Motherboard                   Apple Inc. Mac-[…] MacBookPro11,3
  BIOS                          Apple Inc. 433.120.6.0.0

Processor Information
  Name                          Intel Core i7-4850HQ
  Topology                      1 Processor, 4 Cores, 8 Threads
  Identifier                    GenuineIntel Family 6 Model 70 Stepping 1
  Base Frequency                2.30 GHz
  L1 Instruction Cache          32.0 KB x 4
  L1 Data Cache                 32.0 KB x 4
  L2 Cache                      256 KB x 4
  L3 Cache                      6.00 MB
  L4 Cache                      128 MB

Memory Information
  Size                          16.0 GB
  Type                          DDR3
  Speed                         1600 MT/s

OpenCL Information
  Platform Vendor               Apple
  Platform Name                 Apple
  Device Vendor                 NVIDIA
  Device Name                   GeForce GT 750M
  Device Driver Version         16.0 .12 355.11.11.10.10.143
  Maximum Frequency             810 MHz
  Compute Units                 2
  Device Memory                 2.00 GB


OpenCL
  Running Sobel
[0605/164153:ERROR:src/halogen/cl/program.cpp(36)] Cannot load arch runtime[0605/164153:WARNING:src/halogen/cl/exception.h(36)] halogen::RuntimeError: clBuildProgram returned -11
[0605/164153:ERROR:src/interface/console/consolemain.cpp(818)] Geekbench encountered an internal error and cannot continue. Please contact support@primatelabs.com for assistance.

Internal error message: clBuildProgram returned -11.
 
Last edited:
Is there anyone else experiencing a loginwindow crash when waking from sleep? My hardware is a MacBook Air 4,2 on Monterey 12.4 with OCLP 0.4.6. I first experienced this loginwindow crash with 12.3.1 and OCLP 0.4.4 and after updating both OCLP from 0.4.4=>0.4.5=>0.4.6 and Monterey=>12.4, loginwindow still crashes when I open the lid to wake the machine from sleep.

I have uploaded a pastebin of the crash details here: https://pastebin.pl/view/9a703fcb
Update: I suspected that my issue was related to my setting a Memoji for my user image. I changed it to another static image and Voila! I'm assuming its metal related, as it never animated on my non-Metal machines anyways.
 
  • Like
Reactions: hwojtek
Hi there guys I am having a hard time trying to make Opencore the default boot device. Every time I start up my 2010 MBA, I get a white/black screen and I have to boot into opencore using the option key to get it to work. I have tried using the control key to get the refresh symbol to make opencore the default boot device but it doesn't work. I have tried reseting PRAM and SMC and it didn't help at all. Does anybody else have any ideas on how I could fix this?
 
Hi there guys I am having a hard time trying to make Opencore the default boot device. Every time I start up my 2010 MBA, I get a white/black screen and I have to boot into opencore using the option key to get it to work. I have tried using the control key to get the refresh symbol to make opencore the default boot device but it doesn't work. I have tried reseting PRAM and SMC and it didn't help at all. Does anybody else have any ideas on how I could fix this?
Just bless the EFI partition: mount the EFI using Clover Configurator and run Bless Opencore. You have the tools in

 
Nope I just clean installed this MacBook with only Monterey installed.
Weird. Normally that error is due to a mess in the partition table or certificates from EFI installations of windows. Take a look at

 
Weird. Normally that error is due to a mess in the partition table or certificates from EFI installations of windows. Take a look at


I managed to get the tool to work by completely disabling SIP as the opencore legacy patcher only disables SIP partially. However, the tool did not fix my issue and I still must use the option key to boot into the EFI partition manually or else I just get a white screen.
 
OpenCore 4.5 on a Fusion Drive.

Trying to install OpenCore Legacy Patcher v0.4.5 in Terminal. The menu option "2. Install OpenCore to USB/internal drive" gives the option to install on the SSD or HDD. Which is correct, or can both be installed?

###############
# Select Disk #
###############
Missing disks? Ensure they have an EFI or FAT32 partition.
0. disk0: APPLE SSD SM128E (121.3 GB)
1. disk1: APPLE HDD HTS541010A9E662 (1.0 TB)
3. disk3: 3200BMV External (320.1 GB)
4. disk4: SanDisk 3.2Gen1 (494.2 GB)
B. Back
Please select the disk you would like to install OpenCore to:

Various searches did not give a clear answer. Out of date comments that APFS does not support fusion drives or suggestions to disable the Fusion Drive.
 
OpenCore 4.5 on a Fusion Drive.

Trying to install OpenCore Legacy Patcher v0.4.5 in Terminal. The menu option "2. Install OpenCore to USB/internal drive" gives the option to install on the SSD or HDD. Which is correct, or can both be installed?

###############
# Select Disk #
###############
Missing disks? Ensure they have an EFI or FAT32 partition.
0. disk0: APPLE SSD SM128E (121.3 GB)
1. disk1: APPLE HDD HTS541010A9E662 (1.0 TB)
3. disk3: 3200BMV External (320.1 GB)
4. disk4: SanDisk 3.2Gen1 (494.2 GB)
B. Back
Please select the disk you would like to install OpenCore to:

Various searches did not give a clear answer. Out of date comments that APFS does not support fusion drives or suggestions to disable the Fusion Drive.
install to 0. And it's not a good idea to install more than 1x OCLP.
 
OpenCore 4.5 on a Fusion Drive.

Trying to install OpenCore Legacy Patcher v0.4.5 in Terminal. The menu option "2. Install OpenCore to USB/internal drive" gives the option to install on the SSD or HDD. Which is correct, or can both be installed?

###############
# Select Disk #
###############
Missing disks? Ensure they have an EFI or FAT32 partition.
0. disk0: APPLE SSD SM128E (121.3 GB)
1. disk1: APPLE HDD HTS541010A9E662 (1.0 TB)
3. disk3: 3200BMV External (320.1 GB)
4. disk4: SanDisk 3.2Gen1 (494.2 GB)
B. Back
Please select the disk you would like to install OpenCore to:

Various searches did not give a clear answer. Out of date comments that APFS does not support fusion drives or suggestions to disable the Fusion Drive.
I do use Fusion Drives in three of my iMacs (SATA SSD + SATA HDD). I have created them within Monterey install/recovery utility, using a Terminal command diskutil resetFusion. After that I installed OpenCore (only) to the SSD EFI folder. It works reliably - in one case I even (deliberately) swapped the SATA port connections of the SSD and the HDD. The machine simply started from the EFI on the SSD and properly recognized the Fusion Drive.
 
Hello,
I have Monterey installed on my early 2009 iMac and I wanted to reboot into a network disk. However, when I try to do so, it directly goes into the EFI boot picker which does not show the network disk. Before installing Monterey I was able to netboot, and it still shows up in System Preferences in Mavericks. Is there a way to temporarily disable the EFI boot so I can netboot?
Thanks
 
Hello,
I have Monterey installed on my early 2009 iMac and I wanted to reboot into a network disk. However, when I try to do so, it directly goes into the EFI boot picker which does not show the network disk. Before installing Monterey I was able to netboot, and it still shows up in System Preferences in Mavericks. Is there a way to temporarily disable the EFI boot so I can netboot?
Thanks
On reboot do a PRAM reset and hold the option key. You will enter the EFI boot picker with no OpenCore loaded.
 
  • Like
Reactions: tensixturtle
Since the topic of Photoshop 2022 on unsupported Macs came up... if anyone knows how to pass the SSE4.2 requirement for the installer to run, I'd be glad to hear it.
 
Screenshot 2022-06-06 at 21.27.41.png
 
Last edited:
Found the procedure to disable the known to fail discrete graphics chip in the online guide. I have a late 2011 MBP8,2 with the AMD HD 6750 & the HD 3000 graphics. Never knew it could be updated to Monterey (incredible work by the OCLP devs!). That MBP is still running High Sierra. Do you think it is better to try Big Sur first or go directly to Monterey?
After a clean install using OCLP 0.4.5, there were many problems getting the MBP to a state where I could run the post-install root patch (the worst was the bluetooth not recognizing a mouse, and the trackpad being very difficult to use).
After running the OCLP post-install root patch, most things settled down, but I still do not see the Energy Saver System Preferences pane. Is that normal? While the Energy Saver pane is installed in the System/Library/Application Support/PreferencePanes subfolder, it doesn't sho up in the System Preferences. I do have that pane on my iMac running the same 12.4 version of Monterey with OCLP 0.4.5.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.