From ba43de9c4fe99609d4951ab1ed839eb45cff7975 Mon Sep 17 00:00:00 2001 From: ParaDoX1994 <35791009+ParaDoX1994@users.noreply.github.com> Date: Sun, 29 Oct 2023 23:00:35 +0000 Subject: [PATCH] =?UTF-8?q?Deploying=20to=20gh-pages=20from=20=20@=20d23e4?= =?UTF-8?q?835423219990677583e0f3a895e7d6384e5=20=F0=9F=9A=80?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- 404.html | 6 +++--- ACCEL.html | 6 +++--- BOOT.html | 6 +++--- BUILD.html | 6 +++--- DEBUG.html | 6 +++--- DONATE.html | 6 +++--- HOW.html | 6 +++--- ICNS.html | 8 ++++---- INSTALLER.html | 6 +++--- ISSUES-HOLD.html | 6 +++--- LICENSE.html | 6 +++--- MODELS.html | 6 +++--- MONTEREY-DROP.html | 6 +++--- PATCHEXPLAIN.html | 6 +++--- POST-INSTALL.html | 6 +++--- SONOMA-DROP.html | 6 +++--- START.html | 6 +++--- TERMS.html | 6 +++--- TROUBLESHOOTING.html | 6 +++--- UNINSTALL.html | 10 +++++----- UNIVERSALCONTROL.html | 6 +++--- UPDATE.html | 8 ++++---- VENTURA-DROP.html | 6 +++--- WINDOWS.html | 6 +++--- assets/js/32.0bcc4938.js | 1 - assets/js/32.1ee9c6a2.js | 1 + assets/js/{app.ae751934.js => app.07658647.js} | 4 ++-- index.html | 6 +++--- 28 files changed, 82 insertions(+), 82 deletions(-) delete mode 100644 assets/js/32.0bcc4938.js create mode 100644 assets/js/32.1ee9c6a2.js rename assets/js/{app.ae751934.js => app.07658647.js} (93%) diff --git a/404.html b/404.html index 107a284fc..8eacda52c 100644 --- a/404.html +++ b/404.html @@ -11,13 +11,13 @@ - + -

404

There's nothing here.
+ - + diff --git a/ACCEL.html b/ACCEL.html index bbf5090cf..c4d15e383 100644 --- a/ACCEL.html +++ b/ACCEL.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# Working Around Legacy Acceleration Issues

The below page is for users experiencing issues with their overall usage of macOS Big Sur / Monterey / Ventura and the Legacy Graphics Acceleration patches. Note that the following GPUs currently do not have acceleration support in Big Sur / Monterey / Ventura:

  • Intel 3rd and 4th Gen - GMA series

For those unfamiliar with what is considered a non-Metal GPU, see the chart below:

macOS GPU Chart

Metal is Apple's in-house graphics API that acts as a replacement for OpenGL/OpenCL, introduced in 2015. With the release of macOS Mojave, every system without a Metal-capable GPU was dropped.

Graphics Vendor Architecture Series Supports Metal
ATI TeraScale 1 HD 2XXX - HD 4XXX No
TeraScale 2 HD 5XXX - HD 6XXX
AMD GCN (and newer) HD 7XXX+ Yes
NVIDIA Tesla 8XXX - 3XX No
Fermi 4XX - 5XX
Kepler 6XX - 7XX Yes
Maxwell 8XX - 9XX No (on 10.14 and newer)
Pascal 10XX
Intel GMA GMA 900 - GMA X3000 No
Iron Lake HD series
Sandy Bridge HD 3000
Ivy Bridge (and newer) HD 4000 Yes

# Broken Background Blurs

By default with the non-Metal acceleration patches, many background blur menus may act distorted when moving a cursor over it. With 0.4.1 and newer, users can enable a new Beta Blur feature to try and resolve the issue:

Do note that enabling beta blurs can be more demanding on slower hardware

# Downloading older non-Metal Apps

Many Apple apps now have direct reliance on Metal for proper functioning, however legacy builds of these apps still do work in Big Sur. See below for archive of many apps such as Pages, iMovie, GarageBand.

Note: This archive assumes that you own these copies of these apps through the Mac App Store, Dortania does not condone piracy

# Unable to run Zoom

Currently Zoom relies partially on Metal and so needs a small binary patch. Dosdude1 has provided a nice script for this:

# Unable to grant special permissions to apps (ie. Camera Access to Zoom)

Currently for Ventura 13.3 and newer, due to new patches required, permissions are yet again broken. Use TCCPlus in the Workaround dropdown to work around the issue.

This issue is fully resolved for 13.2.1 and lower starting from 0.2.5.

Workaround for 0.2.4, Ventura 13.3+

Due to the usage of amfi_get_out_of_my_way=1, macOS will fail to prompt users for special permissions upon application start as well as omit the entires in System Preferences. To work around this, we recommend users install tccplus to manage permissions.

Download TCCPlus (opens new window)

Example usage with Discord and microphone permissions:

# Open Terminal and run the following commands
+     (opens new window)    
 
# Working Around Legacy Acceleration Issues
  
The below page is for users experiencing issues with their overall usage of macOS Big Sur / Monterey / Ventura and the Legacy Graphics Acceleration patches. Note that the following GPUs currently do not have acceleration support in Big Sur / Monterey / Ventura:
 
  • Intel 3rd and 4th Gen - GMA series
 
For those unfamiliar with what is considered a non-Metal GPU, see the chart below:
 
macOS GPU Chart 
Metal is Apple's in-house graphics API that acts as a replacement for OpenGL/OpenCL, introduced in 2015. With the release of macOS Mojave, every system without a Metal-capable GPU was dropped.
 
Graphics Vendor Architecture Series Supports Metal
 
ATI TeraScale 1 HD 2XXX - HD 4XXX No
 
TeraScale 2 HD 5XXX - HD 6XXX
 
AMD GCN (and newer) HD 7XXX+ Yes
 
NVIDIA Tesla 8XXX - 3XX No
 
Fermi 4XX - 5XX
 
Kepler 6XX - 7XX Yes
 
Maxwell 8XX - 9XX No (on 10.14 and newer)
 
Pascal 10XX
 
Intel GMA GMA 900 - GMA X3000 No
 
Iron Lake HD series
 
Sandy Bridge HD 3000
 
Ivy Bridge (and newer) HD 4000 Yes
 
# Broken Background Blurs
 
By default with the non-Metal acceleration patches, many background blur menus may act distorted when moving a cursor over it. With 0.4.1 and newer, users can enable a new Beta Blur feature to try and resolve the issue:
 
 
Do note that enabling beta blurs can be more demanding on slower hardware
 
# Downloading older non-Metal Apps
 
Many Apple apps now have direct reliance on Metal for proper functioning, however legacy builds of these apps still do work in Big Sur. See below for archive of many apps such as Pages, iMovie, GarageBand.
  
Note: This archive assumes that you own these copies of these apps through the Mac App Store, Dortania does not condone piracy
 
# Unable to run Zoom
 
Currently Zoom relies partially on Metal and so needs a small binary patch. Dosdude1 has provided a nice script for this:
  
# Unable to grant special permissions to apps (ie. Camera Access to Zoom)
 
Currently for Ventura 13.3 and newer, due to new patches required, permissions are yet again broken. Use TCCPlus in the Workaround dropdown to work around the issue.
 
This issue is fully resolved for 13.2.1 and lower starting from 0.2.5.
 
Workaround for 0.2.4, Ventura 13.3+ 
Due to the usage of amfi_get_out_of_my_way=1, macOS will fail to prompt users for special permissions upon application start as well as omit the entires in System Preferences. To work around this, we recommend users install tccplus to manage permissions.
 
Download TCCPlus (opens new window)
 
Example usage with Discord and microphone permissions:
 
# Open Terminal and run the following commands
 cd ~/Downloads/
 chmod +x tccplus
 ./tccplus add Microphone com.hnc.Discord
@@ -45,6 +45,6 @@ nvram FA4CE28D-B62F-4C99-9CC3-6815686E30F9:gpu-power-prefs

-    
+    
   
 
diff --git a/BOOT.html b/BOOT.html
index 5fb3b8631..852396144 100644
--- a/BOOT.html
+++ b/BOOT.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
   
   
@@ -19,7 +19,7 @@
     GitHub
      (opens new window)

# Booting OpenCore and macOS

Now we finally get to boot OpenCore!

Reboot the machine while holding Option to select the EFI Boot entry with the OpenCore icon (holding the Control key will make this the default boot entry):

  • This will be the Mac Boot Picker

Note for Mac Pros/Xserves/iMacs with unflashed GPUs

(Adapted from the OpenCore on the Mac Pro guide (opens new window))

For Mac Pro, Xserve and, iMac users with non-flashed GPUs, you can still easily boot OpenCore and view the entire boot process.

Firstly, open the Terminal and run the following command:

sudo nvram "recovery-boot-mode=unused" && sudo reboot recovery
+     (opens new window)    
 
# Booting OpenCore and macOS
 
Now we finally get to boot OpenCore!
 
Reboot the machine while holding Option to select the EFI Boot entry with the OpenCore icon (holding the Control key will make this the default boot entry):
 
  • This will be the Mac Boot Picker
 
 
Note for Mac Pros/Xserves/iMacs with unflashed GPUs 
(Adapted from the OpenCore on the Mac Pro guide (opens new window))
 
For Mac Pro, Xserve and, iMac users with non-flashed GPUs, you can still easily boot OpenCore and view the entire boot process.
 
Firstly, open the Terminal and run the following command:
 
sudo nvram "recovery-boot-mode=unused" && sudo reboot recovery
 
This will make your machine reboot into the Recovery Environment. Alternatively, holding Command + R when your machine is starting up will also let you enter the Recovery.
 
Secondly, open the Recovery Environment's Terminal (Menu bar > Utilities > Terminal).
 
Now you'll want to get a list of drive identifiers. To do so, run the following command:
 
diskutil list
 
The command should produce a list of drives installed in your system:
 
 
Keep track of the drive with the OCLP install. You will need the drive identifer for later.
 
Now you'll want to mount the EFI partition (where OCLP is installed, though it may differ if you've installed OCLP to a FAT-32 volume).
 
Run the following command (Replace X with the drive number):
 
diskutil mount diskXs1
@@ -35,6 +35,6 @@ If everything is correct, the EFI partion should be mounted.
 
Now you'll w
       
       ⟶
- + diff --git a/BUILD.html b/BUILD.html index e829396fb..5d431c874 100644 --- a/BUILD.html +++ b/BUILD.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# Building and installing OpenCore

Now that we have a macOS installer, let's now build our OpenCore configuration!

If you haven't downloaded OpenCore Patcher yet, do so now:

Next, run the OpenCore-Patcher.app:

WARNING

OpenCore configurations are hardware specific. + (opens new window)

# Building and installing OpenCore

Now that we have a macOS installer, let's now build our OpenCore configuration!

If you haven't downloaded OpenCore Patcher yet, do so now:

Next, run the OpenCore-Patcher.app:

WARNING

OpenCore configurations are hardware specific. If you're building OpenCore for a different model than you're currently running, it is absolutely necessary to select the proper model from Settings.

Here we'll select Build and Install OpenCore and start building:

Start Building Finished Building
OCLP GUI Build Finished

Once it finishes building, you'll want to select the Install OpenCore button:

  • If you created a macOS USB manually and don't see it listed, make sure it's either formatted as GUID/GPT or has a FAT32 partition for OpenCore to reside on.
Select Drive Select Partition

# Once finished, head to Booting OpenCore and macOS

⟵ ⟶

- + diff --git a/DEBUG.html b/DEBUG.html index 626fb0389..1a1b5b0ba 100644 --- a/DEBUG.html +++ b/DEBUG.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# How to debug with OpenCore

For those who've hit an odd bug and are unsure if it's user error or within the patcher, we recommend asking on the OpenCore Patcher Paradise Discord Server (opens new window) for help.

# Debugging yourself

The easiest way to debug yourself is via Patcher Settings. Here there are many different settings, however, the 3 main options that will help are:

  • "Enable Verbose Mode"
  • "Enable OpenCore DEBUG"
  • "Enable Kext DEBUG"

When you've enabled these 3 options, rebuild OpenCore and install to your drive. This will provide much greater debug information as well as write logs to the EFI Partition.

# Obtaining OpenCore logs from disk

With "Enable OpenCore DEBUG" set, on every boot there will be a .txt file generated on the EFI Partition. To grab these logs, download and run MountEFI (opens new window):

Once you've mounted the EFI Partition of the drive you have macOS on, you should see some nice logs:

# Obtaining Kernel logs from macOS

With "Enable Kext DEBUG" set, every boot will now have much more detailed logs stored in the OS. To get these logs, simply run the below command:

sudo dmesg > ~/Desktop/DMESG.txt
+     (opens new window)    
 
# How to debug with OpenCore
 
For those who've hit an odd bug and are unsure if it's user error or within the patcher, we recommend asking on the OpenCore Patcher Paradise Discord Server (opens new window) for help.
 
# Debugging yourself
 
The easiest way to debug yourself is via Patcher Settings. Here there are many different settings, however, the 3 main options that will help are:
 
  • "Enable Verbose Mode"
    •  
  • "Enable OpenCore DEBUG"
    •  
  • "Enable Kext DEBUG"
 
 
When you've enabled these 3 options, rebuild OpenCore and install to your drive. This will provide much greater debug information as well as write logs to the EFI Partition.
 
# Obtaining OpenCore logs from disk
 
With "Enable OpenCore DEBUG" set, on every boot there will be a .txt file generated on the EFI Partition. To grab these logs, download and run MountEFI (opens new window):
 
 
Once you've mounted the EFI Partition of the drive you have macOS on, you should see some nice logs:
 
 
# Obtaining Kernel logs from macOS
 
With "Enable Kext DEBUG" set, every boot will now have much more detailed logs stored in the OS. To get these logs, simply run the below command:
 
sudo dmesg > ~/Desktop/DMESG.txt
 
From there, you'll have a log on your desktop.
 
# Filing an issue with us
 
WARNING
 
Currently issues have been disabled due to current events. You can continue to receive support in the OpenCore Patcher Paradise Discord Server (opens new window), where there are active members of the community available.
 
Now that you have proper logs, you can now file issues with us (opens new window). This is a reminder to include the following info:
 
  • Model that you're patching for (ie. MacBookPro10,1)
    •  
  • Target OS (ie. macOS 11.2.3)
    •  
  • Host OS (ie. macOS 10.15.7)
    •  
  • Upload of your OpenCore Build Folder
    •  
  • Upload of your OpenCore log (if applicable)
    •  
  • Upload of your Kernel log (if applicable)
 
Additionally, please search to see if the issue has been reported before. This avoids having duplicate issues.
  

       ⟵
       
       ⟶
- + diff --git a/DONATE.html b/DONATE.html index 8551d14ac..f17cbfb6f 100644 --- a/DONATE.html +++ b/DONATE.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# Supporting the patcher

