It's that time of year again and with it, and a new macOS beta has been dropped. Here's all the info you need to get started.

Reminder that Dortania and any tools mentioned in this guide are neither responsible for any corruption, data loss, or other ill effects that may arise from this guide, including ones caused by typos. You, the end user, must understand this is beta software on unsupported machines so do not pester developers for fixes. Dortania will not be accepting issues regarding this mini-guide except for typos and/or errors.

WARNING DO NOT INSTALL Big Sur 11.3 it is not compatible with Mac Pro 5,1s. Only 11.2.3 works and may be the final version of Mac OS for our 5,1s unless the. My OpenCore package only allow you to run Catalina on the Mac Pro 5,1, but not install it.If you want to install Catalina, please follow the steps in this vi. My latest OpenCore package can be downloaded at herehttps://forums.macrumors.com/threads/activate-amd-hardware-acceleration.2180095/page-53?post=28255048#pos. 'Easy' Install of OpenCore on a Mac Pro 4,1 flashed to 5,1 or a 2010 -2012 Mac Pro 5,1. Don’t Do This. do you research and make sure it is something yo.

This guide expects you to have a basic understanding of hackintoshing. If you are not familiar with it, we highly recommend you to wait until there is an easier and more straight-forward solution available.

# Backstory

More a mini-explainer as to why this release is a bit more painful than average macOS releases, the main culprits are as follows:

# AvoidRuntimeDefrag

With macOS Big Sur, the AvoidRuntimeDefrag Booter quirk in OpenCore broke. Because of this, the macOS kernel will fall flat when trying to boot. Reason for this is due to cpu_count_enabled_logical_processors requiring the MADT (APIC) table, and so OpenCore will now ensure this table is made accessible to the kernel. Users will however need a build of OpenCore 0.6.0 with commit bb12f5f or newer to resolve this issue.

# Kernel Collections vs prelinkedkernel

Since 10.7, the prelinkedkernel has been the default way for real macs to boot. This contained a very minimal amount of kexts to get a mac booted. This same bundle is what OpenCore uses to inject kexts, and was hoped to last quite some time. With macOS Big Sur, a huge change happened in where Apple no longer makes it the default form of booting.

Due to the hard work of @acidanthera, OpenCore gained experimental support for this new format in roughly 2 weeks, and we can now attempt to boot Big Sur on our hackintoshes without a Mac or VM - although you will likely run into some issues along the way.

# Prerequisites

Before we can jump head first into installing Big Sur, we need to go over a few things:

# A supported SMBIOS

Big Sur dropped a few Ivy Bridge and Haswell based SMBIOS from macOS, so see below that yours wasn't dropped:

• iMac14,3 and older
  • Note iMac14,4 is still supported
• MacPro5,1 and older
• MacMini6,x and older
• MacBook7,1 and older
• MacBookAir5,x and older
• MacBookPro10,x and older

If your SMBIOS was supported in Catalina and isn't included above, you're good to go!

For those wanting a simple translation for their Ivy and Haswell Machines:

• iMac13,2, iMac14,2 and iMac14,3 should transition over to using iMac15,1
• iMac14,1 should transition over to iMac14,4

# Supported hardware

Not much hardware has been dropped, though the few that have:

• Official Ivy Bridge U, H and S CPUs.
  • These CPUs will still boot without much issue, but note that no Macs are supported with consumer Ivy Bridge in Big Sur.
  • Ivy Bridge-E CPUs are still supported thanks to being in MacPro6,1
• Ivy Bridge iGPUs.
  • HD 4000 and HD 2500, initial developer beta forgot to remove drivers but more than likely to be removed in later updates.
• BCM94331CD based Wifi cards.
  • See Wireless Buyers guide for potential cards to upgrade to.
• Certain SATA controllers dropped
  • For some reason, Apple removed the AppleIntelPchSeriesAHCI class from AppleAHCIPort.kext. Due to the outright removal of the class, trying to spoof to another ID (generally done by SATA-unsupported.kext) can fail for many and create instability for others.
  • A partial fix is to block Big Sur's AppleAHCIPort.kext and inject Catalina's version with any conflicting symbols being patched. You can find a sample kext here: Catalina's patched AppleAHCIPort.kext
  • This will work in both Catalina and Big Sur so you can remove SATA-unsupported if you want.

