Jump to content
TallCoolOne

Sleep mode on Gigabyte Z170X Gaming 5

20 posts in this topic

Recommended Posts

Hey all,

I got my Sierra hackinotsh mostly working perfectly including audio, nvidia gfx, power management, etc.

Shutdown works fine but sleep mode does not. It goes to sleep but then wakes up within a few seconds on its own.

I have tried the SlpSmiAtWake option in Clover, that is what enabled it to get past being able to wake from sleep at all, but cant seem to figure out why it wont stay asleep.

Any ideas?

thanks!

 

Share this post


Link to post
Share on other sites
Advertisement

Hey all,

I got my Sierra hackinotsh mostly working perfectly including audio, nvidia gfx, power management, etc.

Shutdown works fine but sleep mode does not. It goes to sleep but then wakes up within a few seconds on its own.

I have tried the SlpSmiAtWake option in Clover, that is what enabled it to get past being able to wake from sleep at all, but cant seem to figure out why it wont stay asleep.

Any ideas?

thanks!

hello, I have the same motherboard, you'd be so kind to explain how you got it?

Share this post


Link to post
Share on other sites

are you using nullcpupowermanagement? i heard that breaks sleep on some board. have you tried the flag darkwake=0 

 

Nope not using nullcpu, and yes I have tried darkwake=0 since I think I read it as a possible solution on a thread. What exactly do those values mean? should I try a different one?

Thanks!

hello, I have the same motherboard, you'd be so kind to explain how you got it?

 

Where exactly are you getting stuck?

Share this post


Link to post
Share on other sites

Are you using a water cooler? I have the same board and sleep wakes up for me straight away because I have the usb header plugged in for my water cooler and power supply.

 

Sent from my SM-G900I using Tapatalk

Share this post


Link to post
Share on other sites

Nope not using nullcpu, and yes I have tried darkwake=0 since I think I read it as a possible solution on a thread. What exactly do those values mean? should I try a different one?

Thanks!

 

Where exactly are you getting stuck?

network and audio not work with sierra

Share this post


Link to post
Share on other sites

Are you using a water cooler? I have the same board and sleep wakes up for me straight away because I have the usb header plugged in for my water cooler and power supply.

 

Sent from my SM-G900I using Tapatalk

 

I am actually, the Corsair H100i v2, and I do have the USB connection on it. Perhaps that is it. What does the USB connection on that even do? I'm guessing there is software for monitoring it through Windows...is it required?

Thanks a bunch, much appreciated!

network and audio not work with sierra

 

For network I used IntelMausiEthernet v2.2.0, and I am using the bottom ethernet port on the motherboard, I have not tested if the top one works.

For audio I used ALC1150 option, then ran toledo's script, the 120 version from here:

https://www.tonymacx86.com/threads/audio-realtek-alc-applehda-guide.143757/#post886744

 

Edit: Oh before running toledo's script I also added this to ACPI,  DSDT Patches section in Clover Configurator:

 

Comment: Rename HDAS to HDEF

Find: 48444153

Replace: 48444546

Share this post


Link to post
Share on other sites

I am actually, the Corsair H100i v2, and I do have the USB connection on it. Perhaps that is it. What does the USB connection on that even do? I'm guessing there is software for monitoring it through Windows...is it required?

Thanks a bunch, much appreciated!

 

 

For network I used IntelMausiEthernet v2.2.0, and I am using the bottom ethernet port on the motherboard, I have not tested if the top one works.

For audio I used ALC1150 option, then ran toledo's script, the 120 version from here:

https://www.tonymacx86.com/threads/audio-realtek-alc-applehda-guide.143757/#post886744

 

Edit: Oh before running toledo's script I also added this to ACPI, DSDT Patches section in Clover Configurator:

 

Comment: Rename HDAS to HDEF

Find: 48444153

Replace: 48444546

Yes in widows there is software for setting fan curves and monitoring. If you need your pc to sleep then you can unplug the usb from it.

 

Sent from my SM-G900I using Tapatalk

There is actually a whole lot of information on this board in another thread on this forum.

 

Sent from my SM-G900I using Tapatalk

http://www.insanelymac.com/forum/index.php?/topic/309352-El-Capitan-on-GA-Z170X-Gaming-5

 

Sent from my SM-G900I using Tapatalk

Share this post


Link to post
Share on other sites

I am actually, the Corsair H100i v2, and I do have the USB connection on it. Perhaps that is it. What does the USB connection on that even do? I'm guessing there is software for monitoring it through Windows...is it required?

 

I don't know the role of this port, but from your description, I understand the water cooler is connected to one of the internal USB2 ports (2 ports hub attached to HS08 or HS11 or HS12).

From my experience, a good sleep requires that this port is defined as internal (type 255) in the USB injection method you use.

 

Another solution would be enabling SuspendOverride in DSDT section of Clover's config.plist

Share this post


Link to post
Share on other sites

I don't know the role of this port, but from your description, I understand the water cooler is connected to one of the internal USB2 ports (2 ports hub attached to HS08 or HS11 or HS12).

From my experience, a good sleep requires that this port is defined as internal (type 255) in the USB injection method you use.

 

Another solution would be enabling SuspendOverride in DSDT section of Clover's config.plist

 

Interesting, ok I will definitely try both of those, thanks for the suggestions.

 

On the topic of USB injection, I'm in the process of making my own SSDT for USB (currently just using the port limit expansion patch), I have most of the ports mapped out except the USB 3.1 port (not type-c). My USB3 device shows up on the Mac when I plug it in there, and I can find it in IORegistryExplorer under IOResources/AppleUSBHostResources, but not in the XHC section. According to IOResources it is on AppleUSBXHCI@00000000, whereas all my other ports show up under AppleUSBXHCI@14000000. So all my entries for the other ports are under PCI0@0/AppleACPIPCI/XHC@14, shouldn't there also be an XHC@00 somewhere with this port?

Share this post


Link to post
Share on other sites

On the topic of USB injection, I'm in the process of making my own SSDT for USB (currently just using the port limit expansion patch), I have most of the ports mapped out except the USB 3.1 port (not type-c). My USB3 device shows up on the Mac when I plug it in there, and I can find it in IORegistryExplorer under IOResources/AppleUSBHostResources, but not in the XHC section. According to IOResources it is on AppleUSBXHCI@00000000, whereas all my other ports show up under AppleUSBXHCI@14000000. So all my entries for the other ports are under PCI0@0/AppleACPIPCI/XHC@14, shouldn't there also be an XHC@00 somewhere with this port?

 