OpenCore Legacy Patcher is a hobby project for us developers, and while we love helping out the community, it's very difficult for us to troubleshoot issues remotely. The best way for us to get to work on the patcher, fix issues and add enhancements is having the hardware in-hand. As a hobby project, neither of the main developers can afford to buy every legacy Mac to test on.

The best way to support us in all honesty is to donate any old hardware you no longer need, as this allows us to have machines to test locally and push fixes much faster. While we appreciate cash donations, this makes it much more difficult for us to handle as an organization.

Main sections of help we'd appreciate:

- + diff --git a/HOW.html b/HOW.html index bf3d35ee0..67217e7b5 100644 --- a/HOW.html +++ b/HOW.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# Boot Process with OpenCore Legacy Patcher

OpenCore Legacy Patcher itself is actually quite a "dumb" program. It essentially edits a config.plist file and moves files around, actually having little logic regarding the boot process. The real magic of OCLP is OpenCorePkg (opens new window), our back-end, and what makes this patcher so powerful.

# Boot Process with OpenCore

To understand a bit more of how OpenCore is able to revive older Macs in such a native-like way, we need to go over how OpenCore works with your Mac:

+ (opens new window)

# Boot Process with OpenCore Legacy Patcher

OpenCore Legacy Patcher itself is actually quite a "dumb" program. It essentially edits a config.plist file and moves files around, actually having little logic regarding the boot process. The real magic of OCLP is OpenCorePkg (opens new window), our back-end, and what makes this patcher so powerful.

# Boot Process with OpenCore

To understand a bit more of how OpenCore is able to revive older Macs in such a native-like way, we need to go over how OpenCore works with your Mac:

⟵ ⟶

- + diff --git a/ICNS.html b/ICNS.html index 1bf64352d..9cd26c614 100644 --- a/ICNS.html +++ b/ICNS.html @@ -11,7 +11,7 @@ - + @@ -19,19 +19,19 @@ GitHub (opens new window)

# Creating custom icons for OpenCore and Mac Boot Picker

For users who want to customize their setup to be more personal, OpenCore does allow for custom icons and images in the boot picker.

# Custom OpenCore icons

To generate custom OpenCore icons, you'll need the following:

- + diff --git a/INSTALLER.html b/INSTALLER.html index f0ca90aac..4d7c676b5 100644 --- a/INSTALLER.html +++ b/INSTALLER.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# Download and build macOS Installers

This document is centered around downloading and writing the macOS installer to a USB drive. If you're already familiar with how to do this, you can skip this section.

  • Note: 16GB+ USB drive will be required for the installer

# Creating the installer

With OpenCore Legacy Patcher, our new GUI includes a download menu for macOS installers. So to start off, you'll want to grab our app:

For this guide, we'll be using the standard OpenCore-Patcher (GUI).

Once downloaded, open the app and you should be greeted by this menu:

OCLP GUI Main Menu

First, we'll want to select the "Create macOS Installer" button. This will present you with 2 options:

For this example, we'll assume you'll need an installer. Selecting this option will download Apple's Installer Catalogs and build a list for you to choose:

Downloading Listed Installers Unsupported Installer
OCLP GUI Installer Download Catalog OCLP GUI Installer Download Listed Products

Since the patcher officially supports Big Sur and newer for patching, only those entires will be shown. For ourselves, we'll select macOS 12 as that's the latest public release at the time of writing. This will download and install the macOS installer to your applications folder.

  • Note that some machines (namely 2012 and older) may not be currently supported on macOS Ventura. If you see this prompt, you'll need to use an older version of macOS.
Downloading the Installer Requesting to install Finished Installing
OCLP GUI Installer Download Progress OCLP GUI Installer Needs Installing OCLP GUI Installer Download Finished

Once finished, you can proceed to write the installer onto a USB drive.

  • Note: The entire USB drive will be formatted
Select Downloaded Installer Select disk to format

Now the patcher will start the installer flashing!

Flashing Success Prompt Finished Flashing

# Once finished, head to Building and installing OpenCore

+ (opens new window)

# Download and build macOS Installers

This document is centered around downloading and writing the macOS installer to a USB drive. If you're already familiar with how to do this, you can skip this section.

  • Note: 16GB+ USB drive will be required for the installer

# Creating the installer

With OpenCore Legacy Patcher, our new GUI includes a download menu for macOS installers. So to start off, you'll want to grab our app:

For this guide, we'll be using the standard OpenCore-Patcher (GUI).

Once downloaded, open the app and you should be greeted by this menu:

OCLP GUI Main Menu

First, we'll want to select the "Create macOS Installer" button. This will present you with 2 options:

For this example, we'll assume you'll need an installer. Selecting this option will download Apple's Installer Catalogs and build a list for you to choose:

Downloading Listed Installers Unsupported Installer
OCLP GUI Installer Download Catalog OCLP GUI Installer Download Listed Products

Since the patcher officially supports Big Sur and newer for patching, only those entires will be shown. For ourselves, we'll select macOS 12 as that's the latest public release at the time of writing. This will download and install the macOS installer to your applications folder.

  • Note that some machines (namely 2012 and older) may not be currently supported on macOS Ventura. If you see this prompt, you'll need to use an older version of macOS.
Downloading the Installer Requesting to install Finished Installing
OCLP GUI Installer Download Progress OCLP GUI Installer Needs Installing OCLP GUI Installer Download Finished

Once finished, you can proceed to write the installer onto a USB drive.

  • Note: The entire USB drive will be formatted
Select Downloaded Installer Select disk to format

Now the patcher will start the installer flashing!

Flashing Success Prompt Finished Flashing

# Once finished, head to Building and installing OpenCore

⟵ ⟶

- + diff --git a/ISSUES-HOLD.html b/ISSUES-HOLD.html index 0999f073e..c0e725abb 100644 --- a/ISSUES-HOLD.html +++ b/ISSUES-HOLD.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# The current hold on new issues and pull requests

As written with the release of OpenCore Legacy Patcher 0.4.3, and macOS 12.3:

With today's macOS 12.3 release, I decided it would be best to release this build of OpenCore Legacy Patcher to ensure some important issues are resolved with today's release (namely Open/Save dialog problem introduced by Apple in the 12.3 Betas)

As the situation develops back home with my family in Ukraine, I am unlikely to continue the development of OpenCore Legacy Patcher in the near future. At most, there may be potential PatcherSupportPkg updates from ASentientBot and the rest of the amazing non-Metal development team however otherwise development may potentially be taken over by others later on. Issues will continue to remain closed for the time being.

With regards to the future of this project, this release should be treated as its last major release for the next couple of months. When WWDC2022 is presented, I hope my country will be in a calmer situation where we can tinker with Macs again peacefully.

This is not a final goodbye for me with this project, just a round-about way to say I'll be returning someday. I want to give the biggest thank you's to the community and to the many amazing developers within it. OpenCore Legacy Patcher is not just my project, it's the cumulation of many people that are all responsible for where we are today.

-- Mykola

If you encounter new issues with the patcher that do not have solutions easily available, our helpful community in the OpenCore Patcher Paradise Discord Server (opens new window) can provide support in the meantime. You should still provide as much information as you can by gathering debug logs when you ask for help.

+ (opens new window)

# The current hold on new issues and pull requests

As written with the release of OpenCore Legacy Patcher 0.4.3, and macOS 12.3:

With today's macOS 12.3 release, I decided it would be best to release this build of OpenCore Legacy Patcher to ensure some important issues are resolved with today's release (namely Open/Save dialog problem introduced by Apple in the 12.3 Betas)

As the situation develops back home with my family in Ukraine, I am unlikely to continue the development of OpenCore Legacy Patcher in the near future. At most, there may be potential PatcherSupportPkg updates from ASentientBot and the rest of the amazing non-Metal development team however otherwise development may potentially be taken over by others later on. Issues will continue to remain closed for the time being.

With regards to the future of this project, this release should be treated as its last major release for the next couple of months. When WWDC2022 is presented, I hope my country will be in a calmer situation where we can tinker with Macs again peacefully.

This is not a final goodbye for me with this project, just a round-about way to say I'll be returning someday. I want to give the biggest thank you's to the community and to the many amazing developers within it. OpenCore Legacy Patcher is not just my project, it's the cumulation of many people that are all responsible for where we are today.

-- Mykola

If you encounter new issues with the patcher that do not have solutions easily available, our helpful community in the OpenCore Patcher Paradise Discord Server (opens new window) can provide support in the meantime. You should still provide as much information as you can by gathering debug logs when you ask for help.

⟵ ⟶

- + diff --git a/LICENSE.html b/LICENSE.html index 4c21783a1..3e2ea285f 100644 --- a/LICENSE.html +++ b/LICENSE.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# OpenCore Legacy Patcher License

This patcher is made of multiple external applications from different people and organizations. See each program for their licensing:

- + diff --git a/MODELS.html b/MODELS.html index 62884ec60..b79ec3d57 100644 --- a/MODELS.html +++ b/MODELS.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# Supported Models

Any Intel-based Mac listed below can install and make use of OpenCore Legacy Patcher. To check your hardware model, open System Information and look for the Model Identifier key.

  • This applies even if Apple supports the model natively.
  • OpenCore Legacy Patcher does not support PowerPC- or Apple Silicon-based Macs.
  • If your model is not listed below, it is not supported by this patcher.

The below tables can be used to reference issues with a particular model, and see which OS would work best on your machine.

OpenCore Patcher application

The patcher application requires OS X Yosemite 10.10 or later to run.

  • OS X El Capitan 10.11 or later is required to make installers for macOS Ventura and later.

The patcher is designed to target macOS Big Sur 11.x to macOS Sonoma 14.x.

  • Other versions may work, albeit in a broken state. No support is provided for any version outside of the above.

# MacBook

Model Name Identifier Tagged Issues
MacBook (13-inch, Aluminum, Late 2008) MacBook5,1 - non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
MacBook (13-inch, Early 2009)
MacBook (13-inch, Mid 2009)		 MacBook5,2 - non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
- Trackpad gestures are partially broken
MacBook (13-inch, Late 2009) MacBook6,1 - non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
MacBook (13-inch, Mid 2010) MacBook7,1
MacBook (Retina, 12-inch, Early 2015) MacBook8,1 - Legacy Metal (macOS 13+) (opens new window)
MacBook (Retina, 12-inch, Early 2016) MacBook9,1
MacBook (Retina, 12-inch, 2017) MacBook10,1 - Supported by OpenCore Legacy Patcher

# MacBook Air

Model Name Identifier Tagged Issues
MacBook Air (13-inch, Late 2008)
MacBook Air (13-inch, Mid 2009)		 MacBookAir2,1 - non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
MacBook Air (11-inch, Late 2010) MacBookAir3,1
MacBook Air (13-inch, Late 2010) MacBookAir3,2
MacBook Air (11-inch, Mid 2011) MacBookAir4,1
MacBook Air (13-inch, Mid 2011) MacBookAir4,2
MacBook Air (11-inch, Mid 2012) MacBookAir5,1 - Legacy Metal (macOS 13+) (opens new window)
MacBook Air (13-inch, Mid 2012) MacBookAir5,2
MacBook Air (11-inch, Mid 2013)
MacBook Air (11-inch, Early 2014)		 MacBookAir6,1
MacBook Air (13-inch, Mid 2013)
MacBook Air (13-inch, Early 2014)		 MacBookAir6,2
MacBook Air (11-inch, Early 2015) MacBookAir7,1
MacBook Air (13-inch, Early 2015)
MacBook Air (13-inch, 2017)		 MacBookAir7,2
MacBook Air (Retina, 13-inch, 2018) MacBookAir8,1 - Supported by Apple
MacBook Air (Retina, 13-inch, 2019) MacBookAir9,1
MacBook Air (Retina, 13-inch, 2020) MacBookAir10,1

# MacBook Pro

Model Name Identifier Tagged Issues
MacBook Pro (15-inch, Early 2008)
MacBook Pro (17-inch, Early 2008)		 MacBookPro4,1 - non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
MacBook Pro (15-inch, Late 2008) MacBookPro5,1
MacBook Pro (17-inch, Early 2009)
MacBook Pro (17-inch, Mid 2009)		 MacBookPro5,2
MacBook Pro (15-inch, Mid 2009) MacBookPro5,3
MacBook Pro (13-inch, Mid 2009) MacBookPro5,5
MacBook Pro (17-inch, Mid 2010) MacBookPro6,1 - non-Metal GPU (macOS 11+) (opens new window)
MacBook Pro (15-inch, Mid 2010) MacBookPro6,2
MacBook Pro (13-inch, Mid 2010) MacBookPro7,1 - non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
MacBook Pro (13-inch, Early 2011)
MacBook Pro (13-inch, Late 2011)		 MacBookPro8,1 - non-Metal GPU (macOS 11+) (opens new window)
MacBook Pro (15-inch, Early 2011)
MacBook Pro (15-inch, Late 2011)		 MacBookPro8,2
MacBook Pro (17-inch, Early 2011)
 MacBookPro8,3
MacBook Pro (15-inch, Mid 2012) MacBookPro9,1 - Legacy Metal (macOS 13+) (opens new window)
MacBook Pro (13-inch, Mid 2012) MacBookPro9,2
MacBook Pro (Retina, 15-inch, Mid 2012)
MacBook Pro (Retina, 15-inch, Early 2013)		 MacBookPro10,1
MacBook Pro (Retina, 13-inch, Late 2012)
MacBook Pro (Retina, 13-inch, Early 2013)		 MacBookPro10,2
MacBook Pro (Retina, 13-inch, Late 2013)
MacBook Pro (Retina, 13-inch, Mid 2014)		 MacBookPro11,1
MacBook Pro (Retina, 15-inch, Late 2013)
MacBook Pro (Retina, 15-inch, Mid 2014)		 MacBookPro11,2
MacBookPro11,3
MacBook Pro (Retina, 15-inch, Mid 2015) MacBookPro11,4
MacBookPro11,5
MacBook Pro (Retina, 13-inch, Early 2015) MacBookPro12,1
MacBook Pro (13-inch, 2016, 2 Thunderbolt 3 ports) MacBookPro13,1
MacBook Pro (13-inch, 2016, 4 Thunderbolt 3 ports) MacBookPro13,2
MacBook Pro (15-inch, 2016) MacBookPro13,3
MacBook Pro (13-inch, 2017, 2 Thunderbolt 3 ports) MacBookPro14,1 - Supported by OpenCore Legacy Patcher
MacBook Pro (13-inch, 2017, 4 Thunderbolt 3 ports) MacBookPro14,2
MacBook Pro (15-inch, 2017) MacBookPro14,3 - Legacy Metal (macOS 14+) (opens new window)
MacBook Pro (13-inch, 2018, 4 Thunderbolt 3 ports)
MacBook Pro (13-inch, 2019, 4 Thunderbolt 3 ports)		 MacBookPro15,2 - Supported by Apple
MacBook Pro (15-inch, 2018)
MacBook Pro (15-inch, 2019)		 MacBookPro15,1
MacBook Pro (13-inch, 2019, 2 Thunderbolt 3 ports) MacBookPro15,4
MacBook Pro (16-inch, 2019) MacBookPro16,1
MacBookPro16,4
MacBook Pro (13-inch, 2020, 4 Thunderbolt 3 ports) MacBookPro16,2
MacBook Pro (13-inch, 2020, 2 Thunderbolt 3 ports) MacBookPro16,3