Also note that AMD OSX has updated their patches, but they are experimental and unsupported and you will not obtain support for them:

And a special note for MSI Navi users, you no longer require the ATY,rom/-wegnoegpu patch to boot the installer!

# Up-to-date kexts, bootloader and config.plist

Ensure you've updated to the latest builds (not releases) of OpenCore and all your kexts, as to avoid any odd incompatibility issues. You can find the latest builds of kexts and OpenCore here:

• Driver Repo (contains OpenCore builds too).

You will also need to ensure you have a few NVRAM variables set:

• NVRAM -> Add -> 7C436110-AB2A-4BBB-A880-FE41995C9F82:
  • boot-args:
    • -lilubetaall
      • Newest builds of Lilu(v1.4.6+) and most plugins do not require this boot-arg
    • vsmcgen=1
      • Newest builds of Lilu(v1.4.6+) and VirtualSMC(v1.1.5+) don't need this boot-arg
    • -disablegfxfirmware
      • Newer builds of WhateverGreen(v1.4.1+) resolves this

If you're unsure what version of OpenCore you're using, you can run the following in terminal:

• Note: The about command will require you to include bit 0x2 in Misc -> Security -> ExposeSensitiveData, recommended values for ExposeSensitiveData is 0x6 which includes bits 0x2 and 0x4.

# Known issues

With Big Sur, quite a bit broke. Mainly the following:

• Lilu
  • Mainly user-space patching has severely broke, meaning certain patches like DRM don't work
  • Kernel-space should be working correctly with v1.4.6, but plugins may require updates due to a complete rewrite of the patcher for Kernel Collection support.
• VirtualSMC
  • Some users may notice that even with vsmcgen=1 in boot-args, you'll still have VirtualSMC failing. To work around this, you may need to use FakeSMC till vSMC and Lilu issues are resolved.
  • Resolved with v1.1.5+
• Battery status
  • Currently RehabMan's ACPIBatteryManager is the only working kext for battery status.
  • Resolved with VirtualSMC v1.1.5+
• AirportBrcmFixup
  • Forcing a specific driver to load with brcmfx-driver= may help
  • BCM94352Z users for example may need brcmfx-driver=2 in boot-args to resolve this, other chipsets will need other variables.
• Intel HEDT hackintoshes failing to boot
  • This is due to Asus and many other OEMs excluding certain regions from your RTC device, to resolve this we can create a new RTC device with the proper regions.
  • OpenCorePkg includes a sample SSDT that goes in-depth: SSDT-RTC0-RANGE.dsl

And while not an issue, SIP has now gained a new bit so to properly disable SIP you need to set csr-active-config to FF0F0000. See here for more info: Disabling SIP

# Installation

For the installation, you'll need a few things:

• macOS Big Sur installer
• 12GB+ USB drive
• A Mac, hack, or pre-existing VM to download the installer and create install media
• Latest builds of OpenCore and kexts (see above)

# Grabbing the installer

To grab the Big Sur installer, download the beta profile from Apple's developer portal, then check for updates in System Preferences. If you don't have a developer account, you can use gibMacOS to download it:

Download gibMacOS and open gibMacOS.command:

Press M to change the Max OS, then enter 10.16 to switch the (update) catalog to the Big Sur one.

Press C to change the catalog, then select the number for the developer catalog.

Select the number for the Big Sur beta to start downloading it.

Once finished, open the InstallAssistant.pkg that was downloaded - it will be located in the gibMacOS/macOS Downloads/developer/XXX-XXXXX - Install macOS Beta folder. This package from Apple will create Install macOS Big Sur Beta.app in your /Applications folder.

Run the InstallAssistant.pkg and point this to whichever drive you're booting off of, this is where the Install.app will be dropped:

Once done, you should find it located in your Applications folder:

# Creating the installer

To create the USB is quite simple, grab your USB drive and open Disk Utility in macOS. Next format as follows:

• Name: MyVolume
• Format: macOS Journaled
• Scheme: GUID Partition Map

Once this is done, run the following command:

