From 48e0d03dd4b0319f4723677786096023886a38b4 Mon Sep 17 00:00:00 2001 From: ParaDoX1994 <35791009+ParaDoX1994@users.noreply.github.com> Date: Sun, 21 Jul 2024 21:35:50 +0000 Subject: [PATCH] =?UTF-8?q?Deploying=20to=20gh-pages=20from=20=20@=20580fb?= =?UTF-8?q?83b4da6178c96a9c64dae6399342c519a8d=20=F0=9F=9A=80?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- 404.html | 4 ++-- ACCEL.html | 4 ++-- BOOT.html | 4 ++-- BUILD.html | 4 ++-- DEBUG.html | 4 ++-- DONATE.html | 4 ++-- HOW.html | 4 ++-- ICNS.html | 4 ++-- INSTALLER.html | 4 ++-- ISSUES-HOLD.html | 4 ++-- LICENSE.html | 4 ++-- MODELS.html | 4 ++-- MONTEREY-DROP.html | 4 ++-- PATCHEXPLAIN.html | 4 ++-- POST-INSTALL.html | 11 ++++++----- PROCESS.html | 4 ++-- SONOMA-DROP.html | 4 ++-- START.html | 4 ++-- TERMS.html | 4 ++-- TROUBLESHOOTING.html | 4 ++-- UNINSTALL.html | 4 ++-- UNIVERSALCONTROL.html | 4 ++-- UPDATE.html | 4 ++-- VENTURA-DROP.html | 4 ++-- WINDOWS.html | 4 ++-- assets/js/{13.cbfb8b87.js => 13.ca3d857c.js} | 2 +- assets/js/17.0f1e81b7.js | 1 + assets/js/17.2edde964.js | 1 - assets/js/{21.6c546bc0.js => 21.625fb5b2.js} | 2 +- assets/js/{22.f0d1a9e3.js => 22.9a706226.js} | 2 +- assets/js/{24.cc043e95.js => 24.7709e51c.js} | 2 +- assets/js/{29.07eab220.js => 29.2cbae388.js} | 2 +- assets/js/{30.8b2580fb.js => 30.cfad7a4d.js} | 2 +- assets/js/{34.caa450b6.js => 34.a08275e9.js} | 2 +- assets/js/{35.5d6be7d9.js => 35.0dc73b70.js} | 2 +- assets/js/{37.8551ebe2.js => 37.c2331bb2.js} | 2 +- assets/js/{38.e637d566.js => 38.8e9b7620.js} | 2 +- assets/js/{40.0c128b1f.js => 40.a2656d87.js} | 2 +- assets/js/{41.6ad5e52c.js => 41.8d0c42c3.js} | 2 +- assets/js/{42.586742c6.js => 42.be3bfd96.js} | 2 +- assets/js/{43.cf02c5ef.js => 43.4f360704.js} | 2 +- assets/js/{44.23e634a4.js => 44.6c8d5236.js} | 2 +- assets/js/{45.40adea3f.js => 45.1a7fd413.js} | 2 +- assets/js/{47.670f9e5a.js => 47.53ab8459.js} | 2 +- assets/js/{49.f1bf7b17.js => 49.52174ef9.js} | 2 +- assets/js/{app.c66ce990.js => app.75d85b0a.js} | 4 ++-- index.html | 4 ++-- 47 files changed, 77 insertions(+), 76 deletions(-) rename assets/js/{13.cbfb8b87.js => 13.ca3d857c.js} (99%) create mode 100644 assets/js/17.0f1e81b7.js delete mode 100644 assets/js/17.2edde964.js rename assets/js/{21.6c546bc0.js => 21.625fb5b2.js} (88%) rename assets/js/{22.f0d1a9e3.js => 22.9a706226.js} (98%) rename assets/js/{24.cc043e95.js => 24.7709e51c.js} (82%) rename assets/js/{29.07eab220.js => 29.2cbae388.js} (93%) rename assets/js/{30.8b2580fb.js => 30.cfad7a4d.js} (96%) rename assets/js/{34.caa450b6.js => 34.a08275e9.js} (99%) rename assets/js/{35.5d6be7d9.js => 35.0dc73b70.js} (97%) rename assets/js/{37.8551ebe2.js => 37.c2331bb2.js} (95%) rename assets/js/{38.e637d566.js => 38.8e9b7620.js} (98%) rename assets/js/{40.0c128b1f.js => 40.a2656d87.js} (93%) rename assets/js/{41.6ad5e52c.js => 41.8d0c42c3.js} (97%) rename assets/js/{42.586742c6.js => 42.be3bfd96.js} (98%) rename assets/js/{43.cf02c5ef.js => 43.4f360704.js} (99%) rename assets/js/{44.23e634a4.js => 44.6c8d5236.js} (99%) rename assets/js/{45.40adea3f.js => 45.1a7fd413.js} (96%) rename assets/js/{47.670f9e5a.js => 47.53ab8459.js} (96%) rename assets/js/{49.f1bf7b17.js => 49.52174ef9.js} (97%) rename assets/js/{app.c66ce990.js => app.75d85b0a.js} (93%) diff --git a/404.html b/404.html index bd3e06ec7..3b19280d6 100644 --- a/404.html +++ b/404.html @@ -11,13 +11,13 @@ - +

