Jump to content

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



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

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

Categories

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

Categories

  • OSx86
  • Apple News

Found 88 results

  1. Successfully running my iMac Pro Skylake-X/X299 Build with macOS High Sierra 10.13.4 (17E199)! Extended major revision of the guide completed. Thanks for your patience! Abstract and Introduction: This originating post constitutes a new macOS 10.13 High Sierra Desktop Guide for Skylake-X/X299, which certainly can still grow and improve by your estimated user feedback. This Skylake-X/X299 10.13 High Sierra Desktop Guide bases on the ASUS Prime X299 Deluxe. However, also other X299 ASUS mainboard models or X299 mainboards of other brands should be compatible with this guide by considering a few mandatory modifications detailed below. The i7-7800X (6-core) was chosen as the Skylake-X Startup Configuration Model in order to minimise the guide development costs. It has been replaced within the goal configuration by the i9-7980XE (18 core). All other Skylake-X models compatible with this guide are detailed in the figure below. Carefully consider, which Skylake-X model might be the correct choice for your specific needs. Also the note of the following limitations: a.) The i7-7640X and 7740X only support two channels DDR4-2666 and only posses 16 PCI express 3.0 lanes, which are already used up by implementing a state-of-the-art 16 lane PCIe graphics adapter. Thus, there are no further PCI express 3.0 lanes for using PCIe NVMe drives or additional PCIe adapters! b.) The i7-7800X and i7-7820X already support four channels DDR4-2666 but however also possess only 28 PCI express 3.0 lanes! Thus by using a state-of-the-art 16 lane PCIe graphics adapter and a PCIe NVMe drive, there are nearly no PCI express 3.0 lanes remaining. When adding one or two additional PCIe adapters, one exceeds the 28 available PCI express 3.0 lanes by far! In this case, the resulting configuration might be error-prone! c.) Thus, considering a.) and b.), I strongly recommend to start at least with the i9-7900X, which already supportsfour channels DDR4-2666 and also implements 44 PCI express 3.0 lanes Further note, that for all Skylake-X processors, a sophisticated liquid cooling system is absolutely mandatory! For stock speeds something like the Corsair H115i might by sufficient. However, if somebody aims at OverClocking (OC) of the i9-7900X or Skylake-X Processors above, sophisticated Water Blocks for CPU and VRM of e.g. EKWB seem absolutely mandatory and unavoidable. My Skylake-X/X299 System is up, fully stable and fully functional apart from the yet non-functional onboard WLAN (WIFI) module (chipset not natively supported by OS X). For Wifi, I therefore use the OSX WIFI PCIe Adapter instead. Thanks to a very recent iMac Pro dump performed by @TheOfficialGypsy, we now have been able to successfully implement the necessary iMacPro1,1 details in both Clover_v2.4k_r4369 (thanks to @Sherlocks) and Clover Configurator v4.60.0.0 (SMBIOS details, thanks to Mackie100) by beginning of January 2018. In collaboration with @macandrea, we first achieved the direct implementation of macOSHigh Sierra 10.13.2 (17C2120), and now also the direct implementation of macOSHigh Sierra 10.13.4 (17E199), which can be subsequently updated to macOSHigh Sierra 10.13.5 Beta via the Appstore once the latter will be available. Note that with AptioMemoryFix.efi, the new Skylake/X299 iMac Pro build now also features fully native NVRAM support. No need for EmuVariableUefi-64.efi in /EFI/Clover/drivers64UEFI/ to properly transmit the SMBIOS iMacPro1,1 credentials to Apple. We also reached Native Display Brightness Control / Native NightShift Functionality for Monitors like the LG 38 inch display with DCC/IC Support thanks to users @Bendge and @Ramalama. Since 10.13 SU and with AppleIntelPCHPMC, Apple now natively implements IOPCIPrimaryMatchID "a2af8068" and AppleUSBXHCISPT on the ASUS Prime X299 Deluxe. Thus, 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) ports work natively at expected data transfer rates (90 Mb/S (USB 3.0)and 40 MB/s (USB 2.0), respectively) for all X299 mainboards. All external and internal USB 3.1 (USB 3.1 Gen 2 Type-A and Type-C) ports were natively implemented already before on different controllers than XHC and also work at data rates up to 140 MB/s. Up to my best knowledge, the native XHC USB implementation states for all X299 mainboards. Also the ASUS Thunderbolt EX3 Extension Card is fully implemented including TB XHC USB and TB hot plug functionality. External Thunderbolt drives connected via Apples Thunderbolt 3 to Thunderbolt 2 Adapter work at expected data rates and speeds. The same states for all USB 3.1 Gen 2 Type-A and Type-C devices (see Section E.5 of my guide)! Note that opposite to my previous EFI-Folder distributions, EFI-X299-10.13.4-Release-iMacPro1,1-310318.zip does not contain any default audio configuration. You have to implement the audio approach of your choice during the Post Installation process in Section E.)! You can select between three possible audio implementations detailed in section E.3): 1.) The AppleALC audio approach (section E.3.1) bases on AppleALC.kext v1.2.4 and Lilu.kext v1.2.2 and could be implemented thanks to the extensive efforts and brilliant work of @vit9696 and @apfelnico. 2.) The VoodooHDA audio approach (section E.3.2) bases on the VoodooHDA.kext v2.9.0d10 and VoodooHDA.prefPane v1.2. 3.) Finally, @toleda's cloverALC audio approach (section E.3.3) bases on the realtekALC.kext v2.8 and on an additional pathing of the native vanilla AppleHDA.kext in the /S/L/E/ directory of the System Disk and has been successfully implemented thanks to the instructions and help of @Ramalama. The correct HDMI/DP digital Audio PCI implementation will be detailed in Section E.9) of this guide in line with the HDEF and GPU PCI device implementation. The ASUS Prime X299 Deluxe on-board Bluetooth is natively supported and also Bluetooth Audio works OoB, however due to the non-functionality of the ASUS Prime X299 Deluxe on-board Wifi Module, I also use the Bluetooth 4.0 module of the OSX WIFI PCIe Adapter, which in line with its natively supported Wifi-module also provides native Airdrop, native Handoff and native Continuity as well as keyboard support in BIOS/UEFI and Clover Boot Loader. A full-featured alternative and more budget friendly BT/WIFI solution is the ABWB 802,11 AC WI-FI + Bluetooth 4.0 PCI-Express (PCI-E) BCM94360CD Combo PCIe Adapter of Flughafen Computer especially for our friends in Europe (thanks to @DSM2 for providing this information). 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 is now correctly implemented and fully functional, in addition to the anyway natively implemented and of course also fully operational Intel I219-V Gigabyte on-board LAN controller of the Asus Prime X299 Deluxe (see Section E.8 of my guide). Excellent news concerning CPU Power Management: ASUS, MSI and ASROCK mainboards allow now for manually unlocked the MSR 0xE2 BIOS Register and make any BIOS Firware patching obsolete. The MSR 0xE2 BIOS Register of all Gigabyte mainboards is anyway unlocked by factory default. By this we achieve fully native HWP (Intel SpeedShift Technology) CPU Power Management for all Skylake-X processors on all mainboards with unlocked MSR 0xE2 BIOS Register, resulting in absolutely brilliant and top-end CPU performance (see Section E.1). 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. Outstanding historical Skylake-X/X299 iMac pro Benchmark Scores finally also depict the excellent overall build and and system performance: Geekbench i9-7980XE (4.8GHz) CPU Benchmark: Multi-Core Sore: 65.348 Single-Core Sore: 5.910 Cinebench i9-7980XE (4.8GHz) CPU Benchmark: 4.618 CB Geekbench Gigabyte Nvidia GeForce GTX 1080 Ti WaterForce WB 11GB Xtreme Edition OpenGL and Metal2 Benchmark: OpenGL Sore: 229.965 Metal 2 Sore: 242.393 See Sections F.1) and F.2) for further details. All Skylake-X Systems harbouring a mainboard with unlocked MSR 0xE2 BIOS Register now also posses fully native forced and automated Sleep/Wake Functionality not only thanks too a fully developed SSDT implementation and respective ACPI replacements. Good new also for all users of C422 and XEON-W System. This guide seems also fully compatible with your systems Before starting with all detailed instructions, please find a Table of Content that provides an overview of the individual topics addressed within this guide: -------------------------------------------------------------------------------- Table of Contents A.) Hardware Overview Details about the build configuration that states the baseline of this guide. B.) Mainboard BIOS B1.) ASUS BIOS Firmware Patching (obsolete) 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.13 High Sierra System Setup This chapter includes a general guideline how to perform the initial setup of your iMac Pro with macOS High Sierra 10.13.4 (17E199). Note that the macOS High Sierra 10.13.4 (17E199) full package installer apparently can be only successfully downloaded on non-iMacPro systems. For iMacPro systems, there we provide a sophisticated workaround that bases on pristine sources from Apple. D.1) iMac Pro EFI-Folder Preparation D.2) iMac Pro macOS High Sierra 10.13.4 (17E199) Installer Package Creation D.3) iMac Pro macOS High Sierra 10.13.4 (17E199) USB Flash Drive Installer Creation D.4) iMac Pro macOS High Sierra 10.13.4 (17E199) 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 High Sierra Build 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) ASUS Prime X299 Deluxe Thunderbolt EX3 PCIe Add-On Implementation E.6) NVMe compatibility E.7.) SSD TRIM Support Extend the life of your SSD and maintained its normal speed E.8) ASUS Prime X299 Deluxe on-board Ethernet-Functionality E.9) ASUS Prime X299 Deluxe PCI Device Implementation E.9.1) ACPI DSDT Replacement Implementation E.9.2) SSDT-X299-iMacPro.aml PCI Implementation E.9.2.1) - HDEF - onboard PCI Audio Controller PCI Implementation E.9.2.2) - GFX0, HDAU - Nvidia Graphics Card 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) - ANS2 - Apple NVMe Controller PCI Implementation E.9.2.8) - SAT1 - Intel AHCI SATA Controller PCI Implementation E.9.2.9) - ETH0/ETH1 - onboard LAN Controller PCI Implementation E.9.2.10) - ARPT - OSX WIFI Broadcom BCM94360CD 802.11 a/b/g/n/ac + Bluetooth 4.0 AirPort Controller PCI Implementation E.9.2.11) - ThunderboltEX 3 Controller PCI Implementation E.9.2.12) - DTGP Method E.10) System Overview CPU Cosmetics E.11) ASUS Boot Splash Screen Cosmetics E.12) Native Display Brightness Control / Native NightShift Functionality for Monitors with DCC/IC Support E.13) Logic-X and Audio Studio Software Functionality E.14) 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 -------------------------------------------------------------------------------- Now enjoy and have have fun with the detailed guidelines below. Many thanks to [USER=956262]@paulotex[/USER] for committing the efforts in providing the Table of Contents detailed above. A.) Hardware Overview Mainboard: Asus Prime X299 Deluxe [380€] CPU: i9-7980XE (18 core, 4.4Ghz) [1.900€] RAM Memory: Tridentz DDR-4 3200 Mhz 128GB (8x16GB) Kit (F4-3200C14Q2-128GTZSW) [1.400€] GPU: Gigabyte Aorus GTX 1080 Ti Waterforce WB Extreme Edition 11GB [900€] System Disks: EVO 960 NVMe M.2 1TB (system disk macOS High Sierra 10.13.3) [450€] ; EVO 960 NVMe M.2 1TB (system disk macOS Sierra 10.12.6 Sierra) [450€] Power Supply: Corsair AX1500i [450€] Monitor: LG 38UC99-W 38" curved 21:9 Ultra Wide QHD+ IPS Display (3840 pix x 1600 pix) [1.350€] WebCam: Logitech C930e [80€] Mouse: Apple Magic Mouse 2 [75€] Keyboard: Apple Magic Keyboard Wireless [99€] Bluetooth + Wifi: PC/HACKINTOSH - APPLE BROADCOM BCM94360CD - 802.11 A/B/G/N/AC + BLUETOOTH 4.0 [129€] Internal USB2.0 HUB: NZXT AC-IUSBH-M1T [20€] Case: Thermaltake Core X71 Tempered Glass Edition Full Tower Chassis [140€] CPU/GPU Cooling: Water Cooling main components: - 1x EK-FB ASUS Prime X299 RGB Monoblock - Nickel [117€] - 1x EK-CoolStream PE 360 (Triple, 39 mm, Roof) [80€] - 1x EK-CoolStream Ce 280 (Dual, 45mm, Front) [90€] - 2x EK-CoolStream XE 360 (Triple, 60 mm, Cellar) [220€] - 1x XSPC Twin D5 Dual Bay Reservoir/Pump Combo [209€] - 15x Thermaltake Riing 12 High Static Pressure LED Radiator Fan (120mm) [210€] - 5x Thermaltake Riing 14 High Static Pressure LED Radiator Fan (140mm) [100€] - 3x Phantek PMW Fan Hub (up to 12 fans or 30W power consumption) [17€] - 1x Alphacool Eisflügel Flow Indicator Black G1/4 IG [16€] - 1x Phobya Temperatur Sensor G1/4 + C/F Display [22€] ----------- Total: 8904€ ----------- Compared with: B.) Mainboard BIOS Please find below a summary of my actual Asus X299 Prime Deluxe BIOS settings (Section B.2), in line with some actual Gigabyte Designare EX settings (Section B.3). All detailed instructions for ASUS X299 mainboard BIOS Firmware patching formerly outlined in Section B1.) are already obsolete. B1.) ASUS BIOS Firmware Patching On a real Mac with native OSX XCPM power management, the MSR 0xE2 register is unlocked and therefore writeable. However, on ASUS mobos this register 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, @PikeAlpha and @Adrian_dsl), we were able to successfully patch any ASUS X299 mainboard BIOS distribution and unlock the MSR 0xE2 register. 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. Within the 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, which makes any additional firmware patching totally obsolete. MSI and ASRock mainboards already previously allowed for manually unlocking the MSR 0xE2 BIOS Register. The MSR 0xE2 BIOS Register of all Gigabyte mainboards is anyway unlocked by factory default. By this we achieve fully native HWP (Intel SpeedShift Technology) CPU Power Management for all Skylake-X processors on all mainboards with unlocked MSR 0xE2 BIOS Register, resulting in absolutely brilliant and top-end CPU performance (see Section E.1). 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 7.) in Section C.) of this guide). The most recent ASUS mainboard BIOS firmware can be uploaded to the specific ASUS X299 mainboard in many different ways. The ASUS EZ BIOS Flashback Procedure is one of several options. The individual steps for the latter procedure are detailed below: 1.) Add TSCAdjustRest.kext to your /EFI/Clover/kexts/Other directory (see further instructions in Error prevention 7.) of Section C.) below). 2.) Download the most recent BIOS Firmware file from ASUS. For the ASUS Prime X299 Deluxe follow THIS LINK 3.) Copy the most recent ASUS BIOS Firmware file to your Desktop, e.g. cp ~/Downloads/PRIME-X299-DELUXE-ASUS-1301.CAP ~/Desktop/ Change to your desktop cd ~/Desktop/UEFIPatch/ 4.) Now rename the patched BIOS Firmware distribution file in concordance with the ASUS EZ Flashback filename convention for your particular ASUS X299 mainboard. For the ASUS Prime X299 Deluxe, the modified BIOS Firmware distribution file must be named "X299D.CAP": mv ~/Desktop/PRIME-X299-DELUXE-ASUS-1301.CAP.patched ~/Desktop/X299D.CAP Now copy the CAP-file with the correct ASUS EZ Flashback filename convention to a USB Drive with a FAT32 File System of your choice. cp ~/Desktop/X299D.CAP /Volumes/"YOUR_USB_DRIVE"/ and shut down your system. 5.) Connect the USB Drive to the USB-port assigned to the ASUS BIOS Flashback procedure (see your mainboard manual for further details) Subsequently, press the EZ BIOS-Flashback button on your mainboard for three seconds until the EZ BIOS Flashback led starts blinking, indicating that the EZ BIOS Flashback procedure is in progress. Release the button and wait until the light turns off, indicating that the EZ BIOS Flashback procedure has completed. 6.) Boot your system, enter the BIOS Menu with F2 and implement the ASUS BIOS settings detailed in Section B.2). Save your BIOS settings and exit the BIOS with F7 and F10. Now you completed the BIOS update procedure and you should have an ASUS X299 mainboard with an unlocked MSR 0xE2 register. To check that the latter is the case, enter the following terminal command after rebooting your system: bdmesg The Clover boot log will show if the MSR 0xE2 register of your ASUS mainboard is unlocked. If you are able to find something like the following information, you fully succeeded in unlocking your MSR 0xE2 register: MSR 0xE2 before patch 00000402 MSR 0xCE 00070C2C_F3011A00 MSR 0x1B0 00000000 Alternatively, you can also check the status of your MSR 0xE2 register by means of the VoltageShift distribution. Download the VoltageShift distribution by following THIS LINK. Copy the voltageshift folder to your desktop mv ~/Downloads/voltageshift ~/Desktop/ Enter the following terminal commands: cd ~/Desktop/voltageshift/ sudo chmod -R 755 VoltageShift.kext sudo chown -R root:wheel ~/Desktop/voltageshift/VoltageShift.kext ./voltageshift read 0xe2 With unlocked MSR 0xE2 register, the output should look like as follows: RDMSR e2 returns value 0x7e000003 0x7e000003 is the value we need for our Skylake-X processors: This is from the latest kernel, the E2 value is in bold and backwards: 00a572c0: E200 0000 4C00 0000 0000 0000 0000 0000 ....L........... 00a572d0: 0F04 0000 0000 0000 0500 001E 0000 0000 ................ 00a572e0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00a572f0: E200 0000 9033 0000 0000 0000 0000 0000 .....3.......... 00a57300: 0F04 0000 0000 0000 0800 007E 0000 0000 ...........~.... 00a57310: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00a57320: E200 0000 0040 0000 0000 0000 0000 0000 .....@.......... 00a57330: 0F04 0000 0000 0000 0300 007E 0000 0000 ...........~.... 00a57340: 0000 0000 0000 0000 0000 0000 0000 0000 ................ Alternatively you can also check the MSR 0xE2 register status by means of Pike Alpha's AppleIntelInfo.kext. Note however that the latter kext is incompatible with the i9-7980XE! Users of the latter Skylake-X CPU should opt for either the "bdmesg" or "voltageshift" MSR 0xE2 register verification approach detailed above. Here I link the actual ASUS Prime X299 Deluxe 1301 BIOS firmware distribution X299D.CAP, which already includes the iMacPro Splash Screen image implemented by the procedure detailed in Section E.11). B2.) ASUS BIOS Configuration Before applying the specific settings, please provide your ASUS X299 Prime Deluxe with most actual BIOS firmware 1301. 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 [optional "Disabled", see important notification below!] b.) AVX Instruction Core Ratio Negative Offset: "3" [optional "Auto", see important notification below!] c.) AVX-512 Instruction Core Ratio Negative Offset: "2" [optional "Auto", see important notification below!] d.) CPU Core Ratio: Sync All Cores [optional "Auto", see important notification below!] e.) CPU SVID Support: Enabled [fundamental for proper IPG CPU power consumption display] f.) DRAM Frequency: DDR4-3200MHz 2.) /Advanced/CPU Configuration/ a.) Hyper Threading [ALL]: Enabled b.) MSR Lock Control: Disabled (NEW BIOS FEATURE TO UNLOCK MSR 0xE2 REGISTER) 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 (crucial for native HWP Intel SpeedShift Technology CPU Power Management) 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 (see VT-d notification below) 6.) /Boot/ a.) Fast Boot: Disabled b.) Above 4G Decoding: Off c.) Set your specific Boot Option Priorities 7.) /Boot/Boot Configuration a.) Boot Logo Display: Auto (important for E.11 - ASUS Boot Splash Screen Cosmetics) 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. Important Notes: "ASUS MultiCore Enhancement": When set to "Auto", MCE allows you to maximise the overclocking performance optimised by the ASUS core ratio settings. When disabled, MCE allows to set to default core ratio settings. "CPU Core Ratio - Sync All Cores": Tremendous increase in CPU performance can be achieved with the CPU Core Ratio set to "Sync All Cores". In case of i9-7980XE stock settings (max. turbo 4.4.Ghz), the Geekbench score difference is approx. 51.000 (disabled) compared to 58.000 (enabled)! Note however, that Sync All Cores should be used only in case of the availability of an excellent and extremely sophisticated water cooling system! Otherwise, CPU Core Ratio should be set to "Auto". Further note that with CPU Core Ratio set to "Sync All Cores", the AVX Instruction Core Ratio Negative Offset must be set to "3" and the AVX-512 Instruction Core Ratio Negative Offset must be set to "2". Without the correct core ratio offsets, your system might become unstable with CPU Core Ratio set to "Sync All Cores"! VT-d Note: For compatibility with VM or parallels, VT-d can be also ENABLED... Verify however, in this case that in your config.plist the boot flag "dart=0" is checked under Arguments in the "Boot" Section of Clover Configurator! Intel® Power Gadget (IPG) CPU Power Consumption note: for the proper display of the CPU Power Consumption in e.g. the Intel® Power Gadget it is absolutely mandatory to enable both /AI Tweaker/CPU SVID Support/ and /Advanced/CPU Configuration/CPU Power Management Configuration/Enhanced Intel Speed Step Technology (EIST) CPU Core Voltage Correction for ASUS X299 mainboard users: The ASUS Skylake-X BIOS microcode implementation has improved considerably. Former issues with "/AI Tweaker/CPU Core Voltage/" set to "Auto", where the assigned CPU Core Voltages have been too high by far, have been totally removed. At least with the i9-7980XE it is not anymore necessary to fix the CPU Core Voltage in the ASUS mainboard BIOS to a minimum value that still provides flawless system boot and full system performance during CPU max. load conditions in line with significantly CPU core temperatures, as detailed below. However, for the sake of completeness I did not remove the respective description so far. With CPU max. load conditions, I refer to the max. turbo frequency (e.g. 4.4 Ghz for the i9-7980XE) applied to ALL cores! Iterative manual approach to derive minimal CPU Core Voltages: This iterative approach detailed assumes the BIOS settings described in Section B1) - point 1) to 10), however by considering the following else optional settings: i.) "ASUS MultiCore Enhancement" set to "Auto" ii.) "CPU Core Ratio" set to "Sync All Cores" iii.) "AVX Instruction Core Ratio Negative Offset" set to "3" iv.) "AVX-512 Instruction Core Ratio Negative Offset" set to "2" 1.) Boot into Windows and launch ASUS CPU-Z as well as Cinebench. 2.) Run Cinebench CPU benchmarks and watch the Core VID values in CPU-Z under CPU max.load conditions. These values will usually exceed 1.2V with "/AI Tweaker/CPU Core Voltage/" set to "Auto". 3.) To optimise the "/AI Tweaker/CPU Core Voltage/" perform the following steps: a.) Enter the BIOS, go to "/AI Tweaker/CPU Core Voltage/" and change from "Auto" to "Manual" b.) Enter a slightly lower CPU Core Voltage Overrride (e.g. typically 0.01 V less) than originally observed with CPU-Z under Cinebench CPU benchmark max.load conditions in Windows, e.g. 1.190 V in the first iteration. c.) Reboot into windows and check if the Cinebench CPU benchmark scores are still in the expected range by also controlling the respective Core VID values during the Cinebench CPU benchmark max. load conditions d.) Repeat b.) and c.) until either your Cinebench CPU benchmarks scores start to significantly decrease or you start facing problems in booting your system. Given my personal experience with the i9-7980XE, a CPU Core Voltage Override of 1.120 V was optimal for a stock 4.4 GHz stock turbo frequency. In case of OC, the minimal CPU Core Voltage easily exceeded 1.2 V. Warning! Before performing the CPU Core Voltage Override Value Optimisation Approach, save your actual BIOS settings to a USB Drive. If during the iterative approach you are not able to successfully boot your system, perform a CMOS reset and restore your BIOS settings from the USB Drive, by subsequently entering the last successful CPU Core Voltage Override value! It is not recommend to use CPU Core Voltage Overrride larger than 1.27 V! Too high voltages can severely damage your CPU! In any case, when performing OC, a sophisticated water block circuit is absolutely mandatory! Always watch also your CPU temps when performing the CPU Core Voltage Optimisation, which should not exceed 90 deg C under CPU max. load conditions! Many thanks to @DSM2 for all his comments, valuable input, and proposed solutions. 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 (optional; consider warning in Section B.2) - ASUS BIOS Settings) 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 (optional) b.) Security option: Setup c.) Full Screen Logo Show: Enbabled 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/ (Designare EX only) a.) Security Level : SL0 - No Security 8.) /Chipset/ a.) VT-d: Disabled/Enabled (optional, see VT-d notification in Section B.2) - ASUS BIOS settings) 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 setting up your Skylake-X/X299 System and implementing the latest macOS High Sierra distribution. 1.) Note that the /EFI/Clover/drivers64UEFI/-directory of EFI-X299-10.13.4-Release-iMacPro1,1-310318.zip contains by default AptioMemoryFix.efi, which replaces OsxAptioFix3Drv-64.efi and all former OsxAptioFixDrv-64.efi or OsxAptioFix2Drv-64.efi implementations. AptioMemoryFix.efi is a totally new approach developed by @vit9696. AptioMemoryFix.efi is under permanent development. For further details and related discussions follow THIS LINK. To retrieve the most actual version, download and compile the AptioMemoryFix.efi Source Code from Github by means of AptioMemory-Builder.sh developed by @Pavo, using the following terminal commands: rm -rf AptioMemFix git clone https://github.com/Pavo-IM/AptioMemFix rm -rf ~/Desktop/AptioMemFix/ rm -rf ~/Desktop/AptioFix/ mv AptioMemFix/ ~/Desktop/ chmod +x ~/Desktop/AptioMemFix/AptioMemory_Builder.sh ~/Desktop/AptioMemFix/AptioMemory_Builder.sh This will create "AptioFix" and "AptioFix_Build" folders on your Desktop. The compiled AptioMemoryFix.efi can be found in ~/Desktop/AptioFix_Build/RELEASE/. Note that with Clover_v2.4k_r4392, AptioMemoryFix.efi has become an official Customization Option of Clover and can now be selected and therefore also just easily implemented in the frame of the Clover Boot Loader Installation. AptioMemoryFix.efi implements native NVRAM on our iMac Pro Skylake-X/X299 Systems under macOS High Sierra 10.13.2 (17C2120), 10.13.2 SA (17C2205), 10.13.3 (17D2047), 10.13.3 SA (17D2102), 10.13.3 SA (17D2104) and now also 10.13.4 (17E199), thus EmuVariableUefi-64.efi has been also omitted in the /EFI/Clover/drivers64UEFI/ directory contained in EFI-X299-10.13.4-Release-iMacPro1,1-310318.zip! Note that 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 AptioMemoryFix.efi works absolutely flawless on my system, without any memory allocation errors or slide issues even with the "slide" boot flag disabled. However, anybody witnessing issues with AptioMemoryFix.efi can try to use Clover's OsxAptioFix3Drv-64.efi instead. Don't forget to remove AptioMemoryFix.efi from the /EFI/Clover/drivers64UEFI/ directories in the EFI-Folders of your macOS USB Flash Drive Installer and macOS System Disk in this case. Also OsxAptioFix3Drv-64.efi maintains fully native NVRAM implementation and works absolutely flawless on my system, without any memory allocation errors or slide issues with the "slide" boot flag disabled. Note also that with OsxAptioFix3Drv-64.efi, Clover's RC Scripts have to be omitted during the clover boot loader installation. If already previously installed, remove Clover's RC Scripts from the /etc directory of your macOS USB Flash Drive Installer or System Disk as detailed above. 2.a.) All Users of rudimentary and basic ATI Starter Graphics Cards like the ATI Radeon RX 560 or RX 580 should use WhateverGreen.kext v1.1.7 and Lilu.kext v1.2.2. Advanced ATI Vega 64 and Frontier GPUs are natively implemented by OSX and run Out of Box (OoB). No need for an additional Whatevergreen.kext and Lilu.kext implementation. Remaining HDMI/DP port errors, hot plug errors and flaws with multi-monitor or 5K display configurations can be fixed by means of VegaGraphicsFixup.kext, kindly provided by @jyavenard. Important notifications for all Vega users with 4K monitors: When connecting e.g. the Vega Frontier 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). @DSM2 reported similar issues with his true 4K display and with both the ASUS Prime X299 Deluxe and the Gigabyte Designare EX. Thus the VEGA DP 4K boot screen resolution issue is neither related with the fact that the LG 38UC99-W is a 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 4K displays, as the DP 4K boot screen resolution issue is totally absent with my Nvidia GPU and the problem also does not only affect the ASUS Splash Screen but also spreads over the entire boot process until the login screen is reached (Windows and macOS). Splash Screen, Apple logo or verbose boot messages are not stretched but rather have VGA like resolution. Any fix of the AMD vBIOS would be highly appreciated. It is more than disappointing to witness such issues with 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 and everything will work as expected. b.) All Users with Maxwell and Pascal Nvidia Graphics Cards Users and SMBIOS MacPro1,1 can employ officially distributed Nvidia 10.13 Web Drivers for their Nvidia Pascal and Maxwell graphics cards! Upon my request from 7 January 2018, Nvidia officially released first WebDriver-387.10.10.10.25.105 for 10.13.2 (17C2120) and first WebDriver-387.10.10.10.25.106 for 10.13.2 SA (17C2205) - Supplemental Update on 11 January 2018. On 25 January 2018, Nvidia released a Web Driver 387.10.10.10.25.157 for 10.13.3 (17D2047), which worked flawless with Pascal GPUs (lagging issues have been reported for Maxwell GPUs). On 20 February 2018, Nvidia released a Web Diver 387.10.10.10.30.159 for 10.13.3 SA (17D2102). On 31 March 2018, Nvidia also released a Web Driver 387.10.10.10.30.103 for 10.13.4 (17E199). In case of persistent lagging issues, Maxwell GPU Users can alternatively use WebDriver-78.10.10.10.25.106 after a simple patching procedure detailed in Section E.2) - Graphics configuration. Future 10.13.5 Public Beta users can either use WebDriver-78.10.10.10.25.106 or 387.10.10.10.30.103 after the same Web Driver patching procedure. Nvidia Kepler Graphics Cards were anyway already natively implemented in the earlier beta distributions of macOS 10.13. Note that the Nvidia Black Screen Prevention by means of NvidiaGraphixFixup.kext has become obsolete with SMBIOS iMacPro1.1. Thus, the latter kext can be removed from the /EFI/Clover/kexts/Other/ directory of the EFI-Folder on your macOS USB Flash Drive Installer and 10.13 System Disk. For further details and error prevention see Section E.2). 3.) Avoid any MacOS assignments in KextToPatch and KernelToPatch entries implemented in the "Kernel and Kext Patches" Section of the Clover Configurator. If subsequently in my Guide you still find MatchOS assignments in respective figures or text, just ignore all likely yet persistent MatchOS assignments. In the config.plist of the EFI-Folder contained in EFI-X299-10.13.4-Release-iMacPro1,1-310318.zip, all MatchOS assignments have been definitely removed. 4.) If you have the Thunderbolt EX3 PCIe extension card already successfully connected with your ASUS Prime X299 Deluxe and properly implemented in your system, disconnect any Thunderbolt 2 drives during the macOS installation/upgrade procedure. If however the Thunderbolt EX3 PCIe extension card yet has not been properly configured and implemented in your system, remove the card for the macOS Upgrade or Clean Install procedure. 5.) Note that on some systems it might be necessary to check the KernelPM Option in the "Kernel and Kext Patches Section" of the Clover Configurator to successfully boot the respective system. Note that in the config.plist of the EFI-Folder attached below, this option is unchecked, as it is not required in case of the ASUS Prime X299 Deluxe. 6.) Always check that you have the most actual apfs.efi in the /EFI/CLOVER/drivers64UEFI/ - directories of your USB Flash Drive Installer and System Disk! The actual apfs.efi can be obtained by following the respective guideline detailed below: a.) Download and install Pacifist for Mac. b.) Copy the "Install macOS High Sierra.app" to your Desktop -> right-click with your mouse on the app and select "Show Package Contents" -> click with the mouse on "Contents" and subsequently on "Shared Support" -> right-click with the mouse on "BaseSystem.dmg" and select "Open With" -> select "pacifist.app". Pacifist is now loading the "BaseSystem.dmg" package contents. c.) Now click with the mouse on "usr" -> "standalone" -> "i386". After a right-click on apfs.efi, select "Extract toCustom Location...". Choose your Desktop as Destination. Answer the subsequent question "Extract apfs.efi ?" with "Extract". You now have the most actual version of apfs.efi on your Desktop. d.) Note that the EFI-Folder of EFI-X299-10.13.4-Release-iMacPro1,1-310318.zip contains a patched apsf.efi without verbose boot. The respective patching procedure and the related discussion can be derived by following THIS LINK. Credits to @PMheart and @ErmaC from InsanelyMac. e.) If necessary (usually the /EFI/CLOVER/drivers64UEFI/ - directory of my distributed EFI-Folders already containsthe most actual apfs.efi version), copy the actual patched apfs.efi to the /EFI/CLOVER/drivers64UEFI/ - directories of your USB Flash Drive Installer and System Disk! 7.) To avoid Skylake-X thread TSC desynchronisation errors during boot and wake from S3, 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! 8.) Already during the first Beta Versions of macOS 10.13 High Sierra, Apple forced the beta users to use the new Apple file system APFS in case of a Clean Install/update of MacOS High Sierra 10.13. Also within macOS High Sierra 10.13.4 (17E199) this is the case. Most APSF incompatibilities with available system related software apparently have been already removed. All recent versions of Carbon Copy Cloner (CCC) support the direct cloning of APFS system disks and provide the previously missing option for APFS system backups. Until Boot-Loader Distribution Clover_v2.4k_r4210, it was also impossible to install the Clover Boot-Loader in the EFI-Partition of an APFS System Disk by means of the Clover Boot-Loader Installer Package (the Clover Boot-Loader files had to be added manually). However, all recent Clover Boot-Loader Distributions work absolutely flawless with APFS System Disks. In any case, with @Brumbear's UnSolid.kext in the /EFI/Clover/kexts/Other/ directory, OSX is forced to remain with the HFS+ file format when installing or updating to the most recent macOS 10.13 distribution. Note that there is no way to convert an APFS disk back to HFS+ without the loss of all data, but one can easily reformat an APFS formatted disk to HFS+ under OSX by using either Apple's Disk Utility App or "diskutil" commands. All you need to do is to previously unmount the APFS volume before erasing it with a journaled HFS+ file system and a GRUB Partition Table (GTP). If you want to maintain the disk's content, perform a backup before erasing the disk with a HFS+ format. The application of Apple's Disk utility is straight forward. The "diskutil" equivalent is detailed below: In the Terminal app, type: diskutil list In the output which you can read by scrolling back, you will find all internal disks named /dev/disk0, /dev/disk1, depending upon how many physical disks are present in your system. Make a note of the disk identifier for the disk you intend to format (you can eliminate risk by removing all disks but the intended target). In the Terminal app, type: diskutil unmount /dev/diskX where diskX is a place holder for the disk to be unmounted. Subsequently, you can erase the entire disk with HFS+ and a GPT by typing the following terminal command: diskutil partitionDisk /dev/diskX 1 GPT jhfs+ "iMacPro" R where /dev/diskX is again a place holder for disk to be erased and iMacPro would be the label for the single partition created. The remaining 1 GPT jhfs+ and R arguments tell diskutil to create a single partition, within a GUID partition table, formatted as Journaled HFS+ and using the entire disk, respectively. Alternatively one can also use the following terminal command: diskutil partitionDisk /dev/diskX GPT JHFS+ iMacPro 0b where /dev/diskX is again a place holder for disk to be erased and iMacPro is again the label for the disk partition created. The GPT HFFS+ and 0b arguments again tell diskutil to create a single partition, within a GUID partition table, formatted as Journaled HFS+ and covering the entire disk, respectively. In the Terminal app, type now: diskutil mount /dev/diskX where diskX is again a place holder for the disk to be remounted. Note, that by means of the "diskutil approach", brand new unformatted or not compatibly formatted system NVMe, SSD and HDD system drives can be also directly formatted within the macOS Clean Install procedure. When presented with the initial install screen where you are presented options to Restore From Backup or Install, select Terminal from the Utilities menu bar item; The "diskutil" terminal approach is also able to convert a HFS+ macOS High Sierra 10.13 System Disk to APFS. To do so enter the following terminal command: diskutil apfs convert /dev/diskX where diskX is again a place holder for the HFS+ disk to be converted to APFS. The same procedure again can also be directly performed by means of Apple's Disk Utility. If you opt for an APFS System Disk implementation, please note that all other disks on your system also should be formatted with APFS. On systems with APFS disks and non-APFS disks, the boot duration will increase, as apsf.efi will perform a fsck check of non-AFPS disks (like HFS+ or Fat32) during boot. However, dual boot APFS Systems with an NTFS Windows System Disk are not effected by the apsf.efi issue, as OSX does not know how to properly deal with NTFS. 9.) 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.13 System Disk, or to disable the second LAN port in the BIOS during the MacOS Installation. 10.) Lilu and Lilu Plugin distribution remarks: To access, download and compile most actual but not yet officially released Lilu and Lilu plugin distributions, follow these links: a.) Lilu Source distribution b.) AppleALC Source Distribution c.) NvidiaGraphicsFixup d.) Whatevergreen To successfully compile the AppleALC, NvidiaGraphicsFixup and Whatevergreen source code distributions with Xcode 9.3 under macOS High Sierra 10.13.4 (17E199), download, unzip and copy the respective actual Lilu DEBUG distribution to the AppleALC, NvidiaGraphicsFixup and Whatevergreen source code distribution directories. To compile the respective Lilu, AppleALC, and NvidiaGraphicsFixup source code distributions just execute the terminal command "xcodebuild" after changing to the respective source code distribution with the "cd" terminal command. The resulting compiled kexts can be always found in the respective /build/Release/ sub-directories of the respective source code distribution directories. Further details to the topic can be accessed by following THIS LINK. 11.) To clearly get kernel panic images with a call trace in case of kernel panics, I implemented (checked) boot flags "debug=0x100" and "keepsyms=1" in the config.plist of EFI-X299-10.13.4-Release-iMacPro1,1-310318.zip in the "Boot" Section of Clover Configurator under "Arguments". 12.) Note that in the current EFI-X299-10.13.4-Release-iMacPro1,1-310318.zip distributions, I also removed CsmVideoDxe-64.efi from /EFI/CLOVER/drivers64UEFI, as the latter file is only required for proper Legacy screen resolution purposes with CSM enabled, which is definitely not our case. 13.) 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". 14.) Note that I added to the config.plist contained in EFI-X299-10.13.4-Release-iMacPro1,1-310318.zip in Section "Devices" of Clover Configurator under "Arbitrary" the following details absolutely mandatory for TB hot plug functionality in line with the SSDT-X299-iMacPro.aml, detailed in Section E.9.2) of this guide: PCIAddr* Comment 01:00.00 PCI THUNDERBOLT 1578 0 Key* value* Value Type PCI-Thunderbolt 1 NUMBER IOName pci-bridge STRING All credits to boryspoass All entries should be removed by all users without TB hardware implementation. D.) iMac Pro macOS 10.13 High Sierra System Setup Below, one finds a detailed description for the Clean Install of macOS High Sierra 10.13.4 17E199 (D.4). This also includes the iMacPro EFI-Folder Preparation (D.1) as well as the macOS High Sierra 10.13.4 (17E199) Installer Package (D.2) and macOS High Sierra 10.13.4 (17E199) USB Flash Drive Installer Creation (D.3). 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 a standard macOS build implementation (D.5), as well as for the subsequent iMac Pro macOS High Sierra 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 EFI-X299-10.13.3-Release-iMacPro1,1-310318.zip attached at the bottom of this originating post/guide 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 EFI-X299-10.13.4-Release-iMacPro1,1-310318.zip. Press several times the "Generate New" Button next to serial number text field. In the final step, open a terminal, enter repeatedly the command "uuidgen", and copy the output value to the SMUUID field in the "SMBIOS" Section of the Clover Configurator. Finally save the modified config.plist. 3.) Copy the appropriate TSCAdjustRest.kext, which you modified by following error prevention C.7), to the /EFI/CLOVER/kexts/Other/ directory of the EFI-Folder. You know have a fully equipped EFI-Folder for subsequent implementations as detailed below. D.2) iMac Pro macOS High Sierra 10.13.4 (17E199) Installer Package Creation While on non-iMacPro systems the macOS High Sierra 10.13.4 (17E199) full package installer (5.22 GB) can be retrieved directly from the Appstore, the download on iMacPro systems apparently results in a file with largely reduced size (22.5 MB). To derive the macOS High Sierra 10.13.4 (17E199) Full-Package Installer on iMac Pro Systems just follow the individual steps below: 1.) Open a terminal and create a "091-76233" directory on your Desktop. Subsequently change to the newly created directory. All this can be done with the following terminal commands: mkdir ~/Desktop/091-76233/ cd ~/Desktop/091-76233/ 2.) Download the following files from the Apple server (public links) to your ~/Desktop/091-62779/ directory by a copy & paste of the following terminal commands: curl https://swdist.apple.com/content/downloads/10/62/091-76233/v27a64q1zvxd2lbw4gbej9c2s5gxk6zb1l/091-76233.English.dist -o 091-76233.English.dist curl http://swcdn.apple.com/content/downloads/10/62/091-76233/v27a64q1zvxd2lbw4gbej9c2s5gxk6zb1l/RecoveryHDMetaDmg.pkg -o RecoveryHDMetaDmg.pkg curl http://swcdn.apple.com/content/downloads/10/62/091-76233/v27a64q1zvxd2lbw4gbej9c2s5gxk6zb1l/InstallInfo.plist -o InstallInfo.plist curl http://swcdn.apple.com/content/downloads/10/62/091-76233/v27a64q1zvxd2lbw4gbej9c2s5gxk6zb1l/AppleDiagnostics.chunklist -o AppleDiagnostics.chunklist curl http://swcdn.apple.com/content/downloads/10/62/091-76233/v27a64q1zvxd2lbw4gbej9c2s5gxk6zb1l/OSInstall.mpkg -o OSInstall.mpkg curl http://swcdn.apple.com/content/downloads/10/62/091-76233/v27a64q1zvxd2lbw4gbej9c2s5gxk6zb1l/AppleDiagnostics.dmg -o AppleDiagnostics.dmg curl http://swcdn.apple.com/content/downloads/10/62/091-76233/v27a64q1zvxd2lbw4gbej9c2s5gxk6zb1l/InstallESDDmg.chunklist -o InstallESDDmg.chunklist curl http://swcdn.apple.com/content/downloads/10/62/091-76233/v27a64q1zvxd2lbw4gbej9c2s5gxk6zb1l/BaseSystem.chunklist -o BaseSystem.chunklist curl http://swcdn.apple.com/content/downloads/10/62/091-76233/v27a64q1zvxd2lbw4gbej9c2s5gxk6zb1l/InstallESDDmg.pkg -o InstallESDDmg.pkg curl https://swdist.apple.com/content/downloads/10/62/091-76233/v27a64q1zvxd2lbw4gbej9c2s5gxk6zb1l/RecoveryHDMetaDmg.pkm -o RecoveryHDMetaDmg.pkm curl http://swcdn.apple.com/content/downloads/10/62/091-76233/v27a64q1zvxd2lbw4gbej9c2s5gxk6zb1l/BaseSystem.dmg -o BaseSystem.dmg curl https://swdist.apple.com/content/downloads/10/62/091-76233/v27a64q1zvxd2lbw4gbej9c2s5gxk6zb1l/InstallESDDmg.pkm -o InstallESDDmg.pkm curl http://swcdn.apple.com/content/downloads/10/62/091-76233/v27a64q1zvxd2lbw4gbej9c2s5gxk6zb1l/InstallAssistantAuto.pkg -o InstallAssistantAuto.pkg curl https://swdist.apple.com/content/downloads/10/62/091-76233/v27a64q1zvxd2lbw4gbej9c2s5gxk6zb1l/InstallAssistantAuto.pkm -o InstallAssistantAuto.pkm The full list of package files can be found within the following catalog URL, searching for key https://swscan.apple.com/content/catalogs/others/index-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog.gz. 3.) Create the installer.pkg on your Desktop with the following terminal command: cd .. productbuild --distribution ./091-76233/091-76233.English.dist --package-path ./091-76233/ installer.pkg 4.) Create the "Install MacOS High Sierra.app" 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 High Sierra.app" with the following terminal commands: sudo cp ./091-76233/InstallESDDmg.pkg /Applications/Install\ macOS\ High\ Sierra.app/Contents/SharedSupport/InstallESD.dmg sudo cp ./091-76233/AppleDiagnostics.dmg /Applications/Install\ macOS\ High\ Sierra.app/Contents/SharedSupport/ sudo cp ./091-76233/AppleDiagnostics.chunklist /Applications/Install\ macOS\ High\ Sierra.app/Contents/SharedSupport/ sudo cp ./091-76233/BaseSystem.dmg /Applications/Install\ macOS\ High\ Sierra.app/Contents/SharedSupport/ sudo cp ./091-76233/BaseSystem.chunklist /Applications/Install\ macOS\ High\ Sierra.app/Contents/SharedSupport/ Verify your "Install High Sierra.app" for completeness. You should now have a complete macOS High Sierra 10.13.4 (17E199) Installer package in your /Applications Folder. Many thanks to [USER=17860]@macandrea[/USER] for his substantial and extensive contributions. He even now automatised the entire "Install High Sierra.app" creation procedure detailed above within one single script: createInstaller.sh will automatically create on any MacOS System the "Install High Sierra.app" for macOS High Sierra 10.13.4 (17E199) in the /Applications folder. Just download und unzip createInstaller.sh.zip and run the following terminal commands: cd ~/Downloads chmod +x createInstaller.sh ./createInstaller.sh Absolutely brilliant, gorgeous and genius job man! D.3) iMac Pro macOS High Sierra 10.13.4 (17E199) USB Flash Drive Installer Creation Follow the individual steps detailed below to successfully create a bootable iMac Pro macOS High Sierra 10.13.4 (17E199) 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 High Sierra 10.13.4 (17E199) Installer Package in your /Application Folder, connect your USB Flash Drive (named USB) and run the following terminal command: sudo /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ High\ Sierra.app --nointeraction Alternatively, one can create the iMac Pro macOS USB Flash Drive Installer also by means of the Install Disk Creator.app 3.) Yet we have to make our iMac Pro macOS USB Flash Drive Installer also bootable. This can be partly done by means of the following terminal commands: cd /Volumes/YOUR_USB_VOLUME mkdir .IABootFiles cd .IABootFiles cp /Volumes/YOUR_USB_VOLUME/System/Library/CoreServices/boot.efi . This is a tricky part where many people fail. Note that "YOUR_USB_VOLUME" is a place holder in the above commands for the name of your real USB Flash Drive. Before executing the above commands, replace "YOUR_USB_VOLUME" by the real name of your USB Flash Drive. To make the entire thing idiot proofed, let me explain the entire procedure by means of some nice example once provided by @paulotex to some user: If your USB is called "Super USB I Like It Very Much" then you have to use: cd /Volumes/Super\ USB\ I\ Like\ It\ Very\ Much Note the "\" before each space. The entire procedure for the assumed USB Flash Drive with the above name convention would look like that (don't forgot the isolated dot "." at the end of the last copy (cp) command below): cd /Volumes/Super\ USB\ I\ Like\ It\ Very\ Much mkdir .IABootFiles cd .IABootFiles cp /Volumes/Super\ USB\ I\ Like\ It\ Very\ Much/System/Library/CoreServices/boot.efi . With the terminal command: ls boot.efi you can subsequently verify that boot.efi is there where it should be. If you mistake at this point, your USB Flash Drive Installer will not be bootable and the USB Flash Drive macOS Installer partition will be simply invisible in the Clover Boot Menu! 4.) For successfully booting your iMac Pro macOS USB Flash Drive Installer, the latter must however also contain a valid EFI- Folder with an SMBIOS iMacPro1,1 system definition. Thus, copy the EFI-Folder you prepared in Section D.1) to the yet empty EFI Partition of your iMac Pro macOS USB Flash Drive Installer. You now have a fully functional and bootable iMac Pro macOS High Sierra 10.13.4 (17E199) USB Flash Drive Installer. Many thanks to @macandrea for his substantial and extensive contributions. D.4) iMac Pro macOS High Sierra 10.13.4 (17E199) Clean Install on Skylake-X/X299 Follow the individual steps detailed below to successfully setup macOS High Sierra 10.13.4 (17E199) on a virgin system drive of your choice (NVMe, SSD or HDD). 1.) In order to perform a clean install of macOS High Sierra 10.13.4 (17E199), 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 iMac Pro macOS High Sierra 10.13.4 (17E199) USB Flash Drive Installer, your created in Section D.2) 4.) While booting your system, press the F8 button to enter the BIOS boot menu. Select to boot from your iMac Pro macOS USB Flash Drive Installer. 5.) Subsequently, click on the USB Flash Drive Installer Icon in the clover boot menu to boot the respective macOS Installer partition on your iMac Pro macOS USB Flash Drive Installer 6.) After successful boot, pass the individual steps of the macOS high Sierra 10.13 installation menu and finally select the destination drive of your macOS High Sierra 10.13 Installation, which should be logically the system disk you successfully configured above. In the next step, the Installer will create a macOS High Sierra 10.13 Installer Partition on the system disk and subsequently reboot your system. 7.) During system reboot, just press again the F8 button to enter the BIOS boot menu. Select again to boot from your USB Flash Drive. In contrary to 6.), click this time on the "Install MacOS.." Icon in the clover boot screen to boot the newly created macOS High Sierra 10.13 Installer Partition on your system disk. 8.) After successful boot, you will enter now the macOS High Sierra 10.13 Installer Screen with a progress bar starting at 34 minutes. 9.) After another reboot, press again the F8 button to enter the BIOS boot menu. Select to boot with your System Disk EFI-folder. Click on the "MacOS High Sierra" icon in the clover boot screen to boot the updated macOS High Sierra 10.13 partition on your system disk. 10.) After successful boot you will enter again the macOS High Sierra 10.13 Installer Screen with a progress bar starting at 18 minutes. After successfully registration at iCloud at the end of the macOS installation, you now have your first iMac Pro macOS High Sierra 10.13.4 (17E199) build. Proceed with Section D.6) - iMac Pro macOS High Sierra Build Updates (if necessary) or E.) - Post Installation Process. D.5) Direct iMac Pro conversions of a functional 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 High Sierra.app") to your /Applications folder. Alternatively to D.2) and the macOS Full Package Installer, it is also sufficient to just download the original unmodified macOS High Sierra 10.13.4 (17E199) BaseSystem.dmg distribution from the Apple Server to your Desktop with the following terminal commands: cd ~/Desktop/ curl http://swcdn.apple.com/content/downloads/10/62/091-76233/v27a64q1zvxd2lbw4gbej9c2s5gxk6zb1l/BaseSystem.dmg -o BaseSystem.dmg 4.) Double click on the "Install High Sierra.app" in the /Applications Folder to start the macOS High Sierra 10.13.4 (17E199) installation. Alternatively, double click on the BaseSystem.dmg to mount the macOS installer and double click on the therein contained "Install macOS High Sierra.app" to start the macOS High Sierra 10.13.4 (17E199) installation. 5.) After reboot, click on the "Install MacOS.." Icon in the clover boot screen to boot the newly created macOS High Sierra 10.13 Installer Partition on your system disk. 6.) After successful boot, you will enter now the macOS High Sierra 10.13 Installer Screen with a progress bar starting at 43 minutes. 7.) After another reboot, click on the "MacOS High Sierra" icon in the clover boot screen to boot the updated macOS High Sierra 10.13 partition on your system disk. 8.) After successful boot you will enter again the macOS High Sierra 10.13 Installer Screen with a progress bar starting at 18 minutes. After successfully registration at iCloud at the end of the macOS installation, you now have your first iMac Pro macOS High Sierra 10.13.4 (17E199) 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 High Sierra Update Procedure After the successful clean install or conversion you will be able to update your iMac Pro macOS High Sierra 10.13.4 (17E199) build to macOS High Sierra 10.13.5 Public Beta directly via the Appstore, once the latter has been released. For macOS beta builds it is recommended to clone your macOS High Sierra 10.13.4 (17E199) System Disk with Carbon Copy Cloner (CCC) to a test drive and to update to the Public Beta on the latter. Also any other future macOS High Sierra Update can be directly performed via the Appstore. 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 Section "Kernel and Kext Patches" of Clover Configurator, which by default is still implemented but disabled in the config.plist of the distributed EFI-Folder EFI-X299-10.13.4-Release-iMacPro1,1-310318.zip. 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. Typically the command "sysctl machdep.xcpm.mode" reveals 1, which means that XCPM is active. 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. Alternatively, the plugin-type injection also can be performed by some injector SSDT like the ssdt.aml provided by @interferenc, linked here. For the proper "plugin-type" injection on your system, alternatively download and unzip the ssdt.aml and copy the file to the /EFI/Clover/ACPI/patched/ directory of the EFI-Folder on your System Disk and reboot subsequently. a.) Verify that in the IORegistryExplorer you have now under CP00@0 the following entry: Property: Type: Value: plugin-type Number 0x1 b.) 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> c.) Verify with the following terminal command: kextstat|grep -y appleintelcpu that you got now rid of the Apple Intel CPU power management. If the result is empty you are fine. d.) 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: ATI Starter Graphics Cards solutions like the ATI Radeon RX 560 or RX 580 just require two basic kexts in the /EFI/Clover/kexts/Other/ directory of the EFI folders on both USB Flash Drive Installer and 10.13 System Disk , i.e. namely WhateverGreen.kext v1.1.7 and Lilu.kext v1.2.2. Advanced ATI Vega 64 and Frontier GPUs are natively implemented by OSX and run Out of Box (OoB). No need for an additional Whatevergreen.kext and Lilu.kext implementation. Remaining HDMI/DP port errors, hot plug errors and flaws with multi-monitor or 5K display configurations can be fixed by means of VegaGraphicsFixup.kext, kindly provided by @jyavenard. Important notifications for all Vega users with 4K monitors: When connecting e.g. the Vega Frontier 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). @DSM2 reported similar issues with his true 4K display and with both the ASUS Prime X299 Deluxe and the Gigabyte Designare EX. Thus the VEGA DP 4K boot screen resolution issue is neither related with the fact that the LG 38UC99-W is a 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 4K displays, as the DP 4K boot screen resolution issue is totally absent with my Nvidia GPU and the problem also does not only affect the ASUS Splash Screen but also spreads over the entire boot process until the login screen is reached (Windows and macOS). Splash Screen, Apple logo or verbose boot messages are not stretched but rather have VGA like resolution. Any fix of the AMD vBIOS would be highly appreciated. It is more than disappointing to witness such issues with 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 and everything will work as expected. Nvidia Kepler Graphics Cards were already natively implemented in the earlier beta distributions of macOS 10.13. All Users with Maxwell and Pascal Nvidia Graphics Cards on SMBIOS MacPro1,1 can employ officially distributed Nvidia 10.13 Web Drivers for their Nvidia Pascal and Maxwell graphics cards! Upon my request from 7 January 2018, Nvidia officially released first WebDriver-387.10.10.10.25.105 for 10.13.2 (17C2120) and first WebDriver-387.10.10.10.25.106 for 10.13.2 SA (17C2205) - Supplemental Update on 11 January 2018. On 25 January 2018, Nvidia released a Web Driver 387.10.10.10.25.157 for 10.13.3 (17D2047), which worked flawless with Pascal GPUs (lagging issues have been reported for Maxwell GPUs). On 20 February 2018, Nvidia released a Web Diver 387.10.10.10.30.159 for 10.13.3 SA (17D2102). On 31 March 2018, Nvidia also released a Web Driver 387.10.10.10.30.103 for 10.13.4 (17E199). In case of persistent lagging issues, Maxwell GPU Users can alternatively use WebDriver-78.10.10.10.25.106 after a simple patching procedure detailed below. Future 10.13.5 Public Beta users can either use WebDriver-78.10.10.10.25.106 or 387.10.10.10.30.103 after the same Web Driver patching procedure. How to patch an Nvidia WebDriver: Download the Nvidia WebDriver-Payload Repackager from InsanelyMac. Credits to Chris111 and Pavo. The patch procedure is simple,fully described in the implemented Readme.txt and will reveal a Repackaged-WebDriver.pkg, which can be used for installing the patched Nvidia Web Driver Installation under macOS 10.13.4 (17E199) or any future 10.13.5 Beta distributions. Nvidia Web Driver Installation and Black Screen Prevention: Apparently with SMBIOS iMacPro1,1, the Nvidia Black Screen Prevention has become obsolete. Thanks to @fabiosun from InsanelyMac for this finding. Thus, NvidiaGraphicsFixup.kext, subverting AppleMobileFileIntegrity banning the driver can be fully removed from the /EFI/CLOVER/kexts/Other/ directory of your macOS Flash Drive Installer and 10.13 System Disk! a.) Install the original or patched Nvidia 10.13 Web Driver Package. b.) In case of the original Web Driver, just reboot as requested and you will already have a fully functional Web Driver. c.) In case of the patched Web Driver, 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 "17C2205" or "17E199" to "17E199" or the corresponding build number of future 10.13.5 Beta distributions. 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 will not be active yet. Therefore, open the Nvidia Driver Manager and select "Nvidia Web Driver". ix.) Now reboot as requested and you will have a fully functional patched Web Driver under 10.13.4 (17E199) or future 10.13.5 Beta distributions. E.3) Audio Configuration: Note that opposite to my previous EFI-Folder distributions, EFI-X299-10.13.4-Release-iMacPro1,1-3103218.zip 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 @Rehabman from gitbucket.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 @vit9696 and @apfelnico. This new AppleALC audio approach bases on AppleALC.kext v1.2.4, which further requires Lilu.kext v1.2.2 in the /EFI/CLOVER/kexts/Other/ directory of your System Disk. Provided that you use the EFI-Folder contained in EFI-X299-10.13.4-Release-iMacPro1,1-310318.zip, 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 DSDT replacement patch in Clover Configurator Section "ACPI" under "DSDT Patches". Comment: Find*[Hex] Replace [Hex] CAVS -> HDEF 43415653 48444546 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 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 v1.2.2 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 the EFI-Folder contained in EFI-X299-10.13.4-Release-iMacPro1,1-310318.zip, 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 DSDT Replacement Patch in Clover Configurator Section "ACPI" under "DSDT Patches". Comment Find*[HEX] Replace*[HEX] Rename CAVS to HDEF 43415653 48444546 2.) Download, unzip and copy the 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&0xfffe0000</string> with <key>IOPCIPrimaryMatch</key> <string>0x43831002</string> b.) Download, unzip and run the IORegistryExplorer.app v2.1 attached at the end of this originating post/guide. 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. 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, unzip 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 DSDT 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 @Toldea'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 the EFI-Folder contained in EFI-X299-10.13.4-Release-iMacPro1,1-3103.zip, 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 DSDT Replacement Patch in Clover Configurator Section "ACPI" under "DSDT Patches". Comment Find*[Hex] Replace[Hex] Rename CAVS to HDEF 43415653 48444546 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 3.) Download, unzip and copy the realtekALC.kext v2.8 to the /EFI/CLOVER/kexts/Other/ directory on your System Disk 4.) Download and execute audio_cloverALC-130.sh, which will patch the native vanilla AppleHDA.kext in the /S/L/Edirectory of your System Disk 5.) 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 DSDT 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 natively implements IOPCIPrimaryMatchID "a2af8068" and AppleUSBXHCISPT on the ASUS Prime X299 Deluxe. Thus, 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) ports work natively at expected data transfer rates (90 Mb/S (USB 3.0)and 40 MB/s (USB 2.0), respectively) for all X299 mainboards. All external and internal USB 3.1 (USB 3.1 Gen 2 Type-A and Type-C) ports were natively implemented already before on different controllers than XHC and also work at data rates up to 140 MB/s. Up to my best knowledge, the native XHC USB implementation states for all X299 mainboards. My former sophisticated board-specific XHC USB Kext Workaround and all respective Guidelines are herewith obsolete for X299. Anybody with a ASUS Prime X299 Deluxe and still interested in the latter XHC USB Kext can still download KGP-iMacPro-XHCI.kext. Just note that for the else now totally native XHC USB implementation, one just needs to add a XHC USB port limit patch in the config.plist under "KextsToPatch" in Section "Kernel and Kext Patches" of Clover Configurator, as else not all available XHC USB ports will be natively implemented. Further note, the new USB port Limit Patch for 10.13.4 (17E199): Name* Find*[Hex] Replace* [Hex] Comment AppleUSBXHCI 837d940f 0f839704 0000 837d941a 90909090 9090 10.13.4 USB Port Limit Patch Many thanks to @PMHeart from InsanelyMac for providing the respective XHC USB port limit patches. USB 2.0 and USB 3.0 Benchmark Results USB 3.1 Type-A and Type-C Benchmark Results E.5) ASUS Prime X299 Deluxe Thunderbolt EX3 PCIe Add-On Implementation For the successful implementation of the Thunderbolt EX3 PCIe Add-On Adapter, a fully working Dual Boot System with an UEFI Windows Implementation is unfortunately absolutely mandatory. You will not be able to configure your Thunderbolt EX3 PCIe Add-On Adapter in the mainboard BIOS, until the Adapter has been successfully recognised and initialised by the UEFI Windows System. Fortunately legal and official License Keys for the actual Windows 10 Pro distribution can be purchased with a little bit of temporal effort on Google for an actual price of 20 $ or even below! Thus, the installation of a dual boot system with Windows will require some additional temporal user effort but will not noticeably further affect the users's budget. Please note that I especially emphasize the term UEFI, when speaking about the parallel Windows implementation. Don't use or perform a Legacy Implementation of Windows! In order to properly implement your Windows partition later-on in the Clover Bootloader and to comply with the actual Mainbaord-BIOS settings requirements, it is absolutely mandatory to run or perform an UEFI Windows implementation! So if not already implemented, how to achieve a fully working UEFI Windows Implementation and Dual boot System with Windows? 1.) Important Note! For the implementation of the UEFI Windows Distribution disconnect all usually plugged macOSDrives from your rig! The Windows installer will implement a Windows Boot Loader! If you have any macOS Drive connected during installation, the latter Windows Boot Loader might overwrite and destroy your current Clover Boot Loader. This is the last thing you want! Thus for the windows installation just connect the destination drive for the installation and the Windows USB Flash Drive Installer your will create in the subsequent step below! 2.) This Tutorial explains in all necessary detail how to download an actual Windows 10 Creator distribution, and how tosubsequently create a bootable USB Flash Drive Installer for a subsequent UEFI Windows 10 installation by means RUFUS! Don't put emphasis on alternative optional methods and always take care that you just follow the instructions for a successful subsequent UEFI Windows Installation! 3.) This Tutorial explains in all necessary detail how to properly perform the actual Windows 10 Pro Creator UEFIInstallation, subsequent to the a bootable Windows USB Flash Drive Installer realisation detailed in 2.) above. 4.) This Tutorial explains in all necessary detail, how to migrate/clone/backup your Windows 10 UEFI System Disk afterinstallation for future maintenance and safety. 5.) After successfully performing the UEFI Windows 10 Pro Creator Implementation, you can reconnect your macOS driveto your rig. The newly created UEFI Windows 10 Pro Creator Partition will automatically appear as a further boot option in both BIOS Boot Option Menu (F8) and Clover Boot Menu! No additional or further actions or measurements have to be taken! 6.) Once your Windows 10 Pro Creator Partition is fully operational, install all drivers and programs implemented on theASUS Prime X299 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 of your rig and start with the installation of the Thunderbolt EX3 PCIe Add-On Adapter a.) I recommend to install the adapter in third PCIe Slot from the bottom which is PCIEX_3 b.) Don't forget to also connect the attached TB-Cable with both the connector on the Thunderbolt EX3 PCIe Add-OnAdapter and the TB-Header on the ASUS Prime X299 Deluxe mainboard. 8.) Reboot into windows and install the ASUS ThunderboltEX 3 DVD accompanying your ASUS Prime X299 Deluxe mainboard. 9.) Reboot and enter the Mainboard BIOS (F2) a.) Go to /Advanced/ Thunderbolt(TM) Configuration/ and apply the following BIOS Settings detailed below: TBT Root por Selector PCIE16_3 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 SL1-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 Disabled 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 Disabled b.) Verify in /Boot/ that Above 4G Decoding is Off Above 4G Decoding Off 10.) Shut down your rig, connect the Thunderbolt Device with the Thunderbolt EX3 Adaptor and boot 11.) You are done! Your Thunderbolt EX3 PCIe Adapter and connected devices should be now fully implemented andfunctional. 12.) We will add TB XHC USB and TB Hot Plug functionality by considering error prevention C.14) and by means of the SSDT-X299-iMacPro.aml described in Section E.9.2) of this guide. Thunderbolt Benchmarks: For the sake fo completeness and for testing the overall Thunderbolt Functionality and Performance, I benchmarked the the data rates of an external Thunderbolt Drive connected via Apple's Thunderbolt-3 to Thunderbolt-2 Adapter. As External Thunderbolt Drive, I once more used the Lacie Rugged Thunderbolt / USB Type-A and Type-C HDD. E.6) NVMe compatibility In contrary to macOS Sierra 10.12, in macOS High Sierra 10.13 there is native support of non-4Kn NVMe SSDs, like my Samsung EVO 960 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 10.13 on M.2 NVMEs like the Samsung EVO 960. E.7.) SSD TRIM Support Macs only enable TRIM for Apple-provided solid-state drives they come with. If you upgrade a Mac with an aftermarket SSD, the Mac won’t use TRIM with it. The same applies for SSD's used by a Hackintosh. When an operating system uses TRIM with a solid-state drive, it sends a signal to the SSD every time you delete a file. The SSD 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 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 can then manage its available storage more intelligently.. Note that the config.plist in the EFI-folder of EFI-X299-10.13.4-Release-iMacPro1,1-310318.zip, contains an SSD "TRIM Enabler" KextsToPatch entry, which can be found in the " Kernel and Kext Patches" Section of the Clover Configurator. Name* Find*[HEX] Replace*[HEX] Comment MatchOS IOAHCIBlockStorage 4150504c 45205353 4400 00000000 00000000 0000 Trim Enabler 10.12.x,10.13.x With this KextToPatch entry, SSD TRIM should be fully enabled on your 10.13 System, see Apple's System Report below. For the sake of completeness please find below the Benchmark of connected NVMe and SDD Drives. E.8) ASUS Prime X299 Deluxe on-board 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 anyway natively implemented Intel I219-V Gigabyte on-board LAN controller of the ASUS Prime X299 Deluxe. Thus, both ethernet ports on the ASUS Prime X299 Deluxe should now be fully operational.. E.9) ASUS Prime X299 Deluxe PCI Device Implementation In order to properly implement all PCI device drivers on his/her system and build, one needs an adequate ACPI DSDT Replacement Patch Table and a sophisticated SSDT-X299.aml. Both requirements have been originally successfully implemented for the ASUS Prime X299 Deluxe by our gorgeous @apfelnico with partial contributions of @TheOfficialGypsy. Many thanks for the extensive efforts and extremely fruitful and brilliant work! I now adopted the ACPI DSDT Replacement Patches and the SSDT-X299.aml in concordance with SMBIOS iMacPro1,1. The updated ACPI DSDT Replacement Patches are already part of the config.plist contained in EFI-X299-10.13.4-Release-iMacPro1,1-310318.zip. The new SSDT-X299-iMacPro.aml is attached at the bottom of this originating post/guide. Note that both ACPI DSDT Replacement Patches and SSDT-X299-iMacPro.aml can be build and PCIe slot population dependend and have to be verified and likely 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 I will use in the following the PCIe Slot nomenclature depicted below: The verification and likely adaptation/modification can be performed by the help of IORegistryExplorer v1.2. How to adopted or modify the ACPI DSDT Replacement Patches and SSDT-X299-iMacPro.aml is detailed in post #225 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 PCI Device implementation by means of a minimalistic starter SSDT-X299-iMacPro.aml, which just contains the Definition Block and Device Implementation for one single specific device. Once this PCI device has been successfully implemented, other PCI Device definitions can be added to the SSDT-X299-iMacPro.aml. In case that subsequently the implementation of a specific PCI Device would be erroneous and fail, also all other already successfully implemented PCI devices would disappear from Section "PCI" of Apple's System report and the entire "PCI" Device implementation would fail. Thus a stepwise PCI device implementation/adaptation is highly recommended and sometimes deemed necessary! 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 Replacement Patches and SSDT-X299-iMacPro.aml implementation detailed below requires SMBIOS iMacPro1,1. E.9.1) ACPI DSDT Replacement Implementation Note that all required ACPI DSDT Patches are already implemented in the config.plist in the /EFI/CLOVER/ directory of the EFI-Folder contained in EFI-X299-10.13.4-Release-iMacPro1,1-310318.zip. However, by default they are disabled, thus we will now open the config.plist in the /EFI/CLOVER/ directory of your 10.13 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 CAVS -> HDEF DSDT replacement patch is audio related and has the aim to achieve the SMBIOS iMacPro1,1specific HDEF onboard audio controller implementation. If not already enabled in Section E.3), please enable this DSDT replacement patch now independent from your mainboard. Comment: Find*[Hex] Replace [Hex] CAVS -> HDEF 43415653 48444546 b.) 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 c.) SL05 -> GFX0 is a graphics related ACPI DSDT replacement patch to achieve consistency with the SMBIOSiMacPro1,1 variable naming. This ACPI DSDT replacement patch is not mainboard but slot specific! All mainboard users with their GPU in PCIe Slot 1 can now enable this ACPI DSDT replacement patch. Comment: Find*[Hex] Replace [Hex] SL05 -> GFX0 534c3035 47465830 All mainboard users with their GPU in a PCIe Slot different from one have to adopt the patch previously. E.g. with a GPU in PCIe Slot 4, the ACPI DSDT replacement patch looks the following. Comment: Find*[Hex] Replace [Hex] SL01 -> GFX0 534c3031 47465830 Users with two GPUs in PCIe Slot 1 and 4 might use the following ACPI DSDT replacement patches Comment: Find*[Hex] Replace [Hex] SL05 -> GFX0 534c3035 47465830 SL01 -> GFX1 534c3031 47465831 Note that the respective ACPI DSDT replacement patch(es) are not GPU brand specific. However, the SSDT-X299-iMacPro.aml, which will be addressed in detail in Section E.9.2) below, can have GPU brand dependent device definitions and can also be sensitive with respect to the GPU PCIe population. d.) 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-X299-iMacPro.aml. 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. The respective SSDT-X299-iMacPro.aml implementations will be discussed in Section E.10.2) below. Note that in addition to the OSI -> XOSI DSDT Replacement Patch, one needs to add the SSDT-XOSI.aml in the /EFI/Clover/ACPI/pathed directory of the System Disk EFI-Folder. ii.) On the Asus X299 Prime Deluxe 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 e.) GBE1 -> ETH0 and D0A4 -> ETH1 are ASUS Prime X299 Deluxe specific LAN related ACPI DSDT replacement patches to achieve consistency with the MAC variable naming. All ASUS Prime X299 users can now enable the respective ACPI DSDT replacement patches. Note that the ETH0 and ETH1 implementations in the SSDT-X299-iMacPro.aml addressed in Section E.9.2.) are of cosmetic nature. All users of mainboards different from the ASUS Prime X299 Deluxe have to find their mainboard-specific LAN-entries in the IOREG and replace the "GBE1" and "D0A4" ACPI DSDT Replacement Patches and SSDT-X299-iMacPro.aml implementations depending on the mainboard in use. Alternatively, the GBE1 -> ETH0 and D0A4 -> ETH1 ACPI DSDT replacement patches can als maintain disabled. Comment: Find*[Hex] Replace [Hex] GBE1 -> ETH0 47424531 45544830 D0A4 -> ETH1 44304134 45544831 f.) 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'. 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 g.) The PMC1 -> PMCR ACPI DSDT patch replacement is Power Management Controller (PMC) related and applied forconsistency with the PMC naming on real Macs. Please enable now this ACPI DSDT replacement patch independent from your mainboard. Comment: Find*[Hex] Replace [Hex] PMC1 -> PMCR 504d4331 504d4352 h.) 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, the LPCB functionality will be disabled within the SSDT-X299-iMacPro.aml. Please enable now this ACPI DSDT replacement patch independent from your mainboard. Comment: Find*[Hex] Replace [Hex] LPC0 -> LPCB 4c504330 4c504342 i.) The SMBS._ADR -> XSBU.XADR Replacement renames SMBS for 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 j.) 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 k.) SLOC -> ARPT is an Airport related ACPI DSDT replacement patch, which I additionally introduced for consistencywith the variable naming on a real Mac when using an OSX WIFI Broadcom BCM94360CD 802.11 a/b/g/n/ac + Bluetooth 4.0 PCIe Adapter on the ASUS Prime X299 Deluxe in PCIe Slot 3. The respective SSDT-X299-iMacPro.aml implementations will be addressed in Section E.9.2). All ASUS Prime X299 Deluxe and OSX WIFI Broadcom BCM94360CD 802.11 a/b/g/n/ac + Bluetooth 4.0 users with the PCIe Adapter in PCIe Slot 3 can now enable the respective ACPI DSDT Replacement patch. Comment: Find*[Hex] Replace [Hex] SLOC -> ARPT 534c3043 41525054 All OSX WIFI Broadcom BCM94360CD 802.11 a/b/g/n/ac + Bluetooth 4.0 users of different mainboards or with the PCIe Adapter in a PCIe Slot different from 3 have to primarily verify and likely adopt/modify the SLOC -> ARPT in concordance with the IOREG entries for their specific mainboard and build or slot population. Users without the OSX WIFI Broadcom BCM94360CD 802.11 a/b/g/n/ac + Bluetooth 4.0 PCIe Adapter can simply leave this ACPI DSDT replacement patch disabled. Users of a WIFI and Bluetooth Adapter different from the OSX WIFI Broadcom BCM94360CD 802.11 a/b/g/n/ac + Bluetooth 4.0 can enable this ACPI DSDT replacement patch but might have to adopt the SSDT-X299-iMacPro.aml device implementation discussed in Section E9.2 below. l.) 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 E.9.2) SSDT-X299-iMacPro.aml PCI Implementation For the proper PCI device driver implementation (detailed in the Figure above), which is mostly directly related with the PCI device functionality, we now have to revise and likely adopt or modify the attached SSDT-X299-iMacPro.aml to our specific build and system configuration with the help of the IORegistryExplorer. Note that for each device, the SSDT-X299-iMacPro.aml 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 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 drivers is recommended! E.9.2.1) - HDEF - onboard PCI Audio Controller PCI Implementation: DefintionBlock entry: External (_SB_.PCI0.HDEF, DeviceObj) // (from opcode) PCI Device Implementation: Scope (\_SB.PCI0.HDEF) { Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x16) { "AAPL,slot-name", Buffer (0x09) { "Built In" }, "model", Buffer (0x1C) { "Realtek ALC S1220A HD Audio" }, "name", Buffer (0x27) { "Realtek ALC S1220A HD Audio Controller" }, "hda-gfx", Buffer (0x0A) { "onboard-1" }, "device_type", Buffer (0x14) { "HD-Audio-Controller" }, "device-id", Buffer (0x04) { 0xF0, 0xA2, 0x00, 0x00 }, "compatible", Buffer (0x0D) { "pci8086,0C0C" }, "MaximumBootBeepVolume", Buffer (One) { 0xEE }, "MaximumBootBeepVolumeAlt", Buffer (One) { 0xEE }, "layout-id", Buffer (0x04) { 0x07, 0x00, 0x00, 0x00 }, "PinConfigurations", Buffer (Zero) {} }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } The HDEF PCI device implementation is valid for the ASUS Prime X299 Deluxe and likely for all other mainboards with the Realtek ALC S1220A Audio Controller chipset. It is a build-in device and does not have any slot specific dependency. In any case verify device path "PCI0.HDEF" and PCI device implementations by means of IOREG. E.9.2.2) - GFX0, HDAU - Nvidia Graphics Card and HDMI/DP Audio PCI implementation DefintionBlock entry: External (_SB_.PC02.BR2A, DeviceObj) // (from opcode) External (_SB_.PC02.BR2A.GFX0, DeviceObj) // (from opcode) External (GFX0, DeviceObj) // (from opcode) PCI Device Implementation: Scope (_SB.PC02.BR2A) { Scope (GFX0) { OperationRegion (PCIS, PCI_Config, Zero, 0x0100) Field (PCIS, AnyAcc, NoLock, Preserve) { PVID, 16, PDID, 16 } Method (_PRW, 0, NotSerialized) // _PRW: Power Resources for Wake { Return (GPRW (0x69, 0x04)) } Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x14) { "built-in", Buffer (One) { 0x00 }, "device-id", Buffer (0x04) { 0x06, 0x1B, 0x00, 0x00 }, "hda-gfx", Buffer (0x0A) { "onboard-2" }, "AAPL,slot-name", Buffer (0x07) { "Slot-1" }, "@0,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@1,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@2,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@3,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@4,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@5,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Device (HDAU) { Name (_ADR, One) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x0C) { "built-in", Buffer (One) { 0x00 }, "device-id", Buffer (0x04) { 0xEF, 0x10, 0x00, 0x00 }, "AAPL,slot-name", Buffer (0x07) { "Slot-1" }, "device_type", Buffer (0x16) { "Multimedia Controller" }, "name", Buffer (0x1D) { "NVIDIA High Definition Audio" }, "hda-gfx", Buffer (0x0A) { "onboard-2" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } } The actual 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, or with an Nvidia graphics card in a PCIe slot different from PCIe Slot 1, will have to adopt the respective device path entries PC02.BR2A, PCIe Slot definitions and PCI device properties following their respective IOREG entries. Below one finds an example of @apfelnico for a GFX and HDAU PCI implementation of 2x Radeon Vega 64 in PCIe Slot 1 and 4. Note that for such implementation also requires an additional DSDT Replacement patch, namely: SL01->GFX1 534c3031 47465831 DefintionBlock entry: External (_SB_.PC02.BR2A, DeviceObj) // (from opcode) External (_SB_.PC02.BR2A.SL05, DeviceObj) // (from opcode) External (_SB_.PC01.BR1A, DeviceObj) // (from opcode) External (_SB_.PC01.BR1A.SL01, DeviceObj) // (from opcode) PCI Device Implementation: Scope (\_SB.PC02.BR2A.GFX0) { OperationRegion (PCIS, PCI_Config, Zero, 0x0100) Field (PCIS, AnyAcc, NoLock, Preserve) { PVID, 16, PDID, 16 } Method (_PRW, 0, NotSerialized) // _PRW: Power Resources for Wake { Return (GPRW (0x69, 0x04)) } Device (GFXA) { Name (_ADR, Zero) // _ADR: Address Device (GFX0) { Name (_ADR, Zero) // _ADR: Address OperationRegion (PCIB, PCI_Config, Zero, 0x0100) Field (PCIB, AnyAcc, NoLock, Preserve) { Offset (0x10), BAR0, 32, BAR1, 32, BAR2, 64, BAR4, 32, BAR5, 32 } Method (_INI, 0, NotSerialized) // _INI: Initialize { If (LEqual (BAR5, Zero)) { Store (BAR2, Local0) } Else { Store (BAR5, Local0) } OperationRegion (GREG, SystemMemory, And (Local0, 0xFFFFFFF0), 0x8000) Field (GREG, AnyAcc, NoLock, Preserve) { Offset (0x6800), GENA, 32, GCTL, 32, LTBC, 32, Offset (0x6810), PSBL, 32, SSBL, 32, PTCH, 32, PSBH, 32, SSBH, 32, Offset (0x6848), FCTL, 32, Offset (0x6EF8), MUMD, 32 } Store (Zero, FCTL) Store (Zero, PSBH) Store (Zero, SSBH) Store (Zero, LTBC) Store (One, GENA) Store (Zero, MUMD) } Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x16) { "AAPL,slot-name", Buffer (0x07) { "Slot-1" }, "CFG,CFG_USE_AGDC", Buffer (One) { 0x00 }, "PP,PP_DisableAutoWattman", Buffer (One) { 0x00 }, "ATY,Part#", Buffer (0x0C) { "113-3E366DU" }, "@0,AAPL,boot-display", Buffer (One) { 0x00 }, "@0,name", Buffer (0x0D) { "ATY,Kamarang" }, "@1,name", Buffer (0x0D) { "ATY,Kamarang" }, "@2,name", Buffer (0x0D) { "ATY,Kamarang" }, "@3,name", Buffer (0x0D) { "ATY,Kamarang" }, "model", Buffer (0x13) { "AMD Radeon Vega 64" }, "hda-gfx", Buffer (0x0A) { "onboard-2" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Device (HDAU) { Name (_ADR, One) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x0C) { "built-in", Buffer (One) { 0x00 }, "AAPL,slot-name", Buffer (0x07) { "Slot-1" }, "layout-id", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "name", Buffer (0x0D) { "AMD HD-Audio" }, "model", Buffer (0x0D) { "AMD HD-Audio" }, "hda-gfx", Buffer (0x0A) { "onboard-2" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } } } Scope (\_SB.PC01.BR1A.GFX1) { OperationRegion (PCIS, PCI_Config, Zero, 0x0100) Field (PCIS, AnyAcc, NoLock, Preserve) { PVID, 16, PDID, 16 } Method (_PRW, 0, NotSerialized) // _PRW: Power Resources for Wake { Return (GPRW (0x69, 0x04)) } Device (GFXB) { Name (_ADR, Zero) // _ADR: Address Device (GFX1) { Name (_ADR, Zero) // _ADR: Address OperationRegion (PCIB, PCI_Config, Zero, 0x0100) Field (PCIB, AnyAcc, NoLock, Preserve) { Offset (0x10), BAR0, 32, BAR1, 32, BAR2, 64, BAR4, 32, BAR5, 32 } Method (_INI, 0, NotSerialized) // _INI: Initialize { If (LEqual (BAR5, Zero)) { Store (BAR2, Local0) } Else { Store (BAR5, Local0) } OperationRegion (GREG, SystemMemory, And (Local0, 0xFFFFFFF0), 0x8000) Field (GREG, AnyAcc, NoLock, Preserve) { Offset (0x6800), GENA, 32, GCTL, 32, LTBC, 32, Offset (0x6810), PSBL, 32, SSBL, 32, PTCH, 32, PSBH, 32, SSBH, 32, Offset (0x6848), FCTL, 32, Offset (0x6EF8), MUMD, 32 } Store (Zero, FCTL) Store (Zero, PSBH) Store (Zero, SSBH) Store (Zero, LTBC) Store (One, GENA) Store (Zero, MUMD) } Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x16) { "AAPL,slot-name", Buffer (0x07) { "Slot-4" }, "CFG,CFG_USE_AGDC", Buffer (One) { 0x00 }, "PP,PP_DisableAutoWattman", Buffer (One) { 0x00 }, "ATY,Part#", Buffer (0x0C) { "113-3E366DU" }, "@0,AAPL,boot-display", Buffer (One) { 0x00 }, "@0,name", Buffer (0x0D) { "ATY,Kamarang" }, "@1,name", Buffer (0x0D) { "ATY,Kamarang" }, "@2,name", Buffer (0x0D) { "ATY,Kamarang" }, "@3,name", Buffer (0x0D) { "ATY,Kamarang" }, "model", Buffer (0x13) { "AMD Radeon Vega 64" }, "hda-gfx", Buffer (0x0A) { "onboard-2" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Device (HDAU) { Name (_ADR, One) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x0C) { "built-in", Buffer (One) { 0x00 }, "AAPL,slot-name", Buffer (0x07) { "Slot-3" }, "layout-id", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "name", Buffer (0x0D) { "AMD HD-Audio" }, "model", Buffer (0x0D) { "AMD HD-Audio" }, "hda-gfx", Buffer (0x0A) { "onboard-2" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } } } Note that with 10.13.4, Apple changed the com.apple.driver.AppleHDAController implementation. To make the HDAU PCI device driver work, one needs to add the following KextToPatch entry in Section "Kernel and kext Patches" of Clover Configurator, as already implemented in the config.plist contained in EFI-X299-10.13.4-Release-iMacPro1,1-310318: Name* Find* [HEX] Replace* [HEX] Comment com.apple.driver.AppleHDAController DE100B0E DE10EF10 FredWst DP/HDMI patch Credits to @FreedWst and thanks to@fabiosunfor pointing me to this solution. E.9.2.3) - PMCR - onboard Power Management Controller (PMC) PCI Implementation: DefintionBlock entry: External (_SB_.PCI0.PMCR, DeviceObj) // (from opcode) PCI Device Implementation: Scope (\_SB.PCI0.PMCR) { Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x0E) { "AAPL,slot-name", Buffer (0x09) { "Built In" }, "model", Buffer (0x1E) { "Intel X299 Series Chipset PMC" }, "name", Buffer (0x0A) { "Intel PMC" }, "device-id", Buffer (0x04) { 0xA1, 0xA2, 0x00, 0x00 }, "device_type", Buffer (0x0F) { "PMC-Controller" }, "built-in", Buffer (One) { 0x00 }, "compatible", Buffer (0x0D) { "pci8086,a2a1" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } The PMCR PCI device implementation should be valid for all X299 mainboards and should not require any build specific adaptation/modification. In any case verify device path "PCI0.PMCR" and PCI device implementations by means of IOREG. E.9.2.4) - USBX: PCI Device Implementation: Device (_SB.USBX) { Name (_ADR, Zero) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LNot (Arg2)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x08) { "kUSBSleepPortCurrentLimit", 0x0834, "kUSBSleepPowerSupply", 0x13EC, "kUSBWakePortCurrentLimit", 0x0834, "kUSBWakePowerSupply", 0x13EC }) } } 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 USBX PCI device implementation fixes this errors. E.9.2.5) - XHCI - onboard Extended Host Controller Interface (XHCI) PCI Implementation: DefintionBlock entry: External (_SB_.PCI0.XHCI, DeviceObj) // (from opcode) PCI Device Implementation: Scope (\_SB.PCI0.XHCI) { Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x1B) { "AAPL,slot-name", Buffer (0x09) { "Built In" }, "built-in", Buffer (One) { 0x00 }, "device-id", Buffer (0x04) { 0xAF, 0xA2, 0x00, 0x00 }, "name", Buffer (0x34) { "ASMedia / Intel X299 Series Chipset XHCI Controller" }, "model", Buffer (0x34) { "ASMedia ASM1074 / Intel X299 Series Chipset USB 3.0" }, "AAPL,current-available", 0x0834, "AAPL,current-extra", 0x0A8C, "AAPL,current-in-sleep", 0x0A8C, "AAPL,max-port-current-in-sleep", 0x0834, "AAPL,device-internal", Zero, "AAPL,clock-id", Buffer (One) { 0x01 }, "AAPL,root-hub-depth", 0x1A, "AAPL,XHC-clock-id", One, Buffer (One) { 0x00 } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } The XHCI USB3.0 ASMedia ASM1074 / Intel X299 Series Chipset PCI device implementation is valid for the ASUS Prime X299 Deluxe and for all other X299 mainboards with the same XHC controller chipset. Verify and adopt/modify if necessary device path "PCI0.XHCI" and PCI device implementations by means of IOREG. E.9.2.6) - XHC2,3,4 - ASMedia ASM3142 USB 3.1 Controller PCI Implementation: DefintionBlock entry: External (_SB_.PCI0.RP01.PXSX, DeviceObj) // (from opcode) External (_SB_.PCI0.RP01.XHC2, DeviceObj) // (from opcode) External (_SB_.PCI0.RP05.PXSX, DeviceObj) // (from opcode) External (_SB_.PCI0.RP05.XHC3, DeviceObj) // (from opcode) External (_SB_.PCI0.RP07.PXSX, DeviceObj) // (from opcode) External (_SB_.PCI0.RP07.XHC4, DeviceObj) // (from opcode) PCI Device Implementation: Device (\_SB.PCI0.RP01.XHC2) { Name (_ADR, Zero) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Store (Package (0x1B) { "AAPL,slot-name", Buffer (0x09) { "Built In" }, "built-in", Buffer (One) { 0x00 }, "device-id", Buffer (0x04) { 0x42, 0x21, 0x00, 0x00 }, "name", Buffer (0x17) { "ASMedia XHC Controller" }, "model", Buffer (0x2F) { "ASMedia ASM3142 #1 1x USB 3.1 Type-C Internal " }, "AAPL,current-available", 0x0834, "AAPL,current-extra", 0x0A8C, "AAPL,current-in-sleep", 0x0A8C, "AAPL,max-port-current-in-sleep", 0x0834, "AAPL,device-internal", Zero, "AAPL,clock-id", Buffer (One) { 0x01 }, "AAPL,root-hub-depth", 0x1A, "AAPL,XHC-clock-id", One, Buffer (One) { 0x00 } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Name (_SB.PCI0.RP01.PXSX._STA, Zero) // _STA: Status Device (\_SB.PCI0.RP05.XHC3) { Name (_ADR, Zero) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Store (Package (0x1B) { "AAPL,slot-name", Buffer (0x09) { "Built In" }, "built-in", Buffer (One) { 0x00 }, "device-id", Buffer (0x04) { 0x42, 0x21, 0x00, 0x00 }, "name", Buffer (0x17) { "ASMedia XHC Controller" }, "model", Buffer (0x2E) { "ASMedia ASM3142 #2 2x USB 3.1 Type-A External" }, "AAPL,current-available", 0x0834, "AAPL,current-extra", 0x0A8C, "AAPL,current-in-sleep", 0x0A8C, "AAPL,max-port-current-in-sleep", 0x0834, "AAPL,device-internal", Zero, "AAPL,clock-id", Buffer (One) { 0x01 }, "AAPL,root-hub-depth", 0x1A, "AAPL,XHC-clock-id", One, Buffer (One) { 0x00 } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Name (_SB.PCI0.RP05.PXSX._STA, Zero) // _STA: Status Device (\_SB.PCI0.RP07.XHC4) { Name (_ADR, Zero) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Store (Package (0x1B) { "AAPL,slot-name", Buffer (0x09) { "Built In" }, "built-in", Buffer (One) { 0x00 }, "device-id", Buffer (0x04) { 0x42, 0x21, 0x00, 0x00 }, "name", Buffer (0x17) { "ASMedia XHC Controller" }, "model", Buffer (0x4A) { "ASMedia ASM3142 #3 1x USB 3.1 Type-A / ASM1543 1x USB 3.1 Type-C External" }, "AAPL,current-available", 0x0834, "AAPL,current-extra", 0x0A8C, "AAPL,current-in-sleep", 0x0A8C, "AAPL,max-port-current-in-sleep", 0x0834, "AAPL,device-internal", Zero, "AAPL,clock-id", Buffer (One) { 0x01 }, "AAPL,root-hub-depth", 0x1A, "AAPL,XHC-clock-id", One, Buffer (One) { 0x00 } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Name (_SB.PCI0.RP07.PXSX._STA, Zero) // _STA: Status The XHC2,XHC3,XHC4 ASMedia ASM3142/ASM1543 USB 3.1 onboard Intel XHCI 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 that this SSDT-X299-iMacPro.aml device implementation also performs the following ACPI Replacements PCI0.RP01.PXSX -> PCI0.RP01.XHC2 PCI0.RP05.PXSX -> PCI0.RP01.XHC3 PCI0.RP07.PXSX -> PCI0.RP01.XHC4 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. E.9.2.7) - ANS2 - Apple NVMe Controller PCI Implementation: DefintionBlock entry: External (_SB_.PCI0.RP09.PXSX, DeviceObj) // (from opcode) External (_SB_.PCI0.RP09.ANS2, DeviceObj) // (from opcode) PCI Device Implementation: Device (\_SB.PCI0.RP09.ANS2) { Name (_ADR, Zero) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Store (Package (0x08) { "AAPL,slot-name", Buffer (0x09) { "Built In" }, "built-in", Buffer (One) { 0x00 }, "name", Buffer (0x14) { "AppleANS2Controller" }, "model", Buffer (0x12) { "Apple SSD AP1024M" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Name (_SB.PCI0.RP09.PXSX._STA, Zero) // _STA: Status The current ANS2 Apple NVMe Controller PCI implementation is of purely cosmetic nature and is valid for the ASUS Prime X299 Deluxe. Note that this SSDT-X299-iMacPro.aml device implementation also performs the following ACPI Replacement PCI0.RP09.PXSX -> PCI0.RP09.ANS2 in concordance with the respective SMBIOS iMacPro1,1 variable naming. Verify and adopt/modify if necessary the "PCI0.RP09.ANS2" PCI device implementations by means of IOREG. E.9.2.8) - SAT1 - Intel AHCI SATA Controller PCI Implementation: DefintionBlock entry: External (_SB_.PCI0.SAT1, DeviceObj) // (from opcode) PCI Device Implementation: Scope (\_SB.PCI0.SAT1) { Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x0C) { "AAPL,slot-name", Buffer (0x09) { "Built In" }, "built-in", Buffer (One) { 0x00 }, "name", Buffer (0x16) { "Intel AHCI Controller" }, "model", Buffer (0x1F) { "Intel X299 Series Chipset SATA" }, "device_type", Buffer (0x15) { "AHCI SATA Controller" }, "device-id", Buffer (0x04) { 0x82, 0xA2, 0x00, 0x00 } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } The SAT1 onboard Intel AHCI SATA controller PCI device implementation is valid for the ASUS Prime X299 Deluxe 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) - ETH0/ETH1 - onboard LAN Controller PCI Implementation: DefintionBlock entry: External (_SB_.PCI0.ETH0, DeviceObj) // (from opcode) External (_SB_.PCI0.RP02.ETH1, DeviceObj) // (from opcode) PCI Device Implementation: Scope (\_SB.PCI0.ETH0) { Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x10) { "AAPL,slot-name", Buffer (0x09) { "Built In" }, "built-in", Buffer (One) { 0x00 }, "name", Buffer (0x16) { "Intel I219V2 Ethernet" }, "model", Buffer (0x2A) { "Intel I219V2 PCI Express Gigabit Ethernet" }, "location", Buffer (0x02) { "1" }, "subsystem-id", Buffer (0x04) { 0x72, 0x86, 0x00, 0x00 }, "device-id", Buffer (0x04) { 0xB8, 0x15, 0x00, 0x00 }, "subsystem-vendor-id", Buffer (0x04) { 0x43, 0x10, 0x00, 0x00 } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Scope (\_SB.PCI0.RP02.ETH1) { Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x10) { "AAPL,slot-name", Buffer (0x09) { "Built In" }, "built-in", Buffer (One) { 0x00 }, "name", Buffer (0x16) { "Intel I211VA Ethernet" }, "model", Buffer (0x2A) { "Intel I211VA PCI Express Gigabit Ethernet" }, "location", Buffer (0x02) { "2" }, "subsystem-id", Buffer (0x04) { 0xF0, 0x85, 0x00, 0x00 }, "device-id", Buffer (0x04) { 0x39, 0x15, 0x00, 0x00 }, "subsystem-vendor-id", Buffer (0x04) { 0x43, 0x10, 0x00, 0x00 } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Note that the ETH0/ETH1 Intel I219V2 PCI Express Gigabit Ethernet and Intel I211VA PCI Express Gigabit Ethernet onboard LAN controller 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. E.9.2.10) - ARPT - OSX WIFI Broadcom BCM94360CD 802.11 a/b/g/n/ac + Bluetooth 4.0 AirPort Controller PCI Implementation: DefintionBlock entry: External (_SB_.PC03.BR3D.ARPT, DeviceObj) // (from opcode) PCI Device Implementation: Scope (_SB.PC03.BR3D.ARPT) { OperationRegion (PCIS, PCI_Config, Zero, 0x0100) Field (PCIS, AnyAcc, NoLock, Preserve) { PVID, 16, PDID, 16 } Method (_PRW, 0, NotSerialized) // _PRW: Power Resources for Wake { Return (GPRW (0x69, 0x04)) } Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x0E) { "built-in", Buffer (One) { 0x00 }, "device-id", Buffer (0x04) { 0xA0, 0x43, 0x00, 0x00 }, "AAPL,slot-name", Buffer (0x07) { "Slot-3" }, "device_type", Buffer (0x13) { "AirPort Controller" }, "model", Buffer (0x4A) { "OSX WIFI Broadcom BCM94360CD 802.11 a/b/g/n/ac + Bluetooth 4.0 Controller" }, "compatible", Buffer (0x0D) { "pci14e4,43a0" }, "name", Buffer (0x10) { "AirPort Extreme" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } The ARPT 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. Users of this PCIe Adapter within a PCIe slot population different from PCIe Slot 3 have to adapt/modify the respective device path "PC03.BR3D.ARPT" and likely also the respective ACPI DSDT Replacement Patch. Users of the Asus Prime X299 Deluxe onboard Bluetooth chipset controller or with a completely different WIFI/Bluetooth configuration have to either adopt the entire Airport PCI implementation by means of IOREG or can also skip the entire part. E.9.2.11) - ThunderboltEX 3 Controller PCI Implementation: DefintionBlock entry: External (_SB_.PC01.BR1A, DeviceObj) // (from opcode) External (_SB_.PC01.BR1A.PEGP, DeviceObj) // (from opcode) External (_SB_.PC01.BR1A.SL01, DeviceObj) // (from opcode) External (_SB_.PC01.BR1A.UPSB, DeviceObj) // (from opcode) External (OSDW, MethodObj) // 0 Arguments (from opcode) External (OSYS, UnknownObj) // (from opcode) External (PEGP, DeviceObj) // (from opcode) External (SL01, DeviceObj) // (from opcode) External (UPSB, DeviceObj) // (from opcode) PCI Device Implementation: Scope (\_SB.PC01.BR1A) { Scope (SL01) { Name (_STA, Zero) // _STA: Status } Scope (PEGP) { Name (_STA, Zero) // _STA: Status } Device (UPSB) { Name (_ADR, Zero) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LNot (Arg2)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x02) { "PCI-Thunderbolt", One }) } Name (_RMV, One) // _RMV: Removal Status Device (DSB0) { Name (_ADR, Zero) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LNot (Arg2)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x02) { "PCIHotplugCapable", One }) } Device (NHI0) { Name (_ADR, Zero) // _ADR: Address Name (_STR, Unicode ("Thunderbolt")) // _STR: Description String Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x0D) { "built-in", Buffer (One) { 0x00 }, "device_type", Buffer (0x19) { "Thunderbolt 3 Controller" }, "AAPL,slot-name", Buffer (0x07) { "Slot-4" }, "model", Buffer (0x30) { "ThunderboltEX 3 Intel DSL6540 Thunderbolt 3 NHI" }, "name", Buffer (0x37) { "ThunderboltEX 3 Intel DSL6540 Thunderbolt 3 Controller" }, "power-save", One, Buffer (One) { 0x00 } }) } } } Device (DSB1) { Name (_ADR, 0x00010000) // _ADR: Address Name (_SUN, 0x04) // _SUN: Slot User Number OperationRegion (A1E0, PCI_Config, Zero, 0x40) Field (A1E0, ByteAcc, NoLock, Preserve) { AVND, 32, BMIE, 3, Offset (0x18), PRIB, 8, SECB, 8, SUBB, 8, Offset (0x1E), , 13, MABT, 1 } Method (_BBN, 0, NotSerialized) // _BBN: BIOS Bus Number { Return (SECB) } Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0F) } Method (_RMV, 0, NotSerialized) // _RMV: Removal Status { Return (Zero) } Device (UPS0) { Name (_ADR, Zero) // _ADR: Address OperationRegion (ARE0, PCI_Config, Zero, 0x04) Field (ARE0, ByteAcc, NoLock, Preserve) { AVND, 16 } Method (_RMV, 0, NotSerialized) // _RMV: Removal Status { If (OSDW ()) { Return (One) } Return (Zero) } Device (DSB0) { Name (_ADR, Zero) // _ADR: Address OperationRegion (A1E0, PCI_Config, Zero, 0x40) Field (A1E0, ByteAcc, NoLock, Preserve) { AVND, 32, BMIE, 3, Offset (0x18), PRIB, 8, SECB, 8, SUBB, 8, Offset (0x1E), , 13, MABT, 1, Offset (0x3E), , 6, SBRS, 1 } Method (_BBN, 0, NotSerialized) // _BBN: BIOS Bus Number { Return (SECB) } Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0F) } Method (_RMV, 0, NotSerialized) // _RMV: Removal Status { Return (One) } Device (DEV0) { Name (_ADR, Zero) // _ADR: Address Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0F) } Method (_RMV, 0, NotSerialized) // _RMV: Removal Status { Return (One) } } } Device (DSB1) { Name (_ADR, 0x00010000) // _ADR: Address OperationRegion (A1E0, PCI_Config, Zero, 0x40) Field (A1E0, ByteAcc, NoLock, Preserve) { AVND, 32, BMIE, 3, Offset (0x18), PRIB, 8, SECB, 8, SUBB, 8, Offset (0x1E), , 13, MABT, 1 } Method (_BBN, 0, NotSerialized) // _BBN: BIOS Bus Number { Return (SECB) } Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0F) } Method (_RMV, 0, NotSerialized) // _RMV: Removal Status { Return (One) } Device (DEV0) { Name (_ADR, Zero) // _ADR: Address Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0F) } Method (_RMV, 0, NotSerialized) // _RMV: Removal Status { Return (One) } } } Device (DSB2) { Name (_ADR, 0x00020000) // _ADR: Address OperationRegion (A1E0, PCI_Config, Zero, 0x40) Field (A1E0, ByteAcc, NoLock, Preserve) { AVND, 32, BMIE, 3, Offset (0x18), PRIB, 8, SECB, 8, SUBB, 8, Offset (0x1E), , 13, MABT, 1 } Method (_BBN, 0, NotSerialized) // _BBN: BIOS Bus Number { Return (SECB) } Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0F) } Method (_RMV, 0, NotSerialized) // _RMV: Removal Status { Return (One) } Device (DEV0) { Name (_ADR, Zero) // _ADR: Address Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0F) } Method (_RMV, 0, NotSerialized) // _RMV: Removal Status { Return (One) } } } Device (DSB3) { Name (_ADR, 0x00030000) // _ADR: Address OperationRegion (A1E0, PCI_Config, Zero, 0x40) Field (A1E0, ByteAcc, NoLock, Preserve) { AVND, 32, BMIE, 3, Offset (0x18), PRIB, 8, SECB, 8, SUBB, 8, Offset (0x1E), , 13, MABT, 1 } Method (_BBN, 0, NotSerialized) // _BBN: BIOS Bus Number { Return (SECB) } Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0F) } Method (_RMV, 0, NotSerialized) // _RMV: Removal Status { Return (One) } Device (DEV0) { Name (_ADR, Zero) // _ADR: Address Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0F) } Method (_RMV, 0, NotSerialized) // _RMV: Removal Status { Return (One) } } } Device (DSB4) { Name (_ADR, 0x00040000) // _ADR: Address OperationRegion (A1E0, PCI_Config, Zero, 0x40) Field (A1E0, ByteAcc, NoLock, Preserve) { AVND, 32, BMIE, 3, Offset (0x18), PRIB, 8, SECB, 8, SUBB, 8, Offset (0x1E), , 13, MABT, 1 } Method (_BBN, 0, NotSerialized) // _BBN: BIOS Bus Number { Return (SECB) } Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0F) } Method (_RMV, 0, NotSerialized) // _RMV: Removal Status { Return (One) } Device (DEV0) { Name (_ADR, Zero) // _ADR: Address Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0F) } Method (_RMV, 0, NotSerialized) // _RMV: Removal Status { Return (One) } } } Device (DSB5) { Name (_ADR, 0x00050000) // _ADR: Address OperationRegion (A1E0, PCI_Config, Zero, 0x40) Field (A1E0, ByteAcc, NoLock, Preserve) { AVND, 32, BMIE, 3, Offset (0x18), PRIB, 8, SECB, 8, SUBB, 8, Offset (0x1E), , 13, MABT, 1 } Method (_BBN, 0, NotSerialized) // _BBN: BIOS Bus Number { Return (SECB) } Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0F) } Method (_RMV, 0, NotSerialized) // _RMV: Removal Status { Return (One) } Device (DEV0) { Name (_ADR, Zero) // _ADR: Address Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0F) } Method (_RMV, 0, NotSerialized) // _RMV: Removal Status { Return (One) } } } } } Device (DSB2) { Name (_ADR, 0x00020000) // _ADR: Address Device (XHC5) { Name (_ADR, Zero) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x12) { "built-in", Buffer (One) { 0x00 }, "AAPL,slot-name", Buffer (0x07) { "Slot-4" }, "model", Buffer (0x41) { "ThunderboltEX 3 Texas Instruments TPS65982 USB 3.1 Type-A/Type-C" }, "name", Buffer (0x31) { "ThunderboltEX 3 Texas Instruments XHC Controller" }, "device_type", Buffer (0x13) { "USB 3.1 Controller" }, "device-id", Buffer (0x04) { 0xB6, 0x15, 0x00, 0x00 }, "USBBusNumber", Zero, "UsbCompanionControllerPresent", One, "AAPL,XHCI-clock-id", One }) } Device (RHUB) { Name (_ADR, Zero) // _ADR: Address Device (SSP1) { Name (_ADR, One) // _ADR: Address Name (_UPC, Package (0x04) // _UPC: USB Port Capabilities { 0xFF, 0x09, Zero, Zero }) Name (_PLD, Package (0x01) // _PLD: Physical Location of Device { Buffer (0x10) { /* 0000 */ 0x81, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0008 */ 0x31, 0x1C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 } }) Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x02) { "UsbCPortNumber", One }) } } Device (SSP2) { Name (_ADR, 0x02) // _ADR: Address Name (_UPC, Package (0x04) // _UPC: USB Port Capabilities { 0xFF, 0x09, Zero, Zero }) Name (_PLD, Package (0x01) // _PLD: Physical Location of Device { Buffer (0x10) { /* 0000 */ 0x81, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0008 */ 0x31, 0x1C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 } }) Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x02) { "UsbCPortNumber", 0x02 }) } } Device (HS01) { Name (_ADR, 0x03) // _ADR: Address Name (_UPC, Package (0x04) // _UPC: USB Port Capabilities { 0xFF, 0x09, Zero, Zero }) Name (_PLD, Package (0x01) // _PLD: Physical Location of Device { Buffer (0x10) { /* 0000 */ 0x81, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0008 */ 0x31, 0x1C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 } }) } Device (HS02) { Name (_ADR, 0x04) // _ADR: Address Name (_UPC, Package (0x04) // _UPC: USB Port Capabilities { 0xFF, 0x09, Zero, Zero }) Name (_PLD, Package (0x01) // _PLD: Physical Location of Device { Buffer (0x10) { /* 0000 */ 0x81, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0008 */ 0x31, 0x1C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 } }) } } } } Device (DSB3) { Name (_ADR, 0x00030000) // _ADR: Address } Device (DSB4) { Name (_ADR, 0x00040000) // _ADR: Address } } } This sophisticated ThunderboltEX 3 PCI device driver implementation (thanks for the contributions of @apfelnico, @Mork vom Ork, @Matthew82 and @borysbass) provides full TB XHC USB and TB hot plug functionality for the TBEX 3 PCIe Adapter in PCIe Slot 4. Users of this PCIe Adapter within a PCIe slot population different from PCIe Slot 4 have to adapt/modify the respective ACPI path entries "PC01", "BR1A" and respective SL01 -> PEGP and PEGP -> UPSB ACPI Replacements, directly performed within the SSDT-X299-iMacPro.aml. Users of TB PCIe Adapters different from the ASUS TBEX 3 or users without any TB PCIe Adapter, have to either adopt the entire TB PCI implementation by means of IOREG or can simply skip the entire part. Finally note that for full TB XHC hot plug functionality one also has to consider and implement Error Prevention C.14), as already implemented in the config.plist contained EFI-X299-10.13.4-Release-iMacPro1,1-310318.zip. E.9.2.12) - DTGP Method: Method (DTGP, 5, NotSerialized) { If (LEqual (Arg0, ToUUID ("a0b5b7c6-1318-441c-b0c9-fe695eaf949b"))) { If (LEqual (Arg1, One)) { If (LEqual (Arg2, Zero)) { Store (Buffer (One) { 0x03 }, Arg4) Return (One) } If (LEqual (Arg2, One)) { Return (One) } } } Store (Buffer (One) { 0x00 }, Arg4) Return (Zero) } } The DTG Method Implementation is required for SSDT functionality and has not to be modified or adopted in any case. E.10) System Overview CPU Cosmetics As our Skylake-X CPU at present will not be properly recognised by OS X, Apple's System Overview ("About This Mac") reveals incomplete or simply wrong CPU details. Many times CPU's like the i9-7980XE are implemented as "unknown"... I recently discovered on InsanelyMac a sophisticated fix of pure cosmetic nature developed by Shaneee (also thanks to fabiosun for pointing me to this direction), which allows to implement those CPU details you want to be implemented. For the sake of simplicity, I summarise the necessary steps once more below. Note that the following example is only valid for systems with English as main system language. If your system language is German, French, Spanish, Chinese etc., substitute "English.lproj" in the individual commands by the "lproj" of your System language! Thanks to @PedroJSkywalker for this latter important advice! 1.) Open a terminal and use the following commands: cp /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/Resources/English.lproj/AppleSystemInfo.strings ~/Desktop/ sudo mv /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/Resources/English.lproj/AppleSystemInfo.strings /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/Resources/English.lproj/AppleSystemInfo.strings-Backup 2.) Open "AppleSystemInfo.strings" on your Desktop with TextWrangler and change <key>UnknownCPUKind</key> <string>Unknown</string> to what ever you want. In my case I choose: <key>UnknownCPUKind</key> <string>4,5 GHz 18-core 36-thread Skylake-X i9-7980XE</string> Save "AppleSystemInfo.strings" 3.) Run the following terminal commands: sudo codesign -f -s - ~/Desktop/AppleSystemInfo.strings sudo cp ~/Desktop/AppleSystemInfo.strings /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/Resources/English.lproj/ and reboot your system. 4.) Open your config.plist with Clover Configurator and in Section "CPU" set "Type" to "Unknown". Save the config.plist and reboot. 5.) Apple's System Overview now will reveal the following details: As fall back option enter the following terminal commands: sudo rm /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/Resources/English.lproj/AppleSystemInfo.strings sudo mv /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/Resources/English.lproj/AppleSystemInfo.strings-Backup /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/Resources/English.lproj/AppleSystemInfo.string and reboot. E.11) ASUS Boot Splash Screen Cosmetics Based on the ideas and instructions of @Matthew82 from InsanelyMac, I achieved an iMacPro ASUS Boot Splash Screen by means of the following procedure: 1.) Installation of the BREW distribution: a.) Open a terminal and change to "bash" shell. bash b.) Now enter the following "bash" terminal command and follow the standard BREW installation instructions: /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" 2.) After the successful installation of the BREW distribution, we have to implement the QT5 distribution, again by using a "bash" terminal shell. Just enter the following "bash" terminal commands: brew install qt5 brew link qt5 --force 3.) After successfully implementing BREW and QT5, we can now download the most actual CodeRush UEFIPatch distribution from Github to our home directory with the following terminal command: git clone https://github.com/LongSoft/UEFITool 4.) Now compile the UEFI Tool distribution with the following terminal commands: cd /UEFITools/ qmake uefitool.pro make 5.) Download and unzip iMacPro.raw to your Desktop. 6.) Now launch by UEFITool by clicking on the newly compiled UEFITool.app in the UEFITools Folder in your home directory. a.) Select "File" -> "Open image file" and load your patched or unpatched BIOS Firmware distribution. Select "Search.." in the UEFITool "Edit" Menu and perform a "GUID" search of "7BB28B99-61BB-11D5-9A5D-0090273FC14D" with "Header only"... You will receive a message "GUID pattern "7BB28B99-61BB-11D5-9A5D-0090273FC14D" found as .... in 7BB28B99-....". Double click on that message and search for the "Raw section" accompanying the "7BB28B99-...." entry, which indeed is the Boot Image, which you can easily verify by extracting the raw section body (right-click on "Raw section" and select "Extract body") to your Desktop and by subsequently opening the extracted raw-file directly with Apple's "Preview.app" (right-click an the raw file and select "Open with.." -> Preview.app). b.) To exchange the default original ASUS Boot Logo image file stored in "Raw Section" by the iMacPro.raw image file that you previously downloaded to your Desktop, right-click again on "Raw section", select this time "Replace body" and select the iMacPro.raw image file on your Desktop. Note that the actual image dimension of iMacPro.raw (2131pix x 1457pix) was adopted for its use on my 38" LG 38UC99. For monitors with reduce screen resolution, iMacPro.raw might have to be adopted to an image dimension that suites your particular screen resolution, before its upload to "Raw section". If the Boot Logo image dimension is too big for your Monitor's screen resolution, you might just end up with a black screen during the BIOS initialisation at boot. To do so, select in the Preview.app Menu -> "Tools" -> "Adjust Size". Change the image dimension and save the modified image with "File" -> "Export". In the "Export menu" press "Save", after selecting "JPEG" under "Format" , after choosing "Desktop" as the place to store the image, and after entering the new file name, which has to end with ".jpg". Double-check by right-clicking on the resulting jpg image file and selecting "Get Info" that its file size does no exceed 200KB by far. If the latter would be the case, you would not be able to save the modified BIOS Firware file subsequently. Finally just rename your new "XXXX.jpg" file to "XXXX.raw.... I guess, that by following the procedure detailed above, it is obvious that iMacPro.raw also can be substituted by any other image of your personal choice. Just be aware that it's background colour should be black (ecstatic reason for a its nice integration within the else black ASUS BIOS Boot Screen) c.) After replacing "Raw Section" with iMacPro.raw or the XXX.raw image of your choice, save your modified BIOS Firmware File with the Option "File" -> "Save Image File..." d.) Copy your modified BIOS Firmware file to a USB3.0 Flash Drive, formatted with FAT32. e.) Reboot, enter the Mainboard BIOS and save your BIOS settings to the USB Flash Drive f.) Flash your mainboard BIOS with the modified BIOS Firmware g.) Renter the Mainboard BIOS and restore your BIOS settings from the USB Flash Drive h.) Save your restored BIOS settings with (F7) and (F10), reboot and you are done. Just don't forget to set BIOS Setting "Boot Logo Display" to "Auto", when using this new approach. Any different setting might result in a black screen during BIOS initialisation. E.12) Native Display Brightness Control / Native NightShift Functionality for Monitors with DCC/IC Support 1.) Native Display Brightness Control Many of you might miss the ability to control the display brightness with the F1/F2 keys on original Apple Keyboards, or with FN&F1/FN&F2 on non-Apple keyboards. @bensge wrote a small but genius application to do just that on any Hackintosh System and to show the native OSX brightness system UI. The App works for desktops and monitors that support DDC/CI. You have to connect your monitor to your GPU either via HDMI or DP. Note that you also have to enable DDC/CI support on your monitor to make the program work. This application automatically adds itself as a Login Item in your User Settings in System Preferences. Please carefully read all instructions on his NativeDiplayBrightness GitHub page before downloading the program. git clone https://github.com/Bensge/NativeDisplayBrightness/ cd ~/NativeDisplayBrightness/ xcodebuild The compiled NativeDisplayBrightness.app can be found in subfolder ~/NativeDisplayBrightness/build/Release To add the application as a Login Item in your User Settings in System Preferences, just double click on the App. If you're using an original Apple keyboard, this app won't work with your F1/F2 keys straight away. On non-Apple keyboards it won't work out off the box, even with FN&F1/FN&F2 as it should work . In both cases you need to additionally add two KernelToPatch entries in your config.plist in Section "Kernel and Kext Patches" of Clover Configurator: Name* Find* [Hex] Replace* [HEX] Comment com.apple.driver.AppleHIDKeyboard 30783030 30373030 33612c30 78666630 31303032 31 30783030 30373030 33612c30 78303030 37303033 61 by Wern com.apple.driver.AppleHIDKeyboard 30783030 30373030 33622c30 78666630 31303032 30 30783030 30373030 33622c30 78303030 37303033 62 by Wern 2.) Native NightShift Functionality for Monitors with DDC/IC Support To enable native NightShift functionality on the 38" LG 38UC99, one needs to download and unzip the respective Display Override Profile DisplayProductID-76fc, subsequently properly sign the file, and finally copy the file to /System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-1e6d/. The latter to steps can be done by the following terminal commands: cd ~/Downloads sudo codesign -f -s - DisplayProductID-76fc sudo cp DisplayProductID-76fc /System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-1e6d/ Subsequently you have to reboot and to newly adjust your Screen Resolution under "Display" in System Preferences. And your are done: Note that the attached Display Override Profile, does not allow a LG 38UC99 Monitor Frequency of 75Hz. Only 60Hz are supported. Many thanks to user @Ramalama for providing this approach to our community. NightShift should also work for the Acer 38" and Dell 38" Monitors. Yet @Ramalama misses the respective EDIDs. Any body with e.g. the Acer XR382CQK should immediately upload the requested information and contact @Ramalama by posting in this thread! Many thanks in advance! E.13) Logic-X and Audio Studio Software Functionality The ASUS BIOS patching, providing full read/write access for the OSX Kernel to the MSR 0xE2 register, apparently also circumvents the Intel SKZ7 bug and yet missing BIOS microcode implementations. The Xnu CPU Power Management (XCPM) is now solely handled by the OSX Kernel, which completely resolves all former Logic-X or other studio audio software implementations. The same states for all other X299 mainboards with factory-default open MSR 0xE2 register implementation. Nevertheless there is a second extremely important intrinsic LOGIC X configuration setting, which has to be adopted depending on the degree of sophistication of the studio audio hardware (Latency) in use. In the following description, I will provide the correct audio preference settings for the ASUS Prime X299 with the onboard Realtek ALC S1220A audio chip: 1.) Within Logic X go to "Preferences" -> "Audio" 2.) Under Advanced check "Show Advanced Tools" 3.) Go back to the "Audio" settings and adopt "I/O Buffer Size" from "128" to e.g. "512" or even better "1024" Samples, in case you really use the onboard Realtek ALC S1220A audio chipset. Users of more sophisticated Studio Audio Hardware with better latencies have to adopt the I/O Buffer Size accordingly to their hardware implementation. To check the now flawless functionality and performance of Logic-X, download, unzip and run the attached Logic-X test sample Test Hyperthreading Bug.logicx.zip of @DSM2. attached at the bottom of this originating post/guide. Note that the test sample sound volume output is zero, for avoiding epileptic or panic attacks at audience side... this is just a test sample to check the Logic-X functionality and performance and not a chart breaking audio sample. Start Intel Power Gadget (IPG) in parallel and play the test sample with Logic-X: You will rapidly notice that everything fully behaves as expected. The Hyperthreading-sample plays flawless at alternated CPU frequencies. All credits to @DSM2. E.14) 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 most actual iStatMenus v6.1 distribution can be assessed at https://bjango.com/mac/istatmenus/ The most 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/. Note that all compiled kext binaries are once more attached towards the bottom of this originating thread (guide). Just download and unzip HW-Sensors-IF.zip and copy all kexts to /EFI/Clover/kexts/Other/. Note that this pre-compiled binary package already implements a modified GPU Sensor kext of @Kozlek, which should also account for Polaris GPUs. Many thanks to both @interferenc and @Bjango for their awesome and extensive contributions and brilliant work! Skylake-X/X299 iStatMenus Hardware Sensor Data: Skylake-X CPU Thread Utilisation Graphs: To change from CPU core to thread utilisation monitoring, uncheck "Hide Hyper-Threading cores" in Section "CPU & GPU" of iStatMenus Preferences. Temperature unites can be adjusted between Celsius, Fahrenheit and Kelvin in Section "Sensors" of iStatMenus Preferences. F.) Benchmarking F.1) Sylake-X Intel I9-7980XE (4.8GHz) CPU Benchmarking Geekbench CPU Benchmark: Multi-Core Sore: 65.348 Single-Core Sore: 5.910 Cinebench Cpu Benchmark: 4.618 CB Compare with recent Geekbench results for the 18-core iMacPro (W2191B): Geekbench CPU Benchmark: Multi-Core Sore: 46.406 Single-Core Sore: 5.175 F.2) Gigabyte AORUS GTX 1080 Ti Waterforce EB 11GB Extreme Edition Benchmarking Geekbench OpenGl and Metal2 Benchmarks: OpenGL Sore: 229.965 Metal2 Sore: 242.393 G.) Summary and Conclusion: Already during the first individual macOS High Sierra 10.13 beta releases, Syklake-X/X299 systems reached full functionality together with flawless stability. Now with macOS High Sierra 10.13.4 (17E199), it might be the right moment to follow my build and Desktop Installation Guide to unfold the unbelievable Skylake-X/X299 potential together with macOS High Sierra 10.13 (special iMac Pro build)! I am quite optimistic that high-end builds based on extremely novel Skylake-X/X299 technology will find 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 will make X299 to a "relatively cheap" but really serious alternative to the iMac Pro's and Mac Pro's. The principal intention of this desktop guide was to demonstrate, that we are able to build and configure fully functional and relatively "low-cost" high-end systems nowadays, which go far beyond of what Apple is able to offer at present or will be ever able to offer for some reasonable pricing. A Skylake-X/X299-System, that allows 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) should make such system affordable for anybody (also home office, audio and video editing/production, etc.) and allow its perfect adaptation for the specific purpose, requirements and available budgets. It might not be necessary to outline, that current Skylake-X/X299 Systems perform absolutely stable on a 24/7/365 basis. I am a scientist, expert in solar physics, space weather forecast and related telescope/instrument/space-mission development. In the frame of my scientific research, I developed parallelized image reconstruction, spectral line inversion and numerical modeling algorithms/applications, which require tremendous parallelized calculation power, RAM memory and storage capacities to reduce, analyze and interpret extensive and pioneering scientific ground-based or space-born observational data sets. This basically was also the professional motivation for developing my innovative iMacPro macOS High Sierra Hackintosh Build iSPOR-S (the imaging Spectropolarimetric Parallel Organized Reconstruction Server running iSPOR-DP, the Imaging Spectropolarimetric Parallel Organized Reconstruction Data Pipeline software package for the GREGOR Fabry-Pérot Interferometer, located at the 1.5m GREGOR Solar Telescope (Europe's largest solar telescope) on Tenerife, Canary Islands, Spain) and for the entire respective iMac Pro Skylake-X/X299 Desktop User Guide Development, which hopefully will be also of benefit for others. Anybody interested can find more details on my personal webpage.
  2. Could someone tell me in detail what all these features are and what exactly they mean? I would be grateful. I mean Clover and its settings, especially the CPU and PCI Devices tabs. I will start with the CPU: Halt Enabler PLimitDict UnderVoltStep Double First State Generate PStates Generate CStates Enable C2 Enable C4 Enable C6 Enable C7 Use system IO C3 Latency Bus speed (KHz) QPI (MHz) Saving mode Patch APIC Then PCI Devices: USB Ovner Ship USB Injection Inject Clock ID Inject EFI Strings Just a short description of what it is and what it serves.
  3. My Original Specifications - Proccessor Intel Core 2 Duo E7500 2.93 Ghz - RAM 2 GB PC10600 DDR3 - HDD WD Blue 250 GB - DVD-R 9mm - LAN Broadcom BCM57780 NetLink Gigabit Ethernet - Codec Audio Chipset ACL269 Rev 0x0100 - OS Windows 7 Professional (OEM License) - GPU Intel GMA X4500 My Mod - RAM 4 GB (2 GB + 2 GB) PC10600 DDR3 - Replace DVD-R 9mm With HDD Caddy 9mm SATA to 9.5mm SATA (i put 500 GB WD Blue 9.5mm inside the HDD Caddy) - GPU ATI Mobility Radeon HD 5450 1 GB DDR3 - OS macOS Sierra 10.12.6 (16G1212) with SMBIOS iMac 10,1 on WD Blue 250 GB HDD (GUID) + Windows 7 Professional SP 1 (64-bit) (OEM License) on WD Blue 500 GB HDD (MBR) - Broadcom BCM4322 PCI Wireless Adapter - USB Bluetooth Dongle Tools and Softwares - USB FlashDrive 8GB - Clover OS X El Capitan-V7 by chris1111 (in some case if my attach EFI Folder is not work, you may need to install El Capitan by making USB Bootable using this tool) - Install macOS Sierra.app or Install OS X El Capitan.app from App Store (just like i said before in point 2, i downloaded both 10.13 High Sierra the latest version and 10.11 El Capitan) - For installing macOS Sierra, i am using CreateInstallMedia Command to make a USB Bootable - Clover v2.4k Rev. 4259 as Bootloader with EFI Folder in my attach (i attach 2 Folder, the first one is for USB Bootable that you can use too for Post Install without DSDT Patch for AMD5450 Graphics and the second one is for Post Intall with DSDT Patch for AMD5450 Graphics) - Kext Wizard (Optional) Tutorials 1. Format your USB FlashDrive to HFS+ with GUID Partition format and named "USB" (without quotes). Next, open Terminal and use this command "sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ Sierra.app/ --nointeraction" (without quotes). 2. Now, install Clover v2.4k Rev. 4259 and select like this : - Install Clover in the ESP - Bootloader, select Install boot0ss in MBR - CloverEFI, select CloverEFI 64-bits SATA - For theme, do not select anything because i already have a theme in my attach EFI Folder - Driver64 do not select anything like i said in Point 4 (Theme) - For Drivers64UEFI do not select anything like i said in Point 4 (Theme) 3. Copy my attach EFI Folder (USB Bootable) to your EFI Partition in USB Bootable. 4. Just boot from your USB FlashDrive and make installation like normal. I make partition like this : - WD Blue 250 GB (Internal HDD) : "Macintosh HD" (the name is optional) for OSX (if you are using SSD, you can choose APFS format or HFS+ if you are using HDD), and "Time Machine" for macOS backup. - WD Blue 500 GB (in HDD Caddy) : "BOOTCAMP" for Windows, and "Stuff" for saving any data (i choose NTFS on Stuff partition for simple cross-platform OS). 5. Again, install Clover v2.4k Rev. 4259 but now install it to your Harddrive (Macintosh HD or Macintosh SSD) and add a new option at Clover Option Installer Menu like this : - Install RC scripts on target volume - Install Clover Preference Pane (Optional, but i select this) 6. If you are using ATI Mobility Radeon HD 5000 Series in macOS High Sierra 10.13.x (just High Sierra), you need to install additional kext from macOS Sierra 10.12.6 that's i already atach too using Kext Wizard if you not do that, you will get Black Screen (it's happen when you using my EFI Folder with DSDT Patch or you using Fake Clover ID). 7. Last, mount your EFI partition of your Harddrive and Copy EFI Folder you have downloaded from my attach (Post Install with DSDT or USB Bootable without DSDT) then paste it in EFI Partition of your harddrive. 8. Reboot, and you will get QE/CI for ATI Mobility Radeon HD 5000 Series (if you are using this Graphics Card), Full Working of LAN and Audio (for Audio, just Back Panel is working.. for Front Panel is not working because it's not detected at System Preferences. Already use some Audio Inject and all Audio Ports detected but only Output port in Back Panel is working..) Fix and Patches (from Andres ZeroCross post in InsanelyMac) for dual-booting with Windows using 1 HDD 1. After install Windows with UEFI Mode then you will never boot to Clover GUI. We can't change Boot Entry via Shell Command or Bios Setup. There is no option for this. Solution is - Boot with your USB Installer, then mount EFI Partition of Your Harddrive and go to "EFI/Microsoft/Boot" and change "bootmgfw.efi" to "bootmgfw-orig.efi". - Then go to "EFI/CLOVER/" and Copy "CLOVERX64.efi" and paste at "EFI/Microsoft/Boot" then rename it to "bootmgfw.efi" - Restart and you can boot in to CLOVER GUI again Inside my /EFI/CLOVER/kexts/Other : - FakeSMC.kext - FakeSMC_CPUSensors.kext - FakeSMC_ACPISensors.kext - Lilu.kext - WhateverGreen.kext - WhateverGreen.kext.dSYM - AppleALC.kext - AppleALC.kext.dSYM - BCM5722D.kext Everything just Working Fine.. Sleep, Shutdown, Restart and iMessage+FaceTime with MLB+ROM from MBP Late 2012. for BIOS, i am not disable anything.. like Serial Port and VT-D (Intel Virtualization) but in some case maybe you need to disable one or all of them i mentioned. But for Graphics, i set manualy to PEG because i am using additional Graphics Card. Download Links EFI (USB Bootable) : https://drive.google.com/open?id=0B8iEbJG0g9wFRDZ0NmFTVFllaVk EFI (Post Install) : https://drive.google.com/open?id=0B8iEbJG0g9wFa2tPMlhNMEhDXzA Kext for fix AMD5000 Series in HS 10.13.x : https://drive.google.com/open?id=0B8iEbJG0g9wFWjNGbXM4WnNpWTg Credits to : - Allah S.W.T - Rehabman - chris1111 - Andres ZeroCross - Badruzeus Shava - Group Hackintosh Indonesia on Facebook - And others, that's i cannot mentioned your name one by one
  4. Samsung Galaxy Book 12

    Hey there ! I would like to install sierra on my Galaxy Book 12 inch!! Specs i5 7200u HD 620 1440p res SSD sata3 USB c ports WIFI ATHEROS/QUALCOMM QCA6174 Its a 2 in 1 convertible laptop! So its detachable and also i can use it with a keyboard! Can i install osx sierra or high sierra on this? Actually im tryinh to install but i get thoose errors cartellaEFI.zip
  5. --Create a bootable copy of macOS Sierra http://www.insanelymac.com/forum/files/file/559-flash-drive-maker/ --Create a bootable copy of macOS HighSierra http://diskmakerx.com/ --Install Clover in USB stick https://sourceforge.net/projects/cloverefiboot/files/Installer/ --Replace with my Clover folder CLOVER.zip --Install Sierra/High Sierra and boot into system! Post Installation --Install Clover in HDD/SSD and replace with my folder CLOVER.zip --Nvidia WebDriver Sierra http://www.insanelymac.com/forum/topic/312525-nvidia-web-driver-updates-for-macos-sierra-update-07212017/ --Nvidia WebDriver High Sierra http://www.insanelymac.com/forum/topic/324195-nvidia-web-driver-updates-for-macos-high-sierra-update-10162017/ --Cuda http://www.insanelymac.com/forum/topic/302795-cuda-90214-is-out-update-10162017/ Now you need a fine tune! --DSDT DSDT.GA H97M-D3H MaLd0n.zip Patches -FIX ERRORS AND WARNINGS -HPET -SATA -SLPB -EHCx -DARWIN -LPC -XHCI -HDEF -RTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -PNLF --Power Management Use "plugin-type"=1 in DSDT, SSDT or Clover config.plist --Brightness Install .app, select the required permission and reboot. Work in F1 / F2 keys! NativeDisplayBrightness.app.zip https://github.com/Bensge/NativeDisplayBrightness/releases *in some cases .app don't work, check patches in config.plist inside Clover folder Post Install --FakeSMC https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek/downloads/ --Audio https://github.com/vit9696/AppleALC --USB https://bitbucket.org/RehabMan/os-x-usb-inject-all/downloads --LAN http://www.insanelymac.com/forum/topic/287161-new-driver-for-realtek-rtl8111/ -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders! Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad and many, many, many others! We're all here to have fun and learn from each other! ENJOY!
  6. Hello, im looking for a graphic card for my build. I have been using integrated graphics (Intel HD 4600) of my Gigabyte Z87X-UD3H in my Mavericks. Now I have Sierra installed and I need a better graphics. I use my hackintosh for music production (Logic Pro X and Pro tools) also for video edition with Final Cut Pro X and Photoshop. I don't need a really hi-end graphic card, because I don't play games. I want a good performance working with this programs. Of course with a 100% compatibility with Sierra jajaja I have seen a lot of graphics cards, but I don't really know what kind of graphic card I need. Im not new hackintoshing, but yes with graphics cards jaja. thanks you so much for your help!
  7. Hello guys, after getting a great help by RehabMan, finally I can post my steps to use Clover UEFI with hotpatch. My laptop have the following hardware: CPU: i5-3210M Video: HD 4000 Audio: Cx20590 Wifi: AR9285 Network: Atheros AR8162 BIOS: Insyde H2O - 3.7 (5ECN90WW) All OOB, unless Card Reader (yet). My BIOS settings: Boot mode: Legacy Support - This laptop has the UEFI option too, but if I enable it, I don't have the Ethernet port working. Boot priority: UEFI First USB boot: Enabled OS Optimized Defaults: [Other OS] OS X Installation. For install OS X El Capitan, use this guide: Making a 10.10/10.11 USB Installer /w Clover (UEFI and Legacy) the correct way! Clover version: v4003 Steps. Look at RehabMan guide about 'hotpatch' for a complete info. Google for it. If you are using 'staticpatch' way, made a backup of the entire EFI/Clover first. Read more about what each Clover patch/resource do in CloverWiki or in Clover v.2 Instructions My 'Fixes' in config.plist: <key>Fixes</key> <dict> <key>AddDTGP_0001</key> <true/> <key>AddIMEI_80000</key> <true/> <key>AddPNLF_1000000</key> <true/> <key>FIX_WAK_200000</key> <true/> <key>FixAirport_4000</key> <true/> <key>FixHDA_8000</key> <true/> <key>FixHPET_0010</key> <true/> <key>FixShutdown_0004</key> <true/> My 'Patches': <key>Patches</key> <array> <dict> <key>Comment</key> <string>change EHC1 to EH01</string> <key>Disabled</key> <false/> <key>Find</key> <data> RUhDMQ== </data> <key>Replace</key> <data> RUgwMQ== </data> </dict> <dict> <key>Comment</key> <string>change EHC2 to EH02</string> <key>Disabled</key> <false/> <key>Find</key> <data> RUhDMg== </data> <key>Replace</key> <data> RUgwMg== </data> </dict> <dict> <key>Comment</key> <string>change GFX0 to IGPU</string> <key>Disabled</key> <false/> <key>Find</key> <data> R0ZYMA== </data> <key>Replace</key> <data> SUdQVQ== </data> </dict> <dict> <key>Comment</key> <string>change SAT0 to SATA</string> <key>Disabled</key> <false/> <key>Find</key> <data> U0FUMA== </data> <key>Replace</key> <data> U0FUQQ== </data> </dict> <dict> <key>Comment</key> <string>Rename _DSM to XDSM</string> <key>Disabled</key> <false/> <key>Find</key> <data> X0RTTQ== </data> <key>Replace</key> <data> WERTTQ== </data> </dict> <dict> <key>Comment</key> <string>Change _OSI to XOSI</string> <key>Disabled</key> <false/> <key>Find</key> <data> X09TSQ== </data> <key>Replace</key> <data> WE9TSQ== </data> </dict> <dict> <key>Comment</key> <string>Change Mutex(ABCD,7) to Mutex(ABCD,0)</string> <key>Disabled</key> <false/> <key>Find</key> <data> WwFBQkNEBw== </data> <key>Replace</key> <data> WwFBQkNEAA== </data> </dict> <dict> <key>Comment</key> <string>_Q12 to XQ12</string> <key>Disabled</key> <false/> <key>Find</key> <data> X1ExMgA= </data> <key>Replace</key> <data> WFExMgA= </data> </dict> <dict> <key>Comment</key> <string>_Q11 to XQ11</string> <key>Disabled</key> <false/> <key>Find</key> <data> X1ExMQA= </data> <key>Replace</key> <data> WFExMQA= </data> drivers64UEFI: The files used in Clover/ACPI/patched: Patches.zip For get WiFi working, I use the ProBookAtheros.kext provided by RehabMan. Credits: RehabMan and ahmed_ais
  8. SONY VAIO FIT macOS SIERRA 10.12.3 UNDER CONSTRUCTION AGAIN. --- Sorry guys, there have been some things missing, or had been in wrong order. Because of the extrem long guide, I removed the content temporarily. Will be fixed soon.
  9. With the purpose of running the beloved Apple Mac OS X on our Intel ASUS laptop I am writing this guide to share my experience and knowledge about this Hackintosh. This tutorial applies to running versions between 10.9 and 10.11.6, focusing specially in El Capitan. This method applies also for Sierra but at the moment my WiFi Card doesn't work well with 10.12 so I chose to remain in a stable Mac OS X I have 99% functionality: What Works : WiFi, Bluetooth, Airdrop, HandOff, FindMyMac (WiFi card has to be replaced, I put a BCM94352HMB) Full QE/CI acceleration with integrated HD4400 graphics Trackpad with 1finger, 2finger, 3finger and 4finger gestures Keyboard (Perfect with Volume, Brightness, Play/Pause, Numpad working) Battery Percentage Sleep, Shutdown and Reboot Internal Speakers, Internal Microphone, Headphone Jack, HDMI audio DVD Drive HDMI audio and video VGA out iMessage and FaceTime Recovery Partition What is not working Internal SD Card Reader When you install Clover Bootloader to your USB media or HDD you should select the following options: - Install for UEFI booting only - Install Clover in the ESP - Drivers64UEFI (Fat-64, OSxAptioFix2Drv) After installation is complete, the EFI partition we want to configure will already be mounted, so we proceed to open it and do the following Install HFSPlus.efi and NTFS.efi in drivers64UEFI folder and remove VboxHFS.efi Open the folder /EFI/Clover/kexts and delete all the folders starting by 10 and leave only the “other” folder In the above mentioned “other” folder place the kexts that I will quote next, please note that the kexts marked in red are the absolute necessary ones for booting Mac OS X installer , the rest should only be installed afterwards, after having Mac OS X installed to your hard drive and directly to /System/Library/Extensions : ACPIBatteryManager.kext AppleALC.kext ApplePS2SmartTouchpad.kext BrcmFirmwareRepo.kext BrcmPatchRAM (Mavericks) or BrcmPatchRAM2 (Yosemite or later) CodecCommander.kext DisableTurboBoostBattery.kext FakePCIID_XHCIMux.kext (Only for El Capitan) FakePCIID_IntelHDMIaudio.kext FakePCIID_BroadcomWiFI.kext (makes my BCM94352HMB work) FakePCIID_IntelHDGraphics.kext FakePCIID.kext FakeSMC, HWInfo, IntelCPUMonitor (HwSensors3 from Slice) IntelBacklight.kext RealtekRTL8111.kext USBInjectAll.kext (Only for El Capitan) After all the kexts necessary are in the correct folder, proceed to mimic my config.plist Note that the Kext patches included only work for El Capitan. If you want older version support, post here and I can help. I recommend using Clover Configurator App config.plist.zip For your SMBIOS choose MacbookPro11,2 and shake those serial numbers to really get a genuine one. In order to get everything working properly , follow these guidelines for ACPI tables patching. Firstly, press F4 at Clover GUI in order to dump the native ACPI tables. You will most probably get a crash, a red screen full of weird black numbers and strange symbols, do not worry, just force shutdown. At the next boot if you look in /EFI/Clover/ACPI/origin in your USB you should have a bunch of files. After getting MaciASL and acpica tools from RehabMan (always updated) and installing them, and adding rehabman’s laptop dsdt patch repository, which is this: https://github.com/R...ptop-DSDT-Patch I recommend patching these tables before installing Mac OS X in order to have a better user experience and better functionality as well as a cleaner and smoother install. Your computer may not even reach the installer since we have no way of disabling our discrete NVIDIA Geforce 820m without getting our hands dirty in DSDT patches. Delete all files that don’t start with DSDT or SSDT- If you have an SSDT with an x just delete it because it is dynamically loaded and so does not need our attention. Place the files in our interest in a folder and: cd /path/to/a/folder iasl -da -dl *.aml After obtaining the .dsl files you should open them and check for errors. In the latest BIOS we have the following errors: DSDT- We will find 4 errors The parse op Zero errors can be fixed by deleting all the “Zero” you find in the conflicting place The remaining two errors are fixed by applying the ADBG fix from RehabMan repo SSDT-1- We find many errors and all can be fixed by applying the patch “Remove _PSS placeholders” SSDT-12- We find an error related to a specific sector of a cryptic DOS device, we can safely delete these following lines from the SSDT Now that all our ACPI tables are nice and clean we can proceed to patching First of all, open all the tables at the same time and hit Command + F to bring up the Find Replace dialog box and Find:GFX0 and Replace it with: IGPU Find:B0D3 and Replace it with HDAU Do this in all the tables, so the renames are the same in all your tables When that is done, apply the following patches to the DSDT: Use the patch "DTGP" (you can easily find it with our friend Google ) Use the patch "Fix _WAK Arg0 v2" Use the patch "HPET Fix" Use the patch "SMBUS Fix" Use the patch "IRQ Fix" Use the patch "RTC Fix" Use the patch "OS Check Fix Windows 8” Use the patch "Add IMEI" Use the patch “7-8 Series USB” Use the patch "USB PRW 0x0D" Use the patch "Igpu Brightness Fix" Use the patch "Audio Layout id 3" When you have applied the Audio Layout Patch just Find: layout and it should show the only result, then make that part look like mine, so that you can use AppleALC for native on the fly audio If you want HDMI audio you should open SSDT-10 and find layout again and make it look like the one you just edited in DSDT, we do this because we want layout-id 29 instead of layout-id 3 For battery percentage you should use the ASUS N55SL/Vivobook patch Finally when you did all that you should follow RehabMan’s tutorial for Disabling Discrete Graphics Cards, on a web which I am not allowed to mention. This will give you much more battery life and a lot less heat. You should read it properly and you will notice there is close to no difference between his example and our laptop so it will be easier than it looks like. Make sure you also use the patch he posts to fix shutdown and sleep when our NVIDIA is disabled. After all the ACPI tables are properly patched save them all and cd /path/to/where/your/patched/tables/are Then delete all the original aml files And then iasl *.dsl After getting the resulting patched aml files, place them in /EFI/Clover/ACPI/patched for Clover to load it Place them all together in /EFI/Clover/ACPI/patched and in the ACPI section of your config.plist make sure to "Drop OEM" tables and set the "Sorted Order" as I did in the attached config.plist. Before installing Mac OS X make sure in your BIOS you have legacy mode disabled and you have secure boot and fast boot also disabled, so that Clover works well. Also make sure the controller is set to AHCI mode. Remember to use a GUID partition table on your Hard Drive and if you plan to dual boot just create two Mac OS Extended Journaled partitions, don't create any Fat partition using Disk Utility cause that will leave you unable to install Windows in UEFI mode. Post-Install Finally you will need to generate an SSDT using ssdtPRGen.sh (this can only be done when you have installed Mac OS X) https://github.com/P...ha/ssdtPRGen.sh Add it to the Sorted Order and you are done Make sure to set the hibernate mode to either 0 or 2 . ​You can copy the colour profiles from ASUS Splendid Utility and use them in Mac OS X, but for my eyes, I prefer the default LCD one This is the first fully functional Hackintosh I ever accomplished and it took me a few months of learning… I am using Mac OS X for about two or more years in this Hack and I am still in love like the very first boot hihihi This is almost the perfect HackBook and has worked since Mountain Lion until now Hope you enjoyed!
  10. First... If you need DSDT edits for SkyLake, KabyLake or CoffeeLake... -Post your full Clover folder with original tables in Origin folder(Extract with F4 in Clover boot screen) -Post Ioreg, extract with Ioreg Explorer http://www.insanelymac.com/forum/index.php?app=core&module=attach&section=attach&attach_id=222606 -Run it, post files generated in your desktop http://www.insanelymac.com/forum/index.php?app=core&module=attach&section=attach&attach_id=222609 Installation --Create a bootable copy of macOS Sierra Check out the link http://www.insanelymac.com/forum/files/file/559-flash-drive-maker/ --Create a bootable copy of macOS HighSierra Check out the link http://diskmakerx.com/ --Install Clover in USB stick https://sourceforge.net/projects/cloverefiboot/files/Installer/ --Replace with my Clover folder CLOVER.zip --Install Sierra/High Sierra and boot into system! Post Installation --Install Clover in HDD/SSD and replace with my folder CLOVER.zip --Reboot and activate video! -Nvidia WebDriver Sierra http://www.insanelymac.com/forum/topic/312525-nvidia-web-driver-updates-for-macos-sierra-update-07212017/ -Nvidia WebDriver High Sierra http://www.insanelymac.com/forum/topic/324195-nvidia-web-driver-updates-for-macos-high-sierra-update-10162017/ -Cuda http://www.insanelymac.com/forum/topic/302795-cuda-90214-is-out-update-10162017/ --DSDT My DSDT with patches for Skylake DSDT.MaLd0n ASUS Z170M PLUS.zip Patches -FIX ERRORS AND WARNINGS -HPET -SATA -SLPB -DMAC -DARWIN -LPC -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -RTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -USBX -PMCR -EC -IMEI -PNLF -HDMI --FakeSMC http://www.hwsensors.com/releases --Audio https://github.com/vit9696/AppleALC --USB https://bitbucket.org/RehabMan/os-x-usb-inject-all/downloads --LAN https://github.com/Mieze/IntelMausiEthernet -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders! Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad and many, many, many others! We're all here to have fun and learn from each other! ENJOY!
  11. No hokus pokus - No magic I am basically making this more current and simplifying it for people with HP Z800 wanting to run Sierra. With a bit more detail on the BIOS settings All credit really goes to: chatdeau, Rockey12 and ZoroZZ for helping out and creating the first topic on the HP Z series found here I am not sure who to credit for the kexts but a big THANK YOU to whoever you are! The HP Z series is very powerful and affordable computers which I simply think is a brilliant Hackintosh solution. MY HW Specification : HP Z800 with BIOS version : 3.60 CPU: x2 6-core X5690 RAM: 32 GB GFX: ATI HD5870 SSD: Samsung SSD 840 EVO 250GB What you need. - A HP Z800/600 (obviously) - A working computer running Mac OS X - A 8gb or higher USB 2.0 key - Mac OS X Sierra app - Latest CLOVER - The Attached Kexts Step one – BIOS Update Update your BIOS to the latest (currently it is 3.60 Rev.A 14 Apr 2016) Download there The easiest way is to run the flash tool on a Windows installation. Step two – BIOS settings Setup the BIOS settings with the following settings. Please keep in mind that there might be option you can turn on or off depending on your need but this is just what worked for me. Storage > Storage Options - Removal Media Boot = Enable - Legacy Diskette Write = Enable - SATA Emulation = RAID+AHCI Security > System Security - Data Execution Prevention = Enable - Virtualization (VTx) = Disable - Virtualization (VT-d2) = Disable - AES Instruction = Enable Security > Device Security (Everything to “Device Available” except these) - Serial port = Hidden - Internal USB = Hidden - SAS Controller = Hidden - Legacy Diskette = Hidden - Embedded Security = Hidden Power > OS Power Management - Runtime Power Man = Enable - MWAIT-Aware OS = Enable - Idle Power savings = Extended - ACPI S3 Hard Disk = Disable - ACPI S3 PS2 Mouse = Enable - USB Wake = Disable - Unique Sleep State = Disable Power > Hardware Power Management - SATA Power Manage = Enable - Intel Turbo Boost = Enable - Enhanced Intel Turbo Boost = Enable - EUP Compliance = Enable Advanced > Processor - Hyper-Threading = Enable - Active Cores = All Cores - Limited CPUID = Disable Advanced > Chipset/Memory - PCI SERR# Generation = Disable - PCI VGA Palette Snooping = Disable - Enhanced Memory Performance = Enable Advanced > Device Options - Num Lock = Off - S5 Wake on LAN = Enable - Multi-Processor = Enable - Internal Speaker = Disable - Monitor Tracking = Disable - NIC PXE = Disable - SATA RAID Option ROM = Enable Step tree – Create the USB Download the Mac OS Sierra installer app from the Appstore on a working computer running Mac Run Disk Utility and format the USB key as Mac OS Extended (Journaled) with GUID Partition Map. I just named the USB Key Untitled as standard Then open terminal and run this command to create the USB key sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --applicationpath /Applications/Install\ macOS\ Sierra.app Please note that this part of the command “/Volumes/Untitled” is the path to the USB key and if you have named it anything else than “Untitled” you will have to edit it with the name of your USB key. Once the command is done you have to install Clover which can be downloaded here Run the clover pkg and remember to “Change Install Location” to your usb. Then choose costumize and choose the following: - Bootloader - Install boot0af in MBR - CloverEFI - CloverEFI 64-bits SATA Once Clover is installed you will need to add the following Kexts (attached below) to the /EFI/CLOVER/kexts/10.12 folder on your USB Key. - AHCIPortInjector_v1.0.0_Micky1979.kext - FakeSMC_v6.16.1372_netkas.kext - IOAHCIBlockStorageInjector_v1.0.0_Micky1979.kext - NullCPUPowerManagement_v1.0.0d2_tgwbd.kext Step four – Boot to Installation Insert the USB key and start the computer. At the HP screen choose F9 to choose boot option. Then select USB drive When you are at the CLOVER screen you can choose options and in the boot arguments you should write use the –v bootflag to be able to see what is going on in case there is any errors. In my case I am using a ATI 5870 GPU and I don’t need to do anything as the ATI 5xxx series is supported but Mac OS X by default. If you have an Nvidia card you need to add the nv_disable=1 boot argument to avoid a black screen. Now run the installer as you would with any Mac and at the install screen you shall rund Disk Utility and format the drive you want to use as we did previously with the USB key. Mac OS Extended (Journaled) with GUID Partition Map. The installer will reboot the computer and when It starts again you need to hit F9 again select the USB key but this time at the Clover screen You need to choose your newly created Hard drive. The Installer will continue after this and boot one last time before booting in to the new system. Please note that you need to boot from the USB and choose the hard drive each time at the Clover screen. Step five – Make the OS bootable Once you are running your new OS you will need to install clover to that drive like we did previously on the USB key. Run the clover pkg and remember to “Change Install Location” to your hard drive. Then choose costumize and choose the following: - Bootloader - Install boot0af in MBR - CloverEFI - CloverEFI 64-bits SATA Once Clover is installed you will need to add these following Kexts found here to the /EFI/CLOVER/kexts/10.12 folder on you’re the OS X hard drive. If you have an Nvidia GPU you will need to install the web driver which is found here And use the nvda_drv=1 boot flag at the clover screen. You will need to add this to the config.plist ether manually or with clover configurator to avoid typing it in all the time. Enjoy your new powerful hackintosh. HP Z800 kexts Sierra.zip
  12. NOTE: This guide mixes static patch with hotpatch. It will be edited to make it works only with static patch soon. There's zero issues with this guide but it seems better not to mix patching methods (thanks, RehabMan) Hello, everybody! After two years of using my Cintiq Companion 2 with Yosemite thanks to mactabletman’s guide and reading, testing a lot and trying to understand what I was doing, I’m in a good path to share my experiences and help you to install macOS Sierra in your Companion 2 keeping your Windows installation. There are a few things that need to be solved, like sleep/wake (Cintiq goes to sleep, led blinks but display doesn’t wake up, maybe framebuffer, IOKit or PWR related) or audio using AppleHDA for codec ALC286 instead of VoodooHDA (I will add notes in each section about all this). WE HAVE GOOD NEWS, CINTIQ MODE WORKS!! (see notes at the bottom) No need to say that I’m taking zero responsibilities of what happened if you follow this guide. We are all grown people and before taking any step you better read all the info you can find about what you are trying to accomplish. This guide is done for the Cintiq Companion 2 i5-4258U 128GB model (DTHW1310L) with the last BIOS version (MB01) but can be useful as a start for other CPU/graphic models. I’m assuming you updated or reinstalled and have Windows 10 running but same procedure is required for Windows 8/8.1. WORKING: All except wake from sleep using Power Button (wake well if previously connected in Cintiq mode), PCI Realtek SD Card Reader, volume buttons and HDMI audio. So first, things you are going to need: - 2 usb drives (16GB and 32GB minimum), one for create an installer and another to install Sierra into. - 1 usb keyboard and 1 usb mouse since Clover has no support for touch devices and touch doesn't work natively in Sierra as it does in Yosemite. - 1 usb drive for Clonezilla (*optional but recommended) - 1 external hard drive to backup your whole internal SSD using Clonezilla (*optional but recommended) - An original Apple computer to create installer. - A BCM94352Z WiFi and Bluetooth 4.0 card to replace default Intel wireless card. You can check how to open your device here. * In order to create a Clonezilla Live USB, I recommend to use Yumi. You can create a multiboot installer for your Windows version, Ubuntu, Wifislax… very useful stuff. CREATING THE INSTALLER… Ok, you did a backup of your data, so let’s create a usb installer for macOS Sierra: - Download macOS Sierra from App Store, this will download the last update 10.12.1 - Open Disk Utility and format your 16GB usb to HFS+J, GUID partition and rename it to install_osx. - Copy and paste these commands in Terminal, one by one: sudo "/Applications/Install macOS Sierra.app/Contents/Resources/createinstallmedia" --volume /Volumes/install_osx --applicationpath "/Applications/Install macOS Sierra.app" --nointeraction sudo diskutil rename "Install macOS Sierra" install_osx INSTALLING CLOVER IN USB INSTALLER… Now open the Clover installer and select your Install macOS Sierra USB, click on “Customize” and use this configuration: - Check Install for UEFI booting only, Install Clover in the ESP is also automatically selected - Check embebbed theme. - Check OsxAptioFixDrv-64 from Drivers64UEFI - Check PartitionDxe-64 from Drivers64UEFI - Check EmuVariableUefi-64 from Drivers64UEFI* - Check Install RC scripts on target volume from Drivers64UEFI* - Click Install. After install Clover, a EFI partiton is mounted. Go to EFI/CLOVER, delete that config.plist and put my config_install.plist there. Rename it to config.plist. - Go to EFI/CLOVER/Drivers64UEFI and delete VboxHfs-64.efi. Put there HFSPlus.efi. - Go to EFI/CLOVER/kexts/ and leave only "10.12" and “Other” folders. Put FakeSMC.kext inside both of them. Now your installer USB is ready. *NOTES ABOUT NVRAM EmuVariableUefi-64 and Install RC scripts on target volume might be needed to make NVRAM works in a dual boot configuration since both systems read and write there (I guess). Or maybe our device has not NVRAM hardware, I don’t know. Anyway, I’ve tested it. To test NVRAM, type this in Terminal: sudo nvram MyVar=TestValue Check/show NVRAM: nvram -p You should see the following entry among others: MyVar=TestValue Reboot, check NVRAM again and if above entry persists, your NVRAM is working. Mine didn’t installing only OsxAptioFixDrv-64, so I reinstalled Clover with EmuVariableUefi-64 and Install RC scripts on target volume. BIOS CONFIGURATION… Check your BIOS. Press power button while holding volume up button to enter BIOS. - CPU Configuration: Boot performance mode: Turbo performance; EIST: enabled; Turbo Mode: enabled; Performance/Watt: Performance; Configurable TDP: TDP Nominal. - Intel Smart Connect Technology: disabled. - CSM configuration: CSM Support: enabled; Network: Do not launch; Video: Legacy. - Chipset/System Agent (SA) Configuration/Graphics Configuration: Aperture Size: 256MB; DVMT Pre-Allocated: 128MB; DVMT Total Gfx Mem: MAX. - BOOT: Fast Boot: disabled; Boot mode select: dual; all fixed boot order priorities disabled except for UEFI USB KEY. - Save & Exit. BOOTING INSTALLER… Now, to boot into Clover you just need to reboot with your installer usb plugged, so your motherboard recognize the UEFI entry in that drive. Click on power icon in Windows, and while pressing SHIFT, click on reset to go to Windows Boot Manager. Click on "Use a device" and next on "UEFI: SanDisk, Partiton 1" (if you are using SanDisk drive, if not it will be diferent but easily to discover). Click enter in your keyboard to boot "Install macOS Sierra". You will se the verbose log in order to fix any boot issue (you shouldn't need to if you follow this guide). Open Disk Utility and format your 32GB drive to HFS+J, GUID partition and give it a name, for example, SierraHD. Close Disk Utility and Select Install macOS Sierra and install it to your SierraHD drive. Wait until it reboots after creating the Recovery partition. You will need to boot again into Clover and boot this time from your new boot entry in your SierraHD drive to finish installation. INSTALLING CLOVER TO SIERRAHD USB… After install macOS Sierra you might want to install Clover to your SierraHD drive so you don’t need both usb drives to be plugged in order to boot. Follow same steps than before in INSTALLING CLOVER IN USB INSTALLER… Ok, now you’re able to boot into your macOS Sierra but you don’t have CPU PM, IGPU PM, backlight control, battery level… Some of them will be fixed installing kexts, other with DSDT patches or renames, some with Clover… ACPI FILES - DSDT & SSDT ACPI Tables Extraction using Clover Press F4 in Clover boot menu and OEM ACPI tables will be placed in EFI/CLOVER/ACPI/origin. Copy only those files named DSDT.aml and SSDT-X.aml (where X is any number) to your desktop in a new folder called ACPI that we will use to disassemble with iASL. Disassembling ACPI files Download iASL to your Downloads directory, type this in Terminal: cd ~/Downloads git clone https://github.com/RehabMan/Intel-iasl.git iasl.git cd iasl.git make sudo make install Install MaciASL.app to your Applications directory and run this command in Terminal to update iASL: sudo cp /usr/bin/iasl /Applications/MaciASL.app/Contents/MacOS/iasl61 Now we are going to disassemble the files. Type in Terminal: cd Desktop cd ACPI iasl -da -dl *.aml You can also try to disassemble them using External declarations in a text file called refs.txt. This may help to fix some unresolved externals (symbols not defined in any file). Copy the following text and create a refs.txt into ACPI folder in your Desktop: External(MDBG, MethodObj, 1) External(_GPE.MMTB, MethodObj, 0) External(_SB_.PCI0.LPCB.H_EC.ECWT, MethodObj, 2) External(_SB_.PCI0.LPCB.H_EC.ECRD, MethodObj, 1) External(_SB_.PCI0.PEG0.PEGP.SGPO, MethodObj, 2) External(_SB.PCI0.GFX0.DD02._BCM, MethodObj, 1) External(_SB.PCI0.SAT0.SDSM, MethodObj, 4) External(_SB.PCI0.SAT1.SDSM, MethodObj, 4) External(_GPE.VHOV, MethodObj, 3) Type in Terminal: iasl -da -dl -fe refs.txt *.aml Using refs.txt or not, this will create .dsl files that we will use to patch. Open them using MaciASL and click “Compile” to check for errors. Main mission here is to have them compile without errors (warnings and optimizations are ok). We only need DSDT and all non dynamic SSDT files. Clover shows dynamic SSDT files adding "x" (SSDT-4x.aml for example). Use dynamic files only to disassemble. NOTE: never open .aml files with MaciASL and compile, if you ever get lost among DSDT and SSDT files, extract and disassemble them again. POST-INSTALLATION… Ok, we can boot our Sierra installation, we have our ACPI files disassembled and with no errors, not patched yet, so it’s time to start fixing things. First thing to fix must be CPU Power Management. For that we use ssdtPRGen.sh. In my CC2_PACK.zip there is a SSDT for my CPU (i5-4258U). If you have other CPU, you need to generate a proper one (you will need internet access so install now FakePCIID and FakePCIID_Broadcom_WiFi and copy all WiFi related Clover patches from config_OK.plist to your config.plist). Open Terminal and type this command to download ssdtPRGen: curl -o ~/ssdtPRGen.sh https://raw.githubusercontent.com/Piker-Alpha/ssdtPRGen.sh/master/ssdtPRGen.sh Now change the file mode (+x) with: chmod +x ~/ssdtPRGen.sh Default SSDT generation: sudo ~/ssdtPRGen.sh Type n and n one more time. Open Finder and go to /Library/ssdtPRGen/. You will see a SSDT.aml, this is our CPU Power Management SSDT. Copy it to your EFI/CLOVER/ACPI/patched. You will see if PM is well implemented if X86PlatformPligin is loaded under CPU0@0 in IOReg (use IORegistryExplorer to check it. You can also use AppleIntelInfo.kext) Open SSDT-HACK.dsl with MaciASL, save it as SSDT_HACK.aml and put it into EFI/CLOVER/ACPI/patched. You can check SSDT-HACK.dsl to see what I did there (Basically, emulate Windows (_OSI to XOSI), injecting IGPU properties and ig-platform, disabling EHCI, injecting XHC properties, fixing GPRW to avoid instant wake and making EXEL and ESEL do nothing). Second thing should be IGPU Power Management. For that GFX0 needs to be renamed to IGPU in our DSDT and all SSDT files that contain any GFX0 reference. We will rename it in DSDT using Clover patch and manually find/replace in SSDT files (in our case, SSDT-7 has some GFX0 code). Third, we are going to install some kexts to enable Bluetooth, WiFi (if you replaced default wireless card with BCM94352Z), all USB ports and backlight control. Just open Kext Wizard (we will always use it to install kext files), click “Install” and look for: - FakeSMC.kext - FakePCIID.kext - FakePCIID_Broadcom_WiFi.kext - IntelBacklight.kext - XHCInjectorCC2.kext - BrcmPatchRAM2.kext - BrcFirmwareRepo.kext Any time you install any kext file, you must rebuild your cache and fix permissions. You can do it with KextWizard but it is recommended to use Terminal (see TIPS AND EXTRAS) Now that you have WiFi enabled, OS X probably put it at en1 while Bluetooth PAN is at en0. To reorder them just do the following: - Go to System Preferences > Network and delete all interfaces (WiFi and Bluetooth PAN). If you are asked about bluetooth reappearing again, click no. - In Finder go to ~/Library/Preferences/SystemConfiguration and delete NetworkInterfaces.plist. - Reboot, go to System Preferences > Network and add your WiFi interface again. This will reorder your interfaces, leaving WiFi as en0 and letting you to access Apple services as Mac App Store. You still needing to create a good SMBIOS profile, with a serial, etc. in order to activate everything: FaceTime, iMessage, Mac App Store… You can follow these guides: How to enable iMessage Clover: iMessage/Facetime Fix for Yosemite With all this you will have everything working except for battery status and audio/sound. Now it's a good time to install Wacom drivers. Battery status needs ACPIBatteryManager.kext to be installed and a patched DSDT. I’ve created a patch that you can use with MaciASL and your DSDT (you extracted and disassembled before, remember?), just click “Patch” and look for Battery CC2 Patch.txt, apply and save. NOTE: Recent tests with RehabMan probes my patch matches Dell XPS 18, so that will work too. Use any of them. IMPORTANT: Until now we were booting with ACPI/SSDT/DropOEM=false because we weren't using patched OEM files. Now we are going to use a DSDT file, so we must also provide all patched SSDT files, set DropOEM=true and set SorterOrder (same order than OEM files, making SSDT.aml the first and SSDT-HACK.aml the last, so it will be: SSDT.aml, SSDT-0.aml, SSDT-1.aml, SSDT-2.aml, SSDT-3.aml, SSDT-7.aml, SSDT-HACK.aml). You can do this with PlistEdit Pro or Xcode by yourself (check Clover Wiki for how-to). Anyway, I've prepared config_OK.plist with all these changes and more patches. Paste it in EFI/CLOVER/ and rename it to config.plist to continue with post-installation. I would like to avoid adding patched ACPI files transforming my DSDT patch to the new hotpach method (thanks Rehabman!), adding code to SSDT-HACK and adding DSDT/patches to Clover if necessary but is waaaay out of my league. Any help achieving this will be appreciated. NOTE: DSDT only needs Battery CC2 Patch for now. SSDT files only need names to be balanced, so any rename we are doing with Clover in ACPI/DSDT/Patches need to be do it as well in all SSDT (GFX0 to IGPU; B0D3 to HDAU…) If you did it all well, you should have battery status working. Audio/Sound can be achieved installing VoodooHDA. You will be able to use the internal microphone and speakers, so Siri will work. Airplay audio works too. HDMI needs work. A better choice would be to patch our codec and use AppleHDA, HDMI audio seem to work better this way and might help to fix sleep/wake. I’ve attached a dump from my Realtek ALC286 and my Intel Haswell HDMI if somebody want to help with this matter. CLONING TO INTERNAL DRIVE Now that you have an almost fully working hackintosh, you probably want to clone it to your internal SSD. For that, just follow these steps: - Boot into Windows, and shrink your C: partition using Disk Management. - Format new volume to FAT32 and give it a name (you can use MacDrive to format to HFS+J) - Boot using your USB installer, open Disk Utility and format your new internal partition to HFS+J (if you didn’t do it before using MacDrive). If you are prompted with an error, try it again. If error persists, try next step. - Clone your current installation selecting as source your SierraHD drive and destination your new internal partition. After clone, you still needing to install Clover in your internal EFI partition, so boot again your Sierra installation using your USB and repeat steps in INSTALLING CLOVER IN USB INSTALLER… You also need to place proper config.plist and your ACPI patched files, SSDT.aml and SSDT-HACK.aml in EFI/CLOVER/ACPI/patched. Note that your internal EFI partition could have no name, mine in fact shows as NO NAME in Finder In order to boot your internal Clover installation, you might like to create an entry in your Windows Boot Manager. I use EasyUEFI for that. Just click on the Create a new entry icon, select Linux or other OS, and select the path to EFI/CLOVER/CLOVERX64.EFI. Give entry a name, for example macOS Sierra NOTES: I still having some doubts about this guide. For example: - Our graphics device 8086,0A2E is natively recognized but doesn’t show a name in DPCIManager, I don’t know if can be an issue. - PCI Realtek Card Reader 10EC,5229 has no support. - USB may need work to make wake from Power Button work properly. I’ve created an injector and disable EHC with SSDT-HACK.aml and it’s under 15 port limit. I did the same with a EHC injector and FakePCIID_XHCIMux.kext or USBInjectAll.kext and a SSDT-UIAC.aml. Same result, ports work, wake with Power Button doesn’t, some of them are lost when reboot after try to wake up from sleep (using Power Button) - There are some errors with methods in EC0 that probably need work (GBTT, SMB0._STA) - Good news!! Cintiq Mode works Just plug your cable to your PC or Mac, put your Companion to sleep and it should wake as a plain Cintiq and recognized by your PC or Mac. When you unplug your video cable, you Companion come back with everything working. Enjoy - I did another test and wake quite good but with black screen: go to sleep (no cable video plugged), plug video cable, this will make screen wake but remain black, unplug video cable, use screen sharing to access and change resolution or detect displays in SysPref to push the signal to your internal display. TIPS AND EXTRAS - If you want to install any software, you must enable the lost option inside Security and Privacy. Type this in Terminal: sudo spctl —master-disable - If you want to enable HiDPi resolutions, just copy DisplayVendorID-5c23 folder into ~/System/Library/Displays/Contents/Resources/Overrides and install RDM. - If you need to rebuild caches, run this in Terminal: sudo rm -r /System/Library/Caches/com.apple.kext.caches sudo touch /System/Library/Extensions && sudo kextcache -u / - Sometimes boot into safe mode is needed. Just add -x to boot flags in Clover or push spacebar in Clover boot menu (this second option is not working for me right now, I don’t know why). - To enable playing a power chime sound effect when battery charged is plugged, type this in Terminal: defaults write com.apple.PowerChime ChimeOnAllHardware -bool true; open /System/Library/CoreServices/PowerChime.app & - If you want to try the new TouchBar present in new MacBook Pro, you can give it a try! Go here and follow instructions CONCLUSIONS AND THOUGHTS The Cintiq Companion maybe is not a famous tablet because its mainly client target are professional artists than doesn’t have too much time to play with this hackintosh stuff, but it works very well in my opinion, better than Surface devices. Geekbench results is same than MacBook Pro with same CPU and LuxMark gives a result of more than 1600 for what I checked. The only thing that it would need to be perfect, in my opinion, is to sleep and wake properly. We can do that just plugin the video cable and entering Cintiq Mode, unplug and wake but it would be nice to wake it with the Power Button. For those who could help, here you have some clues you may find helpful to solve it. Sleep works, display goes off, fans go off and led starts blinking. But when wake (only with power button) display goes back but remains black for seconds and suddenly go off, fans keep running, led keep on without blinking, but can’t access using VNC or screen sharing. If you enable the power chime sound effect, you will hear it if you unplug and plug your battery charger. The only way to come back is to force a restart by holding power button and next time you boot some devices are missing (WiFi and some USB). Restarting one more time makes all devices work again. Since I have no idea of binary patching, programming or ACPI concepts, it was very hard for me to get all this together. I’m probably doing something wrong or there’s a better way to make things work, so if you have any idea or suggestion, don’t hesitate to comment or ask. I'm doing this for two reasons, to share what I learned and to keep all the information together in one post. And this is everything, folks! I hope this help you to install macOS Sierra in your Companion 2. Now that new model is out (but far away from my budget) you can find some affordable second hand units. DOWNLOAD MY CC2_PACK It contains: ACPI folder, before and after patches (for those who want to check). Battery CC2 Patch. Kexts folder. Official BIOS folder, in case you didn’t update your Companion 2 or disabled CSM support and can’t see BIOS menu. SSDT Files folder, containing SSDT-HACK.dsl and SSDT.aml for i5-4258U PM. APPS folder: Clover Configurator 2, DPCIManager, PlistEdit Pro, Kext Wizard, MaciASL, IORegistryExplorer. EXTRAS folder: Brightness app (slider control in menu bar), Intel Power Gadget, iStat Pro widget, AppleIntelInfo.kext (for checking CPU PM). HiDPi: DisplayVendorID-5c23 folder and RDM-2.2.pkg codec_dump_ALC286.txt and codec_dump_HDMI.text for someone to may help patching AppleHDA. I want to give a HUGE thanks to all the people that are involved in making this possible, from developers to testers (Piker, Rehabman, the-darkvoid, Slice, Allan... I don't know, I'm still learning who you are, people, you are a lot so don't be offended if I didn't mention you, please ). And sorry if there's some grammar mistakes or something, it's my first guide in english.
  13. Since winter 2015 I've been slowly building my Hackintosh workstation based on Supermicro X9DAi. This mobo has quite good reputation in the community, that's why I have chosen it as my base platform. It quickly turned out the X9DAi Hackintosh setup process is time consuming and has very steep learning curve. Preparation of my rig went into months. Ethernet, USB, USB3, PM, ... step by step I fixed succeeding issues. Days, weeks – you probably know that. It was all worth it however, cause today I have 100% functional muscle hack. Thanks to wonderful community I overcame many obstacles and solved hundred of issues. So now is my turn to put my two cents. ___ Last thing which not worked in my system was audio. Many users reported lack of ability to fix this and after several attempts I also quit. Bought cheapo USB PnP sound card and left the issue unsolved. Having to test some DIY microphone project I did recently, I thought why not to give another shot to my onboard ALC889? I did, and after an hour had working audio onboard. Setup is very simple and you can proceed it in minutes. Of course this is not my developement but compilation of solutions from the web. Tested on OS X Yosemite 10.10.5 only. I don't know whether it works in other system versions. So, here's step by step how-to guide: ___ 1. Download "Realtek ALC888s Solution for Yosemite by Mister Thibard" here: http://www.osx86.net/files/file/4299-realtek-alc888s-solution-for-yosemite/ This is very convenient set of utilities suitable here. Download, mount DMG, read the README. 2. Run the PKG from "A" folder. App installs to S/L/E two kexts: VoodooHDA & AppleHDADisabler, Also Voodoo preference pane and VoodooHdaSettingsLoader.app in the Utilities. 3. Open the "B" folder from DMG and copy VoodooHDA.kext somewhere on your HD. Go to new kext location, do "show package content" and edit containing info.plist file in any plain text editor. VoodooHDA is an open source audio driver for devices compliant with the Intel High Definition Audio specification. It is intended as a replacement for AppleHDA on Mac OS X. 4. Check whether your device ID is indeed 0x1d208086 under the "IOPCIPrimaryMatch" key. <key>IOPCIPrimaryMatch</key> <string>0x1d208086</string> If it's not, refer to the README on DMG (or use DPCIManager utility to get device ID). 5. Find the "AllowMSI" key and change its value to "false". <key>AllowMSI</key> <true/> to: <key>AllowMSI</key> <false/> NOTE: if sound is lost after few seconds of any first play, it means you have missed this step 6. Save the info.plist file and close editor. 7. Using KextWizard, KextUtility or any similar app install edited VoodooHDA in /S/L/E and do usual full service. 8. Make VoodooHdaSettingsLoader load at startup. Go to System Preferences -> Users & Groups -> (select desired user) -> Login Items tab. Click "+" and locate VoodooHdaSettingsLoader.app in the Utilities. Select it and add to your startup items: 9. Restart machine. Enjoy your new sound. This solution is quick, effective and elegant. Checkout the Sound pane in System Preferences – all motherboard audio connectors are present: In the VoodooHDA preference pane you may fine-tune output & input source parameters. Very convenient. Cheers!
  14. Run macOS Sierra on a Dell Latitude E6320 NO ONE IN THIS FORUM (INCLUDING ME) IS RESPONSIBLE FOR ANY LOSS (DATA, MATERIAL, EQUIPMENT…) OCCURRED TO YOU, YOU ARE THE ONLY ONE RESPONSIBLE, AND BY FOLLOWING THESE INSTRUCTIONS YOU AGREE TO TAKE ALL THE RISKS AND RESPONSIBILITIES. THIS INSTALLATION ISN'T WITHOUT RISKS SO TAKE ALL THE PRECAUTIONS BEFORE DOING ANY FOOLISH ACTION, BACKUP YOUR DATA! This tutorial will describe the steps to install macOS Sierra on a Dell Latitude E6320 i5 2520M. If you find any mistakes or have something to improve then please send me a PM and i will update the tutorial. A special thanks goes to Brian from Tech Erra, 9 to 5 Mac and Morpheousman for using parts of their tutorial I am from The Netherlands so sorry for my bad English. 1. Credits/Sources Everything OSx86-related is a collaborative effort amongst people who enjoy doing these things, as well as those of us who enjoy tweaking and experimenting with things. Below are a list of sources used to compile this guide: OSX Latitude.com Tech Erra OSX86 Wiki InsanelyMac Forum member Jake Lo from OSXLatitude.com for helping me out with installing. Morpheousman and Polyzargon from InsanelyMac who helping me with my other topics. (Dell 780) MacPeet, Chris1111 and all other forum members who helping out the community. A special thanks goes to Brian from Tech Erra, 9 to 5 Mac and Morpheousman for using parts of their tutorial. And Hervé from insanelymac for using is modified DSDT.aml for E6320 2. Requirements Here are the requirements: A Dell Latitude E6320 – This is necessary to install macOS Sierra for this tutorial A copy of Mac OS X – This can be in the form of an existing hackintosh, a virtual machine within Windows or Linux, or even a regular Mac. If you don’t have any of these things, then find someone who can help you out for a while. I prefer using a hackintosh with OSX El Capitan, Using an already working copy of Mac OS X either in a VM or a native hackintosh install is HIGHLY recommended. A 8GB USB flash drive (or larger) – We’ll be copying the files to the drive appropriately, so make sure that you have a flash drive with enough storage space (8GB or larger). A copy of macOS Sierra – The method used by this guide requires that you have a copy of the macOS Sierra Installation app, wich is available for free from the Mac App Store. 30-60 minutes of time – Depending on how tech-savvy you are, this may be quick, or it may take a while. An SSD or HDD to install 10.12 to – For me, I used a 500GB HDD to install 10.12 to. An Wireless N Nano USB Adaptor – For use with wifi Highly recommended. I use a TP-LINK TL-WN725N adaptor. E6320_V2.zip – This ZIP file contains everything that you need to get your flash drive properly prepared. 3. My Specs My installation was successfully done on an Dell Latitude E6320 i5-2520M laptop computer with the following specs. Intel Core i5-2520M @ 2.5GHz, 3MB cache, Dual Core 4GB DDR3 1333Mhz RAM Western Digital 250GB HDD INTEL HD3000 Video Intel 825xx onboard network Dell wireless 375 Bluetooth 3.0 onboard (works OOB) IDT 92HDxxx HD audio onboard TL-WN725N Wireless N Nano USB Adaptor Apple Magic Trackpad (only @home) Apple Wireless Keyboard US (only @home) Apple Magic Mouse 4. Download OS X Sierra Download macOS Sierra from the Mac App Store. Once macOS Sierra is downloaded, close the install pop-up that appears using Command (⌘)+Q. The application INSTALL macOS Sierra will appear in /Applications Done! 5. Prepare bootable USB Installer Note on flash drives: You will need a USB flash drive to make this work. Your USB should be at least 8GB and a USB 3.0 drive is preferred. Kingston sells an 8GB USB 3.0 drive for less than 10 euro. Now, we need to prepare the USB Drive so that it will properly bootup on your PC. Make sure that the disk you choose to use doesn't contain anything that you want to keep, because the following tutorial will purge everything on the drive. Open Finder - Applications and right-click on Install macOS Sierra and select Show Package Contents. Open Contents - Resources. Open a Terminal window thru Applications - Utilities - Terminal. In the Terminal window type sudo followed by a space. Drag the createinstallmedia file from the finder window opened in Step 4 to the Terminal Window. Type --volume followed by a space. Connect your USB drive and drag the USB drive into the Terminal Window. Type --applicationpath in the Terminal followed by a space. Open Finder - Applications and drag the Install macOS Sierra into the Terminal Window. Press Return on the keyboard to submit the full command. Type a 'Y' to continue when prompted to do so, and press Return on your keyboard The install process will begin by erasing the contents of your USB disk and copying the installer files to the USB disk. The entire process is quite lengthy; it can takes around 15-30 minutes, so you will need to show some patience 6. Installing Clover to the USB Disk Unpack the E6320.zip to your desktop or specified map you preferred. Open the map E6320 - Clover_v2.3k_r3726. DubbleClick on the Clover_v2.3k_r3726.pkg package file. Clover installation screen will be prompt. Click on Continue - Continue. Click on Change Install Location on the right bottom. Choose your USB Stick named Install macOS Sierra Public Beta click on Continue. Click on Customize on the left bottom. Choose Install Clover in the ESP Choose Bootloader : Install boot0af in MBR Choose in Clover EFI for CloverEFI 64- Bits SATA At last choose Install RC Scripts on target volume Click after that on Install. Clover will installed on the EFI Partition on the USB after install you can see the EFI partition in Finder. 7. Prepare USB stick for the Dell E6320 Now, we need to prepare the USB Drive so that it will properly bootup on your Laptop. Go to map where you have unpacked the E6320 zip file there you will find a map called EFI. Copy the map EFI and go to your EFI partition thru Finder. Paste the EFI folder in the EFI partition and replace everything. Done your USB Stick is ready to boot macOS Sierra installer. 8. Bios Settings Dell Latitude E6320 Before we boot from the Dell Latitude we need to optimize the bios for OSX Sierra Start your Dell Latitude and press F2 to get into the Bios. In the main screen click on "Load Defaults", the bios will be reset to default settings. Go to General - Boot Sequence and choose on the right for USB Device and click the up arrow so that the USB Device is on top, click on apply to make the setting. Go then to System Configuration - SATA Operation and choose on the right for AHCI click again on apply and choose exit, now the Bios is ready for installing OSX Sierra. 9. Installing OSX Sierra from your USB drive Time for the fun stuff! We’ll now boot from your USB drive and install macOS Sierra onto the Hard Drive. Using a USB 4G flash drive will help things out quite a bit. Power on unit while tapping F12 Key to choose boot device, select USB device. When Clover boot screen is visible, choose boot "Install macOS from Sierra USB Installer". Choose you desired language and click on the arrow, the macOS Utilities screen will appear. For a new installation of macOS, you must erase and format the destination drive according to the following steps before continuing. If you are upgrading from Mavericks , Yosemite or El Capitan and you want to keep your files and apps, skip steps 1-9. (NOT TESTED IN SIERRA) Choose in the macOS utilities for Disk Utility and click Continue. Disk Utility will be opened, highlight your target drive for macOS Sierra installation in the left column. Click ERASE button on top. Under Name: Type Sierra or any other name. Under Format: Choose Mac OS Extended (Journaled). Under Scheme: Choose GUID Partition Map. Click Erase. Click on Done. Close Disk Utility you will be prompted to the macOS Utilities screen. In the macOS Utilities screen choose Install macOS and click 2x on Continue. Agree the license agreement and click again on Agree When the installer asks you where to install macOS, choose your Sierra HDD click on Install. Sierra will be installed on the HDD, this will take about 6 - 15 minutes depending of your HDD. Upon completion, system will restart a 1st time. Press F12 key to choose the boot device. When the Clover Boot screen is visible, Choose "Boot macOS Install from Sierra". macOS will continue to Install the OS on your HDD this will take about 10 -25 minutes after that the installation will be finished and your laptop will reboot. 10. Booting for the first time macOS Sierra When the Clover Boot screen is visible, Choose "Boot MAC OS X from Sierra" You will eventually get to the setup screens for macOS Sierra. Go through the setup process to setup macOS Sierra. At the country selection choose your country and press continue. Select Your Keyboard choose ABC and press Continue. Choose at "How do i connect to the internet " ..."My Computer Does Not Connect to the Internet", we will fix this later, go further with the setup process and press continue. Choose at Transform Information To This Mac for "Don't Transfer any information now" click on Continue. At Enable Location Services for "Enable Location Services on this Mac" click Continue. Agree the Terms and Conditions. Create your Computer Account and uncheck "Set time zone based on current location" press Continue. Choose your Timezone and click Continue. At the Diagnostic screen click Continue. The setup process is ready, Done!. 11. Setting up your keyboard When the setup is finished the Keyboard Setup Assistent will appear. Press Continue to Identify Your Keyboard. You will ask to press some keys. After pressing some keys you will get the message Your Keyboard Cannot Be Identified, press OK. Choose at Select the Keyboard Type for ANSI (United States and others) Press Done your Keyboard is setup 12. Adjust some settings in macOS 10.12 Once in 10.12 go to Finder – Preferences – General and choose in show these items on the desktop for Hard Disk External Disk Go to tab Sidebar and choose your desired Favorites, Shared and Devices. Close the Finder Preferences. 13. Change Security & Privacy for 3rd party software Start Terminal choose GO - Utilities - Terminal. In Terminal type sudo spctl --assess --master-disable followed by password to activate the option in Security & Policy "Allow apps downloaded from" Anywhere. Go to System Preferences – Security& Privacy and look of the option "Anywhere" is active if not activate the option. Close system preferences. 14. Revert HDD for proper boot. Launch Terminal and execute the following command: sudo diskutil corestorage revert / When prompt type your password. Exit Terminal and reboot again with your USB to macOS. 15. Installing Clover to the HD The steps 15 and 16 are the same as steps 6 and 7 but now we will install clover to the HDD of the E6320. Unpack the E6320.zip to your desktop or specified map you preferred. Open the map E6320 - Clover_v2.3k_r3726. DubbleClick on the Clover_v2.3k_r3726.pkg package file. Clover installation screen will be prompt. Click on Continue - Continue. Click on Change Install Location on the right bottom. Choose your HDD named Sierra click on Continue. Click on Customize on the left bottom. Choose Install Clover in the ESP Choose Bootloader : Install boot0af in MBR Choose in Clover EFI for CloverEFI 64- Bits SATA At last choose Install RC Scripts on target volume Click after that on Install, Clover will installed on the EFI Partition on the USB after install you can see the EFI partition in Finder. 16. Prepare HDD for booting the Dell E6320 Now, we need to prepare the HDD Drive so that it will properly bootup on your PC. Go to map where you have unpacked the E6320 zip file there you will find a map called EFI. Copy the map EFI and go to your EFI partition thru Finder. Paste the EFI folder in the EFI partition and replace everything. Done your E6320 is ready to boot macOS Sierra. 17. Install Wlan driver for the TL-WN725N The wireless lan on the Dell E6320 doesn’t work, therefore I use a Wireless N USB Nano Adaptor from TP-LINK. The software is straight forward and installs without problems. Go to your E6320 folder which you have extracted to your HDD of your macOS Sierra. Open the map "beta driver for mac os X 10.11" . Run Installer_RTL.pkg Click Continue - Continue - Continue - Agree - Install Enter your Password and click Install Software - Continue Installation Click Restart to Reboot your Laptop. The first time you will get a kernel panic don't worry reboot again and the laptop will start macOS Sierra. Done! 18. What's working? Just about everything. 19. Finished! You’ve successfully installed macOS Sierra onto your Dell Latitude E6320. TROUBLESHOOTING 20. iMessage & FaceTime Fix You will need MLB and Rom numbers from a legit Mac device that is on the mac server. Run iMessage debug on a iMac, Macbook, etc and make a copy and paste of the Terminal output. Open Clover Configurator. Mount EFI Partition. Import config.plist from EFI/EFI/Clover (File , import configuration, browse to config.plist and select). In Clover Configurator Click on RT Variables, Enter Rom and MLB Values from iMessage output from valid iMac device. Save changes to config.plist. Reboot, Sign into iMessage. iMessage and FaceTime should now both be working. 21. BOOT 0 Error If you are using a 4k HDD you can get boot:0 error, to solve this issue do the following. Reboot system back into Sierra installer (USB)FLASH DRIVE). Run Disk Utility find the Disk Identifier (eg. disk0s2). Unmount the drive you installed Sierra on. Launch Terminal and execute the following command: dd if=/usr/standalone/i386/boot1h of=/dev/disk0s2. Exit Terminal. Boot Normally. Run macOS Sierra 10.12 E6320.pdf
  15. Preface I recently snagged a Vizio CT14-A0 on eBay for around $170(!). What caught my eye was it's sleek yet aggressive all- aluminum design. It's rock solid, has a great screen, and is plenty fast for average use. I call it: The SwagBook Air! The trackpad makes me want to slit my wrists, but other than that, it’s a very solid and well-rounded HackBook if I do say so myself ***This guide should work for similar A1/A2/A3/A4 Models. Configurations may differ slightly*** Read through this guide in it's entirety before attempting installation. Keep in mind Wifi will not work during the process, so it's a good idea to download all the necessary files and put them on your installation USB. I'm assuming you have general knowledge of hackintoshing/kexts/Clover/DSDTs. Needless to say, backup your data. I assume no responsibility for the loss or damage of your intellectual property. Specs: 1.8Ghz Intel Core i3 3217u / HM76 Chipset Intel HD4000 Graphics 14.1” 1600x900 IPS(!) 4GB RAM DDR3 @ 1333 Mhz Cirrus Logic CS4210 Audio 128GB Toshiba mSata SSD QUANTA UEFI BIOS Broadcom BCM94352 802.11ac 5Ghz Wifi+BT4LE (I used an AzureWave AW-CE123H to replace the completely incompatible stock card, grabbed it for ~$20, has all the bells and whistles) What's working: Graphics (Resolution, HDMI, QE/CI) Keyboard & Trackpad Audio (Headphones, Speakers, Internal mic) USB (haven’t tested speeds) Wifi & Bluetooth (with aftermarket adapter) FaceTime, iMessage, App Store, And iCloud Power management (Sleep, SpeedStep) Camera What's not working (yet): Native audio (VoodooHDA required; no audio over HDMI) Big thanks to InsanelyDeepak for the patched AppleHDA! Inject audio id 13 in Clover. No microphone input though, and I still can't figure out how to get HDMI audio working. AppleHDA-274.9-CS4210.zip Working closely with InsanelyDeepak for an AppleALC /Clover solution! Not-horribly-depressing-glitchy-unusable-trackpad-with-basic-gestures (Updated Sentelic driver for VoodooPS2Controller.kext needed) Pre-Install Create a bootable OS X Installer with whatever method you like (I'm partial to createinstallmedia). Clover Options to check: (Dig through the menus a little bit!) Install for UEFI booting only EmuVariableUefi OsxAptioFixDrv PartitionDxe NTFS UEFI Add these kexts: FakeSMC (Optional: FakeSMC Plugins): https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek/downloads ACPIBacklight: https://bitbucket.org/RehabMan/os-x-acpi-backlight/downloads ACPIBatteryManager: https://bitbucket.org/RehabMan/os-x-acpi-battery-driver/downloads ACPIDebug: https://bitbucket.org/RehabMan/os-x-acpi-debug/downloads BrcmFirmwareData & BrcmPatchRAM2: https://bitbucket.org/RehabMan/os-x-brcmpatchram/downloads VoodooHDA: http://sourceforge.net/projects/voodoohda/files/VoodooHDA.kext-2.8.8-final.zip/download VoodooPS2Controller: https://bitbucket.org/RehabMan/os-x-voodoo-ps2-controller/downloads Edit these options in your config.plist: Devices/Fake ID/Wifi:0x43a014E4 (Fake PCI ID injection for Wifi) Gui/Screen Resolution:1600x900 (So Clover looks better) Graphics/Dual Link:1 (For functional screen output) Graphics/ig-platform-id:0x01660004 (For functional screen) Graphics/Inject-Intel (For functional screen) Kernel and Kext Patches: AsusAICPUPM SMBIOS/Magic Wand Thingy/MacBook Air Graphic/Shake both shake buttons a few times DON’T Forget to come back after you’ve install Clover to your machine and fix the RTVariables section with your MAC Address (without colons) as your ROM and your Clover-generated serial number + 5 hex digits to fix iMessage and FaceTime Copy and paste this directly into the KextsToPatch section of your config.plist (You can’t copy these values directly into Clover Configurator as they are base64 and the GUI needs hexadecimal) Vizio CT14-A0 Clover Kext Patches.txt Explanations: Some of the rather obvious patches are from Toleda/lisai9093 for Handoff/5Ghz Wifi/BT, One is to fix HD4000 Garbled graphics on startup, and the rest are framebuffer patches to enable HDMI output (Rehabman). Install Boot the installer in verbose mode. Install OS X as usual. Post-Install Boot again from your USB stick into your fresh install of OS X. Click through the setup and configure it to your liking. Internet will NOT be working at this point. Install Clover to your internal SSD with the same options as before, except this time selecting “Install in ESP”. Copy the config.plist and kexts into their places. Patch DSDT/SSDT SSDT.aml.zip Add this to /EFI/EFI/CLOVER/ACPI/origin. With our SSDT in place, the remaining thing to do is patch our DSDT. This will enable Wifi + Bluetooth (if you have the same chipset), Display brightness and keyboard brightness control, and battery indicator. Extract DSDT using method of choice. I like to press f4 in Clover to extract to /EFI/EFI/CLOVER/ACPI/origin. Patches (MUST APPLY IN THIS ORDER): rename_GFX0: https://github.com/RehabMan/Laptop-DSDT-Patch/blob/master/graphics/graphics_Rename-GFX0.txt Visio CT14 Battery: https://github.com/RehabMan/Laptop-DSDT-Patch/blob/master/battery/battery_Vizio-Ultrabook-CT14.txt Arpt3-bcm4352: https://github.com/toleda/wireless_half-mini/blob/master/Patches/arpt3-bcm4352.txt Map brightness keys to brightness controls: Brightness Fix.txt ***UPDATED***Fix Volume/Brightness/Media keys To enable the use of the brightness, volume, and play/pause/seek keys without also holding function, add this, starting at line 296: <string>3f=e005</string> <string>40=e006</string> <string>41=e020</string> <string>42=e02e</string> <string>43=e030</string> <string>44=e010</string> <string>57=e022</string> <string>58=e019</string> <string>e005=3f</string> <string>e006=40</string> <string>e020=41</string> <string>e02e=42</string> <string>e030=43</string> <string>e010=44</string> <string>e022=57</string> <string>e019=58</string> That’s it. Reboot and enjoy. Enjoy Congrats, enjoy the fruit of your labor. I broke my back searching through poorly written guides, and old threads, and experimenting with kexts and patches to compile this guide, but it’s nowhere near what the developers who created these things went through. Support them! Notes Dual-Booting Windows 10 My laptop would not let me manually enter a UEFI entry, hence the ghetto fix: After installing Clover to the internal SSD, I had issues with the Windows Boot Manager being the only UEFI option in the BIOS (I'm dual-booting Windows 10). I went to /EFI/EFI/Microsoft/Boot/ and renamed bootmgfw.efi. In this state, Windows is not bootable. On reboot, Clover successfully loaded. Once in OS X, I renamed bootmgrw.efi back to it's original name. After rebooting once more, Clover took priority as intended and I was once again able to boot into either OS. Bugs Glitchy Trackpad: Trackpad is incredibly awful under OS X; VoodooPS2Controller only provides basic support for the Sentelic Touchpad. It’s very very buggy, as in barely usable. See for yourself. Having more than one finger makes the whole thing freak out Fix: None ;( Thanks for reading! Please feel free to ask questions and comment if you have any improvements. I hope I’ve helped someone learn something
  16. Hi, I would install El Capitan on my Asus. Do you help me? Intel Core i5-6500u 4GB di Ram DDR4
  17. This is simple guide how to change/alias location of home folders. Many of hackintosh users use SSD drives for system and apps and would prefer not to crowd them with extensive amounts of data. This guide, courtesy of Davemreed from MacRumors.com explains in most simple way how to link default home folders to any secondary internal or external hard drive. Thanks to this solution you can store downloads, pictures, music, FCP libraries etc not on your system drive. This example refers to 'Downloads' folder, but can be applied to any home folders respectively. Warning!!! - this procedure deletes home folder with whole its content, so please be careful. First copy your Download folder to target location, otherwise you lose it. Launch Terminal Type: sudo rm -rf ~/Downloads/ You will prompted by a password, preceded by a warning about being careful. Now your Downloads folder is deleted from your home location. Next, in the Terminal window, type: ln -s (with a space following the 's'). Now, open a Finder window and go to the target location of your Downloads. Drag the new Downloads folder into the Terminal window. The path to the new destination will auto fill. Hit the return key to issue the command. The new Downloads default folder has now been successfully changed. Enjoy!
  18. Welcome to this guide by me Shuuin ! XD "WARNING GUIDE BY NOOB" Before using this guide you need to know there is little i can help with!! - Started using hackintosh 2 days ago ( 16-03-2016 ) this is just for those who doesn't have a mac nor know someone with a mac. - I might be able to help with Graphics, i had some problems with Nvidia 780 ti, Black screen after instalment of Web drivers! We'll be starting of with what you'll need to start this! 1. USB with 8GB of storage, mine was 16GB 2. Windows machine, i used Windows 10 3. TransMac. You can download it here click on ( tmsetup.exe ) 4. You'll need El Capitan, you can download the .dmg i'm not allowed to share link! (1) - Download and install TransMac. After installment right click and open "As administrator" Now you should get an interface plug-in your USB then click Tools and refresh. You should now see your USB stick. Right click on your USB stick and click "Format Disk for mac" then click Yes/Okay.. (2) - USB stick is now formatted and your ready for install! Before you do anything else, check and see if your download is done "El Capitan" If it's done, then right click on your USB stick again in TransMac and click on "Restore with Disk Image" you'll now have to find your .dmg file, this file i named "EFI.dmg" Let it finish, then when it's done loading then you're ready for install, on your Hackintosh machine. Before doing this, you have to do some things in your BIOS. To access BIOS/UEFI Setup, press and hold Delete on a USB Keyboard while the system is booting up. Load Optimized Defaults before doing anything else. If your CPU supports VT-d, find the setting and disable it. If your system has CFG-Lock, find the setting and disable it. If your system has Secure Boot Mode, find the setting and disable it. Set OS Type to Other OS, if applicable. Save and exit. Your machine should reboot. My setup: CPU: i5-4690K RAM: 16GB GPU: Nvidia GTX 780 Ti MotherBoard/Chipset: B85m Gamer / Intel B85 Problems i had! Started out with having problems with my Graphics cards Web drivers. After i installed CUDA and Web Drivers i got black screen, i then booted with nv_disable=1 after that i was on my desktop, still with bad graphics. What i did to fix this was, open clover config and load my config.plist after that i then go to the "boot" option. Then i disabled everything and only enabled the nvda_drv=1 i then moved to Graphics and made sure the Inject NVidia was off and then turned on Inject Intel (remember to save config file). I rebooted and then booted into my Mac OS without the nv_disable=1 and everything was working fine! I hope this guide was any help, if not ask!
  19. Hello newcomer, As i saw that many users upload their config.plist or SMBIOS.plist with non deleted S/N and MLB, ROM values. Noobs please never upload your unique machine values like ROM, MLB, Serial Number or System UUID. If you upload these values your Apple ID will be suspended form Apple services (AppStore, FaceTime, iCloud, iMessage, iTunes ...) directly, because some other noobs will try to "clone" your system as described here. It is an easy process ... simply remove these information from your uploaded media as blurring the data (watch here) or as removing / censoring the files for upload (watch here) Thank you for your attention and have a good start, here, in the forums at Insanelymac. P.S. don't blame me for this shared serial. I had found it just before i wrote this guide .
  20. Introduction - The "must know" for the Guide to work. Preparation - Erasing the "garbage" of iMessage and other Apple Products. Set Up - The correct Clover Config explained. Optional - Calling the Apple Support the "right" way.
  21. This is a very quick guide on making the Recovery HD partition usable in El Capitan, bootable via Clover. 1- " diskutil list " * you will get de partition list, note that the Recovery Partition is obviously named " Recovery HD "... * check the number of the partition it is in, in this case, 3:, so, you will have disk0s3 as mount device... --- /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *240.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_HFS El Capitan 239.2 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 --- 2- create a folder in Volumes folder for Recovery HD and mount it there... " sudo mkdir /Volumes/Recovery\ HD/ " " sudo mount -t hfs /dev/disk0s3 /Volumes/Recovery\ HD/ " 3- enter the directory and remove the " prelinkedkernel " " cd /Volumes/Recovery\ HD/com.apple.recovery.boot/ " " sudo rm -rf prelinkedkernel " 4- now, copy your working prelinkedkernel there... " sudo cp /System/Library/PrelinkedKernels/prelinkedkernel /Volumes/Recovery\ HD/com.apple.recovery.boot/ " and just in case... " sudo touch prelinkedkernel " 5- reboot and test it... (takes some time to load even in real macs) Enjoy!
  22.  OS X 10.11 El Capitan UEFI Clover on Sony VAIO S PLEASE REFER TO THE GUIDE. I WILL NOT ANSWER QUESTIONS IF ALREADY ANSWERED IN THE GUIDE! BY FOLLOWING THIS GUIDE YOU AGREE TO TAKE THE RISKS AND RESPONSIBILITIES OF LOSING DATA. ALWAYS BACKUP! This guide will give you step-by-step instructions on How to Install OS X 10.11 El Capitan on Sony VAIO SVS13. Sony VAIO S13p (SVS13A2C5E) Specs: Intel Core i7-3520M 12GB SDRAM Intel HD Graphics 4000 NVIDIA GeForce GT 640M Samsung 850 Evo 250GB What's working? Intel HD4000 Graphics with QE/CI Acceleration HDMI Sound (Speakers, Microphone, Headphone Jack, HDMI, USB) Keyboard, Touchpad USB 2.0/3.0 Webcam Optical Drive Ethernet Bluetooth (Intel) Brightness Power button Sleep/Wake UEFI/NVRAM *WiFi (Broadcom/Atheros) *Airport Extreme 2,4GHz/5GHz *802.11ac/n/g/b/a *Bluetooth (Broadcom/Atheros) *Airdrop *Handoff & Hotspot with BT4LE What's partially working? Bluetooth Intel BT worked OOB but does not feature Handoff since it's not a BT4LE. Replace your chip with an Atheros or Broadcom one. Webcam Since the Exmor sensor built in is not the best, you get a dark image in OS X. Windows uses software/drivers to increase the brightness. What's not working? Intel WiFi Apple doesn't use Intel WiFi. Replace your chip with an Atheros or Broadcom one. Discrete graphics card NVIDIA GeForce 640M uses NVIDIA Optimus for dual-configuration which is not supported the same way on OS X. VGA Apple removed this feature in OS X 10.8.3 Mountain Lion SD-Card/Memory Stick Reader (no drivers for OS X) Speed/Stamina switch Fingerprint sensor (no drivers for OS X) Disc Eject/Assist/Web/VAIO buttons You need… ... an empty USB flash drive or an external hard drive (8gb at least) ... a Mac or a virtual machine with OS X (10.6.8 or later) On your Mac/OS X VM Download OS X 10.11 El Capitan from the App Store Create the OS X Installer You can actually create the OS X installer on the (external) hard drive but to keep things simple from now on I will refer to ‚USB‘. IF YOU HAVE IMPORTANT DATA ON YOUR USB, PLEASE MAKE A BACKUP! THE USB WILL BE FORMATTED AND EVERYTHING WILL BE DELETED! You can create the USB with either a MBR or a GPT partition scheme. If you select MBR, you will have to manually create a FAT partition for CLOVER EFI and a separate HFS+J partition for the OS X Installer. With GPT you just need 1 HFS+J partition and Disk Utility creates a hidden EFI partition. Since we will use this USB with a UEFI system, we can use GPT. On legacy system you need a MBR USB. Create Partition(s) on USB Open Disk Utility under /Applications/Utilities. Select the USB. Click on the Partition tab. Click on Partition Layout > 1 partition. Click on Options. Select GUID Partition Table. Apply with OK. Under Format select Mac OS Extended (Journaled). Under Name rename the partition to „install_osx“. Click on Apply. Click on Partition. When it’s finished creating the USB partition(s) close Disk Utility. Make OS X Installer on USB*1 Open Terminal and type this command, then press Enter: sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/install_osx --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction You need a password for this command*2. Type your password and press Enter. This process can take several minutes, depending on the USB write speed. Mine took 5 minutes to finish. Close Terminal. You now have a OS X installer for real Macs. We need the Clover bootloader to actually boot the OS X Installer on a non-Mac system. *1 The createinstallmedia method is not supported under OS X 10.6 Snow Leopard. Use alternative methods. *2 If you don't have a password (blank), you need to set one under System Preferences > User & Groups > Change Password Install Clover to USB Download Clover EFI bootloader. http://sourceforge.net/projects/cloverefiboot/ Open the Clover installer package. Click on Continue, Continue. Click on Change Install Location. Select your USB drive now called ‚Install OS X El Capitan’. Don't select the internal Hard Drive on your real Mac/VM! Click on Continue. Click on Customize. Check ‚Install for UEFI booting only‘. ‚Install Clover in the ESP‘ will be selected automatically and installed to the hidden EFI partition. Under Drivers64UEFI check ‚OsxAptioFixDrv2-64‘. Optional: Install BlueMac under Themes. Click on Install. Type your password. Click on Install Software. When it’s finished, press Close. Since the EFI partition is hidden, we need to mount it to copy some files. But the Clover installer already mounted it.*3 Go to the EFI partition (on your Desktop). Open the folder /EFI/CLOVER/drivers64UEFI Delete VBoxHFS.efi Download HFSPlus.efi https://github.com/JrCs/CloverGrowerPro/blob/master/Files/HFSPlus/X64/HFSPlus.efi?raw=true Copy HFSPlus.efi to /EFI/CLOVER/drivers64UEFI Go to the folder /EFI/CLOVER/kexts Delete all the folders inside /EFI/CLOVER/kexts except for ‚Other‘. Download FakeSMC https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek/downloads Copy FakeSMC.kext to /EFI/CLOVER/kexts/Other Download VoodooPS2Controller https://bitbucket.org/RehabMan/os-x-voodoo-ps2-controller/downloads Copy VoodooPS2Controller.kext (Release) to /EFI/CLOVER/kexts/Other Download RealtekRTL8111.kext. https://bitbucket.org/RehabMan/os-x-realtek-network/downloads Copy RealtekRTL8111.kext to /EFI/CLOVER/kexts/Other If you have a RAID configuration, you will need HPRAIDInjector.kext Download HPRAIDInjector.kext Copy HPRAIDInjector.kext to /EFI/CLOVER/kexts/Other Download a config.plist for your system with appropriate frame buffer for your display resolution. 1366x768 config_HD4000_1366x768.plist 1600x900/1920x1080 config_HD4000_1600x900.plist To download, select File > Save As Under Format select Page Source. Select Desktop as your location. Click Save. Click Don’t Append. Rename the config file on your desktop to ‚config.plist‘. Copy config.plist from your Desktop to /EFI/CLOVER and replace the default one. Make a backup of your /EFI/CLOVER folder to the other USB partition (‚Install OS X El Capitain‘). You’ll need it later. Create a folder for that. Eject the EFI partition. Eject the USB. *3 If you unmounted/ejected the EFI partition of the USB, read the Mouning EFI section under Post Installation of this guide. On the Sony VAIO S BACKUP ALL YOUR IMPORTANT DATA BEFORE PROCEEDING. THE HARD DRIVE WILL BE FORMATTED AND EVERYTHING WILL BE DELETED! BIOS Settings Shut down your laptop. Press the Assist button. Press F2 to boot into BIOS. Restore default settings under the Exit tab. Make sure ‚UEFI‘ is on. Make sure ‚Booting from external device‘ is on.*4 Save settings. Shut down your laptop. *4 This option External Device Boot applies when you set the external device to first boot priority. it doesn't affect pressing F11 to boot from External Device. Boot the OS X Installer Plug in your USB into a USB 3 port. The USB 2 port will not work without GenericXHCI (GenericXHCI does not work in OS X 10.11 El Capitan anyway). Press the Assist button. Press F11 to boot from external device.*5 Press ENTER to boot the OS X Installer. *5 If you have set the External Device as first Boot Priority you don't have to boot from Rescue Mode (Assist Button). Just connect the USB and boot your Laptop. Installing OS X El Capitan Select language. Continue. Launch Disk Utility. Erase your hard disk. Rename your partition and apply. Exit Disk Utility. Install OS X. Continue. Select your hard drive partition. Install. This process creates the Recovery partition. After a while the OS X Installer will automatically restart and beging the real installation. The real installation can take several minutes, depending on read/write speeds. When it’s finished you will again boot into your USB’s Clover Menu. Select your partition in Clover Boot Menu and boot into OS X. Configure OS X. Installing Clover to the Hard Drive To boot without USB you need to install Clover again - this time your Hard Drive. It’s a similar process to installing it to USB. Download Clover EFI bootloader. http://sourceforge.net/projects/cloverefiboot/ Open the Clover installer package. Click on Continue, Continue. Click on Change Install Location. Select your Hard Drive partition. Continue. Don't select your USB. Click on Customize. Check ‚Install for UEFI booting only‘. ‚Install Clover in the ESP‘ will be selected automatically. Under Drivers64UEFI check ‚OsxAptioFixDrv2-64‘. Check ‚Install RC scripts on target volume‘ (Optional) Check ‚Install Clover Preference Pane‘ Click on Install. When it’s finished, press Close. Enable ‚Hard disks’ under Finder > Preferences > General > Show these items on the desktop. You can disable it later. Open the folder /EFI/CLOVER/drivers64UEFI Delete VBoxHFS.efi Open your USB drive. Copy the contents of the EFI-backup to EFI partition of your hard drive. Replace the files. Open the folder /EFI/CLOVER/kexts. Rename ‚Other‘ to ‚10.11‘. Restart your laptop without the USB and boot into OS X. Post Installation Mounting EFI Whenever you install something to the EFI partition, you will need to first mount it. Download Clover Configurator. https://dl.dropboxusercontent.com/u/182149214/cloverconf/app/10.10/CCV.zip Launch Clover Configurator. Mount EFI partition. Select diskXsY for your hard drive. Patching DSDT & SSDTs Extracting native ACPI files Boot into Clover bootloader menu. Press F4 on your keyboard. This will dump your native DSDT/SSDT files to /EFI/CLOVER/ACPI/origin. You will get no feedback. Proceed. Boot into OS X. Mount EFI. Patching ACPI files Download MaciASL. http://sourceforge.net/projects/maciasl/ Launch MaciASL. Go to MaciASL > Preferences > iASL. Set ACPI 5.1 under Compiler Options > ACPI Specifications. I created an automated terminal command to patch your DSDT/SSDTs. Either follow this method or the manual way. Automatic Patching with Terminal Manual Way Compiling ACPI files Open DSDT.dsl in MaciASL. Save as ACPI Machine Language Binary (aml) „DSDT.aml“. Open SSDT-2.dsl in MaciASL. Save as ACPI Machine Language Binary (aml) „SSDT-2.aml“. Including patched ACPI files in Clover Use this Terminal command or follow the manual way: Automatic with Terminal ​ Manual way: SSDT/Power Management Use ssdtPRGen to create a SSDT for your system. https://github.com/P...ha/ssdtPRGen.sh Open Terminal and type: curl -o ~/ssdtPRGen.sh https://raw.githubusercontent.com/Piker-Alpha/ssdtPRGen.sh/master/ssdtPRGen.sh chmod +x ~/ssdtPRGen.sh Type this command to generate an SSDT for your system: ~/ssdtPRGen.sh Including created SSDT in Clover Use this Terminal command or follow the manual way: Automatic with Terminal ​ Manual way: Restart. Power Management Verification Download ApplteIntelInfo.kext (built by pokenguyen #284 Verify Speedsteps in terminal: cd ~/Downloads sudo chown -R root:wheel ./AppleIntelInfo.kext sudo chmod -R 755 ./AppleIntelInfo.kext sudo kextload AppleIntelInfo.kext cat /var/log/system.log | grep "AICPUPMI:" sudo kextunload AppleIntelInfo.kext Sleep/Wake Real Macs use Hibernation Mode. You need to deactivate hibernation mode. Open a Terminal window. Type these commands and enter: sudo pmset -a hibernatemode 0 sudo rm /var/vm/sleepimage sudo mkdir /var/vm/sleepimage Backlight The backlight patch and kext in OS X El Capitan has changed. If you use an older DSDT with patches already applied, you need to re-apply the backlight patches. Download ACPIBacklight.kext https://bitbucket.org/RehabMan/os-x-acpi-backlight/downloads Copy ACPIBacklight.kext to /EFI/CLOVER/kexts/10.11 Battery Download ACPIBatteryManager.kext https://bitbucket.org/RehabMan/os-x-acpi-battery-driver/downloads Copy ACPIBatteryManager.kext to /EFI/CLOVER/kexts/10.11 USB USB in El Capitan has significantly changed. We can no longer use GenericXHCI or USB 3 Multiplex patch. Download FakePCIID_XHCIMux.kext https://bitbucket.org/RehabMan/os-x-fake-pci-id/downloads Copy FakePCIID_XHCIMux.kext and FakePCIID.kext to /EFI/CLOVER/kexts/10.11 Clover method: DSDT patch method: Audio Download KextUtility. http://cvad-mac.narod.ru/index/0-4 Download DummyHDA.kext. https://www.dropbox.com/sh/u22fjjv499gax1u/AABuJriY_0xEA4fBmIswAFYka?dl=1 Install DummyHDA.kext with KextUtility. DummyHDA only works in /System/Library/Extensions Download CodecCommander.kext. https://bitbucket.org/RehabMan/os-x-eapd-codec-commander/downloads Install CodecCommander.kext with KextUtility. CodecCommanders (in OS X 10.11 El Capitan) only works in /System/Library/Extensions Add these patches to Clover under Kernel and Kext patches section: Name: AppleHDA Find: 8508EC10 Replace: 00000000 Comment: AppleHDA #1 of 3 Name: AppleHDA Find: 8419D411 Replace: 7502EC10 Comment: AppleHDA #2 of 3 AppleHDA #3 of 3 is not necessary in El Capitan anymore. It’s only for Yosemite/Mavericks. In El Capitan there is a new codec 0x11D41983 which must not be loaded. Otherwise AppleHDA has no sound output. Name: AppleHDA Find: 8319D411 Replace: 00000000 Comment: Disable the new codec 0x11D41983 (El Capitan) Under Devices in Clover use Audio Layout 3. Additional steps after OS X 10.11.4: Copy DummyHDA.kext from System/Library/Extensions to your Desktop. Right click on DummyHDA.kext and Show package content. Open the file Info.plist inside the folder Contents with a Text Editor. Search these lines: <key>OSBundleLibraries</key> <dict> Add this below the lines: <key>com.apple.iokit.IOPCIFamily</key> <string>1.1</string> <key>com.apple.iokit.IOACPIFamily</key> <string>1.2.0a1</string> Save and exit. Install DummyHDA.kext with KextUtlity. Rebuild Cache for Audio.*6 *6 Necessary if even after a reboot there is no sound. Look at Tuning/Tips section at the end of this guide. HDMI Depending on the IGPlatform ID you use, you may already have partial HDMI output. If you use IGP=3, you already have HDMI video but no audio. IGP=4 has no HDMI at all. Add these patches to Clover under Kernel and Kext patches section: Name: AppleIntelFramebufferCapri Find: 020500000004000007040000 Replace: 020500000008000006000000 Comment: HDMI-audio HD4000, port 0205 Name: AppleIntelFramebufferCapri Find: 030400000004000081000000 Replace: 030400000008000006000000 Comment: HDMI-audio HD4000, port 0304 Name: AppleIntelFramebufferCapri Find: 040600000004000081000000 Replace: 040600000008000006000000 Comment: HDMI-audio HD4000, port 0406 For HDMI-Video on IGP=4 you’ll need additional patches: Under Clover > Devices check ‚UseIntelHDMI‘. Restart. You may have to rebuild cache. Check "Rebuild Cache (for AppleHDA)" under Tuning & Tips section. WiFi & Bluetooth The Intel Wireless Card is not compatible with OS X. Only Bluetooth will partially work. Replace it with a compatible one. Atheros AR5B195 For compatible Atheros cards download toledaARPT. https://github.com/toleda/wireless_half-mini/blob/master/Deprecated%20Files/airport_kext_enabler/toledaARPT.kext.zip?raw=true This method is deprecated. If you wish to use a new method, follow the Airport - PCIe Half Mini guide http://www.insanelymac.com/forum/topic/292542-airport-pcie-half-mini/ For Bluetooth download and install IOath3kfrmwr.kext. https://bitbucket.org/RehabMan/os-x-atheros-3k-firmware/downloads Broadcom BCM94352 HMB (AzureWave AW-CE123H) For BCM94352 download FakePCIID_BCM94352Z_as_BCM94360CS2.kext or Broadcom.kext (2015-11-02 and later versions) Copy FakePCIID_BCM94352Z_as_BCM94360CS2.kext or Broadcom.kext to /EFI/CLOVER/kexts/10.11 Restart. Bluetooth/Handoff Patch Name: IOBluetoothFamily Find: 4885FF7447488B07 Replace: 41BE0F000000EB44 Comment: 10.11 BT4LE Handoff Hotspot 5GHz AirPort Patch Select only one patch appropriate for your country. Name: AirPortBrcm4360 Find: 4183FCFF742C48 Replace: 66C7065553EB2B Comment: 10.11-BCM94352-5GHz-US-FCC-dv Name: AirPortBrcm4360 Find: 58 54 00 25 18 2B 21 00 20 Replace: 58 54 08 0A 32 1B 43 00 0A Comment: 5 GHz Fix for BCM94352HMB with XT country Name: AirPortBrcm4360 Find: 4183FCFF742C48 Replace: 66C7064445EB2B Comment: 10.11-BCM94352-5GHz-de You can change the country code as you like. Read this post to. #329 Tuning & Tips Bootscreen Glitch Fix Name: IOGraphicsFamily Find: 0100007517 Replace: 010000EB17 Comment: OS X10.10.x/10.11.x Boot graphics glitch Alternative patch: Name: IOGraphicsFamily Find: 0100007517 Replace: 0100007417 Comment: OS X 10.11 Second Stage Boot Glitch fix SSD TRIM If you have an SSD, be sure to enable TRIM. SSHD doesn't count as an SSD. See below. Clover method Terminal method Verify under System Information SSD Check TRIM Support: Yes SSHD As you can see, it's not like the SSD above. It (Seagate SSHD 500GB) uses an HDD and has it own access to the SSD inside. The controller probably has TRIM support. No need for TRIM patch for SSHD. TurboDisable/DisableTurboBoostBattery.kext (deprecated) This kext will increase battery life by disabling TurboBoost speeds on battery. Increases battery life by disabling TurboBoost speeds on battery. Since Clover Rev. 3350 there is an option TurboDisable. You can find it in CloverConfigurator 4.28.0+ under CPU Section. Rebuild Cache (for AppleHDA) Boot into Clover Press Spacebar. Boot without Caches. Run KextUtility. Reboot. Modding VoodooPS2Controller Sources http://www.insanelymac.com/forum/topic/282787-clover-v2-instructions Booting the OS X installer on LAPTOPS with Clover - Guide by RehabMan 10.11+ USB changes and solutions - Guide by RehabMan [Fix] 10.11.4 broken audio with AppleHDA injector (dummyHDA) - Guide by RehabManhttp://www.insanelymac.com/forum/topic/295587-power-management-for-sandyivy-bridgehaswell-cpus/ http://www.insanelymac.com/forum/topic/292542-airport-pcie-half-mini Updated: 19:08 Tuesday May 10, 2016
  23. I just upgraded my 10.9.5 Mavericks install on this laptop to 10.11.1 (posting this from the new install) I used the same technique as my Yosemite upgrade, which can be found here... http://www.insanelymac.com/forum/topic/300289-acer-aspire-4752-1095-guide-with-kextpack/page-2?do=findComment&comment=2170828 The only real difference is in the creation of the USB stick. The usual tool everyone uses creates a GUID EFI USB stick, which is unusable on this laptop... You will need to use Disk Utility to create a Sparse Image of the MAIN PARTITION, and then restore that usb.sparseimage to restore to MAIN PARTITION of OTHER MBR formatted Mac OS Extended (Journaled) USB stick. You can then safely install Enoch's custom Chameleon build onto this USB, and boot with csr_active_config=3 + Kernel_booter I hope to get a more thorough guide together when I find time... I am still using old SSDT/DSDT from Mavericks, and all is good, except: No Audio (obviously) No USB 3.0 (this will be challenging to fix) Computer restarts instead of shutting down (annoying, but hitting the power button quickly shuts it off instantly). More news as it happens...
  24. Run OS X El Capitan on a Dell Latitude E6320 This tutorial will describe the steps to install OS X El Capitan on a Dell Latitude E6320 i5 2520M. If you find any mistakes or have something to improve then please send me a PM and i will update the tutorial. A special thanks goes to Brian from Tech Erra, Jake Lo from OSX Latitude.com and Morpheousman for using parts of their tutorial I am from The Netherlands so sorry for my bad English. 1. Credits/Sources Everything OSx86-related is a collaborative effort amongst people who enjoy doing these things, as well as those of us who enjoy tweaking and experimenting with things. Below are a list of sources used to compile this guide: Tech Erra OSX86 Wiki InsanelyMac Forum member Jake Lo from OSX Latitude.com for helping me out with installing Morpheousman and Polyzargon from Insanelymac who helping me with my other topics. (Dell 780) MacPeet, Chris1111 and all other forum members who helping out the community. 2. Requirements Here are the requirements: A Dell Latitude E6320 i5 2520M – This is necessary to install OS X El Capitan for this tutorial A copy of Mac OS X – This can be in the form of an existing hackintosh, a virtual machine within Windows or Linux, or even a regular Mac. If you don’t have any of these things, then find someone who can help you out for a while. I prefer using a hackintosh with OS X Yosemite. Using an already working copy of Mac OS X either in a VM or a native hackintosh install is HIGHLY recommended. A 8GB USB flash drive (or larger) – We’ll be copying the files to the drive appropriately, so make sure that you have a flash drive with enough storage space (8GB or larger). A copy of OS X El Capitan – The method used by this guide requires that you have a copy of the OS X El Capitan Installation app, wich is available for free from the Mac App Store. 30-60 minutes of time – Depending on how tech-savvy you are, this may be quick, or it may take a while. An SSD or HDD to install 10.9 to – For me, I used a 250GB partition to install 10.9 to. An Wireless N Nano USB Adaptor – For use with wifi Highly recommended. I use a TP-LINK TL-WN725N adaptor. E6320.zip – This ZIP file contains everything that you need to get your flash drive properly prepared. 3. My Specs My installation was successfully done on an Dell Latitude E6320 i5 2520M Laptop computer with the following specs. NOTE: A Wireless N Nano USB Adaptor is recommended to use the full potential of OS Mavericks because the on board wifi doesn't work. - Intel Core i5-2520M @ 2.5GHz, 3MB cache, Dual Core - 4GB DDR3 1333Mhz RAM - Western Digital 250GB HDD - INTEL HD3000 Video - Intel 825xx onboard network - Bluetooth radio onboard (works OOB) - IDT 92HDxxx HD audio onboard - TL-WN725N Wireless N Nano USB Adaptor - Apple Magic Trackpad (only @home) - Apple Wireless Keyboard US (only @home) - Apple Magic Mouse 4. Download OS X El Capitan Start OS X Yosemite on a exsisting Mac or Hackintosh, to prepare your USB Flash drive. Make sure to backup the files that are already on your USB Flash drive thru disk Utility in Mac OS X. Open Mac App Store. Login with your Apple ID. Download OS X El Capitan Done! The application INSTALL OS X El Capitan will appear in /Applications. 5. Prepare Bootable USB Installer Now, we need to prepare the USB Drive so that it will properly bootup on your PC. I recommend using Chris1111'S app for creating your USB Installer. It is a great timesaver! Download App Here[/url Follow the instructions in the first Post for creating USB Installer. Select Installer OS X El Capitan and Install in ESP (see image below) Select Install. This step may take some time, good time to get a drink. After App is finished, you will see a EFI Partition of USB installer on your desktop. Open EFI Partition, then open EFI folder, copy and paste the Clover folder from the zip file, to the EFI folder, choose replace folder. Download the latest version of Clover Bootloader and copy it to the root of your USB installer. USB Installer is Done! 6. Bios Settings Dell Latitude E6320 Before we boot from the Dell Latitude we need to optimize the bios for OS X El Capitan. Start your Dell Latitude and press F2 to get into the Bios. In the main screen click on "Load Defaults", the bios will be reset to default settings. Go to General - Boot Sequence and choose on the right for USB Device and click the up arrow so that the USB Device is on top, click on apply to make the setting. Go then to System Configuration - SATA Operation and choose on the right for AHCI click again on apply and choose exit, now the Bios is ready for installing OS X El Capitan. 7. Installing OS X El Capitan from your USB drive Time for the fun stuff! We’ll now boot from your USB drive and install OS X El Capitan onto the Hard Drive. Using a USB 4G flash drive will help things out quite a bit. Power on unit while tapping F12 Key to choose boot device, select USB device. When Clover boot screen is visible, choose boot "Mac OS X from El Capitan USB Installer". The system will then boot into OS X installer For a new installation of OS X, you must erase and format the destination drive according to the following steps before continuing. If you are upgrading from Lion, Mountain Lion, Mavericks or Yosemite and you want to keep your files and apps, skip steps a-j. A. Choose Disk Utility B. Highlight your target drive for El Capitan installation in the left column. C. Click Partition tab D. Click Current and choose 1Partition E. Click Options.... F. Choose GUID Partition Table. G. Under name: Type El Capitan (you can change it later if desired). H. Under Format: Choose Mac OS Extended (Journaled). I. Click Apply the Partition. J. Close Disk Utility. When the installer asks you where to install, choose El Capitan Hard Drive. Upon completion, system will restart a 1st time. Press F12 key to choose the boot device. When the Clover Boot screen is visible, Choose your El Capitan Hard Drive. You will eventually get to the setup screens for OS X El Capitan. Go through the setup process to setup OS X El Capitan. Choose at "How do i connect to the internet " ..."My Computer Does Not Connect to the Internet", we will fix this later, go further with the setup process. The setup process will take about 3 minutes. Done! 8. Adjust some settings in OS X 10.11 Once in 10.11 go to finder – preferences – General and choose in "show these items on the desktop" for Hard Disk External Disk CD Go also to System Preferences – Security& Privacy click on the lock icon in the lower left corner and type your password. Choose by “Allow applications downloaded from": click on "Anywhere" Close system preferences. 9. Installing The Clover Bootloader on Your Hackintosh The following instructions may appear a bit oversimplified, but we are trying to keep it simple for first-time Clover Bootloaders users. Copy the Clover Installer from the root of your El Capitan USB Installer to your desktop. Open Clover Package installer. Hit Continue, Continue, Change Install Location... Choose your HD, now called El Capitan and press Continue (see images below) Hit Customize and install clover with the following Custom Install settings (see images below) After installation of the Clover Bootloader, the EFI Partition of your El Capitan Hard Drive should be mounted on your desktop. Copy the Clover folder from the zip file into your El Capitan EFI Partition > EFI Folder. Make sure to choose to Replace the Clover folder. In Tools Folder of the zip file, Open Clover Configurator. Click File, Open File and select config.plist in EFI/EFI/Clover. Click on SMBIOS in left side pane and create your new SMBIOS (iMac 8.1) with Random Serial Number. Close Clover Configurator and save changes. Finished! Now remove the USB Installer and reboot into OS X El Capitan. 10. Install Wlan driver for the TL-WN725N The wireless lan on the Dell E6320 doesn’t work, therefore I use a Wireless N USB Nano Adaptor from TP-LINK. The software is straight forward and installs without problems, the only thing is that after login the wireless app starts up and you have must close it every time, therefore I have made a script to launch the program after login and close it after 5 seconds. For installing the driver go to the folder “E6320 – Wlan_TP-LINK”. Launch the Installer.pkg and install the software, after install you will get the message to restart. Choose restart to restart you laptop. After restart the software will start the Wireless App. Choose you desired network and add it to your profile. Now we can install the login script. Go to “System Preferences – Users & Groups”, go to tab Login Items. Choose the + sign and browse to the folder “Install_E6320 - Wlan_TP-LINK” and choose “Wireless App2”. Close System Preferences. 11. iMessage & FaceTime Fix You will need MLB and Rom numbers from a legit Mac device that is onthe mac server. Run iMessage debug on a iMac, Macbook, etc and make a copy and paste of the Terminal output. Open Clover Configurator. Mount EFI Partition. Import config.plist from EFI/EFI/Clover (File , import configuration, browse to config.plist and select). In Clover Configurator Click on RT Variables, Enter Rom and MLB Values from iMessage output from valid iMac device. Save changes to config.plist. Reboot, Sign into iMessage iMessage and FacTime should now both be working. 12. What's working? Just about everything. 13. Finished! You’ve successfully installed OS X El Capitan onto your Dell Latitude E6320. TROUBLESHOOTING 14. BOOT 0 ERROR If you are using a 4k HDD you can get boot:0 error, to solve this issue do the following Reboot system back into El Capitan installer (USB)FLASH DRIVE). Run Disk Utility find the Disk Identifier (eg. disk0s2). Unmount the drive you installed Mavericks on Launch Terminal and execute the following command: dd if=/usr/standalone/i386/boot1h of=/dev/disk0s2 . Exit Terminal Boot Normally 15. 16 Message "attempted to boot into EFI while legacy is on". Sometimes the above message will appear after formatting HDD and installing OS X. Reboot system back into El Capitan installer (USB)FLASH DRIVE). Run Terminal. Launch Terminal and execute the following command: sudo diskutil corestorage revert / When prompt type your password. Exit Terminal Boot with your USB to El Capitan Launch Terminal again and execute the following command to format EFI partition: sudo newfs_msdos -V EFI -F 32 /dev/rdisk0s1 After that install Clover to your HDD see chapter 10 "Installing The Clover Bootloader on Your Hackintosh" Done ! run os x el capitan 10.11 E6320.pdf
  25. [GUIDE]AsRock extreme 4 970/AMD/Nvidia

    HI. I've been struggling getting mac working on my machine, and I've got it to work! Now, I'm going to post step by step, everything that I've done in order to make it work(maybe there are others that are trying to get this baby work. Mbo: AsRock extrem 4 970. cpu: AMD FX 6350 GPU: nvidia gt 630 (going to upgrade shortly) ram: 12 gb hdd: 120 gb ssd, and some other mechanical hard drives. I've downloaded niresh distro (not vanilla yada yada, but it works!), booted with /amdfx -v -x npci=0x3000 At the installer, I unchecked laptop box, and ethernet box, from kexts(only fakesmc and sound), and checked npci=0x3000, GraphicsEnabler=Yes USBBusFix=Yes I completed the installer, and booted from usb(legacy mode) with the following flag: msibase=0x90 Downloaded RealtekRTL8111.kext, installed through kext utility, and downloaded nvidia driver from their website. Everything seems to work, even dual screen(both on hdmi)! (for sound, you'll have to go to settings, voodooHDA, and get the noise down to 0, to kill the continuous beeping). If you have any questions, feel free to ask!
×