This will take some time so you may want to grab a coffee, once done your USB should be good to boot!(Assuming you updated OpenCore and co earlier)

# Installing

Installing macOS 11: Big Sur on a Hackintosh is fairly similar to how previous version of macOS were installed, with the main issues being:

• KernelCollections over prelinkedkernel (discussed above)
• Installation being much longer
  • This is due to the new snapshot feature of the OS
• Certain kexts breaking
  • Mainly Lilu and plugins, though quite obvious when they break

For the last one, if you get a kernel panic with Lilu we highly recommend you to update to the latest version with links we provided above. If errors are still not resolved, you may need to disable Lilu outright.

# Troubleshooting

# Stuck at Forcing CS_RUNTIME for entitlement

This is actually the part at where macOS will seal the system volume, and where it may seem that macOS has gotten stuck. DO NOT RESTART thinking you're stuck, this will take quite some time to complete.

# Stuck at PCI Configuration Begins for Intel's HEDT boards

As previously mentioned, Intel HEDT motherboards may have some issues revolving around their RTC device in ACPI. To resolve, you'll need to look at your RTC device and see which regions are missing. For more information, see here: SSDT-RTC0-RANGE.dsl

# Stuck on ramrod(^^^^^^^^^^^^^)

If you get stuck around the ramrod section (specifically, it boots, hits this error, and reboots again back into this, causing a loop), this hints that your SMC emulator is broken. To fix this, you have 2 options:

• Ensure you're using the latest builds of VirtualSMC and Lilu, with the vsmcgen=1 boot-arg
• Switch over to Rehabman's FakeSMC (you can use the MinKernel/MaxKernel trick mentioned above to restrict FakeSMC to Big Sur and up

And when switching kexts, ensure you don't have both FakeSMC and VirtualSMC enabled in your config.plist, as this will cause a conflict.

# DeviceProperties injection failing

With Big Sur, macOS has become much pickier with devices being present in ACPI. Especially if you're injecting important properties for WhateverGreen or AppleALC, you may find they're no longer applying. To verify whether your ACPI defines your hardware, check for the acpi-path property in IORegistryExplorer:

If no property is found, you'll need to create an SSDT that provides the full pathing as you likely have a PCI Bridge that is not documented in your ACPI tables. An example of this can be found here: SSDT-BRG0

• Note: This issue may also pop up in older versions of macOS, however Big Sur is most likely to have issues.

# Some kexts may not be compatible with Big Sur yet

There are a lot of kexts out there, and Big Sur is still pretty new. Not all kexts are working yet, so if you're experiencing a weird kernel panic, one thing you can try is booting with only the essential kexts (Lilu, VirtualSMC/FakeSMC, WhateverGreen) and seeing if it works. If so, you can enable kexts one by one to try to narrow down the issue.

# Virtual Machine Route

If you're still facing issues, or if with a new beta things break, you can try the virtual machine route to install on a disk and then transfer it over to your hack. Follow the following instructions to build install media and then install in a hypervisor.

Note: If you have an AMD CPU, this method isn't going to work.

# Building the Installation Media

Requirements:

• A computer or VM running macOS
• The desired macOS installation software installed to /Applications

Once you have the installation software installed to /Applications you will need to create a VDI of the installation media that will be used to install macOS in your VM. The instructions below are intended to be cut and pasted without editing unless specified.

First, set the IMAGE variable to the name of the installation you are installing. The example defines the image for Big Sur.

Next, create an empty 16GB image to host the media.

Verify that you have a 16GB file named 'Install macOS Beta.img' before continuing. After that, attach it to your macOS system as a virtual disk using the variable you created earlier.

Run diskutil list and verify that you have a disk attached that is type 'disk image'.

Now that the image is mounted, format it to Journaled HFS+.

Once the image is formatted, create the installation media.

Now detach or eject the virtual disk.

You now have a raw image of the installer. Follow the appropriate page for the hypervisor you'll be choosing:

以下为 快照 页面，建议前往来源网站查看，会有更好的阅读体验。
原文链接: https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/

OpenCore on the Mac Pro