# Mac mini

Model Name Identifier Tagged Issues
Mac mini (Early 2009) Macmini3,1 - non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
Mac mini (Mid 2010) Macmini4,1 - non-Metal GPU (macOS 11+) (opens new window)
Mac mini (Mid 2011) Macmini5,1
Macmini5,2
Macmini5,3
Mac mini (Late 2012) Macmini6,1
Macmini6,2		 - Legacy Metal (macOS 13+) (opens new window)
Mac mini (Late 2014) Macmini7,1
Mac mini (Late 2018) Macmini8,1 - Supported by Apple

# iMac

Model Name Identifier Tagged Issues
iMac (20-inch, Mid 2007)
iMac (24-inch, Mid 2007)		 iMac7,1 - Requires SSE4.1 CPU (opens new window)
- non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
- Remove stock Bluetooth to prevent panics
iMac (20-inch, Early 2008)
iMac (24-inch, Early 2008)		 iMac8,1 - non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
iMac (20-inch, Early 2009)
iMac (24-inch, Early 2009)
iMac (20-inch, Mid 2009)		 iMac9,1 - non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
- Recommend upgrading to Metal GPU (opens new window)
iMac (21.5-inch, Late 2009)
iMac (27-inch, Late 2009)		 iMac10,1
iMac (27-inch, Late 2009) iMac11,1
iMac (21.5-inch, Mid 2010) iMac11,2
iMac (27-inch, Mid 2010) iMac11,3
iMac (21.5-inch, Mid 2011)
iMac (21.5-inch, Late 2011)		 iMac12,1
iMac (27-inch, Mid 2011) iMac12,2
iMac (21.5-inch, Late 2012) iMac13,1 - Legacy Metal (macOS 13+) (opens new window)
iMac (27-inch, Late 2012) iMac13,2
iMac (21.5-inch, Early 2013) iMac13,3
iMac (21.5-inch, Late 2013) iMac14,1
iMac (27-inch, Late 2013) iMac14,2
iMac14,3
iMac (21.5-inch, Mid 2014) iMac14,4
iMac (Retina 5K, 27-inch, Late 2014)
iMac (Retina 5K, 27-inch, Mid 2015)		 iMac15,1
iMac (21.5-inch, Late 2015) iMac16,1
iMac (Retina 4K, 21.5-inch, Late 2015) iMac16,2
iMac (Retina 5K, 27-inch, Late 2015) iMac17,1
iMac (21.5-inch, 2017) iMac18,1 - Supported by OpenCore Legacy Patcher
iMac (Retina 4K, 21.5-inch, 2017) iMac18,2
iMac (Retina 5K, 27-inch, 2017) iMac18,3
iMac (Retina 5K, 27-inch, 2019) iMac19,1 - Supported by Apple
iMac (Retina 4K, 21.5-inch, 2019) iMac19,2
iMac (Retina 5K, 27-inch, 2020) iMac20,1
iMac20,2
iMac Pro (2017) iMacPro1,1

# Mac Pro

Model Name Identifier Tagged Issues
Mac Pro (Early 2008) MacPro3,1 - Recommend upgrade to Metal GPU (opens new window)
- non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
- Remove stock Bluetooth to prevent panics
Mac Pro (Early 2009) MacPro4,1 - Recommend upgrade to Metal GPU (opens new window)
- non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
Mac Pro (Mid 2010)
Mac Pro (Mid 2012)		 MacPro5,1
Mac Pro (Late 2013) MacPro6,1 - Legacy Metal (macOS 13+) (opens new window)
Mac Pro (2019) MacPro7,1 - Supported by Apple

# Xserve

Model Name Identifier Tagged Issues
Xserve (Early 2008) Xserve2,1 - Recommend upgrade to Metal GPU
- non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
Xserve (Early 2009) Xserve3,1

# Once you've verified your hardware is supported, head to Download and build macOS Installers

+ (opens new window)

# Supported Models

Any Intel-based Mac listed below can install and make use of OpenCore Legacy Patcher. To check your hardware model, open System Information and look for the Model Identifier key.

  • This applies even if Apple supports the model natively.
  • OpenCore Legacy Patcher does not support PowerPC- or Apple Silicon-based Macs.
  • If your model is not listed below, it is not supported by this patcher.

The below tables can be used to reference issues with a particular model, and see which OS would work best on your machine.

OpenCore Patcher application

The patcher application requires OS X Yosemite 10.10 or later to run.

  • OS X El Capitan 10.11 or later is required to make installers for macOS Ventura and later.

The patcher is designed to target macOS Big Sur 11.x to macOS Sonoma 14.x.

  • Other versions may work, albeit in a broken state. No support is provided for any version outside of the above.

# MacBook

Model Name Identifier Tagged Issues
MacBook (13-inch, Aluminum, Late 2008) MacBook5,1 - non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
MacBook (13-inch, Early 2009)
MacBook (13-inch, Mid 2009)		 MacBook5,2 - non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
- Trackpad gestures are partially broken
MacBook (13-inch, Late 2009) MacBook6,1 - non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
MacBook (13-inch, Mid 2010) MacBook7,1
MacBook (Retina, 12-inch, Early 2015) MacBook8,1 - Legacy Metal (macOS 13+) (opens new window)
MacBook (Retina, 12-inch, Early 2016) MacBook9,1
MacBook (Retina, 12-inch, 2017) MacBook10,1 - Supported by OpenCore Legacy Patcher

# MacBook Air

Model Name Identifier Tagged Issues
MacBook Air (13-inch, Late 2008)
MacBook Air (13-inch, Mid 2009)		 MacBookAir2,1 - non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
MacBook Air (11-inch, Late 2010) MacBookAir3,1
MacBook Air (13-inch, Late 2010) MacBookAir3,2
MacBook Air (11-inch, Mid 2011) MacBookAir4,1
MacBook Air (13-inch, Mid 2011) MacBookAir4,2
MacBook Air (11-inch, Mid 2012) MacBookAir5,1 - Legacy Metal (macOS 13+) (opens new window)
MacBook Air (13-inch, Mid 2012) MacBookAir5,2
MacBook Air (11-inch, Mid 2013)
MacBook Air (11-inch, Early 2014)		 MacBookAir6,1
MacBook Air (13-inch, Mid 2013)
MacBook Air (13-inch, Early 2014)		 MacBookAir6,2
MacBook Air (11-inch, Early 2015) MacBookAir7,1
MacBook Air (13-inch, Early 2015)
MacBook Air (13-inch, 2017)		 MacBookAir7,2
MacBook Air (Retina, 13-inch, 2018) MacBookAir8,1 - Supported by Apple
MacBook Air (Retina, 13-inch, 2019) MacBookAir9,1
MacBook Air (Retina, 13-inch, 2020) MacBookAir10,1

# MacBook Pro

Model Name Identifier Tagged Issues
MacBook Pro (15-inch, Early 2008)
MacBook Pro (17-inch, Early 2008)		 MacBookPro4,1 - non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
MacBook Pro (15-inch, Late 2008) MacBookPro5,1
MacBook Pro (17-inch, Early 2009)
MacBook Pro (17-inch, Mid 2009)		 MacBookPro5,2
MacBook Pro (15-inch, Mid 2009) MacBookPro5,3
MacBook Pro (13-inch, Mid 2009) MacBookPro5,5
MacBook Pro (17-inch, Mid 2010) MacBookPro6,1 - non-Metal GPU (macOS 11+) (opens new window)
MacBook Pro (15-inch, Mid 2010) MacBookPro6,2
MacBook Pro (13-inch, Mid 2010) MacBookPro7,1 - non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
MacBook Pro (13-inch, Early 2011)
MacBook Pro (13-inch, Late 2011)		 MacBookPro8,1 - non-Metal GPU (macOS 11+) (opens new window)
MacBook Pro (15-inch, Early 2011)
MacBook Pro (15-inch, Late 2011)		 MacBookPro8,2
MacBook Pro (17-inch, Early 2011)
 MacBookPro8,3
MacBook Pro (15-inch, Mid 2012) MacBookPro9,1 - Legacy Metal (macOS 13+) (opens new window)
MacBook Pro (13-inch, Mid 2012) MacBookPro9,2
MacBook Pro (Retina, 15-inch, Mid 2012)
MacBook Pro (Retina, 15-inch, Early 2013)		 MacBookPro10,1
MacBook Pro (Retina, 13-inch, Late 2012)
MacBook Pro (Retina, 13-inch, Early 2013)		 MacBookPro10,2
MacBook Pro (Retina, 13-inch, Late 2013)
MacBook Pro (Retina, 13-inch, Mid 2014)		 MacBookPro11,1
MacBook Pro (Retina, 15-inch, Late 2013)
MacBook Pro (Retina, 15-inch, Mid 2014)		 MacBookPro11,2
MacBookPro11,3
MacBook Pro (Retina, 15-inch, Mid 2015) MacBookPro11,4
MacBookPro11,5
MacBook Pro (Retina, 13-inch, Early 2015) MacBookPro12,1
MacBook Pro (13-inch, 2016, 2 Thunderbolt 3 ports) MacBookPro13,1
MacBook Pro (13-inch, 2016, 4 Thunderbolt 3 ports) MacBookPro13,2
MacBook Pro (15-inch, 2016) MacBookPro13,3
MacBook Pro (13-inch, 2017, 2 Thunderbolt 3 ports) MacBookPro14,1 - Supported by OpenCore Legacy Patcher
MacBook Pro (13-inch, 2017, 4 Thunderbolt 3 ports) MacBookPro14,2
MacBook Pro (15-inch, 2017) MacBookPro14,3 - Legacy Metal (macOS 14+) (opens new window)
MacBook Pro (13-inch, 2018, 4 Thunderbolt 3 ports)
MacBook Pro (13-inch, 2019, 4 Thunderbolt 3 ports)		 MacBookPro15,2 - Supported by Apple
MacBook Pro (15-inch, 2018)
MacBook Pro (15-inch, 2019)		 MacBookPro15,1
MacBook Pro (13-inch, 2019, 2 Thunderbolt 3 ports) MacBookPro15,4
MacBook Pro (16-inch, 2019) MacBookPro16,1
MacBookPro16,4
MacBook Pro (13-inch, 2020, 4 Thunderbolt 3 ports) MacBookPro16,2
MacBook Pro (13-inch, 2020, 2 Thunderbolt 3 ports) MacBookPro16,3

# Mac mini

Model Name Identifier Tagged Issues
Mac mini (Early 2009) Macmini3,1 - non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
Mac mini (Mid 2010) Macmini4,1 - non-Metal GPU (macOS 11+) (opens new window)
Mac mini (Mid 2011) Macmini5,1
Macmini5,2
Macmini5,3
Mac mini (Late 2012) Macmini6,1
Macmini6,2		 - Legacy Metal (macOS 13+) (opens new window)
Mac mini (Late 2014) Macmini7,1
Mac mini (Late 2018) Macmini8,1 - Supported by Apple

# iMac

Model Name Identifier Tagged Issues
iMac (20-inch, Mid 2007)
iMac (24-inch, Mid 2007)		 iMac7,1 - Requires SSE4.1 CPU (opens new window)
- non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
- Remove stock Bluetooth to prevent panics
iMac (20-inch, Early 2008)
iMac (24-inch, Early 2008)		 iMac8,1 - non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
iMac (20-inch, Early 2009)
iMac (24-inch, Early 2009)
iMac (20-inch, Mid 2009)		 iMac9,1 - non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
- Recommend upgrading to Metal GPU (opens new window)
iMac (21.5-inch, Late 2009)
iMac (27-inch, Late 2009)		 iMac10,1
iMac (27-inch, Late 2009) iMac11,1
iMac (21.5-inch, Mid 2010) iMac11,2
iMac (27-inch, Mid 2010) iMac11,3
iMac (21.5-inch, Mid 2011)
iMac (21.5-inch, Late 2011)		 iMac12,1
iMac (27-inch, Mid 2011) iMac12,2
iMac (21.5-inch, Late 2012) iMac13,1 - Legacy Metal (macOS 13+) (opens new window)
iMac (27-inch, Late 2012) iMac13,2
iMac (21.5-inch, Early 2013) iMac13,3
iMac (21.5-inch, Late 2013) iMac14,1
iMac (27-inch, Late 2013) iMac14,2
iMac14,3
iMac (21.5-inch, Mid 2014) iMac14,4
iMac (Retina 5K, 27-inch, Late 2014)
iMac (Retina 5K, 27-inch, Mid 2015)		 iMac15,1
iMac (21.5-inch, Late 2015) iMac16,1
iMac (Retina 4K, 21.5-inch, Late 2015) iMac16,2
iMac (Retina 5K, 27-inch, Late 2015) iMac17,1
iMac (21.5-inch, 2017) iMac18,1 - Supported by OpenCore Legacy Patcher
iMac (Retina 4K, 21.5-inch, 2017) iMac18,2
iMac (Retina 5K, 27-inch, 2017) iMac18,3
iMac (Retina 5K, 27-inch, 2019) iMac19,1 - Supported by Apple
iMac (Retina 4K, 21.5-inch, 2019) iMac19,2
iMac (Retina 5K, 27-inch, 2020) iMac20,1
iMac20,2
iMac Pro (2017) iMacPro1,1

# Mac Pro

Model Name Identifier Tagged Issues
Mac Pro (Early 2008) MacPro3,1 - Recommend upgrade to Metal GPU (opens new window)
- non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
- Remove stock Bluetooth to prevent panics
Mac Pro (Early 2009) MacPro4,1 - Recommend upgrade to Metal GPU (opens new window)
- non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
Mac Pro (Mid 2010)
Mac Pro (Mid 2012)		 MacPro5,1
Mac Pro (Late 2013) MacPro6,1 - Legacy Metal (macOS 13+) (opens new window)
Mac Pro (2019) MacPro7,1 - Supported by Apple

# Xserve

Model Name Identifier Tagged Issues
Xserve (Early 2008) Xserve2,1 - Recommend upgrade to Metal GPU
- non-Metal GPU (macOS 11+) (opens new window)
- USB 1.1 (macOS 13+) (opens new window)
Xserve (Early 2009) Xserve3,1

# Once you've verified your hardware is supported, head to Download and build macOS Installers

⟵ ⟶

- + diff --git a/MONTEREY-DROP.html b/MONTEREY-DROP.html index 8288a817e..f1fa39012 100644 --- a/MONTEREY-DROP.html +++ b/MONTEREY-DROP.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

