This topic is now closed to further replies.
Recently Browsing 0 members
No registered users viewing this page.
Hi, I'm having trouble with installing Catalina with OpenCore. The installer has started, progressed for half an hour or so and rebooted the machine. Then in OpenCore menu a new item, referring to my hard drive, has appeared so I've selected it. After displaying a lot of logs (most kexts I'm using is in debug mode), typical Apple's loading bar appears - black screen, white apple, empty loading bar underneath. And it hangs at this place forever. Any ideas what it might be?
My config is: i7-4770K, Asus Gryphon Z87 mobo, Intel HD4600 iGPU.
It's been known that there is indeed support for VGA in Coffe Lake and that support for prior iGPUs was deprecated as the VGA port was removed since Sierra. However, using port patches in Devices Properties (Open Core), I made the VGA port to work again with graphics acceleration.
But there's a catch, the port is glitchy. Once macOS displays the accounts, you can see the Enter Password box with the blur effect. But after some seconds, the whole display will turn to another color (depends on the background). I'm not sure why that happens.
I would suggest learning what are Ports, Connectors, Indexes, Types, and BusIDs before continuing, otherwise, you would get lost.
These are the patches that are supposed to enable the VGA port according to the Whatevergreen Intel guide:
06020000 02000000 30000000 // Option 1 06020000 01000000 30000000 // Option 2 None of those ports seem to work. The first problem is that the Index is 6, which does not make any sense as the Azul framebuffer only supports up to 3 Indexes (software ports). So we first have to change the Index for the VGA port on your motherboard, which is 2 (physical port is 0x06)) for me.
So that means that the target port is the Index 2, which is 02040A00 00040000 87000000.
bus-id 4 is for DP so we would change that to 2, which is VGA. That is according to what Hackintool says. I also proved other bus-ids but none of the other ones seem to work.
I have no idea what pipe does so I just type zeros.
I think pipe is basically another way group ports. So later I changed that to 10, which is 0A in hex. That means pipe remains the same as it was originally. 02020A00 01000000 87000000
The next part is the connector-type, for which I used 02000000.
I tried the VGA connector-types that Hackintool suggested but I noted some weird differences whereas 02000000 and 01000000 seem to work okay.
Finally, I don't know what flags do so I tried with 30000000 and 87000000. The only difference is that with 87000000 I'd gain more seconds before the whole screen turns to another color.
This is the final configuration:
AAPL,ig-platform-id <0300220D> framebuffer-con1-alldata <02020A00 0100000 87000000> framebuffer-con1-enable <01000000> framebuffer-patch-enable <01000000> This is the video proof:
macOS Catalina 10.15.3
Kexts: Whatevergreen 1.3.7
Boot loader: OpenCore 0.5.6
Intel Core i5 4460
Intel HD Graphics 4600
4GB RAM DDR3
How to build your own Mac Pro based on Broadwell-E/EP, Haswell-E/EP and X99 [Successful Build/Extended Guide]By KGP-iMacPro
Up and successfully running Broadwell-E/X99 with macOS High Sierra 10.13.3 SA (17D102)!
Abstract and Introduction:
This Broadwell-E/EP, Hasell-E/EP, X99 Build and macOS High Sierra 10.13 Desktop User Guide is the logical continuation of my Broadwell-E/EP, Hasell-E/EP, X99 Build and macOS Sierra 10.12 Desktop User Guide. At the same time if is my last guide based on Broadwell-E/EP, Hasell-E/EP, X99 systems. Note that just recently, I released my brand new iMacPro Skylake-X/X299 Build and macOS High Sierra 10.13 Desktop Guide to live already now the future.
This guide might still marginally grow thanks to your estimated and appreciated user feedback. However, it is nice to see that my X99 system behaves absolutely stable and is fully functional, including native Handoff and Airdrop and even forced Sleep/Wake functionality. Many thanks to @DSM2 for his collaboration and important contribution to the initial Broadwell-E/X99 macOS High Sierra 10.13 system setup.
Let me first briefly summarize my actual build, which constitutes the base for this macOS High Sierra Desktop Guide. Note however that like in case of 10.12 macOS Sierra, there should be also compatibility of my guide with all Broadwell-E/EP and Haswell-E processors and most X99 mobos (ASUS, GYGABYTE, ASRock, MSI etc.). During the last months, I received even success feedback of users with Broadwell-EP/Haswell-EP processers with up to 22 cores (44 threads) at clock speeds around 2.8 Ghz each thread, making X99 to a "realtively cheap" alternative to iMac Pro Systems.
Before starting with all detailed instructions, please find a Table of Content that provides an overview of the individual topics addressed within this guide:
Table of Contents:
A.) Hardware Summary
B.) Mainboard BIOS
B.1) ASUS BIOS Firmware Patching
B.2) ASUS X99-A II BIOS Configuration
C.) Important General Note/ Advice and Error Prevention
D.) MacPro macOS 10.13 High Sierra System Setup
D.1) MacPro EFI-Folder Preparation
D.2) MacPro macOS High Sierra 10.13.3 (17D47) Installer Download Procedure
D.3) MacPro macOS High Sierra 10.13.3 (17D47) USB Flash Drive Installer Creation
D.4) macPro macOS High Sierra 10.13.3 (17D47) Clean Install on Broadwell-E/EP/Haswell-E/EP X99
D.5) MacOS High Sierra Update from earlier macOS distributions as well as future MacPro macOS High Sierra Update Procedures
E.) Post Installation Process
E.1) Graphics Configuration
E.2) Audio Configuration
E.3) USB Configuration
E.4) M.2/NVMe Configuration
E.5) SSDT TRIM Support
E.6) Xnu CPU Power Management (XCPM) Configuration
E.7) Enhanced Intel SpeedStep Technology (EIST) and PMDrvr.kext
E.9) ASUS X99-A II PCI Deice Implementation - Sleep/Wake Functionality
E.9.1) ACPI DSDT Replacement Patching Table Implementation
E.9.2) SSDT-ASUS-X99-A-II.aml PCI Implementation
E.9.2.1) HDEF - onboard Audio Controller PCI Implementation
E.9.2.2) GFX1, HDAU - Nvidia Graphics Card and HDMI/DP Audio PCI Implementation
E.9.2.3) IMEI - onboard Intel Management Engine Interface (IMEI) Controller PCI Implementation
E.9.2.4) Glan - onboard LAN Controller PCI Implementation
E.9.2.5) XHCI - onboard Extended Host Controller Interface (XHCI) PCI Implementation
E.9.2.6) ASMedia ASM1142 USB3.1 Controller PCI Implementation
E.9.2.7) SAT1 - Intel AHCI SATA Controller PCI Implementation
E.9.2.8) EVVS - Intel X99 sSata Controller PCI Implementation
E.9.2.9) NVMe Controller PCI Implementation
E.9.2.10) Inateck KTU3FR-502U XHC 7-Port USB 3.0 Controller PCI Implementation
E.9.2.11) ARPT - OSX WIFI Broadcom BCM94360CD 802.11 a/b/g/n/ac + Bluetooth 4.0 AirPort Controller PCI Implementation
E.9.2.12) ThunderboltEX 3 Controller Implementation
E.9.2.13) DTGP Method
E.10) Hardware Monitoring
E.11) System Overview CPU Cosmetics
F.1) i7-6950X CPU Benchmarks
F.2) Gigabyte AORUS GTX 1080 Ti 11GB Xterme Edition OpenGL and Metal Benchmarks
F.3) Blackmagic Disk Speed Benchmarks
G.) Summary and Conclusion
Now enjoy and have have fun with the detailed guidelines below.
A.) Hardware Summary
Motherboard: Asus X99-A II
CPU: I7-6950X (10-core) RAM: 128 KIT (8X16GB) G.Skill TridentZ (F4-3200C14Q2-128GTZSW) System Disk: Samsung 850 EVO 1TB (SSD) / Samsung 960 EVO 1TB (NVMe, M.2) RAID: 3x Western Digital Red Pro 6TB (18TB); Graphics: Gigabyte AORUS GeForce® GTX 1080 Ti Xtreme Edition 11G (GV-N108TAORUS X-11GD) Wifi + Bluetooth: OSXWIFI PC/Hackintosh - Apple Broadcom Bcm9436cd - 802.11 A/B/G/N/AC +Bluetooth 4.0 PCIe Power Supply: Corsair AX860 CPU Cooler: Corsair H80i v2 Webcam: Logitech HD Pro WebCam C930 Monitor: LG 38UC99-W, 38", WQHD, 21:9, 3840x1600 pixel, 75 Hz. Case: Corsair CC600TWM-WHT, Graphite Series 600T, Mid Tower Keyboard: Logitech K811 Mouse: Logitech Ultra-Thin Touch Mouse T631 Blu-Ray/DVD Writer: LG Super Multi Blue BH16 (BH16NS55)
B.) ASUS Mainboard BIOS
Please find below a detailed instruction for ASUS X99 mainboard BIOS Firmware patching, as well as a summary of my actual Asus X99-A II BIOS configuration.
B1.) ASUS Mainboard BIOS Patching
On a real Mac with native OSX XCPM power management, the MSR 0xE2 register is unlocked and therefore writeable. However, on ASUS mobos this register is usually read only. This is also the case for all ASUS X99 mobos. When the kernel tries to write to this locked register, it causes a kernel panic. This panic can happen very early in the boot process, with the result that your system freezes or reboots during the boot process. We can circumvent the MSR 0xE2 register write with a dedicated KernelToPatch entry in the config.plist, namely "xcpm_core_scope_msrs © Pike R. Alpha" and by enabling the "KernelPM" in the config.plist in Section "Kernel and Kext Patches" of the Clover Configurator. See Section E.1) for further details.
However, thanks to CodeRush's Longsoft UEFIPatch distribution and sophisticated MSR 0xE2 Register patches, we are able to successfully patch any ASUS X99 mainboard BIOS distribution and unlock the MSR 0xE2 register. This makes the "xcpm_core_scope_msrs © Pike R. Alpha" KernelToPatch entry obsolete and allows full native read/write MSR 0xE2 register access by the OSX kernel. The patched ASUS mainboard BIOS firmware finally can be uploaded each specific ASUS X99 mainboard by means of the ASUS EZ BIOS Flashback Procedure.
The individual steps for the ASUS X99 BIOS Patching are detailed below:
1.) Download and unzip the CodeRush's UEFI patch to your Desktop.
2.) To patch the latest BIOS for your ASUS mobo, download the most actual BIOS version from the ASUS mobo support page (e.g., follow the subsequent link to obtain the latest BIOS Version for the Asus X99-A II).
3.) Unzip the bios file and copy the CAP file into the UEFIPatch directory on your Desktop.
4.) Open a terminal; type "cd " and drag the "UEFIPatch"-folder on your Desktop into the Terminal window and press "Enter". One can also use the terminal command equivalent:
cd ~/Desktop/UEFIPatch_0.3.9_osx/ Note that this step is important to successfully execute the UEFI-Patch procedure! You must be in the UEFIPatch directory on your terminal, in order to successfully execute step 5.) below!
Once in the UEFIPatch directory on your terminal, drop the "UEFIPatch"-executable into the terminal window; Also drop the most actual BIOS CAP file into the terminal window; Press enter to execute the "UEFIPatch"-procedure. The equivalent terminal command is:
./UEFIPatch X99-A-II-ASUS-1701.CAP by assuming that you want to patch the latest X99-A-II-ASUS-1701.CAP BIOS-files for the ASUS X99-A II. For other mobos, please adapt the adequate BIOS CAP-filename in the command!
During the patch procedure, you will see something like the following message, which can be simply ignored:
parseImageFile: Aptio capsule signature may become invalid after image modifications parseSection: section with unknown type 52h parseFile: non-empty pad-file contents will be destroyed after volume modifications parseSection: section with unknown type 52h parseFile: non-empty pad-file contents will be destroyed after volume modifications patch: replaced 6 bytes at offset F69h 0FBA6C24400F -> 0FBA7424400F Image patched 6.) You will now find a ***.CAP.patched BIOS-file in the UEFIPatch folder, which is your patched (MSR 0xE2 unlocked) BIOS file.
7.) Rename the ***.CAP.patched BIOS file to X99A2.CAP, the required filename for the ASUS X99-A II BIOS Flashback procedure. Note that the required filename varies for each ASUS mobo. For details see the ASUS BIOS Flashback filename convention.
8.) Copy the X99A2.CAP (or it's derivative in case you use a different ASUS mobo) to a FAT-formatted USB2.0 storage device.
9.) Shut-down your hack, connect the USB2.0 storage device to the USB-port assigned to the ASUS BIOS Flashback procedure (see the mobo manual for details). Press the BIOS-Flashback button for three seconds until the flashback-led starts to blink, indicating that the BIOS Flashback is in progress. Release the button. The locations of the BIOS-Flashback button and the USB-port assigned to the BIOS-Flashback procedure on the ASUS X99-A II are indicated in the figure below:
10.) Wait until the Flashback-led stops blinking and turns off, indicating that the BIOS Flashback process as been successfully completed. You now successfully installed the most actual patched BIOS, compatible with native OSX/MacOS power management. 11.) Boot your system and apply the BIOS settings described below. B2.) ASUS X99-A II BIOS Configuration Please find below a summary of the most important BIOS settings for the ASZS X99-A II.
To overclock your RAM memory in concordance with your RAM specifications, enable the EZ XMP Switch on your ASUS Mainboard and enable posteriorly XMP in the Standard ASUS BIOS Setup mode (F7). Subsequently switch from standard to advanced ASUS BIOS Setup mode by pressing again F7.
Press F7 and subsequently F10 key to change to "Standard Mode", Save and Reboot Important Note: "ASUS MultiCore Enhancement": When set to "Auto", MCE allows you to maximise the overclocking performance optimised by the ASUS core ratio settings. When disabled, MCE allows to set to default core ratio settings. "Sync All Cores": Tremendous increase in CPU performance can be achieved with the CPU Core Ratio set to "Sync All Cores". In case of my i9-7980XE, the Geekbench score difference is approx. 51.000 (disabled) compared to 58.000 (enabled)! Note however, that Sync All Cores should be used only in case of the availability of an excellent and extremely sophisticated water cooling system! Otherwise, CPU Core Ratio should be set to "Auto". Further note that with CPU Core Ratio set to "Sync All Cores", the AVX Instruction Core Ratio Negative Offset must be set to "3" and the AVX-512 Instruction Core Ratio Negative Offset must be set to "2". Without the correct core ratio offsets, your system might become unstable with CPU Core Ratio set to "Sync All Cores"! VT-d Note: For compatibility with VM or parallels, VT-d can be also ENABLED... Verify however, in this case that in your config.plist the boot flag "dart=0" is checked under Arguments in the "Boot" Section of Clover Configurator! The boot flag "dart=0" is now implemented by default in config.plist of the EFI-Folder contained in EFI-X99-10.13.3-SA-Release-020318.zip in line with the boot flag implementation "slide=0". Above 4G Decoding Note: I always assumed that the latter BIOS functionality would be mandatory for successfully operating the ThunderboltEX 3 PCie adaptor. This is definitely not the case. Thus in contrary to the BIOS Settings Table above I now rather recommend to DISABLE the latter BIOS functionality (Above 4G Decoding: off), as it also seems to affect the system sleep/wake functionality when enabled.
C.) Important General Note/Advice and Error Prevention
Please note the following important General Note / Advice and Error Prevention, when setting up your X99 System by implementing the latest macOS High Sierra 10.13 distribution.
Before entering the detailed description of the individual System Upgrade Options from previous versions of macOS High Sierra 10.13 or the Clean Install of macOS High Sierra 10.13.3 (17D47), please consider the following error prevention. 1.) Note that the /EFI/Clover/drivers64UEFI/-directory of EFI-X99-10.13.3-SA-Release-020318.zip implements a totally new approach, namely AptioMemoryFix.efi developed by @vit9696, which successfully replaces OsxAptioFix2Drv-free2000.efi. Note that AptioMemoryFix.efi is under permanent development. For further details and to access the ongoing discussion to the topic follow THIS LINK. To retrieve the most actual version, download and compile the AptioMemoryFix.efi Source Code from Github by means of AptioMemory-Builder.sh developed by @Pavo, using the following terminal commands: rm -rf AptioMemFix git clone https://github.com/Pavo-IM/AptioMemFix rm -rf ~/Desktop/AptioMemFix/ rm -rf ~/Desktop/AptioFix/ mv AptioMemFix/ ~/Desktop/ chmod +x ~/Desktop/AptioMemFix/AptioMemory_Builder.sh ~/Desktop/AptioMemFix/AptioMemory_Builder.sh This will create "AptioFix" and "AptioFix_Build" folders on your Desktop. Now you can copy the most actual compiled AptioMemoryFix.efi release from ~/Desktop/AptioFix_Build/RELEASE/ to the /EFI/Clover/drivers64UEFI/ directories in the EFI-Folders of your macOS USB Flash Drive Installer and macOS System Disk. Don't forget to remove OsxAptioFix2Drv-free2000.efi from the /EFI/Clover/drivers64UEFI/ directories in the EFI-Folders of your macOS USB Flash Drive Installer and macOS System Disk. For further details and to access the ongoing discussion to the topic follow THIS LINK. AptioMemoryFix.efi works absolutely flawless on my system, without any memory allocation errors or slide issues with the "slide" boot flag disabled. Note that also with AptioMemoryFix.efi, Clover's RC Scripts have to be omitted during the clover boot loader installation. If already previously installed, remove Clover's RC Scripts from the /etc directory of your macOS USB Flash Drive Installer or System Disk with the following terminal commands: sudo rm -rf /etc/rc.boot.d sudo rm -rf /etc/rc.shutdown.d sudo rm -rf /etc/rc.boot.d sudo rm -rf /etc/rc.shutdown.d 2.) a.) All ATI Graphics Cards Users with typical rudimentary and basic Starter ATI Graphics Cards like the ATI Radeon RX 560 or RX 580 should use WhateverGreen.kext v1.1.4. and Lilu.kext v1.2.2.
Not however, that all ATI Vega 64 and Frontier GPUs are natively implemented by OSX and run Out of Box (OoB). No need for the additional Whatevergreen.kext and Lilu.kext implementation. b.) All Nvidia Graphics Cards Users with SMBIOS MacPro6,1 can employ the officially distributed Nvidia 10.13 Web Drivers for their Nvidia Pascal and Maxwell graphics cards! Nvidia Kepler Cards were anyway already natively implemented in the earlier beta distributions of macOS 10.13. For further details and error prevention see Section E.1). 3.) Avoid any MacOS assignments in KextToPatch and KernelToPatch entries implemented in the "Kernel and Kext Patches" Section of the Clover Configurator. If subsequently in my Guide you still find MatchOS assignments in respective figures or text, just ignore all likely yet persistent MatchOS assignments. In the config.plist of the EFI-Folder contained in EFI-X99-10.13.3-SA-Release-020318.zip, all MatchOS assignments have been definitely removed. 4.) Note that non ASUS mobo owners might have to check the "KernelPm" entry in the "Kernel and Kext Patches" Section of the Clove Configurator to successfully boot the 10.13 MacOS USB Flash Drive Installer or 10.13 System Disk! However, this entry is currently unchecked in the config.plist of the EFI-Folder contained in EFI-X99-10.13.3-SA-Release-020318.zip for all ASUS boarders.
5.) Always check that you have the actual apfs.efi in the /EFI/CLOVER/drivers64UEFI/ - directory of your USB Flash Drive Installer and System Disk!
The actual apfs.efi can be obtained by following the respective guideline detailed below: a.) Download and install Pacifist for Mac. b.) Copy the "Install macOS High Sierra.app" to your Desktop -> right-click with your mouse on the app and select "Show Package Contents" -> click with the mouse on "Contents" and subsequently on "Shared Support" -> right-click with the mouse on "BaseSystem.dmg" and select "Open With" -> select "pacifist.app". Pacifist is now loading the "BaseSystem.dmg" package contents. c.) Now click with the mouse on "usr" -> "standalone" -> "i386". After a right-click on apfs.efi, select "Extract to Custom Location...". Choose your Desktop as Destination. Answer the subsequent question "Extract apfs.efi ?" with "Extract". You now have the most actual version of apfs.efi on your Desktop. d.) Note that the EFI-Folder EFI-X99-10.13.3-SA-Release-030218.zip contains a patched apsf.efi without verbose boot. The respective patching procedure and the related discussion can be derived by following THIS LINK. Credits to PMheart and ErmaC from InsanelyMac. e.) If necessary (usually the /EFI/CLOVER/drivers64UEFI/ - directory of my distributed EFI-Folders already containsthe most actual apfs.efi version), copy the actual patched apfs.efi to the /EFI/CLOVER/drivers64UEFI/ - directories of your USB Flash Drive Installer and System Disk! 6.) To avoid boot problems and for sleep/wake functionality, it is absolute mandatory to have VoodooTSCSync.kext in the /EFI/CLOVER/kexts/Other/ directory of both USB Flash Drive and System Disk. Please note that the linked VoodooTSCSync.kext.zip is configured for a 10-core CPU (12 threads) like the i7-6950X. To adopt the kext for Skylake-X processers with more or less than 10 cores, apply the following approach: a.) Download and unzip the linked VoodooTSCSync.kext.zip to your desktop. b.) Right-click with the mouse on the VoodooTSCSync.kext file and select "Show Packet Contents". c.) Double-click with the mouse on /contents/ . After a right-click on the "Info.plist" file, select "Open with / Other". Select the TextEdit.app and edit the "Info.plist" file. d.) Use the "find"-function of TextEdit.app and search for the term "IOCPUNumber" e.) Note that the adequate IOCPUNumber for your particular Skylake-X processor is the number of its threads -1, by always keeping in mind that the number of it's threads is always 2x the number of it's cores. Thus in case of the 10 core i7-6950X, the IOCPUNumber is 19 (20 threads - 1). <key>IOCPUNumber</key> <integer>19</integer> By following this methodology, the correct IOCPUNumber for the 8-core i7-6900K would be (16 threads -1) <key>IOCPUNumber</key> <integer>15</integer> and the IOCPUNumber for the 6-core i7-6800K would result in (12 threads -1) <key>IOCPUNumber</key> <integer>11</integer> f.) After adopting the IOCPUNumber for your particular Skylake-X processor, save the info.plist file and copy the modified VoodooTSCSync.kext to the /EFI/CLOVER/kexts/Other/ - directories of both USB Flash Drive Installer and System Disk! 7.) Already during the last Beta Versions of macOS 10.13 High Sierra, Apple forced the beta users to use the new Apple file system APFS in case of a Clean Install/update of MacOS High Sierra 10.13. Also within macOS High Sierra 10.13.3 SA (17D102) this is the case. Most APSF incompatibilities with available system related software apparently have been already removed. The actual version of Carbon Copy Cloner (CCC) now supports the direct cloning of APFS system disks and hereby enables the previously missing option for APFS system backups. Until Boot-Loader Distribution Clover_v2.4k_r4210, it was also impossible to install the Clover Boot-Loader in the EFI-Partition of an APFS System Disk by means of the Clover Boot-Loader Installer Package. However, with any actual Clover Boot-Loader Distribution, the Clover Boot-Loader Installation works absolutely flawless on APFS System Disks. Note that there is no way to convert an APFS disk back to HFS+ without the loss of all data, but one can easily reformat an APFS formatted disk to HFS+ under OSX by using either Apple's Disk Utility App or "diskutil" commands. All you need to do is to previously unmount the APFS volume before erasing it with a journaled HFS+ file system and a GRUB Partition Table (GTP). If you want to maintain the disk's content, perform a backup before erasing the disk with a HFS+ format. The application of Apple's Disk utility is straight forward. The "diskutil" equivalent is detailed below: In the Terminal app, type: diskutil list In the output which you can read by scrolling back, you will find all internal disks named /dev/disk0, /dev/disk1, depending upon how many physical disks are present in your system.
Make a note of the disk identifier for the disk you intend to format (you can eliminate risk by removing all disks but the intended target). In the Terminal app, type: diskutil unmount /dev/diskX where diskX is a place holder for the disk to be unmounted.
Subsequently, you can erase the entire disk with HFS+ and a GPT by typing the following terminal command: diskutil partitionDisk /dev/diskX 1 GPT jhfs+ "iMacPro" R where /dev/diskX is again a place holder for disk to be erased and iMacPro would be the label for the single partition created. The remaining 1 GPT jhfs+ and R arguments tell diskutil to create a single partition, within a GUID partition table, formatted as Journaled HFS+ and using the entire disk, respectively.
Alternatively one can also use the following terminal command: diskutil partitionDisk /dev/diskX GPT JHFS+ iMacPro 0b where /dev/diskX is again a place holder for disk to be erased and iMacPro is again the label for the disk partition created. The GPT HFFS+ and 0b arguments again tell diskutil to create a single partition, within a GUID partition table, formatted as Journaled HFS+ and covering the entire disk, respectively.
In the Terminal app, type now: diskutil mount /dev/diskX where diskX is again a place holder for the disk to be remounted. Note, that by means of the "diskutil approach", brand new unformatted or not compatibly formatted system NVMe, SSD and HDD system drives can be also directly formatted within the macOS Clean Install procedure. When presented with the initial install screen where you are presented options to Restore From Backup or Install, select Terminal from the Utilities menu bar item;
The "diskutil" terminal approach is also able to convert a HFS+ macOS High Sierra 10.13 System Disk to APFS. To do so enter the following terminal command: diskutil apfs convert /dev/diskX where diskX is again a place holder for the HFS+ disk to be converted to APFS. The same procedure again can also be directly performed by means of Apple's Disk Utility.
If you opt for an APFS System Disk implementation, please note that all other disks on your system also should be formatted with APFS. On systems with APFS disks and non-APFS disks, the boot duration will increase, as apsf.efi will perform a fsck check of non-AFPS disks (like HFS+ or Fat32) during boot. However, dual boot APFS Systems with an NTFS Windows System Disk are not effected by the apsf.efi issue, as OSX does not know how to properly deal with NTFS.
8.) To clearly get kernel panic images with a call trace in case of kernel panics, I implemented (checked) boot flags "debug=0x100" and "keepsyms=1" in the config.plist of EFI-X99-SA-10.13.3-Release-020318.zip in the "Boot" Section of Clover Configurator under "Arguments".
9.) Note that in the current EFI-X99-10.13.3-SA-Release-020318.zip distributions, I also removed CsmVideoDxe-64.efi from /EFI/CLOVER/drivers64UEFI, as the latter file is only required for proper Legacy screen resolution purposes with CSM enabled, which is definitely not our case. D.) MacPro macOS 10.13 High Sierra System Setup Below, one finds a detailed description for the Clean Install of macOS High Sierra 10.13.3 (17D47) (D.4). This also includes the MacPro EFI-Folder Preparation (D.1) as well as the Mac Pro macOS High Sierra 10.13.3 (17D47) Full Package Download Procedure (D.2) and the Mac Pro macOS High Sierra 10.13.3 (17D47) USB Flash Drive Installer Creation (D.3). One also finds detailed instructions for the MacOS High Sierra update from earlier MacOS distributions as well as for future Mac Pro macOS High Sierra Update Procedures. D.1) MacPro EFI-Folder Preparation In order to successfully boot a macOS USB Flash Drive Installer or System Disk on a Hackintosh system, both drives must be equipped with an EFI-Folder in their EFI partitions. In this Section we will prepare a fully equipped EFI-Folder with SMBIOS MacPro6,1 System definition. 1.) Download and unzip EFI-X99-10.13.3-SA-Release-020318.zip and copy the therein contained EFI-Folder to your Desktop. 2.) Open the config.plist in /EFI/Clover/ with the latest version of Clover Configurator (>/= v.4.60.0), proceed to the "SMBIOS" Section and complete the SMBIOS MacPro6,1 Serial Number, Board Serial Number and SMUUID entries. These details are mandatory to successfully run iMessage and FaceTime on your iMac Pro System. Note that all other MacPro6,1 SMBIOS Details are already implemented in the config.plist of EFI-X99-10.13.3-SA-Release-020318.zip. In order to successfully run XCPM with Pike Alpha's ssdtPRGen.sh and ssdt.aml, you have to maintain the MacPro6,1 SMBIOS entries already implemented in the config.plist in the distributed EFI-Folder. i.) Press several times the "Generate New" Button next to serial number text field. Copy the serial number and perform the serial number check on http://www.everymac.com/ultimate-mac-lookup/ by following @P1LGRIM's related instructions in "An iDiots's Guide To iMessage". ii.) Also perform the serial number check on https://checkcoverage.apple.com by following @P1LGRIM's related instructions in "An iDiots's Guide To iMessage". If all checks have been past successfully, proceed to point iii.) below. iii.) Note that the latest versions of Clover Configurator already correctly implements the Board Serial Number in parallel. Thus one can skip the related description in@P1LGRIM's "An iDiots's Guide To iMessage" iv.) In the final step, open a terminal, enter repeatedly the command "uuidgen", and copy the output value to the SMUUID field in the "SMBIOS" Section of the Clover Configurator. 3.) Depending on your system configuration (Broadwell-E/EP or Haswell-E/EP) change or adopt the following settings if necessary: a.) CPU "TYPE" in the "CPU" Section (obsolete with properly configured XCPM): Broadwell-E/EP CPU Type: "0x0a02" Haswell-E/EP CPU Type: "0x0a01" (thanks to @nmano for his valuable feedback) b.) "FakeCPUID" in the "Kernel and Kext Patches" Section (obsolete with properly configured XCPM):
Broadwell-E/EP FakeCPUID: "0x040674" (thanks to @GDS for his valuable feedback based on his XEON e5-2696v4) Haswell-E/EP standard FakeCPUID: "0x0306F2" (thanks to @nmano and @dragoonchang for their valuable feedback) c.) "KernelToPatch" entries in the "Kernel and Kext Patches" Section:
Broadwell-E/EP "xcpm_cpuid_set_info" and "xcpm_bootstrap": Find: Replace: Comment: MatchOS: 723cd077 500fb6c0 6a3cd077 500fb6c0 xcpm_cpuid_set_info © Pike R. Alpha 10.13.x 89d804c4 3c227722 89d804c3 3c227722 xcpm_bootstrap © Pike R. Alpha 10.13.x Haswell-E/EP "xcpm_cpuid_set_info" and "xcpm_bootstrap": Find: Replace: Comment: MatchOS: 723cd077 500fb6c0 6f3cd077 500fb6c0 xcpm_cpuid_set_info © Pike R. Alpha 10.13.x 89d804c4 3c227722 89d804c1 3c227722 xcpm_bootstrap © Pike R. Alpha 10.13.x Please note that Haswell-E processors in principle do not require the patching of the switch table used by "xcpm_cpuid_set_info". Apple already took care of it. One can therefor disable the xcpm_cpuid_set_info KernelToPatch entry for the latter processor architecture. If you encounter against all expectations problems during your XCPM configuration though, use the "xcpm_cpuid_set_info" entry provided above! Note that the appropriate Xnu Cpu Power Management (XCPM) settings for each CPU architecture are once more addressed, discussed and finalized in the Xnu Cpu Power Management (XCPM) Section of this guide below. Finally save the modified config.plist. 3.) Copy the appropriate VoodooTSCSync.kext, which you modified by following error prevention C.7), to the /EFI/CLOVER/kexts/Other/ directory of the EFI-Folder. You know have a fully equipped EFI-Folder for subsequent implementations as detailed below. D.2) MacPro macOS High Sierra 10.13.3 (17D47) Installer Download Procedure
To derive the macOS 10.13.3 build 17D47 Full-Package Installer download the latter from the Mac App Store. The "Install macOS High Sierra.app" will be installed in your /Applications folder.
D.3) MacPro macOS High Sierra 10.13.3 (17D47) USB Flash Drive Installer Creation
Follow the individual steps detailed below to successfully create a bootable iMac Pro macOS High Sierra 10.13.3 (17D47) USB Flash Drive Installer.
1.) Format a USB Flash Drive of your choice (source, named USB) with HFS+ [(Mac OS Extended (Journaled)] and a GUID partition table by means of Apple's Disk Utility on any other Hackintosh or Mac of your choice. This will create an empty HFS+ Partition and a yet empty EFI-partition on your iMac Pro macOS USB Flash Drive Installer. 2.) With the iMac Pro macOS High Sierra 10.13.3 (17D47) Installer Package in your /Application Folder, connect your USB Flash Drive (named USB) and run the following terminal command: sudo /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ High\ Sierra.app --nointeraction Alternatively, one can create the iMac Pro macOS USB Flash Drive Installer also by means of the Install Disk Creator.app 4.) For successfully booting your Mac Pro macOS USB Flash Drive Installer, the latter must however also contain a valid EFI- Folder with an SMBIOS MacPro6,1 system definition. Thus, copy the EFI-Folder you prepared in Section D.1) to the yet empty EFI Partition of your Mac Pro macOS USB Flash Drive Installer. You now have a fully functional and bootable iMac Pro macOS High Sierra 10.13.3 (17D47) USB Flash Drive Installer. D.4) MacPro macOS High Sierra 10.13.3 (17D47) Clean Install on Broadwell-E/EP/Haswell-E/EP X99 Follow the individual steps detailed below to successfully setup macOS High Sierra 10.13.3 (17D47) on a virgin system drive of your choice (NVMe, SSD or HDD). 1.) In order to perform a clean install of macOS High Sierra 10.13.3 (17D47), prepare a virgin NVMe, SDD or HDD destination drive for the iMac Pro macOS installation by formatting the drive with HFS+ [(Mac OS Extended (Journaled)] and a GUID partition table by means of Apple's Disk Utility on any other Hackintosh or Mac of your choice. This will create an empty HFS+ Partition and a yet empty EFI-partition on the drive. 2.) Copy the EFI-Folder you prepared in Section D.1) to the yet empty EFI Partition. 3.) Now connect the Destination Drive to your Hackintosh System and boot the latter with the plugged Mac Pro macOS High Sierra 10.13.3 (17D47) USB Flash Drive Installer, your created in Section D.2) 4.) While booting your system, press the F8 button to enter the BIOS boot menu. Select to boot from your iMac Pro macOS USB Flash Drive Installer. 5.) Subsequently, click on the USB Flash Drive Installer Icon in the clover boot menu to boot the respective macOS Installer partition on your iMac Pro macOS USB Flash Drive Installer. 6.) After successful boot, pass the individual steps of the macOS high Sierra 10.13 installation menu and finally select the destination drive of your macOS High Sierra 10.13 Installation, which should be logically the system disk you successfully configured above. In the next step, the Installer will create a macOS High Sierra 10.13 Installer Partition on the system disk and subsequently reboot your system. 7.) During system reboot, just press again the F8 button to enter the BIOS boot menu. Select again to boot from your USB Flash Drive. In contrary to 6.), click this time on the "Install MacOS.." Icon in the clover boot screen to boot the newly created macOS High Sierra 10.13 Installer Partition on your system disk. 8.)After successful boot, you will enter now the macOS High Sierra 10.13 Installer Screen with a progress bar starting at 34 minutes. 9.) After another reboot, press again the F8 button to enter the BIOS boot menu. Select to boot with your System Disk EFI-folder. Click on the "MacOS High Sierra" icon in the clover boot screen to boot the updated macOS High Sierra 10.13 partition on your system disk. 10.) After successful boot you will enter again the macOS High Sierra 10.13 Installer Screen with a progress bar starting at 18 minutes. After successfully registration at iCloud at the end of the macOS installation, you now have your first Mac Pro macOS High Sierra 10.13.3 (17D47) build. Proceed to Section E.) - Post Installation Process. D.5) macOS High Sierra Update from earlier macOS distributions as well as future MacPro macOS High Sierra Update Procedures 1.) Backup you current system disk EFI-Folder. 2.) Copy the EFI-Folder prepared in D.1) to the EFI-Partition of your System Disk 3.) If you intent to update a previous macOS High Sierra Installation, just proceed with the standard MacOS Appstore procedure, indicated by the red circle on the Appstore Icon directly from your system disk. If you intent to update from macOS Sierra 10.12.6, download the macOS High Sierra Full Package Installer as described in D.2) and double-click on the "Install MacOS High Sierra.app" in your /Applications folder. 4.) After reboot, click on the "Install MacOS.." Icon in the clover boot screen to boot the newly created macOS High Sierra 10.13 Installer Partition on your system disk. 5.) After successful boot, you will enter now the macOS High Sierra 10.13 Installer Screen with a progress bar starting at 43 minutes.
6.) After another reboot, click on the "MacOS High Sierra" icon in the clover boot screen to boot the updated macOS High Sierra 10.13 partition on your system disk.
7.) After successful boot you will enter again the macOS High Sierra 10.13 Installer Screen with a progress bar starting at 18 minutes. After successfully registration at iCloud at the end of the macOS installation, you now have your most actual Mac Pro macOS High Sierra 10.13 build. 8.) After finishing the macOS Upgrade, proceed to Section Graphics Configuration. Download and update the Nvidia 10.13 Web Driver compatible with your current macOS High Sierra 10.13 distribution. 9.) Now proceed to the Section "Xnu CPU Power Managment XCPM" below, and re-inject the frequency vector to your Mac- F60DEB81FF30ACF6.plist. Note that the latter file has been rewritten during the macOS High Sierra upgrade! If you are using EIST and PMDrvr.kext, add the latter to your EFI directory! It is not part of EFI-X99-10.13.3-SA-Release-020318.zip! You are done! The same update procedure will also apply for all future macOS High Sierra 10.13 releases. E.) Post Installation Process By following the individual steps listed below, you will gain an absolutely stable and fully functional system. E.1) Graphics Configuration ATI graphics cards startup solutions like the Gigabyte Radeon RX 560 or RX 580 just require two basic kexts in the /EFI/Clover/kexts/Other/ directory of the EFI folders on both USB Flash Drive Installer and 10.13 System Disk , i.e. namely the Whate