OpenCore on Legacy Apple Hardware
This guide explains how to use the excellent OpenCore bootloader on a classic Mac Pro to install, run and update macOS Catalina, resulting in a clean, unpatched operating system no different than on a supported Mac.
Why OpenCore?
There are several advantages to using OpenCore on a classic Mac Pro:
Boot picker screen (even with a standard graphics card)

Software Update (just like on a supported Mac)Hardware acceleration (and DRM for Netflix on Safari)Requirements* Need to upgrade? See the upgrade instructions.
** Several GPUs that are supported with High Sierra had support removed from Mojave and Catalina, like any non-Kepler generation NVIDIA GPUs or AMD GPUs earlier than HD 7950. Several HD 78xx GPUs (Pitcairn) were rebadged as R9 2xx and are not supported anymore by Mojave/Catalina drivers. All Mac Pro factory GPUs had support removed with Mojave.1 Disk Setup
Prepare two disks as follows:Disk ADisk BThese disks should be the only ones in your Mac. To ensure a bootable fallback, it is recommended that Disk B be a SATA disk in Bay 1.
2 Install OpenCore
You will need:Copy the files to the EFI volume of Disk A

• Open Terminal
• Find the EFI volume of Disk A by entering: diskutil list

• Mount the EFI volume by entering: sudo diskutil mount /dev/diskAs1

• Copy the folder OpenCore/X64/EFI to the volume /Volumes/EFI

• Copy config.plist to /Volumes/EFI/EFI/OC

3 First Boot
Reboot into recovery

• Open Terminal
• Reboot into recovery by entering: sudo nvram 'recovery-boot-mode=unused' && sudo reboot recovery

Bless the EFI volume of Disk A and reboot

• In recovery, open Terminal (see Utilities in the menu bar)
• Find the EFI volume of Disk A by entering: diskutil list

• Mount the EFI volume by entering: diskutil mount /dev/diskAs1
• Bless the volume for booting by entering: bless --mount /Volumes/EFI --setBoot

• Now shut down your Mac and reset the SMC (unplug the power cord, wait 15 seconds, plug the power cord back in, wait 5 seconds, and then press the power button)

Check the installation

• Open Terminal
• Check that OpenCore has actually booted the system by entering: nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version

• Check the VMM flag by entering: sysctl machdep.cpu.features

4 Install Catalina
You will need:Install Catalina to Disk A

• Run the installer and select Disk A

• Complete the installation

5 Post-Install
Open the configuration file

• Open Terminal
• Find the EFI volume of Disk A by entering: diskutil list

• Mount the EFI volume by entering: sudo diskutil mount /dev/diskAs1

• Navigate to /Volumes/EFI/EFI/OC and copy config.plist to your home folder
• Open config.plist in your home folder with TextEdit

Toggle the VMM flag

• Find Cpuid1Mask and make the appropriate change

ONOFFDisable the special GOP renderer if not needed

• Find DirectGopRendering and change true to false

Customize the boot screen

• If you have a HiDPI display (retina), find UIScale and change AQ to Ag
• To get a black boot screen (like all supported Macs), find ConsoleAttributes and change 112 to 0 and find DefaultBackgroundColor and change v7+/AA to AAAAAA
• To hide the boot picker find ShowPicker and change true to false

Load the configuration

• Close config.plist and copy it back to /Volumes/EFI/EFI/OC
• Reboot

Enabling Hardware Acceleration
You will need:Copy the files to the kexts folder

• Open Terminal
• Find the EFI volume of Disk A by entering: diskutil list

• Mount the EFI volume by entering: sudo diskutil mount /dev/diskAs1

Install Opencore Mac Pro 5 15

• Copy Lilu.kext and WhateverGreen.kext and (if you have a dual-processor machine) AppleMCEReporterDisabler.kext to /Volumes/EFI/EFI/OC/Kexts

Open the configuration file

• Navigate to /Volumes/EFI/EFI/OC and copy config.plist to your home folder
• Open config.plist in your home folder with TextEdit

Tell OpenCore about the kexts

• Locate the Kernel key
• Below it, replace

• If you have a dual-processor machine, add

Add the device properties

• Find the DeviceProperties key
• Below it, replace

Hybridization

• Find the SMBIOS key
• Below it, replace

• Find UpdateSMBIOS and change false to true

Clean up the NVRAM

• Find NVRAM and delete

