Jump to content

Search the Community: Showing results for tags 'x99'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace

Categories

  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 41 results

  1. Up and running macOS Mojave 10.14.3 (18D42) 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 "5.2.0.24" 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 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. Important recommendation: If you opt for an APFS System Disk implementation, try to also implement all other disks of your system with APFS file format. 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. 6.) In order to successfully boot your X99 macOS 10.14 Mojave System system, carefully verify that your config.plist contains in Section "KextsToPatch" of Section "Kernel and Kext Patches" of Clover Configurator the 10.14 IOPCIFamily Kext Patch kindly provided by @PMHeart. D.) iMac macOS 10.14 Mojave System Setup Below, one finds a detailed description for the Installation/Update of/to macOS Mojave 10.14. This also includes the EFI-Folder Preparation (D.1), the macOS Mojave 10.14 Installer Package creation (D.2), the macOS Mojave 10.14 USB Flash Drive Installer Creation (D.3) and the macOS Mojave 10.14 Clean Install. One also finds instructions for a direct iMac Pro conversion of a functional Broadwell-E/EP, Haswell-E/EP X99 system with a SMBIOS System Definition different from iMacPro1,1 and standard macOS build implementation (D.5) of any former macOS distribution. D.6 finally provides details to the future iMac Pro macOS Mojave Update Procedure. D.1) iMac Pro 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 iMacPro1,1 System definition. 1.) Download and unzip my actual respective X99 EFI-Folder distribution 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 iMacPro1,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 iMacPro1,1 SMBIOS Details are already implemented in the config.plist of my actual respective X99 EFI-Folder distribution. Press several times the "Generate New" Button next to serial number text field. 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. Depending on your system configuration (Broadwell-E/EP or Haswell-E/EP) change or adopt the following settings if necessary a.) Users of mainboards with locked MSR Register (disabled MSR OSX Kernel write access) have to add the xcpm_core_scope_msrs © Pike R. Alpha Kernel patch in their config.plist under "KernelToPatch" in Section "Kernel and Kext Patches" of Clover Configurator xcpm_core_scope_msrs © Pike R. Alpha 10.14 (kindly provided by @PMHeart) Find: 31 d2 e8 91 fc ff ff Replace: 31 d2 90 90 90 90 90 and also to check "KernelPm". b.) "FakeCPUID" in "Kernel and Kext Patches" Section of Clover Configurator: Broadwell-E/EP FakeCPUID: "0x040674" Haswell-E/EP standard FakeCPUID: "0x0306F2" c.) All Broadwell-E/EP and Haswell-E/EP users have to enable the macOS independent _xcpm performance kernel patch for 10.13.6+ and all 10.14 version (kindly provided by @PMheart and based on the method developed by @vit9696) in their config.plist under "KernelToPatch" in Section "Kernel and Kext Patches" of Clover Configurator to enable the OC capability of their respective CPUs. macOS independent _xcpm performance kernel patch for 10.13.6+ and all 10.14 version (kindly provided by @PMheart and based on the method developed by @vit9696) Find: C1E30848 63D389D0 48C1EA20 B99901 Replace: C1E308B8 00FF0000 31D29090 B99901 To successfully boot my Broadwell-E X99 System and to obtain full XCPM-performance I also need to include the following Kernel patch: d.) xcpm_pkg_scope_msrs © Pike R. Alpha (kindly provided by @PMHeart) Find: BE070000 0031D2E8 91FCFFFF Replace: BE070000 0031D290 90909090 Further one might want to include: e.) _xcpm_SMT_scope_msrs 1 & 2 © Pike R. Alpha 10.14 (kindly provided by @PMHeart) Find: BE0B0000 0031D2E8 66FCFFFF Replace: BE0B0000 0031D290 90909090 Find: 31D2E87E FCFFFF Replace: 31D29090 909090 f.) Enable "PluginType" in your config.plist under SSDT/Generate Options/ in Section ACPI of Clover Configurator for a fully working XCPM implementation. Note that by this, Pike Alpha's former ssdt.aml XCPM implementation becomes totally obsolete. g.) Aslo verify once more that your config.plist contains the 10.14 IOPCIFamily kext patch! Name* Find*[HEX] Replace*[HEX] Comment IOPCIFamily 483D0000 0040 483D0000 0080 IOPCIFamily patch © PMHeart h.) Enable USB port limit patches: Valid USB port limit patches for 10.14.3 provided by ©ydeng and hardwired but yet disabled in my respective EFI-Folder distribution: kext : com.apple.iokit.IOUSBHostFamily Find : 83FB0F0F 871604 00 Replace : 83FB3F0F 871604 00 Name : USB Port Limit Patch 1 ©ydeng kext : com.apple.driver.usb.AppleUSBXHCI Find : 83FB0F0F 838F0400 00 Replace : 83FB3F0F 838F0400 00 Name : USB Port Limit Patch 2 ©ydeng kext : com.apple.iokit.IOUSBHostFamily Find : 83E30FD3 E34109DF Replace : 83E33FD3 E34109DF Name : USB Port Limit Patch 3 ©ydeng Finally save the modified config.plist. 3.) Copy the appropriate TSCAdjustRest.kext, which you modified in error prevention C.4), 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) iMac Pro macOS Mojave 10.14 Installer Package Creation If you are not able to successfully download the macOS Mojave 10.14.3 (18D42) full package installer (6.03 GB) from the Appstore, follow the individual steps detailed below:1.) Open a terminal and create a "041-31308" directory on your Desktop. Subsequently change to the newly created directory. All this can be done with the following terminal commands: mkdir ~/Desktop/041-31308/ cd ~/Desktop/041-31308/ 2.) Download the following files from the Apple server (public links) to your ~/Desktop/041-31308/ directory by a copy & paste of the following terminal commands: curl https://swdist.apple.com/content/downloads/22/46/041-31308/r39g613fmms2li42if9r120zwn2bn7rnhn/041-31308.English.dist -o 041-31308.English.dist curl http://swcdn.apple.com/content/downloads/22/46/041-31308/r39g613fmms2li42if9r120zwn2bn7rnhn/InstallAssistantAuto.smd -o InstallAssistantAuto.smd curl http://swcdn.apple.com/content/downloads/22/46/041-31308/r39g613fmms2li42if9r120zwn2bn7rnhn/AppleDiagnostics.chunklist -o AppleDiagnostics.chunklist curl http://swcdn.apple.com/content/downloads/22/46/041-31308/r39g613fmms2li42if9r120zwn2bn7rnhn/AppleDiagnostics.dmg -o AppleDiagnostics.dmg curl http://swcdn.apple.com/content/downloads/22/46/041-31308/r39g613fmms2li42if9r120zwn2bn7rnhn/OSInstall.mpkg -o OSInstall.mpkg curl http://swcdn.apple.com/content/downloads/22/46/041-31308/r39g613fmms2li42if9r120zwn2bn7rnhn/BaseSystem.chunklist -o BaseSystem.chunklist curl http://swcdn.apple.com/content/downloads/22/46/041-31308/r39g613fmms2li42if9r120zwn2bn7rnhn/InstallESDDmg.chunklist -o InstallESDDmg.chunklist curl http://swcdn.apple.com/content/downloads/22/46/041-31308/r39g613fmms2li42if9r120zwn2bn7rnhn/BaseSystem.dmg -o BaseSystem.dmg curl https://swdist.apple.com/content/downloads/22/46/041-31308/r39g613fmms2li42if9r120zwn2bn7rnhn/RecoveryHDMetaDmg.pkm -o RecoveryHDMetaDmg.pkm curl http://swcdn.apple.com/content/downloads/22/46/041-31308/r39g613fmms2li42if9r120zwn2bn7rnhn/RecoveryHDMetaDmg.pkg -o RecoveryHDMetaDmg.pkg curl https://swdist.apple.com/content/downloads/22/46/041-31308/r39g613fmms2li42if9r120zwn2bn7rnhn/InstallAssistantAuto.pkm -o InstallAssistantAuto.pkm curl http://swcdn.apple.com/content/downloads/22/46/041-31308/r39g613fmms2li42if9r120zwn2bn7rnhn/InstallAssistantAuto.pkg -o InstallAssistantAuto.pkg curl http://swcdn.apple.com/content/downloads/22/46/041-31308/r39g613fmms2li42if9r120zwn2bn7rnhn/InstallInfo.plist -o InstallInfo.plist curl https://swdist.apple.com/content/downloads/22/46/041-31308/r39g613fmms2li42if9r120zwn2bn7rnhn/MajorOSInfo.pkm -o MajorOSInfo.pkm curl http://swcdn.apple.com/content/downloads/22/46/041-31308/r39g613fmms2li42if9r120zwn2bn7rnhn/MajorOSInfo.pkg -o MajorOSInfo.pkg curl https://swdist.apple.com/content/downloads/22/46/041-31308/r39g613fmms2li42if9r120zwn2bn7rnhn/InstallESDDmg.pkm -o InstallESDDmg.pkm curl http://swcdn.apple.com/content/downloads/22/46/041-31308/r39g613fmms2li42if9r120zwn2bn7rnhn/InstallESDDmg.pkg -o InstallESDDmg.pkg The full list of package files can be found within the following catalog URL, searching for key "r39g613fmms2li42if9r120zwn2bn7rnhn": https://swscan.apple.com/content/ca...ion-snowleopard-leopard.merged-1.sucatalog.gz 3.) Create the installer.pkg on your Desktop with the following terminal command: cd .. productbuild --distribution ./041-31308/041-31308.English.dist --package-path ./041-31308/ installer.pkg 4.) Create the "Install MacOS Mojave" in the /Applications folder of your System Disk with the following terminal command: sudo /usr/sbin/installer -pkg installer.pkg -target / In case that you receive an error message, ignore the latter and proceed with 5.)5.) Now add the following files to your "Install macOS Mojave.app" with the following terminal commands: sudo cp ./041-31308/InstallESDDmg.pkg /Applications/Install\ macOS\ Mojave.app/Contents/SharedSupport/InstallESD.dmg sudo cp ./041-31308/AppleDiagnostics.dmg /Applications/Install\ macOS\ Mojave.app/Contents/SharedSupport/ sudo cp ./041-31308/AppleDiagnostics.chunklist /Applications/Install\ macOS\ Mojave.app/Contents/SharedSupport/ sudo cp ./041-31308/BaseSystem.dmg /Applications/Install\ macOS\ Mojave.app/Contents/SharedSupport/ sudo cp ./041-31308/BaseSystem.chunklist /Applications/Install\ macOS\ Mojave.app/Contents/SharedSupport/ Verify your "Install Mojave.app" for completeness. You should now have a complete macOS Mojave 10.14.3 (18D42) Installer package in your /Applications Folder.The entire "Install macOS Mojave.app" creation procedure has been also fully automatised within one single script, as already implemented for macOS High Sierra with the help of @macandrea. createInstaller-10.14.3.sh will automatically create on any MacOS System the "Install macOS Mojave.app" for macOS Mojave 10.14.3 (18D42) in the /Applications folder.Just download und unzip createInstaller-10.14.3.sh.zip and run the following terminal commands: cd ~/Downloads chmod +x createInstaller-10.14.3.sh ./createInstaller-10.14.3.sh D.3) iMac Pro macOS Mojave 10.14 USB Flash Drive Installer Creation Follow the individual steps detailed below to successfully create a bootable iMac Pro macOS Mojave 10.14 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 macOS Mojave 10.14 Installer Package in your /Application Folder, connect your USB Flash Drive (named USB) and run the following terminal command: sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --nointeraction Alternatively, one can create the iMac Pro macOS USB Flash Drive Installer also by means of the Install Disk Creator.app. 3.) For successfully booting your iMac Pro macOS USB Flash Drive Installer, the latter must however also contain a valid EFI- Folder with an SMBIOS iMacPro1,1 system definition. Thus, copy the EFI-Folder you prepared in Section D.1) to the yet empty EFI Partition of your macOS USB Flash Drive Installer. You now have a fully functional and bootable macOS Mojave 10.14 USB Flash Drive Installer. D.4) iMac Pro macOS Mojave 10.14 Clean Install on Broadwell-E/EP, Haswell-E/EP, X99 Follow the individual steps detailed below to successfully setup macOS Mojave 10.14 on a virgin system drive of your choice (NVMe, SSD or HDD). 1.) In order to perform a clean install of macOS Mojave 10.14, 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 macOS Mojave 10.14 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 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 macOS USB Flash Drive Installer 6.) After successful boot, pass the individual steps of the macOS 10.14 Mojave installation menu and finally select the destination drive of your macOS 10.14 Mojave Installation, which should be logically the system disk you successfully configured above. In the next step, the Installer will create a macOS Mojave 10.14 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 Mojave 10.14 Installer Partition on your system disk. 8.) After successful boot, you will enter now the macOS Mojave 10.14 Installer Screen with a progress bar starting at about 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 Mojave" icon on the clover boot screen to boot the new macOS Mojave partition of your system disk. 10.) After successful boot you have to perform the iCloud registration to have your first iMac Pro macOS Mojave 10.14 build. Proceed with Section D.6) - iMac Pro macOS High Sierra Build Updates (if necessary) or E.) - Post Installation Process. D.5) Direct iMac Pro conversions of a functional Broadwell-E/EP, Haswell-E/EP, X99 system with a SMBIOS System Definition different from iMacPro1,1 and a standard macOS build implementation 1.) Replace the EFI-Folder of your System Disk by the EFI-Folder you created in Section D.1) 2.) Copy /System/Library/CoreServices/PlatformSupport.plist to your Desktop, add BoardID "Mac-7BA5B2D9E42DDD94" under SupportedBoardIDs by means of Xcode as suggested by user Griven from the German Hackintosh-Forum and copy back the modified PlatformSupport.plist to System/Library/CoreServices/. 3.) If not already in your /Applications folder after performing Section D.2), copy the iMac Pro macOS Installer Package to your /Applications folder. 4.) Double click on the "Install macOS Mojave.app" in the /Applications Folder to start the macOS Mojave 10.14 installation. 5.) After reboot, click on the "Install MacOS.." Icon in the clover boot screen to boot the newly created macOS Mojave 10.14 Installer Partition on your system disk. 6.) After successful boot, you will enter now the macOS Mojave 10.14 Installer Screen with a progress bar starting at 43 minutes. 7.) After another reboot, click on the "MacOS Mojave" icon in the clover boot screen to boot the updated macOS Mojave 10.14 on your system disk. 8.) After successful boot you have to register at iCloud at the end of the macOS installation, and you will now have your first iMac Pro macOS Mojave 10.14 build. Proceed with Section D.6) - iMac Pro macOS 10.14 Mojave Update Procedure (if necessary) or Section E.) - Post Installation Process. D.6) iMac Pro macOS 10.14 Mojave Update Procedure If you already used my 10.13 iMacPro X99 guide to setup a 10.13 iMac Pro macOS build, you simply have to update your EFI-Folder and directly perform the update to macOS 10.14.0 Mojave from System Disk by else following steps 4.) to 8.) of D.5) above. Any future macOS Mojave update can be directly performed via "Software Update" under "System Preferences". E.) Post Installation Process E.1) XNU CPU Power Management (XCPM) Configuration The config.plist of my actual respective X99 EFI-Folder distribution already contains a fully functional XCPM configuration for the i7-6950X Broadwell-E CPU, which just needs to be adopted for other CPU configurations (Broadwell-E/EP different from i7-6950X, Haswell-E/EP). Before adapting the XCPM configuration, verify the following BIOS settings: Advanced\CPU Configuration\CPU Power Management Configuration\ Enhanced Intel SpeedStep Technology (EIST): Disabled Turbo mode: Enabled CPU C-State: Enabled Enhanced C1 State: Enabled CPU C3 Report: Enabled CPU C6 Report: Enabled Package C State Limit: C6(non Retention) state Subsequently, follow the individual steps below. 1.) Open the config.plist of your 10.14 system disk and revise the "Kernel and Kext Patches" Section. a.) Users of mainboards with locked MSR Register (disabled MSR OSX Kernel write access) have to add the xcpm_core_scope_msrs © Pike R. Alpha Kernel patch in their config.plist under "KernelToPatch" in Section "Kernel and Kext Patches" of Clover Configurator xcpm_core_scope_msrs © Pike R. Alpha 10.14 (kindly provided by @PMHeart) Find: 31 d2 e8 91 fc ff ff Replace: 31 d2 90 90 90 90 90 and also to check "KernelPm". b.) Verify "FakeCPUID" in "Kernel and Kext Patches" Section of Clover Configurator: Broadwell-E/EP FakeCPUID: "0x040674" Haswell-E/EP standard FakeCPUID: "0x0306F2" c.) All Broadwell-E/EP and Haswell-E/EP users have to enable the macOS independent _xcpm performance kernel patch for 10.13.6+ and all 10.14 version (kindly provided by @PMheart and based on the method developed by @vit9696) in their config.plist under "KernelToPatch" in Section "Kernel and Kext Patches" of Clover Configurator to enable the OC capability of their respective CPUs. macOS independent _xcpm performance kernel patch for 10.13.6+ and all 10.14 version (kindly provided by @PMheart and based on the method developed by @vit9696) Find: C1E30848 63D389D0 48C1EA20 B99901 Replace: C1E308B8 00FF0000 31D29090 B99901 To successfully boot my Broadwell-E X99 System and to obtain full XCPM-performance I also need to include the following Kernel patch: d.) xcpm_pkg_scope_msrs © Pike R. Alpha (kindly provided by @PMHeart) Find: BE070000 0031D2E8 91FCFFFF Replace: BE070000 0031D290 90909090 Further one also might like to implement: e.) _xcpm_SMT_scope_msrs 1 & 2 © Pike R. Alpha 10.14 (kindly provided by @PMHeart) Find: BE0B0000 0031D2E8 66FCFFFF Replace: BE0B0000 0031D290 90909090 Find: 31D2E87E FCFFFF Replace: 31D29090 909090 f.) Enable "PluginType" in your config.plist under SSDT/Generate Options/ in Section ACPI of Clover Configurator for a fully working XCPM implementation. Note that by this, Pike Alpha's former ssdt.aml XCPM implementation becomes totally obsolete. All other former XCPM kernel patches have become obsolete with 10.14 at least for Broadwell-E. There is also no need for injecting any additional frequency vector. 2.) Reboot after applying any changes. To verify your XCPM configuration, perform the following steps: 1.) Verify with the terminal command "sysctl machdep.xcpm.mode" if the XCPM mode is active. If so, "sysctl machdep.xcpm.mode" should return "1". 2.) Verify that in the IORegistryExplorer you have the following entry under CP00@0: Property: Type: Value: plugin-type Number 0x1 3.) Verify with the terminal command kextstat|grep -y x86plat that the "X86PlatformPlugin.kext" is loaded. If the command returns something like 112 1 0xffffff7f822bc000 0x17000 0x17000 com.apple.driver.X86PlatformPlugin (1.0.0) FD88AF70-3E2C-3935-99E4-C48669EC274B <111 19 18 13 11 7 6 5 4 3 1> 146 1 0xffffff7f822d3000 0x7000 0x7000 com.apple.driver.X86PlatformShim (1.0.0) DCEA94A4-3547-3129-A888-E9D5C77B275E <112 111 13 7 4 3> you are fine. 4.) Verify with the terminal command [code]kextstat|grep -y appleintelcpu[/code] that you got rid of the Apple Intel CPU power management. If the result is empty you are fine. 5.) To verify that the Frequency-Vectors are loaded, use the following terminal command: sysctl -n machdep.xcpm.vectors_loaded_count If everything is ok, the command returns "1". 6.) To obtain further information on your XCPM Power Management configuration, download Piker Alpha’s AppleIntelInfo.kext from Github. To compile the source code, you need to primarily install Xcode (Appstore) and Xcode Command Line Tools! This guideline might be helpful for the successfully installation of the latter. Now enter the following terminal commands: cd ~/Downloads/AppleIntelInfo-master xcodebuild cd build/Release chmod -R 755 AppleIntelInfo.kext sudo chown -R root:wheel AppleIntelInfo.kext Load the AppleIntelInfo.kext with "kextload" and "cat" the info-results with the following terminal commands: sudo kextload AppleIntelInfo.kext sudo cat /tmp/AppleIntelInfo.dat The cat command should reveal something like the following result: AppleIntelInfo.kext v2.5 Copyright © 2012-2017 Pike R. Alpha. All rights reserved. Settings: ------------------------------------------ logMSRs..................................: 1 logIGPU..................................: 0 logCStates...............................: 1 logIPGStyle..............................: 1 InitialTSC...............................: 0x11d3a1760ecb2 (10453 MHz) MWAIT C-States...........................: 8480 Processor Brandstring....................: Intel(R) Core(TM) i7-6950X CPU @ 3.00GHz Processor Signature..................... : 0x406F1 ------------------------------------------ - Family............................... : 6 - Stepping............................. : 1 - Model................................ : 0x4F (79) Model Specific Registers (MSRs) ------------------------------------------ MSR_CORE_THREAD_COUNT............(0x35) : 0x0 ------------------------------------------ - Core Count........................... : 10 - Thread Count......................... : 20 MSR_PLATFORM_INFO................(0xCE) : 0x20080C3BF3811E00 ------------------------------------------ - Maximum Non-Turbo Ratio.............. : 0x1E (3000 MHz) - Ratio Limit for Turbo Mode........... : 1 (programmable) - TDP Limit for Turbo Mode............. : 1 (programmable) - Low Power Mode Support............... : 1 (LPM supported) - Number of ConfigTDP Levels........... : 1 (additional TDP level(s) available) - Maximum Efficiency Ratio............. : 12 - Minimum Operating Ratio.............. : 8 MSR_PMG_CST_CONFIG_CONTROL.......(0xE2) : 0x1E000005 ------------------------------------------ - I/O MWAIT Redirection Enable......... : 0 (not enabled) - CFG Lock............................. : 0 (MSR not locked) - C3 State Auto Demotion............... : 1 (enabled) - C1 State Auto Demotion............... : 1 (enabled) - C3 State Undemotion.................. : 1 (enabled) - C1 State Undemotion.................. : 1 (enabled) - Package C-State Auto Demotion........ : 0 (disabled/unsupported) - Package C-State Undemotion........... : 0 (disabled/unsupported) MSR_PMG_IO_CAPTURE_BASE..........(0xE4) : 0x10414 ------------------------------------------ - LVL_2 Base Address................... : 0x414 - C-state Range........................ : 1 (C-States not included, I/O MWAIT redirection not enabled) IA32_MPERF.......................(0xE7) : 0xACF485063 IA32_APERF.......................(0xE8) : 0xB96AC7BB7 MSR_0x150........................(0x150) : 0x0 MSR_FLEX_RATIO...................(0x194) : 0xE0000 ------------------------------------------ MSR_IA32_PERF_STATUS.............(0x198) : 0x204900001E00 ------------------------------------------ - Current Performance State Value...... : 0x1E00 (3000 MHz) MSR_IA32_PERF_CONTROL............(0x199) : 0x2A00 ------------------------------------------ - Target performance State Value....... : 0x2A00 (4200 MHz) - Intel Dynamic Acceleration........... : 0 (IDA engaged) IA32_CLOCK_MODULATION............(0x19A) : 0x0 IA32_THERM_INTERRUPT.............(0x19B) : 0x0 IA32_THERM_STATUS................(0x19C) : 0x883D0000 ------------------------------------------ - Thermal Status....................... : 0 - Thermal Log.......................... : 0 - PROCHOT # or FORCEPR# event.......... : 0 - PROCHOT # or FORCEPR# log............ : 0 - Critical Temperature Status.......... : 0 - Critical Temperature log............. : 0 - Thermal Threshold #1 Status.......... : 0 - Thermal Threshold #1 log............. : 0 - Thermal Threshold #2 Status.......... : 0 - Thermal Threshold #2 log............. : 0 - Power Limitation Status.............. : 0 - Power Limitation log................. : 0 - Current Limit Status................. : 0 - Current Limit log.................... : 0 - Cross Domain Limit Status............ : 0 - Cross Domain Limit log............... : 0 - Digital Readout...................... : 61 - Resolution in Degrees Celsius........ : 1 - Reading Valid........................ : 1 (valid) MSR_THERM2_CTL...................(0x19D) : 0x0 IA32_MISC_ENABLES................(0x1A0) : 0x850089 ------------------------------------------ - Fast-Strings......................... : 1 (enabled) - FOPCODE compatibility mode Enable.... : 0 - Automatic Thermal Control Circuit.... : 1 (enabled) - Split-lock Disable................... : 0 - Performance Monitoring............... : 1 (available) - Bus Lock On Cache Line Splits Disable : 0 - Hardware prefetch Disable............ : 0 - Processor Event Based Sampling....... : 0 (PEBS supported) - GV1/2 legacy Enable.................. : 0 - Enhanced Intel SpeedStep Technology.. : 1 (enabled) - MONITOR FSM.......................... : 1 (MONITOR/MWAIT supported) - Adjacent sector prefetch Disable..... : 0 - CFG Lock............................. : 0 (MSR not locked) - xTPR Message Disable................. : 1 (disabled) MSR_TEMPERATURE_TARGET...........(0x1A2) : 0x640A00 ------------------------------------------ - Turbo Attenuation Units.............. : 0 - Temperature Target................... : 100 - TCC Activation Offset................ : 0 MSR_MISC_PWR_MGMT................(0x1AA) : 0x402000 ------------------------------------------ - EIST Hardware Coordination........... : 0 (hardware coordination enabled) - Energy/Performance Bias support...... : 1 - Energy/Performance Bias.............. : 0 (disabled/MSR not visible to software) - Thermal Interrupt Coordination Enable : 1 (thermal interrupt routed to all cores) MSR_TURBO_RATIO_LIMIT............(0x1AD) : 0x2A2A2A2A2A2A2A2A ------------------------------------------ - Maximum Ratio Limit for C01.......... : 2A (4200 MHz) - Maximum Ratio Limit for C02.......... : 2A (4200 MHz) - Maximum Ratio Limit for C03.......... : 2A (4200 MHz) - Maximum Ratio Limit for C04.......... : 2A (4200 MHz) - Maximum Ratio Limit for C05.......... : 2A (4200 MHz) - Maximum Ratio Limit for C06.......... : 2A (4200 MHz) - Maximum Ratio Limit for C07.......... : 2A (4200 MHz) - Maximum Ratio Limit for C08.......... : 2A (4200 MHz) MSR_TURBO_RATIO_LIMIT1...........(0x1AE) : 0x2222222222222A2A ------------------------------------------ - Maximum Ratio Limit for C09.......... : 2A (4200 MHz) - Maximum Ratio Limit for C10.......... : 2A (4200 MHz) IA32_ENERGY_PERF_BIAS............(0x1B0) : 0x5 ------------------------------------------ - Power Policy Preference...............: 5 (balanced performance and energy saving) MSR_POWER_CTL....................(0x1FC) : 0x2904005B ------------------------------------------ - Bi-Directional Processor Hot..........: 1 (enabled) - C1E Enable............................: 1 (enabled) MSR_RAPL_POWER_UNIT..............(0x606) : 0xA0E03 ------------------------------------------ - Power Units.......................... : 3 (1/8 Watt) - Energy Status Units.................. : 14 (61 micro-Joules) - Time Units .......................... : 10 (976.6 micro-Seconds) MSR_PKG_POWER_LIMIT..............(0x610) : 0x7FFF80015FFF8 ------------------------------------------ - Package Power Limit #1............... : 4095 Watt - Enable Power Limit #1................ : 1 (enabled) - Package Clamping Limitation #1....... : 1 (allow going below OS-requested P/T state during Time Window for Power Limit #1) - Time Window for Power Limit #1....... : 10 (2560 milli-Seconds) - Package Power Limit #2............... : 4095 Watt - Enable Power Limit #2................ : 1 (enabled) - Package Clamping Limitation #2....... : 1 (allow going below OS-requested P/T state setting Time Window for Power Limit #2) - Time Window for Power Limit #2....... : 3 (20 milli-Seconds) - Lock................................. : 0 (MSR not locked) MSR_PKG_ENERGY_STATUS............(0x611) : 0xC06AC ------------------------------------------ - Total Energy Consumed................ : 48 Joules (Watt = Joules / seconds) MSR_PKGC3_IRTL...................(0x60a) : 0x0 MSR_PKGC6_IRTL...................(0x60b) : 0x0 MSR_PKG_C2_RESIDENCY.............(0x60d) : 0x298ED1EE0 MSR_PKG_C3_RESIDENCY.............(0x3f8) : 0xD638F0 MSR_PKG_C2_RESIDENCY.............(0x60d) : 0x298ED1EE0 MSR_PKG_C3_RESIDENCY.............(0x3f8) : 0xD638F0 MSR_PKG_C6_RESIDENCY.............(0x3f9) : 0x44911A9AC IA32_TSC_DEADLINE................(0x6E0) : 0x11D3A1BDB3826 CPU Ratio Info: ------------------------------------------ Base Clock Frequency (BLCK)............. : 100 MHz Maximum Efficiency Ratio/Frequency.......: 12 (1200 MHz) Maximum non-Turbo Ratio/Frequency........: 30 (3000 MHz) Maximum Turbo Ratio/Frequency............: 42 (4200 MHz) P-State ratio * 100 = Frequency in MHz ------------------------------------------ CPU P-States [ (12) 27 30 ] CPU C3-Cores [ 1 2 4 6 8 10 12 14 16 18 ] CPU C6-Cores [ 0 2 4 6 8 10 12 14 16 18 ] CPU P-States [ 12 17 27 (30) ] CPU C3-Cores [ 1 2 3 4 6 7 8 10 11 12 14 15 16 18 19 ] CPU C6-Cores [ 0 2 4 6 8 9 10 12 14 16 17 18 ] CPU P-States [ (12) 17 27 30 31 ] CPU C3-Cores [ 0 1 2 3 4 6 7 8 9 10 11 12 14 15 16 18 19 ] CPU P-States [ (12) 14 17 27 30 31 ] CPU C3-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 18 19 ] CPU C6-Cores [ 0 2 4 6 8 9 10 12 14 15 16 17 18 ] CPU P-States [ (12) 14 17 20 27 30 31 ] CPU C3-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 ] CPU C6-Cores [ 0 1 2 4 6 7 8 9 10 12 14 15 16 17 18 ] CPU P-States [ (12) 14 16 17 20 27 30 31 ] CPU P-States [ (12) 14 16 17 18 20 27 30 31 ] CPU P-States [ (12) 14 16 17 18 20 27 30 31 32 ] CPU P-States [ (12) 14 16 17 18 20 22 27 30 31 32 ] CPU C6-Cores [ 0 1 2 3 4 6 7 8 9 10 12 14 15 16 17 18 ] CPU P-States [ (12) 13 14 16 17 18 20 22 27 30 31 32 ] CPU C6-Cores [ 0 1 2 3 4 6 7 8 9 10 12 13 14 15 16 17 18 19 ] CPU P-States [ (12) 13 14 16 17 18 20 22 23 27 30 31 32 ] CPU P-States [ 12 13 14 (15) 16 17 18 20 22 23 27 30 31 32 ] CPU P-States [ (12) 13 14 15 16 17 18 20 22 23 25 27 30 31 32 ] CPU P-States [ (12) 13 14 15 16 17 18 20 21 22 23 25 27 30 31 32 ] CPU C6-Cores [ 0 1 2 3 4 6 7 8 9 10 11 12 13 14 15 16 17 18 19 ] CPU P-States [ 12 13 14 15 16 17 18 20 21 22 23 (24) 25 27 30 31 32 ] CPU P-States [ (12) 13 14 15 16 17 18 19 20 21 22 23 24 25 27 30 31 32 ] CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 23 24 25 27 29 (30) 31 32 ] CPU C6-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 ] CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 23 24 25 27 28 29 30 31 32 (42) ] CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 23 24 25 27 28 29 30 31 32 36 (42) ] CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 23 24 25 27 28 29 30 31 32 34 36 (42) ] CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 23 24 25 27 28 29 30 31 32 34 35 36 (42) ] CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 23 24 25 27 28 29 30 31 32 34 35 36 41 (42) ] CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 23 24 25 27 28 29 30 31 32 34 35 36 37 41 (42) ] CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 23 24 25 27 28 29 30 31 32 34 35 36 37 38 41 (42) ] CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 23 24 25 27 28 29 30 31 32 34 35 36 37 38 39 41 (42) ] CPU P-States [ (12) 13 14 15 16 17 18 19 20 21 22 23 24 25 27 28 29 30 31 32 34 35 36 37 38 39 40 41 42 ] CPU P-States [ (12) 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 34 35 36 37 38 39 40 41 42 ] CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 (42) ] To unload the AppleIntelInfo.kext, enter the terminal command: sudo kextunload AppleIntelInfo.kext E.2) Graphics Configuration 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 the latest version of 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). Also Nvidia Kepler Graphics Cards are natively implemented. 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 Public 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 below, although the latter Web Driver is not really suited for 10.14 and just works with strong limitations. How to patch an Nvidia WebDriver: Download the Nvidia WebDriver-Payload Repackager from InsanelyMac. Credits to @Chris111 and @Pavo. The patch procedure is simple and fully described in the implemented Readme.txt and will reveal a Repackaged-WebDriver.pkg, which can be used for installing the patched Nvidia Web Driver xxx.35.106 under macOS Mojave 10.14. Nvidia Web Driver Installation and Black Screen Prevention: Apparently with SMBIOS iMacPro1,1, the Nvidia Black Screen Prevention has become obsolete. Thanks to @fabiosun for this finding. Thus, NvidiaGraphicsFixup.kext, subverting AppleMobileFileIntegrity banning the driver can be theoretically removed from the /EFI/CLOVER/kexts/Other/ directory of your macOS Flash Drive Installer and 10.13 System Disk. However, actual releases of Whatevergreen.kext and Lilu.kext apparently also help in fixing the Nvidia HDAU implementation and sporadic black screen issues while wake from sleep. Thus, the latter kext combination might still represent potential workarounds for few likely remaining system issues. a.) Install the patched Nvidia 10.13 Web Driver Package. b.) Now perform the following additional steps: i.) Copy /L/E/NVDAStartupWeb.kext to your Desktop. ii.) Right-click on NVDAStartupWeb.kext and select show package content. iii.) Change to "Contents" and edit the "Info.plist" with Xcode. iv.) Go to IOKitPersonalities -> NVDAStartup -> change "NVDARequiredOS" from "17F77" to "18D42", the corresponding build number of MacOS Mojave 10.14.3. v.) Save the "Info.plist" file and copy the modified "NVDAStartupWeb.kext" to /L/E/ with root permission. vi.) Open a terminal and enter the following commands: sudo chmod -R 755 /Library/Extensions/NVDAStartupWeb.kext sudo chown -R root:wheel /Library/Extensions/NVDAStartupWeb.kext sudo touch /System/Library/Extensions && sudo kextcache -u / sudo touch /Library/Extensions && sudo kextcache -u / vii.) Reboot. viii.) The patched Web Driver might not be active yet. Therefore, open the Nvidia Driver Manager and select "Nvidia Web Driver". ix.) Now reboot as requested and you will have a fully functional patched Web Driver for MacOS Mojave 10.14.1. E.3) Audio Configuration My actual respective X99 EFI-Folder distribution contains an already fully functional AppleALC audio configuration. The latter consist of: 1.) Actual versions of codeccommander.kext, AppleALC.kext and Lilu.kext in "/EFI/CLOVER/kexts/Other/ 2.) Note that ALZA -> HDEF ACPI patch needs to be added to the config.plist in Section "ACPI" of Clover Configurator, in case one does not use the adopted system SSDT discussed in Section 9.2). Comment: Find: Replace: ALZA -> HDEF 414c5a41 48444546 3.) Audio ID Injection "5" in the config.plist under Audio/Inject in Section "Devices" of Clover Configurator. This audio configuration provides a correct analogue onboard audio chipset system implementation. The correct digital HDMI/DP HDAU PCI device implementation will be detailed in Section E.9) in line with the HDEF and GPU PCI device implementation. Thanks to @nmano for helping me with the initial AppleALC audio setup for 10.14 Mojave. E.4) USB Configuration Since 10.13.SU and with AppleIntelPCHPMC, macOS should properly implement all external and internal XHC USB 3.0 (USB 3.1 Gen 1 Type-A) and USB 2.0 (USB 2.0 Gen 1 Type-A) connectors, always provided that one uses working USB port limit patches. Valid USB port limit patches for 10.14.3 provided by ©ydeng and hardwired but yet disabled in my respective EFI-Folder distribution: kext : com.apple.iokit.IOUSBHostFamily Find : 83FB0F0F 871604 00 Replace : 83FB3F0F 871604 00 Name : USB Port Limit Patch 1 ©ydeng kext : com.apple.driver.usb.AppleUSBXHCI Find : 83FB0F0F 838F0400 00 Replace : 83FB3F0F 838F0400 00 Name : USB Port Limit Patch 2 ©ydeng kext : com.apple.iokit.IOUSBHostFamily Find : 83E30FD3 E34109DF Replace : 83E33FD3 E34109DF Name : USB Port Limit Patch 3 ©ydeng Valid USB port limit patch for 10.14.4 Beta1 provided by @PMHeart and hardwired but yet disabled in my respective EFI-Folder distribution: kext : com.apple.iokit.IOUSBHostFamily Find : 83FB0F0F 870B0400 00 Replace : 83FB3F0F 870B0400 00 Name : USB Port Limit Patch 1 ©PMHeart kext : com.apple.driver.usb.AppleUSBXHCI Find : 4183FF0F 0F839404 0000 Replace : 4183FF3F 0F839404 0000 Name : USB Port Limit Patch 2 ©PMHeart kext : com.apple.iokit.IOUSBHostFamily Find : 83E30FD3 E34109DF Replace : 83E33FD3 E34109DF Name : USB Port Limit Patch 3 ©PMHeart However, it is strongly recommended to use board-specific XHC USB kexts in addition. Such board-specific XHC USB kexts can be easily created for any motherboard of any brand by following my respective XHC USB Kext Creation guideline. Being mainboard specific, a XHC USB kext is only valid for one particular mainboard model although users of the same mainboard model naturally can share the same XHC USB kext, if complete and properly implemented without any additional efforts. KGP-iMacPro-ASUS-X99AII-XHCI.kext would be the XHC USB kext for the ASUS X99-A II with all 20 ports implemented. However, it is strongly recommend to keep respective USB port limit patches disabled and to use a truncated 15-port kext instead, which might avoid buffer overruns and makes your system more vanilla with respect to future macOS updates. For the truncated 15-port kext, we have to drop some of the 20 HS and SS ports implemented from the kext to stay within Apple's 15 USB port limit. For truncating a fully implemented XHC USB kext (all 20 HS and SS ports implemented), I usually recommend to drop one out of usually two internal USB3.0 connectors (which already reduces the number of implemented ports to 16 for the ASUS ASUS X99-A II): To remain within the 15 USB port limit, I also recommend to drop one of the four USB2.0 ports at the backside of the mainboard from the kext (HS05, HS06, HS13 or HS14), which further reduces the number of implemented USB ports by one. Thus, in total we have now 15 implemented HS and SS ports and we just stay within the 15 USB port limit. In the truncated KGP-iMacPro-ASUS-X99AII-XHCI-15port.kext attached below, I removed HS03, HS04, SSP3, SSP4 (assigned to the internal USB3.0 header USB3_34) and HS05 (assigned to the most right USB2.0 connector in the second column from top on the back panel of the mainboard) from the kext. By this, all other USB2.0 and USB3.0 ASUS-A II onboard connectors remain fully functional. Alternatively, one could also drop e.g. HS01, HS01, SSP1, SSP1 (assigned to the internal USB3.0 header USB3_12) and either HS13, HS14 or HS06 from KGP-iMacPro-ASUS-X99AII-XHCI.kext. Up to your personal taste. All experienced users are kindly invited to provide their fully implemented XHC USB kext and truncated 15-port XHC USB kext for a motherboard not yet being part of the respective XHC USB Kext Library with an implemented port-layout.rtf and by else following the correct kext nomenclatures defined in my XHC USB Kext creation guidelines in line with full motherboard and SMBIOS denominations. Remaining USB ejection issues during sleep/wake likely can be fixed by 3rd party software tools like e.g. mountain.app E.5) M.2/NVMe Configuration In contrary to macOS Sierra 10.12, and like already in case of macOS High Sierra 10.13, also macOS 10.14 Mojave provides native support of non-4Kn NVMe SSDs, like my Samsung EVO 960 M.2/NVMe. All patches applied under macOS Sierra 10.12 are obsolete. The native support of non-4Kn NVMe SSDs enables the unique opportunity to directly perform a clean-install of macOS High Sierra 10.13 on M.2 NVMEs like the Samsung EVO 960. The only current drawback consists in the external drive implementation of NVMEs. This minor issue should be easily solved by adding the actual External NVME Icon KextToPatch entry to the config.plist by means of the Clover Configurator. [code] Name* Find* [HEX] Replace* [HEX] Comment IONVMeFamily 4885c074 07808b20 4885c090 90808b20 External NVME Icon Patch[/code] Not however that within the actual 10.14 Mojave distribution, this approach does not seem to work anymore, despite the KextToPatch entry detailed above. If you still have your NVMe implemented in form of an external drive you have to perform the following workaround, detailed below. 1.) Disable the not working External NVME Icon KextToPatch entry. 2.) Open the IORegistryExplorer, in the upright search field type nvme and take not of values in the left column, i.e. indicated as v.1, v.2 and v.3 and marked by red rectangles in the figure below. As you can see by following these entries, your nvme device shows up in PCI0@0 > BR1B@1,1 > H000@0 3.) Download and unzip the SSDT-NVMe-extern-icon-patch.aml.zip, and open the SSDT-NVMe-extern-icon-patch.aml with MaciASL-DSDT.app, both attached towards the end of this guide. For deviating system configurations, replace the values highlighted in blue color in the figure below with those of your IOReg, marked by red rectangles and indicated by v.1, v.2 and v.3 in the figure of my IOReg above. 4.) Save and copy the modified SSDT-NVMe-extern-icon-patch.aml to the /EFI/CLOVER/ACPI/patched/ folder of your system drive. 5.) Reboot Now your NVMe drive should correctly show up as internal. E.6) SSDT/NVMe TRIM Support Macs only enable TRIM for Apple-provided solid-state drives they come with. If you upgrade a Mac with an aftermarket SSD/NVMe, the Mac won’t use TRIM with it. The same applies for SSDs/NVMes used by a Hackintosh. When an operating system uses TRIM with a solid-state drive, it sends a signal to the SSD/NVMe every time you delete a file. The SSD/NVMe knows that the file is deleted and it can erase the file’s data from its flash storage. With flash memory, it’s faster to write to empty memory — to write to full memory, the memory must first be erased and then written to. This causes your SSD/NVMe to slow down over time unless TRIM is enabled. TRIM ensures the physical NAND memory locations containing deleted files are erased before you need to write to them. The SSD/NVMe can then manage its available storage more intelligently. Note that the config.plist of my actual respective X99 EFI-Folder distribution contains an SSD/NVMe "TRIM Enabler" KextsToPatch entry, which can be found in the " Kernel and Kext Patches" Section of the Clover Configurator. Name* Find*[HEX] Replace*[HEX] Comment IOAHCIBlockStorage 4150504c 45205353 4400 00000000 00000000 0000 Trim Enabler With this KextToPatch entry, SSD/NVMe TRIM should be fully enabled also on your 10.14 System. See your Apple's System Report. E.7) GC-Titan Ridge / GC-Alpine Ridge or ASUS TBEX 3 Add-in PCIe Adapter Implementation For the successful implementation of the GC-Titan Ridge (recommended), GC-Alpine Ridge (compatible) or ASUS Thunderbolt EX3 (R.I.P) PCIe Add-In Adapters, a fully working Dual Boot System with an UEFI Windows Implementation is unfortunately absolutely mandatory. You will not be able to configure your Thunderbolt 3 Adapter in the mainboard BIOS, until the Adapter has been successfully recognised and initialised by the UEFI Windows System. Fortunately legal and official License Keys for the actual Windows 10 Pro distribution can be purchased with a little bit of temporal effort on Google for an actual price of 20 $ or even below! Thus, the installation of a dual boot system with Windows will require some additional temporal user effort but will not noticeably further affect the users's budget. Please note that I especially emphasize the term UEFI, when speaking about the parallel Windows implementation. Don't use or perform a Legacy Implementation of Windows! In order to properly implement your Windows partition later-on in the Clover Bootloader and to comply with the actual Mainbaord-BIOS settings requirements, it is absolutely mandatory to run or perform an UEFI Windows implementation! So if not already implemented, how to achieve a fully working UEFI Windows Implementation and Dual boot System with Windows? 1.) Important Note! For the implementation of the UEFI Windows Distribution disconnect all usually plugged macOSDrives from your rig! The Windows installer will implement a Windows Boot Loader! If you have any macOS Drive connected during installation, the latter Windows Boot Loader might overwrite and destroy your current Clover Boot Loader. This is the last thing you want! Thus for the windows installation just connect the destination drive for the installation and the Windows USB Flash Drive Installer your will create in the subsequent step below! 2.) This Tutorial explains in all necessary detail how to download an actual Windows 10 Creator distribution, and how tosubsequently create a bootable USB Flash Drive Installer for a subsequent UEFI Windows 10 installation by means RUFUS! Don't put emphasis on alternative optional methods and always take care that you just follow the instructions for a successful subsequent UEFI Windows Installation! 3.) This Tutorial explains in all necessary detail how to properly perform the actual Windows 10 Pro Creator UEFIInstallation, subsequent to the a bootable Windows USB Flash Drive Installer realisation detailed in 2.) above. 4.) This Tutorial explains in all necessary detail, how to migrate/clone/backup your Windows 10 UEFI System Disk afterinstallation for future maintenance and safety. 5.) After successfully performing the UEFI Windows 10 Pro Creator Implementation, you can reconnect your macOS driveto your rig. The newly created UEFI Windows 10 Pro Creator Partition will automatically appear as a further boot option in both BIOS Boot Option Menu (F8) and Clover Boot Menu! No additional or further actions or measurements have to be taken! 6.) Once your Windows 10 Pro Creator Partition is fully operational, install all mainboard drivers and programs implemented on the DVD attached to your mainboard. 7.) Now switch off your rig and start with the installation of our Thunderbolt 3 Add-In PCIe AdapterI recommend to install the Thunderbolt 3 Add-In PCIe Adapter in the 4th PCIe Slot from top, which is PCIEX_3 8.) Reboot into windows and install accompanying TB3 PCIe Drivers and Software.9.) Reboot and enter the Mainboard BIOS (F2)Go to /Advanced/ Thunderbolt(TM) Configuration/ and apply the following BIOS Settings detailed below: 10.) Shut down your rig, connect the Thunderbolt Device to your Thunderbolt 3 Adaptor and boot your system. 11.) You are done! Your Thunderbolt 3 Adapter and the connected device should now be fully implemented and functional.12.) We will add TB XHC USB and TB HotPlug functionality in Section E.9.2) of this guide. Note that with the GC-Titan Ridge, HotPlug functionality can be gained with the THB_C connected. For HotPlug with the other TB adaptors, the THB-C must be removed from most of the available mainboards. E.8) Gigabit and 10-Gbit Ethernet Implementations Section E.8.1) and and E.8.2.) below, describe in all necessary detail how to gain full Gbit and 10-Gbit LAN functionality on X99 systems. E.8.1) ASUS X99-A onboard Gbit functionality The Intel I218-V2 Gigabit on-board LAN controller of the ASUS X99-A II is implemented by means of IntelMausiEthernet.kext (already part of my EFI-Folder distributions). E.8.2) 10-Gbit Lan Implementations E.8.2.1) ASUS XG-C100C Aquantia AQC 10-Gbit NIC Starting with 10.13.2, there is native support for Aquantia based 10GBit network cards, which are implemented by means of a Apple Vanilla kext called "AppleEthernetAquantiaAqtion.kext", which is further part of "IONetworkingFamily.kext/Contents/PlugIns/" placed in /System/Library/Extensions/ (credits to @mikeboss). First success with the ASUS XG-C100C under MacOS 10.13.3 has been reported by @d5aqoep. @Mieze finally came up with a AppleEthernetAquantiaAqtion KextPatch for the use of the ASUS XG-C100C also under 10.13.4 and and later macOS versions. For further information and discussion see . How to successfully implement the ASUS XG-C100C AQC107 PCIe x4 10GBit Ethernet Adapter: 1.) A temporal macOS High Sierra 10.13.3 (17D2047 in case of the iMac Pro) installation is absolutely mandatory at first place. Only within the latter macOS High Sierra build, the ASUS XG-C100C will receive the proper AQC107 Apple firmware to be recognised and fully implemented by OSX. The firmware update will be performed during system boot. Several boot intents might be necessary until the firmware update finally succeeds. Only subsequently, the ASUS XG-C100C will be natively implemented in macOS High Sierra 10.13.3 and fully functional. 2.) To finally use the ASUS XG-C100C with macOS builds >10.13.4, one has to implement the following AppleEthernetAquantiaAqtion KextPatch provided by [USER=389154]@Mieze[/USER]: Name* Find*[HEX] Replace*[HEX] Comment AppleEthernetAquantiaAqtion 6275696C 742D696E 62626262 62626262 Aquantia "built-in" patch ©Mieze 3.) The proper XGBE ASUS XG-C100C PCI SSDT implementation is detailed in Section E.9.2) 4.) Note that after the firmware update under macOS High Sierra 10.13.3, the ASUS XG-C100C will refuse the official Windows Lan drivers provided by ASUS and will only work with Apple's customised Aquantia64.zip boot camp drivers attached below. E.8.2.2) Intel X540-T1 10-Gbit NIC Thanks to some Ubuntu EEPROM modding, I also achieved the successful implementation of the Intel X540-T1 single port 10GB LAN PCIe Adapter by means of the Small-Tree 10GB macOS 10.13 driver. Important additional notes to the EEPROM modding guideline linked above can be assessed in Section E.8.2.2) of my iMac Pro Skylake-XX299 macOS 10.14 Mojave Build and Desktop guide. The proper Intel X540-T1 PCI SSDT implementation is detailed in Section E.9.2) E.8.2.3) Small-Tree P2EI0G-2T 10-GBit NIC The Small-Tree P2EI0G-2T 2-Port 10GB LAN PCIe Adapter constitutes now the actual base line in my iMac Pro X299 10Gbit LAN configuration. It works OoB with the Small-Tree 10GB macOS 10.13 driver. The proper Small-Tree P2EI0G-2T PCI SSDT implementation is detailed in Section E.9.2) E.8.2.4) NetGear ProSave XS508M 8-port 10-Gbit Switch As already mentioned above, the NetGear ProSave XS508M 8-port 10GBit switch constitutes the turntable of my 10-GBit Ethernet Network. It further connects with a QNAP TS-431X2 Quad-core 4-Bay NAS tower with Built-in 10GbE SFP+ Port. E.8.2.5) QNAP TS-431X2 Quad-core 4-Bay NAS The QNAP TS-431X2 Quad-core 4-Bay NAS tower finally harbours 4x 12 TB Seagate IronWolf drives in RAID 0 configuration (as I rather opt for read/write speed than redundancy). E.8.2.5) 10-Gbit Ethernet Optimization 1.) Use SMB 3.0 instead of AFS for your Ethernet communication. 2.) Enable Jumbo Frames on your NAS and macOS network settings. 3.) The service order in your macOS network settings should have your 10-Gbit NIC at first position. 4.) You can turn off the SMB packet signing of the client and server in a secure network. Incoming SMB Enter the following terminal commands: sudo -s
 echo "[default]" >> /etc/nsmb.conf 