You may have a look at this injector : https://files.macg.co/macgupload/1473833650-16437614854540.zip. The archive contains pictures identifying the ports.

 

You will have to adapt the kext's info.plist to your particular needs :

- change the two references to "iMac17,1" to what fits your SMBIOS setting

- as said before, change port type to 255 where needed

- (optional but recommended) in order to limit yourself to what macOS natively supports (15 ports), remove references to unneeded ports (and remove the current patch to bypass the limit)

 

 

You are right, the USB3.1 ports aren't under XHC@14.

They seem to be handled independently (so they don't count in the 15 ports limit) and I did not have to explicitly inject them to have them appear in System Information (with a USB3.0 speed limit).

They don't seem to be very reliable with current versions of macOS though.

Share this post


Link to post
Share on other sites

You may have a look at this injector : https://files.macg.co/macgupload/1473833650-16437614854540.zip. The archive contains pictures identifying the ports.

 

You will have to adapt the kext's info.plist to your particular needs :

- change the two references to "iMac17,1" to what fits your SMBIOS setting

- as said before, change port type to 255 where needed

- (optional but recommended) in order to limit yourself to what macOS natively supports (15 ports), remove references to unneeded ports (and remove the current patch to bypass the limit)

 

 

You are right, the USB3.1 ports aren't under XHC@14.

They seem to be handled independently (so they don't count in the 15 ports limit) and I did not have to explicitly inject them to have them appear in System Information (with a USB3.0 speed limit).

They don't seem to be very reliable with current versions of macOS though.

 

Ahhh I had just finished mapping all mine out manually...well at least it confirms I go them all right :)

Interesting this is in the form of a kext, I was making an aml file using MacAISL based on the steps I had found...this should be quicker though...

 

Finally, I've been using iMac14,2 because I had read it was more problem free, since 17,1 is an actual Skylake CPU would I gain anything by switching to it (or lose anything)?

I think I read somewhere I would have more CPU states for power management...I tried making making my own SSDT for that but I'm not sure it's working...perhaps because of the board id not matching? I just said continue in the ssdtPRGen script.

 

Thanks for all the help!

Share this post


Link to post
Share on other sites

Ahhh I had just finished mapping all mine out manually...well at least it confirms I go them all right :)

Interesting this is in the form of a kext, I was making an aml file using MacAISL based on the steps I had found...this should be quicker though...

I'd be interested to see at least a sample of your aml file… Comparing different approaches is always interesting.

 

Finally, I've been using iMac14,2 because I had read it was more problem free, since 17,1 is an actual Skylake CPU would I gain anything by switching to it (or lose anything)?

I think I read somewhere I would have more CPU states for power management...I tried making making my own SSDT for that but I'm not sure it's working...perhaps because of the board id not matching? I just said continue in the ssdtPRGen script.

You can download my configuration and track my progresses on Github.

 

Initially, I tested iMac17,1 but chose to switch to 14,2, because I want my macOS install to remain as "vanilla" as possible, and solutions to the "dark screen" issue caused by the 17,1 SMBIOS would have required messing inside the System/Library/Extensions folder.

 

For the time being, I see no reason to prefer 17,1. It required exactly the same steps (1 and 2) to get native power management, and performance appears to be identical.

 

I am almost 100% satisfied with my current setup. Wakes from deep sleep will require more work, but I am sure I 've got a solution : I just want to be sure I have a clear comprehension of what is required and what is optional.

Share this post


Link to post
Share on other sites

I'd be interested to see at least a sample of your aml file… Comparing different approaches is always interesting.

 

You can download my configuration and track my progresses on Github.

 

Initially, I tested iMac17,1 but chose to switch to 14,2, because I want my macOS install to remain as "vanilla" as possible, and solutions to the "dark screen" issue caused by the 17,1 SMBIOS would have required messing inside the System/Library/Extensions folder.

 

For the time being, I see no reason to prefer 17,1. It required exactly the same steps (1 and 2) to get native power management, and performance appears to be identical.

 

I am almost 100% satisfied with my current setup. Wakes from deep sleep will require more work, but I am sure I 've got a solution : I just want to be sure I have a clear comprehension of what is required and what is optional.

 

I couldn't get mine to work with the kext USB you sent me, I made the edits for 14,2 as well as the ports but I would only get USB 2.0 ports (HSxx). I got USB working with the aml approach though, and I tried the value of 255 for the port where the cooler is connected but it still wakes up right away after sleep.

 

Here is my USB dsl source file as well as the aml: https://d.pr/ETmC

 

I will take a look at your power management setup, thanks!

Share this post


Link to post
Share on other sites

I've had a similar problem where the system wakes up immediately after sleep. Later I found out, that the first sleep right after booting is always successfully. However, the second and subsequent sleeps will depend on how the system was waken last time.

If the system is waken by a key press or mouse/trackpad click, the next sleep would always fail with this problem.

If the system is waken by pressing the power button on the case, the next sleep is always successful.

I don't use DSDT/SSDT, and 17,1 SMBIOS is used. USBInjectorAll.kext is used with HS08 for BRCM20702 BT changed to 255.

Share this post


Link to post
Share on other sites

Thought I would post an update here for anyone else looking into the same issues.

My sleep mode is working fine now, I just disabled HS08 (the port where the H100i is connected) in the boot options in clover. If I want to change the Corsair Link config now I can't use VMware anymore (since the port is disabled) but I can boot into Windows to do so. I never really need to change the settings anyway after setting them.

I connected the H100i pump directly to the CPU_FAN motherboard header and the fans (using a Y cable) to the CPU_OPT header. I then set the pump to Full Speed in the BIOS and CPU_OPT to Normal. I found the fans were firing up a lot though and can be quite loud, so I installed Macs Fan Control to set them to turn on only when the CPU goes above 40C. This keeps the machine nice and quiet most of the time.

My sound doesn't work after wake from sleep but I have found quite a bit of info on that and will look into the various options next.

Share this post


Link to post
Share on other sites

Sounf after sleep dont working with AppleALC and Codec commander. 

A have same MB and sleep working like it should. 

I dont use USBInjectAll.kext, maybe problem in kext? 

 

I got my sound working after sleep, the only other issue I had was my USB drives being ejected on sleep, used SafeSleepUSB and that works now too.

 