Verify the configuration

• Close config.plist
• In Terminal, enter: plutil -convert xml1 config.plist && plutil config.plist

Load the configuration

• Copy config.plist back to /Volumes/EFI/EFI/OC
• Reboot

Enabling Night Shift
You will need:Copy the files to the kexts folder

• Open Terminal
• Find the EFI volume of Disk A by entering: diskutil list

Install Opencore Mac Pro 5 1

• Mount the EFI volume by entering: sudo diskutil mount /dev/diskAs1

• Copy Lilu.kext (unless you already have it) and NightShiftEnabler.kext to /Volumes/EFI/EFI/OC/Kexts

Open the configuration

• Navigate to /Volumes/EFI/EFI/OC and copy config.plist to your home folder
• Open config.plist in your home folder with TextEdit

Tell OpenCore about the kexts

• Locate the Kernel key
• If this is your first time adding kexts, replace

• Otherwise, add the NightShiftEnabler dictionary entry to the array

Verify the configuration

• Close config.plist
• In Terminal, enter: plutil -convert xml1 config.plist && plutil config.plist

Load the configuration

• Copy config.plist back to /Volumes/EFI/EFI/OC
• Reboot

Making External Drives Internal
You will need:Open the configuration file

• Open Terminal
• Find the EFI volume of Disk A by entering: diskutil list

• Mount the EFI volume by entering: sudo diskutil mount /dev/diskAs1

• Navigate to /Volumes/EFI/EFI/OC and copy config.plist to your home folder
• Open config.plist in your home folder with TextEdit

Add the built-in property

• Locate the DeviceProperties key
• If this is your first time adding device properties, replace

• Otherwise, add the path key and dictionary entry to the dictionary

Verify the configuration

• Close config.plist
• In Terminal, enter: plutil -convert xml1 config.plist && plutil config.plist

Load the configuration

• Copy config.plist back to /Volumes/EFI/EFI/OC
• Reboot

Enabling the Graphical Boot Picker
You will need:Copy the files to the resources folder

• Open Terminal
• Find the EFI volume of Disk A by entering: diskutil list

• Mount the EFI volume by entering: sudo diskutil mount /dev/diskAs1

• Copy OcBinaryData/Resources to /Volumes/EFI/EFI/OC (overwrite the existing folder)

Open the configuration file

• Navigate to /Volumes/EFI/EFI/OC and copy config.plist to your home folder
• Open config.plist in your home folder with TextEdit

Enable OpenCanopy

• Find PickerMode and change Builtin to External
• Locate the Drivers key and add

Verify the configuration

• Close config.plist
• In Terminal, enter: plutil -convert xml1 config.plist && plutil config.plist

Load the configuration

• Copy config.plist back to /Volumes/EFI/EFI/OC
• Reboot

