Recently Browsing 1 member
After using my old Dell Clover convert for a few years, I recently built a new Catalina box using OpenCore. Everything works perfectly and has been very stable. The only thing that is not working is unlocking with my Apple Watch. The screen says "Unlocking with Apple Watch" with the spinning graphic and then just prompts for my password. It does not shake or anything as if the password is incorrect. My 2014 MBP unlocks without issue and they both use the same iCloud account. I purchased the Fenvi FV-T919 pci-e adapter and BT, WIFI, Handoff, and Airdrop are all working without issue. I confirmed in system preferences that unlock is supported and made sure that automatic login is disabled in my profile. I have cleared keys out of the keystore, restarted a number of times, logged out and back into iCloud all to no avail. Anyone else having this issue? Thanks in advance!!
More info my build:
Asus PRIME z370-A II
Core i7 9700K
32 GB PC3200 Crucial Ballistix RAM
Sapphire Pulse RX380
Samsung 970 Evo Plus
2x Seagate Barracuda 4TB
CoolerMaster MasterLiquid ML240L V2
I have been trying to install Big sur on Opencore and i believe i'm almost there but i get stuck on a grey screen with my mouse pointer just before i can see the installer screen.
I have applied the various SSDT patches for X99. I thought that was linked to VirtualSMC which I replaced by FakeSMC but same issue. I also declared my graphic card in config.plist as i thought it could come from there but that's not the issue (Radeon RX 570).
I have been scratching my head for some time now. Any idea from anyone please.
I have attached my EFI folder and my ioreg extract. Let me know if you need anything else.
Thanks a million.
Asus X99 Deluxe
Radeon RX 570
I would appreciate your help please. Any views of what could be wrong? Thanks a lot
OpenCore 0.6.2 for X99 BIG SUR.zip
X99 iMac Pro.ioreg.zip
I have installed MacOS and Windows on the following hardware:
AMD Ryzen 7 3700X MSI B450M Mortar Max Sapphire Radeon Pulse RX 5600 XT 6G Samsung 860 QVO, 1 TB SSD (PciRoot(0x0)/Pci(0x1,0x3)/Pci(0x0,0x1)/Sata(0x5,0xFFFF,0x0)) - MacOS on this disk Kingston A2000 SSD 1TB M.2 2280 NVMe (PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,15-AD-CD-26-28-B7-26-00)) - Windows on this disk
OpenCore 0.6.1 MacOS 10.15.7 both disks GPT UEFI
Both OSs boot nicely and work as a charm when selecting either of the disks as boot disks in the BIOS.
However, trying to boot Windows 10 from the Opencore Bootmanager (no matter whether PickerMode=internal or OpenCanopy) causes a Windows Blue Screen ("SYSTEM THREAD EXCEPTION NOT HANDLED").
To be on the safe side, I have added an appropriate entry to Misc->Entries:
<key>Arguments</key> <string></string> <key>Auxiliary</key> <false/> <key>Comment</key> <string>Not signed for security reasons</string> <key>Enabled</key> <true/> <key>Name</key> <string>Windows 10</string> <key>Path</key> <string>PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,15-AD-CD-26-28-B7-26-00)/HD(1,GPT,2E9695CB-0F9A-4005-AADB-2FF9C96AD02C,0x800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi</string> It points to the Windows 10 bootmanager on the Windows disk's EFI partition.
What's wrong with that? Why does this cause a BSOD? It is not clear to me why it works when booting from BIOS but not here.
config.plist attached (but maybe it has no relevance for the problem).
OpenCore as boot manager instead of Clover on a PC with Z390 Aorus Elite motherboard, i3 9100 Coffee Lake, RX 580 graphics card and macOS Catalina, with iMac19,1 SMBIOS, with integrated graphics card enabled and not configured in the config.plist file and USB port map specific for this motherboard.
Clover and OpenCore
Today we have 2 projects to boot macOS on compatible PCs: Clover and OpenCore (OC onwards). Clover is a mature project, started in 2011 by SergeySlice, capable of booting macOS, Windows and Linux in UEFI mode; currently it seems to be a little behind OC, a recent project started in 2019 by vit9696 and Download-Fritz among others under the name Acidanthera.
Clover is easier to configure. New versions are released at the CloverHackyColor GitHub website. It has an installer package. I have used it on my Hackintosh for 5 years and so far it has worked excellent.
OC is more difficult to configure, the number of options is greater and has some new ones to learn. It is considered to be slightly faster than Clover and its ability to inject extensions or patches at boot is higher. With the added advantage that some of the solutions that have appeared recently come from OC developers so it seems that their future evolution is clearer than in the case of Clover.
I have switched from Clover to OC on my PC with Z390 Aorus Elite board, i3 9100 Coffee Lake, Radeon RX 580 graphics card and macOS Catalina. The learning curve has been steeper than in the case of Clover but, once properly configured, it works very well. The general impression is that some things require more work in OC but it also offers other possibilities that Clover lacks. Not forgetting that, to this day, OC allows to start the beta versions of macOS Big Sur but Clover is not yet capable of doing so.
Migrate from Clover to OC
The main differences are:
EFI-Clover-ACPI-patched folder is now EFI-OC-ACPI EFI-Clover-drivers-UEFI folder is now EFI-OC-Drivers EFI-Clover-kexts-Other folder is now EFI-OC-Kexts There is no EFI-Clover-Themes folder but there is an EFI-OC-Resources folder containing folders and files required to display the OC menu with graphical interface The main configuration file has the same name, config.plist, it is in EFI-OC-config.plist and its structure is different from Clover. Once this file has been built, there is a website of the OC developers (OpenCore Sanity Checker) where to check the integrity and suitability of config.plist, at least in terms of the parameters used by the OC's specific version used, at the present time it is 0.6.2 and the official site of the project is called Dortania.
Mackie100 has a program designed to configure config.plist graphically much more comfortably than in text mode, it is called OpenCore Configurator, equivalent to Clover Configurator but specific for this platform, the most recent version is 18.104.22.168 suitable for 0.6.2, I have tested it and it works very well although on the net there are comments rejecting its use and encouraging the editing of config.plist in text mode. Among its many advantages is that of checking at startup if the config.plist file, which is XML type, is well formed, which can avoid errors with messages after BIOS such as "OC: Failed to parse configuration!" since, if this file is not well constructed, OC does not start.
My Clover and OC Files
OC's ACPI folder contains the same SSDT files as Clover's patched folder:
SSDT-AWAC.aml: for errors in system clock on Z390 chipsets among others. This file is equivalent to another called SSDT-RTC0.aml, SSDT-AWAC tries to activate the old macOS compatible RTC clock and SSDT-RTC0 creates a fake compatible RTC clock if it does not exist. SSDT-PMC.aml: native NVRAM on systems that lack it, for example Z390 chipsets. It is equivalent to SSDT-NVRAM.aml, both have the same function. SSDT-USBX.aml: to get USB3 ports working at its correct power. SSDT-PLUG.aml: to configure the plugin-type=1 parameter on the first processor (power management on the CPU). SSDT-USBW.aml: to get out of sleep with a single touch instead of 2 touches on USB mouse or keyboard.
Drivers folder differs from Clover's, it contains 3 files:
HfsPlus.efi: for volumes with HFS Plus file system. It can be replaced by VBoxHfs.efi but you cannot use both at the same time. OpenCanopy.efi: allows you to have a graphical interface in OC menu. OpenRuntime.efi: required to activate NVRAM among other functions. Mandatory.
Kexts folder also keeps same extensions as in Clover:
AppleALC.kext IntelMausi.kext Lilu.kext USBMap.kext USBWakeFixup.kext VirtualSMC.kext WhateverGreen.kext XHCI-unsupported.kext.
USBMap.kext defines the mapping of USB ports for this board to not exceed the limit of 15 imposed by macOS. This extension only has an Info.plist file (Show package content-Contents) with the ports that macOS must load at startup and in the IOKitPersonalities section it must refer to the type of Mac that we have configured, for example if we have iMacPro1,1 in SMBIOS, in this section this model must also appear (in 2 different lines). By modifying this parameter we can use the same USB port map with different SMBIOS.
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <!-- (CFBundle keys) --> <key>IOKitPersonalities</key> <dict> <key>iMac19,1-XHC</key> <dict> <!-- (ports list) --> </dict> <key>model</key> <string>iMac19,1</string> </dict> </dict> <key>OSBundleRequired</key> <string>Root</string> </dict> </plist> USBWakeFixup.kext is complementary to SSDT-USBW.aml.
Resources folder contains files required for graphical interface of the OC menu. Font and Image folders are of interest. Image contains icons that OC will use to display different partitions and file systems in the boot menu. OpenCanopy.efi has a default theme but on the net there are sites with other icon themes. I like chris1111's Gold theme and it's the one included in my EFI folder (this and other themes are available at chris1111's github site).
Config.plist file differs from clover and requires specific training, these are the options I use. Remember that they are for version 0.6.2 of OC.
SSDT files are added and Quirks are left blank.
These Quirks are marked:
Blank since I have SMBIOS configured as iMacPro1,1, integrated graphics card enabled in BIOS and RX 580 card as primary, this way I have H264 and HEVC video encoding-decoding.
Kernel / Add
Kexts we have in kexts folder are added.
Kernel / Patch
3 patches are added: Hot plug SATA, Orange Desktop icons and TRIM for SSD.
Kernel / Scheme
FuzzyMatch selected. KernelArch and KernelCache in Auto.
Kernel / Quirks
These Quirks are marked:
Boot / Debug / Security tabs as in the pics.
OpenCore usually creates the required entries for this section. In case it is not, configure it as in the pics. There are 3 sections: Add, Delete and LegacySchema.
Note: csr-active-config = 67000000 equals SIP disabled. If you want to enable SIP, it must be csr-active-config = 00000000.
Here you configure SMBIOS parameters. I choose iMac19,1. Check the "Add this section to config.plist" box. At the bottom, check all boxes (Automatic, UpdateDataHub, UpdateNVRAM, UpdateSMBIOS) and in UpdateSMBIOSMode select Create.
It has 7 tabs (APFS, Audio, Drivers, Input, Output, ProtocolOverrides and ReservedMemory) that are configured as in the images (OCQuirks section included).
Note: EnableJumpstart and JumpstartHotPlug must be selected in order to boot from the recovery partition.
EFI folder attached.