404

Looks like we've got some broken links.
Take me home.
- + diff --git a/ACCEL.html b/ACCEL.html index 9663de42e..9c563b4be 100644 --- a/ACCEL.html +++ b/ACCEL.html @@ -11,7 +11,7 @@ - + @@ -45,6 +45,6 @@ nvram FA4CE28D-B62F-4C99-9CC3-6815686E30F9:gpu-power-prefs
- + diff --git a/BOOT.html b/BOOT.html index c7539f563..635b89fdc 100644 --- a/BOOT.html +++ b/BOOT.html @@ -11,7 +11,7 @@ - + @@ -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 2302e1ffe..441a94084 100644 --- a/BUILD.html +++ b/BUILD.html @@ -11,7 +11,7 @@ - + @@ -29,6 +29,6 @@ If you're building OpenCore for a different model than you're currently running, ⟶

- + diff --git a/DEBUG.html b/DEBUG.html index f6588850a..9c48e8eff 100644 --- a/DEBUG.html +++ b/DEBUG.html @@ -11,7 +11,7 @@ - + @@ -29,6 +29,6 @@ ⟶

- + diff --git a/DONATE.html b/DONATE.html index 57ced5bcf..f08f90303 100644 --- a/DONATE.html +++ b/DONATE.html @@ -11,7 +11,7 @@ - + @@ -28,6 +28,6 @@ ⟶

- + diff --git a/HOW.html b/HOW.html index b0542a4d3..82cd82a41 100644 --- a/HOW.html +++ b/HOW.html @@ -11,7 +11,7 @@ - + @@ -28,6 +28,6 @@ ⟶

- + diff --git a/ICNS.html b/ICNS.html index 786d63245..03b9fa4b4 100644 --- a/ICNS.html +++ b/ICNS.html @@ -11,7 +11,7 @@ - + @@ -32,6 +32,6 @@ ⟶

- + diff --git a/INSTALLER.html b/INSTALLER.html index 71f6973df..37f0fef66 100644 --- a/INSTALLER.html +++ b/INSTALLER.html @@ -11,7 +11,7 @@ - + @@ -28,6 +28,6 @@ ⟶

- + diff --git a/ISSUES-HOLD.html b/ISSUES-HOLD.html index 088406b15..b2d45a78d 100644 --- a/ISSUES-HOLD.html +++ b/ISSUES-HOLD.html @@ -11,7 +11,7 @@ - + @@ -28,6 +28,6 @@ ⟶

- + diff --git a/LICENSE.html b/LICENSE.html index 60de1724a..869635575 100644 --- a/LICENSE.html +++ b/LICENSE.html @@ -11,7 +11,7 @@ - + @@ -31,6 +31,6 @@ ⟶

- + diff --git a/MODELS.html b/MODELS.html index 568c68d29..1ff4bc301 100644 --- a/MODELS.html +++ b/MODELS.html @@ -11,7 +11,7 @@ - + @@ -28,6 +28,6 @@ ⟶

- + diff --git a/MONTEREY-DROP.html b/MONTEREY-DROP.html index 1b5faf84d..8083a0970 100644 --- a/MONTEREY-DROP.html +++ b/MONTEREY-DROP.html @@ -11,7 +11,7 @@ - + @@ -33,6 +33,6 @@ ⟶

- + diff --git a/PATCHEXPLAIN.html b/PATCHEXPLAIN.html index d64ae627f..fc3bc78d8 100644 --- a/PATCHEXPLAIN.html +++ b/PATCHEXPLAIN.html @@ -11,7 +11,7 @@ - + @@ -115,6 +115,6 @@

- + diff --git a/POST-INSTALL.html b/POST-INSTALL.html index 39c2a72ae..44aa62269 100644 --- a/POST-INSTALL.html +++ b/POST-INSTALL.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,9 @@ 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:

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.