Updating Catalina
To update Catalina, simply turn on the VMM flag (see toggle the VMM flag in step 5 of Part I and don't forget to reboot). To manually check for updates, choose Apple menu > System Preferences, then click Software Update.
Updating OpenCore
OpenCore is currently being updated on the first Monday of every month. To update OpenCore, simply repeat steps 2 and 5 of Part I (overwriting /Volumes/EFI/EFI/OC and /Volumes/EFI/EFI/BOOT) and (if applicable) repeat Part II. To facilitate the process, @TECK has developed a nifty script, which you can adapt to your configuration. This tool is especially useful for advanced configurations.
Disabling OpenCore
Open the configuration file

• Open Terminal
• Find the EFI volume of Disk A by entering: diskutil list

• Mount the EFI volume by entering: sudo diskutil mount /dev/diskAs1
• Navigate to /Volumes/EFI/EFI/OC and copy config.plist to your home folder
• Open config.plist in your home folder with TextEdit

Turn off boot selection routing

• Find RequestBootVarRouting and change true to false

Load the configuration

• Close config.plist and copy it back to /Volumes/EFI/EFI/OC
• Reboot

Select Mojave and reboot

• Select Mojave in System Preferences > Startup Disk
• Reboot

Reenabling OpenCore
Open the configuration file

• Open Terminal
• Find the EFI volume of Disk A by entering: diskutil list

• Mount the EFI volume by entering: sudo diskutil mount /dev/diskAs1
• Navigate to /Volumes/EFI/EFI/OC and copy config.plist to your home folder
• Open config.plist in your home folder with TextEdit

Turn on boot selection routing

• Find RequestBootVarRouting and change false to true

Repeat the first-boot stepsUninstalling OpenCore
Disable OpenCoreDelete the files

• Open Terminal
• Find the EFI volume of Disk A by entering: diskutil list

• Mount the EFI volume by entering: sudo diskutil mount /dev/diskAs1

• Delete /Volumes/EFI/EFI/OC and /Volumes/EFI/EFI/BOOT

Installing Windows 10
You will need:Prepare two disks as follows:Disk CUSBAdd the exFat driver

• Open Terminal
• Find the EFI volume of Disk A by entering: diskutil list

• Mount the EFI volume by entering: sudo diskutil mount /dev/diskAs1

• Copy OcBinaryData/Drivers/ExFatDxeLegacy.efi to EFI/OC/Drivers

Open the configuration file

• Navigate to /Volumes/EFI/EFI/OC and copy config.plist to your home folder
• Open config.plist in your home folder with TextEdit

Tell OpenCore about the driver

• Find the Drivers key and add

Verify the configuration

• Close config.plist
• In Terminal, enter: plutil -convert xml1 config.plist && plutil config.plist

You should see config.plist: OK. If not, recheck all the steps.
Load the configuration

• Copy config.plist back to /Volumes/EFI/EFI/OC
• Reboot

Prepare the installer

• Enter: rsync -r /Volumes/CCCOMA_X64/ /Volumes/USB

Proceed with the installation

• Reboot and select Windows (External) from the boot picker

• At the Windows Setup window, press Shift+F10 to open the Command Prompt
• Start diskpart by entering: diskpart

• Identify your disks by entering: list volume

• Select Disk C by entering: select volume 1

• Format the disk by entering: format quick fs=ntfs label=Windows

• Enter: exit

• Enter: D:
• Backup the efi folder of the installer by entering: ren efi efi.bak
• Enter: cd sources
• Identify the version of Windows that you want to install by entering: dism /get-wiminfo /wimfile:install.wim

• Apply the install image by entering: dism /apply-image /imagefile:install.wim /index:1 /applydir:C: /compact /EA

• Create the boot files by entering:bcdboot C:Windows /s D: /f uefi

• Enter: exit
• Close the Windows Setup window (click the X)

• Reboot into macOS

Copy the boot files

• Open Terminal
• Find the EFI volume of Disk C by entering: diskutil list

• Mount the EFI volume by entering: sudo diskutil mount /dev/diskCs1

• Copy /USB/EFI/Microsoft to /Volumes/EFI/EFI
• Delete /USB/EFI and rename efi.bak to efi
• Eject the USB

Finish the installation

• Reboot and use the boot picker to select Windows

• Complete the configuration

Acknowledgements
A big thank you to @vit9696 and the other talented developers of Acidanthera for making all of this possible. Special gratitude goes to @h9826790 for spearheading the hardware acceleration study and @startergo for the relentless testing that led to boot screen support. And thanks to all those that have contributed to this thread!

Install Opencore Mac Pro 5 11

猜你喜欢

• 7

  Mac Pro 3,1, A1186, EMC21331149TMmacrumors mem...

• 1

  MP 1,1-5,1 Mac Pro and Thunderbolt Display ?!?F

• 2

  Resolved Mac Pro 1,1 Firmware upgrade issuesC...

• 0

  Mac Pro 5,1 Randomly Freezing and CrashingCConradish...

• 1

  Bring an old Mac Pro 4.1 to lifeKKostaskmacrumor...

• 0

  12 Pro stutter when closing apps W

• 6

  rogue (?) pixels in iPad Pro 12.9 2020joseleo90macrumors newbieOriginal poster

• 2

  12 Pro Max overheating shooting HDR 4K 60fps videoDDexBe...

• 1

  iPhone 12 Pro Downgrade from 12 pro to 12?H

• 5

  iPad Pro 12.9 in iPad Pro or wait for 2021 upgrade?

Install Opencore Mac Pro 5 10

关于极客头条