With OpenCore Legacy Patcher v0.1.7 and newer, we've implemented beta macOS Monterey support for users. Please note that Apple has dropped a lot of hardware with this release as well as broken many of our previous patch sets. This page will be used to inform users regarding current issues and will be updated as new patch sets are developed and added to our patcher.

# Newly dropped hardware

With Monterey, Apple continues their their somewhat ruthless march of dropping Intel hardware. This release saw the removal, and thus addition into OpenCore Legacy Patcher, of the following models:

  • iMac14,4
  • iMac15,1
  • MacBook8,1
  • MacBookAir6,1
  • MacBookAir6,2
  • MacBookPro11,1
  • MacBookPro11,2
  • MacBookPro11,3
Model names
  • iMac (21.5-inch, Mid 2014)
  • iMac (Retina 5K, 27-inch, Late 2014)
  • MacBook (Retina, 12-inch, Early 2015)
  • MacBook Air (11-inch, Mid 2013)
  • MacBook Air (13-inch, Mid 2013)
  • MacBook Air (11-inch, Early 2014)
  • MacBook Air (13-inch, Early 2014)
  • MacBook Pro (Retina, 13-inch, Late 2013)
  • MacBook Pro (Retina, 15-inch, Late 2013)
  • MacBook Pro (Retina, 13-inch, Mid 2014)
  • MacBook Pro (Retina, 15-inch, Mid 2014)

All of these models now have support in OpenCore Legacy Patcher.

# Current Monterey Issues

# MacBookPro11,3 booting issue without Kepler acceleration

Due to the display being routed through the NVIDIA Kepler card and macOS being rendered on the Intel iGPU, users have been experiencing issues booting without post-install patches applied (see here for more info (opens new window).) Currently the only workaround is to install the patches in safe mode, by holding down Shift+Enter when you select macOS in the OCLP boot picker.

# Previously Broken Hardware

iMac15,1 5K Display Output Issue (Resolved in 0.3.2 and newer)
- + diff --git a/PATCHEXPLAIN.html b/PATCHEXPLAIN.html index d104dd801..c5ae29a4c 100644 --- a/PATCHEXPLAIN.html +++ b/PATCHEXPLAIN.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# Explaining the patches in OpenCore Legacy Patcher

In our patcher, there are numerous patches used to ensure a stable system. Here, we're going to go over what patches are used and why we recommend or even require them.

# OpenCore Settings

Below is a rundown of the main logic that OpenCore Legacy Patcher uses to gain native support in macOS. Note that OpenCore's configuration is documented within OpenCorePkg (opens new window) as well as on an online version provided by us:

Configuration Explanation

# ACPI -> Add

- + diff --git a/POST-INSTALL.html b/POST-INSTALL.html index 13ea1e203..3a1647644 100644 --- a/POST-INSTALL.html +++ b/POST-INSTALL.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# Post-Installation

# Booting without USB drive

Once you've installed macOS through OpenCore, you can boot up and go through the regular install process. To boot without the USB drive plugged in is quite simple:

  • Download OpenCore Legacy Patcher
  • Change Patcher settings as you'd like
  • Build OpenCore again
  • Install OpenCore to internal drive
  • Reboot holding Option, and select the internal EFI

And voila! No more USB drive required.

# Booting seamlessly without Boot Picker

To do this, run the OpenCore Patcher and head to Patcher Settings, then uncheck "Show OpenCore Bootpicker" on the Build tab:

Once you've toggled it off, build your OpenCore EFI once again and install to your desired drive. Now to show the OpenCore selector, you can simply hold down the "ESC" key while clicking on EFI boot, and then you can release the "ESC" key when you see the cursor arrow at the top left.

# Enabling SIP

For many users, SIP will be lowered by default on build. For Intel HD 4000 users, you may have noticed that SIP is partially disabled. This is to ensure full compatibility with macOS Monterey and allow seamless booting between it and older OSes. However for users who do not plan to boot Monterey, you can re-enable under Patcher Settings.

Note: Machines running macOS Ventura or systems with non-Metal GPUs cannot enable SIP outright, due to having a patched root volume. Enabling it will brick the installation.

Going forward with 0.6.6, SIP settings can be accessed from the Security tab shown in the images.

SIP Enabled SIP Lowered (Root Patching) SIP Disabled

WARNING

If you're unsure whether you should enable SIP, leave it as-is. Systems where you have already ran the Post Install Root Patching cannot enable SIP without potentially breaking the current install.

# Applying Post Install Volume Patches

WARNING

If you need to use Migration Assistant to bring over data to your new macOS install, it is highly recommended to avoid restoring from inside Setup Assistant and waiting to install root patches until after the transfer is complete. If root patches were automatically installed, you can use the options available in the OCLP app to remove them.

Using Migration Assistant while patches are installed can lead to an unbootable system, requiring a reinstall of macOS.

Post Install Volume Patches, sometimes also called root patches, are patches that have to be installed to disk for some older Macs to gain back functionality.

OCLP will automatically root patch your system during a first time install if the USB install media was created within OCLP. Users will also be prompted to install these patches after macOS updates or whenever patches are not detected on the system. We recommend rebuilding OpenCore with the latest version of OCLP to take advantage of these new features.

Users can also see whether applicable patches have been installed, date and version the system was root patched with in the Post-Install Menu.

Automatic install prompt Status

# Running Post Install patches manually

If you're using OCLP v0.4.3 or earlier, or need to run the patcher manually, you can do so with the app. There is no harm in trying to run the Patcher, as without compatible hardware, nothing will be done. You can see below on whether your hardware needs root volume patching or not.

There is also an option to remove root patches, which may be required in some situations, such as switching GPUs in Mac Pros or using Migration Assistant.

Listing Patches Patching Finished

WARNING

With macOS Ventura and Macs with AMD Legacy GCN GPUs (ie. Metal), Root Patching requires a network connection to grab Apple's Kernel Debug Kit to start root patching. If your system is unable to connect to the internet, you can manually download a KDK from Apple's site:

Grab the Kernel Debug Kit whose version is closest to the OS you installed, and install it to the machine running Ventura.

Machines that require this are those with AMD Metal dGPUs:

  • 2008 - 2013 Mac Pros (MacPro3,1 - 6,1)
  • 2009 - 2016 iMacs (iMac10,1 - 17,1)
  • 2015 15" MacBook Pro with a dGPU (MacBookPro11,5)

Below entries represent GPUs no longer natively supported, ie. requiring root volume patching with OpenCore Legacy Patcher:

GPUs requiring patching in macOS Big Sur
  • NVIDIA: + (opens new window)

    # Post-Installation

    # Booting without USB drive

    Once you've installed macOS through OpenCore, you can boot up and go through the regular install process. To boot without the USB drive plugged in is quite simple:

    • Download OpenCore Legacy Patcher
    • Change Patcher settings as you'd like
    • Build OpenCore again
    • Install OpenCore to internal drive
    • Reboot holding Option, and select the internal EFI

    And voila! No more USB drive required.

    # Booting seamlessly without Boot Picker

    To do this, run the OpenCore Patcher and head to Patcher Settings, then uncheck "Show OpenCore Bootpicker" on the Build tab:

    Once you've toggled it off, build your OpenCore EFI once again and install to your desired drive. Now to show the OpenCore selector, you can simply hold down the "ESC" key while clicking on EFI boot, and then you can release the "ESC" key when you see the cursor arrow at the top left.

    # Enabling SIP

    For many users, SIP will be lowered by default on build. For Intel HD 4000 users, you may have noticed that SIP is partially disabled. This is to ensure full compatibility with macOS Monterey and allow seamless booting between it and older OSes. However for users who do not plan to boot Monterey, you can re-enable under Patcher Settings.

    Note: Machines running macOS Ventura or systems with non-Metal GPUs cannot enable SIP outright, due to having a patched root volume. Enabling it will brick the installation.

    Going forward with 0.6.6, SIP settings can be accessed from the Security tab shown in the images.

    SIP Enabled SIP Lowered (Root Patching) SIP Disabled

    WARNING

    If you're unsure whether you should enable SIP, leave it as-is. Systems where you have already ran the Post Install Root Patching cannot enable SIP without potentially breaking the current install.

    # Applying Post Install Volume Patches

    WARNING

    If you need to use Migration Assistant to bring over data to your new macOS install, it is highly recommended to avoid restoring from inside Setup Assistant and waiting to install root patches until after the transfer is complete. If root patches were automatically installed, you can use the options available in the OCLP app to remove them.

    Using Migration Assistant while patches are installed can lead to an unbootable system, requiring a reinstall of macOS.

    Post Install Volume Patches, sometimes also called root patches, are patches that have to be installed to disk for some older Macs to gain back functionality.

    OCLP will automatically root patch your system during a first time install if the USB install media was created within OCLP. Users will also be prompted to install these patches after macOS updates or whenever patches are not detected on the system. We recommend rebuilding OpenCore with the latest version of OCLP to take advantage of these new features.

    Users can also see whether applicable patches have been installed, date and version the system was root patched with in the Post-Install Menu.

    Automatic install prompt Status

    # Running Post Install patches manually

    If you're using OCLP v0.4.3 or earlier, or need to run the patcher manually, you can do so with the app. There is no harm in trying to run the Patcher, as without compatible hardware, nothing will be done. You can see below on whether your hardware needs root volume patching or not.

    There is also an option to remove root patches, which may be required in some situations, such as switching GPUs in Mac Pros or using Migration Assistant.

    Listing Patches Patching Finished

    WARNING

    With macOS Ventura and Macs with AMD Legacy GCN GPUs (ie. Metal), Root Patching requires a network connection to grab Apple's Kernel Debug Kit to start root patching. If your system is unable to connect to the internet, you can manually download a KDK from Apple's site:

    Grab the Kernel Debug Kit whose version is closest to the OS you installed, and install it to the machine running Ventura.

    Machines that require this are those with AMD Metal dGPUs:

    • 2008 - 2013 Mac Pros (MacPro3,1 - 6,1)
    • 2009 - 2016 iMacs (iMac10,1 - 17,1)
    • 2015 15" MacBook Pro with a dGPU (MacBookPro11,5)

    Below entries represent GPUs no longer natively supported, ie. requiring root volume patching with OpenCore Legacy Patcher:

    GPUs requiring patching in macOS Big Sur
    • NVIDIA:
      • Tesla (8000 - 300 series)
    • AMD:
      • TeraScale (2000 - 6000 series)
    • Intel:
      • Iron Lake
      • Sandy Bridge (2000 - 3000 series)
    GPUs requiring patching in macOS Monterey
    • NVIDIA: @@ -38,6 +38,6 @@ ⟶

- + diff --git a/SONOMA-DROP.html b/SONOMA-DROP.html index f287ef595..55189e048 100644 --- a/SONOMA-DROP.html +++ b/SONOMA-DROP.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

Well here we are again, it's always such a pleasure~

Apple has yet again dropped a bunch of models, continuing their journey on discontinuing Intel Macs. With the release of OpenCore Legacy Patcher 1.0.0, early support for macOS Sonoma has been implemented.

# Versioning

With 1.0.0, we'll be switching to a proper major, minor and bug fix system (Semantic Versioning (opens new window)). This means the coming release will be version 1.0.0, and future releases plan to follow this scheme:

  • First digit: Major changes, including new OS support, API changes, and significant patch set changes, etc
  • Second digit: Minor changes, including incoming OS update fixes, minor patch set changes, etc
  • Third digit: Bug fixes, primarily hot fixes either due to a regression in prior release or resolving issues in already released OS updates

# Newly dropped hardware

  • MacBook10,1: MacBook (Retina, 12-inch, 2017)
  • MacBookPro14,1: MacBook Pro (13-inch, 2017, Two Thunderbolt 3 ports)
  • MacBookPro14,2: MacBook Pro (13-inch, 2017, Four Thunderbolt 3 Ports)
  • MacBookPro14,3: MacBook Pro (15-inch, 2017)
  • iMac18,1: iMac (21.5-inch, 2017)
  • iMac18,2: iMac (Retina 4K, 21.5-inch, 2017)
  • iMac18,3: iMac (Retina 5K, 27-inch, 2017)

# Current status

OpenCore Legacy Patcher 1.0.0 will support Sonoma for all models normally supported by the Patcher, however some challenges remain. You can find information about them below.

# Issues

# Bluetooth

Sometimes Bluetooth may not work after boot on pre-2012 models. Running NVRAM reset can alleviate it.

Dual boots may also bring the issue back even after the reset.

# T1 Security chip

Support for the T1 Security chip (Resolved in 1.1.0 and newer)

Sonoma has removed support for T1 chips found in most 2016 and 2017 Macs. Therefore on these systems, the following will not function:

  • Enable or disable FileVault
  • Open the Password Settings window
  • Add fingerprints (if upgrading, existing fingerprints will be deleted)
  • Add cards to Apple Pay

More information here (opens new window)

WARNING

Note that erasing the entire drive will remove the T1 firmware and it won't be reinstalled.

# USB 1.1 (OHCI/UHCI) Support

For Penryn systems, pre-2013 Mac Pros and Xserve, USB 1.1 support was outright removed in macOS Ventura and naturally this continues in Sonoma. + (opens new window)

Well here we are again, it's always such a pleasure~

Apple has yet again dropped a bunch of models, continuing their journey on discontinuing Intel Macs. With the release of OpenCore Legacy Patcher 1.0.0, early support for macOS Sonoma has been implemented.

# Versioning

With 1.0.0, we'll be switching to a proper major, minor and bug fix system (Semantic Versioning (opens new window)). This means the coming release will be version 1.0.0, and future releases plan to follow this scheme:

  • First digit: Major changes, including new OS support, API changes, and significant patch set changes, etc
  • Second digit: Minor changes, including incoming OS update fixes, minor patch set changes, etc
  • Third digit: Bug fixes, primarily hot fixes either due to a regression in prior release or resolving issues in already released OS updates

# Newly dropped hardware

  • MacBook10,1: MacBook (Retina, 12-inch, 2017)
  • MacBookPro14,1: MacBook Pro (13-inch, 2017, Two Thunderbolt 3 ports)
  • MacBookPro14,2: MacBook Pro (13-inch, 2017, Four Thunderbolt 3 Ports)
  • MacBookPro14,3: MacBook Pro (15-inch, 2017)
  • iMac18,1: iMac (21.5-inch, 2017)
  • iMac18,2: iMac (Retina 4K, 21.5-inch, 2017)
  • iMac18,3: iMac (Retina 5K, 27-inch, 2017)

# Current status

OpenCore Legacy Patcher 1.0.0 will support Sonoma for all models normally supported by the Patcher, however some challenges remain. You can find information about them below.

# Issues

# Bluetooth

Sometimes Bluetooth may not work after boot on pre-2012 models. Running NVRAM reset can alleviate it.

Dual boots may also bring the issue back even after the reset.

# T1 Security chip

Support for the T1 Security chip (Resolved in 1.1.0 and newer)

Sonoma has removed support for T1 chips found in most 2016 and 2017 Macs. Therefore on these systems, the following will not function:

  • Enable or disable FileVault
  • Open the Password Settings window
  • Add fingerprints (if upgrading, existing fingerprints will be deleted)
  • Add cards to Apple Pay

