国产足交电影

    1. <form id=PLArfghvg><nobr id=PLArfghvg></nobr></form>
      <address id=PLArfghvg><nobr id=PLArfghvg><nobr id=PLArfghvg></nobr></nobr></address>

      Jump to content

      iMac Pro X299 - live the future new with macOS 10.14 Mojave [Successful Build/Successful Guide]


      142 posts in this topic

      Recommended Posts

      378853121_Screenshot2018-06-07at04_12_40.thumb.png.3143ea6ee5e86024fdef2d0af661893b.png

      ?

      Up and running macOS Mojave 10.14.4? (18E226) on iMac Pro Skylake-X/X299 Hackintosh!

      ?

      X299-10_14.4.jpg.1604d32eadeb221111e702cfbf8859f6.jpg

      ?

      ?

      1952633164_Screenshot2018-06-06at11_57_37.png.eca4d4a04bfbbd77ccacbe15f338cf76.png

      ?

      ?

      This afternoon @DSM2?advised me that yesterday Apple seems to have added a second special build of MacOS 10.14.4 (18E2034) on?swcdn.apple.com,?likely for new devices.

      ?

      1009787285_Screenshot2019-03-26at23_16_16.thumb.jpg.f6b6cd91f6382a21a1afac9778830973.jpg

      ?

      ?

      1023005410_Screenshot2019-03-26at23_28_40.thumb.png.bb058f0cf1d428c75f088586c8f1fca3.png

      ?

      Abstract and Introduction:?

      This originating post constitutes a new macOS 10.14?Mojave?Desktop Guide for Skylake-X/X299, which certainly will?further?grow not only?thanks?to your estimated feedback and?contributions. It is the logical continuation of my?successful?iMac Pro Skylake-X/X299 Build and?Desktop Guide published for macOS?High Sierra 10.13. To?avoid?jumping back and forth, I will make this guide as?consistent as the?former, which?however implies also some?redundancy.????

      ?

      As everybody already might now, my Skylake-X/X299 Desktop Guide bases?on the ASUS Prime X299 Deluxe. However, also other X299 ASUS mainboard models or X299 mainboards of other brands might be compatible after likely considering and implementing few mandatory modifications. The same states for guide?compatibility?with all Skylake-X/299?CPUs different form the i9-7980XE employed here.?I recently changed from the ASUS Prime X299 Deluxe to the ASUS WS X299 Sage 10G. While the default EFI-Folder distribution remains the same, very few differences in the post installation process for the ASUS WS X299 Sage 10G will be added to my guidelines during the next days.

      ?

      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 Overview
      Details about the build configuration that states the baseline of this guide.
      ?
      B.) Mainboard BIOS
      B1.) ASUS BIOS Firmware Patching
      B2.) ASUS BIOS Configuration
      B3.) Gigabyte BIOS Configuration
      ?
      C.) Important General Note/Advice and Error Prevention
      Hardware and System Configuration recommendations. Make sure you've read all of this before complaining that something does not work.
      ?
      D.) iMac Pro macOS 10.14?Mojave System Setup
      This chapter includes a general guideline how to perform the initial setup of your iMac Pro with macOS Mojave 10.14.
      D.1) iMac Pro EFI-Folder Preparation
      D.2) iMac Pro macOS Mojave 10.14 Installer Package Creation
      D.3) iMac Pro macOS Mojave?10.14 USB Flash Drive Installer Creation
      D.4) iMac Pro macOS Mojave?10.14 Clean Install on Skylake-X/X299
      D.5) Direct iMac Pro conversions of a functional Skylake-X/X299 system with a SMBIOS System Definition different from iMacPro1,1 and a standard macOS build implementation
      D.6)?iMac Pro macOS 10.14 Mojave Update Procedure
      ?
      E.) Post Installation Process
      E.1) HWP (Intel SpeedShift Technology) CPU Power Management Configuration
      E.2) Graphics Configuration
      General ATI and Nvidia GPU advices including a detailed guideline for Nvidia Web Driver Installation and Black Screen Prevention
      E.3) Audio Configuration
      Use only one of the following, where E.3.1 is recommended by the author.
      E.3.1.) AppleALC Audio Implementation
      E.3.2) VoodooHDA Audio Implementation
      E.3.3) cloverALC Audio Implementation
      E.4) USB Configuration
      including some initial benchmarks
      E.5) NVMe compatibility
      E.6.) SSD/NVMe TRIM Support
      E.7) GC-Titan Ridge?/ GC-Alpine Ridge /Asus TBEX 3 PCIe Add-In Implementation
      Extend the life of your SSD and maintained its normal speed
      E.8) Gbit and 10-Gbit Ethernet Implementations
      E.8.1) ASUS Prime X299 Deluxe 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) Onboard Intel X550-AT2 10-Gbit NICs of the ASUS WS X299 Sage 10G
      E.8.2.4) Small-Tree P2EI0G-2T 10-Gbit NIC
      E.8.2.5) NetGear ProSave XS508M 8-port 10-Gbit Switch
      E.8.2.6) QNAP TS-431X2 Quad-core 4-Bay NAS tower
      E.8.2.7) 10-GBit Ethernet Optimisation
      E.9) ASUS Prime X299 Deluxe PCI Device Implementation
      E.9.1) ACPI DSDT Replacement Implementation
      E.9.2) System SSDT PCI Device Implementation
      E.9.2.1) - HDEF - onboard PCI Audio Controller PCI Implementation
      E.9.2.2) - GFX0, HDAU - GPU and HDMI/DP Audio PCI implementation
      E.9.2.3) - PMCR - onboard Power Management Controller (PMC) PCI Implementation
      E.9.2.4) - USBX - fixing XHCI USB Power errors during Boot
      E.9.2.5) - XHCI - onboard Extended Host Controller Interface (XHCI) PCI Implementation
      E.9.2.6) - XHC2,3,4 - ASMedia ASM3142 USB 3.1 Controller PCI Implementation
      E.9.2.7) - ANS1, ANS2 - Apple NVMe Controller PCI Implementation
      E.9.2.8) - SAT1 - Intel AHCI SATA Controller PCI Implementation
      E.9.2.9) - THSS - Intel Thermal Subsystem Controller Implementation
      E.9.2.10) XGBE - 10GBit NIC Implementation
      E.9.2.11) - ETH0/ETH1 - onboard LAN Controller PCI Implementation
      E.9.2.12) - ARPT - OSX WIFI Broadcom BCM94360CD 802.11 a/b/g/n/ac + Bluetooth 4.0 AirPort Controller PCI Implementation
      E.9.2.13) - GC-Titan Ridge?/ GC-Alpine Ridge / Asus TBEX 3 Thunderbolt HotPlug System Implementation
      E.9.2.14) - DTGP Method
      E.9.2.15) - 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) Sylake-X Intel I9-7980XE CPU Benchmarking
      F.2) Gigabyte AORUS GTX 1080 Ti Waterforce EB 11GB Extreme Edition Benchmarking
      ?
      G.) Summary and Conclusion

      ?

      ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------

      ?

      A.)? Hardware Overview

      ?

      Mainboard:?ASUS WS X299 Sage 10G, former?Asus Prime X299 Deluxe
      CPU:?i9-7980XE?(18 core, 4.4Ghz)
      RAM Memory:?Corsair Dominator Platinum 128GB (8x16GB) DDR4 3200 MHz C16 Kit?@3600MHz OC
      GPU:?Sapphire Nitro+ Radeon RX Vega 64 8GB
      GPU Water-Blocking:?Bykski Sapphire Nitro+ Radeon RX Vega 64 8GB water block?from Aliexpress
      System Disks:?EVO 970 PRO NVMe M.2 1TB?(MacOS);?EVO 960 NVMe M.2 1TB?(Windows 10)
      Thunderbolt 3:?GC-Titan Ridge?40GB/s Intel Thunderbolt 3 Certified Add-in PCIe Adaptor
      Power Supply:?Corsair AX1500i
      Monitor:?LG 34WK95U-W?34" 21:9 Ultra Wide 5K2K Nano IPS LED Monitor with HDR600 and DP1.4/TB3
      WebCam:?Logitech C930e
      Mouse:?Apple Magic Mouse 2
      Keyboard:?Apple Magic Keyboard Wireless
      Bluetooth + Wifi:?PC/HACKINTOSH - APPLE BROADCOM BCM94360CD - 802.11 A/B/G/N/AC + BLUETOOTH 4.0
      Internal USB2.0 HUB:?NZXT AC-IUSBH-M1T?(Prime X299 Deluxe)
      Case:?Lian Li PC-D888WX 8Pack Limited Edition?(WS X299 Sage 10G), fromer:?Thermaltake Core X71 Tempered Glass Edition Full Tower Chassis?(Prime X299 Deluxe)

      ?

      10Gbit Ethernet?components:
      ?

      -?1x ASUS XG-C100C AQC107 PCIe x4 10GBit LAN Adapter (Prime X299 Deluxe)

      -?1x Intel X540-T1 single port 10GBit LAN PCIe Adapter (Prime X299 Deluxe, now installed in my X99 rig)

      -?1x Small-Tree P2EI0G-2T 2-Port 10GBit LAN PCIe Adapter (Prime X299 Deluxe)

      -?2x Intel X550-AT2 (onboard WS X299 Sage 10G)

      - 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 once more 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.
      ?
      CPU/GPU Cooling:?Water Cooling main components:
      ?

      - 1x EK-Velocity D-RGB - Nickel + Plexi (WS X299 Sage 10G); former: 1x EK-FB ASUS Prime X299 RGB Monoblock - Nickel (Prime X299 Deluxe)

      - 1x EK-CoolStream PE 360 (Triple, 39 mm, Roof - TT Core X71, Roof - right chamber - Lian Li)

      - 1x EK-CoolStream Ce 280 (Dual, 45mm, Front - TTCore X71); 2x Alphacool NexXxos XT 45 240mm (Dual, 45mm, back side - right chamber -Lian Li)

      - 2x EK-CoolStream XE 360 (Triple, 60 mm, Cellar - TT Core X71, top and front - left chamber - Lian Li)

      - 1x XSPC Twin D5 Dual Bay Reservoir/Pump Combo

      - 15x (TT Core X71), 18x (Lian Li) Thermaltake Riing 12 High Static Pressure LED Radiator Fan (120mm)

      - 5x Thermaltake Riing 14 High Static Pressure LED Radiator Fan (140mm, TT Core X71)

      - 3x Phantek PMW Fan Hub (up to 12 fans or 30W power consumption)

      - 1x Alphacool Eisflügel Flow Indicator Black G1/4 IG

      - 1x?Phobya Temperatur Sensor G1/4 + C/F Display

      ?

      Most of the components purchased at Amazon.de, Caseking.de, Mindfactory.de, Alernate.de

      ?

      ?

      B.) Mainboard BIOS

      ?
      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 was usually read only for ages.? When the kernel tried to write to this locked register, it caused a kernel panic. This panic could happen very early in the boot process, with the result that the system freezes or reboots during the boot process. We could 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.
      ?
      Thanks to recent modifications in CodeRush's Longsoft UEFIPatch distributions and thanks to three sophisticated MSR 0xE2 Register patches provided by @interferenc (partly former work of CodeRush, Pike Alpha and Adrian_dsl), we were able to successfully patch any ASUS X299 mainboard BIOS firmware distribution and unlock the MSR 0xE2 register. The patched ASUS mainboard BIOS firmware finally has been?uploaded to the specific ASUS X299 mainboard by means of the ASUS EZ BIOS Flashback Procedure. This made?the "xcpm_core_scope_msrs ? Pike R. Alpha" KernelToPatch entry obsolete and allowed?full native read/write MSR 0xE2 register access by the OSX kernel.
      ?
      Since?ASUS Prime X299 Deluxe BIOS firmware 1301, ASUS now allows upon my user request for the first time to manually unlock the MSR 0xE2 register within the most recent BIOS settings. This makes the ASUS BIOS firmware patching obsolete.?MSI and ASRock X299 mainboards allowed??the manual unlock of the MSR 0xE2 BIOS Register right from?the beginning?and the MSR 0xE2 BIOS Register of all Gigabyte mainboards is anyway unlocked by factory default. However, yet we witness some TSC desynchronisation of the Skylake-X threads at boot and wake from S3. Until further microcode updates are performed by the mainboard manufacturers, we therefore have to use ?the TSCAdjustRest.kext provided by @inteferenc (see error prevention C.4?of this guide) to circumvent this TSC?desynchronisation?issue.?
      ?
      By this we achieve fully native HWP (Intel SpeedShift Technology) CPU Power Management for all Skylake-X processors on all X299 mainboards with unlocked MSR 0xE2 BIOS Register, resulting in absolutely brilliant and top-end CPU performance (see Section E.1).
      ?
      Before summarising all necessary ASUS and?Gigabyte BIOS settings, ?let me provide X299D.CAP, the best working ASUS Prime X299 Deluxe BIOS Firmware 1503 with an iMacPro Splash Screen Image (see Section E.10), which can be flashed by means of the well known ASUS EZ BIOS Flashback procedure.?You should stay away from subsequent BIOS firmware versions 1603 and 1704, as they can either introduce XHCI related issues or prevent GPU firmware load at boot. Thus please, stay with 1503 as the best firmware implementation for the ASUS Prime X299 Deluxe! For the?ASUS WS X299 Sage 10G, I also attach below BIOS Firmware version 0905 with the iMacPro Splash Screen Image, i.e WSXTG.CAP,?also to be?flashed?with the ASUS EZ BIOS Flashback procedure.?
      ?
      B2.) ASUS BIOS Configuration
      ?
      After Updating System time and System Date, enable X.M.P for your DDR4 modules. Don't forget to enable the EZ XMP Switch previously to this step on your ASUS Mainboard! Subsequently switch form the easy to the advanced ASUS BIOS Setup mode by pressing F7.
      ?
      I use all optimized BIOS settings (OoB, no OC yet) despite a few changes listed in detail below:
      ?
      1.)?/AI Tweaker/
      a.) ASUS MultiCore Enhancement:?Auto?
      b.) AVX Instruction Core Ratio Negative Offset: "3"?
      c.) AVX-512 Instruction Core Ratio Negative Offset: "2"?
      d.) CPU Core Ratio:?Sync All Cores
      e.)?CPU SVID Support:?Enabled?
      f.) DRAM Frequency: DDR4-3200MHz (in my particular case)
      ?
      2.)?/Advanced/CPU Configuration/
      a.) Hyper Threading [ALL]: Enabled
      b.)?MSR Lock Control: Disabled
      ?
      3.)?/Advanced/CPU Configuration/CPU Power Management Configuration/
      a.)?Enhanced Intel Speed Step Technology (EIST): Enabled
      b.) Autonomous Core C-States: Enabled
      c.) Enhanced Halt State (C1E): Enabled
      d.) CPU C6 report: Enabled
      e.) Package C-State: C6(non retention) state
      f.)?Intel SpeedShift Technology: Enabled
      g.) MFC Mode Override: OS Native
      ?
      4.)?/Advanced/Platform Misc Configuration/??
      a.) PCI Express Native Power Management: Disabled
      b.) PCH DMI ASPM: Disabled
      d.) ASPM: Disabled
      e.) DMI Link ASPM Control: Disabled
      f.)? PEG - ASMP: Disabled
      ?
      5.)?/Advanced/System Agent Configuration/
      a.) Intel VT for Directed I/O (VT-d): Disabled/Enabled
      ?
      6.)?/Boot/
      a.) Fast Boot: Disabled
      b.) Above 4G Decoding:?Off?(must be?ON?with Prime X299 Deluxe BIOS firmware 1603 and 1704 and WS X299 Sage 10G BIOS?firmware?0905?in case of GPU firmware load and?XHCI ACPI implementation issues. When?employing?WS X299 Sage 10G BIOS?firmware?0905 and enabling Above 4G?Decoding in the respective BIOS settings as?required, "First VGA 4G Decode" must be set to "Auto", as both?Windows 10 and macOS can become irresponsive with different "First VGA 4G Decode" settings.
      c.) Set your specific Boot Option Priorities
      ?
      7.)?/Boot/Boot Configuration
      a.) Boot Logo Display:?Auto?
      b.) Boot up NumLock State: Disabled
      c.) Setup Mode: Advanced
      ?
      8.)?/Boot/Compatibility Support Module/
      a.) Launch CSM: Disabled
      ?
      9.)?/Boot/Secure Boot/
      a.) OS Type: Other OS
      ?
      With F7 and F10 you can save the modified BIOS settings.
      ?
      Note the important additional comments to the above BIOS settings provided in Section B.2) of my?iMac Pro Syklake-X/X299 macOS 10.13 High Sierra Build and Desktop Guide.?
      ?
      B.3) - Gigabyte BIOS Configuration
      ?
      Please find below the BIOS settings for the Gigabyte Designare EX kindly provided by @jyavenard and @DSM2.
      ?
      1.)?/M.I.T/Advanced Frequency Settings/
      a.) Extreme Memory Profile: (X.M.P): Profile1
      ?
      2.)?/M.I.T/Advanced Frequency Settings/Advanced CPU Core Settings
      ?
      a.) Active Cores Control: Auto
      b.) Hyper-Threading Technology: Enabled
      c.) Intel Turbo Boost Max Technology 3.0 : Enabled
      d.)? Intel Speed Shift Technology : Enabled
      e.) Enhanced Multi-Core Performance: Enabled/Disabled?
      f.) CPU Enhanced Halt (C1E): Enabled
      g.) C6/C7 State Support: Enabled
      h.) Package C State limit: C6
      i.) CPU EIST Function: Enabled
      j.)? Energy Efficient Turbo : Disabled
      ?
      3.)?/M.I.T/Advanced Memory Settings/
      a.) Extreme Memory Profile (X.M.P): Profile1
      ?
      4.)?/BIOS/
      a.) Boot Numlock State: Disabled/Enabled?
      b.) Security option: Setup
      c.) Full Screen Logo Show: Enabled
      d.) Fast Boot: Disabled
      e.) CSM Support: Disabled
      ?
      5.)?/BIOS/Secure Boot/
      a.) Secure Boot Enable: Disabled
      ?
      6.)?/Peripherals/USB Configuration/
      a.) XHCI Hand-off: Enabled
      ?
      7.)?/Peripheral/Thunderbolt Configuration/?
      a.) Security Level : SL0 - No Security
      ?
      8.)?/Chipset/
      a.) VT-d: Disabled/Enabled
      ?
      9.)?/Save& Exit/
      a.) Save & Exit

      ?

      C.)?Important General Note/Advice and Error Prevention

      ?

      Please note the following important General Note / Advice and Error Prevention, when implementing macOS Mojave on your?Skylake-X/X299 System.

      ?

      1.) My?actual respective X299 EFI-Folder distribution?contains by default?AptioMemoryFix.efi thanks to?@vit9696.?Note that already 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.

      ?

      With macOS 10.14.5 Beta 1, also the new Radeon VII is now natively implemented.

      By means of my RadeonVII/Vega64/Vega56/RX560/RX580 SSDTs, available in my respective?X299 SSDT Github repository, and Whatevergreen.kext, all available DP and HDMI ports, including multi-monitor support, display HotPlug and system sleep/wake should be automatically and successfully implemented. 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 AMD SSDTs do pretty well their job.

      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 Prime X299 Deluxe 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 any?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 works?without?hardware acceleration.

      ?

      3.) The?/EFI/Clover/drivers64UEFI/-directory of all former EFI-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.??
      ?
      1705330857_Screenshot2018-06-16at20_13_18.png.9a9a38baf5d38941f11df5d6b6acbb2e.png
      ?
      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.?
      ?
      4.)?To avoid Skylake-X thread TSC desynchronisation errors during boot and wake from S3 with unpatched X299 mainboards, likely induced by yet erroneous Skylake-X 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.?
      ?
      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-7820X. To adopt the kext for Skylake-X processers 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 Skylake-X processor is the number of its threads -1, by always keeping in mind that the number of it's threads is always 2x the number of it's cores.
      ?
      Thus in case of the 8 core i7-7820X, the IOCPUNumber is 15 (16 threads - 1).
      ?
      <key>IOCPUNumber</key>				<integer>15</integer>
      ?
      By following this methodology, the correct IOCPUNumber for the 10-core i9-7900X would be 19 (20 threads -1)
      ?
      <key>IOCPUNumber</key>				<integer>19</integer>
      ?
      and the IOCPUNumber for the 18-core i9-7980XE would result in 35 (36 threads -1).
      ?
      <key>IOCPUNumber</key>				<integer>35</integer>
      ?
      e.) After adopting the IOCPUNumber for your particular Skylake-X processor, save the info.plist file and copy the modified TSCAdjustRest.kext to the /EFI/CLOVER/kexts/Other/ - directories of both USB Flash Drive Installer and System Disk and you are save and all done!

      ?

      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 10.14 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.) All ASUS Prime X299 Deluxe users, who enabled the second LAN controller in the ASUS Prime X299 Deluxe BIOS, are advised to download, unzip and copy the SmallTree-Intel-211-AT-PCIe-GBE.kext??to the EFI-Folders of both USB Flash Drive Installer and 10.14?System Disk, or to disable the second LAN port in the BIOS during the MacOS Installation.?In case of the ASUS WS X299 Sage 10G, remove both IntelMausiEthernet.kext and SmallTree-Intel-211VA-PCIe-GBE.kext from your respective EFI-Folder. ?

      ?

      7.) All Gigabite mainboard users need to add the "npci=0x2000" boot flag to their config.plist by checking the latter in Section "Boot" of Clover Configurator under "Arguments".

      ?

      ?

      D.) iMac Pro 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 Skylake-X/X299 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 X299 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 X299 EFI-Folder distribution.
      ?
      Press several times the "Generate New" Button next to the serial number text field to generate a serial number and board serial number.

      With SMBIOS of an iMacPro1,1 it is not currently possible to verify the validity of the serial number on everymac.com.
      Therefore, verify the validity of your serial number on?appleserialnumberinfo.com?instead.
      ?
      Open the?https://checkcoverage.apple.com?site, paste your Serial Number and confirm that the serial number is not in use yet.

      Finally press several times the "Generate New" button next to SmUUID.
      ?
      Users of mainboards with locked MSR Register (disabled MSR OSX Kernel write access) have to enable 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 and also check "KernelPM".
      ?
      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.

      Enable USB port limit patches:

      Valid USB port limit patches for 10.14.4 provided by @PMHeart (hardwired but yet disabled in my respective EFI-Folder distribution)?by following initial USB port limit patch approach for 10.14.3 by?@ydeng?:
      ?
      kext     : com.apple.iokit.IOUSBHostFamily
      Find     : 83FB0F0F 87
      Replace  : 83FB3F0F 87
      Name     : USB Port Limit Patch 1 ?PMHeart
      kext     : com.apple.driver.usb.AppleUSBXHCI
      Find     : 4183FF0F 0F83
      Replace  : 4183FF3F 0F83
      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

      ?

      Finally save the modified config.plist.
      ?
      3.) Now copy the appropriate TSCAdjustRest.kext, which has been 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.4 (18E226) full package installer (6.04 GB) from the Appstore, follow the individual steps detailed below:

      1.) Open a terminal and create a "041-56507" directory on your Desktop. Subsequently change to the newly created directory. All this can be done with the following terminal commands:
      ?
      mkdir ~/Desktop/041-56507/
      cd ~/Desktop/041-56507/

      ?

      2.) Download the following files from the Apple server (public links) to your ~/Desktop/041-56507/ directory?by a copy & paste of the following terminal commands:

      curl https://swdist.apple.com/content/downloads/32/45/041-56507/k6okp4vkzucqpoxrgrgycji6jo8z8na8sg/041-56507.English.dist -o 041-56507.English.dist
      curl http://swcdn.apple.com/content/downloads/32/45/041-56507/k6okp4vkzucqpoxrgrgycji6jo8z8na8sg/InstallAssistantAuto.smd -o InstallAssistantAuto.smd
      curl http://swcdn.apple.com/content/downloads/32/45/041-56507/k6okp4vkzucqpoxrgrgycji6jo8z8na8sg/AppleDiagnostics.chunklist -o AppleDiagnostics.chunklist
      curl http://swcdn.apple.com/content/downloads/32/45/041-56507/k6okp4vkzucqpoxrgrgycji6jo8z8na8sg/AppleDiagnostics.dmg -o AppleDiagnostics.dmg
      curl http://swcdn.apple.com/content/downloads/32/45/041-56507/k6okp4vkzucqpoxrgrgycji6jo8z8na8sg/OSInstall.mpkg -o OSInstall.mpkg
      curl http://swcdn.apple.com/content/downloads/32/45/041-56507/k6okp4vkzucqpoxrgrgycji6jo8z8na8sg/BaseSystem.chunklist -o BaseSystem.chunklist
      curl http://swcdn.apple.com/content/downloads/32/45/041-56507/k6okp4vkzucqpoxrgrgycji6jo8z8na8sg/InstallESDDmg.chunklist  -o InstallESDDmg.chunklist
      curl http://swcdn.apple.com/content/downloads/32/45/041-56507/k6okp4vkzucqpoxrgrgycji6jo8z8na8sg/BaseSystem.dmg -o BaseSystem.dmg
      curl https://swdist.apple.com/content/downloads/32/45/041-56507/k6okp4vkzucqpoxrgrgycji6jo8z8na8sg/RecoveryHDMetaDmg.pkm -o RecoveryHDMetaDmg.pkm
      curl http://swcdn.apple.com/content/downloads/32/45/041-56507/k6okp4vkzucqpoxrgrgycji6jo8z8na8sg/RecoveryHDMetaDmg.pkg -o RecoveryHDMetaDmg.pkg
      curl https://swdist.apple.com/content/downloads/32/45/041-56507/k6okp4vkzucqpoxrgrgycji6jo8z8na8sg/InstallAssistantAuto.pkm -o InstallAssistantAuto.pkm
      curl http://swcdn.apple.com/content/downloads/32/45/041-56507/k6okp4vkzucqpoxrgrgycji6jo8z8na8sg/InstallAssistantAuto.pkg -o InstallAssistantAuto.pkg
      curl http://swcdn.apple.com/content/downloads/32/45/041-56507/k6okp4vkzucqpoxrgrgycji6jo8z8na8sg/InstallInfo.plist -o InstallInfo.plist
      curl https://swdist.apple.com/content/downloads/32/45/041-56507/k6okp4vkzucqpoxrgrgycji6jo8z8na8sg/MajorOSInfo.pkm -o MajorOSInfo.pkm
      curl http://swcdn.apple.com/content/downloads/32/45/041-56507/k6okp4vkzucqpoxrgrgycji6jo8z8na8sg/MajorOSInfo.pkg -o MajorOSInfo.pkg
      curl https://swdist.apple.com/content/downloads/32/45/041-56507/k6okp4vkzucqpoxrgrgycji6jo8z8na8sg/InstallESDDmg.pkm -o InstallESDDmg.pkm
      curl http://swcdn.apple.com/content/downloads/32/45/041-56507/k6okp4vkzucqpoxrgrgycji6jo8z8na8sg/InstallESDDmg.pkg -o InstallESDDmg.pkg

      ?

      The full list of package files can be found within the following catalog URL, searching for key "k6okp4vkzucqpoxrgrgycji6jo8z8na8sg":

      ?

      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-56507/041-56507.English.dist --package-path ./041-56507/ 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-56507/InstallESDDmg.pkg /Applications/Install\ macOS\ Mojave.app/Contents/SharedSupport/InstallESD.dmg
      sudo cp ./041-56507/AppleDiagnostics.dmg /Applications/Install\ macOS\ Mojave.app/Contents/SharedSupport/
      sudo cp ./041-56507/AppleDiagnostics.chunklist /Applications/Install\ macOS\ Mojave.app/Contents/SharedSupport/
      sudo cp ./041-56507/BaseSystem.dmg /Applications/Install\ macOS\ Mojave.app/Contents/SharedSupport/
      sudo cp ./041-56507/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. (18E226)?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 off @macandrea.?

      createInstaller-10.14.4-23042019.sh?will automatically create on any MacOS System the "Install macOS Mojave.app" for macOS Mojave 10.14.4 (18E226)?in the /Applications folder.

      Just download und unzip?createInstaller-10.14.4-23042019.sh.zip?and run the following terminal commands:

      ?

      cd ~/Downloads
      chmod +x createInstaller-10.14.4-23042019.sh
      ./createInstaller-10.14.4-23042019.sh

      ?

      And here is?createInstaller-10.14.4-SB-23042019.sh,?which will automatically create on any MacOS System the "Install macOS Mojave.app" for macOS Mojave 10.14.4 (18E2034) - special build in the /Applications folder.

      ?

      Just download und unzip createInstaller-10.14.4-SB-23042019.sh.zip and run the following terminal commands:

      ?

      	
      
      	cd ~/Downloads	
      
      	chmod +x createInstaller-10.14.4-SB-23042019.sh	
      
      	./createInstaller-10.14.4-SB-23042019.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 yourmacOS 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 Skylake-X/X299
      ?
      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 do the requested iCloud registration and you will have your first iMac Pro macOS Mojave 10.14 system.
      ?
      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 Skylake-X/X299 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 ("Install macOS Mojave.app") 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 High Sierra Build Updates (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 Skylake-X/X299 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 Mojave from System Disk by else following steps 4.) to 8.) of D.5) above. Any future macOS Mojave update can be directly performed fully vanilla via "Software Update" under "System Preferences".
      ?
      E.)?Post Installation Process
      ?
      E.1) HWP (Intel SpeedShift Technology) CPU Power Management Configuration
      ?
      On Skylake-X/X299 Systems with unlocked mainboard BIOS MSR 0xE2 BIOS register and SMBIOS iMacPro1,1 we gain fully native HWP (IntelSpeedShift) Power Management after disabling the last remaining XCPM KernelToPatch entry "xcpm_core_scope_msrs" in the config.plist under Section "Kernel and Kext Patches" of Clover Configurator, which by default is still implemented but disabled in the config.plist of my?actual respective X299 EFI-Folder distribution.
      ?
      XCPM.thumb.png.53b953035d599b21a9f9b3c973e3f5fb.png
      ?
      Users with locked mainboard BIOS MSR 0xE2 register, still have to use the "xcpm_core_scope_msrs" XCPM KernelToPatch entry to successfully boot their systems. Otherwise the OSX Kernel will write to that BIOS register and cause KP at boot!??
      ?
      HWP is a way for the processor itself to manage the power consumption, with minor input from OSX on what it thinks it needs. In contrary, XCPM is the OSX power management part. It directly controls older hardware like Broadwell-E/EP or Haswell-E/EP and enables HWP on newer hardware like Skylake-X. It also sets some HWP variables, like the desired frequency at the maximum.
      ?
      XCPM is enabled by default.
      ?
      For it's complete configuration, XCPM still requires the CPU "plugin-type" injection to properly load the required XCPM frequency vectors from the iMacPro.plist, which can be directly achieved within the config.plist by checking "PluginType" in Section "ACPI" of Clover Configurator.
      ?
      PluginType.thumb.png.b538366f5cf7090fe0efa017d9a91d21.png
      ?
      How to verify a working xcpm?configuration?
      ?
      a.) Typically the command "sysctl machdep.xcpm.mode" reveals 1, which means that XCPM is active.
      ?
      b.) Verify that in the IORegistryExplorer you have now under CP00@0 the following entry:
      Property:? ? ? ?? Type:? ? ? ?? Value:
      plugin-type? ? ?? Number? ? ? ? 0x1

      c.) Also verify with the terminal command:

      kextstat|grep -y x86plat

      that the "X86PlatformPlugin.kext"?is now 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>

      d.) Verify with the following terminal command:

      kextstat|grep -y appleintelcpu

      that you got rid of the Apple Intel CPU power management. If the result is empty you are fine.

      ?
      e.)? Verify with the following terminal command:
      sysctl -n machdep.xcpm.vectors_loaded_count

      If this command returns "1", the XCPM FrequencyVectors are properly loaded and you are all set.

      ?
      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.
      ?
      With macOS 10.14.5 Beta 1, also the new Radeon VII is now natively implemented.

      By means of my RadeonVII/Vega64/Vega56/RX560/RX580 SSDTs, available in my respective?X299 SSDT Github repository, and Whatevergreen.kext, all available DP and HDMI ports, including multi-monitor support, display HotPlug and system sleep/wake should be automatically and successfully implemented. 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 AMD SSDTs do pretty well their job.
      ?
      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 Prime X299 Deluxe 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 any 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 Betas from Nvidia, which has been rejected. I really hope that Nvidia will not leave the respective community again 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 works without hardware acceleration.?
      ?
      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 e.g. the patched Nvidia Web Driver xxx.40.105?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, Whatevergreen.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, the actual releases of?Whatevergreen.kext?and?Lilu.kext?apparently 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 Nvidia GPU 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 "17G65" to?"18D45", 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 Web Driver implementation for?MacOS Mojave 10.14.
      ?
      E.3) Audio Configuration
      ?
      Note that my?actual respective X299 EFI-Folder distribution?does not contain any default audio configuration. You have to implement the audio approach of your choice during the Post Installation process! Please select between one out of three possible audio implementations detailed below.?To avoid the loss of analogue onboard audio (S1220A in case of the ASUS Prime X299 Deluxe) on Wake from Sleep, please download, unzip and copy the latest CodecCommander.kext distribution of [USER=429483]@RehabMan[/USER] from bitbucket.org to the /EFI/Clover/kexts/Other directory in the EFI-Folder of your System Disk:?https://bitbucket.org/RehabMan/os-x-eapd-codec-commander/downloads/.
      ?
      E.3.1.) AppleALC Audio Implementation
      ?
      The actual AppleALC audio implementation traces back to the extensive efforts and brilliant work of @vit9696 ?and @apfelnico. This new AppleALC audio approach requires latest versions of?AppleALC.kext?and?Lilu.kext?in the /EFI/CLOVER/kexts/Other/ directory of your System Disk.
      ?
      Provided that you use my?actual respective X299 EFI-Folder distribution, you need to open the config.plist in the /EFI/CLOVER/ directory of your System Disk with the Clover Configurator and add the CAVS -> HDEF ACPI replacement patch in Clover Configurator Section "ACPI" under "DSDT Patches".
      ?
      Comment:? ? ? ? ? Find*[Hex]? ?? Replace [Hex]
      CAVS -> HDEF? ? ? 43415653? ? ?? 48444546

      When implementing the SSDT in Section 9.2), we will perform the ?CAVS -> HDEF ACPI replacement directly within the SSDT. We then have to remove again the?CAVS -> HDEF ACPI replacement from the config.plist!

      ?
      Note that opposite to the alternative VoodooHDA and CLoverALC approach detailed below, the AppleALC audio implementation requires an Audio ID in injection of "7" instead of "1". Implement the latter Audio ID in the config.plist of your System Disk under "Audio" and "Injection" in the Section "Devices" of the Clover Configurator.
      ?
      The correct HDAU HDMI/DP digital Audio PCI implementation will be detailed in Section E.9) in line with the HDEF and GPU PCI device implementation.
      ?
      To remove the AppleALC Audio Approach Implementation perform the following steps:
      ?
      1.) Remove?AppleALC.kext from the /EFI/CLOVER/kexts/Other/ directory of your System Disk.
      ?
      2.) Disable in the config. plist the CAVS -> HDEF DSDT Replacement Patch in Clover Configurator Section "ACPI" under "DSDT Patches".
      ?
      3.) Adopt the Audio ID Injection in your respective config.plist in Clover Configurator Section "Devices" for the alternative audio approach you intent to use.
      ?
      4.) Reboot
      ?
      E.3.2) VoodooHDA Audio Implementation
      ?
      1.) Provided that you use my?actual respective X299 EFI-Folder distribution, you need to open the config.plist in the /EFI/CLOVER/ directory of your System Disk with the Clover Configurator and enable the CAVS -> HDEF ACPI Replacement Patch in Clover Configurator Section "ACPI" under "DSDT Patches".
      Comment? ? ? ? ? ? ? ? ? ? ? ?? Find*[HEX]? ? ? Replace*[HEX]
      Rename CAVS to HDEF? ? ? 43415653? ? ? ? 48444546

      When implementing the SSDT in Section 9.2), we will perform the ?CAVS -> HDEF ACPI replacement directly within the SSDT. We then have to remove again the?CAVS -> HDEF ACPI replacement from the config.plist!

      ?
      2.) Download?VoodooHDA.kext v2.9.0d10?to your Desktop. Mouse Right-Click on VoodooHDA.kext -> select "Show Package Contents" -> click on "Contents" -> Right-Click on "Info.plist" -> "Open With" -> "Other" -> select "TextEdit.app"
      ?
      3.) a.) In the TextEdit.app select in the menu "Edit" -> "Find" -> "Find..." -> search for? "IOPCIClassMatch" and
      ?
      replace
      <key>IOPCIClassMatch</key>
      <string>0x04020000&amp;0xfffe0000</string>

      with

      <key>IOPCIPrimaryMatch</key>
      <string>0x43831002</string>

      ?

      b.) Download, unzip and run?IORegistryExplorer.
      ?
      Search for HDEF and write down the "IOName"-entry under e.g. PC00@0/AppleACPIPCI/HDEF@1F,3 which can slightly deviate on mainboards different from the ASUS Prime X299 Deluxe.
      ?
      HDEF.thumb.png.21b8043336bc06f804d7119606fc4b44.png
      ?
      The HDEF-IOName on the ASUS Prime X299 Deluxe is "pci8086,a2f0"
      ?
      Concert the IOName as shown below in case of the HDEF-IOName of the ASUS Prime X299 Deluxe:
      ?
      "0xa2f08086"
      ?
      c.) Now replace in the "Info.plist" of "VoodooHDA.kext"
      ?
      "0x43831002"
      ?
      by
      ?
      "0xa2f08086"
      ?
      and save the "Info.plist".
      ?
      d.) Copy the modified "VoodooHDA.kext" to the /EFI/Clover/kexts/Other/ - directory of your System Disk.
      ?
      4.) Download and copy the?VoodooHDA.prefPane v1.2?attached below to ~/Library/PreferencePanes/
      ?
      5.) Note that the VoodooHDA audio approach requires an Audio ID in injection of "1". The corresponding modification of the config.plist has to be implemented by means of the Clover Configurator by modifying the respective entry in Section "Devices".
      ?
      6.) Reboot
      ?
      To remove the VoodooHDA audio implementation, perform the following steps:
      ?
      1.)? Disable in the config. plist the CAVS -> HDEF ACPI Replacement Patch in Clover Configurator Section "ACPI" under "DSDT
      Patches".
      ?
      2.) Remove VoodooHDA.kext? from the /EFI/CLOVER/kexts/Other/ directory of your System Disk.
      ?
      3.) Remove?VoodooHDA.prefPane?from ~/Library/PreferencePanes/
      ?
      4.) Adopt the Audio ID Injection in your config.plist in Section "Devices" of the Clover Configurator for the alternative audio?approach you intent to use
      ?
      5.) Reboot
      ?
      E.3.3) cloverALC Audio Implementation
      ?
      @toleda 's cloverALC audio approach has been implemented thanks to the respective advices and help of user @Ramalama.?Note that in contrary to the AppleALC and VoodooHDA approaches, the cloverALC audio approach detailed below will patch the native vanilla AppleHDA.kext in the /S/L/E directory of your System Disk! This before implementing the cloverALC audio approach, backup your native vanilla AppleHDA.kext from the /S/L/E directory on your System Disk! You will have to reinstall the native vanilla AppleHDA.kext from the /S/L/E directory on your System Disk with the appropriate permissions during a removal of the cloverALC Audio Implementation! Thus you need a backup of the latter native vanilla kext in any case!???
      ?
      CloverALC audio approach installation:
      ?
      1.) Provided that you use?my?actual respective X299 EFI-Folder distribution,??you need to open the config.plist in the /EFI/CLOVER/ directory of your System Disk with the Clover Configurator and enable the CAVS -> HDEF ACPI Replacement Patch in Clover Configurator Section "ACPI" under "DSDT Patches".
      Comment? ? ? ? ? ? ? ? ? Find*[Hex]? ? Replace[Hex]
      Rename CAVS to HDEF? ? ? 43415653? ? ? 48444546
      When implementing the SSDT in Section 9.2), we will perform the? CAVS -> HDEF ACPI replacement directly within the SSDT. We then have to remove again the CAVS -> HDEF ACPI replacement from the config.plist!
      ?
      2.) Change the Audio ID Injection in the config.plist on your System Disk in Section "Devices" under "Audio" and "Inject" to "1".
      ?
      3.) Add the following cloverALC related KextToPatch entries to your config.plist on your System Disk in section "Kerneland Kext Patches" of Clover Configurator in the "KextsToPatch" listing:
      Name*? ? ? ?? Find*[Hex]? ? ? ?? Replace* [Hex]? ? Comment
      AppleHDA? ? ? 8a19d411? ? ? ? ?? 00000000? ? ? ? ? t1-10.12-AppleHDA/Realtek ALC...
      AppleHDA? ? ? 8b19d411? ? ? ? ?? 2012ec10? ? ? ? ? t1-10.12-AppleHDA/RealtekALC1220
      AppleHDA? ? ? 786d6c2e 7a6c? ? ? 7a6d6c2e 7a6c? ?? t1-AppleHDA/Resources/xml>zml

      ?

      4.) Download, unzip and copy the?realtekALC.kext v2.8? to the /EFI/CLOVER/kexts/Other/ directory on your System Disk
      ?
      5.) Download and execute?audio_cloverALC-130.sh, which will patch the native vanilla AppleHDA.kext in the /S/L/Edirectory of your System Disk
      ?
      6.) Reboot
      ?
      To remove the cloverALC audio implementation, perform the following steps:
      ?
      1.) Remove realtekALC.kext from the /EFI/CLOVER/kexts/Other/ directory on your System Disk
      ?
      2.) Remove all cloverALC related KextToPatch entries from the config.plist on your System Disk? in the "Kernel andKext Patches" section of Clover Configurator.
      ?
      3.)?Disable in the config. plist the CAVS -> HDEF ACPI Replacement Patch in Clover Configurator Section "ACPI" under"DSDT Patches".
      ?
      4.) Delete the patched AppleHDA.kext in the /S/L/E/ Directory on your System Disk
      ?
      5.) Reinstall the original vanilla AppleHDA.kext with the appropriate permission in the /S/L/E/ directory on yourSystem Disk using?Kext Utility
      ?
      6.) Adopt the Audio ID Injection in your config.plist in Section "Devices" of the Clover Configurator for the alternative audioapproach you intent to use
      ?
      7.) Reboot
      ?
      ?
      E.4) USB Configuration:
      ?

      Since 10.13 SU and with AppleIntelPCHPMC, Apple implements IOPCIPrimaryMatchID "a2af8068" and AppleUSBXHCISPT also for the ASUS Prime X299 Deluxe. Until 10.14.0, by this 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 of all X299 mainboards where fully implemented, always provided that one uses a working USB port limit patches.

      ?

      Valid USB port limit patch for 10.14.4 provided by @PMHeart (hardwired but yet disabled in my respective EFI-Folder distribution) by following USB port limit patch approach for 10.14.3 by [USER=1614363]@ydeng[/USER]:

      ?

      USB port limit patch for 10.14.4 provided by @PMheart:

      kext     : com.apple.iokit.IOUSBHostFamily
      Find     : 83FB0F0F 87
      Replace  : 83FB3F0F 87
      Name     : USB Port Limit Patch 1 ?PMHeart
      kext     : com.apple.driver.usb.AppleUSBXHCI
      Find     : 4183FF0F 0F83
      Replace  : 4183FF3F 0F83
      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

      ?

      Former USB port limit patches for 10.14.3 provided by ?ydeng:

      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

      ?

      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-PX299D-XHCI.kext?would be the XHC USB kext for the Prime X299 Deluxe 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 Prime X299 Deluxe):
      ?
      2120939180_Screenshot2018-11-05at08_12_18.png.13e03eb5188d39139b7eddcab8d4c9b3.png
      ?
      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 (HS09, HS10, HS11 or HS12), which further reduces the number of implemented USB ports by one.
      ?
      729473306_Screenshot2018-11-02at02_17_25.thumb.jpg.dc507c28e850302129953b5ad58e8fae.jpg
      ?
      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-PX299D-XHCI-15port.kext, I removed HS03, HS04, SSP3, SSP4?(assigned to the internal USB3.0 header U31G1_34) and HS12?(assigned to the most left USB2.0 connector on the back panel of the mainboard) from the kext. By this, all other USB2.0 and USB3.0 ASUS Prime X299 Deluxe onboard connectors remain fully functional. Alternatively, one could also drop e.g. HS01, HS01, SSP1, SSP2?(assigned to the internal USB3.0 header U31G1_12) or either HS09, HS10?or HS11?from?KGP-iMacPro-ASUS-PX299D-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.
      ?
      Respective XHC USB kexts for the ASUS WS X299 Sage 10G have been kindly provided by @Djlild7hina?and are available in the Github repository. However note that?DJ7-iMacPro-ASUS-WSX299S10G-XHCI.kext.zip?and?DJ7-iMacPro-ASUS-WSX299S10G-XHCI-15port.kext.zip?are identical as HS/SS ports assigned to the USB3.0 connectors/header of the ASUS WS X299 Sage 10G do not exceed Apple's 15-port Usb limit.
      ?
      Remaining USB ejection issues during sleep/wake likely can be fixed by 3rd party software tools like e.g.?mountain.app.
      ?
      ?
      E.5.) NVMe Compatibility
      ?
      In contrary to macOS Sierra 10.12?and as?already?in macOS High Sierra 10.13, under macOS 10.14 Mojave,?there is native support of non-4Kn NVMe SSDs, like my Samsung EVO 970 Pro M.2 NVME. All patches applied under macOS Sierra 10.12 are therefore obsolete. The native support of non-4Kn NVMe SSDs enables the unique opportunity to directly perform a clean-install of macOS High Sierra or Mojave on M.2 NVMEs like the Samsung EVO 970 Pro.
      ?
      E.6.) SSD/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 in?my?actual respective X299 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.
      ?
      Trim.thumb.png.456c6498268abcb97a40536927fc1690.png
      ?
      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 on your 10.13 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 drive to 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 drivers and programs implemented on the?ASUS Prime X299 Deluxe/WS?X299 Sage 10G?Series DVD attached to your mainboard. This will further allow you to properly adjust the desired AURA Mainboard Settings and offer many other? mainboard configuration options.
      ?
      7.) Now switch off your rig and start with the installation of our Thunderbolt 3 Add-In PCIe Adapter
      ?
      On the ASUS Prime X299 Deluxe, I recommend to install any Thunderbolt 3 Add-In PCIe Adapter in the 4th PCIe Slot from top, which is PCIEX_3, while on the ASUS WS X299 Sage 10G any?Thunderbolt 3 Add-In PCIe Adapter must be in the second slot from top PCIEX_2 by default.
      ?
      Prime.png.f3fda07a551c74b3301df1c8a8fca152.png
      ?
      1757721-n0.jpg.87b5d30756c97703798cc4990a173bde.jpg
      ?
      ?
      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:
      ?
      /Advanced/ Thunderbolt(TM) Configuration/
      TBT Root por Selector? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? PCIE16_3 (Prime X299 Deluxe) / PCIE16_2 (WS X299 Sage 10G)
      Thunderbolt USB Support? ? ? ? ? ? ? ? ? ? ? ? ? ?? Enabled
      Thunderbolt Boot Support? ? ? ? ? ? ? ? ? ? ? ? ? ? Enabled
      Wake From Thunderbolt(TM Devices)? ? ? ? ? ? ? ? ?? Off
      Thunderbolt(TM) PCIe Cache-line Size? ? ? ? ? ? ? ? 128
      GPIO3 Force Pwr? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? On
      Wait time in ms after applying Force Pwr? ? ? ? ? ? 200
      Skip PCI OptionRom? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Enabled
      Security Level? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? SL0-No Security
      Reserve mem per phy slot? ? ? ? ? ? ? ? ? ? ? ? ? ? 32
      Reserve P mem per phy slot? ? ? ? ? ? ? ? ? ? ? ? ? 32
      Reserve IO per phy slot? ? ? ? ? ? ? ? ? ? ? ? ? ?? 20
      Delay before SX Exit? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 300
      GPIO Filter? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? Enabled
      Enable CLK REQ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Disabled
      Enable ASPM? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? Enabled
      Enable LTR? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Disabled
      Extra Bus Reserved? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 65
      Reserved Memory? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? 386
      Memory Alignment? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 26
      Reserved PMemory? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 960
      PMemory Alignment? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? 28
      Reserved I/O? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 0
      Alpine Ridge XHCI WA? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Enabled

      ?

      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) Gbit 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 Skylake-X/X299 systems.
      ?
      E.8.1) ASUS Prime X299 Deluxe on-board Gbit Ethernet Functionality
      ?
      Thanks to the?SmallTree-Intel-211-AT-PCIe-GBE.kext, also the Intel I211_AT Gigabit on-board LAN controller of the ASUS Prime X299 Deluxe will be correctly implemented and fully functional, in addition to the Intel I219-V Gigabyte on-board LAN controller of the ASUS Prime X299 Deluxe implemented by means of IntelMausiEthernet.kext (already part of my EFI-Folder distributions). Thus, both ethernet ports on the ASUS Prime X299 Deluxe should now be fully operational..
      ?
      Just download , unzip? and copy the?SmallTree-Intel-211-AT-PCIe-GBE.kext?attached below to the /EFI/Clover/kexts/Other/, reboot and you should be done.
      ?
      E.8.2) 10-GBit Lan Implementations?ASUS Prime X299 Deluxe on-board Gbit Ethernet Functionality
      ?
      E.8.2.1)?ASUS XG-C100C?Aquantia AQC107 10-Gbit NIC
      ?
      Starting with 10.13.2 there is native support for the Aquantia AQTION AQC107 10-GBit NIC of the iMac Pro in form of vanilla kext "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?Aquantia AQTION AQC107 10-GBit PCIe x4?NIC?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 Aquantia AQTION AQC107 10-GBit PCIe x4?NIC?also under 10.13.4 and and later macOS versions.
      ?
      How to successfully implement the?ASUS XG-C100C?Aquantia AQTION AQC107 10-GBit ?PCIe x4 NIC:
      ?
      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 Aquantia AQTION AQC107 10GBit PCIe x4 NIC?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 Aquantia AQTION AQC107 10GBit PCIe x4 NIC?will be natively implemented in macOS High Sierra 10.13.3 and fully functional.
      ?
      2.) To finally use the ASUS XG-C100C Aquantia AQTION AQC107 10GBit PCIe x4 NIC?with macOS builds >10.13.4 and finally also with?10.14, one has to implement the following AppleEthernetAquantiaAqtion KextPatch provided by @Mieze:
      ?
      ?
      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 AQTION AQC107 10GBit PCIe x4 NIC?will refuse the official Windows Lan drivers provided by ASUS and will only work with Apple's customised?Aquantia64v2.0.015.0?boot camp drivers attached below.
      ?
      Preferable AQC107 10-Gbit NIC PCIe solutions now available on?the market are the?Syba 1 Port PCIe x4 10GB ?Aquantia AQTION AQC107 NIC?(thanks to @mirwaiz for his respective discovery and for all subsequent confirmation of his findings by @mm2margaret?, who also pointed me to this extremely valid approach) and the?1 Port PCIe x4 10GB Aquantia AQtion AQC107 10G Gaming NIC?(thanks to @izo1 for respective findings and advises), which are natively implemented under macOS OoB and neither need the above firmware update nor the respective AppleEthernetAquantiaAqtion kext patch.
      ?
      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.
      ?
      Some additional notes to the EEPROM modding guideline provided by the above link.
      ?
      1.) When creating your Ubuntu USB Flash Drive, use?RUFUS 3.0?and select the GPT option to obtain a Ubuntu USB boot drive, fully compatible with your UEFI BIOS implementation!
      ?
      2.) To install "net-tools", enter the following terminal command
      sudo apt install net-tools

      ?

      ?
      3.) To install "ethtool" enter the following terminal command:
      sudo apt-get install ethtool

      ?

      ?
      4.) Within the latest Ubuntu distributions, ETH0, ETH1, etc. have been replaced by some weird "enp" port-nomenclature, thus the command "ifconfig" would reveal something like the following:
      ?
      ifconfig.thumb.jpg.291609c36d0f3fd7cb0ac74ec6665c6b.jpg
      ?
      My Intel X540-T1 was assigned to enp225s0.
      ?
      5.) With the command "lspci -nn -vvv | grep Ethernet" you have to use in 6.) the Vendor/Device-ID entry highlighted by the green rectangle.
      ?
      Vendor-ID.png.65c99a6c2d61d978931c8a7d3f91712d.png
      ?
      6.) By running the "sudo ethtool -e enp225s0 | less" command and eyeballing the offsets, be aware that the latter can be distributed over two lines:
      ?
      offsets.thumb.png.a3acf2603a65e719b85654a261420cd1.png
      ?
      ?
      You have to count from left to right 0,1,2,3,4,5,6,7,8,9,a,b,c,d,e,f for each pair of digits for each offset.
      ?
      Thus, the commands I had to run to mod the Intel X540-T1 EEPROM were:
      sudo ethtool -E enp225s0 magic 0x15288086 offset 0x48e value 0x0a
      
      sudo ethtool -E enp225s0 magic 0x15288086 offset 0x48f value 0x00

      ?

      Note that the "magic" value implemented in this command has been taken from the "lspci -nn -vvv | grep Ethernet" command output, again encircled by a green rectangle:
      ?
      1799042842_Vendor-ID2.png.56a94f780f7b22d4dafce9cb4282b554.png
      ?
      The rest is as described in the EEPROM modding guideline linked above.
      ?
      The proper Intel X540-T1 PCI SSDT implementation is detailed in Section E.9.2)
      ?
      Actually, I am now currently using this adaptor in my X99 system configuration.
      ?

      E.8.2.3)?Onboard Intel X550-AT2 10-Gbit NICs of the ASUS WS X299 Sage 10G

      ?

      The same Ubuntu EEPROM modding detailed in E.8.2.2) can be also applied for the 2x onboard Intel X550-AT2 NICs of the ASUS WS X299 Sage 10G.

      ?

      In my case I deduced the following Ubuntu terminal commands for performing the final Ubuntu EEPROM modding:

      ?

      sudo ethtool -E enp179s0f0 magic 0x15638086 offset 0x242 value 0x0a
      sudo ethtool -E enp179s0f0 magic 0x15638086 offset 0x243 value 0x00
      sudo ethtool -E enp179s0f1 magic 0x15638086 offset 0x242 value 0x0a
      sudo ethtool -E enp179s0f1 magic 0x15638086 offset 0x243 value 0x00

      Note that the enp address can vary with the Ubuntu version.

      ?
      E.8.2.4)?Small-Tree P2EI0G-2T 10-Gbit NIC
      ?
      The?Small-Tree P2EI0G-2T?2-Port 10GB LAN PCIe Adapter constitutes the actual base line in my 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.5)?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.6) QNAP TS-431X2 Quad-core 4-Bay NAS tower
      ?
      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.7) 10-GBit Ethernet Optimisation
      ?
      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 Prime X299 Deluxe / WS X299 Sage 10G?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. 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 X299 EFI-Folder distribution. Others are part of my System SSDTs provided in my?X299-System-SSDTs Github repository.

      Note that the ACPI DSDT Replacements in config.plist and System SSDTs are build and PCIe slot population dependent and have to be verified and adopted or modified for all mainboards different from the ASUS Prime X299 Deluxe and builds or PCIe slot populations different from the one that constitutes the baseline of this guide.
      ?
      For the ASUS Prime X299 Deluxe and ASUS WS X299 Sage 10G I will use in the following the PCIe Slot nomenclature depicted below:
      ?
      ASUS Prime X299 Deluxe:
      ?
      ASUSPrimeX299Deluxe-PCI-Slot-Nomenclature.thumb.png.9c67e3562cea6d9f90cdaf83e3b77e87.png
      ?
      ASUS WS X299 Sage 10G:
      ?
      2111941963_Screenshot2019-03-21at14_20_56.thumb.jpg.6ccd90af07810fec4f85026036f76460.jpg
      ?
      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-X299-iMacPro.aml has been split into separated modules now forming part of my?X299-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 in the /EFI/CLOVER/ directory of my?actual respective X299 EFI-Folder distribution?or are directly part of the System SSDTs provided in my?X299-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.) The PC00 -> PCI0 ACPI DSDT replacement patch has the main aim to achieve a SMBIOS iMacPro1,1specific PCI implementation. Note that under SMBIOS iMacPro1,1 all other PC0x definitions remain unchanged.
      ?
      Please enable now the PC0x -> PCIx ACPI DSDT replacement patch.
      Comment:? ? ? ? ? ? Find*[Hex]? ?? Replace [Hex]
      PC00 -> PCI0? ? ? ? 50433030? ? ?? 50434930

      ?

      b.) OSI -> XOSI, EC0_ -> EC__ and H_EC? -> EC__ are once more ACPI DSDT replacement patches to achieveconsistency with the SMBIOS iMacPro1,1 variable naming.
      ?
      i.) XOSI functionality is required as explained by @RehabMan.
      ?
      The ACPI code can use the_OSI method (implemented by the ACPI host) to check which Windows version is running. Most DSDT implementations will vary the USB configuration depending on the active Windows version. When running OS X, none of the DSDT _OSI("Windows <version>") checks will return "true" as there is only response from "Darwin". This issue can be solved by implementing the "OS Check Fix" family of DSDT patches in the SSDT. By DSDT patching we can simulate a certain version of Windows although running Darwin and we can obtain a system behaviour similar to a windows version specific environment.
      ?
      ii.) On the Asus X299 Prime Deluxe?/ WS X299 Sage 10G and most likely on all other X299 mobos we have the EC0 and H_EC controllers,which have to be renamed to 'EC' for proper USB power management.? Thus once more investigate your mainboard specific IOREG entry and enable both EC0_ -> EC__ or 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

      ?

      c.) The HEC1 -> IMEI and IDER->MEID ACPI DSDT Replacement patches are Intel Management Engine Interface relatedand 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 ACPI DSDT Replacement patches independent from your mainboard.
      Comment:? ? ? ? ? ?? Find*[Hex]? ? ?? Replace [Hex]
      HEC1 -> IMEI? ? ? ?? 48454331? ? ? ?? 494d4549
      IDER->MEID? ? ? ? ? 49444552? ? ? ?? 4d454944

      ?

      d.) The LPC0 -> LPCB ACPI DSDT Replacement Patch is AppleLPC and SMBus related and is applied for consistency withthe variable naming on a real Mac. Note that LPCB injects AppleLPC, which however is not required in the X299 environment. X299 Systems seem to have sleep problems with the SMBus properties injected. Thus, LPCB will not be implemented by means of any SSDT.
      ?
      Please enable now this ACPI DSDT replacement patch independent from your mainboard.
      Comment:? ? ? ? ? ?? Find*[Hex]? ? ? ?? Replace [Hex]
      LPC0 -> LPCB? ? ? ?? 4c504330? ? ? ? ?? 4c504342

      ?

      e.) FPU_->MATH, TMR_->TIMR, PIC_->IPIC are all ACPI DSDT Replacement Patches for consistency with the variablenaming on a real Mac. The variables are however functionless on either our X299 boards or real Macs.
      ?
      Please enable now all three ACPI DSDT Replacement Patches independent from your mainboard.
      Comment:? ? ? ? ? ?? Find*[Hex]? ? ? ? Replace [Hex]
      FPU_ -> MATH? ? ? ?? 4650555f? ? ? ? ? 4d415448
      TMR_ -> TIMR? ? ? ?? 544d525f? ? ? ? ? 54494d52
      PIC_ -> IPIC? ? ? ?? 5049435f? ? ? ? ? 49504943

      ?

      f.) The SMBS._ADR -> XSBU.XADR Replacement frees SBUS two show up in IOREG. In principle we have two devices with the same address, one called SMBS and the other one called SBUS. SBUS will never show up in IOREG as long SMBS exists. But SBUS is exactly the variable we need in concordance with the IOREG from the iMacPro Dump.
      ?
      Please enable now this ACPI DSDT replacement patch independent from your mainboard.
      Comment:? ? ? ? ? ? ? ? ? ? ?? Find*[Hex]? ? ? ? ? ? ? ? ? ?? Replace [Hex]
      SMBS._ADR -> XSBU.XADR? ? ? ?? 534d4253 085f4144 52? ? ? ? ?? 58534255 08584144 52

      ?

      g.) The DSM -> XDSM DSDT replacement patch is vital for loading the SSDT-X299-iMacPro.aml, as all DSM methods used in theoriginal 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

      ?

      h.) The 56 CPxx -> PRxx replacements are i9-7980XE specific and result in a proper CPU core reordering as well as in a iMac Pro specific CPU core variable naming.
      ?
      All i9-7980XE users can now enable all 56 CPxx -> PRxx replacements. All users of CPUs different from the i9-7980XE have to adopt/modify the 56 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
      CP0E -> PR10? ? ? ?? 43503045? ? ? ? ? 50523130
      CP0F -> PR11? ? ? ?? 43503046? ? ? ? ? 50523131
      CP10 -> PR12? ? ? ?? 43503130? ? ? ? ? 50523132
      CP11 -> PR13? ? ? ?? 43503131? ? ? ? ? 50523133
      CP12 -> PR14? ? ? ?? 43503132? ? ? ? ? 50523134
      CP13 -> PR15? ? ? ?? 43503133? ? ? ? ? 50523135
      CP14 -> PR16? ? ? ?? 43503134? ? ? ? ? 50523136
      CP15 -> PR17? ? ? ?? 43503135? ? ? ? ? 50523137
      CP1C -> PR18? ? ? ?? 43503143? ? ? ? ? 50523138
      CP1D -> PR19? ? ? ?? 43503144? ? ? ? ? 50523139
      CP1E -> PR20? ? ? ?? 43503145? ? ? ? ? 50523230
      CP1F -> PR21? ? ? ?? 43503146? ? ? ? ? 50523231
      CP20 -> PR22? ? ? ?? 43503230? ? ? ? ? 50523232
      CP21 -> PR23? ? ? ?? 43503231? ? ? ? ? 50523233
      CP22 -> PR24? ? ? ?? 43503232? ? ? ? ? 50523234
      CP23 -> PR25? ? ? ?? 43503233? ? ? ? ? 50523235
      CP24 -> PR26? ? ? ?? 43503234? ? ? ? ? 50523236
      CP25 -> PR27? ? ? ?? 43503235? ? ? ? ? 50523237
      CP2A -> PR28? ? ? ?? 43503241? ? ? ? ? 50523238
      CP2B -> PR29? ? ? ?? 43503242? ? ? ? ? 50523239
      CP2C -> PR30? ? ? ?? 43503243? ? ? ? ? 50523330
      CP2D -> PR31? ? ? ?? 43503244? ? ? ? ? 50523331
      CP2E -> PR32? ? ? ?? 43503245? ? ? ? ? 50523332
      CP2F -> PR33? ? ? ?? 43503246? ? ? ? ? 50523333
      CP30 -> PR34? ? ? ?? 43503330? ? ? ? ? 50523334
      CP31 -> PR35? ? ? ?? 43503331? ? ? ? ? 50523335
      CP0A -> PR36? ? ? ?? 43503041? ? ? ? ? 50523336
      CP0B -> PR37? ? ? ?? 43503042? ? ? ? ? 50523337
      CP0C -> PR38? ? ? ?? 43503043? ? ? ? ? 50523338
      CP0D -> PR39? ? ? ?? 43503044? ? ? ? ? 50523339
      CP16 -> PR40? ? ? ?? 43503136? ? ? ? ? 50523430
      CP17 -> PR41? ? ? ?? 43503137? ? ? ? ? 50523431
      CP18 -> PR42? ? ? ?? 43503138? ? ? ? ? 50523432
      CP19 -> PR43? ? ? ?? 43503139? ? ? ? ? 50523433
      CP1A -> PR44? ? ? ?? 43503141? ? ? ? ? 50523434
      CP1B -> PR45? ? ? ?? 43503142? ? ? ? ? 50523435
      CP26 -> PR46? ? ? ?? 43503236? ? ? ? ? 50523436
      CP27 -> PR47? ? ? ?? 43503237? ? ? ? ? 50523437
      CP28 -> PR48? ? ? ?? 43503238? ? ? ? ? 50523438
      CP29 -> PR49? ? ? ?? 43503239? ? ? ? ? 50523439
      CP32 -> PR50? ? ? ?? 43503332? ? ? ? ? 50523530
      CP33 -> PR51? ? ? ?? 43503333? ? ? ? ? 50523531
      CP34 -> PR52? ? ? ?? 43503334? ? ? ? ? 50523532
      CP35 -> PR53? ? ? ?? 43503335? ? ? ? ? 50523533
      CP36 -> PR54? ? ? ?? 43503336? ? ? ? ? 50523534
      CP37 -> PR55? ? ? ?? 43503337? ? ? ? ? 50523535

      ?

      Resulting CPU Core Implementation:
      ?
      CPU-core-implementation.thumb.png.ded9dbfb08781c47e4a7cfa726da6ac2.png
      ?
      ?
      ?
      E.9.2)?System SSDT PCI Device Implementation
      ?
      ASUS Prime X299 Deluxe
      ?
      PCI.jpg.67473e279d9a4681fdcd6b0a9b50eaec.jpg
      ?
      ?
      ASUS WS X299 Sage 10G
      ?
      1823445905_Screenshot2019-03-22at01_57_02.jpg.3aa3b2aad9f13f66a29e08450d9db105.jpg
      ?
      ?
      For the proper PCI device driver implementation (detailed in the figure above), within my?X299-System-SSDTs Github repository?one finds two sets of system SSDTs for the ASUS Prime X299 Deluxe and the?ASUS WS X299 Sage 10Grespectively, which partly need to be modified/adapted/extended, depending on the user specific motherboard, device or PCIe Slot population/configuration. How to adopted or modify ACPI path, ACPI replacements and respective SSDT Device definitions is detailed within?this short guideline?by means of the OSXWIFI PCIe Adaptor implementation in PCIe Slot-3 of the ASUS Prime X299 Deluxe. Further note, that any PCIe devices in respective PCIe slots on e.g. the ASUS WS X299 Sage 10G, sharing the same PCI device on different PCI bridges, like PC02.BR2A.SL05 in case of the ANS1 NVME controller in Slot-1 (PCI bridge @10) and in case of the ARPT OSXWIFI Broadcom BCM94360CD BT/WIFI PCIe Adapter in Slot-3 (PCI bridge @08), need to be implemented in the same system SSDT, like in case of SSDT-X299-Slot1-Slot3-PC02-BR2A-SL05-ANS-ARPT.aml for the ASUS WS X299 Sage 10G.

      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 PCI Audio Controller PCI Implementation:

      The?SSDT-X299-HDEF.aml?onboard Realtek ALC S1220A Audio Controller chipset HDEF PCI device implementation is valid for the ASUS Prime X299 Deluxe ?/ ASUS WS X299 Sage 10G?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 CAVS -> HDEF replacement directly performed within the SSDT!

      E.9.2.2) - GFX0, HDAU - GPU and HDMI/DP Audio PCI implementation:
      ?
      A.) Radeon RX Vega 64 GPUs

      The?SSDT-X299-Vega.aml?GFX0 and HDAU PCI device implementation is valid for SMBIOS iMacPro1,1 (GFX0), the ASUS Prime X299 Deluxe 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 with a Vega graphics card in a PCIe slot different from PCIe Slot 1 or with a mainboard different from the ASUS Prime X299 Deluxe, will have to adopt the respective device path entries PC02.BR2A, ACPI DSDT replacements and PCIe Slot definition following their respective IOREG entries. Note in this context the actual SL05 -> PEGP ACPI DSDT replacements directly performed within the SSDT.

      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" and "PP_DisablePowerContainment" and "PP_FuzzyFanControl" SSDT implementation.

      Everybody can change the respective Vega properties by means of VTGTab-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-X299-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, 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:?
      with the help of the IORegistryExplorer.
        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.2. 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 and 10.14.0). 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 successful system sleep/wake..
      ?
      SSDT-X299-Vega-Frontier.aml?contains former?Kamarang frame buffer SSDT implementation by @apfelnico for 1x Radeon Vega Frontier in PCIe Slot 1 of ASUS Prime X299 Deluxe.
      ?
      For any AMD RX Vega 64 in Slot-5 under PCI device PC01.BR1A.SL01 on PCI bridge @10, one finds a dedicated system SSDT?SSDT-X299-Slot5-PC01-BR1A-SL01-Vega64.aml?in the?ASUS WS X299 Sage 10G subdirectory of the X299 SSDT Github repository. Be careful though, the implemented OC load table is for my water blocked Nitro+ RX Vega 64 and should not be used for any Vegas with air flow fan cooling. Latter users should implement the load table from??SSDT-X299-Vega64.aml?for the ASUS Prime X299 Deluxe or generate their own GPU load table suited for their respective Vega 64 hardware implementation.
      ?
      B.) Radeon VII, Vega56, RX560 and RX580 GPUs

      Note that there also Radeon VII, Vega56, RX580 and RX560 SSDTs available in my?X299 SSDT Github repository, which likely need to be adopted depending on your motherboard and GPU PCIe slot population by following your original IOREG ACPI table information.
      ?
      C.) Nvidia GPUs??

      The actual?SSDT-X299-Nvidia.aml?GFX0 and HDAU PCI device implementation is valid for SMBIOS iMacPro1,1 (GFX0), the ASUS Prime X299 Deluxe 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 graphics card, with a Nvidia graphics card in a PCIe slot different from PCIe Slot 1 or with a mainboard different form the ASUS Prime X299 Deluxe, will have to adopt the respective device path entries PC02.BR2A, ACPI DSDT replacements and PCIe Slot definitions following their respective IOREG entries. Note in this context the actual SL05 -> PEGP and PEGP -> GFX0 ACPI replacements directly performed within the SSDT.

      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 X299 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.?

      Users of Whatevergreen.kext might be able to drop this KextToPatch entry, as the latter kext already properly implements the Nvidia HDAU PCI driver.

      ?
      ?
      E.9.2.3) - PMCR - onboard Power Management Controller (PMC) PCI Implementation:

      The?SSDT-X299-PMCR.aml?onboard Power Management PMCR PCI device implementation should be valid for all X299 mainboards and should not require any build specific adaptation/modification. Note the PMC1 -> PMCR ACPI replacement directly performed within the SDDT.

      E.9.2.4) - 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-X299-USBX.aml?PCI device implementation fixes this errors.

      E.9.2.5) - XHCI - onboard Extended Host Controller Interface (XHCI) PCI Implementation:

      The?SSDT-X299-XHCI.aml?USB3.0 ASMedia ASM1074 / Intel X299 Series Chipset XHCI PCI device implementation is valid for the ASUS Prime X299 Deluxe / ASUS WS X299 Sage 10G?and for all other X299 mainboards with the same XHC controller chipset. Verify and adopt/modify if necessary device path "PCI0.XHCI" and XHCI PCI device implementation by means of IOREG.

      E.9.2.6) - XHC2,3,4 - ASMedia ASM3142 USB 3.1 Controller PCI Implementation:

      The?SSDT-X299-XHC.aml?onboard ASMedia ASM3142/ASM1543 USB 3.1 XHC2,XHC3,XHC4 controller PCI device implementation is valid for the ASUS Prime X299 Deluxe and for all other X299 mainboards with the same XHC USB3.1 controller ASMedia ASM3142 chipset configuration. Note the following ACPI Replacements

      PCI0.RP01.PXSX -> PCI0.RP01.XHC2
      PCI0.RP05.PXSX -> PCI0.RP01.XHC3
      PCI0.RP07.PXSX -> PCI0.RP01.XHC4

      within the SSDT in concordance with the respective SMBIOS iMacPro1,1 variable naming. Verify and adopt/modify if necessary the corresponding "PCI0.RP01.XHC2", "PCI0.RP05.XHC3", "PCI0.RP07.XHC4" PCI device implementations by means of IOREG.
      ?
      Note that there is a separate?SSDT-X299-XHC.aml?device implementation for the ASMedia ASM3142 USB3.1 XHC1 and XHC2 controllers on the ASUS WS X299 Sage 10G in the?ASUS WS X299 Sage 10G subdirectory of the X299 SSDT Github repository.

      E.9.2.7) ANS1, ANS2 - Apple NVMe Controller PCI Implementation:

      The?SSDT-X299-ANS.aml?Apple NVMe Controller ANS1 and ANS2 PCI implementations are of purely cosmetic nature and are valid for the ASUS Prime X299 Deluxe. Note the following ACPI Replacements

      PCI0.RP09.PXSX -> PCI0.RP09.ANS1
      PCI0.RP21.PXSX -> PCI0.RP21.ANS2

      performed within the SDDT in concordance with the respective SMBIOS iMacPro1,1 variable naming.

      Verify and adopt/modify if necessary the "PCI0.RP09.ANS1" and "PCI0.RP21.ANS2" PCI device implementations by means of IOREG.
      ?
      Note that there is a separate?SSDT-X299-ANS.aml?device implementation for the ASUS WS X299 Sage 10G in the?ASUS WS X299 Sage 10G subdirectory of the X299 SSDT Github repository.

      E.9.2.8) - SAT1 - Intel AHCI SATA Controller PCI Implementation:

      The?SSDT-X299-SAT1.aml?onboard Intel AHCI SATA controller PCI device implementation is valid for the ASUS Prime X299 Deluxe / ASUS WS X299 Sage 10G?and for all other X299 mainboards with the same AHCI SATA controller chipset. Verify and adopt/modify if necessary device path "PCI0.SAT1" and PCI device implementations by means of IOREG.

      E.9.2.9) - THSS - Intel Thermal Subsystem Controller Implementation:

      The?SSDT-X299-THSS.aml?onboard Intel X299 Series Thermal Subsystem controller PCI device implementation, recently provided by @apfelnico?is valid for the ASUS Prime X299 Deluxe / ASUS WS X299 Sage 10G?and for all other ASUS X299 mainboards with the same Thermal Subsystem controller chipset.

      E.9.2.10) XGBE - 10GBit NIC Implementation:

      SSDT-X299-ACQU.aml,?SSDT-X299-X540-T1.aml?and?SSDT-X299-P2EI0G-2T.aml?perform a XGBE (XGBF) PCI implementation of an Acquantia AQC107-AFW, Intel X540-T1 and 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 "PC03", "BR3A" and respective SL09 -> PEGP and PEGP -> XGBE ACPI Replacements (in compliance with the iMac Pro 10GB ACPI variable nomenclature), directly performed within each SSDT.
      ?
      Note that there is a separate XGBE/XGBF PCI device implementation SSDT-X299-ETH.aml available for the 2x Intel X550-AT2 10GB onboard NICs of the ASUS WS X299 Sage 10G, which one finds in the?ASUS WS X299 Sage 10G subdirectory of the X299 SSDT Github repository.

      E.9.2.11) - ETH0/ETH1 - onboard LAN Controller PCI Implementation:

      Note that the?SSDT-X299-ETH.aml?Intel I219V2 PCI Express Gigabit Ethernet and Intel I211VA PCI Express Gigabit Ethernet onboard LAN controller ETH0/ETH1 PCI implementations are of pure cosmetic nature and only valid for ASUS Prime X299 Deluxe or X299 mainboards with the same LAN Controller configuration. Owners of different X299 mainboards have to verify and adopt/modify if necessary the device these PCI device implementations by means of IOREG. Note the PCI0.GBE1 -> PCI0.ETH0, PCI0.RP02.D0A4 -> PCI0.RP02.PXSX and PCI0.RP02.PXSX -> PCI0.RP02.ETH1 ACPI replacements directly performed within the SSDT.
      ?
      Note that there are no onboard 1GB hardware implementations on the ASUS WS X299 Sage 10G, thus E.9.2.11 can be skipped entirely by all users of the latter motherboard.?

      E.9.2.12) - ARPT - OSX WIFI Broadcom BCM94360CD 802.11 a/b/g/n/ac + Bluetooth 4.0 AirPort Controller PCI Implementation:

      The?SSDT-X299-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 3 of the ASUS Prime X299 Deluxe. Users of this PCIe Adapter within a PCIe slot population different from PCIe Slot 3 or on a mainboard different form the ASUS Prime X299 Deluxe have to likely adapt/modify the respective device path "PC03","BR3D","ARPT" and likely also the respective ACPI Replacements PC03.BR3D.SL0C -> PC03.BR3D.PEGP and PC03.BR3D.PEGP -> PC03.BR3D.ARPT, directly performed within the SSDT. Users of the Asus Prime X299 Deluxe onboard Bluetooth chipset controller or with a completely different WIFI/Bluetooth configuration have to adopt the entire Airport PCI implementation by means of IOREG.
      ?
      On the ASUS WS X299 Sage 10G, the ANS2 NVME controller in Slot-1 (PCI bridge @10) and the ARPT OSXWIFI Broadcom BCM94360CD BT/WIFI PCIe Adapter in Slot-3 (PCI bridge @08) share the same PCI device on different PCI bridges and therefore need to be implemented within the same system SSDT, namely SSDT-X299-Slot1-Slot3-PC02-BR2A-SL05-ANS-ARPT.aml, which one finds in the?ASUS WS X299 Sage 10G subdirectory of the X299 SSDT Github repository.
      ?
      E.9.2.13) - 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-X299-TB3HP.aml?constitute workarounds for achieving TB HotPlug and USB-C HotPlug functionality with the respective GC-Titan Ridge, GC-Alpine Ridge and TBEX 3 Add-In adapters.

      ?

      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.
      ?

      Video: GC-Titan Ridge TB HotPlug + TB USB-C HotPlug under macOS Mojave 10.14.0?

      ?

      GC-Titan Ridge + ASUS Prime X299 Deluxe + SSDT-X299-TB3HP-TTR.aml +TB HotPlug TB + TB USB-C HotPlug successfully verified under macOS Mojave 10.14.0

      ?

      1728868063_Screenshot2018-09-27at07_20_25.thumb.png.bcbf99b75ddf3b99bc9b01abf33496e8.png

      ?

      Klick the link below to see the video:

      ?

      https://youtu.be/8P0X5Z7giEg

      ?

      Like always, I verified TB HotPlug with my ?5 TB Lacie Rugged Thunderbolt 2 HDD (+ Apple TB3 -> TB2 adopter) and TB USB-C HotPlug with my Transcend JetFlash 850 USB 3.1 Type-C Stick.

      ?

      In the meanwhile, I also successfully verified?GC-Titan Ridge + ASUS Prime X299 Deluxe + SSDT-X299-TB3HP-TTR.aml +TB HotPlug TB + TB USB-C HotPlug?under macOS High Sierra 10.13.6
      ?
      I also successfully verified the?GC-Titan Ridge DisplayPort 1.4 and DisplayPort 1.4 HotPlug?functionality?
      ?
      image.png.494136e19ea7086c837c9b9bd37c23ed.png
      ?
      ?
      ?
      as well as the?Kanex Premium USB-C -> HDMI 4K Adapter?and? Kanex Premium USB-C -> HDMI 4K?Adapter HotPlug functionality.
      ?
      image.png.23fddc9e2353435de5689d941e01f33b.png
      ?
      image.thumb.png.634288dbcaf0059c0fff6b42d0f52a47.png
      ?
      Remaining issues:?With the ASUS Prime X299 Deluxe, one faces a black screen (KP) issue on wake from sleep with TB devices connected to the GC-Titan Ridge during sleep. The issue can be omitted by disconnecting TB devices primer to system sleep. There are no sleep/wake issues with USB-C devices connected to the GC-Titan Ridge.?

      Note that there is a separate SSDT-X299-TB3H.aml for TB3 Add-in PCIe adapters in Slot-2 under PCI0.RP05.PXSX of the ASUS WS X299 Sage 10G, which is also compatible with the ASUS Prime X299 Deluxe II onboard TTR implementation and accessible in the?ASUS WS X299 Sage 10G subdirectory of the X299 SSDT Github repository. Test on GC-TTR / ASUS WS X299 Sage 10G functionality/compatibility are currently ongoing.?

      ?

      E.9.2.14) - 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.15) - 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
      ?
      ASUS-Splash-Screen.png.19b30cd11094e87f395d7c1d9c2e8c79.png
      ?
      by means of the following procedure:
      ?
      1.) Installation of the BREW distribution (if not already performed in Section B.1):
      ?
      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. If not already performed in Section B1.), just 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"...
      ?
      Guid-Search.png.3f8df668ab943fdd9305a6c283ef7649.png
      ?
      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.
      ?
      UefiTool.png.757acdabe4f1de99964ad83bc9fb30a6.png
      ?
      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, it seems that we achieved a major step forward in properly monitoring Skylake-X/X299 Hardware with iStatMenus. iStatMenus now correctly interfaces with the HWSensor and FakeSMC kext distribution provided by @interferenc.
      ?
      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 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/.
      ?
      Many thanks to both @interferenc and @Bjango for their awesome and extensive contributions and brilliant work!
      ?
      Note that I recently modified the Kozlek/Interferenc Source Code distribution locally to also support GPU Temp sensor information for all Vegas and the new Radeon VII. In my recent 10.14 X299 EFI-Folder distributions, the resulting FakeSMC.kext and HWSensor.kexts supporting all Vegas already have been implemented by default in /EFI/CLOVER/kexts/Other. The actual 10.14.5 Beta X299 EFI-Folder distribution contains FakeSMC.kext and HWSensor.kexts also supporting the new Radeon VII.?
      ?
      Skylake-X/X299 iStatMenus Hardware Sensor Data:
      ?
      iStatMenues.thumb.png.95239adab2afe08c576d28d40fec2f6a.png
      ?
      Skylake-X CPU Thread Utilisation Graphs:
      ?
      iStatMenus-CPU-Utilization.png.52b89ab52f63fc9419ded69de7ac2747.png
      ?
      To change from CPU core to thread utilisation monitoring, uncheck "Hide Hyper-Threading cores" in Section "CPU & GPU" of iStatMenus Preferences.
      ?
      iStatMenus-Preferences-1.png.642bb6d0282f23067347035e6d2d5064.png
      ?
      Temperature unites can be adjusted between Celsius, Fahrenheit and Kelvin in Section "Sensors" of iStatMenus Preferences.
      ?
      iStatMenus-Preferences-2.png.192f47c3202c8f8dc3b49438d8714b3b.png
      ?
      F.) Benchmarking
      ?
      F.1) Sylake-X Intel I9-7980XE (4.7GHz) CPU Benchmarking
      ?
      Jesus?:drool:
      ?
      Geekbench.thumb.png.585ccb3a4485de25a430b00b7787a07f.png
      ?
      Cinebench-CPU.png.06ca5dcb1d4495feec3ffd6e69acb46e.png
      ?
      F.2) Sapphire Nitro+ RX Vega 64 8GB
      ?
      615138185_Screenshot2018-09-25at08_34_50.png.530d3604857fcaee3850393cca8c61d7.png
      ?
      1613909697_Screenshot2018-09-25at08_37_17.png.dd6441b8a568f3c9e3cd6728dce8f0b3.png
      ?
      Cinebench-OpenGL.png.b3995342d1c6064cfe22b696a62aed5a.png
      ?
      OpenCL.thumb.png.dc9c74480a2792d13caab0f4f4336ad1.png
      ?
      Metal2.thumb.png.25ea1c050289b3db6065ed190277d753.png
      ?
      Heaven.jpg.abca0294a068bf0dbd0830febf84a2e1.jpg
      ?
      Valley.jpg.5f1c58e7b52383a60847ed50d1183743.jpg
      ?
      ?
      ?
      ?
      G.) Summary and Conclusion
      ?
      Already?under?macOS 10.13 High Sierra, Syklake-X/X299 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 Skylake-X/X299 potential!
      ?
      High-end builds based on extremely novel Skylake-X/X299 technology have found manifold application, not only in science and research at universities or research institutions, engineering facilities, or medical labs, etc... Skylake-X processors with up to 18 cores (36 threads) and turbo frequencies up to 4.8?GHz have made X299 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. Skylake-X/X299-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 Skylake-X 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 Skylake-X/X299 Systems perform absolutely stable on a 24/7/365 basis.
      ?
      ?
      post-1362934-0-41431100-1516222345.png

      ?

      • Like 5
      • Thanks 2

      Guide History Log:

      ?

      06.06.2018:?Writing up guide

      ?

      08.06.2018: Guide Setup complete. Yet missing benchmarks. Problems with CPU Idle frequency temperature: 50 deg C @1.2Ghz Idle. Max. load temps saturate at 105 deg C. GPU?Benchmarks postponed until a 10.14 Nvidia Web Driver has been released.???

      ?

      10.06.2018: Implementation of new EFI-Folder EFI-X299-10.14-DP1-Release-iMacPro1,1-100618

      EFI-Folder related changes:?Implementation of Boot Loader Clover_v2.4k_r4522;?Adding SMCHelper-64.efi and VBoxHfs-64.efi in /EFI/Clover/drivers64UEFI/ solved the issue with the USB macOS Installer partition being invisible in the Clover Boot Loader Menu.?Sorry for any inconvenience caused by the previous EFI-Folder distribution.

      ?

      16.06.2018: Implementation of new EFI-Folder?EFI-X299-10.14-DP1-Release-iMacPro1,1-160618.

      EFI-Folder related changes:??Implementation of Boot Loader Clover_v2.4k_r4548;?Removal of aspf.efi from /EFI/CLOVER/drivers64UEFI/;?Adding ApfsDriverLoader.efi to /EFI/CLOVER/drivers64UEFI/;?Adding AGPMEnabler.kext to/EFI/CLOVER/kexts/Other (thanks to @apfelnico)

      Guide related changes: ?Update of Section C.3) with explanations to?aspf.efi,?ApfsDriverLoader.efi and Clover Package Creation.

      ?

      18.06.2018: Modifications of Vega 64 and Frontier SSDT implementations.

      ?

      19.06.2018:??Guide Update 10.14 DP2 (18A314h);?Implementation of?EFI-X299-10.14-DP2-Release-iMacPro1,1-190618.

      EFI-Folder related changes:??Implementation of Boot Loader Clover_v2.4k_r4558; Implementation of 10.14 DP2 USB port limit patch. ?

      ?

      21.06.2018:?SSDT-TB3-L02-BR1X.aml?modified.?

      ?

      24.09.2018:?System and Guide Update to 10.14.0 (18A391) completed. Guide related changes: New Section D.2) with manual and automatic "Install macOS Mojave.app" full package installer creation approach; Revised Section E.7)?GC-Titan Ridge?/ GC-Alpine Ridge /Asus TBEX 3 PCIe Add-In Implementation; Revised Section E.9.2) with?new?System SSDTs;?Revised Section E.9.13)?GC-Titan Ridge?/ GC-Alpine Ridge / Asus TBEX 3 Thunderbolt HotPlug System Implementation; New EFi-Folder?EFI-X299-10.14.0-Release-iMacPro1,1-240918.zip. EFI-Folder related changes: Implementation of Clover_v2.4k_r4674; Removal of Beta Boot Flags for Lilu and Lilu Plugins.

      ?

      31.10.2018:?Guide update to macOS Mojave 10.14.1 (18B75). Modified section E.4 - USB Configuration for 10.14.1 USB2.0 and USB3.0 compatibility. New EFI-Folder?EFI-X299-10.14.1-Release-iMacPro1,1-311018.zip. EFI-Folder related changes: Implementation of Clover_v2.4k_r4726; Disabling AppleUSBXHCI USB port limit kexts patch in config.plist.. non functional under 10.14.1.

      ?

      05.11.2018:?Update of?Section?E.4) -?USB?Configuration?

      ?

      06.12.2018:?Guide update to macOS Mojave 10.14.2 (18C54).?New EFI-Folder?EFI-X299-10.14.2-Release-iMacPro1,1-101218.zip. EFI-Folder related changes: Implementation of Clover_v2.4k_r4805; Implementation of new FakeSMC and HWSensor distribution.

      ?

      23.01.2019:?Guide update to macOS Mojave 10.14.3 (18D42). New EFI-Folder?EFI-X299-10.14.3-Release-iMacPro1,1-230119.zip. EFI-Folder related changes: Implementation of Clover_v2.4k_r4859;

      ?

      25 January 2019:?New EFI-Folders?EFI-X299-10.14.3-Release-iMacPro1,1-250119?and?EFI-X299-10.14.4-Beta1-Release-iMacPro1,1-250119?with Clover_v2.4k_r4862 and new working USB port limit patches.

      ?

      21 March 2019:?System change from ASUS Prime X299 Deluxe to ASUS WS X299 Sage 10G. ASUS WS X299 Sage 10G system configuration successfully added to general guidelines in the originating post of this thread (guide).

      ?

      25 March 2019:?Guide update to 10.14.4. New 10.14.4 EFI-Folder distribution?EFI-X299-10.14.4-Release-iMacPro1,1-250319.zip?in the X299 EFI-Folder Github repository. Clover_v2.4k_r4903 and new 10.14.4 USB port limit patch implementation. Updated FakeSMC and HWSensor distribution. One should also implement latest Lilu.kext, AppleALC.kext and Whatevergreen.kext distributions. Still no native vanilla Radeon VII macOS implementation (still no default Radeon VII device-ID 0x66AF1002 in the vanilla AMDRadeonX5000.kext). Also note new Xcode 10.2 and Xcode 10.2 Command Line distributions.

      ?

      05 April 2019:?New X299 10.14.5 Beta EFI-Folder distribution?EFI-X299-10.14.5-Beta-iMacPro1,1-050419.zip. EFI-Folder related changes: Implementation of Clover_v2.4k_r4918. I also modified Kozlek/Interferenc?FakeSMC/HWSensor source code distribution for adding Radeon VII GPU Temp sensor information and subsequently added new FakeSMC.kext and HWSensor.kexts to /EFI/Clover/kexts/Other. The new GPU Sensor kext should now support all Vegas and also the new Radeon VII, when using iStatMenus.

      Edited by KGP-iMacPro
      Update
      6 hours ago, KGP-iMacPro said:

      -----------

      ?

      All mainboard users who do not employ ASUS mainboards with patched BIOS firmware need to download, adopt and add?TSCAdjustReset.kext?

      ?

      ?

      ?

      post-1362934-0-41431100-1516222345.png

      ?

      Thank you for your upcoming guide.

      When you have some time could you elaborate better the part I have quoted from your message?

      ?

      54 minutes ago, Allan said:

      Amazing guide!?:D

      @KGP-iMacPro?MaLd0n told me that you had some problems to edit your topic.

      ?

      It still happens? How I can help you?

      Hi @Allan,

      ?

      thanks for the flowers :-)?

      ?

      yes, cannot edit or find thread and originating post that I created to come up with an iMac Pro X99 macOS Mojave Guide in addition.?

      ?

      Tow days ago I?published a first?draft, which?should be subsequently filled up with content like?in case of X299.?

      ?

      Here the link:?

      ?

      I just reach to a blank screen, when clicking on the link above..?

      ?

      Can you fix?that for me, thus I can continue with my work?

      ?

      Or should I just start from scratch and open a new thread and originating post to come up with my?iMac Pro X99 macOS Mojave Guide in addition to the one?successfully published?above for X299?

      ?

      ?

      ?

      Edited by KGP-iMacPro
      • Like 1
      40 minutes ago, Allan said:

      Got it!

      ?

      Please check again.?;)

      ?

      Yup!! Cool! Working! Please leave it like this, ok? I will fill the post with content as I did in case of?X299. Just be patient...?:wink_anim:

      ?

      The iMac Pro X99 Mojave Guide?will be quite nice too...

      ?

      ?

      • Like 1
      On 6/7/2018 at 8:09 PM, Kynyo said:

      Thank you for such a great tutorial! Did you managed to get Graphics Acceleration over Pascal GPUs??

      I patched latest HS Webdriver, GPU is it recognized correctly but i don't have any graphics acceleration.

      ?

      Like you, I am running patched WEB Driver xxx.35.106 for 10.13.5: correct display resolution, some video acceleration, HDAU working. No?OpenGL or Metal 2 support though!

      ?

      And here are the quite sad news for now. After some chat with Ray from Nvidia (he supported the Web Driver implementation for special OSX build iMac Pro)?I am anything else than optimistic that a Web Driver would be released within the next days.?

      ?

      Hi KGP,
      
      I can leave your case open, and if there are any new information I can share 
      then I'll let you know.
      
      Best regards,
      
      Ray
      
      ------------
      
      Hi Ray, 
      
      well these are indeed not very promising news. I really hope that we will not have to wait until 
      September/October to see a working Web Driver like in 2017. This might be the end of Nvidia products 
      on many Hackintosh systems. 
      
      Thanks for all your efforts and the quick response anyway. 
      
      I hope my incident will remain open though. 
      
      Kind regards,
      
      KGP
      
      ------------
      
      Hi KGP,
      
      I am sorry but unfortunately I was not able to get any details with regards to NVIDIA Web driver 
      support for 10.14 Mojave. Development have no information to share at the moment so there is really 
      not much more I can add. I will certainly let you know if anything changes.
      
      Best regards,
      Ray
      
      ------------
      
      Hi Ray, 
      
      many thanks for your reply. Gorgeous that you check with your development 
      team to get my input. 
      
      I am already writing up the first X299 and X99 guides for 10.14 Mojave DP1
      
      Systems are up and perfectly performing, apart from Nvidia graphics. 
      
      All I am missing and the entire community desires is a working Nvidia Web 
      Driver for the 10.14 Mojave Betas. 
      
      I really hope that you will come back to me with gorgeous news for all off 
      us, which also shall be of large benefit for NVIDIA. 
      
      Kind regards, 
      
      KGP
      
      ---------------
      
      Hi KGP,
      
      I don't have any information with regards to NVIDIA Web driver support for 
      this OS. Let me check with our development team to get this input. Let me get 
      back to you on this. If there are information I can share then I will definitely 
      update right away.
      
      Best regards,
      
      Ray
      
      -----------
      
      [Retaking conversation few days ago.] 
      
      Dear Ray, 
      
      I just succeeded in installing macOS Mojave 10.14 DP1 (18A293u). I tried to patch 
      web driver xxx.35.106 for macOS High Sierra 10.13.5, but no way to get it work under 
      10.14 DP1. 
      
      Now everything depends on Nvidia. I would like to publish a new iMac Pro 10.14 Desktop 
      guide. 
      
      I really hope that Nvidia will provide us with a Web Driver for all upcoming macOS 
      Mojave 10.14 Betas. 
      
      I would really like to further promote your products along my Desktop Guides, which 
      reach hundreds of thousands of potential Nvidia Clients. 
      
      Looking forward to receive your positive reply as soon as possible, 
      
      KGP
      
      -------------------
      
      [Originating answer from 05/09/2018]
      
      Hi Klaus,
      
      Unfortunately I don't have much insight into release schedules for NVIDIA Web drivers, 
      but I will be happy to forward your feedback to the development manager for review and 
      consideration. I agreed with you that there are certainly room for improvement but I just 
      don't know how much of this is due to Apple's release policy. I know that for many of the 
      Apple's OS updates we don't get any advanced noticed for their release date, so the NVIDIA 
      Web driver will always lag behind. 
      
      I'm not in development so I really can't comment too much on the NVIDIA Web driver release 
      schedule. Again I will be happy to forward your input to the development manager. Thank you 
      for your valuable feedback.
      
      Best regards,
      Ray
      
      ---------------
      
      [Originating reuqest from 05/09/2018]
      
      Hi Ray,
      
      Writing you after long time :-)
      
      First at all, congratulations to NVIDIA's latest web drivers! 387.10.10.10.30.106 and 
      387.10.10.10.30.107 work absolutely brilliant with all NVIDA GPUs and finally also removed 
      some remaining lag in the macOS High Sierra UI. The user feedback was extremely and exclusively 
      positiv!   
      
      The reason for writing you however is another :-)
      
      You know 4th June 2018 is approaching (WWDC) - And we are all waiting for 10.14 beta 1.. 
      
      As soon the first beta will be released, I will come up with a new iMac Pro Hackintosh guide, 
      which hopefully will be as successful as the one for 10.13. 
      
      Knowing the NVIDIA policy and guidelines I however fear, that all Nvidia users again will be without 
      any Web Driver Support during the 10.14 betas for more than 3-4 months. Lot of arguing and complains 
      from the NVIDIA user side already during 10.13 betas last year. All Nvidia users have been very deceived 
      with Nvidia’s strategy not to provide any Web Driver for 10.13 betas before it’s finally release.. 
      Many changed to ATI GPUs.. 
      
      It would be absolutely gorgeous if we could do it better this time! 
      
      Any chance to come up with a 10.14 beta web driver with the release of 10.14 beta 1 in June 2018? 
      
      If the latter works, there would not be any real necessity for NVIDIA to keep the driver permanently 
      updated during the individual 10.14 betas. We are all now familiar with repacking a working web driver 
      to be compatible with future iterations of the same macOS.
      
      It is a dream of mine to avoid any gap in the web driver support. I cross all fingers that we will be 
      able to manage. 
      
      Eagerly waiting for your reply :-)
      
      Warm regards,
      
      KGP
      ________

      ??

      Edited by KGP-iMacPro
      • Like 1
      6 minutes ago, d5aqoep said:

      Spectacular guide!

      ?

      Is Nvidia hardware acceleration working for UI and transparency effects for 1080Ti ?

      ?

      Thanks, man!?Nvidia Hardware acceleration working for UI, although without transparent effects.. No OpenGL and no Metal2 support. Basic Video acceleration though. The performance of patched Web Driver 10.13.5 is a?little bit better than the one of patched web driver 10.12.6 used during?the 10.13 betas in 2017.?

      Edited by KGP-iMacPro

      @KGP-iMacPro?what?does disabling Above 4G Decoding in the ThunderBolt 3 instructions do? I've read in a few places that this setting causes instability in ASUS Prime?X299?Deluxe motherboards, but haven't seen any further detail than that.

      2 hours ago, Tony Arnold said:

      @KGP-iMacPro?what?does disabling Above 4G Decoding in the ThunderBolt 3 instructions do? I've read in a few places that this setting causes instability in ASUS Prime?X299?Deluxe motherboards, but haven't seen any further detail than that.

      ?

      Honestly I have not seen any advantage or disadvantage in enabling or disabling Above 4G decoding on X299. I usually disabled it therefore.?

      Edited by KGP-iMacPro

      Loloflat6_X299_iMacPro.thumb.png.3306c78e70d6907e80bada370364f263.pngI have managed intall MacOs Mojave beta dp1 on a HDD HFSJ+ patition : works perfectly :)

      ( i have installed before MacOs Mojave in another system with Mojave MBR HFS Firmware Check Patch 10.14.db1 , i did a dmg image from the partition an restorered this dmg image on my X299 system? :happymac: )

      Some restrictions :

      - Sleep / wake issue

      - Whatevergreen.kext is needed

      The great point TB3 with SSDT-X299-TB3-iMacPro-Gigabyte is fully working hot plug with USB_C for my screen.

      ?

      ?

      ?

      ;)

      Edited by Loloflat6
      • Like 1
      • 2 weeks later...
      Upcoming?iStatMenus v.6.20
      ?
      Note the release of a iStatMenus 6.20?Beta?for testing purposes:?files.bjango.com/istatmenus6/is…
      ?
      Many former bugs have been apparently removed.?
      ?
      If you still witness remaining issues, report back to @bjango on twitter.?
      ?
      Enjoy and have fun,
      ?
      kgp.png.75676e26a1d9badd5daf66f7f02ded65.png

      Hi KGP, It's just me Punk. Just wanted to reach out as I emailed you a few times within the week?and was looking forward to a reply. I'm sure you're busy, but when you have time, I look forward to your reply. Thank you.

      Hi KGP, I just tried to follow the steps to acquire the file you mentioned that I needed:

      ?

      4.)?To avoid Skylake-X thread TSC desynchronisation errors during boot and wake from S3 with unpatched X299 mainboards, likely induced by yet erroneous Skylake-X 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.?
      ?
      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??

      Unfortunately, It gave me this reply in Terminal:

      ?

      Last login: Sun Jul ?8 13:17:23 on console
      Mypc-iMac:~ mypc$
      -bash: mypc: command not found
      Mypc-iMac:~ mypc$ git clone https://github.com/interferenc/TSCAdjustReset
      Cloning into 'TSCAdjustReset?'...
      fatal: unable to access 'https://github.com/interferenc/TSCAdjustReset?/': The requested URL returned error: 400
      Mypc-iMac:~ mypc$ mv /TSCAdjustReset ~/Desktop
      mv: rename /TSCAdjustReset to /Users/mypc/Desktop/TSCAdjustReset: No such file or directory
      Mypc-iMac:~ mypc$?

      ?

      So obviously I'm doing something wrong that it won't post this file to my desktop.

      ?

      I did go here and downloaded the zip file:?https://github.com/interferenc/TSCAdjustReset

      ?

      Anything else that I need to do?

      21 minutes ago, PunkNugget said:

      Hi KGP, I just tried to follow the steps to acquire the file you mentioned that I needed:

      ?

      4.)?To avoid Skylake-X thread TSC desynchronisation errors during boot and wake from S3 with unpatched X299 mainboards, likely induced by yet erroneous Skylake-X 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.?
      ?
      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??

      Unfortunately, It gave me this reply in Terminal:

      ?

      Last login: Sun Jul ?8 13:17:23 on console
      Mypc-iMac:~ mypc$
      -bash: mypc: command not found
      Mypc-iMac:~ mypc$ git clone https://github.com/interferenc/TSCAdjustReset
      Cloning into 'TSCAdjustReset?'...
      fatal: unable to access 'https://github.com/interferenc/TSCAdjustReset?/': The requested URL returned error: 400
      Mypc-iMac:~ mypc$ mv /TSCAdjustReset ~/Desktop
      mv: rename /TSCAdjustReset to /Users/mypc/Desktop/TSCAdjustReset: No such file or directory
      Mypc-iMac:~ mypc$?

      ?

      So obviously I'm doing something wrong that it won't post this file to my desktop.

      ?

      I did go here and downloaded the zip file:?https://github.com/interferenc/TSCAdjustReset

      ?

      Anything else that I need to do?

      ?

      You need to adopt the file for your cpu. The rest I already explained by mail...?

      10 hours ago, KGP-iMacPro said:

      ?

      You need to adopt the file for your cpu. The rest I already explained by mail...?

      Thank you for letting me know this. When you say "adopt the file for your CPU." I have no idea what that means. I know I just emailed you my reply, but what I'm going to do (as I mentioned before), I'm going to wait until the full version of Mojave (10.4.X) comes out and when it does I will take two to three days of focused time and?follow your updated steps?and then go back and forth with my questions that I will have then. Thank you again for your dedication and help.

      ?

      On a side note, for anyone who reads this, we benefit off of men like KGP who contribute their time and effort (quite honestly to have the best Hackintosh setup out there currently).?I know to some it may not mean much, but if there is any type of contribution that we can give KGP (if you haven't yet), then if you can, please find a way to contribute towards his efforts. By the way KGP never asked me to do this, I'm just saying this as he has been a amazing help to me and the rest of us who have this particular setup. I like having a Mac Pro system that runs circles around the current Mac Pro for half the cost and it's faster! Thanks again KGP!!!:thumbsup_anim:

      • Like 1
      1 hour ago, PunkNugget said:

      Thank you for letting me know this. When you say "adopt the file for your CPU." I have no idea what that means. I know I just emailed you my reply, but what I'm going to do (as I mentioned before), I'm going to wait until the full version of Mojave (10.4.X) comes out and when it does I will take two to three days of focused time and?follow your updated steps?and then go back and forth with my questions that I will have then. Thank you again for your dedication and help.

      ?

      On a side note, for anyone who reads this, we benefit off of men like KGP who contribute their time and effort (quite honestly to have the best Hackintosh setup out there currently).?I know to some it may not mean much, but if there is any type of contribution that we can give KGP (if you haven't yet), then if you can, please find a way to contribute towards his efforts. By the way KGP never asked me to do this, I'm just saying this as he has been a amazing help to me and the rest of us who have this particular setup. I like having a Mac Pro system that runs circles around the current Mac Pro for half the cost and it's faster! Thanks again KGP!!!:thumbsup_anim:

      ?

      Many thanks for all your flowers, man! Appreciated! ..?B)

      ?

      To properly prepare yourself for September 2018, please read Section C.7)?of my guide, where you will find a detailed explanation how to adopt?TSCAdjustReset.kext to?your?CPU?in use.?:wink_anim:?

      Edited by KGP-iMacPro
      21 hours ago, KGP-iMacPro said:

      ?

      Many thanks for all your flowers, man! Appreciated! ..?B)

      ?

      To properly prepare yourself for September 2018, please read Section C.7)?of my guide, where you will find a detailed explanation how to adopt?TSCAdjustReset.kext to?your?CPU?in use.?:wink_anim:?

      You got it. I was wondering where is "C.7)?" I couldn't find here. All I could find was C.5) then it went straight to C.9). Maybe I'm looking at the wrong section.?:rofl:

      Guest
      This topic is now closed to further replies.
      ×
      ×
      • Create New...
      He decided to pay out another bit of rope. “All right! All right! He’s an innocent man.” “Then somebody is still close. How long ago?——” Back along the hangar wall they crept, until they came up to the small wooden cupboard with its dusty, frayed protecting burlap across the front. Under the cupboard boards the wires ran well concealed by more dusty lint which seemed to have been swept into the corners by the lazy act of some cleaner. She asked what he had thought of doing about it. Instead of taking means to conciliate the public, Bute, stung by these testimonies of dislike, and by the pamphlets and lampoons which issued like swarms of wasps, revenged himself by others, which only intensified the hatred against him. Still worse for him, he had caused the Dukes of Newcastle and Grafton, and the Marquis of Rockingham, to be dismissed from the Lord-Lieutenancies of their respective counties, because they voted against the peace on Bute's terms. With a still more petty rancour he had visited the sins of these noblemen on the persons in small clerkships and other posts who had been recommended by them, turning them all out. Sir Henry Fox joined him relentlessly in these pitiful revenges, and would have carried them farther had he not been checked by others. "Their camp's right over there on that ridge (pointing to the crest on which the Deacon had seen the smoke). They're probably on the lookout for us, and we'll have to be very careful if we get near enough to jump them. I thought I saw one of their lookouts about here when we came up. Yes, there he is in there." "Go to brimstone blazes," shouted the rebel. "If yo'uns have got me, why don't y' take me. I kin lick the hull caboodle o' y' sneakin' mulatters. Come on, why don't y'?" Then came an evening in April, when the air smelled of primroses and young leaves. The choir practice was early, and rifts of sunshine sloped up the clerk's kitchen, linking in one golden slant Robert's dark healthy face just under the ceiling, Bessie's shoulders pressed against his arm, the frail old hands of Joe Hearsfield on his flute, and the warm plum-brown of the bass viol close to the floor. To Robert it was all a dream of holiness and harmony. Old Spodgram confined himself almost entirely to two notes, Miss Hubble insisted on her four bars of arrears, young Ditch extemporised an alto of surprising reediness, and Robert bellowed the last lines of the last verse just as the other choristers were loudly taking in breath preparatory to line three—but the whole thing was to him a foretaste of Paradise and the angels singing ever world without end. "Stop your ranting and tell me how the hogs got you." He was not visible from where Caro sat, for he had come out of the water, and for a minute or two she vowed that she would have nothing to do with Rose's disgraceful spree. But after a time her curiosity got the better of her. Would Rose be able to do as she said—persuade her husband's drover to kiss her, simply by looking at him through half-closed eyes? Of course Handshut was very forward, Caro told herself, she had often disliked his attitude towards his mistress—he would not want much encouragement. All the same she wanted to see if Rose succeeded, and if she succeeded—how. She craned her neck, but could see nothing till she had crept a few yards through the reeds. Then she saw Rose and Handshut sitting just beyond the hedge, by the water's rim. "You've told me a dunnamany things, and you can tell me as many more as you justabout like"—touching the climax of self-sacrifice. A strange sensation thrilled through the heart of the excited monk—an impulse to shed blood! The weapon of the prostrate Byles was snatched from the earth—it waved fiercely round his head; nature and religion warred, for an instant, in his bosom, but the latter triumphed: the weapon was flung to a distance; and Father John, crossing himself, disappeared among the tombs. HoME国产足交电影 ENTER NUMBET 0017
      ranru4.com.cn
      lgcoin.com.cn
      www.geri2.net.cn
      yshh2.com.cn
      suyii.com.cn
      www.fenju5.net.cn
      buzuo0.net.cn
      taiyi3.com.cn
      194s.com.cn
      www.rendi9.com.cn
      苍井空人体图片新浪 大胆日本女优 淫荡爆乳女教师 神乐坂惠写真先锋 WWW.JPTUBES.COM WWW.KBYSW.NET WWW.0315365.COM WWW.BOWEIJX.COM WWW.HNJTQX.COM WWW.SWW002.COM WWW.SE3SE3.COM WWW.HHH050.COM WWW.AIXIAOO.COM WWW.7DNW.COM WWW.555YYXF.COM WWW.XMSWIM.COM WWW.2222XO.COM WWW.B5KP.COM WWW.YUFUHS.COM WWW.CUTYMAX.COM WWW.GZKXZL.COM WWW.SELDDH.COM WWW.28916.COM WWW.GAN863.COM WWW.KXGDY.COM WWW.80SQW.COM WWW.SHJXQM.COM WWW.445P.COM WWW.DCRNY.COM WWW.BBB619.COM WWW.CFHFY.COM WWW.GOMAJI.COM 色农夫五月色导航 久久福利自慰视频 舔老师的美脚 情欲艳谈百度云 自自慰微视频mp4 男男互日小说 骚女插菊花 色裸裸图片 黄色做爱图片小说网 女女狠狠的干 avl撸啊撸 欧美超碰先锋影院 校园乱伦武侠 成人网导航mp4 爱逼影院图片 撸一撸综合网 biaoch 时间停止器系列西瓜 做爱鸡巴疼怎么办啊 青青草在线aH 免费视频好屈日 抽插十几岁无知少女 WWWSAO5566 欧美派对俱乐部 Www11wa 韩日毛片一亚洲av f夜东方 av水莓在线视频 亚洲美女日韩 夜夜射狠狠干夜夜撸 成人妇穿超衣服 wwww062bcom 久看在线看片 2016欧美色图 www十八色图cn 漂亮的姐姐成人视频 偷拍自拍三部 国产母子水柔在线视频 图霸人体艺术模特 3366mp3com 直入骚穴 丝袜骚妇影音先锋 www1100Acom qula77 丁香邪恶 日本美少女18岁人体艺术 制服影音 nfnfnf11不准打灰机 www3344uycom 色就色就吧 日本无码人人色在线视频 我的女友是四十岁的人妻妈妈的闺蜜 另类合集小说在线阅读 qq小妹的逼qq小妹的逼 av农夫电影 我看一级黄色片不穿衣服 狂操不知火舞 亚洲自拍偷拍偷 都市淫乱校园春色自拍偷拍 色琪琪桃花 www567net最新网站 色欲影视淫下载 激情婷婷第五月婷婷强奸乱伦 小咪咪色站 另类变态人人色99999 daselang150 男全裸写真集 肥臀AV下载 444kkkk图片 色福利加油站 小穴插着还是很舒服16p UsUs30 WWWavtb789com 48看 激情综合网激情五月俺去也淫淫网狠狠撸色播五月色五月开心五月丁香五 40岁少妇露脸久久草热在线 家庭迷奸小说 夫妻在线AV www97yescomwww97yescom 丁丁综合五月 淫荡的富豪嫖客和水柔姐姐玩母子乱伦-2 767人体艺术 火影忍者黄色图片美国网址 偷拍自拍3页 高中女孩破处视频在线 japanavtv 一夜十炮清纯唯美 久久激情国 日本片子网址你懂得 zrii 黑人干捷克美女迅雷 潮吹movies 日韩母子乱伦magnet 女优派对 千人斩官网经典mnnnn58com 7zdy 欧美虐待女人视频的网站 国内五旬美老妇做爱 偷插妈妈的菊花下载 日本激情在线 淫妲妲影院 sm一级毛片 怡红院百度转码 和姐姐妹妹小姨妈妈乱伦 淫穴爱爱 大屁股的骚少妇图片 吉泽明步所有电影番号 64kkkk新网址 微信毛片群 黄色网站2016自拍视频 骚货的菊花失守 bt种子综合网 少妇美女快播 森下真依比基尼 韩国美女强奸美女qvod 撸一撸人与狗 炸撸撸 人体多人性交视频 gegepa美女艳照 清纯美女媛交p 电影a片毛片 漂亮少女的活塞运动 chaxueshipin 能看的男同性恋性交视频 WWW_155PP_COM 偸拍女性阴毛 九妹插逼爽导航 成人电影去也 女人被艹动态图 入江辉美在线电影 我操了丈母娘一家作者鸡不属敏 d9e4590e0000131d 女人光bi图 xxx小次郎 天上的诱惑 回家开门时被人强行拖进家中强奸中的女优 帅哥美女激情性爱 美女双穴被奸 十大名逼操起最舒服 乱搞性爱生活 肏徐莉 抗衰老产品 黔中水利枢纽工程 gtv超级杯 矜持王菲 成人高考难吗 淫荡嫩穴草榴 西西人体艺术张筱雨人体 苍井空的那部av好看 狂操空姐狠狠插 和嫂子日屄 骚女美穴电影 WWWDY781COM 成人小说集锦 小学英语在线视频 赵世熙 ctqvcd 榆君林偸 黑黑色成人免费视频 七大叔先锋资源 人妖在线观看网站大全 父与女偷摸乱伦 人体大胆色图片 爱福利微拍广场 WWWCCC212COM WWWG5S2COM 性色妹妹 露阴毛裸体美女 骚熟妇和少年日b照 qvod李宗瑞277 少妇熟女乱伦强奸 野战人人碰 亚州人体艺术模特乳房 熟女俱乐部av熟女熟女自拍 母子伦理xiaoshuo 射她淫b网激情 女同性丝袜紧紧的小穴小说 xingjiaoen 先锋资源p2p影院 911seselu 疯狂肏屄视频 18女人人体 亚洲亚州色图小说在线视频 有没有哥哥妹妹乱伦的小说 页色黄站 美肉商人内兄 ye321ckm 撕衣服的她湿吻视频 4488色百度 人妻操逼逼 大香蕉伊人久草萝莉AV 4p换妻露脸 wwwsdlubacom 肉丝一本道黑丝3p性爱 www33qqrr这个网站怎么进不了 邪恶淫色女人 久久精品视频在线看成人动漫 亚洲图片区偷拍自拍图片欧美图片小说校园春色 日本激情床 强奸制服伦理丝袜诱惑 天天干天天啪天天曰夜夜射 综合激情五综合激情 日本三级美腿妻子电影 丰满骚妇15p 带丝袜的av网址 肥美阴户性交故事 亚洲女性可以双插吗 四房播播百度影激情深爱快播 肉质人体艺术 玲木里美av免费看 绑架人妻迅雷下载 日妈妈撸妈妈狠狠撸 坂本のぞみ写真集ed2k 逼里插着大肉棒 男男激情小说肉文 夜夜春色 樱井莉亚什么病 好外黄网6 www传奇时间 东京热n.180mp3 一生一世酒色图片网 9496酒色网 手机看黄片软件 现在用什么播放器看黄片 淫荡小妹 夫妻交换网 刘色女影院 全是爱社区 电炉色色电影 高清在线电影 免费片任意看 porn99在线 哥要色 松本麻里奈中文字幕种子链接 香港偷拍av 好屌 西瓜影音 岛图A片 gav136 美祢藤コウ影院 最大胆的人本艺 超碰草b日日干 成人免费三十分钟视频 午夜天堂热的国产 青女青春草在线视频成人 情侣车震偷拍迅雷种子 日本一本道激情在线 日日久久福利影院破处 日本有名的sm毛片 日本私人影院在线视频 骚男和骚女骚B视频 九尾狐里m在线视频 加点动漫在线 台湾tpimage免费播放 色狱的物真人加点动漫在线 台湾JVID大尺度情欲视频-豪乳女神张语昕恶魔情趣国度 完美曲线 白色色网址 www:ZZz55Com 屌好操 狼人干成人综合在线 东京热影片 超碰爱剪辑在线 激情影院在线看素人视频 正在播放97国产 磁力番女优无码 在夫的遗影前侵犯 迅雷 福利77 淫妻艳姨 微色中文字幕 wwwuuu7777com 2O14天堂成人网 岛国超级射精量影片资源 监狱乱伦在线播放 RKI-392在线 www843h com abp582 ed2k 电影院帮女友口交 中文字幕狼人在线视频 国产レズ 女人乱欲视频播放 97草草成人在线视频 超级操逼的视频 色院影视 9962黄色网站 赌场人人操 微咪xxxav 东方久久热 黄色网址、 m27baocom高清动态图 色屌丝在线播放 真人阴口交视频华语影院 国产大陆任你爽色视频 午午西西影院 亚洲图片归美图片成人电影在线 91摄像头偷拍影院 欧美学生妹裸体性爱视频 三上悠亚骑兵资源 福利自拍网 捆绑玩阴蒂Bt baoyutv跳转 色播最懂男人的电影网站 九九热视频精品 免费做爱视频网站免费 www88baa 强奸片段磁力 www168ddddcom 女性使用自熨器视频 唐朝av6 色视频146 屌麻B视频 91国产制服 无限资源视频 tuigirl美女视频 色狐吧 偷拍秦先生 热の国产x 小视屏福利网站 性骚做爱吃奶视频 学生性交视频 ftp 午夜影院爽美女 …啊…大鸡巴哥哥…淫水好多…… 普通话啪啪视屏 自慰小视屏免费 哥也射综合 52avav路com www 哥也色2018 中文 做爱大肉棒视频 震动器啪啪 一级黄色毛片进阴不收费带声音的香蕉视频A片 超骚 深圳同居换夫 网友人人操天天碰 久草热线综合网 1永久免费费观看av片 狂操空姐嫩穴洞 国产自拍啪啪在线 国内KTV里妹子表演神技用小穴抽烟吹 苍井空a影片 国模掰阴露鲍艺术摄影 艹逼福利视频在线观看 影音成人五月丁香 日本黄色视频里 国产有剧情的H片magnet 快播电影原老七网 成人电影群 欧美h剧影院 第一色av资源 黄网资源共享 哥也搞大香蕉娱乐官网 操逼的小视频黄点。 被各种玩弄BB很粉嫩拿按摩棒玩出高潮 499M saob8 sm乐园影院 播播撸 步兵番号dky 超蹦97在线观看 69saocom 中国杂技系高清 nnn760五月天 2014a天堂网 强奸乱伦三级中文字小视频 直播高清福利 amsr福利视频 要要橹福利 男人福利超黄网站 快播成人妻视频 wavr黄色 那有小姐操逼视频 操操操自慰淫叫视频 国产小视频免费观看在线 藏精阁宅男福利站 韩国体内射精视频 1314ypcom 自拍偷拍在线更新 古装A片迅雷在线观看 福利社午夜直播频道 亚洲东方无码 haiwe 男人的午夜福利 美女在线福利伦理 vod60 乱伦小说大全福利社视频 色偷偷97视频在线 美女被插小穴揉小穴的视频 少妇少女学生妹国产在线播放 色和尚在线视频成人 乱伦在线视频 全程露脸国产熟妇在线 七草千岁新新电影 肌肉男 尿道 调教 欧美av第一页 古装爱爱伦理 迷奸链接迅雷下载 连体袜系列番号 岛国x视频99精品 久久大香蕉一本东京热 一干到底txt百度云 艳情战场视频 免费观看爆乳家政妇 护士美女穿白丝袜被插鸡 欧洲无码高清视影院 周研希 138v 91影视成年人青青chao 26uuu小说 magnet 3344av 大香蕉九九色综合网 抠阴唇喷水视频 欲巧淫 韩国主播梦 波 福利 韩国美女直播软件 国产在线不信你不射 小黄片人人干哈 韩国美女性感裸照7100。 caoporeg 我的可爱的小女孩手淫p2 露脸操白妹国语 小泽玛丽亚久久热 888kbkb 早乙女由依(萝莉) 美女老师后入gif 韩国禁播女团组合先锋影音 AVAV女教师 美容室:特殊!服务 magnet 秘密爱洗澡啪啪啪 禁止的爱小第九影院 外国黄色成影free 成人综合咪咪 大奶子性爱影片 我和老师做爱漫画 五月天婷婷表姐 找熟妇禄体图片 少妇全裸的乳房bb照片 操美女妹妹小说 图区五月天 匹夫鲁8090 在线骚女电影 男女激情文章 微信极品白嫩女孩看a片被操出白浆后被口爆国语对白mp4136mb 自拍偷拍厕所偷拍头 天天饮食 百度云 � 三极伦理电影 三级视频淫b内射 暗暗撸 美丽的新娘 熟母紧缚 321操逼网 树林野战视频骚逼在线 亚热美女图片 人体美图人体艺术 人i与动物快播 66人体艺术鲍 超级护士美女做爱 妈妈说苍井空 成人快播激情网 俄罗斯熟女视频 快播semm色五情月8888车保养常识结果xt全集下载 要看露屄的女人 女同事 露毛 神勇大汉操逼图 日本空姐被操视频 人妻乱伦区 美女高难度体操性爱 苍井空露妣图片欣赏 佐佐木柚奈 豆瓣 妹子口交性电影 黑人骚妇屄毛 sese78成人美女人体艺术 欧美性感骚屄浪女 欧美美女 性交 西西人体艺术裸图露阴 狂插大吊骚穴 淫娃终结者bt 真实乱伦小说 WWW_BEEG_COMVIDEO 城市部落 如何制作vcr 长虹电视机电路图 激情明星狠狠操乱伦 那里有插逼网站 qvod黄色成人电影 55rfb7yyyy 唐嫣人体艺术图片 干邻居阿姨小说 � 非洲幼女做爱 波多野结衣美熟女30p 色网站怎么都上不去了 先锋影音小也麻莉亚 sss快播a片 同行恋帅女生接吻视频 抽插孕妇大屄 陈冠希艳照门哪里能下载 云欲轨道舒淇 一淫片少女被裸体内射 求波多野结衣图片 自拍偷拍亚洲欧美漫画套图 第一页熟女 心儿人体艺术 8090碰综合网今日 骚妈妈美狐网 先锋李宗瑞资源 女生为什么喜欢被艹 迅雷百度云怎么看黄片 WWWJJ654COM 肉弹叶月奈穗 妹哥张珈祯逼120p 死神纹身血色天使图片 国产骚妇自慰抠逼在线视频 在哪可以看到仓井空的电影作品 花穴乱伦 女人屄百图 女主播边播新闻边做爱 女人掰鄙图 av免费在线手机视频 日韩av干炮图片 干富婆 日本大胆熟女人体艺术 大胆美人体 幼幼破处系列夫妻野战好骚妹 影音先锋成人干网 有真性交拍戏的吗 酷乐人体艺术摄影 成人的爱爱故事 亚洲性爱区删除删除删除删除删除删除 色哥祝屈 三级黄色m2dycc909kkcom 哥哥色在线看wwwhyhy888com 欧美色图亚洲少妇 成人电影偷拍自拍亚欧图片 奇米先锋影音撸 青青草手在线视频网 偷拍港台妹视频播放 公交车上搞美女屄 1024av狼 十八禁短篇故事 插同学妈妈 女人小穴自搞 淫荡操逼大姨子 大人和小孩做系列在线 香港三级成人电影院 网友自拍原创精品社区 色偷偷成人资源站 秘书不详 色人居色奇米影音先锋 大帝av日韩 最新偷拍自拍人妻少妇视频 男女大乱交网 撸一夜视频qqsina 空姐丝袜大乱11p 厕所偷拍浴室偷拍校园偷拍 欧美裸交 情妇中那个电话性爱是在那一集 www南风莞com 少妇熟女搞逼 车里淫荡的小姨 制服诱丝袜伦理片 色乳爆帝国 逼激情 巨乳学妹做爱 家族乱伦做爱小说 久草肛交做爱视频 我和姐姐在车上乱伦激情 黑色内裤15p 插入妈妈阴户 日本熟女性感图 色西西美女人体 先缝影音三级 AV制服丝袜 13yn_com 冲田杏梨中文字幕先风影音播放 天天瑟瑟天天撸 奇米噜噜噜在线视频 五月天丁香成人啪啪结合 淫荡女老师小说 第一福利网站最干净的 动漫女生的恶搞图片 亚洲一成人网站 强奸三个嫂嫂小说 五月丁香色婷婷色久草 恋足视界 哥哥去wwwfy088com 阿v天堂网一本道 狂操黑丝骚妇 万全影院伦理片第一页 撸在线视频亲朋乱伦高速高清视频 ccc36蜜桃 亚洲b色图 人妻都市撸撸 超碰sm免费公开视频 色妹妹插插进去 干姐妹色图 色就是色SU swwwmumu57comhtmsphtm 年轻护土的西西人体艺木 日本啪啪小电影在线 多毛美逼特写图片 kk2929 免费在线伦理电影 wwwsexlnsexcom 日本女星先峰 我与老师在公交车上 脱脱影院 可以免费在线看的黄色网址 萝莉射精xxx 淫色直播的有哪些 九九xxxx开心 韩国三级车震视频 啊啊啊摸奶 WWW3RATCOM www68abcdcon www1122dkcn 插妈妈a片 强奸骚货女朋友 美女直播性器官 色秀人生 青青草毛在线 少女开包迅雷下载 东方av在线看 啊啊舅妈不了了 亚州xx好看网站 桃瘾论坛 捡到高中美眉下载 228zzmagnet 杜泽文近况 成人速播视频 露毛写真日本 羔羊医生土豆观看mkudian365com www4hu49cm 偷拍自拍下载 能看的三级骚逼 免费线上av在线播放 日本激情成人网 狼影视下载 变态自拍亚洲 成人激情视频免费观看自拍 公开视频色偷偷 丝袜ol办公室[完] 欧美成人在线性交视频 美女久纱野水萌MP4 wwwganjpcom 日本午夜户外直播 兽呦奸国产视频 国产普通话叫床 swwwmmmvodcommove7index6html av天堂音影先锋快播电影bbaa1 欧美AV丝袜 成人古装黄色电影迅雷种子下载 413121神马电影 人要乱伦W 首页张柏芝插 ∞黄色电影1日本 领导的老婆淫荡 户外熟女 自拍偷拍网友自拍91 未成年小孩做爱视频 大胸美女拍的电影 姊妹50p 骚妇被内射 wanseqingshufu 韩国美女性交艺术图片 伦理东京热 影音先锋人肏肏狗 淫荡猫女 人体艺术阴部裸体 黑人操女优逼片 电影我爱欲女三邦车视 插逼穴图 床戏时间最长视频 哥哥射俺去撸亚洲性爱 色久 姬岛琉璃种子 66abcd怎么不能看了 北京音乐学院女大学生街头性交 好看的白虎片 五一看白虎馒头屄 成人潮吹影院 qvod 无码自慰潮吹 粉红嫩穴10p www110bbcow 偷排自拍先锋影音 放弃射门 品色堂君子好色而不淫 真空干燥箱使用方法 重口味推荐 尼桑玛驰 彩虹岛无限回廊 姐姐的骚逼图片 爸爸鸡巴插我屄里教我做 欧美最大胆人体艺术照片 老色妹在线播放 美国黄丰满强奸 得得日在线视频 美女被摸小穴图片 操逼就操欧美老婆大骚逼视频在线 亚洲日本色露逼 肏大肥逼 中国小说和韩国小说 美鲍鱼人体 欧美色图大臀 学生逼逼电影 中国幼女性交中国幼女性交 安藤沙耶香写真先锋影音 全裸无遮挡物的美女屁眼 上海女人骚吗 性交漏逼 惊变激情戏在多少分钟 台中综合站湾xxoo 早乙女seba makelovevideosex 白洁亚洲图片 朝阳区女13岁操 西西偷拍 舒畅丝袜照片 高尺度艺术 WWWHHHCOMZIPAI 哥哥影视撸啊撸 在复仇者联盟里草女的黄色小说 gogo人体高清人体孙俪 成人玩具燃油遥控飞机 avidolz护士 黑丝淫 男人插进去无遮挡小电影 茹原雄太郎漫画种子 水柔姐冯丽和女儿桔子碰视频 最美少女身材图片 大鸡巴操骚遥 姐夫舔我B视频 大香蕉成人文学 sqvheqi345cn 火影忍者AVmagnet 人妻熟女肥佬影音 wwwyoujizzzvom ?1?7?1?7?1?7哥视频网wwwa?1?7c24com 日本AV巨乳视版在线 幼少女招嫖 av宫井 小说区黄色小说 wwwAVAVzaixiankan 哥也色人格得得爱色奶奶撸一撸 热亚洲无码热自拍偷拍 人妻10P迅雷高速 大屁股影视free 阿片资源库 幼交片网址 哥要射哥要蝴蝶谷wwwlgdydcom 佐佐木希不雅视频吉吉影音 欧美暴力性爱AV 年少人妻按摩 成年轻v 搞笑有声小说 畅想听吧有声小说 在线的h网 东京热wumaonvmishu 东京热n334 怎么看黄片啊 皇家影院 新品色堂 n4x在线 风月阁论坛 母息子影院 7-Se成人网 救囯集中淫G谁有E 干妹妹 干细胞 桃花小妹 色猫电影乱码 先锋av天网堂2017 不卡AV电影天堂 俺去也网色 fdd 1231av女主演 一本道久在道dvd在线观看 苍老师a片 午夜男日B视频 激情内射网站 色e62视频 WWW,998aVaV,C0m 秋霞在线观看秋霞伦理电影 在线福利视频一家三口 御姐啪啪啪视频在线观看 日本少妇内射在线视频 日本一本加比勒 日本一级无码性片 澳门微拍视频 窝窝爽在av 草壁 92看电影 看雪电影网 欧美色马无情 国产自拍抖音在线视频 爱色综合图片社区 天党网AV japanese girl voise 女地下党受刑奶头 草榴三级 日本人妻最新AV伦理片 韩国三级2017在线观看秘密爱 日韩教师视频在线观看 华裔美女主播电击 下载 > 韩国最新老婆不在家与风骚大姨子偷情流出视频 5038zoo 奥门操逼赌厂 www52rurucom 宅男视频福利无码在线啪 江疏影大保键视频av 白合野 国产 迅雷 www4hu33 人妻G点在线 avavav噜噜 国产 第五页 福利影院 百度云黄片 jj无码激情视频播放 萝莉小逼 www。22bbb 偷拍丝脚打胶贴图 希志爱野 在线 www999re8 caoporn原纱央莉 三上悠亚家庭教师 可以使用的黄色网站 成人教育AV偷拍 2046秋霞 无能皇帝bt 水岛津实蓝衣地铁快播 美女Av高手 嵊州钱佳璐盗窃罪 韩国大尺度床戏 ftp 过膝靴 偷拍 白石茉莉奈飙奶 xfz33网站 Xxx偷窥偷拍在线视频 冲田杏线观看视频 大奶少妇喂 955mmmcom 超碰在线小视频 狼人干练合旧地址亚洲 wwwAV手机 韩国av在线免费观看 潮喷导航 北岛玲有码在线无码 秋山祥子丝袜 mp4 高清免费做爱视频 插 水 叫 视频 欧美孕妇干b视频 虎影院 免费在先看片 牛碰国产 波多野结叫床声视频 Kdd789。 在线av丝袜福利视频 网友自拍 秒拍偷偷色 久久爱免费视顿在线观看免费30 被偷窥的女主播2樱木凛 x'x'x'x'x'x'x'x性交 东方人av 网红自拍露脸在线观看 无毛眼镜嫩妹酒店约炮 国产线路3视频 谭晓彤 福利 视频 在线 snis 951中文字幕 44p44影院福利视频 www1769zy1com 理论片天堂sm 人人摸人人辱 国泰电影院logo 男女干b视频 美国成人天堂 社长秘书紧缚奴隶B 先锋影音亚洲人妻制服乱伦资源 性感巨乳裸体美女视频 性感爱视频在线观看 香蕉视屏 magnet 先锋骑兵香西哾影音先锋 女人的嫩逼 中文字幕无码北条 近距离做爱视频 免费毛片tube 午夜视频1000在线播放色 日本毛片免费视频福利社影院 7M视频l 97伦理理电影不用下载播 日本xxxx黄色视频 亚洲va天堂无码在绒 韩国和年轻继母乱伦免费视频中文 国产性交自尉真人视频 性交自拍 ftp 金蒲团直播艳艳 一本道在线成人 成人免费人人操 婷婷色TV 247semagnet 蜜桃vip能看AV嘛 rct412中文字幕视频 RCT tukuyingyuan 第一黄片视频 夫妻成人无码视频 流浪的妓女完整版视频 成人h漫在线观看 邪恶姐弟动漫小视频 大黑吊啪啪啪视频 操逼操网站 xxoo视频破处 被窝福利一新视觉影视 韩国直播三级片 日本家庭乱伦无码 日本伦理片在线观看更多 3d蒂法三部曲无修 在线视频无码亚洲日韩 女第一滴血H版在线观看 国语在线自拍 3838pao,com 69欲, 啪啪啪tossgirl 久久热在线国产偷拍 国产老鸡磁力连接下载 舔女教师美脚影音先锋 印度三部曲百度网盘 洛阳小少妇在线视频 美女曹逼视频 金荷娜17部svip视频磁力 极品网红大胸美女请房东修理空调 五月丁香欧洲 黄色神马影院 ponrhub手机在线播放 茜公主殿下福利视频 91混血哥双飞高颜值的上海177制服姐妹花普通话对白720P完整版 黄色福利操逼网站 啪啪免费视频酥酥影院 午夜约吧 四虎影库体验区免费视 777sesese 插少妇綾合网 午夜国内自拍 诱惑主播在线播放 日本男女床上做爱狂插射精淫叫视频 迅雷看高清av 凤月影院 英国毛片高清免费视频 天天曰天天看操逼 操逼视频操逼视频老司机影库操逼视频操逼视操操 点击观看福利视频 日韩无码偷拍自拍在线 色吧 春暖花开春暖花开 tear 福利视频 爱看番伦理 哥哥去免费视频 丝袜表演 磁力链接 eee119改成什么网址了 免费在线观看av情人视频 狼色 日本视频短片 茄子女自卫国产视频 半老徐娘迅雷下载 男人鸡扒插女人BR视频 800东方 色女人影院一一 播放器大全 成年人 日本大奶多毛视频在线 妹妹影院ab 美女裸体图片要看到b的网址 丁香五月五月婷婷深爱五月插屁成人 xxx虐待阴茎视频 大奶另类大奶 嫩屄美女脱衣 91pom视频网站 www003secom 韩国女明星香艳视频 骚妹子人体图片 WWW_835AV_COM 呀呀干露脸老婆图 跟邻居操逼自拍性爱 影音先锋看不了岛国片 内射清纯美眉 性爱图片20p小姐