Recently Browsing 0 members
No registered users viewing this page.
EDIT: MacOS Mojave 10.14 ONLY I didn’t test 10.14.1! The EFI folder is compatible with High Sierra.
Guide to installing 10.14 Mojave on a ASUS X555L
What doesn't Work:
-NVidia Web Drivers
Clover plist is downloadable in this topic.
First get a USB with 8+ GB of storage and a MacOS Mojave 10.14 installer from the AppStore.
Partition the USB in a GUID style and 2 partitions, one partition HFS+ and one partition FAT32.
In the FAT32 partition put the EFI Folder there.
On the HFS+ partition get the MacOS Mojave .app using this command:
sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/USBNAME --applicationpath /Applications/Install\ macOS\ Mojave.app --nointeraction Lets install!
Put the USB in a 3.0 port on the LEFT side of the Notebook.
In the BIOS follow the default Hackintosh settings, do NOT forget to put Memory allocation to 64MB (Otherwise you won't boot)
Boot into the Installer and install MacOS Mojave.
Boot into MacOS. Now your Graphics are working but your WiFi and Sound are not! for the WiFi follow this video:
https://www.youtube.com/watch?v=OxFsjhc-AuM Once rebooted WiFi is working!
For sound get the VooDooHDA.kext and place it into /Library/Extensions
Reboot once again and your sound is now working flawlessly!
My EFI Folder is downloadable
Up and running macOS Mojave 10.14.1 (18B75) on my Broadwell-E/X99 iMac Pro Hackintosh!
Abstract and Introduction:
This originating post constitutes an innovative and brand new iMac Pro macOS 10.14 Mojave Build and Desktop Guide for Broadwell-E/EP, Haswell-E/EP and X99, which certainly will further grow not only thanks to your estimated feedback and contributions. It is the logical continuation of my successful iMac Pro Broadwell-E/EP, Haswell-E/EP and X99 Build and Desktop Guide published for macOS High Sierra 10.13 in the other forum. Being an iMac Pro Desktop Guide, it has also large similarities with my Skylake-X/X299 iMac Pro macOS 10.14 Mojave Desktop Guide. However, to avoid jumping back and forth, I will make this guide as consistent as the other, which however implies also some redundancy.
As everybody already might know, my Broadwell-E/EP, Haswell-E/EP and X99 Desktop Guides base on the ASUS X99-A II. However, also other X99 ASUS mainboard models or X99 mainboards of other brands might be compatible after likely considering and implementing few mandatory modifications. The same states for guide compatibility with all Broadwell-E/EP and Haswell-E/EP CPUs different form the i7-6950X employed here.
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.) ASUS Mainboard BIOS B.1) ASUS BIOS Firmware Patching B.1.1) CPU Microcode Update B.1.2) MSR 0xE2 register unlock for OSX Kernel Write B.2) ASUS X99-A II BIOS Configuration C.) Important General Note/ Advice and Error Prevention D.) iMac Pro macOS 10.14 Mojave System Setup This chapter includes a general guideline how to perform the initial setup of a Broadwell-E/EP, Haswell-E/EP, X99 iMac Pro with macOS Mojave DP1 (18A293u). D.1) iMac Pro EFI-Folder Preparation D.2) iMac Pro macOS Mojave Installer Package Creation D.3) iMac macOS Mojave USB Flash Drive Installer Creation D.4) iMac Pro macOS Mojave Clean Install on Broadwell-E/EP, Haswell-E/EP, X99 D.5) Direct iMac Pro conversion of a functional Broadwell-E/EP, Haswell-E/EP, X99 system with a SMBIOS System Definition different from iMac Pro1,1 and a standard macOS build implementation. D.6) iMac Pro macOS High Sierra Build Update Procedure E.) Post Installation Process E.1) Xnu CPU Power Management (XCPM) Configuration E.2) Graphics Configuration E.3) Audio Configuration E.4) USB Configuration E.5) M.2/NVMe Configuration E.6) SSD/NVMe TRIM Support E.7) GC-Titan Ridge / GC-Alpine Ridge /Asus TBEX 3 PCIe Add-In Implementation E.8) Gbit and 10-Gbit Ethernet Implementations E.8.1) ASUS X99-A II on-board Gbit Ethernet Functionality E.8.2) 10-Gbit LAN Implementations E.8.2.1) ASUS XG-C100C Aquantia AQC107 10-Gbit NIC E.8.2.2) Intel X540-T1 10-Gbit NIC E.8.2.3) Small-Tree P2EI0G-2T 10-Gbit NIC E.8.2.4) NetGear ProSave XS508M 8-port 10-Gbit Switch E.8.2.5) QNAP TS-431X2 Quad-core 4-Bay NAS tower E.8.2.6) 10-GBit Ethernet Optimisation E.9) ASUS X99-A II PCI Device Implementation E.9.1) ACPI DSDT Replacement Implementation E.9.2) System SSDT PCI Device Implementation E.9.2.1) HDEF - onboard Audio Controller PCI Implementation E.9.2.2) GFX0, HDAU - GPU and HDMI/DP Audio PCI implementation E.9.2.3) XGBE - 10GBit NIC PCI Implementation: E.9.2.4) ETH0 - onboard LAN Controller PCI Implementation E.9.2.5) SAT1 - Intel AHCI SATA Controller PCI Implementation E.9.2.6) EVSS - Intel X99 sSata Controller PCI Implementation E.9.2.7) ANS1 - NVMe Controller PCI Implementation E.9.2.8) - USBX: E.9.2.9) XHCI - onboard Extended Host Controller Interface (XHCI) PCI Implementation E.9.2.10) XHC2 - ASMedia ASM1142 USB 3.1 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) GC-Titan Ridge / GC-Alpine Ridge / Asus TBEX 3 Thunderbolt HotPlug System Implementation E.9.2.13) DTGP Method E.9.2.14) - Debugging Sleep Issues E.10) iMac Pro Boot Splash Screen Cosmetics E.11) iMac Pro Desktop Background cosmetics E.12) iStatMenus Hardware Monitoring F.) Benchmarking F.1) i7-6950X CPU Benchmarks F.2) Sapphire Nitro+ Radeon RX Vega 64 8GB OpenGL and Metal Benchmarks G.) Summary and Conclusion -------------------------------------------------------------------------------------------------------------- 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: Sapphire Nitro+ Radeon RX Vega 64 8GB Thunderbolt 3 Add-in: GC-Titane Ridge 40GB/s Intel Thunderbolt 3 Certified Add-in PCIe Adaptor 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) Thunderbolt: ASUS TBEX 3 and Gigabyte Alpine Ridge 10Gbit Ethernet components: - 1x ASUS XG-C100C AQC107 PCIe x4 10GBit LAN Adapter (for testing purposes) - 1x Intel X540-T1 single port 10GBit LAN PCIe Adapter (for testing purposes, now installed in my X99 rig) - 1x Small-Tree P2EI0G-2T 2-Port 10GBit LAN PCIe Adapter (now default configuration) - 1x NetGear ProSave XS508M 8-port 10GBit switch - 1x QNAP TS-431X2 Quad-core 4-Bay NAS tower with Built-in 10GbE SFP+ Port and 4x 12 TB Seagate IronWolf in RAID 0 configuration. Let me express my gratitude to @gxsolace at this place for providing me with 1x Intel X540-T1, 1x Small-tree P2EI0G-2T and 4x 12 TB Seagate IronWolf hardware. 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 settings. B.1) Asus Mainboard BIOS Firmware Patching B.1.1) CPU Microcode Update Not every BIOS firmware provided by the different Mainbaord manufacturers always accounts for all CPU microcodes distributed by Intel. Recently we witnessed for instance along the latest macOS 10.13 High Sierra distributions and even during the first macOS Mojave 10.14 distribution a Broadwell/Haswell CPU performance issue (no overclocking) in combination with most X99 mainboard implementations to be traced back a missing Intel CPU microcode implementation in most of the distributed Mainbaord BIOS firmwares. To overcome the OC issue, an Intel CPU microcode update within the respective BIOS firmware distributions is absolutely vital and mandatory. How to perform the Intel CPU microcode update for a given BIOS firmware distribution e.g. under Windows 10 is detailed below for the ASUS X99-A II 1902 BIOS firmware distribution. The same approach, initially provided and described by @michaeljeger (once more many thanks from all of us ) can be applied to any other BIOS Firmware distribution of any mainboard manufacturer. In Windows 10, download the latest UBU software distribution from https://cloud.mail.ru/public/HLDj/6cT1gUPke: a.) From online directory "UEFI BIOS Updater" download und unrar "UBU_v1_70_rc12.rar" or any newer distribution to an "UBU" directory on your Windows Desktop yet to be created b.) Also download and unrar "mms.tar" from the online directory "UEFI BIOS Updater". This will create an "mmt" folder, where from the "184.108.40.206" directory you copy "MMTool.exe" to your "UBU" Desktop directory c.) Download the latest BIOS firmware distribution for your particular mainboard from the respective web page of your mainboard manufacturer. In case of the ASUS X99-A II, it is X99-A-II-ASUS-1902.CAP. Copy the respective BIOS Firmware file to your "UBU" Desktop directory. Now you have all necessary ingredients in your "UBU" Desktop directory. d.) Open a windows terminal, change to the "UBU" Desktop directory and launch the UBU software with the terminal command: ubu
On UBU software launch, UBU will now scan your BIOS firmware file that you previously added to your "UBU" Desktop directory and detect BIOS platform, manufacturer and mainboard model, as well as EFI Driver and OROM components. When you are asked to "Press any key to continue..", follow this request. e.) From the listed options in the consecutive terminal text menu choose option 5 - CPU Microcode by typing "5" and subsequently pressing the "Enter" button. f.) Now the tool will analyse whether are not all respective available CPU microcodes are properly implemented in your BIOS firmware. All implemented CPU microcodes will be highlighted by "YES", all missing CPU microcodes will be highlighted by "No". To download the missing Intel CPU microcodes, choose option "C - Create FFS with MicroCodes" by typing "C" and subsequently pressing the "Enter" button. g.) In the next terminal text menu the tool will summarise all additional downloaded Intel CPU microcodes: To implement the new and complete set of available Intel CPU microcodes in your BIOS firmware file, launch "MMTool", which you previously added to your "UBU" desktop directory, by typing "M" and subsequently pressing the "Enter" button. h.) Now MMTool now will do it's magics and summarise once more the complete Intel microcode table successfully implemented in your BIOS firmware file. Now choose menu option "0 - Exit to Main Menu" by pressing "0" and subsequently "Enter". i.) In the next terminal text menu choose "Rename to ASUS USB BIOS Flashback" by pressing "1" and subsequently "Enter". By this, the UBU tool will save the modified BIOS firmware file in the "UBU" desktop directory already with the correct EZ Flashback convention. For mainboards different from ASUS, this last step might be different though. We have to wait on further user feedback. In case of our ASUS X99-A II 1902 BIOS firmware, we will find X99A2.CAP as the result of the UBU Intel CPU microcode procedure. After providing our firmware with a complete set of Intel microcode implementations, we can now continue with the firmware patching procedure and unlock the MSR 0xE2 register for OSX Kernel write. B.1.2) MSR 0xE2 register unlock for OSX Kernel Write 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 (attached towards the bottom of this guide) to your Desktop. 2.) To unlock the MSR 0xE2 register for kernel write copy the BIOS firmware file modified in section B.1.1) to the "UEFIPatch_0.3.9_osx" directory on your Desktop. 3.) Open a terminal; type "cd " and drag the "UEFIPatch_0.3.9_osx"-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 actual BIOS CAP file into the terminal window; Press enter to execute the "UEFIPatch"-procedure. The equivalent terminal command in case of the ASUS X99-A II BIOS firmware is: ./UEFIPatch X99A2.CAP 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 again to X99A2.CAP or to the correct EZ Flashback filename for your particular ASUS Mainbaord by following 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 actual patched BIOS, compatible with native OSX/MacOS power management. 11.) Boot your system and apply the BIOS settings described below. Instead of stepwise applying the entire Bios firmware patching procedure detailed above, all ASUS X99A-II users can simply download, unzip and flash X99A2.CAP.zip, actual BIOS firmware 1902, accounting for the complete set of available Intel CPU Microcodes, an unlocked MSR register and an iMac Pro Splash Screen Boot Image to be displayed at boot. B.2) Asus X99-A II BIOS Configuration 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. 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 i9-7980XE stock settings (4.4 Ghz, Sync All Cores), 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 water cooling system! Otherwise, CPU Core Ratio should be set to "Auto". Further note that with CPU Core Ratio set to "Sync All Cores", one might have to set the AVX Instruction Core Ratio Negative Offset to "3" in case of system freezes or system instabilities. 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! Above 4G Decoding Note: Enable BIOS function "Above 4G Decoding" to avoid memory relocation errors when using AptioMemoryFix.efi on X99 systems. CPU SVID Support: In addition to the BIOS settings mentioned above one should also Enable CPU SVID support in BIOS Section AI Tweaker, which is fundamental for the proper Intel Power Gadget (IPG) CPU power consumption display. 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 Mojave distribution.
1.) The /EFI/Clover/drivers64UEFI/-directory of my actual respective X99 EFI-Folder distribution contains by default AptioMemoryFix.efi thanks to @vit9696. Note that with Clover_v2.4k_r4392, AptioMemoryFix.efi has become an official Customization Option of Clover and can now be selected and therefore also just easily implemented in the frame of the Clover Boot Loader Installation.
For native NVRAM implementation, 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:
sudo rm -rf /etc/rc.boot.d sudo rm -rf /etc/rc.shutdown.d
Also the "slide" boot flag needs to be disabled.
2.a) Most ATI GPUs, e.g. RX Vega 64, RX Vega Frontier, RX 580, RX 560 are supposed to be "natively" implemented. It is commonly recommended not to use RX 560 and RX 580 GPUs due to the lacking iGPU implementation when using SMBIOS iMacPro1,1. By means of my Vega SSDT PCI device implementation outlined in Section 9.2.2, all available ports on the Gigabyte Vega 64 (3x HDMI, 3x DP), including multi-monitor support and display hot plug are automatically and successfully implemented. However, it seems that DP-port issues (black screen) remain, when employing the respective Vega SSDT PCI device implementation on Sapphire Nitro+ Vega 64 (2x HDMI, 2xDP) or ASUS Strix Vega 64 (2x HDMI, 2x DP, 1x DVI) GPUs, which only can be removed by adding Whatevergreen.kext. Within such configuration, multi-monitor support and display hot plug can be fully achieved also in case of the latter custom Vegas (both 10.13.6 SU and 10.14.1). A fall-back to the formerly used Kamarang frame buffer SSDT implementation of @apfelnico does not provide any valuable solution for these kind of custom Vegas. Also note that Whatevergreen.kext only seems required for all Vegas possessing less than 6 physical ports (including the original Vegas like Frontier and Vega 64), else the current Vega SSDT PCI device implementation does pretty well it's job, including sleep/wake. Important additional comment for all Vega users with 4K monitors though: when connecting a Vega with e.g. the LG 38UC99-W (WUHD, 3840 pix x 1600 pix) via one of the Display Ports (DPs), the screen resolution is fine under both Windows 10 and macOS High Sierra but is totally at odd during boot (VGA like boot screen resolution). The VEGA DP 4K boot screen resolution issue is neither related with the fact that the LG 38UC99-W is an ultra-wide (3840x1600) and not a true UHD (3840x2160) monitor nor related to any likely apparent issue with the ASUS X99-A II firmware. It is definitely a Vega firmware problem in combination with most 4K displays, as the DP 4K boot screen resolution issue is totally absent with my Nvidia GPU and the problem also does not only affect the ASUS Splash Screen but also spreads over the entire boot process until the login screen is reached (Windows and macOS). Splash Screen, Apple logo or verbose boot messages are not stretched but rather have VGA like resolution. Any fix of the AMD vBIOS would be highly appreciated. It is more than disappointing to witness such issues with 600-1000$ GPUs... Fortunately, the 4K boot screen issue is restricted to the Vega DP ports and likely due to the fact that the LG 38UC99-W only supports DP 1.2. Solution: Connect your Vega and your 4K display via the HDMI port. The 30 Hz HDMI monitor frequency issue under 10.13 is successfully removed under Mojave: monitor frequency of 60 Hz with the display connected via HDMI (in contrary to 75 Hz via DP). b.) Also Nvidia Kepler Graphics Cards are natively implemented. c.) All Users with Nvidia Maxwell and Pascal Graphics Cards Users still have to wait for the official release of 10.14 Web Drivers. I was actively requesting Web Driver development for macOS 10.14 Betas from Nvidia, which has been rejected. I really hope that Nvidia will not leave again the respective community without Web Driver support. In the meanwhile, Nvidia GPU users have to live with e.g. patched Web Driver xxx.40.105 for macOS High Sierra 10.13.6 after a simple patching procedure detailed in Section E.2), although the latter Web Driver is not really suited for 10.14 and just works with strong limitations.
3.) The /EFI/Clover/drivers64UEFI/-directory of all former EFI-Folder distributions contained a patched version of the actual apfs.efi. The actual apfs.efi can be obtained by following the respective guideline detailed below:
Right-click with your mouse on the "Install macOS High Sierra.app" and select "Show Package Contents" -> click with the mouse on "Contents" and subsequently on "Shared Support" -> double-click with the mouse on "BaseSystem.dmg" for mounting. Go to "usr" -> "standalone" -> "i386". Drop the apfs.efi to your Desktop. To patch the apfs.efi for non-verbose boot, follow THIS LINK. Credits to @PMheart and @ermac. Note however, that the entire apsf.efi approach detailed above recently has become totally obsolete. Thanks to the ApfsSupportPkg developed by @acidenthera & Co. and thanks to it's recent implementation to Clover (thanks to @Slice, @Philip Petev & Co.) in form of ApsfDriverLoader.efi, there is no further need of the former apsf.efi in the /EFI/Clover/drivers64UEFI/ directory. The actual Clover distribution package including the ApsfDriverLoader.efi can by build by means of the Build_Clover.command available on Gitub. Since Version 4.8.8, the latter script also can be used with 10.14 and Xcode 10 + Xcode 10 Command Line Tools thanks to @vector sigma. By adding export PATH="/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin" && buildclover to the script, the latter also can be used in case of Brew, QT5, UEFITool or MacPorts implementations like Latex, X11, gcc, etc. not yet fully compatible with 10.14 Mojave. Again thanks to @vector sigma for also providing/enabling this trick/possibility . 4.) To avoid CPU thread TSC desynchronisation errors during boot and wake from S3, likely induced by yet erroneous CPU BIOS microcode implementations, we need to use TSCAdjustReset.kext provided by @interferenc in the /EFI/CLOVER/kexts/Other/ directory of both USB Flash Drive and System Disk in the latter case. To access TSCAdjustRest.kext, download primarily its source distribution from Github with the following terminal command: git clone https://github.com/interferenc/TSCAdjustReset Subsequently copy the TSCAdjustRest source distribution to your Desktop using the following terminal command:
mv /TSCAdjustReset ~/Desktop Now change in the terminal to the TSCAdjustReset source distribution on your Desktop with the following terminal command:
cd ~/Desktop/TSCAdjustReset/ Now compile the source distribution with Xcode by using the following terminal command:
xcodebuild After successful compilation, you will find the TSCAdjustRest.kext in ~/Desktop/TSCAdjustReset/build/Release/
Please note that the TSCAdjustRest.kext by default is configured for a 8-core CPU (16 threads) like the i7-7900K. To adopt the kext for Broadwell-E and Haswell-E processors with more or less cores than 8 cores, apply the following approach: a.) Right-click with the mouse on the TSCAdjustRest.kext file and select "Show Packet Contents". b.) 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. c.) Use the "find"-function of TextEdit.app and search for the term "IOCPUNumber" d.) Note that the adequate IOCPUNumber for your particular CPU 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> and following the same methodology, the correct IOCPUNumber for the 6-core i7-6800K is 11 (12 threads -1) <key>IOCPUNumber</key> <integer>11</integer> e.) After adopting the IOCPUNumber for your particular Broadwell-E/EP, Haswell-E/EP 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!
5.) Like under macOS 10.13 High Sierra also with macOS 10.14 Mojave, Apple forces all users to use the new Apple file system APFS in case of a Clean Install. In case that you want to remain with the HFS+ file system, use @Brumbear's Unsolid.kext in the /EFI/Clover/kexts/Other/ directory. 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.
Now delete the APFS container of diskX: diskutil apfs deleteContainer /dev/diskX 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 Mojave System Disk to APFS. To do so enter the following terminal command: diskutil apfs convert /dev/diskX where diskX is again a