More information here (opens new window)

WARNING

Note that erasing the entire drive will remove the T1 firmware and it won't be reinstalled.

# USB 1.1 (OHCI/UHCI) Support

For Penryn systems, pre-2013 Mac Pros and Xserve, USB 1.1 support was outright removed in macOS Ventura and naturally this continues in Sonoma. While USB 1.1 may seem unimportant, it handles many important devices on your system. These include:

  • Keyboard and Trackpad for laptops
  • IR Receivers
  • Bluetooth

With OpenCore Legacy Patcher v0.6.0+, basic support has been implemented via Root Volume patching. However due to this, users will need to use a USB hub for installation and post-OS updates when patches are cleaned:

The following systems rely on USB 1.1

  • iMac10,x and older
  • Macmini3,1 and older
  • MacBook7,1 and older
  • MacBookAir3,1 and older
  • MacPro5,1 and older
  • Xserve 3,1 and older

More information here (opens new window)

# Graphics support and issues

This build includes both Legacy Metal and non-Metal patches for macOS Sonoma. Refer to the following links for more information about Legacy Metal and non-Metal support and their respective issues.

⟵ ⟶

- + diff --git a/START.html b/START.html index 35cd27dea..7fedf7454 100644 --- a/START.html +++ b/START.html @@ -11,7 +11,7 @@ - + @@ -19,11 +19,11 @@ GitHub (opens new window)

# What is OpenCore?

OpenCore is a sophisticated boot loader used to inject and patch data in memory, instead of on disk. This means that we're able to achieve a near-native experience on many unsupported Macs.

# How do I get started?

  1. The first step of ensuring whether your model is supported is by checking the Supported Models page.

  2. Download and build macOS Installer

  3. Run the OpenCore-Patcher.app

  4. Reboot and boot OpenCore

+ (opens new window)

# What is OpenCore?

OpenCore is a sophisticated boot loader used to inject and patch data in memory, instead of on disk. This means that we're able to achieve a near-native experience on many unsupported Macs.

# How do I get started?

  1. The first step of ensuring whether your model is supported is by checking the Supported Models page.

  2. Download and build macOS Installer

  3. Run the OpenCore-Patcher.app

  4. Reboot and boot OpenCore

Supported Models ⟶

- + diff --git a/TERMS.html b/TERMS.html index 75d92b4d2..80f7bf289 100644 --- a/TERMS.html +++ b/TERMS.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# OpenCore Patcher Terminology

With OpenCore Legacy Patcher, we use a lot of different terms to refer to hardware including SSE4.1, 32-Bit Firmware, etc. This page is to help users understand what all these confusing words mean.

# Terminology

Term Description
macOS Apple's own UNIX based OS used for Mac machines and is "What makes a Mac a Mac".
Windows Microsoft's proprietary OS that is used and supported on a wide range of devices
Linux Family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991, by Linus Torvalds. Linux is typically packaged in a Linux distribution. Note that while macOS and Linux may be UNIX-based, they're vastly different.
Bootloader Piece of software that loads an OS, usually made by the OS creators. OpenCore is technically not a bootloader per se (see boot manager explanation down below). Apple's Boot.efi would be the actual boot loader in a Mac.
Boot Manager Piece of software that manages bootloaders – we have many of these: Clover, systemd-boot, OpenCore, rEFInd, rEFIt... These are generally seen as prepping the system for the actual boot loader.
Term Description
OpenCore The new hotness on the scene, made with security in mind by the Acidanthera team (opens new window), has faster booting and lighter weight than previous boot managers. Supports many native Mac features such as SIP, FileVault, Secure Boot, etc
ACPI Tables defined in your firmware defining your hardware and different methods, tied directly to how IOKit/IOService handles device setup
NVRAM Non-volatile storage, where many variables are stored including default boot options, Hibernation keys, Secure Boot information, etc
Term Description
XNU Also known as X is Not Unix, XNU is referred to as macOS's "kernel" and the heart of what makes macOS tick
Kexts Also known as Kernel Extensions, are macOS's drivers. They're used to perform different tasks like device drivers or for a different purpose (in this patcher) like patching the OS, injecting information or running tasks.
KernelCollection Also known as the ImmutableKernel and PrelinkedKernel, this is a bundle of the kernel(XNU) and kernel extensions(Kexts) that we use to boot macOS. This is also what OpenCore patches in memory to allow us to have a seamless experience
- PrelinkedKernel: Default caching system since 10.7
- ImmutableKernel: Secure Boot based caching system since 10.13
- KernelCollection: Merge of both Prelinked and ImmutableKernel's since macOS 11, Big Sur
IOKit Backbone of how Kernel Extensions (Kexts) probe and attach onto hardware, starts quickly after kernel initiates
WindowServer Backbone of the GUI interface in macOS, one of the first userfacing userspace programs to kick-in
OTA Short for Over The Air, refers to native OS updates via System Preferences like a supported Mac
DELTA Often used with OTA, refers to OS updates that much smaller than full installers (generally ~3GB), note Deltas require the root volume to be unmodified otherwise ~12GB updates will occur.
Term Description
EFI It can denote two things:
- Mac's firmware, which is the same as UEFI, but pretty modified for Macs only, so not so "Universal"
- The partition on your hard drive that stores software read by the UEFI to load OSes (like the Windows bootloader) or UEFI Applications (like OpenCore), it's FAT32 formatted and has an ID type of EF00 (in hex). It can be named ESP or SYSTEM, and it's usually from 100MB to 400MB in size but the size doesn't reflect upon anything.
HFS+ Also known as Mac OS Extended (Journaled), this was the default macOS drive format up until macOS 10.13. It was designed around spinning disks.
APFS This is the default macOS drive format from macOS 10.13 and onwards for SSDs, and standard for all drives in Mojave. This format was designed primarily around SSDs.
32 and 64-Bit CPU The bit number of a CPU determines how much data a CPU can address.
- 32-Bit CPUs were only supported up-to Mac OS X 10.6, Snow Leopard.
32-Bit Firmware The bit number of a Firmware determines how much data the firmware can address. In some older Macs, it's common to have a 64-Bit CPU with a 32-Bit firmware
- 32-Bit Firmwares were only supported up-to Mac OS X 10.7, Lion.
SSE Instructions Also known as SIMD Single-Precision Floating-Point Instructions, these are defined as instruction sets supported by your CPU. In macOS, there are a certain number of instruction sets required for normal operation:
- SSE3: Required for all Intel CPUs since Mac OS X 10.4, Tiger
- SSSE3: Required for all Intel 64-Bit CPUs since Mac OS X 10.6, Snow Leopard
- SSE4.1: Required for all Intel CPUs since macOS 10.12, Sierra

+ (opens new window)

# OpenCore Patcher Terminology

With OpenCore Legacy Patcher, we use a lot of different terms to refer to hardware including SSE4.1, 32-Bit Firmware, etc. This page is to help users understand what all these confusing words mean.

# Terminology

Term Description
macOS Apple's own UNIX based OS used for Mac machines and is "What makes a Mac a Mac".
Windows Microsoft's proprietary OS that is used and supported on a wide range of devices
Linux Family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991, by Linus Torvalds. Linux is typically packaged in a Linux distribution. Note that while macOS and Linux may be UNIX-based, they're vastly different.
Bootloader Piece of software that loads an OS, usually made by the OS creators. OpenCore is technically not a bootloader per se (see boot manager explanation down below). Apple's Boot.efi would be the actual boot loader in a Mac.
Boot Manager Piece of software that manages bootloaders – we have many of these: Clover, systemd-boot, OpenCore, rEFInd, rEFIt... These are generally seen as prepping the system for the actual boot loader.
Term Description
OpenCore The new hotness on the scene, made with security in mind by the Acidanthera team (opens new window), has faster booting and lighter weight than previous boot managers. Supports many native Mac features such as SIP, FileVault, Secure Boot, etc
ACPI Tables defined in your firmware defining your hardware and different methods, tied directly to how IOKit/IOService handles device setup
NVRAM Non-volatile storage, where many variables are stored including default boot options, Hibernation keys, Secure Boot information, etc
Term Description
XNU Also known as X is Not Unix, XNU is referred to as macOS's "kernel" and the heart of what makes macOS tick
Kexts Also known as Kernel Extensions, are macOS's drivers. They're used to perform different tasks like device drivers or for a different purpose (in this patcher) like patching the OS, injecting information or running tasks.
KernelCollection Also known as the ImmutableKernel and PrelinkedKernel, this is a bundle of the kernel(XNU) and kernel extensions(Kexts) that we use to boot macOS. This is also what OpenCore patches in memory to allow us to have a seamless experience
- PrelinkedKernel: Default caching system since 10.7
- ImmutableKernel: Secure Boot based caching system since 10.13
- KernelCollection: Merge of both Prelinked and ImmutableKernel's since macOS 11, Big Sur
IOKit Backbone of how Kernel Extensions (Kexts) probe and attach onto hardware, starts quickly after kernel initiates
WindowServer Backbone of the GUI interface in macOS, one of the first userfacing userspace programs to kick-in
OTA Short for Over The Air, refers to native OS updates via System Preferences like a supported Mac
DELTA Often used with OTA, refers to OS updates that much smaller than full installers (generally ~3GB), note Deltas require the root volume to be unmodified otherwise ~12GB updates will occur.
Term Description
EFI It can denote two things:
- Mac's firmware, which is the same as UEFI, but pretty modified for Macs only, so not so "Universal"
- The partition on your hard drive that stores software read by the UEFI to load OSes (like the Windows bootloader) or UEFI Applications (like OpenCore), it's FAT32 formatted and has an ID type of EF00 (in hex). It can be named ESP or SYSTEM, and it's usually from 100MB to 400MB in size but the size doesn't reflect upon anything.
HFS+ Also known as Mac OS Extended (Journaled), this was the default macOS drive format up until macOS 10.13. It was designed around spinning disks.
APFS This is the default macOS drive format from macOS 10.13 and onwards for SSDs, and standard for all drives in Mojave. This format was designed primarily around SSDs.
32 and 64-Bit CPU The bit number of a CPU determines how much data a CPU can address.
- 32-Bit CPUs were only supported up-to Mac OS X 10.6, Snow Leopard.
32-Bit Firmware The bit number of a Firmware determines how much data the firmware can address. In some older Macs, it's common to have a 64-Bit CPU with a 32-Bit firmware
- 32-Bit Firmwares were only supported up-to Mac OS X 10.7, Lion.
SSE Instructions Also known as SIMD Single-Precision Floating-Point Instructions, these are defined as instruction sets supported by your CPU. In macOS, there are a certain number of instruction sets required for normal operation:
- SSE3: Required for all Intel CPUs since Mac OS X 10.4, Tiger
- SSSE3: Required for all Intel 64-Bit CPUs since Mac OS X 10.6, Snow Leopard
- SSE4.1: Required for all Intel CPUs since macOS 10.12, Sierra

⟵ ⟶

- + diff --git a/TROUBLESHOOTING.html b/TROUBLESHOOTING.html index 3864b7c0f..ee07dac1b 100644 --- a/TROUBLESHOOTING.html +++ b/TROUBLESHOOTING.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# Troubleshooting

Here are some common errors that users may experience while using this patcher:

# OpenCore Legacy Patcher not launching

If the application won't launch (e.g. icon will bounce in the Dock), try launching OCLP via Terminal by typing the following command, make sure you've moved the app to /Applications before this.

/Applications/OpenCore-Patcher.app/Contents/MacOS/OpenCore-Patcher
+     (opens new window)    
 
# Troubleshooting
 
Here are some common errors that users may experience while using this patcher:
  
# OpenCore Legacy Patcher not launching
 
If the application won't launch (e.g. icon will bounce in the Dock), try launching OCLP via Terminal by typing the following command, make sure you've moved the app to /Applications before this.
 
/Applications/OpenCore-Patcher.app/Contents/MacOS/OpenCore-Patcher
 
# Stuck on This version of Mac OS X is not supported on this platform or (🚫) Prohibited Symbol
 
This means macOS has detected an SMBIOS it does not support. To resolve this, ensure you're booting OpenCore before the macOS installer in the boot picker. Reminder that the option will be called EFI Boot.
 
Once you've booted OpenCore at least once, your hardware should now auto-boot it until either an NVRAM reset occurs, or you remove the drive with OpenCore installed.
 
However, if the 🚫 Symbol only appears after the boot process has already started (the bootscreen appears/verbose boot starts), it could mean that your USB drive has failed to pass macOS' integrity checks. To resolve this, create a new installer using a different USB drive (preferably of a different model.)
 
# Cannot boot macOS without the USB
 
By default, the OpenCore Patcher won't install OpenCore onto the internal drive itself during installs.
 
After installing macOS, OpenCore Legacy Patcher should automatically prompt you to install OpenCore onto the internal drive. However, if it doesn't show the prompt, you'll need to either manually transfer (opens new window) OpenCore to the internal drive's EFI or Build and Install again and select your internal drive.
 
Reminder that once this is done, you'll need to select OpenCore in the boot picker again for your hardware to remember this entry and auto boot from then on.
 
# Infinite Recovery OS Booting
 
With OpenCore Legacy Patcher, we rely on Apple Secure Boot to ensure OS updates work correctly and reliably with Big Sur. However this installs NVRAM variables that will confuse your Mac if not running with OpenCore. To resolve this, simply uninstall OpenCore and reset NVRAM (opens new window).
 
  • Note: Machines with modified root volumes will also result in an infinite recovery loop until integrity is restored.
 
# Stuck on boot after root patching
 
Boot into recovery by pressing space when your disk is selected on the OCLP bootpicker (if you have it hidden, hold ESC while starting up)
 
  • Note: If your disk name is something else than "Macintosh HD", make sure to change the path accordingly. You can figure out your disk name by typing ls /Volumes.
 
Go into terminal and first mount the disk by typing
 
mount -uw "/Volumes/Macintosh HD"
 
Then revert the snapshot
 
bless --mount "/Volumes/Macintosh HD" --bootefi --last-sealed-snapshot
 
After that, type the following
 
cd "/Volumes/Macintosh HD/Library/Extensions" && ls
@@ -34,6 +34,6 @@
       
       ⟶
- + diff --git a/UNINSTALL.html b/UNINSTALL.html index 03f9850ce..3d376a30e 100644 --- a/UNINSTALL.html +++ b/UNINSTALL.html @@ -3,7 +3,7 @@ - Uninstalling OpenCore | OpenCore Legacy Patcher + Uninstalling OpenCore bootloader | OpenCore Legacy Patcher @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ GitHub (opens new window)

# Uninstalling OpenCore

To remove OpenCore:

  1. Remove OpenCore either from the USB or internal drive
  • You'll need to mount the drive's EFI partition, and delete the EFI/OC and System folders -
  1. Reset NVRAM (opens new window)

WARNING