I used Codec Commander for audio after sleep, it is working for me. I can PM you my kext for you to try when I get home later.

Share this post


Link to post
Share on other sites

Thought I would post an update here for anyone else looking into the same issues.

My sleep mode is working fine now, I just disabled HS08 (the port where the H100i is connected) in the boot options in clover. If I want to change the Corsair Link config now I can't use VMware anymore (since the port is disabled) but I can boot into Windows to do so. I never really need to change the settings anyway after setting them.

I connected the H100i pump directly to the CPU_FAN motherboard header and the fans (using a Y cable) to the CPU_OPT header. I then set the pump to Full Speed in the BIOS and CPU_OPT to Normal. I found the fans were firing up a lot though and can be quite loud, so I installed Macs Fan Control to set them to turn on only when the CPU goes above 40C. This keeps the machine nice and quiet most of the time.

My sound doesn't work after wake from sleep but I have found quite a bit of info on that and will look into the various options next.

 

I have almost the same hardware with you. Initially when I shutdown my machine, it will restart after a few seconds, and I fix this by checking "fix shutdown" in clover configrator. Everything else is working perfect except this sleep problem. 

 

You said that you fixed this problem by disable HS08, but I don't have a H100i connected, how can I fix this?

 

Would you please show me you bios configration and clover config file? Or any advice?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By tluck
      Lenovo T460 macOS with Clover Guide
      Release v2018.06.05 on GitHub Updated to Clover r4513 Updated Lilu.kext - supports both Sierra and High Sierra Updated AppleALC.kext - supports both Sierra and High Sierra + added back DVMT patch for 10.13.2+ Updated VoodooPS2Controller.kext (RehabMan version) + SSDT updates for T460 Added Frank's T470p DSDT files
        Various Tweaks over Last months The zip file is a complete Clover ESP (/EFI) bundle and kext pack for the Lenovo T460. The current file bundle is tested on Sierra. 
      Note: I never got the GFX fully working on El Capitan. 
      Full Clover file set - config.plist etc. Includes all custom kexts Includes custom DSDT/SSDT scripts and patches Utility scripts The zip bundles are posted to GitHub: https://github.com/tluck/Lenovo-T460-Clover/releases
      Caveat: The T460 systems used here was configured with: i5-6300U, Intel HD Graphics 520, 1920x1080 touch screen. If you have a different system model, then extract the ACPI files and use the included scripts to create a set of files consistent with your system type and BIOS version. See below for details.
      Credits: RehabMan, Shmilee, vusun123, TimeWalker, Mieze from which, much of their work and help is/was was used to get the T460 to this point.
      Devices and aspects working:
      Ethernet -  Intel I219LM is enabled via IntelMausiEthernext.kext WiFi/BT - substitute the Intel WiFi/BT with a compatible Broadcom or Atheros chip Audio - ALC293 codec implemented via AppleALC.kext (old AppleHDA_ALC293 and CodecCommander kexts are not needed) PS2 - ClickPad + TrackPoint + all 3 buttons - using a modified VoodooPS2Controller to support new layouts - and added some custom Fn key maps based on 440/450 dsdt USB - implemented via custom SSDT + USBInjectAll kext. All USB3/USB2 ports are intel-based and work -  3 external USB and internal Camera, BT, etc  Sleep/Wake - the sleepwatcher package and custom sleep/wake scripts are used to help with sleep/wake for BT and PS2 devices. Note: have not tried to implement the SD card reader - no driver found.
      ACPI Files
      New Installation - Steps and Details
      Part 1 - OS Installation
      Part 2- Post OS Installation and Setup
      Notes on Custom Kexts
       
    • By frenzycoder
      Hi, 
       
      I try to get a notebook working vanilla. 
       
      I used clover and patched DSDT.aml to get it booting. Now I have power-management issues and sound left. 
      Sound is more important for me at the moment.
       
      My notebook has following hardware: 
      Realtek ALC269 @ Intel Skylake PCH-H 
       
      lspci on ubuntu said: 
      00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
       
      id: multimedia description:  Audio device product:  Sunrise Point-LP HD Audio vendor:  Intel Corporation physical id:  1f.3 bus info:  pci@0000:00:1f.3 version:  21 width:  64 bits clock:  33MHz capabilities:  pm msi bus_master cap_list configuration: driver = snd_hda_intel latency = 32 resources: irq : 128 memory : df120000-df123fff memory : df100000-df10ffff  
      What would be the best way to install it? 
      Is it possible to do it only with EFI/Clover or do I have to touch /L/E? 
       
       
    • By Cyberdevs
      Installing macOS® Sierra® on Gigabyte GA-Z170X-Gaming 5 rev 1.0
      Intel® Core i7 6700K
      nVidia® Graphics Maxwell® or Pascal®
      Disclaimer:
      This guide will assume that you know what you are doing and also assumes that you have already made a backup of your data before making any changes to your hardware or software. If you have not made a backup STOP HERE! and create one.
      I will not be held responsible for any data loss or any damage you might cause to your computer in the process of installing macOS® on your computer.
      By following this guide, you acknowledge that installing Mac OS X® and macOS® on any hardware that is not produced by Apple® is illegal and you will be responsible if you break any laws.
      All the trademarks and copy rights belong to their respective owners.
      This guide is only for your personal use and your information, therefore if you break any laws by using this manual you will be responsible for it not me. Any commercial use of the contents of this guide is prohibited.
      If I forget to mention your name or someone else’s name in the credits section forgive my negligence and feel free to contact me and I will add your name/s.
      This guide is written specifically for the hardware specifications I’m using, but the principal in general might apply to other hardware with similar specs with the exception of DSDT and SSDT files.
      Important Notes:
      1. Always backup your data before making any changes to your hardware or software.
      2. Always keep a bootable Clover USB disk with the latest working configurations just in case.
      3. I suggest you use another bootable USB for testing and not to edit the EFI folder on the hard drive.
      4. Preferably use the latest BIOS (F21 at the time of writing) version and the latest version of Clover EFI bootloader (4077 at the time of writing).
      5. There are two main versions of Clover EFI bootloader available in this package. One for the users with a nVidia GPU and the other one is for the users with IntelHD 530 GPU.
      6. So many parts of this tutorial are universal and they apply to all Hackintosh and Apple computers, like creating the Bootable USB disk drive or mounting the EFI partition. So, you can use them on all the computers that run macOS or even use them for installing macOS on other Hackintosh computers.
      7. The config.plist, the DSDT.aml file and the SSDT tables are specifically created for the GA-Z170X-Gaming 5 motherboard so do not use them on other hardware because they simply won’t work or even if they do you might experience some problems and errors.
      8. This tutorial is based on my personal experience. So, you might need to make some extra adjustments.
       
      Downloading the macOS® Sierra installer from App Store:
      Download the version of macOS® you want to install on your computer from App Store, macOS® Sierra. For downloading the macOS® installer you’ll need an Apple® computer or a working Hackintosh and a valid Apple ID. Although downloading macOS® Sierra® doesn’t require an Apple ID but if you are going to use your Hackintosh for day to day use you’re going to need a valid Apple ID.
      You can download the macOS® Sierra® installer by using the link below:
      macOS® Sierra® 10.12.5:
      https://itunes.apple.com/us/app/macos-sierra/id1127487414?mt=12&ls=1
      You can also use App Store directly for downloading it. The “Install macOS® Sierra.app” will be saved to the following path once downloaded: /Applications/
       
      Creating bootable USB Disk for macOS®:
      Plug in a USB flash drive (8Gb or larger) and launch disk utility to format the flash drive.
      To create a bootable USB drive for macOS®, everything must be exactly as shown in the picture below.
      Once you successfully formatted the flash drive, open Terminal from /Applications/Utilities:
      Copy and paste the following command into terminal without the “”:
      For macOS® Sierra®:
      “sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --applicationpath /Applications/Install\ macOS\ Sierra.app —nointeraction”
      Press return/enter to run the command. You’ll be asked to give your password and once you type your password press return/enter and the process will start.
      Depending on the speed of the USB drive you are using it will take about 5 to 30 minutes to complete the process. It took about 5 minutes on my computer to create the bootable disk on a USB 3.0 flash drive.
       
      How to mount the EFI partition using command line:
      Launch the terminal application again if you closed it previously.
      Type “diskutil list” and press return/enter
      You’ll see list of all the Internal and the external hard drives 
      Type “diskutil mount /dev/diskXsX” and press return/enter
      First X is the number of the disk and the second X is the number of the partition
      In this case the command will be:
      e.g. diskutil mount /dev/disk2s1
      Now you can see the EFI partition of disk6 is mounted on the desktop, if you can’t see the partition on the desktop you can find it in finder window’s “Sidebar” under “Devices”

      BIOS Settings:
      Now it’s time to configure the BIOS before installing macOS®.
      First of all, it’s better to “Load Optimized Defaults” settings on the BIOS so we could start from scratch without having any misconfigurations.
      You need to make the following changes to get macOS® working on your pc:
      BIOS:
      Fast Boot = Disabled
      Windows 8/10 = Windows 8/10 WHQL or Other OS
      CSM Support = Disabled
      Secure Boot = Not Active
      Attempt Secure Boot = Disabled
      Peripherals
      Initial Display Output = PCIe 1 Slot (Only If you are using a nVidia GPU, if you are using an AMD GPU you’ll need to enable IGFX and set it to primary in order to boot into macOS® Sierra®)
      Trusted computing, Security Device Support = Disable
      Super IO Configuration, Serial IO = Disable
      USB Configuration, Legacy USB Support = Enabled
      USB Configuration, XHCI Hand-off = Enabled
      USB Configuration, USB Mass Storage Drive Support = Enabled
      USB Configuration, Port 60/64 Emulation = Enabled
      SATS And RST Configuration = AHCI
      Chipset
      VT-d = Disabled (If you need it add “dart=0” flag to config.plist under Boot section)
      Internal Graphics = Disabled (Only If you are using a discreet GPU if you are using an AMD GPU you’ll need to enable IGFX and set it to primary in order to boot into macOS® Sierra®)
      In Chipset, IOAPIC 24-119 Entries = Disable
      If you are using Intel Graphics or IGFX
      In Chipset, Internal Graphics = Enabled 
      In Chipset, DVMT Pre-Allocated = set it to 64 
      In Chipset, DVMT Total Gfx Mem = set it to max
      Save and Exit.
       
      Installing Clover EFI Bootloader:
      In order to boot successfully into macOS® you’ll need to install a Bootloader on the drive you are using as the main bootable device whether is a flash drive or a hard disk drive.
      There are number of bootloaders that could be used to boot up the macOS® on a PC computer or a Hackintosh but we will only use Clover EFI Bootloader and here is how to properly install and configure Clover EFI Bootloader on your computer.
      In this section, we will be installing the UEFI version of the Clover so if you are using the Legacy BIOS version for whatever reason this guide is not for you.
      You can download the latest version of Clover EFI Bootloader from:
      https://sourceforge.net/projects/cloverefiboot/
      As I mentioned before in the first page of this manual the latest version of the Clover EFI Bootloader is Clover_v2.4k_4077.
       
      Stage 1:
      Once you have downloaded the bootloader double click the installer package to start the installation process. The process will only take few minutes and after that you need to customize or optimize the contents of the EFI partition which you’ve installed clover into. Please make sure you select the USB drive you created earlier as shown below and not the HDD of the computer you are using.
      If you see the following dialog after double clicking the installer package, all you need to do is to right click on the Clover_v2.4k_r4077.pkg and from the menu select open and once more click the open button. 
      Click continue and read the “Important Information” or not and then click continue once more.
      You need to select the location that you want to install Clover EFI Bootloader to.
      Make sure that you are installing clover to the right location, basically you must choose the drive that you have installed macOS® Sierra® onto unless you want to install the bootloader on another drive, say a flash drive.
      Now you need to customize which components of the bootloader to be installed, if not you won’t be able to boot into macOS® at all.
      Check the following items and then click install:
      1. Install for UEFI booting only (Unified Extensible Firmware Interface)
      2. Install Clover in the ESP (EFI System Partition) or (Extensible Firmware Interface System Partition)
      3. Install can also choose a theme for your clover bootloader and the CloverThemeManager.app to change or modify the themes later.
      4. Install Drivers64UEFI that apply to your system you will need at least these two drivers:
      1. EmuVariableUefi-64
      2. OsxAptioFix2Drv-64
      You can also choose other drivers if they apply to your computer and if you need them, otherwise you’re good to go.
      5. You can also install the RC script on the target volume to enable the shell command prompt in clover’s boot screen.
      Once the installation is started, the EFI partition of the hard disk or USB drive that you are installing clover to will be mounted on the desktop, if you can’t see the partition on the desktop you can find it in the finder window’s “Sidebar” under “Devices”
       
      Stage 2:
      In this stage, you need to configure the config.plist and the other components on the EFI partition either by modifying the config.plist inside the /EFI/Clover/ folder using “TextEdit” or any other text editor application that you like or using “Clover Configurator” (recommended) application which has a GUI for editing the config.plist and it has some other useful built-in apps such as EFI mounter or a Base64 to HEX converter etc. or you can just simply replacing the “Clover” folder with the one that is provided with this guide.
      At this moment you might not be familiar with all the settings and options inside the config.plist file and Clover Configurator, no need to worry.
      You can easily replace the whole “Clover” folder inside the “EFI” folder on the EFI partition of your bootable disk (hard disk drive or USB flash drive) with the folder included with this guide and you’ll be good to go as along as your main components specifically your CPU and GPU are the same as mine.
      Otherwise you might need some additional settings and flags to be added to the config.plist.
      For instance, if you are using a NVMe SSD disk drive you’ll need to add proper patches in order to get it to work.
      You can find more about clover and its settings at:
      https://clover-wiki.zetam.org/Home
       
      and you can find “Clover Configurator” at:
      http://mackie100projects.altervista.org
       
      How to enable kext using Clover EFI Bootloader:
      In this section I will briefly explain how to install kexts that are needed to make your macOS® work more properly and efficiently.
      As you know all the hardware components in a computer need a so called “Driver” to operate correctly in the operating system.
      The same principle applies to macOS® and Mac OS X®. We call them “Kext” files or “Extension” files.
      By default, Apple provides all the required kext files with the operating system to run on a legitimate Apple computer.
      On the other hand, on a Hackintosh you need to install some extra kext files created by the community to obtain full functionality of your computer. You can either install them directly to “System/Library/Extensions” folder of macOS® Drive or you can place them into the EFI folder on the EFI partition of your bootable drive, which is a better way because if those files are the modified version of an original kext file that Apple is provided after each major update they will be replaced is the OS and you’ll lose the functionality of that particular component or more components.
      For example, Maxwell and Pascal GPUs have the “Boot to black screen” issue with some SMBIOS settings like iMac17,1, iMac15 and MacPro 6,1 system definitions. It means if you use one of those system definitions your computer will show a black screen after loading macOS® even after installing the nVidiaWebDrivers.
      So, you’ll need to either change the SMBIOS definition or you need to patch the “AppleGraphicsDevicePolicy.kext” to avoid the black screen.
      Once you patch the file with whatever method, if you install macOS® update you’ll need to apply the patch all over again.
      Besides changing the system files in macOS® will mix up the file permission of the files and if it’s not properly installed or if you forget to fix the permission of the files you might render the whole operating system useless and you’ll need to either fix the permissions on the /System/Library/Extensions or for short /S/L/E or you might need to reinstall the whole operating system from scratch. 
      For each version of macOS®, there is a folder inside the following path:
      /EFI/Clover/kext/
      So, you can copy the kexts you need inside the folder that correlates with the version of macOS® you are using.
      Even if you update the OS, the files inside that path won’t get changed.
      How to properly adding kext file to /System/Library/Extensions:
      There are several ways to install additional kexts on macOS, but I will only discuss two methods that are the easiest ways to install kext without having to type any commands in terminal.
       
      Using Kext Utility:
      By using kext utility you can easily install kext files inside /System/Library/Extension.
      All you have to do is to open the Kext Utility app, type in your password and drag the kext file you want to install into the app’s window and it will install them in to the path give above. The good thing about this app is that it will automatically repairs the permission of the /System/Library/Extension folder and the kext files inside it.
      Once the process is done you can reboot the system and see the results.
       
      Kext Wizard:
      Kext wizard is another handy tool with more functions built into it, you can select the path for installing the kexts files even to another operating system on another volume.
      You can repair the permissions and rebuild system kext cache. You can even load kexts files and test them or list the kext that are already loaded in the system.
       
      Post Installation:
      To have a fully functional Hackintosh you need to add the following kext files and DSDT/SSDT files and tables.
      Kexts:
      FakeSMC.kext https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek/downloads/
      Audio:
      AppleALC.kext
      https://github.com/toleda/audio_CloverALC
      Lilu.kext
      https://github.com/vit9696
      CodecCommander.kext v2.4.0 for Audio after sleep
      https://bitbucket.org/RehabMan/os-x-eapd-codec-commander/downloads/RehabMan-CodecCommander-2015-0522.zip
       
      Note:
      Install CodecCommander.kext v. 2.4.0 inside /System/Library/Extensions/ and set darkwake=8 in config.plist to solve the audio after sleep issue.
      I tried installing it inside /EFI/Clover/kexts/10.12 and /EFI/Clover/kexts/Other and it didn’t work.
      I also tried other versions of CodecCommander.kext but none of them worked except for the v. 2.4.0.
      If you don’t want to use Lilu.kext and AppleALC.kext and see the read the “Other methods for activating audio section”.
      realtekALC.kext with https://github.com/toleda/audio_RealtekALC/blob/master/audio_realtekALC-120.command.zip
      audio_cloverHDMI-120_v1.0d.command for HDMI Audio: https://github.com/toleda/audio_CloverHDMI/blob/master/audio_cloverHDMI-120.command.zip
       
      Ethernet:
      AppleIntelE1000e.kext https://sourceforge.net/projects/osx86drivers/files/Kext/Snow_or_Above/AppleIntelE1000e.kext.zip/download
      or
      IntelMausiEthernet.kext https://bitbucket.org/RehabMan/os-x-intel-network/downloads/RehabMan-IntelMausiEthernet-v2-2017-0321.zip
       
      Graphics:
      IntelGraphicsFixup.kext https://sourceforge.net/projects/intelgraphicsfixup/ if you are using the Intel Integrated Graphics 
      Lilu.kext https://github.com/vit9696
      NVidaiGraphicsFixup.kext https://sourceforge.net/projects/nvidiagraphicsfixup/
       
      USB 3.0
      USBInjectAll.kext
      https://bitbucket.org/RehabMan/os-x-usb-inject-all/downloads/RehabMan-USBInjectAll-2017-0517.zip
       
      Note:
      I also tested the system without USBInjectAll.kext and all my USB 2.0 and USB 3.0 ports were fully functional so it’s up to you whether to use it or not.

      VERY IMPORTANT NOTE:
      Before you start using macOS® Sierra®, you need to change the SMBIOS of the config.plist:
      You have to change the SMBIOS settings before starting to use macOS® Sierra®, because the config.plist that is included in this guide doesn’t have a serial number for your Hackintosh, so you won’t be able to use any of Apple’s services without a serial number and a hardware UUID. It’s imperative to do so specially if you are going to use your Hackintosh for daily use. If you don’t change the serial number you won’t be able to use App Store, iCloud, iMessage etc. It’s highly recommended that you use iMac 17,1 SMBIOS as your default. iMac 17,1 and iMac 17,2 models use Skylake processors in Apple's original iMacs.
      For changing the SMBIOS you can use the built-in wizard inside “Clover Configurator” under SMBIOS Section. To open the wizard, click the small magic wand on the right side of the window to use the wizard.
       
      Audio:
      By using the EFI folder included with this guide and by using the patched DSDT/SSDT tables, “AppleALC.kext” and “Lilu.kext” you won’t need to do much to make the audio active on your Hackintosh.
      Just install the macOS® Sierra®, copy the EFI folder and audio is activated by default, HDMI audio will be active once you install nVidiaWebDrivers and restart the computer.
      If the audio didn’t work, you can rebuild prelinked kernel and kexts cache by using the following commands in terminal:
      1. sudo nvram -c 2. sudo purge 3. sudo rm -f /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache && sudo touch /System/Library/Extensions && sudo kextcache -u / sudo update_dyld_shared_cache -force Or you can use “Kext Utility” to repair permissions on /System/Library/Extensions and /Library/Extensions and also it will also rebuilds the system cache for you.
      Kext Utility could be found at:
      http://www.insanelymac.com/forum/index.php?app=core&module=attach&section=attach&attach_id=186603
       
      Note:
      If you see the following output in terminal it means that you forgot to mount the EFI partition, mount it and run the command again.
      EFI partition not mounted
      Boot/EFI not found
      EFI/CLOVER folder not available to install audio
      No system files were changed
      To save a Copy of this Terminal session: Terminal/Shell/Export Text As ...
      logout
      Saving session...
      ...copying shared history...
      ...saving history...truncating history files...
      ...completed.
      [Process completed]
       
      Other methods for activating the Audio:
      1. audio_codecdetect.command
      This command will give you useful information about the audio chipsets and devices that are available on the system, after you run the command, the output will be like this:
      cdetect_v2.2.command ; exit;
      File: audio_codecdetect.command_v2.2
      HDMI audio codec(s)
      Nvidia:   0x10de0083
      Onboard audio codec
      Realtek: 0x10ec0900
      Name: Realtek ALC1150
      Audio ID: 1
      Valid audio codec, audio device and Audio ID; audio injection is working
      Finished
      logout
      Saving session...
      ...copying shared history...
      ...saving history...truncating history files...
      ...completed.
      [Process completed]
       
      This means that the audio chipset is supported and you can go to the next step of installing the audio using Toleda's scripts.
       
      2. audio_cloverALC-120_v1.0f3.command
      Type in the password and press return/enter
      Agreement
      The audio_cloverALC script is for personal use only. Do not distribute
      the patch, any or all of the files or the resulting patched AppleHDA.kext
      for any reason without permission. The audio_cloverALC script is
      provided as is and without any kind of warranty.
      File: audio_cloverALC-120.command_v1.0f3
      Release Mode
      Password:
      EFI partition is mounted
      System Integrity Protection status: disabled.
      OK to patch
      Confirm Realtek ALC1150 (y/n): y
      Clover Audio ID Injection (y/n): y
      Use Audio ID: 1 (y/n): y
      Download ALC1150 files ...
        % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                       Dload  Upload   Total   Spent    Left  Speed
      100 23555  100 23555    0     0  12259      0  0:00:01  0:00:01 --:--:-- 12255
      Edit config.plist/Devices/Audio/Inject/1
      Edit config.plist/SystemParameters/InjectKexts/YES
      Download kext patches
        % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                       Dload  Upload   Total   Spent    Left  Speed
      100  1855  100  1855    0     0   3033      0 --:--:-- --:--:-- --:--:--  3031
      Download config kext and install ...
        % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                       Dload  Upload   Total   Spent    Left  Speed
      100  4223  100  4223    0     0   3383      0  0:00:01  0:00:01 --:--:--  3383
      Install /Volumes/EFI/EFI/CLOVER/kexts/10.12/realtekALC.kext
      Install System/Library/Extensions/AppleHDA.kext/ALC1150 zml files
      Fix permissions ...
      Kernel cache...
      rebuilding //System/Library/PrelinkedKernels/prelinkedkernel
      kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext CodecCommander.kext
      kext-dev-mode allowing invalid signature -67013 0xFFFFFFFFFFFEFA3B for kext AppleMobileDevice.kext
      kext-dev-mode allowing invalid signature -67054 0xFFFFFFFFFFFEFA12 for kext AppleHDA.kext
      kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleGraphicsDevicePolicy.kext
      KernelCache ID: 4EEE3A25D6E9388FE8F02F8E56A57A1D
      kextcache updated critical boot files, requesting launchd reboot
      Install finished, restart required.
      To save a Copy of this Terminal session: Terminal/Shell/Export Text As ...
      logout
      Saving session...
      ...copying shared history...
      ...saving history...truncating history files...
      ...completed.
      [Process completed]
      All you need to do now is to reboot the system and you’ll have audio!
       
      3. HDMI Audio
      For activating the HDMI Audio for you need to run audio_cloverHDMI-120.command
      This command will detect the audio codec for you integrated graphics and discrete GPU and will add the proper SSDT table to /EFI/Cover/ACPI/patched folder
      Agreement
      The audio_cloverHDMI script is for personal use only. Do not distribute
      the patch, any or all of the files for any reason without permission.
      The audio_cloverHDMI script is provided as is and without any warranty.
      File: audio_cloverHDMI-120.command_v1.0d
      Release Mode
      EFI partition is mounted
      No HDMI audio codec(s) detected, continue (y/n): y
      HDMI audio codec(s)
      Integrated Graphics is not installed/enabled
      Install AMD/Nvidia HDMI audio (y/n): y
      Nvidia discrete graphics card 10de1b81 found on PEG0@1/PEGP@0
      Nvidia HDMI audio is not enabled
      Install Nvidia HDMI audio ssdt (y/n): y
      Download SSDT-HDMI-NVIDIA-PEG0 ...
      Password:
        % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                       Dload  Upload   Total   Spent    Left  Speed
      100 44888  100 44888    0     0  39094      0  0:00:01  0:00:01 --:--:-- 39101
      /Volumes/EFI/EFI/CLOVER/ACPI/patched/SSDT-HDMI-NVIDIA-PEG0.aml installed
      Install finished, restart required.
      To save a Copy of this Terminal session: Terminal/Shell/Export Text As ...
      logout
      Saving session...
      ...copying shared history...
      ...saving history...truncating history files...
      ...completed.
      [Process completed]
       
      Audio Troubleshooting:
      If after running the audio_cloverHDMI-120_v1.0d.command you see the following statement
      “Agreement
      The audio_cloverHDMI script is for personal use only. Do not distribute
      the patch, any or all of the files for any reason without permission.
      The audio_cloverHDMI script is provided as is and without any warranty.
      File: audio_cloverHDMI-120.command_v1.0d
      Release Mode
      EFI partition is mounted
      Error: no IOReg/HDEF; BIOS/audio/disabled or ACPI problem
      Continue without HDEF/onboard audio (y/n): y
      No audio codec detected
      No system files were changed
       
      It means you either don’t have a patched DSDT.aml file or SSDT tables and no patches are present inside the config.plist so you need to either add the DSDT/SSDT tables or add patches yourself.
      Don’t be alarmed it’s so easy.
      Open clover configurator and after mounting the EFI partition, open the config.plist and add the following patch :
      Under ACPI, DSDT patches select “change HDAS to HDEF” from “List of Patches” and this will add the following code in the config.plist
      </dict>
      <key>Comment</key>
      <string>change HDAS to HDEF</string>
      <key>Disabled</key>
      <false/>
      <key>Find</key>
      <data>
      SERBUw==
      </data>
      <key>Replace</key>
      <data>
      SERFRg==
      </data>
      </dict>
      or
      Comment: change HDAS to HDEF
      Find*[HEX] 48444153
      Replace*[HEX]48444546
       
      Graphics:
      This section will be dedicated to nVidia GPUs specially Maxwell and Pascal. If you are using any other nVidia or AMD graphics you can skip this section.
      We tested these instructions on an EVGA 1070 Superclocked GPU and a Gigabyte nVidia GeForce GTX960 GAMING-4GB (Please include the brand for reference).
      As you might know the 10 series nVidia GPUs or Pascal are not compatible with Mac OS X El Capitan and earlier versions of macOS® but 9 series and Maxwell are compatible and they both need nVidiaWebDrivers to be fully functional.
      For macOS® Sierra® 10.12.5 you’ll need to download 378.05.05.15f01
      https://images.nvidia.com/mac/pkg/378/WebDriver-378.05.05.15f01.pkg
      Solution 1:
      If you are looking for an easy way to get the GPU working all you have to is to copy the Lilu.kext and nVidaiGraphicsFixup.kext inside the kext folder in clover EFI bootloader.
      The full path is /EFI/Clover/kext/10.12
      Once you finished installing macOS® and nVidiaWebDrivers you’ll need to add the following flags and setting to the config.plist
      Under “Boot” section add or remove nvda_drv=1 if necessary. I don’t need to use it on my computer. You don’t need to inject anything in “Graphics” section Under “System Parameters” check “NvidiaWeb”   When installing Clover EFI bootloader under “Drivers64UEFI” install “EMUVariableUefi-64” // I also use OsxAptioFix2Drv.efi, never tested without it.
      and that’s it!
       
      Solution 2:
      If you don’t want to use nVidaiGraphicsFixup.kext you only have two options:
      1. Run AGDP-fix.app to edit the “AppleGraphicsDevicePolicy.kext” to fix “Boot to Black Screen” issue 2. Or you can edit the “AppleGraphicsDevicePolicy.kext” manually using terminal. If you choose the second solution for any reason remember after each major update you need to apply the patch all over again.
       
      Wi-Fi:
      TP-Link WDN4800 works out of the box without any hassle.
      The only problem that you might encounter with it is "ATHR: unknown locale: 21" error in the verbose boot.
      The Atheros patch is to avoid the series of "ATHR: unknown locale: 21" messages in the verbose boot which they will be registered in message console's logs and they will make the log file bigger. The patch will fix the WiFi location and will stop the error and therefore there will be no more logs.
      Without the patch, the WiFi will work just the same but with lots of messages in the log.
      If you don’t use the TP-Link WDN4800 you can remove the patch or simply leave it as disabled.
       
      USB 3.0:
      Under Kernel and Kext Patches add the following to “KextsToPatch”:
      This patch will raise the limit of the USB ports from 15 to 26.
      For macOS® Sierra
      Name*: AppleUSBXHCIPCI
      Find* [HEX] : 83bd74ff ffff10
      Replace [HEX] : 83bd74ff ffff1b
      Comment: Raise change 15 port limit to 26 in XHCI kext (100-series)
      MatchOS: 10.12.x
      You also might need to add RehabMan’s “USBInjectAll.kext” to the following path under “/EFI/Clover/kexts/10.12” for macOS® Sierra
      Note:
      If you are using a patched DSDT or SSDT tables you don’t need to use any DSDT patches in clover and the “USBInjectAll.kext” you will have full functional USB 2.0 and USB 3.0 ports. I didn’t test USB 3.1 ports because I have no USB 3.1 device to test it!
      The port limit patch must only be temporary, you will need to create your own custom SSDT-UIAC to only inject the ports you use.
       
      Custom SSDT-UIAC:
      A quick rundown on how to create a custom SSDT-UIAC.
      Add the following patch to your config.plist if you don’t already have the patch.
      <dict>
      <key>Comment</key>
      <string>change 15 port limit to 26 in XHCI kext (100-series)</string>
      <key>MatchOS</key>
      <string>10.12.x</string>
      <key>Name</key>
      <string>com.apple.driver.usb.AppleUSBXHCIPCI</string>
      <key>Find</key>
      <data>g710////EA==</data>
      <key>Replace</key>
      <data>g710////Gw==</data>
      </dict>
       
      or
       
      Name*: AppleUSBXHCIPCI
      Find* [HEX] : 83bd74ff ffff10
      Replace [HEX] : 83bd74ff ffff1b
      Comment: Raise change 15 port limit to 26 in XHCI kext (100-series)
      MatchOS: 10.12.x
       
      The USBInjectAll.kext provided in this guide needs to be and stay installed.
      Download ioregistryexplorer Version 3.0.3 from http://mac.softpedia.com/get/System-Utilities/IORegistryExplorer.shtml
      or download IOJones which is an alternative to IORegistryExplorer at: https://sourceforge.net/projects/iojones/
      Download MaciASL from https://bitbucket.org/RehabMan/os-x-maciasl-patchmatic/downloads/RehabMan-MaciASL-2017-0117.zip and extract, drag MaciASL.app into /Applications. (Credit RehabMan)
      Download OS-X-USB-Inject-All Master from: (Credit RehabMan)
      https://github.com/RehabMan/OS-X-USB-Inject-All/archive/master.zip
      and extract the zip file.
      Inside the OS-X-USB-Inject-All-master folder you will find SSDT-UIAC-ALL.dsl, copy it to your desktop.
      Open ioregistryexplorer and find your device id by typing XHC in the search field.
      Open SSDT-UIAC-ALL.dsl with MaciASL and find your appropriate device id section.
      Remove all other sections in the SSDT-UIAC-ALL.dsl that do not correspond with your device id leaving just the one section. Skylake does not have a EHCI controller so “HUB1”, ”HUB2”, ”EH01”, "EH02" can be removed and in my case I can also remove "8086_1e31", "8086_8xxx", "8086_9xxx", "8086_9cb1", "8086_9d2f" and "8086_a2af".
      Compile the file to make sure there are no errors in the code and then save the file with “ACPI Machine Language Binary”. 
      Now we turn our attention to ioregistryexplorer, while you have ioregistry open go to the XHC section and take note of the HSxx or SSxx locations that have devices attached. Now plug in a USB 2.0 device into all USB 2.0 you NEED and do the same with USB 3.0 ports with USB 2 and 3 devices and take note of them all.
      Returning back to the SSDT-UIAC-ALL.dsl you will see all ports listed, you need to remove the ones you did not take note of and you can also add a comment to the ones you keep. 
      UsbConnector values = USB 2.0 = 0, USB 3.0 = 3. Internal = 255
      USB 2.0 devices plugged into USB 3.0 ports HSxx are still marked as USB 3.0 = 3.
      Internal devices such as Bluetooth etc are marked as 255
      Once you gone through and done this to all the devices you need and removed the ones you don’t you can save your SSDT-UIAC-ALL.dsl in MaciASL. Make sure you rename it to SSDT-UIAC and that the file format is ACPI Machine Language Binary
      Copy and paste the resulting SSDT-UIAC.aml into your EFI/EFI/CLOVER/ACPI/patched folder.
      Disable the port limit patch in config.plist and add SSDT-UIAC.aml into SortedOrder if needed.
      Reboot.
       
      Open ioregistryexplorer and test the ports you left enabled USB 2 & 3.
      The number of ports you should see in ioreg should be significantly reduced as they are not being injected anymore.
       
      Special Thanks to:
      I would like to thank MaLd0n for providing the patched version of DSDT and SSDT tables and SavageAUS for doing such a great work on helping me to write this tutorial and testing the files and also writing the “Custom SSDT-UIAC” section.
      I also would like to thank:
      Vit9696 for Lilu.kext
      RehabMan for CodecCommander.kext FakeSMC.kext, IntelMausiEthernet.kext, USBInjectAll.kext.
      Toleda for AppleALC.kext, Audio commands and kexts
      netkas for FakeSMC.kext
      lvs1974 for IntelGraphicsFixup.kext and NvidiaGraphicsFixup.kext
      hnak for AppleIntelE1000e.kext
      Mieze for IntelMausiEthernet.kext
      apianti, blackosx, blusseau, dmazar, slice2009 for Clover EFI Bootloader
      http://mackie100projects.altervista.org for Clover Configurator
      Apple Inc. for macOS® and great many other products.
      And many other great people whom make Hackintosh possible!
       
      The hardware I use in my computer:
      Gigabyte GA-Z170X-Gaming 5
      Intel Skylake Core i7 6700K @ 4.0 GHz
      32 GB (4x8 GB) 2666 GSKILL Ripjaws
      EVGA GTX 1070 SC 8 GB
      Dual Display 23.5"
      Kingston HyperX 240GB SATA III SSD
      250 GB Samsun EVO 850 SSD 
      TP-Link WDN4800 PCIe Wireless Network Adapter
      CoolerMaster Silencio 452 Case
      CoolerMaster Nepton 120XL Liquid Cooler
      CoolerMaster V750 Watts Power Supply
      2x24" Samsung LED Displays + 32" TV
       
      SavageAUS's hardware that was used for testing:
      Gigabyte GA-Z170X-Gaming 5
      Intel Skylake core i7-6700k @ 4Ghz
      32Gb (4 x 8Gb) DDR4 3200 G.Skill Ripjaws
      Gigabyte GTX960 GV-N960WF2OC-4GD
      240Gb Intel SSD
      240Gb Kingston HyperX Savage SSD
      TP-Link WDN4800 WiFi
      Corsair H110i AIO Liquid Cooler
      Corsair RM850i PSU
      Corsair 760t Case
      24" single display Benq GL2450
       
      Please download the PDF version which includes pictures on this guide.
      I hope you find this tutorial helpful.
      Best Regards,
      Cyberdevs
      GA-Z170X-Gaming 5 Release 01 DSDT and SSDT nVidia Version.zip
      GA-Z170X-Gaming 5 Release 01 DSDT and SSDT IntelHD 530 Version.zip
      Installing macOS Sierra on GA-Z170X-Gaming 5 - Final.pdf
      IORegistryExplorer_3.0.3.zip
       
      Updated Clover folders can be found at this post:
      Updated Folders
    • By zeg66
      Trying to install Mavericks on an Asus H170M-E D3 motherboard, Skylake I3-6100 cpu, Intel 530 graphics.
      Last message I see is "root device uud is" and a series of "+++" but then it just stops.
      Have prepared usb with createinstallmedia, added Clover 4413 and changed a few settings with Configurator.
      Any help is welcome.
×