echo "signing_required=no" >> /etc/nsmb.conf 
exit Outgoing SMB: Enter the following terminal commands: smbutil statshares -a sudo defaults write /Library/Preferences/SystemConfiguration/com.apple.smb.server SigningRequired 0 E.9) ASUS X99-A II PCI Device Implementation In order to properly implement all PCI device drivers on his/her system and build, one needs adequate ACPI DSDT Replacements and a sophisticated system SSDTs. Both requirements have been originally successfully implemented for the ASUS Prime X299 Deluxe by our gorgeous @apfelnico with partial contributions of @TheOfficialGypsy. Many thanks for the extensive efforts and extremely fruitful and brilliant work! Subsequently, I adopted the ACPI DSDT Replacements and system SSDTs in concordance with SMBIOS iMacPro1,1. Some ACPI DSDT Replacements are still part of the config.plist contained in my actual respective X99 EFI-Folder distribution. Others are part of my System SSDTs provided in my X99-System-SSDTs Github repository. Note that the ACPI DSDT Replacements in config.plist, System SSDTs and TB-SSDTs are build and PCIe slot population dependent and have to be verified and adopted or modified for all mainboards different from the ASUS X99-A II and builds or PCIe slot populations different from the one that constitutes the baseline of this guide. For the ASUS X99-A II I will use in the following the PCIe Slot nomenclature depicted below: The verification and likely adaptation/modification can be performed by the help of IORegistryExplorer. How to adopted or modify the ACPI DSDT Replacement Patches and System SSDT implementations is detailed within this short guideline by means of the OSXWIFI PCIe Adaptor implementation in PCIe Slot-3. I hope that by this specific example it rapidly becomes evident that the correct PCI Device implementation cannot be outlined for each individual "build-in" or "slot-specific" PCI device within this guide. The complexity and effort would just exceed by far all available capacities and indeed require the implementation of a separate guide and thread in addition. I therefore hope on your skills and flexibility to extend and apply the approach and methodology detailed above to any other "build-in" or "slot-specific" PCI device yet to be adopted or implemented Important Note: It is strongly recommend to perform a stepwise SSDT PCI Device implementation, starting with one single specific PCI device. Once this PCI device has been successfully implemented, another SSDT PCI Device module can be added and verified. In case that the implementation of a specific PCI Device would be erroneous and fail, it would simply disappear from Section "PCI" of Apple's System report. To facilitate the stepwise PCI device implementation, the former SSDT-X99-iMacPro.aml has been split into separated modules now forming part of my X99-System-SSDTs Github repository. Also keep always in mind to modify/adopt the ACPI replacements in your config.plist in parallel when ever necessary! Note once more that the ACPI DSDT Replacements in config.plist and System SSDTs require SMBIOS iMacPro1,1. E.9.1) ACPI DSDT Replacement Implementation Note once more that all required ACPI DSDT Replacements are already implemented in the config.plist of my actual respective X99 EFI-Folder distribution or are directly part of of the System SSDTs provided in my X99-System-SSDTs Github repository. In the config.plist, the ACPI DSDT Replacements are disabled by default, thus we will now open the config.plist in the /EFI/CLOVER/ directory of our 10.14 System Disk EFI-Folder with Clover Configurator and stepwise adopt (if necessary) and enable the different required DSDT replacement patches in Clover Configurator Section "ACPI" under "DSDT patches", by also discussing their respective function and impact.. a.) OSI -> XOSI and EC0_ -> EC__ or H_EC -> EC__ are DSDT replacement patches to achieve consistency with a real Mac variable naming. i.) The XOSI functionality is required as explained by @RehabMan. Thus please enable the OSI -> XOSI DSDT Replacement patch. ii.) On the ASUS X99-A II and ASUS X99 Deluxe II we have EC0 and H_EC controllers, which have to be renamed to 'EC' for proper USB power management. Thus enable both EC0_ -> EC__ and H_EC -> EC__ DSDT Replacement Patches. Comment: Find*[Hex] Replace [Hex] OSI -> XOSI 5f4f5349 584f5349 EC0_ -> EC__ 4543305f 45435f5f H_EC -> EC__ 485f4543 45435f5f b.) The HEC1 -> IMEI and IDER->MEID DSDT Replacement patches are Intel Management Engine Interface related and are vital as MacOS requires the variable names "IMEI" and "MEID" to load the 'AppleIntelMEIDriver'. The latter functionality solves the 'iTunes/Apple Store Content Access Problem' which is discussed here. Please enable now both DSDT Replacement patches independent from your mainboard. Comment: Find*[Hex] Replace [Hex] HECI -> IMEI 48454331 494d4549 IDER->MEID 49444552 4d454944 c.) The LPC0 -> LPCB DSDT Replacement Patch is AppleLPC and SMBus related and is applied for consistency with the variable naming on a real Mac. Please enable now this DSDT replacement patch independent from your mainboard. Comment: Find*[Hex] Replace [Hex] LPC0 -> LPCB 4c504330 4c504342 d.) FPU_->MATH, TMR_->TIMR, PIC_->IPIC are all DSDT Replacement Patches for consistency with the variable naming on a real Mac. The variables are however functionless on either X99 systems or real Macs. Please enable now all three DSDT Replacement Patches independent from your mainboard. Comment: Find*[Hex] Replace [Hex] FPU_ -> MATH 4650555f 4d415448 TMR_ -> TIMR 544d525f 54494d52 PIC_ -> IPIC 5049435f 49504943 e.) The DSM -> XDSM DSDT replacement patch will be vital for loading the SSDT-ASUS-X99-A-II.aml, as all DSM methods used in the original DSDT do have a not compatible structure totally different from the real Mac environment. Without any fix, all DSM methods would be simply ignored. Note that one single device can have only one DSM method, which can assign additional properties to the respective device. Thus please enable the latter DSDT replacement patch completely independent from your mainboard! Comment: Find*[Hex] Replace [Hex] _DSM -> XDSM 5f44534d 5844534d f.) The 48 CPxx -> PRxx replacements are i7-6950X specific and result in a proper CPU core reordering as well as in a iMac Pro specific CPU core variable naming. All i7-6950X users can now enable all 48 CPxx -> PRxx replacements. All users of CPUs different from the i7-6950X have to adopt/modify the 48 CPxx -> PRxx replacements in concordance with their original IOREG CPU core values. Comment: Find*[Hex] Replace [Hex] CP00 -> PR00 43503030 50523030 CP01 -> PR01 43503031 50523031 CP02 -> PR02 43503032 50523032 CP03 -> PR03 43503033 50523033 CP04 -> PR04 43503034 50523034 CP05 -> PR05 43503035 50523035 CP06 -> PR06 43503036 50523036 CP07 -> PR07 43503037 50523037 CP08 -> PR08 43503038 50523038 CP09 -> PR09 43503039 50523039 CP0A -> PR10 43503041 50523130 CP0B -> PR11 43503042 50523131 CP0C -> PR12 43503043 50523132 CP0D -> PR13 43503044 50523133 CP0E -> PR14 43503045 50523134 CP0F -> PR15 43503046 50523135 CP10 -> PR16 43503130 50523136 CP11 -> PR17 43503131 50523137 CP12 -> PR18 43503132 50523138 CP13 -> PR19 43503133 50523139 CP14 -> PR20 43503134 50523230 CP15 -> PR21 43503135 50523231 CP16 -> PR22 43503136 50523232 CP17 -> PR23 43503137 50523233 CP18 -> PR24 43503138 50523234 CP19 -> PR25 43503139 50523235 CP1A -> PR26 43503141 50523236 CP1B -> PR27 43503142 50523237 CP1C -> PR28 43503143 50523238 CP1D -> PR29 43503144 50523239 CP1E -> PR30 43503145 50523330 CP1F -> PR31 43503146 50523331 CP20 -> PR32 43503230 50523332 CP21 -> PR33 43503231 50523333 CP22 -> PR34 43503232 50523334 CP23 -> PR35 43503233 50523335 CP24 -> PR36 43503234 50523336 CP25 -> PR37 43503235 50523337 CP26 -> PR38 43503236 50523338 CP27 -> PR39 43503237 50523339 CP28 -> PR40 43503238 50523430 CP29 -> PR41 43503239 50523431 CP2A -> PR42 43503241 50523432 CP2B -> PR43 43503242 50523433 CP2C -> PR44 43503243 50523434 CP2D -> PR45 43503244 50523435 CP2E -> PR46 43503245 50523436 CP2F -> PR47 43503246 50523437 Resulting CPU Core Implementation E.9.2) System SSDT PCI Device Implementation For the proper PCI device driver implementation (detailed in the figure above), we now have to revise and likely adopt or modify all System SSDTs provided within my X99-System-SSDTs Github repository. Note that each SSDT contains a DefinitionBlock entry and the underlying PCI device implementation. In case of necessary modifications/adaptations, don't forget to also modify/adapt the respective DefinitionBlock entries in concordance with your IOREG entries. The entire SSDT structure is now completely module like. Each module can be independently added, changed or removed in dependence of your specific build, needs and requirements. A stepwise implementation of the individual PCI device modules is highly recommended! E.9.2.1) HDEF - onboard Audio Controller PCI Implementation: The SSDT-X99-HDEF.aml onboard Realtek ALC 1150 Audio Controller HDEF PCI device implementation is valid for the ASUS X99-A II and likely for all other mainboards with the same Audio Controller chipset. It is a build in device and does not have any slot specific dependency. Note the ALZA -> HDEF ACPI Replacement within the SSDT! E.9.2.2) GFX0, HDAU - GPU and HDMI/DP Audio PCI implementation A.) AMD Radeon RX GPUsThe Github X99 SSDT repository now contains the following AMD GFX0, HDAU ASUS X-99-A II PCIe Slot-1 SSDTs:1.) SSDT-X99-Vega64.aml2.) SSDT-X99-Vega56.aml3.) SSDT-X99-Vega-Fontier.aml4.) SSDT-X99-RX580.aml5.) SSDT-X99-RX560.aml The SSDT-X99-Vega.aml GFX0 and HDAU PCI device implementation is valid for SMBIOS iMacPro1,1 (GFX0), the ASUS X99-A II and any Radeon RX Vega 64 GPU implemented in PCIe Slot 1. It is a build and PCIe slot population dependent device implementation. Vega GPU users with more than one graphics card, with a Vega graphics card in a PCIe slot different from PCIe Slot 1, or with a mainboard different from the ASUS X99-A II will have to adopt the respective device path entries PCI0.BR3C, H000, H001, D077 and respective ACPI replacements by following their respective IOREG entries. The above default Vega PCI device implementation performs an OC of an air-flow Nitro+ Vega 64 GPU of up to 1630 Mhz while considering an IDLE fan speed of 1500 Mhz. This seems sufficient to remain with GPU temps of about 80 deg C under GPU load conditions (e.g. Valley Benchmark), while not exceeding any comfortable noise level. The latter Vega properties are achieved by means of a sophisticated "PP_PhmSoftPowerPlayTable", "PP_DisablePowerContainment" and "PP_FuzzyFanControl" SSDT implementation. Everybody can change the respective Vega properties by means of VGTab-en.app, which provides a modified "PP_PhmSoftPowerPlayTable" (output-file VegaTab_64_data.txt), which can replace the "PP_PhmSoftPowerPlayTable", currently implemented in my SSDT-X99-Vega.aml distribution. E.g. users with a water-blocked Nitro+ Vega 64 like myself want to further screw the max. GPU OC frequencies, etc, while others might want to further improve the fan speed behaviour on air-flow Vegas.. Below the "PP_PhmSoftPowerPlayTable" for my custom water-blocked Sapphire Nitro+ Vega 64 8B (used on my Skylake-X/X299 system), with P7 Core Frequency of 1680 Mhz, P7 Core Voltage of 1200 mV, P3 Memory Frequency of 1050 Mhz and a Memory Voltage of 1350 mV. PP_PhmSoftPowerPlayTable: 0x9d, 0x02, 0x08, 0x01, 0x00, 0x5c, 0x00, 0x37, 0x07, 0x00, 0x00, 0xec, 0x2b, 0x00, 0x00, 0x1b, 0x00, 0x48, 0x00, 0x00, 0x00, 0x80, 0xa9, 0x03, 0x00, 0xf0, 0x49, 0x02, 0x00, 0x32, 0x00, 0x08, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x02, 0x01, 0x5c, 0x00, 0x36, 0x02, 0x2d, 0x02, 0x94, 0x00, 0x85, 0x01, 0xaf, 0x00, 0x19, 0x01, 0x7a, 0x00, 0x8c, 0x00, 0xa3, 0x01, 0x00, 0x00, 0x00, 0x00, 0x59, 0x02, 0x00, 0x00, 0x90, 0x00, 0x8f, 0x02, 0x54, 0x01, 0x2a, 0x01, 0x7e, 0x01, 0x00, 0x71, 0x02, 0x00, 0x71, 0x02, 0x02, 0x02, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x08, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x04, 0x00, 0x07, 0x00, 0x03, 0x00, 0x05, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x08, 0x20, 0x03, 0x84, 0x03, 0xb6, 0x03, 0xe8, 0x03, 0x1a, 0x04, 0x4c, 0x04, 0x7e, 0x04, 0xb0, 0x04, 0x01, 0x01, 0x46, 0x05, 0x01, 0x01, 0x84, 0x03, 0x00, 0x05, 0x60, 0xea, 0x00, 0x00, 0x00, 0xdc, 0x4a, 0x01, 0x00, 0x01, 0x00, 0x77, 0x01, 0x00, 0x02, 0x90, 0x91, 0x01, 0x00, 0x03, 0x6c, 0xb0, 0x01, 0x00, 0x04, 0x01, 0x08, 0xd0, 0x4c, 0x01, 0x00, 0x00, 0x00, 0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x88, 0xbc, 0x01, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x98, 0xfc, 0x01, 0x00, 0x02, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x90, 0x0e, 0x02, 0x00, 0x03, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xc4, 0x2f, 0x02, 0x00, 0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x70, 0x56, 0x02, 0x00, 0x05, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x60, 0x7a, 0x02, 0x00, 0x06, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x40, 0x90, 0x02, 0x00, 0x07, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x03, 0x60, 0xea, 0x00, 0x00, 0x00, 0xdc, 0x4a, 0x01, 0x00, 0x00, 0x90, 0x5f, 0x01, 0x00, 0x00, 0x00, 0x08, 0x28, 0x6e, 0x00, 0x00, 0x00, 0x2c, 0xc9, 0x00, 0x00, 0x01, 0xf8, 0x0b, 0x01, 0x00, 0x02, 0x80, 0x38, 0x01, 0x00, 0x03, 0x90, 0x5f, 0x01, 0x00, 0x04, 0xf4, 0x91, 0x01, 0x00, 0x05, 0xd0, 0xb0, 0x01, 0x00, 0x06, 0xc0, 0xd4, 0x01, 0x00, 0x07, 0x00, 0x08, 0x6c, 0x39, 0x00, 0x00, 0x00, 0x24, 0x5e, 0x00, 0x00, 0x01, 0xfc, 0x85, 0x00, 0x00, 0x02, 0xac, 0xbc, 0x00, 0x00, 0x03, 0x34, 0xd0, 0x00, 0x00, 0x04, 0x68, 0x6e, 0x01, 0x00, 0x05, 0x08, 0x97, 0x01, 0x00, 0x06, 0xec, 0xa3, 0x01, 0x00, 0x07, 0x00, 0x01, 0x68, 0x3c, 0x01, 0x00, 0x00, 0x01, 0x04, 0x3c, 0x41, 0x00, 0x00, 0x00, 0x00, 0x00, 0x50, 0xc3, 0x00, 0x00, 0x00, 0x00, 0x00, 0x60, 0x35, 0x01, 0x00, 0x01, 0x00, 0x00, 0x28, 0x9a, 0x01, 0x00, 0x02, 0x00, 0x00, 0x01, 0x08, 0x00, 0x98, 0x85, 0x00, 0x00, 0x78, 0xb4, 0x00, 0x00, 0x60, 0xea, 0x00, 0x00, 0x50, 0xc3, 0x00, 0x00, 0x01, 0x78, 0xff, 0x00, 0x00, 0x40, 0x19, 0x01, 0x00, 0xb4, 0x27, 0x01, 0x00, 0x50, 0xc3, 0x00, 0x00, 0x02, 0x80, 0x38, 0x01, 0x00, 0xdc, 0x4a, 0x01, 0x00, 0xdc, 0x4a, 0x01, 0x00, 0x50, 0xc3, 0x00, 0x00, 0x03, 0xdc, 0x4a, 0x01, 0x00, 0x90, 0x5f, 0x01, 0x00, 0x90, 0x5f, 0x01, 0x00, 0x50, 0xc3, 0x00, 0x00, 0x04, 0x90, 0x5f, 0x01, 0x00, 0x00, 0x77, 0x01, 0x00, 0x90, 0x5f, 0x01, 0x00, 0x50, 0xc3, 0x00, 0x00, 0x05, 0x00, 0x77, 0x01, 0x00, 0x90, 0x91, 0x01, 0x00, 0x90, 0x5f, 0x01, 0x00, 0x50, 0xc3, 0x00, 0x00, 0x06, 0x6c, 0xb0, 0x01, 0x00, 0x6c, 0xb0, 0x01, 0x00, 0x00, 0x77, 0x01, 0x00, 0x50, 0xc3, 0x00, 0x00, 0x07, 0xc0, 0xd4, 0x01, 0x00, 0xc0, 0xd4, 0x01, 0x00, 0x90, 0x91, 0x01, 0x00, 0x50, 0xc3, 0x00, 0x00, 0x01, 0x18, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x0b, 0xe4, 0x12, 0xdc, 0x05, 0xfc, 0x08, 0x41, 0x00, 0x0f, 0x00, 0x54, 0x03, 0x90, 0x01, 0x90, 0x01, 0x90, 0x01, 0x90, 0x01, 0x90, 0x01, 0x90, 0x01, 0x90, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x02, 0x04, 0x21, 0x07, 0x08, 0x01, 0x08, 0x01, 0x08, 0x01, 0x2c, 0x01, 0x00, 0x00, 0x4a, 0x00, 0x69, 0x00, 0x4a, 0x00, 0x4a, 0x00, 0x5f, 0x00, 0x73, 0x00, 0x73, 0x00, 0x64, 0x00, 0x40, 0x00, 0x90, 0x92, 0x97, 0x60, 0x96, 0x00, 0x90, 0x46, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x02, 0x02, 0xd4, 0x30, 0x00, 0x00, 0x02, 0x10, 0x60, 0xea, 0x00, 0x00, 0x02, 0x10 Note that I also changed the Nitro+ Vega 64 firmware to https://www.techpowerup.com/vgabios/200283/200283 (at BIOS jumper position 1). Don't forget to backup the original firmware, in case you return it to the seller! This thread might provide additional information in this context: https://forums.macrumors.com/threads/amd-polaris-vega-gpu-macos-support.2083168/. As already mentioned before, within my current Vega SSDT PCI device implementation, 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 v.1.2.1. 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). 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. SSDT-X99-Vega-Frontier.aml contains former Kamarang frame buffer SSDT implementation by @apfelnico for 1x Radeon Vega Frontier in PCIe Slot 1 of ASUS X99-A II. B.) Nvidia GPUs The actual SSDT-X99-Nvidia.aml GFX0 and HDAU PCI device implementation is valid for SMBIOS iMacPro1,1 (GFX0), the ASUS X99-A II and any Nvidia Graphics Card implemented in PCIe Slot 1. It is a build and PCIe slot population dependent device implementation. Nvidia Graphics Card users with more than one GPU, with a Nvidia graphics card in a PCIe slot different from PCIe Slot 1 or on a mainboard different from ASUS, will have to adopt the respective PCI0, BR3C, H000, H001, D077, GFX0 ACPI path and ACPI replacements following their respective IOREG entries. Also note that with 10.13.4, Apple changed the com.apple.driver.AppleHDAController implementation. To make the NVIDIA HDAU PCI device driver work for e.g. a GeForce GTX 1080 Ti, one needs to add the following KextToPatch entry in Section "Kernel and kext Patches" of Clover Configurator, as already implemented but yet disabled in the config.plist contained in my actual respective X99 EFI-Folder distribution: Name* Find* [HEX] Replace* [HEX] Comment com.apple.driver.AppleHDAController DE100B0E DE10EF10 FredWst DP/HDMI patch Thus, please all Nvidia users enable and like adopt the NVIDIA HDAU patch for your particular Nvidia GPU in dependence of the respective device-id. Credits to @FreedWst and thanks to @fabiosun for pointing me to this solution. With Whatevergreen.kext, mis Nvidia users might be able to drop this KextToPatch entry, as the latter kext already properly implements the Nvidia HDAU PCI driver E.9.2.3) XGBE - 10GBit NIC PCI Implementation: SSDT-X99-ACQU.aml, SSDT-X99-X540-T1.aml and SSDT-X99-P2EI0G-2T.aml perform a 10-Gigabit NIC XGBE (XGBF) PCI implementation of an Acquantia AQC107-AFW, Intel X540-T1 or Small-Tree P2EI0G-2T 10GB NIC, respectively and are mainly of cosmetic nature. For each PCIe Adapter and for different PCIe slot populations or mainboard implementations, the XGBE PCI device implementation needs to be adopted/modified accordingly. This also states for the respective ACPI path entries "PCI0", "BR3A" and respective H000 -> D07C and D07C -> XGBE ACPI Replacements (in compliance with the iMac Pro 10GB ACPI variable nomenclature), directly performed within each SSDT. Those not employing any 10-GBit NIC in their system, can simply skip the corresponding SSDT PCI device implementation. E.9.2.4) ETH0 - onboard LAN Controller PCI Implementation: The SSDT-X99-ETH0.aml onboard Intel i218-V Ethernet controller ETH0 PCI implementation is of pure cosmetic nature and valid for the ASUS X99-A II or X99 mainboards with the same LAN Controller configuration. Owners of different X99 mainboards have to verify and adopt/modify the ACPI path and the PCI device implementations by means of their IOREG entries. Note the GLAN -> ETH0 ACPI replacement directly performed within the SSDT. E.9.2.5) SAT1 - Intel AHCI SATA Controller PCI Implementation: The SSDT-X99-SAT1.aml onboard Intel AHCI SATA controller SAT1 PCI device implementation is valid for the ASUS X99-A II and for all other X99 mainboards with the same AHCI SATA controller chipset. E.9.2.6) EVSS - Intel X99 sSata Controller PCI Implementation: The SSDT-X99-EVSS.aml onboard Intel X99 sSATA controller EVSS PCI device implementation is valid for the ASUS X99-A II and for all other X99 mainboards with the same X99 sSATA controller chipset. Verify and adopt/modify if necessary device path "PCI0.EVSS" and PCI device implementations by means of IOREG. E.9.2.7) ANS1 - NVMe Controller PCI Implementation: The SSDT-X99-ANS1.aml Apple NVMe Controller ANS1 PCI implementation is of purely cosmetic nature and is valid for the ASUS X99-A II. Note ACPI Replacements D075 -> D081 and D081 -> ANS2 directly performed within the SSDT, in concordance with the respective SMBIOS iMacPro1,1 variable naming! E.9.2.8) - USBX: When using the XHCI device name for USB (see the XHCI PCI Device Implementation below), one observes a bunch of USB Power Errors when booting the system. The SSDT-X99-USBX.aml PCI device implementation fixes this errors. E.9.2.9) XHCI - onboard Extended Host Controller Interface (XHCI) PCI Implementation: The SSDT-X99-XHCI.aml onboard USB3.0 controller XHCI PCI device implementation is valid for the ASUS X99-A II and for all other X99 mainboards with the same XHCI controller chipset. Verify and adopt/modify if necessary device path "PCI0.XHCI" and PCI device implementations by means of IOREG. E.9.2.10) XHC2 - ASMedia ASM1142 USB 3.1 Controller PCI Implementation: The SSDT-X99-XHC2.aml onboard ASMedia ASM1142 USB 3.1 AHCI SATA controller XHC2 PCI device implementation is valid for the ASUS X99-A II and for all other X99 mainboards with the same XHC USB3.1 controller chipset configuration. Note the D07D -> D082 and D082 -> XHC2 ACPI replacements directly performed within the SSDT! E.9.2.11) ARPT - OSX WIFI Broadcom BCM94360CD 802.11 a/b/g/n/ac + Bluetooth 4.0 AirPort Controller PCI Implementation: The SSDT-X99-ARPT.aml OSX WIFI Broadcom BCM94360CD 802.11 a/b/g/n/ac + Bluetooth 4.0 AirPort Controller PCI device implementation is of pure cosmetic nature and only valid for users of the latter WIFI/Bluetooth PCIe Adapter in PCIe Slot 5 of the ASUS X99-A II. Users of this PCIe Adapter within a PCIe slot population different from PCIe Slot 5 or on a mainboard different form the ASUS X99-A II have to likely adapt/modify the respective device path "PCI0","RP07","ARPT". Users with a completely different WIFI/Bluetooth configuration have to adopt the entire Airport PCI implementation by means of IOREG. E.9.2.12) GC-Titan Ridge / GC-Alpine Ridge / ASUS TBEX 3 Thunderbolt HotPlug System Implementation: The current Thunderbolt development carefully focuses on iMac Pro SSDT-9.aml and DSDT.aml from @TheOfficialGypsy 's iMac Pro dump, which appear to be the cornerstone for a correct, proper and complete Thunderbolt Hackintosh Local Node implementation. The current development status is briefly reflected in posts and Constructive contributions by experts are highly desired. Until reaching a complete Thunderbolt Hackintosh Local Node implementation, SSDT-X99-TB3HP-TTR.aml (for GC-Titan Ridge and ASUS TBEX 3) and SSDT-X99-TB3HP-APR.aml (for GC-Alpine Ridge) constitute workarounds for achieving TB HotPlug and TB XHC USB HotPlug functionality with the respective TB3 PCIe Add-In adopters. Note once more that with the GC-Titan Ridge, HotPlug functionality can be reached with the THB_C connected. For HotPlug with the other TB adaptors, the THB_C must be removed from most of the available mainboards.For all TB3 SSDTs provided above, partial contributions by by @apfelnico, @nmano, @Mork vom Ork, @Matthew82, @maleorderbride and @TheRacerMaster shall be mentioned and outlined. Their use with mainboards different from ASUS and within PCIe slot populations different from PCIe Slot 4 requires the adaptation/modification of respective ACPI path definitions ("PC01", "BR1A") or ACPI DSDT Table replacements (SL01 -> PEGP and PEGP -> UPSB), directly performed within the SSDTs. >>> https://youtu.be/Jakp5dCoFvY <<< E.9.2.13) DTGP Method: SSDT-DTPG.aml is mandatory for all SSDT implementations listed above (note the external DTPG method call in the definition block of each respective SSDT) and must be always part of /EFI/Clover/ACPI/patched.. External (DTGP, MethodObj) // 5 Arguments (from opcode) E.9.2.14) - Debugging Sleep Issues For debugging sleep issues as proposed by Pike Alpha, one can add SSDT-SLEEP.aml to /EFI/CLOVER/ACPI/patched and follow Pike's comment and advices provided at https://pikeralpha.wordpress.com/2017/01/12/debugging-sleep-issues/ E.10) iMac Pro Boot Splash Screen Cosmetics Based on the ideas and instructions of @Matthew82, I achieved an iMacPro ASUS Boot Splash Screen by means of the following procedure: 1.) Installation of the BREW distribution: a.) Open a terminal and change to "bash" shell. bash b.) Now enter the following "bash" terminal command and follow the standard BREW installation instructions: /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" 2.) After the successful installation of the BREW distribution, we have to implement the QT5 distribution, again by using a "bash" terminal shell. Enter the following "bash" terminal commands: brew install qt5 brew link qt5 --force 3.) After successfully implementing BREW and QT5 and if not already performed in Section B.1), we can now download the actual CodeRush UEFIPatch distribution from Github to our home directory with the following terminal command: git clone https://github.com/LongSoft/UEFITool 4.) Now compile the UEFI Tool distribution with the following terminal commands: cd /UEFITools/ qmake uefitool.pro make 5.) Download and unzip iMacPro.raw to your Desktop. 6.) Now launch by UEFITool by clicking on the newly compiled UEFITool.app in the UEFITools Folder in your home directory. a.) Select "File" -> "Open image file" and load your patched or unpatched BIOS Firmware distribution. Select "Search.." in the UEFITool "Edit" Menu and perform a "GUID" search of "7BB28B99-61BB-11D5-9A5D-0090273FC14D" with "Header only"... You will receive a message "GUID pattern "7BB28B99-61BB-11D5-9A5D-0090273FC14D" found as .... in 7BB28B99-....". Double click on that message and search for the "Raw section" accompanying the "7BB28B99-...." entry, which indeed is the Boot Image, which you can easily verify by extracting the raw section body (right-click on "Raw section" and select "Extract body") to your Desktop and by subsequently opening the extracted raw-file directly with Apple's "Preview.app" (right-click an the raw file and select "Open with.." -> Preview.app). b.) To exchange the default original ASUS Boot Logo image file stored in "Raw Section" by the iMacPro.raw image file that you previously downloaded to your Desktop, right-click again on "Raw section", select this time "Replace body" and select the iMacPro.raw image file on your Desktop. Note that the actual image dimension of iMacPro.raw (2131pix x 1457pix) was adopted for its use on my 38" LG 38UC99. For monitors with reduce screen resolution, iMacPro.raw might have to be adopted to an image dimension that suites your particular screen resolution, before its upload to "Raw section". If the Boot Logo image dimension is too big for your Monitor's screen resolution, you might just end up with a black screen during the BIOS initialisation at boot. To do so, select in the Preview.app Menu -> "Tools" -> "Adjust Size". Change the image dimension and save the modified image with "File" -> "Export". In the "Export menu" press "Save", after selecting "JPEG" under "Format" , after choosing "Desktop" as the place to store the image, and after entering the new file name, which has to end with ".jpg". Double-check by right-clicking on the resulting jpg image file and selecting "Get Info" that its file size does no exceed 200KB by far. If the latter would be the case, you would not be able to save the modified BIOS Firware file subsequently. Finally just rename your new "XXXX.jpg" file to "XXXX.raw.... I guess, that by following the procedure detailed above, it is obvious that iMacPro.raw also can be substituted by any other image of your personal choice. Just be aware that it's background colour should be black (ecstatic reason for a its nice integration within the else black ASUS BIOS Boot Screen) c.) After replacing "Raw Section" with iMacPro.raw or the XXX.raw image of your choice, save your modified BIOS Firmware File with the Option "File" -> "Save Image File..." d.) Copy your modified BIOS Firmware file to a USB3.0 Flash Drive, formatted with FAT32. e.) Reboot, enter the Mainboard BIOS and save your BIOS settings to the USB Flash Drive f.) Flash your mainboard BIOS with the modified BIOS Firmware g.) Renter the Mainboard BIOS and restore your BIOS settings from the USB Flash Drive h.) Save your restored BIOS settings with (F7) and (F10), reboot and you are done. Just don't forget to set BIOS Setting "Boot Logo Display" to "Auto", when using this new approach. Any different setting might result in a black screen during BIOS initialisation. E.11) iMac Pro Desktop Background Cosmetics It might be nice to equip your iMac Pro X299 also with the adequate iMac Pro Desktop Background. 1.) Download, unzip and copy imac-pro-wallpaper.jpg.zip to your Dektop 2.) Right-click with the mouse on your Desktop and select "Change Desktop Background.." 3.) In the left column click on the "+" and add your Desktop Folder 4.) Select imac-pro-wallpaper.jpg to be your new Desktop Background E.12) iStatMenus Hardware Monitoring Thanks to extended tweet session between @BJango, @gxsolace and myself, we achieved a major step forward in properly monitoring Skylake-X/X299 Hardware with iStatMenus. iStatMenus v6.2 now correctly interfaces with the HWSensor and FakeSMC kext distribution provided by @interferenc and can now be also used for Broadwell-E/EP, Haswell-E/EP, X99 system monitoring. My distributed EFI-Folder already contains all necessary HWSensor and FakeSMC kexts. The actual iStatMenus v6.2 distribution can be assessed at https://bjango.com/mac/istatmenus/ The actual HWSensor and FakeSMC kext distribution of @interferenc can be separately assessed at https://github.com/interferenc/HWSensors. To compile the the HWSensor and FakeSMC kexts of @interferenc, perform the individual steps detailed below: 1.) git clone https://github.com/interferenc/HWSensors 2.) cp HWSensors ~/Desktop/ 3.) cd ~/Desktop/HWSensors 4.) xcodebuild -project Versioning\ And\ Distribution.xcodeproj/ 5.) xcodebuild -project HWMonitor.xcodeproj/ 6.) xcodebuild -project HWSensors.xcodeproj -alltargets Subsequently, one finds the all compiled binaries in ~/Desktop/HWSensors/Binaries/. Note that all compiled kext binaries are once more attached towards the bottom of this originating thread (guide). Just download and unzip HW-Sensors-IF.zip and copy all kexts to /EFI/Clover/kexts/Other/. Note that this pre-compiled binary package already implements a modified GPU Sensor kext of @Kozlek, which should also account for Polaris GPUs. Many thanks to both @interferenc and @Bjango for their awesome and extensive contributions and brilliant work! Broadwell-E/EP, Haswell-E/EP, X99 iStatMenus Hardware Sensor Data: Broadwell-E/EP, Haswell-E/EP CPU Thread Utilisation Graphs: To change from CPU core to thread utilisation monitoring, uncheck "Hide Hyper-Threading cores" in Section "CPU & GPU" of iStatMenus Preferences. Temperature unites can be adjusted between Celsius, Fahrenheit and Kelvin in Section "Sensors" of iStatMenus Preferences. F.) Benchmarking F.1) i7-6950X CPU Benchmarks F.2) Sapphire Nitro+ Radeon RX Vega 64 8GB (Air-Flow) OpenGL and Metal Benchmarks G.) Summary and Conclusions Already under macOS 10.12 Sierra and macOS 10.13 High Sierra, Broadwell-E/EP, Haswell-E/EP, X99 systems reached full functionality together with flawless stability. Now with macOS 10.14 Mojave, it might be another opportunity to follow my iMac Pro Build and Desktop Guide to unfold the unbelievable Broadwell-E/EP, Haswell-E/EP, X99 potential! High-end builds based on Broadwell-E/EP, Haswell-E/EP, X99 technology have found manifold application, not only in science and research at universities or research institutions, engineering facilities, or medical labs, etc... Broadwell-E/EP, Haswell-E/EP, X99 with up to 22 cores (44 threads) and turbo frequencies up to 4.4 GHz have made X99 to a "relatively cheap" but really serious alternative to real iMac Pro's and Mac Pro's. The principal intention of my desktop guides is to demonstrate, that we are able to build and configure fully functional and relatively "low-cost" high-end systems, which go far beyond of what Apple is able to offer at present or will be ever able to offer for some reasonable pricing. Broadwell-E/EP, Haswell-E/EP, X99 Systems that allow the use of all software-packages developed for MacOS, Unix, Linux or even Windows at the same time (e.g. think on Vine, Parallels, or a dual boot system configuration). The flexibility between different mainboards (Asus, Gigabyte, ASRock, MSI, etc.), different Broadwell-E/EP, Haswell-E/EP processors, and different RAM memory configurations (16-128GB) make such systems affordable for anybody (also home office, audio and video editing/production, etc.) and allows their perfect adaptation for each specific purpose, requirement and available budget. It might not be necessary to outline, that current Broadwell-E/EP, Haswell-E/EP, X99 Systems perform absolutely stable on a 24/7/365 basis. I am a scientist, expert in solar physics, space weather forecast and related telescope/instrument/space-mission development. In the frame of my scientific research, I developed parallelized image reconstruction, spectral line inversion and numerical modeling algorithms/applications, which require tremendous parallelized calculation power, RAM memory and storage capacities to reduce, analyze and interpret extensive and pioneering scientific ground-based or space-born observational data sets. This basically was also the professional motivation for developing innovative iMac Pro macOS Builds iSPOR-S (imaging Spectropolarimetric Parallel Organized Reconstruction Servers running iSPOR-DP, the Imaging Spectropolarimetric Parallel Organized Reconstruction Data Pipeline software package for the GREGOR Fabry-Pérot Interferometer, located at the 1.5m GREGOR Solar Telescope (Europe's largest solar telescope) on Tenerife, Canary Islands, Spain) as well as for the entire related iMac Desktop Guide Development, which naturally shall also be of benefit for others. Anybody interested can find more details on my personal webpage.
  2. Now have a Olarila app, just download app and clover folder for your Chipset! https://olarila.com/forum/viewtopic.php?f=81&amp;t=6771 Install MacOS with Olarila Image, Step by Step, Install and Post Install https://olarila.com/forum/viewtopic.php?f=50&t=8685 --Install Follow my tutorial and use my Clover folder http://www.insanelymac.com/forum/topic/323052-guide-sierra-high-sierra-on-intel-5-6-7-8-and-9-chipset-series-nehalem-sandybridge-ivybridge-haswell-broadwell/ CLOVER Install.zip --Post Install --Install Clover bootloader and replace with my folder CLOVER Post Install.zip Bingo! Now you need a fine tune! DSDT time! If you need edited DSDT... -Post your full Clover folder with original tables in Origin folder(Extract with F4 in Clover boot screen) -Post Ioreg, extract with Ioreg Explorer IORegistryExplorer.app.zip -Run it, post files generate in your desktop RunMe.app -DSDT bios F23 My DSDT DSDT.MaLd0n GA X99-UD3P.zip -Patches -FIX ERRORS AND WARNINGS -HPET -SATA -sSATA -DMAC -SLPB -DARWIN -LPC -XHCI -EHCI -PLUGIN TYPE -ALZA to HDEF -HDEF -RTC -IRQs -SBUS -BLC0 -BUS1 -MCHC -ALS0 -IMEI -SHUTDOWN -LAN -SPSR -EC -PNLF -HDMI e.g -Clover https://sourceforge.net/projects/cloverefiboot/files/Installer/ -FakeSMC https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek -Audio https://github.com/vit9696/AppleALC -USB https://bitbucket.org/RehabMan/os-x-usb-inject-all/downloads -LAN https://github.com/Mieze/IntelMausiEthernet -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders! Apple, Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, nmano and many, many, many others! We're all here to have fun and learn from each other!
  3. Running my hack now using the iMac Pro SMBIOS, as some may know 10.13.6 has killed Overclocking on most if not all machines. Would someone have a list of the performance patches ( @PMheart , @nmano ) that i can test? Maybe a list of 10.13.5 and list of 10.13.6 patches if possible...
  4. Hello, My desktop Hackintosh is running macOS Mojave 10.14.2 with two dedicated GPUs installed: NVIDIA GTX 1080 Ti, AMD Radeon HD 7970. The AMD GPU is used primarily under macOS and the NVIDIA one under Windows. macOS boots without issues as long as there are no displays connected to the NVIDIA GPU. If a display is connected then the display connected to the AMD GPU will become blank. The system can be accessed using Screen Sharing/VNC. There are no problems if I swap PCI-e slots for the GPUs so that the AMD GPU is in the first slot (primary GPU), but I prefer not to do this. I have tried to remove the whole PCI (bridge) device in the DSDT file and all the lines that refer to it. The PCI entries in ioreg and System Information are gone but System Information still shows an NVIDIA GPU under Graphics/Display. Many of the suggestions I have found in guides and forum posts do not seem to apply here. My problem with some of the guides and answers is that they give the solution without explaining how anything works, or they tell you what to do without explaining the reasons behind it. What else can I do? Thank you for any assistance you can provide! I have attached some files that may help you help me. DSDT_BIOS_3101.zip contains the original ACPI (*.aml) files without any patches. Send me Steffens-iMac.zip is a file produced by RunMe.app, and do contain simple patches to rename some devices. DSDT.dsl.patch is a diff of the original DSDT.dsl file and the one with the PCI devices removed (commented out). Motherboard: ASUS Rampage V Extreme (X99), BIOS version 3101 (macOS does not boot with anything newer). Clover version: 4813. DSDT.dsl.patch: --- /Users/sl/Desktop/DSDT_BIOS_3101/DSDT.dsl 2018-12-17 05:24:30.000000000 +0100 +++ /Volumes/EFI/EFI/CLOVER/ACPI/patched/DSDT.dsl 2018-12-17 16:52:08.000000000 +0100 @@ -5,7 +5,7 @@ * * Disassembling to symbolic ASL+ operators * - * Disassembly of DSDT.aml, Mon Dec 17 05:24:30 2018 + * Disassembly of DSDT.aml, Mon Dec 17 04:01:52 2018 * * Original Table Header: * Signature "DSDT" @@ -2128,7 +2128,7 @@ ^^PCI0.BR2B.OSHP () ^^PCI0.BR2C.OSHP () ^^PCI0.BR2D.OSHP () - ^^PCI0.BR3A.OSHP () + //^^PCI0.BR3A.OSHP () ^^PCI0.BR3B.OSHP () ^^PCI0.BR3C.OSHP () ^^PCI0.BR3D.OSHP () @@ -2274,7 +2274,7 @@ ^^PCI0.BR2B.OSHP () ^^PCI0.BR2C.OSHP () ^^PCI0.BR2D.OSHP () - ^^PCI0.BR3A.OSHP () + //^^PCI0.BR3A.OSHP () ^^PCI0.BR3B.OSHP () ^^PCI0.BR3C.OSHP () ^^PCI0.BR3D.OSHP () @@ -2420,7 +2420,7 @@ ^^PCI0.BR2B.OSHP () ^^PCI0.BR2C.OSHP () ^^PCI0.BR2D.OSHP () - ^^PCI0.BR3A.OSHP () + //^^PCI0.BR3A.OSHP () ^^PCI0.BR3B.OSHP () ^^PCI0.BR3C.OSHP () ^^PCI0.BR3D.OSHP () @@ -2570,7 +2570,7 @@ ^^PCI0.BR2B.OSHP () ^^PCI0.BR2C.OSHP () ^^PCI0.BR2D.OSHP () - ^^PCI0.BR3A.OSHP () + //^^PCI0.BR3A.OSHP () ^^PCI0.BR3B.OSHP () ^^PCI0.BR3C.OSHP () ^^PCI0.BR3D.OSHP () @@ -2803,12 +2803,14 @@ If ((CSTA (Arg0, Arg1) == 0x00)) { FLAG = 0x00 - PRID (APID = 0xFF) = 0xFF + APID = 0xFF + PRID = 0xFF } Else { Local0 = APID - PRID (FLAG = 0x01) = Local0 + FLAG = 0x01 + PRID = Local0 } Return (APIC) @@ -15259,7 +15261,7 @@ ^BR2B.OSHP () ^BR2C.OSHP () ^BR2D.OSHP () - ^BR3A.OSHP () + //^BR3A.OSHP () ^BR3B.OSHP () ^BR3C.OSHP () ^BR3D.OSHP () @@ -26861,7 +26863,7 @@ } } - Device (BR3A) + /*Device (BR3A) { Name (_ADR, 0x00030000) // _ADR: Address OperationRegion (MCTL, SystemMemory, 0xE0013188, 0x04) @@ -27496,7 +27498,7 @@ { Name (_ADR, 0xFFFF) // _ADR: Address } - } + }*/ Device (BR3B) { @@ -30267,7 +30269,7 @@ ^^PCI0.BR2B.OSHP () ^^PCI0.BR2C.OSHP () ^^PCI0.BR2D.OSHP () - ^^PCI0.BR3A.OSHP () + //^^PCI0.BR3A.OSHP () ^^PCI0.BR3B.OSHP () ^^PCI0.BR3C.OSHP () ^^PCI0.BR3D.OSHP () @@ -30567,21 +30569,21 @@ WordIO (ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange, 0x0000, // Granularity 0x4158, // Range Minimum - 0x0000, // Range Maximum + 0x4158, // Range Maximum 0x0000, // Translation Offset 0x0001, // Length ,, , TypeStatic, DenseTranslation) WordIO (ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange, 0x0000, // Granularity 0x5758, // Range Minimum - 0x0000, // Range Maximum + 0x5758, // Range Maximum 0x0000, // Translation Offset 0x0000, // Length ,, , TypeStatic, DenseTranslation) WordIO (ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange, 0x0000, // Granularity 0x5858, // Range Minimum - 0x0000, // Range Maximum + 0x5858, // Range Maximum 0x0000, // Translation Offset 0x0000, // Length ,, , TypeStatic, DenseTranslation) @@ -37604,7 +37606,7 @@ ^^PCI0.BR2B.OSHP () ^^PCI0.BR2C.OSHP () ^^PCI0.BR2D.OSHP () - ^^PCI0.BR3A.OSHP () + //^^PCI0.BR3A.OSHP () ^^PCI0.BR3B.OSHP () ^^PCI0.BR3C.OSHP () ^^PCI0.BR3D.OSHP () @@ -37904,21 +37906,21 @@ WordIO (ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange, 0x0000, // Granularity 0x4558, // Range Minimum - 0x0000, // Range Maximum + 0x4558, // Range Maximum 0x0000, // Translation Offset 0x0001, // Length ,, , TypeStatic, DenseTranslation) WordIO (ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange, 0x0000, // Granularity 0x4259, // Range Minimum - 0x0000, // Range Maximum + 0x4259, // Range Maximum 0x0000, // Translation Offset 0x0000, // Length ,, , TypeStatic, DenseTranslation) WordIO (ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange, 0x0000, // Granularity 0x4359, // Range Minimum - 0x0000, // Range Maximum + 0x4359, // Range Maximum 0x0000, // Translation Offset 0x0000, // Length ,, , TypeStatic, DenseTranslation) @@ -44941,7 +44943,7 @@ ^^PCI0.BR2B.OSHP () ^^PCI0.BR2C.OSHP () ^^PCI0.BR2D.OSHP () - ^^PCI0.BR3A.OSHP () + //^^PCI0.BR3A.OSHP () ^^PCI0.BR3B.OSHP () ^^PCI0.BR3C.OSHP () ^^PCI0.BR3D.OSHP () @@ -45241,21 +45243,21 @@ WordIO (ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange, 0x0000, // Granularity 0x4958, // Range Minimum - 0x0000, // Range Maximum + 0x4958, // Range Maximum 0x0000, // Translation Offset 0x0001, // Length ,, , TypeStatic, DenseTranslation) WordIO (ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange, 0x0000, // Granularity 0x4559, // Range Minimum - 0x0000, // Range Maximum + 0x4559, // Range Maximum 0x0000, // Translation Offset 0x0000, // Length ,, , TypeStatic, DenseTranslation) WordIO (ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange, 0x0000, // Granularity 0x4659, // Range Minimum - 0x0000, // Range Maximum + 0x4659, // Range Maximum 0x0000, // Translation Offset 0x0000, // Length ,, , TypeStatic, DenseTranslation) @@ -53823,7 +53825,7 @@ Notify (\_SB.PCI0.BR2D.H007, Local0) } - If ((\_SB.PCI0.BR3A.PMEP == 0x01)) + /*If ((\_SB.PCI0.BR3A.PMEP == 0x01)) { Local0 = \_SB.PCI0.BR3A.PMEH (0x05) } @@ -53848,7 +53850,7 @@ Notify (\_SB.PCI0.BR3A.H005, Local0) Notify (\_SB.PCI0.BR3A.H006, Local0) Notify (\_SB.PCI0.BR3A.H007, Local0) - } + }*/ If ((\_SB.PCI0.BR3B.PMEP == 0x01)) { @@ -54608,11 +54610,11 @@ \_SB.PCI0.BR2D.PMEP = 0x01 } - If ((Local1 == 0x07)) + /*If ((Local1 == 0x07)) { \_SB.PCI0.BR3A.PMES = 0x01 \_SB.PCI0.BR3A.PMEP = 0x01 - } + }*/ If ((Local1 == 0x08)) { @@ -54879,10 +54881,10 @@ Notify (\_SB.PCI0.BR2D, 0x02) } - If ((\_SB.PCI0.BR3A.DEVS () != 0x00)) + /*If ((\_SB.PCI0.BR3A.DEVS () != 0x00)) { Notify (\_SB.PCI0.BR3A, 0x02) - } + }*/ If ((\_SB.PCI0.BR3B.DEVS () != 0x00)) { @@ -55927,10 +55929,10 @@ { Notify (\_SB.PCI0.BR2D, 0x00) } - Case (0x28) + /*Case (0x28) { Notify (\_SB.PCI0.BR3A, 0x00) - } + }*/ Case (0x29) { Notify (\_SB.PCI0.BR3B, 0x00) @@ -56736,11 +56738,11 @@ } } - Scope (_SB.PCI0.BR3A) + /*Scope (_SB.PCI0.BR3A) { Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { - If ((Arg0 == ToUUID ("e5c937d0-3553-4d7a-9117-ea4d19c3434d") /* Device Labeling Interface */)) + If ((Arg0 == ToUUID ("e5c937d0-3553-4d7a-9117-ea4d19c3434d") / * Device Labeling Interface * /)) { If (((Arg1 == 0x02) && (Arg2 == 0x00))) { @@ -56765,7 +56767,7 @@ 0x00 }) } - } + }*/ Scope (_SB.PCI1.QR1A) { DSDT_BIOS_3101.zip Send me Steffens-iMac.zip DSDT.dsl.patch
  5. autantpourmoi

    Sleeping mode

    Hello , I just put a new M2 samsung ssd disk in my hack and a And rx 580 sapphire 8go and installed High Sierra 10.13.6 , everything seems ok except the sleeping mode When I go to sleeping mode , the 2 monitors will turn to sleeping mode and after 3 to 5 sec the computer too , but the computer restart in a kind os stand by mode while the monitors still black Is it a normal behaviour which I'm doubting about it , is there any way to keep the computer in sleep and reactivate it by keys? any help will be appreciated
  6. Hi there, I'm an Italian student who wants to try out Hackintosh. I'm struggling on this odissey since 3 weeks ago and now I decided to ask for your help. My aim is to get macOS High Sierra up and running on my X99 build. The specs are as follows: Intel Core i7 5820K@3.3GHz Overclocked to 4.2GHz; MSI X99S SLI Plus; Corsair Vengeance LPX DDR4@2133MHz Overclocked to 2400MHz (16GB); DeepCool Assassin II (Cooler); MSI GTX960 2GB OC Edition; SSD Samsung 850EVO 250GB; HDD Seagate Barracuda 2TB. As I said before I was struggling on this machine for 3 weeks with other guys that helped me a lot, but we can't get past the Reloc Block. With the most "successful" attempt we made, I eventually got it to the point you see in photo, after which it reboots in something like 2 or 3 seconds. In the attatched files you'll find the photo of the point where I was stuck (I apologize for the quality, if you need a more redable photo just ask and I'll take a shot) and the EFI used for that attempt. Thanks a lot to all of you for your help and support, if you need any additional information about my computer or the EFI Folder that you can't find in this post or its attatched files, don't hesitate to ask me, I'll be happy to answer. EFI.zip
  7. Good evening! There is a problem with the update from 10.9.4 to 10.9.5. My system asus x99-a 5820k GTX 760 The system drive MBR. Generally after this update the system not to boot. Thank God there is another disk with 10.9.4 which c is loaded. But I need that system(ssd-disk), did Everything as prescribed on Tonymac. Patched all. But some kekst does not allow the system to boot normally. Wrote what type GenericUSBXHCI.kext is not compatible. Before it was patched no more editing of kexts are incompatible. Is Clover and Chimera. Loaded with Clovera. Even priloga kexts which were the changes after the update. Help me to understand. Solved. Remove Cuda driver&
  8. Hi, After a successful installation of 10.10.5 on my x99 system there are still things to fix on post. I would appreciate every one's help and contribution to solve these problems. Needing to be fixed: Backlight/Brightness control Sleep/Wake (It doesn't sleep properly and doesn't wake up through mouse touch or keyboard) ThunderboltEX II isn't recognized being the great mystery of this build (devices are always plugged before booting, Bios Security ID is set to Legacy, the card is installed on Pcie x4_1 and recognized in Windows) AppleThunderboltNHI.kext was removed for faster booting Speedstep not accomplished Nvidia Driver - I can't select it at system preferences. OSX default driver assumes control. One of my software's displays the message "NO CUDA ACCELERATION HARDWARE DETECTED". config.plist.zip IoReg mac.zip SSDT-1.aml.zip 001_2016-04-15_22-27-13_MacPro6,1.zip
  9. Hello Community, I would like to share my El Capitan install guide for the owners of Asus X99-E WS with 5960X Cpu. There are a few guides around with 5960X install, unfortunately with this specific motherboard i couldn’t achieve any success. I always got reboot or freeze after PCI Configuration begin or other problems. Finally i succesfully installed El Capitan 10.11.6. So far everything looks great, no problem at all. Steep stepping is working too with the help of custom SSDT. I didn’t invent anything, just educated guesses and resources from community! Before begin, thank you for all talented people around like; Pike R. Alpha, Brumbaer, SammlerG, stinga11, chris1111, the Clover team and many more… My System Specs Are Asus X99-E WS Intel i7-5960X 64GB DDR4 Ram Nvidia Geforce TitanX 3 x SSD 6 x Hard Drive (4 of them in RAID 10) Noctua CPU and Case fans. The following features are operational: CPU energy management operation from 1.2Ghz to 3.8 GHz (Sleep not working. Black screen) 1 x Ethernet adapter with Gigabit Support (AppleIntelI210Ethernet) NVIDIA GeForce GTX TITAN X working correctly. (Tested with only DVI) USB3.0 and 2.0 ports available ALC 1150 Working Apple apps like FaceTime and iMessage working nicely. Requirements: 10.11.6 El Capitan app from Appstore Access to a Mac / Hackintosh with any version At least 8gb USB drive Latest Clover Bootloader (Mine was Clover_v2.3k_r3799) Clover Configurator (Mine was 4.33.0) AGDPfix.v1.3 (For MacPro 6,1 config. No need for Mac Pro 5,1 or older) Nvidia WebDriver-346.03.15f03.pkg (After install completed needs system security update to install) Cudadriver-8.0.46-macos.dmg CAUTION: Please don’t use my SSDT if your cpu is not overclocked to 3.8 Ghz. Please read SSDT part to regenerate yours. Step by Step USB Guide: Download all needed software to the computer you will use to prepare the USB stick. (Kexts and clover configs included with the topic) The USB stick will be erased. 1 - Start Disk Uitility Select the USB itself. 2 - Select Erase 1 Name: ElCapitan 2 Format: OS X Extended Journaled 3 Scheme: GUID Partition Map 4 Press Erase 4 Quit Disk Utility 3- Open Terminal a. Enter the following and press the <Return> key. sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/ElCapitan --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app —no-interaction Enter <Return> Enter Password Enter Y Enter <Return> Wait…. 4 - Start Clover Bootloader Installer a. Change install location to USB (ElCapitan) b. Customize Select Install for UEFI Booting Only In Drivers64UEFI only choose (DataHubDxe-64 and OsxAptioFixDrv-64) After finished use Clover Configurator to mount EFI drive or manually mount. (It is better to change USB EFI name to another like USBEFI or INSTEFI not mandatory) I include my INSTALL_CLOVER folder (please compare or just use this folder) (All necessary kexts are in CLOVER - Kexts - Other) Included Kexts are (FakeSMC.kext - USBInjectAll.kext - VoodooTSCSync.kext - XHCI-x99-injector.kext) PLEASE don’t forget this guide is only for 5960x and X99-E WS. So VoodooTSCSync.kext is changed to 15 Install USB Clover Config Tips: In this part I will explain my clover config. (This folder is already included. Maybe helpful for other x99 owners) 1 - ACPI a. DSDT Patches I have used these DSDT patches with XHCI-x99-injector.kext for USB3 support. (It is important to disable Asmedia USB3.0 Controller in BIOS only Intel is supported) EHC1 to EH01 find 45484331 replace 45483031 EHC2 to EH02 find 45484332 replace 45483032 XHCI to XH01 find 58484349 replace 58483031 b. SSDT Generate C and P states selected Halt Enabler selected 2 - Boot a. Flags -v -f npci=0x2000 nv_disable=1 3 - Kernel and Kext Patches AppleRTC and KernelHaswellE selected a. KextsToPatch IOPCIFamily 5960X Patch By Brumbaer AppleAHCIPort - External icons patch AppleUSBXHCIPCI - Patch 15 Port limit b. KernelToPatch OS 10.11.6 EIST Patch - fix MSR 0x01A0 by Pike R. Alpha 4 - RT Variables BooterConfig=0x28 CsrActiveConfig=0x67 5 - SMBIOS Macpro5,1 generated 6 - System Parameters Inject Kexts - Detect Inject System ID selected BIOS Guide: I have included my BIOS screenshots. My processor overclocked to 3.8 Ghz. In my opinion the most important thing is disabling Asmedia USB3.0 Controller in BIOS. Otherwise you will fail with PCI Root Configuration. Caution: By the way my bios Fan settings are custom made, don't use with yours. INSTALLING - Proceed with USB stick, boot into OS X installer, select your destination drive, format with Disk Utility if necessary, and reboot. - After boot don’t remove USB stick boot with it but this time select freshly installed OS X drive. - After successful login, install Clover bootloader with the same settings usb install PLUS select Install RC Scripts on Target Volume - Before restart use my OSX_CLOVER folder to replace you OSX EFI. (I used non default theme so it is better to change it to default or download mine.) FIXES - Sound ALC1150 Fix is already done with my OSX_CLOVER. I injected “1” id and used FixHDA. - Graphics Use Nvidia drivers then replace nv_disable=1 with nvda_drv=1. If you will use Macpro 6,1 please use AGDPfix.v1.3 - SSDT Please don’t use my SSDT in clover folder if your CPU is not overclocked to 3,8 Ghz. Use appropriate SSDT with your own settings. You can create your own SSDT before installing OS and replace with USB - CLOVER - ACPI - Patched. (Both for INSTALL and OS X EFI) Use piker alpha’s ssdt generation script from https://github.com/Piker-Alpha/ssdtPRGen.sh If your cpu is not overclocked, use this one for stock “ ./ssdtPRGen.sh -p ‘i7-5960X' -f 3000 -turbo 3500 ” Please enjoy your Hackintosh Yucel BIOS.zip INSTALL_CLOVER.zip OSX_CLOVER.zip
  10. So I am trying to install El Capitan on my system, and I keep getting stuck at the same spot, I have looked at many guides and it seems that I always get the same output. Firstly my specs: -Asus X99-Deluxe -GTX 980 -i7-5820K - 32GB DDR4-2133 And now for show and tell! I have tried and retried the ##### method (that program from tonymacx86 that apparently isn't liked 'round these parts), and the Clover method. I just tried the RampageDev guide, and you could say I made progress, cause now what ever I do I at least get to the following point!: http://i.imgur.com/De9X4Rw.jpg I have tried using -x, nv_disable=1 (with and without InjectNVIDIA), slide=0, dart=0, and npci=0x2000 and npci=0x3000, all give me the same output (in any combination). Does anyone (especially those with similar setups) have any ideas? UPDATE: Ok, so after changing USB headers on my board and retrying the front ports, I can get past the "Still waiting for root device" message! However now I get to these points: Booting with just -v, npci=0x2000 and kext-dev-mode=1 I get this: http://imgur.com/LXunuKm.jpg and with cpus=1 added I get the following: http://imgur.com/6SuTFLN.jpg In both cases the machine restarts after a second or two.
  11. I had been having this issue for a long time that it seemed randomly hits OsxAptioFixDrv: requested memory exceeds our allocated relocation block After retried many times, I found that adding any additional kext will cause this issue on my system at a certain point. before you try this possible solution, please make sure you tried: 1) kernel flag: slide=0 2) OsxAptinFix2Test3 solution. cuz on mamy mobos, those can just fix the issue. if you tried them and they don't solve your problem, please try this Clover build and let me know if it fixed your issue. My build is: MSI x99s SLI Plus mobo gtx 970 DDR4 memory 16gb nvidia web driver is installed. DOWNLOAD: https://www.dropbox.com/s/dugpjh7vx6xr0w8/Clover_v2.3k_r3168%20_0x4400.pkg?dl=0 Make sure to upgrade OsxAptioFixDrv when install.
  12. Hi all, this is my first post! I passed the two quizzes with ease, but was surprised that there were no questions regarding forum rules ;P Current setup: Asus X99 Deluxe II Intel 5930k Corsair Vengeance 2x16GB DDR4 3200 Samsung EVO 850 Pro 512GB - Windows 10 Drive Corsair HXi 1000​ My ultimate goal would to be able to dual boot into Windows or OS X depending on my needs. No overclocking, looking for stability (relative) here. I currently have a second EVO 850 that I am hoping to load with OS X El Capitan 10.11.x. I would highly prefer 10.11.x, but would be willing to settle for Yosemite if the install became too difficult. Worth noting: I have built computer all my life, I own a MacBook Pro, CSE student (2 semesters left) and am not afraid to dig into BIOS/kexts/EFI's, and I'm exited to be here With that out of the way I have three questions: Is this dual boot set up compatible with 10.11.x? Is this dual boot set up compatible with 10.10.x? If yes to 1 or 2 --- would it be easier to install OSX+boot loader+misc with the SSD mounted to my MacBook over a SSD<->USB cable OR to do the generic install method over a USB loaded with the install and EFI partition? Thanks for reading this, really. I've done a bunch of lurking, seen how far some people have gotten with X99 builds, but my inexperience with the subject matter has left me struggling to put together the fragmented and vague information I've found. Thanks again
  13. hello, I ran into an issue with my built on an Asus x99 deluxe (last firmware) and a 5930k cpu. if I enable only the 6 physical cores (clover bootflag cpus=6 out of 12) the machine runs stable and no issue whatsoever. as soon as I turn all the cores I experience random crashes and restart. has anyone any suggestions on this topic. thank you in advance
  14. Hi guys. Just got El capo 10.11.3 running pretty smoothly although some adjustments may be required. System specs: GA X99 gaming 5 F20bios Intel 5930k cpu running at 4ghz 64GB DDR4 2400mhz ram (shows up as ddr3 running at 2100mhz) Nvidia Titan X 12gb GPU Kinston SSD 240gb (win 10 running on separate M2 SSD, switching system using bios boot selection since clover does not see the M.2 chip) SMBios 5,1 (tried using 6,1 but always got the black screen, tried the fix by editing AppleGraphics-thingie but no luck) Geek bench scores are 25k using 64bit test Intel power gadget shows that speed stepping and cpu throttling is active and works This shows up in the kernel log at startup: 08 Feb 2016 15:23:10 kernel[0]: Longterm timer threshold: 1000 ms 08 Feb 2016 15:23:10 kernel[0]: mem_actual: 0x1000000000 08 Feb 2016 15:23:10 kernel[0]: legacy sane_size: 0xff8000000 08 Feb 2016 15:23:10 kernel[0]: PMAP: PCID enabled 08 Feb 2016 15:23:10 kernel[0]: PMAP: Supervisor Mode Execute Protection enabled 08 Feb 2016 15:23:10 kernel[0]: Darwin Kernel Version 15.3.0: Thu Dec 10 18:40:58 PST 2015; root:xnu-3248.30.4~1/RELEASE_X86_64 08 Feb 2016 15:23:10 kernel[0]: vm_page_bootstrap: 16335263 free pages and 409185 wired pages 08 Feb 2016 15:23:10 kernel[0]: kext submap [0x<ptr> - 0x<ptr>], kernel text [0x<ptr> - 0x<ptr>] 08 Feb 2016 15:23:10 kernel[0]: zone leak detection enabled 08 Feb 2016 15:23:10 kernel[0]: "vm_compressor_mode" is 4 08 Feb 2016 15:23:10 kernel[0]: multiq scheduler config: deep-drain 0, ceiling 47, depth limit 4, band limit 127, sanity check 0 08 Feb 2016 15:23:10 kernel[0]: standard timeslicing quantum is 10000 us 08 Feb 2016 15:23:10 kernel[0]: standard background quantum is 2500 us 08 Feb 2016 15:23:10 kernel[0]: WQ[lt_init]: init linktable with max:262144 elements (8388608 bytes) 08 Feb 2016 15:23:10 kernel[0]: WQ[wqp_init]: init prepost table with max:262144 elements (8388608 bytes) 08 Feb 2016 15:23:10 kernel[0]: mig_table_max_displ = 15 08 Feb 2016 15:23:10 kernel[0]: TSC Deadline Timer supported and enabled 08 Feb 2016 15:23:10 kernel[0]: kdp_core zlib memory 0x7000 08 Feb 2016 15:23:10 kernel[0]: "name" not a kext 08 Feb 2016 15:23:10 kernel[0]: "FailedCLUT" not a kext 08 Feb 2016 15:23:10 kernel[0]: "FailedImage" not a kext 08 Feb 2016 15:23:10 kernel[0]: Refusing new kext org.netkas.driver.FakeSMC, v1328.0: already have prelinked v1394.0. 08 Feb 2016 15:23:10 kernel[0]: NullCPUPowerManagement::init: properties=<ptr> 08 Feb 2016 15:23:10 kernel[0]: NullCPUPowerManagement::start 08 Feb 2016 15:23:10 kernel[0]: FakeSMCKeyStore: started 08 Feb 2016 15:23:10 kernel[0]: AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled 08 Feb 2016 15:23:10 kernel[0]: AppleACPICPU: ProcessorId=2 LocalApicId=2 Enabled 08 Feb 2016 15:23:10 kernel[0]: AppleACPICPU: ProcessorId=4 LocalApicId=4 Enabled 08 Feb 2016 15:23:10 kernel[0]: AppleACPICPU: ProcessorId=6 LocalApicId=6 Enabled 08 Feb 2016 15:23:10 kernel[0]: AppleACPICPU: ProcessorId=8 LocalApicId=8 Enabled 08 Feb 2016 15:23:10 kernel[0]: AppleACPICPU: ProcessorId=10 LocalApicId=10 Enabled 08 Feb 2016 15:23:10 kernel[0]: AppleACPICPU: ProcessorId=1 LocalApicId=1 Enabled 08 Feb 2016 15:23:10 kernel[0]: AppleACPICPU: ProcessorId=3 LocalApicId=3 Enabled 08 Feb 2016 15:23:10 kernel[0]: AppleACPICPU: ProcessorId=5 LocalApicId=5 Enabled 08 Feb 2016 15:23:10 kernel[0]: AppleACPICPU: ProcessorId=7 LocalApicId=7 Enabled 08 Feb 2016 15:23:10 kernel[0]: AppleACPICPU: ProcessorId=9 LocalApicId=9 Enabled 08 Feb 2016 15:23:10 kernel[0]: AppleACPICPU: ProcessorId=11 LocalApicId=11 Enabled 08 Feb 2016 15:23:10 kernel[0]: calling mpo_policy_init for TMSafetyNet 08 Feb 2016 15:23:10 kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet) 08 Feb 2016 15:23:10 kernel[0]: calling mpo_policy_init for AMFI 08 Feb 2016 15:23:10 kernel[0]: Security policy loaded: Apple Mobile File Integrity (AMFI) 08 Feb 2016 15:23:10 kernel[0]: calling mpo_policy_init for Sandbox 08 Feb 2016 15:23:10 kernel[0]: Security policy loaded: Seatbelt sandbox policy (Sandbox) 08 Feb 2016 15:23:10 kernel[0]: calling mpo_policy_init for Quarantine 08 Feb 2016 15:23:10 kernel[0]: Security policy loaded: Quarantine policy (Quarantine) 08 Feb 2016 15:23:10 kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993 08 Feb 2016 15:23:10 kernel[0]: The Regents of the University of California. All rights reserved. 08 Feb 2016 15:23:10 kernel[0]: MAC Framework successfully initialized 08 Feb 2016 15:23:10 kernel[0]: using 16384 buffer headers and 10240 cluster IO buffer headers 08 Feb 2016 15:23:10 kernel[0]: AppleCredentialManager::start called 08 Feb 2016 15:23:10 kernel[0]: AssertMacros: tmpData (value: 0x0), file: /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleCredentialManager/AppleCredentialManager-83.20.2/AppleCredentialManager/AppleCredentialManager.cpp, line: 765 08 Feb 2016 15:23:10 kernel[0]: AppleKeyStore starting (BUILT: Dec 10 2015 19:43:11) 08 Feb 2016 15:23:10 kernel[0]: Unsynchronized TSC for cpu 2: 0x00000086e15cfee5, delta 0x789dd4a11c 08 Feb 2016 15:23:10 kernel[0]: Unsynchronized TSC for cpu 4: 0x00000086e223447d, delta 0x789dd4a112 08 Feb 2016 15:23:10 kernel[0]: Unsynchronized TSC for cpu 11: 0x00000086e4d3f2f0, delta 0x789dd4a128 08 Feb 2016 15:23:10 kernel[0]: IOAPIC: Version 0x20 Vectors 64:87 08 Feb 2016 15:23:10 kernel[0]: Current tsc from rdtsc64() is 579376551862. Rendezvouing.. 08 Feb 2016 15:23:10 kernel[0]: ACPI: sleep states S3 S4 S5 08 Feb 2016 15:23:10 kernel[0]: CPUSensors: CPU family 0x6, model 0x3f, stepping 0x2, cores 6, threads 12, TJmax 95 08 Feb 2016 15:23:10 kernel[0]: CPUSensors: setting platform keys to [j43 ] 08 Feb 2016 15:23:10 kernel[0]: CPUSensors: base CPU multiplier is 35 08 Feb 2016 15:23:10 kernel[0]: CPUSensors: started 08 Feb 2016 15:23:10 kernel[0]: RTC: Only single RAM bank (128 bytes) 08 Feb 2016 15:23:10 kernel[0]: FakeSMC v6.18.1394 Copyright 2015 netkas, slice, usr-sse2, kozlek, navi, THe KiNG, RehabMan. All rights reserved. 08 Feb 2016 15:23:10 kernel[0]: pci (build 19:23:54 Dec 10 2015), flags 0xe1000, pfm64 (44 cpu) 0xfff80000000, 0x80000000 08 Feb 2016 15:23:10 kernel[0]: FakeSMC: 13 preconfigured keys added 08 Feb 2016 15:23:10 kernel[0]: FakeSMC: 5 keys exported by Clover EFI 08 Feb 2016 15:23:10 kernel[0]: SMC: successfully initialized 08 Feb 2016 15:23:10 kernel[0]: [ PCI configuration begin ] 08 Feb 2016 15:23:10 kernel[0]: console relocated to 0xe0000000 08 Feb 2016 15:23:10 kernel[0]: 000149.515007 AppleUSBLegacyRoot@: AppleUSBLegacyRoot::init: enabling legacy matching 08 Feb 2016 15:23:10 kernel[0]: [ PCI configuration end, bridges 6, devices 18 ] 08 Feb 2016 15:23:10 kernel[0]: mcache: 12 CPU(s), 64 bytes CPU cache line size 08 Feb 2016 15:23:10 kernel[0]: mbinit: done [128 MB total pool size, (85/42) split] 08 Feb 2016 15:23:10 kernel[0]: rooting via boot-uuid from /chosen: A69CCEF2-67A8-39E9-9801-052717973D5D 08 Feb 2016 15:23:10 kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict> 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: FakePCIID_XHCIMux::init 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: FakePCIID::init() <ptr> 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: Version 1.2.3 starting on OS X Darwin 15.3. 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: FakePCIID::attach() <ptr> 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: FakePCIID_XHCIMux::hookProvider 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] configRead32 address space(0x0000a000, 0x00) result: 0x8d318086 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] configRead32 address space(0x0000a000, 0xd4) result: 0x00007fff 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] configRead32 address space(0x0000a000, 0xd0) result: 0x00000000 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] XHCIMux::startup: newData for PR2: 0x00000000 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: FakePCIID::detach() <ptr> 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: FakePCIID::attach() <ptr> 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: FakePCIID_XHCIMux::hookProvider 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: FakePCIID::start() <ptr> 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: FakePCIID_XHCIMux::hookProvider 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] configRead32 address space(0x0000a000, 0x04) result: 0x02900006 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] configRead32 address space(0x0000a000, 0x00) result: 0x8d318086 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] XHCIMux::configWrite32 address space(0x0000a000, 0x04) data: 0x02900006 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] configRead16 address space(0x0000a000, 0x72) result: 0xc1c2 08 Feb 2016 15:23:10 kernel[0]: com.apple.AppleFSCompressionTypeZlib kmod start 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] configRead32 address space(0x0000a000, 0x04) result: 0x02900006 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] configRead32 address space(0x0000a000, 0x00) result: 0x8d318086 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] XHCIMux::configWrite32 address space(0x0000a000, 0x04) data: 0x02900006 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] configRead32 address space(0x0000a000, 0x04) result: 0x02900006 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] configRead32 address space(0x0000a000, 0x00) result: 0x8d318086 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] XHCIMux::configWrite32 address space(0x0000a000, 0x04) data: 0x02900006 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] configRead32 address space(0x0000a000, 0xd4) result: 0x00007fff 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] configRead32 address space(0x0000a000, 0x00) result: 0x8d318086 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] XHCIMux::configWrite32 address space(0x0000a000, 0xd0) data: 0x00007fff 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] configRead32 address space(0x0000a000, 0xd4) result: 0x00007fff 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] configRead32 address space(0x0000a000, 0xd0) result: 0x00000000 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] XHCIMux::configWrite32 address space(0x0000a000, 0xd0) data: 0x00007fff -> 0x00000000 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] configRead32 address space(0x0000a000, 0xdc) result: 0x0000003f 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] configRead32 address space(0x0000a000, 0x00) result: 0x8d318086 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] XHCIMux::configWrite32 address space(0x0000a000, 0xd8) data: 0x0000003f 08 Feb 2016 15:23:10 kernel[0]: com.apple.AppleFSCompressionTypeDataless kmod start 08 Feb 2016 15:23:10 kernel[0]: Ethernet [AtherosE2200]: TCP/IPv4 segmentation offload enabled. 08 Feb 2016 15:23:10 kernel[0]: Ethernet [AtherosE2200]: TCP/IPv6 segmentation offload enabled. 08 Feb 2016 15:23:10 kernel[0]: Ethernet [AtherosE2200]: TCP/IPv6 checksum offload enabled. 08 Feb 2016 15:23:10 kernel[0]: GeforceSensors: starting early shadow VBIOS... 08 Feb 2016 15:23:10 kernel[0]: GeForceSensors (pci3): trying to shadow VBIOS... 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] configRead32 address space(0x0000a000, 0x40) result: 0x803601fd 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] configRead32 address space(0x0000a000, 0x00) result: 0x8d318086 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] XHCIMux::configWrite32 address space(0x0000a000, 0x40) data: 0x803609fd 08 Feb 2016 15:23:10 kernel[0]: com.apple.AppleFSCompressionTypeZlib load succeeded 08 Feb 2016 15:23:10 kernel[0]: com.apple.AppleFSCompressionTypeDataless load succeeded 08 Feb 2016 15:23:10 kernel[0]: Ethernet [AtherosE2200]: Killer E2200: (Rev. 16) at 0x<ptr>, fc:aa:14:7a:e2:ed 08 Feb 2016 15:23:10 kernel[0]: Ethernet [AtherosE2200]: Version 2.0.1 using max interrupt rate 5000. 08 Feb 2016 15:23:10 kernel[0]: SuperIODevice: found ITE IT8620E on port=0x2e address=0xa40 08 Feb 2016 15:23:10 kernel[0]: IT87xxSensors: started 08 Feb 2016 15:23:10 kernel[0]: GeForceSensors (pci3): VBIOS successfully read from PROM 08 Feb 2016 15:23:10 kernel[0]: GeForceSensors (pci3): chipset: GM200 (NV120) bios: 84.00.1f.00 08 Feb 2016 15:23:10 kernel[0]: GeForceSensors (pci3): started 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] configRead32 address space(0x0000a000, 0x40) result: 0x803601fd 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] configRead32 address space(0x0000a000, 0x00) result: 0x8d318086 08 Feb 2016 15:23:10 kernel[0]: FakePCIID: [8086:8d31] XHCIMux::configWrite32 address space(0x0000a000, 0x40) data: 0x803609fd 08 Feb 2016 15:23:10 kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/EVSS@11,4/AppleAHCI/SECD@1/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDriver/KINGSTON SV300S37A240G Media/IOGUIDPartitionScheme/Mac HDD@2 08 Feb 2016 15:23:10 kernel[0]: USBMSC Identifier (non-unique): AA04012700012726 0x1b1c 0x1ab1 0x1100, 2 08 Feb 2016 15:23:10 kernel[0]: BSD root: disk0s2, major 1, minor 1 08 Feb 2016 15:23:10 kernel[0]: hfs: mounted Mac HDD on device root_device 08 Feb 2016 15:23:10 kernel[0]: VM Swap Subsystem is ONFailed to open swap file 08 Feb 2016 15:23:10 kernel[0]: 30 08 Feb 2016 15:23:10 kernel[0]: vm_swap_create_file failed @ 150 secs 08 Feb 2016 15:23:10 kernel[0]: [ PCI configuration begin ] 08 Feb 2016 15:23:10 kernel[0]: [ PCI configuration end, bridges 7, devices 72 ] 08 Feb 2016 15:23:10 kernel[0]: Waiting for DSMOS... 08 Feb 2016 15:23:10 kernel[0]: Ethernet [AtherosE2200]: Link down on en0 08 Feb 2016 15:23:10 kernel[0]: Previous shutdown cause: 5 08 Feb 2016 15:23:10 kernel[0]: IOGraphics flags 0x43 08 Feb 2016 15:23:10 kernel[0]: NVDAStartupWeb: Web 08 Feb 2016 15:23:10 kernel[0]: com_intel_driver_EnergyDriver[<ptr>]::start(<ptr>) 08 Feb 2016 15:23:10 kernel[0]: NVDAGM100HAL loaded and registered 08 Feb 2016 15:23:10 kernel[0]: DSMOS has arrived 08 Feb 2016 15:23:11 kernel[0]: [IOBluetoothFamily][start] -- completed 08 Feb 2016 15:23:11 kernel[0]: in6_unlink_ifa: IPv6 address 0x7e76c17d1877f52f has no prefixFailed to find sleep policy for this platform! Disabling deep sleep. 08 Feb 2016 15:23:11 kernel[0]: Standby delay is not specified! Defaulting to 0x1068 08 Feb 2016 15:23:11 kernel[0]: ErP Timer is not specified! Defaulting to 0x3840 08 Feb 2016 15:23:11 kernel[0]: Standby delay is not specified! Defaulting to 0x1068 08 Feb 2016 15:23:11 kernel[0]: ErP Timer is not specified! Defaulting to 0x3840 08 Feb 2016 15:23:11 kernel[0]: Standby delay is not specified! Defaulting to 0x1068 08 Feb 2016 15:23:11 kernel[0]: ErP Timer is not specified! Defaulting to 0x3840 08 Feb 2016 15:23:11 kernel[0]: Standby delay is not specified! Defaulting to 0x1068 08 Feb 2016 15:23:11 kernel[0]: ErP Timer is not specified! Defaulting to 0x3840 08 Feb 2016 15:23:11 kernel[0]: Standby delay is not specified! Defaulting to 0x1068 08 Feb 2016 15:23:11 kernel[0]: ErP Timer is not specified! Defaulting to 0x3840 08 Feb 2016 15:23:11 kernel[0]: Standby delay is not specified! Defaulting to 0x1068 08 Feb 2016 15:23:11 kernel[0]: ErP Timer is not specified! Defaulting to 0x3840 08 Feb 2016 15:23:11 kernel[0]: Sound assertion in AppleHDADriver at line 1552 08 Feb 2016 15:23:11 kernel[0]: Sound assertion in AppleHDADriver at line 2212 08 Feb 2016 15:23:11 kernel[0]: Sound assertion in AppleHDADriver at line 206 08 Feb 2016 15:23:11 kernel[0]: Standby delay is not specified! Defaulting to 0x1068 08 Feb 2016 15:23:11 kernel[0]: ErP Timer is not specified! Defaulting to 0x3840 08 Feb 2016 15:23:11 kernel[0]: Standby delay is not specified! Defaulting to 0x1068 08 Feb 2016 15:23:11 kernel[0]: ErP Timer is not specified! Defaulting to 0x3840 08 Feb 2016 15:23:11 kernel[0]: Standby delay is not specified! Defaulting to 0x1068 08 Feb 2016 15:23:11 kernel[0]: ErP Timer is not specified! Defaulting to 0x3840 08 Feb 2016 15:23:11 kernel[0]: Standby delay is not specified! Defaulting to 0x1068 08 Feb 2016 15:23:11 kernel[0]: ErP Timer is not specified! Defaulting to 0x3840 08 Feb 2016 15:23:11 kernel[0]: NTFS driver 3.13 [Flags: R/W]. 08 Feb 2016 15:23:11 kernel[0]: NTFS volume name TRANSFER, version 3.1. 08 Feb 2016 15:23:11 kernel[0]: NTFS-fs error (device /dev/disk2s1, pid 131): ntfs_restart_page_header_is_valid(): $LogFile version 2.0 is not supported. (This driver supports version 1.1 only.) 08 Feb 2016 15:23:11 kernel[0]: NTFS-fs error (device /dev/disk2s1, pid 131): ntfs_restart_page_header_is_valid(): $LogFile version 2.0 is not supported. (This driver supports version 1.1 only.) 08 Feb 2016 15:23:11 kernel[0]: NTFS-fs error (device /dev/disk2s1, pid 131): ntfs_logfile_check(): Did not find any restart pages in $LogFile and it was not empty. 08 Feb 2016 15:23:11 kernel[0]: NTFS-fs warning (device /dev/disk2s1, pid 131): ntfs_system_inodes_get(): $LogFile is not clean. Will not be able to remount read-write. Mount in Windows. 08 Feb 2016 15:23:11 kernel[0]: NTFS volume name Geymsla, version 3.1. 08 Feb 2016 15:23:11 kernel[0]: NTFS-fs error (device /dev/disk1s1, pid 136): ntfs_restart_page_header_is_valid(): $LogFile version 2.0 is not supported. (This driver supports version 1.1 only.) 08 Feb 2016 15:23:11 kernel[0]: NTFS-fs error (device /dev/disk1s1, pid 136): ntfs_restart_page_header_is_valid(): $LogFile version 2.0 is not supported. (This driver supports version 1.1 only.) 08 Feb 2016 15:23:11 kernel[0]: NTFS-fs error (device /dev/disk1s1, pid 136): ntfs_logfile_check(): Did not find any restart pages in $LogFile and it was not empty. 08 Feb 2016 15:23:11 kernel[0]: NTFS-fs warning (device /dev/disk1s1, pid 136): ntfs_system_inodes_get(): $LogFile is not clean. Will not be able to remount read-write. Mount in Windows. 08 Feb 2016 15:23:12 kernel[0]: Ethernet [AtherosE2200]: Link up on en0, 1-Gigabit, Full-duplex, Rx/Tx flow-control 08 Feb 2016 15:23:18 kernel[0]: AppleKeyStore:Sending lock change 0 for handle -501 08 Feb 2016 15:23:19 kernel[0]: ignored is_io_service_close(0x10000069e,IOHIDParamUserClient) 08 Feb 2016 15:23:19 kernel[0]: Sandbox: storeaccountd(311) deny(1) file-write-create /Users/Hjalti/Library/Caches/com.apple.spotlight 08 Feb 2016 15:23:20 kernel[0]: Sandbox: storeaccountd(311) deny(1) file-write-create /Users/Hjalti/Library/Caches/com.apple.spotlight 08 Feb 2016 15:23:20 kernel[0]: Sandbox: storeaccountd(311) deny(1) file-write-create /Users/Hjalti/Library/Caches/com.apple.spotlight 08 Feb 2016 15:23:20 kernel[0]: Sandbox: SocialPushAgent(337) deny(1) file-write-data /Users/Hjalti/Library/Preferences/com.apple.socialpushagent.plist 08 Feb 2016 15:23:20 kernel[0]: Sandbox: SocialPushAgent(337) deny(1) file-write-data /Users/Hjalti/Library/Preferences/com.apple.socialpushagent.plist 08 Feb 2016 15:23:20 kernel[0]: Sandbox: storeaccountd(311) deny(1) file-write-create /Users/Hjalti/Library/Caches/com.apple.Safari/ProductionBag 08 Feb 2016 15:23:21 kernel[0]: Sound assertion in AppleHDADriver at line 3593 08 Feb 2016 15:23:21 kernel[0]: Sound assertion in AppleHDADriver at line 1088 08 Feb 2016 15:23:31 kernel[0]: Sandbox: softwareupdated(392) deny(1) system-fsctl 682f 08 Feb 2016 15:23:41 kernel[0]: **** [IOBluetoothFamily][SearchForTransportEventTimeOutHandler] -- Missing Bluetooth Controller Transport! 08 Feb 2016 15:28:56 kernel[0]: hfs: mounted Recovery HD on device disk0s3 08 Feb 2016 15:28:56 kernel[0]: hfs: unmount initiated on Recovery HD on device disk0s3 Kexts I'm using are attached as well as config.plist for network I'm using [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] for el capo, just to install the fakeSMC, plugins and network kext (ethernet killer 2200) After that i installed Nvidia Webdrivers that now show active! first time ever I'm not having the cosmetic bug, no idea how it got fixed. still have yet to install photoshop but i assume the OpenCL bug is still there, so I will probably have to disable openCL and use medium graphic acceleration (which is very annoying considering i have a f-ing Titan X) Any advice on how i can optimise this setup? Kexts_and_stuff.zip
  15. Hey guys! Running into some problems with my x99 build and hoping someone can help:) I've been following a mix of x99 guides (found both here and tonymacx86) to no success thus far. The furthest I have gotten is a hang up on AMFILoad after [ PCI Configuration Begin ] as seen below Obviously the first error is that it hangs on AMFILoad. I haven't had much luck in finding out what I need to change/fix to get past this. The other error is "Unsynchronized TSC for CPU" (also seen in that screenshot). That one seems more likely to be an issue with the VoodooTSCSync kext but I'm not quite sure why as I have literally just used someone else's (successful) voodoo kext who modified it for the i7 6950x (which is the processor I have) using @Brumbaer's patch where you simply change the IOCPUNumber to 19 (10 cores, 20 threads, subtract 1 from 20 to get the 19) in the kext. I also have a successful Windows 10 boot on a different SSD so I extracted the DSDT.bin and SSDT.bin with RW Everything, converted them to DSDT.aml and SSDT.aml and placed them in the EFI>CLOVER>ACPI>patched folder. Currently, I'm also running it with 1 single 16 GB stick of RAM (and not the full 96 GB of RAM). Additionally, I have tried various usb sticks and usb ports with no additional success. Any and all help would be much appreciated on this issue as I'm pretty much totally stuck Let me know if there is any additional information I can provide or upload, etc.
  16. I am trying to install OS X El Capitan but i keep getting errors. I am stuck at that error mainly: I also tried lots of boot flags but still got different errors, Here is my rig:- Mobo: MSI X99A Raider CPU: Intel Core i7 5820K Graphics Card: Gigabyte GTX 970 G1 Gaming RAM: Kingston 16GBs DDR4 2133MHz I would really appreciate if someone helps me out, cuz I've been trying for ages
  17. Hello, I set up a new X99 workstation based on the Intel i7 5960X a few months ago and Yosemite works very well on it. Except of a "small" part I normally use heavily in my daily workflow: The Terminal Here is a descriptionof the problems I detected (maybe more are hidden but due to the problems I encountered I rarely use this workstation for development and fall back to my MacBook or my old Hack for now). The architecture of the system seems to not be recognised correctly. When I try to install homebrew I get an error that it doesn't find the target platform. So I tried to look at uname and found that it doesn't show the current kernel or anything: x99:~ me$ uname -a x99:~ me$ Same strange behaviour goes for find (in my home with quite a few folders and files): x99:~ me$ find . x99:~ me$ After wondering about this I started zsh and tried both commands: f35% find . zsh: exec format error: find f35% uname -a zsh: exec format error: uname What can I think of this? Any idea hear? I can't really imaging what went wrong there and why everything else works. I can throw different image/video apps up and haven't had problems yet. It's only on the Terminal where I'm not sure what's going on and normally I'm quite often using the Terminal as a long time Linux/*nix user and do many stuff with small scripts and use homebrew to install a bunch of tools also. Installation was done with a modified Kernel and a few modified extensions to get it running on the X99 platform.
  18. well, from Sierra 10.12.2 to 10.12.4 my system is randomly freezing. no post. no error. nothing. no warning, just locks up. Mouse doesnt move, graphics freeze. sound repeats any idea? system AsRock x99m Extreme 4 Intel® Core™ i7-6800K Processor 15M Cache, up to 3.60 GHz Gigabyte GTX960 GV-N960IXOC-2GD HyperX FURY Black 8GB, DDR4, 2400MHz, CL15, 1.2V *2 Solid State Drive (SSD) Intel 600p Series, 256GB, M.2 80mm, PCIe Corsair VS550 550W
  19. Greetings All, I have seen a few random reboots since Yosemite on this particular machine. However, I have seen far too many reboots after El Capitan 10.11.1 update, and even more after 10.11.2. I managed to get it running. It actually runs rather smooth. But I am getting far too many random reboots at any given time after updating. I'm lucky I got past this posting before rebooting on its own. As usual, I updated to the latest Nvidia Webdriver after updating. Contrary to what most people say, my setup along with the eVGA GT 740 FTW requires the webdriver or it won't boot. Sometimes it reboots while browsing online (Any browser). More than likely while watching YouTube videos. It can go from minutes to hours before randomly rebooting, but it depends on the usage. I have tried different SMBIOS to no avail. It seems like booting without caches helps, but not always (that's how I got this far to post). I also added RampageDev's X99 SSDT file for my motherboard (X99-UD4). I recently updated the BIOS to F12. It made no difference. I can't seem to find anyone else with this particular problem, and if there is, they seemed to have left the issue unresolved. If anyone has any info on this issue, please advise. My setup is in my sig below. Thanks in advance. Prof. Synthology
  20. MICKHAEL

    Asrock x99m Extreme 4

    Sierra, 10.12.6/ High Sierra 10.13.6 on x99 chipset with GTX960 GPU and i7 6800k CPU UEFI 3.50 Hi folks. I managed to make it stable as possible. everything seems to work. for suggestions and additions we are all open. see attachment below with respect to developers like Pike R. Toleda MaLd0n fabiosun and many others brave people AsRock x99m Extreme 4 Intel® Core™ i7-6800K Processor 15M Cache, up to 3.60 GHz Gigabyte GTX960 GV-N960IXOC-2GD HyperX FURY Black 8GB, DDR4, 2400MHz, CL15, 1.2V *2 Solid State Drive (SSD) Intel 600p Series, 256GB, M.2 80mm, PCIe Corsair VS550 550W PS: for all apple services to work, you will need to grab some real MLB/ROM mike 2018 asrock_x99m_extreme4_6october2017_EFI_10.12.6.zip asrock_x99m_extreme4_10july2018_EFI_10.13.6.zip
  21. Hi, Here is my experience with this setup: - ASUS X99/A USB3.1 Mainboard - i7 5820k processor - Radeon R9 270x - SAMSUNG M.2 MZHPV256 storage - ASUS PB287Q 4k display (Display Port connector) Since I had to go through a lot of different resources to have it working properly, I wanted to share all the info in a single place. Following the guide from http://www.rampagedev.com, and with the help from Slice, Mieze and Vlada from http://www.insanelymac.com/forum/topic/308025-no-graphics-usb-audio-after-wake/, the info from Stinga from http://www.insanelymac.com/forum/topic/309717-haswell-e-5820k-5930k-installation-guide-with-full-speedstep-working/, El Capitan USB threads from Rehabman and constant updates from Pike's blog https://pikeralpha.wordpress.com we can get a really stable build based on X99 chipset with the following features: - Speedstep working - Audio through DP - All USB2/3 ports working (USB3.1 ports disabled in BIOS) You can find a screenshot attached List of steps to be performed: Disable Serial Port in BIOS (I cannot boot the system with Serial Port enabled), disable ASMEDIA USB 3.1 controller Strictly Follow the installation guide in Rampagedev.com Follow the X99 guide from Ramapgedev (except for config.plist) for 10.10 using the following files: SSDT.aml in ACPI/PATCHED (rampagedev) AppleIntelE1000e for ethernet support (rampagedev) FakeSMC (currently using SLICE 3.x version) http://www.insanelymac.com/forum/topic/296460-amdcpumonitor-and-hwsensors-331/page-1 X99_Injector modified kext (attached) to load AppleLPC kext only (credits to PJALM) config.plist for Clover (attached here) config.plist probably has redundant info, but basically provides the following features: Rename EHC1, EHC2, XHCI in order to have USB fully working use xcpm for power management Patches AppleUSBXHCIPCI to remove usb port limit Forces a fake processor ID to enable xcpm and speedstep There is NO need for a specific processor P-states SSDT, but if you want to get no errors on boot you can create one following the details in the threads above. That's it. Attached mine, in case you want to use my configurations (47x max multiplier, 100Mhz BCLK) BIOS configuration (for my setup): Speedstep enabled Turbo states enabled Max CPU multiplier 47x as you can see from the xcpm info - I would suggest to start with "AUTO" for all CPU-related settings BCLK 100 Mhz Memory set to 2133 Mhz - If I increase memory speed to the upper 2k range or set the BCLK to higher freq. the system is very unstable and reboots without notice (this happens in El Capitan only, Yosemite works perfectly!) Other: M.2 disk does not require ANY specific action on BIOS or OSX USB does not require any specific kext apart from the config.plist patches OSX Sleep/Wake is NOT working properly - Radeon times out In order to use Display Port I had to modify Rampagedev SSDT GFX0 section from: "@0,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@1,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@2,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@3,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, to: "@0,connector-type", Buffer (0x04) { 0x00, 0x04, 0x00, 0x00 }, "@1,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@2,connector-type", Buffer (0x04) { 0x00, 0x02, 0x00, 0x00 }, "@3,connector-type", Buffer (0x04) { 0x00, 0x02, 0x00, 0x00 }, In order to fake MacPro6,1 AMD FirePro300 Video card you can add the following item in clover Info.plist under the KextsToPatch section: Hope this helps!! Andrea X99_Injector.kext.zip config.plist.zip SSDT-1.aml.zip
  22. Hi all, So recently upgraded my motherboard and wanted to get USB3 working in Sierra. I am attempting to follow this guide here by @mfc88 (edit: can you tag users here?) : http://www.insanelymac.com/forum/topic/313296-guide-mac-osx-1012-with-x99-broadwell-e-family-and-haswell-e-family/?p=2354822 However I am stuck at step 4 which asks you to map your ports to HSxx and SPxx.... edit update: My primary problem now (after MaLd0n helped me get SSP shoing in IOReg) is that when plugging in a USB3 device only one port maps to the SSP locations, none of the others do. When opening my DSDT in Rehabmans maciASL I see the HS01-HS14 and SSP1-SSP6 When looking under XHCI in IORegistryExplorer I still see HS01-HS14, but I only see SSP1-SSP2, this prevents me from mapping the USB3 ports, as they dont show up here - Solved - Thanks MaLd0n If I do a System Report and look in the USB 3 Bus for a location ID of a plugged in item I can find it, but if I search for this ID in IOReg it is not there. It is possible I have something else interfering as I used a EFI/Clover folder from someone else's build (he didn't have USB3 working either). However I have removed the FakePCIID kexts to work on this guide. The guide asks you to disable XHCI handoff, however OSX will not boot with this disabled and hangs at HDA Enabler in verbose, or if I remove HDA kexts at Thunderbolt runtime power conservation I can get SSP1 to activate - one of the USB ports maps to this, and when I have a USB3 device plugged into it it works at USB3 speeds. - There is a USB3.1 port which also works at USB3/3.1 speeds but does not show up under XHCI. I have wires plugged into both USB3 headers on the motherboard so I can check all ports. This motherboard also has a Renesas controller on it. I have attached my dsdt (from Clover f4) and clover .plist for reference, Any help or direction greatly appreciated DSDT_plist.zip
  23. Hey all. Specs: ASRock x99 Extreme4 Core i7 5820k 3.3ghz 6-core 8gb DDR4 ATI 2600XT 256mb (Temporary, pulled from an Early 2008 Mac Pro) I've been using RampageDev's guide on creating a Sierra (10.12.2) USB stick (It wasn't much different from when I installed El Capitan on my Latitude E7440 and I've completely written off [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url]), as well as their suggested kexts and Clover config file for x99 chipsets. Things to note: My serial port is disabled CSM is disabled In general, my BIOS matches this posts: http://www.insanelymac.com/forum/topic/310655-x99-10113-resets-upon-wake/?p=2224095 I'm using an 8gb flash drive in a USB 2.0 port on my motherboard My kexts look like this My boot arguments are: npci=0x2000 kext-dev-mode=1 -v After using other people's suggested EFI folders for their x99 systems, I have found that what I have is taking me the farthest so far. However, I'm now stuck here: I'm not quite sure what I'm doing wrong at this point. Any help?
  24. Hi. I have had a stable X99 build running for a year. Build with the help of rampagedev's guide. This has been a super-smooth build, performing well in the range of video editing, sound record, gaming, streaming, and day to day use. The only thing not working has been overclocking. Multiple reports online indicates that certain UD4 boards has a fault with turning anything related to overclock from Auto to Manual (you don't even have to change any values), causes a boot failure. Because of this I was about to RMA my board and go for a X99-A, but trying that just caused a lot of USB problems. I was relieved when Gigabyte released a new BIOS update: the F22h, focusing on overclock. This update indeed fixes the overclock issue, but creates a whole new set of issues. Kernel-panic, random reboots, and USB problems. Nothing else was changed. Most of the time boot just failed with kernel panic. At one time I got it to boot, but I experienced random reboots, the mac freezing when using some USB equipment such as the Elgato Game Capture HD60 and so on. Downgraded to the previous BIOS version and voila, everything working as before. Does anyone else with a UD4 experience these problems with the new update? I really want it to work so I can start overclocking, but I need a stable setup. What sort of logs do I need to provide in order for anyone to help me troubleshoot this problem? As a start I attached the config file, replacing the ROM, MLB, Board Serial Number, Serial Number and SmUUID with X's. All of these values have been extracted from a real mac Build: X99-UD4 5820K GTX 980ti 32GB Balistix 2400MHz OS: OS X 10.11.5 SMBIOS: MacPro 6.1 SSDT: SSDT from rampagedev's X99.dmg (change gfx0 to gfx1 to fix black screen) Kexts: ACPISensors AppleIntelE1000e CPUSensors FakeSMC GPUSensors LPCSensors NullCPUPowerManagement VoodooTSCSync Thank you! -Kristoffer config.plist.zip
  25. Hey guys I know abunch of us have working X99 based Asus installs. Two have given me clover configs that should do full XCPM turbo OC, all usb, and told Apple hda script should identify the codec and patch properly. The only thing that has worked is XCPM, which guy with same OC as my i7 5820k had 4.6ghz turbo OC, with his files I'd get 4.5ghz to show this inconsistency. So what are the latest fixes for our XCPM and X99 usb? Seems most threads relating to our boards are old. I'm sure theres better kexts. I'll be doing some work on mine in goals of near full USB, XCPM, and Audio. I'll post up the fixes I find if I can.
×