Note that after you remove OpenCore, your Mac will no longer boot and show the "prohibited" symbol. Be ready to install an natively-supported version of macOS before you uninstall OpenCore.

  • This does not apply to native Macs just using OpenCore to achieve features like AirPlay to Mac and Sidecar, but it is still recomended to reinstall macOS, after removing OpenCore, if using SMBIOS spoofing to enable Univeral Control.

+ (opens new window)

# Uninstalling OpenCore bootloader

  1. Remove OpenCore either from the USB or internal drive
  • You'll need to mount the drive's EFI partition, and delete the EFI/OC and System folders +
  1. Reset NVRAM (opens new window)

WARNING

Note that after you remove OpenCore, your Mac will no longer boot and show the "prohibited" symbol. Be ready to install an natively-supported version of macOS before you uninstall OpenCore.

  • This does not apply to native Macs just using OpenCore to achieve features like AirPlay to Mac and Sidecar, but it is still recommended to reinstall macOS after removing OpenCore, if using SMBIOS spoofing to enable Univeral Control.

If you used OCLP on a native system and want to remove the application without reinstalling the OS, navigate to /Library/Application Support/ and delete the Dortania folder.

⟵ ⟶

- + diff --git a/UNIVERSALCONTROL.html b/UNIVERSALCONTROL.html index d0717987d..b972ddda2 100644 --- a/UNIVERSALCONTROL.html +++ b/UNIVERSALCONTROL.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# Universal Control on unsupported Macs

Introduced in macOS 12 Monterey, Universal Control is a feature that allows a Mac to control other Macs and/or iPads, share input devices, and share files across them simultaneously. With OpenCore and FeatureUnlock, Universal Control can be unlocked for most unsupported Macs, as long as they meet the technical requirements listed on this page.

  • Note: The following page is primarily for tinkerers, no proper support is provided outside of Discord support (see bottom of page).

# Enabling Universal Control

If you meet all the requirements, in most cases you can go to Display Preferences and tick the Universal Control settings to enable it. If you're planning to use Universal Control with an iPad, make sure to enable Universal Control on the iPad as well.

Display Preferences Universal Control settings
OCLP GUI Build Finished

Most Mac models from 2011 and above should work out of the box. However, older Macs like the 2008-2011 MacBook Pros require upgrading the Wi-Fi/Bluetooth card to a newer model. More info in the requirements section.

Some Monterey-native models are blacklisted, check the blacklisted models section for more info.

# Requirements for Universal Control

Technical requirements:

  • Wi-Fi 4 (802.11n)
  • Bluetooth 4.0
  • macOS Monterey 12.4 or newer
  • iPadOS 15.4 or newer (if applicable)
  • OpenCore Legacy Patcher 0.4.3 or newer

Check the table of models below to see whether you need to upgrade hardware and exactly what hardware is required to be changed based on the offending Macs listed. For help on how to upgrade the Wi-Fi card in older 2008-2011 models, refer to the #hardware channel in the Discord server (opens new window) if required.

Other requirements:

  • All devices are signed into the same iCloud account.
  • Two Factor Authentication is enabled with your Apple ID.
  • Bluetooth and WiFi are enabled. Neither needs to be connected, leaving them enabled is sufficient.
  • Handoff turned on from iCloud settings.
  • The devices in question are in close proximity.

# Table of models

This table shows which models do and do not support Universal Control out of box (OOB) and what is required to gain support. + (opens new window)

# Universal Control on unsupported Macs

Introduced in macOS 12 Monterey, Universal Control is a feature that allows a Mac to control other Macs and/or iPads, share input devices, and share files across them simultaneously. With OpenCore and FeatureUnlock, Universal Control can be unlocked for most unsupported Macs, as long as they meet the technical requirements listed on this page.

  • Note: The following page is primarily for tinkerers, no proper support is provided outside of Discord support (see bottom of page).

# Enabling Universal Control

If you meet all the requirements, in most cases you can go to Display Preferences and tick the Universal Control settings to enable it. If you're planning to use Universal Control with an iPad, make sure to enable Universal Control on the iPad as well.

Display Preferences Universal Control settings
OCLP GUI Build Finished

Most Mac models from 2011 and above should work out of the box. However, older Macs like the 2008-2011 MacBook Pros require upgrading the Wi-Fi/Bluetooth card to a newer model. More info in the requirements section.

Some Monterey-native models are blacklisted, check the blacklisted models section for more info.

# Requirements for Universal Control

Technical requirements:

  • Wi-Fi 4 (802.11n)
  • Bluetooth 4.0
  • macOS Monterey 12.4 or newer
  • iPadOS 15.4 or newer (if applicable)
  • OpenCore Legacy Patcher 0.4.3 or newer

Check the table of models below to see whether you need to upgrade hardware and exactly what hardware is required to be changed based on the offending Macs listed. For help on how to upgrade the Wi-Fi card in older 2008-2011 models, refer to the #hardware channel in the Discord server (opens new window) if required.

Other requirements:

  • All devices are signed into the same iCloud account.
  • Two Factor Authentication is enabled with your Apple ID.
  • Bluetooth and WiFi are enabled. Neither needs to be connected, leaving them enabled is sufficient.
  • Handoff turned on from iCloud settings.
  • The devices in question are in close proximity.

# Table of models

This table shows which models do and do not support Universal Control out of box (OOB) and what is required to gain support. Note: For AirPort upgrades, only the best/newest cards are listed.

MacBook
SMBIOS WiFi/BT version UC OOB Comment
MacBook5,1 Wi-Fi 4 / BT 2.0 EDR NO Use a Broadcom USB Bluetooth 4.0+ Dongle
MacBook5,2 WiFi 4 / BT 2.1 EDR Replace stock AirPort card with an mPCIE + USB Connector Adapter board with a BCM94360CS2 card
MacBook6,1 Replace stock AirPort card with a BCM94331PCIEBT4CAX/BCM94331PCIEBT4 card
MacBook7,1
MacBook8,1 WiFi 4 + BT 4.2 YES Universal Control will work.
MacBook Air
SMBIOS WiFi/BT version UC OOB Comment
MacBookAir2,1 Wi-Fi 4 / BT 2.1 EDR NO Use a Broadcom USB Bluetooth 4.0+ Dongle
MacBookAir3,1 Replace stock AirPort card with a BCM94360CS2 card
MacBookAir3,2
MacBookAir4,1 Wi-Fi 4 + BT 4.0 YES Universal Control will work.
MacBookAir4,2
MacBookAir5,1
MacBookAir5,2
MacBookAir6,1 Wi-Fi 5 + BT 4.0
MacBookAir6,2
MacBookAir7,1 NO Hardware supports UC.
Spoofing required.
MacBookAir7,2
MacBook Pro
SMBIOS WiFi/BT version UC OOB Comment
MacBookPro4,1 Wi-Fi 4 / BT 2.1 EDR NO Replace stock AirPort card with an mPCIE + USB Connector Adapter board with a BCM94360CS2 card
MacBookPro5,1 Use a Broadcom USB Bluetooth 4.0+ Dongle
MacBookPro5,2
MacBookPro5,3
MacBookPro5,4
MacBookPro5,5
MacBookPro6,1
MacBookPro6,2 Replace stock AirPort card with a BCM94331PCIEBT4CAX/BCM94331PCIEBT4 card
MacBookPro7,1 Use a Broadcom USB Bluetooth 4.0+ Dongle
MacBookPro8,1 Wi-Fi 4 + BT 2.1 EDR Replace stock AirPort card with a BCM94331PCIEBT4CAX/BCM94331PCIEBT4 card
MacBookPro8,2
MacBookPro9,1 Wi-Fi 4 + BT 4.0 YES Universal Control will work.
MacBookPro9,2
MacBookPro10,1
MacBookPro10,2
MacBookPro11,1 Wi-Fi 5 + BT 4.0
MacBookPro11,2
MacBookPro11,3
MacBookPro11,4 Wi-Fi 5 + BT 4.2 NO Hardware supports UC.
Spoofing required.
MacBookPro11,5
MacBookPro12,1
Mac mini
SMBIOS WiFi/BT version UC OOB Comment
Macmini3,1 Wi-Fi 4 + BT 2.1 EDR NO Upgrade requires some heavy electrical and case modifications, so instead used a Broadcom USB Bluetooth 4.0+ Dongle.
Macmini4,1
Macmini5,1 Wi-Fi 4 + BT 4.0 YES Universal Control will work.
Macmini5,2
Macmini5,3
Macmini6,1
Macmini6,2
Macmini7,1 Wi-Fi 5 + BT 4.0 NO Hardware supports UC.
Spoofing required.
iMac
SMBIOS WiFi/BT version UC OOB Comment
iMac7,1 Wi-Fi 4 + BT 2.0 EDR NO Replace stock AirPort card with an mPCIE + USB Connector Adapter board with a BCM94360CD card
iMac8,1
iMac9,1 Wi-Fi 4 / BT 2.1 EDR
iMac10,1
iMac11,1
iMac11,2
iMac11,3
iMac12,1 Replace stock AirPort card with an mPCIE + USB Connector Adapter board with a BCM943602CD card
iMac12,2
iMac13,1 Wi-Fi 4 + BT 4.0 YES Universal Control will work.
iMac13,2
iMac13,3
iMac14,1 Wi-Fi 5 + BT 4.0
iMac14,2
iMac14,3
iMac14,4
iMac15,1
iMac16,1 Wi-Fi 5 + BT 4.2 NO Hardware supports UC.
Spoofing required.
iMac16,2
Mac Pro
SMBIOS WiFi/BT version UC OOB Comment
MacPro3,1 Wi-Fi 4 + BT 2.0 EDR NO Replace stock AirPort card with an mPCIE Adapter board with a BCM943602CD card
MacPro4,1 Wi-Fi 4 + BT 2.1 EDR Replace stock AirPort card with an mPCIE + USB Connector Adapter board with a BCM943602CD card
MacPro5,1
MacPro6,1 Wi-Fi 5 + BT 4.0 Hardware supports UC.
Spoofing required.
  • Note: Some older Mac Pro configurations may not have shipped with a WiFi card in the base model
Xserve ;p
SMBIOS WiFi/BT version UC OOB Comment
Xserve2,1 N/A NO Install a PCIe BCM943602CD card
Xserve3,1

# Blacklisted models

The following models are blacklisted from using Universal Control by Apple:

  • MacBookAir7,x - MacBook Air Early 2015 11" / 13"
  • MacBookPro11,4 - MacBook Pro Mid 2015 15" (Intel Iris)
  • MacBookPro11,5 - MacBook Pro Mid 2015 15" (dGPU)
  • MacBookPro12,x - MacBook Pro Early 2015 13"
  • iMac16,x - iMac Late 2015 21"
  • Macmini7,x - Mac mini 2014
  • MacPro6,x - Mac Pro Late 2013

The hardware in these models are capable of supporting Universal Control, but due to blacklisting, the only solution to use Universal Control on these models is to spoof their SMBIOS. SMBIOS spoofing essentially fools some aspects of macOS to think they are running on a different machine.

With SMBIOS Spoofing, the Universal Control handshake recognizes a different SMBIOS and thus grants a blacklisted Mac to connect to other Macs and iPads with Universal Control.

Situation Condition Solution
Mac <-> Mac connection Monterey-unsupported No spoofing needed
Mac <-> iPad connection Monterey-unsupported No spoofing needed
Mac <-> Mac connection One or both are blacklisted Spoofing required on blacklisted Macs
Mac <-> iPad connection Blacklisted Mac Spoofing required on blacklisted Mac

WARNING

Before we continue, please keep in mind that SMBIOS Spoofing is an advanced feature of OpenCore. Reckless usage of it could potentially break important functionality and leave your installation in a non-working state. Once you boot into a spoofed state, it is highly recommended that you stay spoofed, and avoid booting macOS without OpenCore.

# How to spoof

Ventura has dropped more models which includes all of the blacklisted Macs in question, making the procedure slightly different. It is important to follow the guide for the version you're on, failing to do so is likely to cause boot issues.

macOS Sonoma

Firstly run OpenCore Legacy Patcher.

Then go to Settings and SMBIOS tab, set SMBIOS Spoof Level to Moderate. Set SMBIOS Spoof Model one listed next to your native model in the table for spoofed models below.

Notice that "Allow native models" and "Allow Native Spoofs" are NOT enabled unlike on Monterey, this is on purpose. They are no longer relevant on Sonoma and enabling them will cause boot issues.

Main Settings view SMBIOS settings
Table for spoofed models (click to expand)

Spoofing to any model with native Sonoma support should work, but these are the earliest Macs natively supported by Sonoma and thus chosen for the sake of simplicity.

Reminder: Macs that are not listed on this table work without spoofing, including systems that do not natively support Ventura as long as the other requirements are met, since they aren't blacklisted.

Mac by name Native SMBIOS Spoof SMBIOS
MacBook Air Early 2015 11" / 13" MacBookAir7,x MacBookAir8,1
MacBook Pro Early 2015 13" MacBookPro12,x MacBookPro15,2
MacBook Pro Mid 2015 15" MacBookPro11,4 / 11,5 MacBookPro15,2
iMac Late 2015 21" iMac16,x iMac19,2
Mac mini Late 2014 Macmini7,x MacMini8,1
Mac Pro Late 2013 MacPro6,x MacPro7,1
macOS Ventura

Firstly run OpenCore Legacy Patcher.

Then go to Settings and SMBIOS tab, set SMBIOS Spoof Level to Moderate. Set SMBIOS Spoof Model one listed next to your native model in the table for spoofed models below.

Notice that "Allow native models" and "Allow Native Spoofs" are NOT enabled unlike on Monterey, this is on purpose. They are no longer relevant on Ventura and enabling them will cause boot issues.

Main Settings view SMBIOS settings
Table for spoofed models (click to expand)

Spoofing to any model with native Ventura support should work, but these are the earliest Macs natively supported by Ventura and thus chosen for the sake of simplicity.

Reminder: Macs that are not listed on this table work without spoofing, including systems that do not natively support Ventura as long as the other requirements are met, since they aren't blacklisted.

Mac by name Native SMBIOS Spoof SMBIOS
MacBook Air Early 2015 11" / 13" MacBookAir7,x MacBookAir8,1
MacBook Pro Early 2015 13" MacBookPro12,x MacBookPro14,1
MacBook Pro Mid 2015 15" MacBookPro11,4 / 11,5 MacBookPro14,3
iMac Late 2015 21" iMac16,x iMac18,2
Mac mini Late 2014 Macmini7,x MacMini8,1
Mac Pro Late 2013 MacPro6,x MacPro7,1
macOS Monterey

Firstly, run OpenCore Legacy Patcher. Secondly, go to Settings then the App tab and tick Allow native models.

Then, go to SMBIOS tab, tick Allow spoofing native Macs, set SMBIOS Spoof Level to Moderate. Set SMBIOS Spoof Model to one listed next to your native model in the table for spoofed models below.

Main Settings view SMBIOS settings
Table for spoofed models (click to expand)