# SIP settings

SIP, or System Integrity Protection, needs to be lowered on systems where root patching is required to patch data on disk. This will vary between OS versions and the model in question. OCLP by default will determine the proper SIP options for the OS version and Mac model, in most cases the user has no need to touch these settings. However, this part explains how the SIP settings work in OCLP, where lowered SIP is needed and where full SIP could be enabled.

WARNING

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

SIP settings can be accessed from the Security tab shown in the images. To change SIP settings, make the changes here, return in main menu and rebuild OpenCore using the first option.

SIP Enabled SIP Lowered (Root Patching) SIP Disabled

In the cases where SIP can be enabled, manually enabling it is needed. Easiest way to check whether you can fully enable SIP is the "Post Install Root Patch" section, if that section tells your system doesn't need patches (or you don't install the patches e.g. in case you don't need WiFi on a Mac Pro with upgraded GPU running Monterey) then it is safe to assume full SIP can be enabled.

Ventura and newer

In Ventura and newer, all unsupported systems require lowered SIP due to root patching required, where data on the system volume is patched.

Monterey

In Monterey, majority of unsupported systems from 2013 forward can enable full SIP, due to root patches not being required. -Pre-2012 systems, also known as "non-Metal" (includes Mac Pros without upgraded GPU), as well as NVIDIA Kepler and Intel HD 4000 GPUs will require root patching, which requires lowered SIP.

Some systems such as Mac Pros also require root patching for stock WiFi cards but if you do not need WiFi or you plan to upgrade the card, there is no need for root patching and as such SIP can be fully enabled.

Big Sur

Majority of unsupported systems can run with full SIP enabled, as root patching is not required. Non-Metal still requires root patching and lowered SIP.

# 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.

    # SIP settings

    SIP, or System Integrity Protection, needs to be lowered on systems where root patching is required to patch data on disk. This will vary between OS versions and the model in question. OCLP by default will determine the proper SIP options for the OS version and Mac model, in most cases the user has no need to touch these settings. However, this part explains how the SIP settings work in OCLP, where lowered SIP is needed and where full SIP could be enabled.

    WARNING

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

    SIP settings can be accessed from the Security tab shown in the images. To change SIP settings, make the changes here, return in main menu and rebuild OpenCore using the first option.

    SIP Enabled SIP Lowered (Root Patching) SIP Disabled

    In the cases where SIP can be enabled, manually enabling it is needed. Easiest way to check whether you can fully enable SIP is the "Post Install Root Patch" section, if that section tells your system doesn't need patches (or you don't install the patches e.g. in case you don't need WiFi on a Mac Pro with upgraded GPU running Monterey) then it is safe to assume full SIP can be enabled.

    Ventura and newer

    All unsupported systems require lowered SIP.

    Monterey

    Majority of unsupported systems from 2013 onward can enable full SIP. +Pre-2012 systems, also known as "non-Metal" (includes Mac Pros without upgraded GPU), as well as NVIDIA Kepler and Intel HD 4000 GPUs require lowered SIP.

    Some systems such as Mac Pros also require root patching for stock WiFi cards but if you do not need WiFi or you plan to upgrade the card, there is no need for root patching and as such SIP can be fully enabled.

    Big Sur

    All Metal capable systems from 2012 onward (incl. NVIDIA Kepler and Intel HD 4000) as well as Mac Pros with upgraded GPU can run with full SIP enabled. +Non-Metal systems still require lowered SIP.

    # 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: @@ -30,7 +31,7 @@ Pre-2012 systems, also known as "non-Metal" (includes Mac Pros without
      • BCM94328
      • BCM94322
    • Atheros
    GPUs requiring patching in macOS Ventura
    • NVIDIA:
      • Kepler (600 - 800 series)
    • AMD:
      • GCN 1-3 (7000 - R9 series)
      • Polaris (RX 4xx/5xx series, if CPU lacks AVX2)
    • Intel: -
      • Ivy Bridge (4000 series)
      • Haswell (4400, 4600, 5000 series)
      • Broadwell (6000 series)
      • Skylake (500 series)

    +

    • Ivy Bridge (4000 series)
    • Haswell (4400, 4600, 5000 series)
    • Broadwell (6000 series)
    • Skylake (500 series)

⟵ ⟶

- + diff --git a/PROCESS.html b/PROCESS.html index 02d5426b9..98752978a 100644 --- a/PROCESS.html +++ b/PROCESS.html @@ -11,7 +11,7 @@ - + @@ -29,6 +29,6 @@ Dortania cannot do anything about this.