Any model after the list of officially blacklisted Macs should be supported, but these are the earliest Macs with Universal Control support, and thus chosen for the sake of simplicity.

Reminder: Macs that are not listed on this table work without spoofing, including systems that do not natively support Monterey, as long as the other requirements are met, since they aren't blacklisted.

Mac by name Native SMBIOS Spoof SMBIOS
MacBook Air Early 2015 11" / 13" MacBookAir7,x MacBookAir8,1
MacBook Pro Early 2015 13" MacBookPro12,x MacBookPro13,1
MacBook Pro Mid 2015 15" MacBookPro11,4 / 11,5 MacBookPro13,3
iMac Late 2015 21" iMac16,x iMac18,2
Mac mini Late 2014 Macmini7,x MacMini8,1
Mac Pro Late 2013 MacPro6,x MacPro7,1

Note: Unless you are building OpenCore on a different machine than it's targeted for, do not change the model in the main settings view. It is important to understand that OCLP targets this model regardless of what you may have spoofed to, as your Mac is still what the Native SMBIOS shows.

Lastly, Build and install OpenCore again, and reboot back to the OS. Enable Universal Control as explained in the Enabling Universal Control section.

You should now be prompted to log back into iCloud by your Mac. If you get this prompt, you have successfully configured SMBIOS spoofing. Otherwise, verify that you have correctly followed the steps listed above, or ask on the Discord server for further assistance in #misc-help (opens new window).

⟵

# Updating OpenCore and Patches

With OpenCore Legacy Patcher, there's generally very little reason for users to update the OpenCore installation on their machine unless you feel there's a benefit with new versions for your setup, e.g. Bluetooth has stopped working with a new macOS update.

For those who do wish to update, simply download the latest release (opens new window) and rerun the patcher:

Then, rebuild your OpenCore build and install again. OpenCore Will now be updated!

To check what version of OpenCore and the Patcher you're currently running, you can run the following in the terminal:

# OpenCore Version
+     (opens new window)    
 
# Updating OpenCore and Patches
 
With OpenCore Legacy Patcher, there's generally very little reason for users to update the OpenCore installation on their machine unless you feel there's a benefit with new versions for your setup, e.g. Bluetooth has stopped working with a new macOS update.
 
For those who do wish to update, simply download the latest release (opens new window) and rerun the patcher:
 
 
Then, rebuild your OpenCore build and install again. OpenCore Will now be updated!
 
To check what version of OpenCore and the Patcher you're currently running, you can run the following in the terminal:
 
# OpenCore Version
 nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version
 # Patcher Version
 nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:OCLP-Version
@@ -28,10 +28,10 @@ nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:OCLP-Version
        
-        Uninstalling OpenCore
+        Uninstalling OpenCore bootloader
       
       ⟶
- + diff --git a/VENTURA-DROP.html b/VENTURA-DROP.html index 8980cf0a4..fb2635bc2 100644 --- a/VENTURA-DROP.html +++ b/VENTURA-DROP.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

With the release of OpenCore Legacy Patcher v0.5.0 and newer, early support for macOS Ventura has been implemented for most Metal-capable Macs. This page will be used to inform users regarding current issues and will be updated as new patch sets are developed and added to our patcher.

# Newly dropped hardware

Ventura's release dropped a large amount of Intel hardware, thus requiring the usage of OpenCore Legacy Patcher on the following models (in addition to previously removed models):

  • iMac16,1 (21.5-inch, Late 2015)
  • iMac16,2 (21.5-inch and 21.5-inch 4K, Late 2015)
  • iMac17,1 (27-inch 5K, Late 2015)
  • MacBook9,1 (12-inch, Early 2016)
  • MacBookAir7,1 (11-inch, Early 2015)
  • MacBookAir7,2 (13-inch, Early 2015)
  • MacBookPro11,4 (15-inch, Mid 2015, iGPU)
  • MacBookPro11,5 (15-inch, Mid 2015, dGPU)
  • MacBookPro12,1 (13-inch, Early 2015)
  • MacBookPro13,1 (13-inch, Late 2016)
  • MacBookPro13,2 (13-inch, Late 2016)
  • MacBookPro13,3 (15-inch, Late 2016)
  • Macmini7,1 (Late 2014)
  • MacPro6,1 (Late 2013)

# Current status

For older hardware, see below sections:

The team is doing their best to investigate and fix the aforementioned issues, however no estimated time can be provided.

# Currently Unsupported/Broken Hardware in Ventura

# AMD Polaris, Vega and Navi support on pre-2019 Mac Pros and pre-2012 iMacs

For users with 2008 to 2013 Mac Pros (MacPro3,1-6,1) and 2009 to 2011 iMacs (iMac9,1-12,2), keep in mind that macOS Ventura now requires AVX2.0 support in the CPU (opens new window) for native graphics acceleration. Thus while your GPU may be natively supported, you cannot run Ventura officially with these GPUs.

  • CPUs supporting AVX2.0 are Haswell or newer, which no pre-2019 Mac Pros can be upgraded with.

Currently at this time, OpenCore Legacy Patcher only supports patching the AMD Polaris and Vega Graphics stack to no longer require AVX2.0. We're recently received an AMD RX 6600 donation, so hopefully in the future the project can support AMD Navi with pre-Haswell Macs. However, no time estimates can be given.

Following GPUs are applicable:

GPU Architecture Model Families Supported
AMD Polaris RX 4xx/5xx (10/20 series) Supported with patching
AMD Vega Vega 56/64/VII (10/20 series)
AMD Navi RX 5xxx/6xxx (10/20 series) Unsupported

# USB 1.1 (OHCI/UHCI) Support

For Penryn systems and pre-2013 Mac Pros, USB 1.1 support was outright removed in macOS Ventura. While USB 1.1 may seem unimportant, it handles many important devices on your system. These include:

  • Keyboard and Trackpad for laptops
  • IR Receivers
  • Bluetooth

With OpenCore Legacy Patcher v0.6.0, basic support has been implemented via Root Volume patching. However due to this, users will need to use a USB hub for installation and post-OS updates when patches are cleaned:

The following systems rely on USB 1.1

  • iMac10,x and older
  • Macmini3,1 and older
  • MacBook7,1 and older
  • MacBookAir3,1 and older
  • MacBookPro7,1 and older + (opens new window)

    With the release of OpenCore Legacy Patcher v0.5.0 and newer, early support for macOS Ventura has been implemented for most Metal-capable Macs. This page will be used to inform users regarding current issues and will be updated as new patch sets are developed and added to our patcher.

    # Newly dropped hardware

    Ventura's release dropped a large amount of Intel hardware, thus requiring the usage of OpenCore Legacy Patcher on the following models (in addition to previously removed models):

    • iMac16,1 (21.5-inch, Late 2015)
    • iMac16,2 (21.5-inch and 21.5-inch 4K, Late 2015)
    • iMac17,1 (27-inch 5K, Late 2015)
    • MacBook9,1 (12-inch, Early 2016)
    • MacBookAir7,1 (11-inch, Early 2015)
    • MacBookAir7,2 (13-inch, Early 2015)
    • MacBookPro11,4 (15-inch, Mid 2015, iGPU)
    • MacBookPro11,5 (15-inch, Mid 2015, dGPU)
    • MacBookPro12,1 (13-inch, Early 2015)
    • MacBookPro13,1 (13-inch, Late 2016)
    • MacBookPro13,2 (13-inch, Late 2016)
    • MacBookPro13,3 (15-inch, Late 2016)
    • Macmini7,1 (Late 2014)
    • MacPro6,1 (Late 2013)

    # Current status

    For older hardware, see below sections:

    The team is doing their best to investigate and fix the aforementioned issues, however no estimated time can be provided.

    # Currently Unsupported/Broken Hardware in Ventura

    # AMD Polaris, Vega and Navi support on pre-2019 Mac Pros and pre-2012 iMacs

    For users with 2008 to 2013 Mac Pros (MacPro3,1-6,1) and 2009 to 2011 iMacs (iMac9,1-12,2), keep in mind that macOS Ventura now requires AVX2.0 support in the CPU (opens new window) for native graphics acceleration. Thus while your GPU may be natively supported, you cannot run Ventura officially with these GPUs.

    • CPUs supporting AVX2.0 are Haswell or newer, which no pre-2019 Mac Pros can be upgraded with.

    Currently at this time, OpenCore Legacy Patcher only supports patching the AMD Polaris and Vega Graphics stack to no longer require AVX2.0. We're recently received an AMD RX 6600 donation, so hopefully in the future the project can support AMD Navi with pre-Haswell Macs. However, no time estimates can be given.

    Following GPUs are applicable:

    GPU Architecture Model Families Supported
    AMD Polaris RX 4xx/5xx (10/20 series) Supported with patching
    AMD Vega Vega 56/64/VII (10/20 series)
    AMD Navi RX 5xxx/6xxx (10/20 series) Unsupported

    # USB 1.1 (OHCI/UHCI) Support

    For Penryn systems and pre-2013 Mac Pros, USB 1.1 support was outright removed in macOS Ventura. While USB 1.1 may seem unimportant, it handles many important devices on your system. These include:

    • Keyboard and Trackpad for laptops
    • IR Receivers
    • Bluetooth

    With OpenCore Legacy Patcher v0.6.0, basic support has been implemented via Root Volume patching. However due to this, users will need to use a USB hub for installation and post-OS updates when patches are cleaned:

    The following systems rely on USB 1.1

    • iMac10,x and older
    • Macmini3,1 and older
    • MacBook7,1 and older
    • MacBookAir3,1 and older
    • MacBookPro7,1 and older
      • MacBookPro6,x is exempt
    • MacPro5,1 and older
    Legacy Wireless Support (Resolved in v0.6.0 and newer)

    # Legacy Wireless Support

    For systems that required Root Patches in macOS Monterey to achieve Wireless support, unfortunately macOS Ventura has broken the patch set. Currently the following Wifi cards are unsupported:

    • Atheros: All models
    • Broadcom: BCM94328 and BCM94322

    The following machines shipped stock with these cards:

    • iMac12,x and older
    • Macmini3,1 and older
    • MacBook5,x and older
    • MacBookAir2,1 and older
    • MacBookPro7,1 and older
      • MacBookPro6,x is exempt
    • MacPro5,1 and older

    Currently BCM943224, BCM94331, BCM94360 and BCM943602 are still fully supported by OpenCore Legacy Patcher. Consider upgrading to these cards if possible.

    Non-Metal Graphics Acceleration (Resolved in v0.6.0 and newer)

    # Non-Metal Graphics Acceleration

    Regarding non-Metal, the team is hard at work to get non-Metal working, however this is our greatest challenge since Big Sur.

    Apple has made significant changes to the graphics stack in order to facilitate fancy effects, and in particularly, Stage Manager. We will update you as we work on development, however, now is not the best time to ask about ETAs.

    The following GPUs are applicable:

    • NVIDIA:
      • Tesla (8000 - 300 series)
    • AMD: @@ -33,6 +33,6 @@ ⟶

- + diff --git a/WINDOWS.html b/WINDOWS.html index 6b76b1cc9..ab18eaf15 100644 --- a/WINDOWS.html +++ b/WINDOWS.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# Installing Windows in UEFI Mode

Modern versions of Windows officially support two types of firmware: UEFI and BIOS. Users may want to boot Windows through the OCLP Bootpicker, but only UEFI Installations of Windows will show up in the OCLP Bootpicker. + (opens new window)

# Installing Windows in UEFI Mode

Modern versions of Windows officially support two types of firmware: UEFI and BIOS. Users may want to boot Windows through the OCLP Bootpicker, but only UEFI Installations of Windows will show up in the OCLP Bootpicker. Many older Macs do not "officially" support UEFI Windows installations, leading to installation failures and strange behaviour, but OCLP can be used to prevent almost all of these issues.

# Minimum Requirements

This guide will focus on the installation of modern Windows (10/11) without using Boot Camp Assistant.

  • Due to hardware and firmware limitations, UEFI Windows installations are only recommended on the following machines:

    • 2015 MacBook or newer (MacBook8,x+)
    • 2011 MacBook Air or newer (MacBookAir4,x+)
    • 2011 MacBook Pro or newer (MacBookPro8,x+)
    • 2011 Mac mini or newer (Macmini5,x+)
    • 2009* Mac Pro or newer (MacPro4,1+), upgraded GPU is preferred
    • 2010 iMac or newer (iMac11,x+), upgraded GPU is preferred
    • 2009* Xserve (Xserve3,1), upgraded GPU is preferred

*MacPro4,1, MacPro5,1, and Xserve3,1 systems experience issues with the Windows installer, follow the DISM installation section for instructions.

If your machine is not listed, UEFI Windows will likely still install, but you may face stability/driver issues.

# Disk Partitioning and Formatting

The following is required for installation:

  • 8GB+ USB Drive for the Windows installer
  • 30GB+ Free Space on an existing drive / empty drive for the Windows installation

# Formatting the USB Drive

Open Disk Utility in macOS and format the USB Drive as ExFat with the Master Boot Record scheme:

# Formatting the Target Drive

Next, select the drive you wish to install Windows in Disk Utility on and partition it as ExFat (If formatting the entire drive, ensure it's using the GUID Partition Table scheme):

WARNING

Incorrectly erasing your drive can lead to data loss! Please verify that you are erasing the correct drive/partition.

If you plan to use the same hard drive for macOS and Windows, we recommend creating a dedicated partition just for OpenCore. This lets Windows have the ESP to itself and OpenCore can stay within it's own bubble.

Recommended size is 200MB and the partition format must be FAT32 for OpenCore to operate correctly. You will next want to install OpenCore onto the new partition, either moving from the ESP with MountEFI (opens new window) or rerunning the OpenCore-Patcher.app

  • Note 1: For machines with dedicated drives for Windows, having different partitions for OpenCore is not required.
  • Note 2: Having different partitions for OpenCore is not required if the Windows boot files detected by the stock Bootpicker are removed. See "Removing the Windows option from the stock bootpicker" for further information.
  • Note 3: We recommend uninstalling OpenCore from the ESP/EFI Partition when you create this new OpenCore partition to avoid confusion when selecting OpenCore builds in the Mac's boot picker.

# Creating the Windows Installer

The latest Windows installation images can be downloaded from Microsoft using the following links:

Once the file is downloaded, mount the .iso image:

Then open terminal and use the rsync command with the disk image set as the source and your USB drive set as the target. (Replace "CCCOMA_X64" with the mounted image's partition name, and replace "InstallWin10" with your USB Drive's name).

rsync -r -P /Volumes/CCCOMA_X64/ /Volumes/InstallWin10

The rsync command will take some time, so get some coffee and sit back. Once finished, the root of the USB drive should look as follows:

  • Ensure that these folders and files are in the root of the USB drive, otherwise the USB will not boot.

# Installation Process

Once you reboot your machine, you should see a new boot option in the OCLP Bootpicker labelled as "EFI Boot" or "Windows". It may or may not have the Boot Camp icon.

WARNING

If you aren't booted into OCLP, you may see two boot options labelled "Windows" and "EFI Boot". Do not choose either of the options and boot into OCLP to continue.

# Installation: Microsoft Method

Once booted into the Windows installer, proceed as you normally would on any Windows computer. If you see an error message containing “Windows could not prepare the computer to boot into the next phase of installation”, please follow the next portion of this guide (DISM Installation).

Installing Windows 11

If you are installing Windows 11, you will need to modify the Windows Setup (opens new window) to allow installation on unsupported machines.

# Installation: DISM Deployment Method

Once booted into the Windows installer, proceed as you normally would until you reach the "Where do you want to install Windows" disk formatting section.

When you are prompted to select a drive, select your desired partition and delete it using "Delete". If you want to install Windows to an empty drive, erase every partition currently on the desired drive. After your drive/partition is erased, press "New" to create the Windows system partitions.

You will be prompted to confirm the creation of the system partitions, press "OK".

Once the partitions are created, select the main (largest) partition and press "Format". This will format the partition using the NFTS file system.

After the installer formats the partition, open up the Command Prompt by pressing SHIFT + F10. Then run the diskpart command, and list vol. This will produce a list of volumes in your system, make sure to keep track of the drive letters of the main Windows partition (largest, NTFS), the EFI partition (100MB, FAT32), and the Windows installer (Usually Drive D). Run exit to close diskpart

Now, get a list of available Windows editions by running dism /Get-WimInfo /WimFile:D:\Sources\install.wim (substituting D with the Installer Drive Letter). This guide will use Option 6 for Windows 10 Pro.

You can now start the deployment process. Run dism /Apply-Image /ImageFile:D:\Sources\install.wim /index:6 /ApplyDir:E:, replacing "D" with the Installer Drive Letter, "6" with the Windows edition option, and "E" with the Windows Partition Drive Letter.

Once dism finishes its thing, run bcdboot E:\Windows, substituting "E" for the drive letter of the main Windows partition to create the boot files.

Windows is now installed. It should be recognized as "EFI Boot" or "Windows" with a Boot Camp icon in the OCLP Bootpicker.

WARNING

After the boot files are created, DO NOT reboot if you are using a MacPro4,1, MacPro5,1, or Xserve3,1 system! A bug in the Windows bootloader exists that will completely brick the system if it is loaded through the stock bootpicker. See the "Installation: Removing the Windows option from the stock bootpicker" section for a workaround.

# Installation: Removing the Windows option from the stock bootpicker

Removing the Windows boot option from the stock bootpicker is HIGHLY RECOMMENDED on MacPro4,1, MacPro5,1, and Xserve3,1 systems in order to prevent Secure Boot NVRAM corruption and bricking.

Start up a command prompt window in the Windows Setup environment by running cmd.

Next, enter the EFI Folder by running C:, substituting "C" for the EFI Partition Drive Letter. Then run cd EFI to enter the EFI Partition. Then, run rmdir Boot /S /Q to remove the boot files that can be detected by the stock Bootpicker. The OCLP Picker will still be able to detect and boot Windows.

You can verify that the Boot folder is removed by running the dir command:

If, for whatever reason, you are not able to remove the boot files from the Windows setup, shut down your system, boot into macOS, mount your EFI partition with MountEFI (opens new window), and remove the Boot folder (it should have a recent file modification date, and contain Bootx64.efi).

# Post-Installation

# Installing Boot Camp Software

To get started, download the Brigadier utility from the following link:

Once Brigadier is downloaded, move it to your desktop for easy access.

Open up a command prompt window as a standard user and run cd desktop.

Then run .\brigadier.exe --model=MODEL1,1, replacing "MODEL1,1" with your machine's SMBIOS model.

Once the Boot Camp software is downloaded, you can install it by executing Setup.exe or \Drivers\Apple\BootCamp.msi (BootCamp64.msi if present).

# Installing Boot Camp 6 softare on unsupported machines

To get started, download the Brigadier utility from the following link:

Once Brigadier is downloaded, move it to your desktop for easy access.

Open up a command prompt window as a standard user and run cd desktop.

Then run .\brigadier.exe --model=MacPro7,1. This will download the latest BootCamp 6 package.

Once the Boot Camp software is downloaded, you can install Boot Camp 6 by executing \Drivers\Apple\BootCamp.msi in an administrator command prompt window.

# Troubleshooting

# "This version of Boot Camp is not intended for this computer model."

If you built OpenCore with Moderate or higher SMBIOS spoofing, you'll get an error when trying to install Boot Camp drivers. You can solve this by either rebuilding OpenCore with a lower spoof level, or running the installer from Drivers/Apple/BootCamp.msi.

Setup.exe BootCamp.msi
BootCamp.msi quirks

If needed, you can run it from the command line as administrator:

set __COMPAT_LAYER=WIN7RTM && start \path\to\BootCamp\Drivers\Apple\Bootcamp.msi'
@@ -32,6 +32,6 @@ After your drive/partition is erased, press "New" to create the Window
       
       ⟶
- + diff --git a/assets/js/32.0bcc4938.js b/assets/js/32.0bcc4938.js deleted file mode 100644 index d5f5f4cc2..000000000 --- a/assets/js/32.0bcc4938.js +++ /dev/null @@ -1 +0,0 @@ -(window.webpackJsonp=window.webpackJsonp||[]).push([[32],{470:function(e,t,o){"use strict";o.r(t);var n=o(25),r=Object(n.a)({},(function(){var e=this,t=e.$createElement,o=e._self._c||t;return o("ContentSlotsDistributor",{attrs:{"slot-key":e.$parent.slotKey}},[o("h1",{attrs:{id:"uninstalling-opencore"}},[o("a",{staticClass:"header-anchor",attrs:{href:"#uninstalling-opencore"}},[e._v("#")]),e._v(" Uninstalling OpenCore")]),e._v(" "),o("p",[e._v("To remove OpenCore:")]),e._v(" "),o("ol",[o("li",[e._v("Remove OpenCore either from the USB or internal drive")])]),e._v(" "),o("ul",[o("li",[e._v("You'll need to mount the drive's EFI partition, and delete the "),o("code",[e._v("EFI/OC")]),e._v(" and "),o("code",[e._v("System")]),e._v(" folders\n"),o("ul",[o("li",[e._v("Note: "),o("strong",[e._v("Do not")]),e._v(" delete the entire EFI folder, this will likely break any existing Windows and Linux installations.")]),e._v(" "),o("li",[o("a",{attrs:{href:"https://dortania.github.io/OpenCore-Post-Install/universal/oc2hdd.html",target:"_blank",rel:"noopener noreferrer"}},[e._v("See here for an example on how to mount"),o("OutboundLink")],1)]),e._v(" "),o("li",[e._v("For 5K iMac users, you will also need to delete "),o("code",[e._v("boot.efi")]),e._v(" on the root of the EFI partition.")])])])]),e._v(" "),o("ol",{attrs:{start:"2"}},[o("li",[o("a",{attrs:{href:"https://support.apple.com/HT204063",target:"_blank",rel:"noopener noreferrer"}},[e._v("Reset NVRAM"),o("OutboundLink")],1)])]),e._v(" "),o("div",{staticClass:"custom-block warning"},[o("p",{staticClass:"custom-block-title"},[e._v("WARNING")]),e._v(" "),o("p",[e._v('Note that after you remove OpenCore, your Mac will no longer boot and show the "prohibited" symbol. Be ready to install an natively-supported version of macOS before you uninstall OpenCore.')]),e._v(" "),o("ul",[o("li",[e._v("This does not apply to native Macs just using OpenCore to achieve features like AirPlay to Mac and Sidecar, but it is still recomended to reinstall macOS, after removing OpenCore, if using SMBIOS spoofing to enable Univeral Control.")])])])])}),[],!1,null,null,null);t.default=r.exports}}]); \ No newline at end of file diff --git a/assets/js/32.1ee9c6a2.js b/assets/js/32.1ee9c6a2.js new file mode 100644 index 000000000..843945833 --- /dev/null +++ b/assets/js/32.1ee9c6a2.js @@ -0,0 +1 @@ +(window.webpackJsonp=window.webpackJsonp||[]).push([[32],{470:function(e,t,o){"use strict";o.r(t);var n=o(25),r=Object(n.a)({},(function(){var e=this,t=e.$createElement,o=e._self._c||t;return o("ContentSlotsDistributor",{attrs:{"slot-key":e.$parent.slotKey}},[o("h1",{attrs:{id:"uninstalling-opencore-bootloader"}},[o("a",{staticClass:"header-anchor",attrs:{href:"#uninstalling-opencore-bootloader"}},[e._v("#")]),e._v(" Uninstalling OpenCore bootloader")]),e._v(" "),o("ol",[o("li",[e._v("Remove OpenCore either from the USB or internal drive")])]),e._v(" "),o("ul",[o("li",[e._v("You'll need to mount the drive's EFI partition, and delete the "),o("code",[e._v("EFI/OC")]),e._v(" and "),o("code",[e._v("System")]),e._v(" folders\n"),o("ul",[o("li",[e._v("Note: "),o("strong",[e._v("Do not")]),e._v(" delete the entire EFI folder, this will likely break any existing Windows and Linux installations.")]),e._v(" "),o("li",[o("a",{attrs:{href:"https://dortania.github.io/OpenCore-Post-Install/universal/oc2hdd.html",target:"_blank",rel:"noopener noreferrer"}},[e._v("See here for an example on how to mount"),o("OutboundLink")],1)]),e._v(" "),o("li",[e._v("For 5K iMac users, you will also need to delete "),o("code",[e._v("boot.efi")]),e._v(" on the root of the EFI partition.")])])])]),e._v(" "),o("ol",{attrs:{start:"2"}},[o("li",[o("a",{attrs:{href:"https://support.apple.com/HT204063",target:"_blank",rel:"noopener noreferrer"}},[e._v("Reset NVRAM"),o("OutboundLink")],1)])]),e._v(" "),o("div",{staticClass:"custom-block warning"},[o("p",{staticClass:"custom-block-title"},[e._v("WARNING")]),e._v(" "),o("p",[e._v('Note that after you remove OpenCore, your Mac will no longer boot and show the "prohibited" symbol. Be ready to install an natively-supported version of macOS before you uninstall OpenCore.')]),e._v(" "),o("ul",[o("li",[e._v("This does not apply to native Macs just using OpenCore to achieve features like AirPlay to Mac and Sidecar, but it is still recommended to reinstall macOS after removing OpenCore, if using SMBIOS spoofing to enable Univeral Control.")])])]),e._v(" "),o("p",[e._v("If you used OCLP on a native system and want to remove the application without reinstalling the OS, navigate to "),o("code",[e._v("/Library/Application Support/")]),e._v(" and delete the Dortania folder.")])])}),[],!1,null,null,null);t.default=r.exports}}]); \ No newline at end of file diff --git a/assets/js/app.ae751934.js b/assets/js/app.07658647.js similarity index 93% rename from assets/js/app.ae751934.js rename to assets/js/app.07658647.js index 388e27607..9700b5a81 100644 --- a/assets/js/app.ae751934.js +++ b/assets/js/app.07658647.js @@ -1,4 +1,4 @@ -(window.webpackJsonp=window.webpackJsonp||[]).push([[0],[]]);!function(t){function e(e){for(var r,a,c=e[0],s=e[1],u=e[2],f=0,p=[];f0?o(r(t),9007199254740991):0}},function(t,e){var n=Array.isArray;t.exports=n},function(t,e,n){var r=n(33),o=n(19);t.exports=function(t){return r(o(t))}},function(t,e,n){var r=n(142),o="object"==typeof self&&self&&self.Object===Object&&self,i=r||o||Function("return this")();t.exports=i},function(t,e,n){var r=n(6),o=n(1),i=n(7),a=Object.defineProperty,c={},s=function(t){throw t};t.exports=function(t,e){if(i(c,t))return c[t];e||(e={});var n=[][t],u=!!i(e,"ACCESSORS")&&e.ACCESSORS,l=i(e,0)?e[0]:s,f=i(e,1)?e[1]:void 0;return c[t]=!!n&&!o((function(){if(u&&!r)return!0;var t={length:-1};u?a(t,1,{enumerable:!0,get:s}):t[1]=1,n.call(t,l,f)}))}},function(t,e,n){var r=n(114),o=n(2),i=function(t){return"function"==typeof t?t:void 0};t.exports=function(t,e){return arguments.length<2?i(r[t])||i(o[t]):r[t]&&r[t][e]||o[t]&&o[t][e]}},function(t,e){t.exports=function(t){if(null==t)throw TypeError("Can't call method on "+t);return t}},function(t,e){t.exports=!1},function(t,e,n){var r=n(6),o=n(80),i=n(35),a=n(15),c=n(34),s=n(7),u=n(109),l=Object.getOwnPropertyDescriptor;e.f=r?l:function(t,e){if(t=a(t),e=c(e,!0),u)try{return l(t,e)}catch(t){}if(s(t,e))return i(!o.f.call(t,e),t[e])}},function(t,e){var n={}.toString;t.exports=function(t){return n.call(t).slice(8,-1)}},function(t,e){t.exports=function(t){if("function"!=typeof t)throw TypeError(String(t)+" is not a function");return t}},function(t,e,n){var r=n(231),o=n(234);t.exports=function(t,e){var n=o(t,e);return r(n)?n:void 0}},function(t,e,n){"use strict";function r(t,e,n,r,o,i,a,c){var s,u="function"==typeof t?t.options:t;if(e&&(u.render=e,u.staticRenderFns=n,u._compiled=!0),r&&(u.functional=!0),i&&(u._scopeId="data-v-"+i),a?(s=function(t){(t=t||this.$vnode&&this.$vnode.ssrContext||this.parent&&this.parent.$vnode&&this.parent.$vnode.ssrContext)||"undefined"==typeof __VUE_SSR_CONTEXT__||(t=__VUE_SSR_CONTEXT__),o&&o.call(this,t),t&&t._registeredComponents&&t._registeredComponents.add(a)},u._ssrRegister=s):o&&(s=c?function(){o.call(this,(u.functional?this.parent:this).$root.$options.shadowRoot)}:o),s)if(u.functional){u._injectStyles=s;var l=u.render;u.render=function(t,e){return s.call(e),l(t,e)}}else{var f=u.beforeCreate;u.beforeCreate=f?[].concat(f,s):[s]}return{exports:t,options:u}}n.d(e,"a",(function(){return r}))},function(t,e,n){"use strict";var r=n(0),o=n(31).filter,i=n(54),a=n(17),c=i("filter"),s=a("filter");r({target:"Array",proto:!0,forced:!c||!s},{filter:function(t){return o(this,t,arguments.length>1?arguments[1]:void 0)}})},function(t,e){t.exports=function(t){return null!=t&&"object"==typeof t}},function(t,e,n){var r,o=n(5),i=n(189),a=n(78),c=n(36),s=n(113),u=n(75),l=n(49),f=l("IE_PROTO"),p=function(){},d=function(t){return" +