Jump to content
Cyberdevs

El Capitan on GA-Z170X-Gaming 5

790 posts in this topic

Recommended Posts

@cyberdevs

 

Hello again, now is everything working - including sleep etc., everything :3, except sound.

 

I was using your default settings with toledos' patch applied and I had no sound devices.

 

Then I've tried voodoohda however I had a igain bug. I tried to fix it modifying info.plist and set igain to 0. Did not work :/ Then I deleted AppleHDADisabler kext from extensions. No noise but sound only from front panel.

 

The strangest thing is that even if I delete all of the appleHDA patches from config.plist in clover and realtekALC kext in clover/kexts/Other the voodoohdasettingloader app just do not want to open. Even after I added it to login items it is constantly asking me if I want to open this app for the first time.

 

I've also tried to set different id's in clover audio (1, 2 or 3) and also disable resetHDA option.

 

Nothing of this resulted in both front and back panel working without iGain issue :/

 

Any suggestions ?

Share this post


Link to post
Share on other sites
Advertisement

Hi,

 

I have a GA-Z170X-Gaming 5 and I'm trying to install the El Capitan 10.11.3. I've used a few of the EFI files from this thread and I'm stuck at this every time. I'm using the on board Intel HD Graphics 530. The CPU is a i7-6700k.

 

Any idea how to pass over this?

 

Thanks.

 

 

3

 

pitysoft - it looks like you forgot to disable Serial Port in BIOS, its hidden under a sub-menu.

Share this post


Link to post
Share on other sites

@kenmadsen

I used BearExtender-5.4 and it was pretty compatible with my older D-Link DWA 125 usb adapter until recently that I upgraded my system and OS but I'm not sure if that's compatible with El Capitan.

 

 

 

Tried BearExtender 5.4, it didn't work, perhaps because this particular model (ASUS USB-AC51) is dual channel? anyways using the ASUS utility now which is clearly based on the M24 version, which does not seem to auto connect :(

Share this post


Link to post
Share on other sites

anonshin,

 

In order to make sure voodoohdasettingloader.app to load you have to find it in your application folder and right click on it an then choose open, that's because of the GateKeeper feature in mac os x.

make sure all the AppleHDA fixes are removed from the config.plist and install the latest version which I believe is 2.8.8 V3 and set layout ID to 1. the only patch you're gonna need is a DSDT patch under ACPI section for renaming HDAS to HDEF find 48444153 and replace with 48444546 and make sure to set kext-dev-mode=1 and rootless=0


@kenmadsen,

 

You're dual channel capability has nothing to do with the problem you are experiencing, all you are gonna need is to have the compatible kext for your network adapter in your S/L/E folder and bear extender should be able to connect.

Send me a screenshot of your bearextender window and let me see what's wrong. send me a picture of every available tab in the app.

Share this post


Link to post
Share on other sites

They sent me the f5p, before they sent the f5x I can't figure out what kind of numbering they're using! If you want to try, I can upload them.

 

Hi John,

If i understand correct, you already tested f5p a while ago but it didnt work. And have only just received this f5x brand new.

 

Perhaps Gigabyte will also send me an f5x too / similar in due course (on my own eSupport ticket). However if they dont then yeah would really appreciate if can please upload it somewhere online.

 

No need to upload both of them, just the most recent one. And no need to upload if you already tested and it didn't work. Or else did not notice any other new features.

Many thanks.

3

Share this post


Link to post
Share on other sites

No, they first send the f5x and now the new f5p! Sorry I tested but problem NOT solved. I believe they'll send you the same bios. I think Ill open a ticket to clover

I just rolled back to f5x, apart from losing all my OC profiles, I had an issue with the back usb DAC ports not getting power, so I ended up with the still beta F5x

Share this post


Link to post
Share on other sites

Cyberdevs,

 

I did exactly what you have told me to and now I can control voodooHDA, however back is still not working. When I set gain to maximum I can hear that there is a signal coming through but it with no audio.... if I set gain to max and play something it sounds as if it was back channel of surround. Headphones jack in front panel is working just fine.

 

Another thing that caught my eye.... I cannot disable DSP in BIOS. There is no DSP option to change.

Share this post


Link to post
Share on other sites

kenmadesn,

 

Have you tested asus's original installer for mac os x?

 

here is the link:

https://www.asus.com/us/Networking/USBAC51/HelpDesk_Download/


Cyberdevs,

 

I did exactly what you have told me to and now I can control voodooHDA, however back is still not working. When I set gain to maximum I can hear that there is a signal coming through but it with no audio.... if I set gain to max and play something it sounds as if it was back channel of surround. Headphones jack in front panel is working just fine.

 

Another thing that caught my eye.... I cannot disable DSP in BIOS. There is no DSP option to change.

In Mac OS open system preferences and select sound, select output and change "Select a device for sound output: Line-out (Green Rear) and see if it works. and from "Sound Effects" you can also chose the ports for playback the audio.

Share this post


Link to post
Share on other sites

kenmadesn,

 

Have you tested asus's original installer for mac os x?

 

here is the link:

https://www.asus.com/us/Networking/USBAC51/HelpDesk_Download/

 

I'm running the original kext from asus, now running the original ui as well which bears extreme resemblance to the BearExtender version m24. it does not automatically connect, but i can live with that better than not having any wifi connection :) as stated BearExtender 5.4 was able to see my AP, but always failed to connect.

ALL of them have one thing in common (both the old version and the newer version and the asus one.. I have to start adding a dummy entry in order for my previous saved favourite / profile to be seen in the list (which leads me to believe the asus and bear extender use the same user interface.

Share this post


Link to post
Share on other sites

I know 

 

I'm running the original kext from asus, now running the original ui as well which bears extreme resemblance to the BearExtender version m24. it does not automatically connect, but i can live with that better than not having any wifi connection :) as stated BearExtender 5.4 was able to see my AP, but always failed to connect.
ALL of them have one thing in common (both the old version and the newer version and the asus one.. I have to start adding a dummy entry in order for my previous saved favourite / profile to be seen in the list (which leads me to believe the asus and bear extender use the same user interface.

I know how annoying this can be, I had the same problem with my older setup until I found BearExtender which solved my problem, but you're right having a wifi connection with the cost of connecting it manually everytime the system starts is worth it until you find a better solution. But if you are considering to change your network adapter I will definitely recommend TP-Link WND4800 because it's natively supported by mac os x and you can even use airdrop.

Share this post


Link to post
Share on other sites

I know 

 

I know how annoying this can be, I had the same problem with my older setup until I found BearExtender which solved my problem, but you're right having a wifi connection with the cost of connecting it manually everytime the system starts is worth it until you find a better solution. But if you are considering to change your network adapter I will definitely recommend TP-Link WND4800 because it's natively supported by mac os x and you can even use airdrop.

 

I'll keep that one in mind for when i want to update, thanks! :)

Share this post


Link to post
Share on other sites

Hi all, 

 

First of all a big thank you to everyone who has contributed to this thread so far! It's really awesome!

 

I have the gaming 3, just like Majonez and everything seems to be working so far, with a gtx 970 4GB and 16GB (2x8GB DDR4 3000) corsair memory.

 

I have something funny going on though. Only in OSX does my PSU make a whining, squealing noise.

 

I read that I should change the CPU vcore from auto to the value that it shows. However, when I do that, it gives me a KP on login.

 

EDIT:

 

The Vcore that shows is 1.180V, which gives me a KP.

 

However, under MIT I saw that the mobo's vcore was only 1.165, so I set it to 1.165 and it booted up and no squealing noise! :D

Share this post


Link to post
Share on other sites

Hi all, 

 

First of all a big thank you to everyone who has contributed to this thread so far! It's really awesome!

 

I have the gaming 3, just like Majonez and everything seems to be working so far, with a gtx 970 4GB and 16GB (2x8GB DDR4 3000) corsair memory.

 

I have something funny going on though. Only in OSX does my PSU make a whining, squealing noise.

 

I read that I should change the CPU vcore from auto to the value that it shows. However, when I do that, it gives me a KP on login.

 

EDIT:

 

The Vcore that shows is 1.180V, which gives me a KP.

 

However, under MIT I saw that the mobo's vcore was only 1.165, so I set it to 1.165 and it booted up and no squealing noise! :D

Hi there,

Thanks for sharing your experience :)

Share this post


Link to post
Share on other sites

pitysoft - it looks like you forgot to disable Serial Port in BIOS, its hidden under a sub-menu.

 

Hi dreamcat4,

 

You were right, I forgot to disable the serial port in bios. But this didn't fix the Bluetooth problem. I solved it by inserting a USB Bluetooth adapter and I manage to pass that error.

 

I manage to make everything to work, except the dual monitors over DisplayPort. They are working in mirroring if I use the Intel HD 530 onboard video. But with Nvidia GTX 970 I have a black screen.

 

Also I can report that I have the same issue with multiple boot options in bios.

 

Marius

Share this post


Link to post
Share on other sites

Hi dreamcat4,

 

You were right, I forgot to disable the serial port in bios. But this didn't fix the Bluetooth problem. I solved it by inserting a USB Bluetooth adapter and I manage to pass that error.

 

I manage to make everything to work, except the dual monitors over DisplayPort. They are working in mirroring if I use the Intel HD 530 onboard video. But with Nvidia GTX 970 I have a black screen.

 

Also I can report that I have the same issue with multiple boot options in bios.

 

Marius

For me to fix the black screen with web drivers i had to edit a kext. Copy it from system -> library -> extensions -> AppleGraphicsControl.kext to the desktop then right click it then show package contents, open contents folder then plugins folder then right click AppleGraphicsDevicePolicy.kext to show contents, open contents folder then right click on info.plist and open with "other" and choose textedit, scroll down to<key>ConfigMap</key> and find your "mac" key and change the <string> to none like this

Before

<key>Mac-42FD25EABCABB274</key>

<string>Config2</string>

 

After

<key>Mac-42FD25EABCABB274</key>

<string>none</string>

 

Reinstall kext with Kext Utility then reboot with nvda_drv=1

 

Give that a try

Share this post


Link to post
Share on other sites

For me to fix the black screen with web drivers i had to edit a kext. Copy it from system -> library -> extensions -> AppleGraphicsControl.kext to the desktop then right click it then show package contents, open contents folder then plugins folder then right click AppleGraphicsDevicePolicy.kext to show contents, open contents folder then right click on info.plist and open with "other" and choose textedit, scroll down to<key>ConfigMap</key> and find your "mac" key and change the <string> to none like this

Before

<key>Mac-42FD25EABCABB274</key>

<string>Config2</string>

 

After

<key>Mac-42FD25EABCABB274</key>

<string>none</string>

 

Reinstall kext with Kext Utility then reboot with nvda_drv=1

 

Give that a try

 

Thanks a lot, I managed to make it run. I also had to move the DisplayPort cable in another DisplayPort.

Share this post


Link to post
Share on other sites

* Duplicated UEFI Boot Entries Bug is not unique to Clover

* It can be reproduced with other bootloaders

 

Today I have developed a method that:

 

* Can reproduce this bug with PASSMARK Memtext x86 6.2 Free Edition

* Full instructions here:

 

https://gist.github.com/anonymous/f5b09529f279348ac6e6

 

* Information has been passed to Gigabyte eSupport.

* I have asked them to reproduce it with Memtest x86.

 

Please be aware:

 

It is one thing to reproduce this BIOS bug reliably (not simple). However it is entirely another task to track down, and try to really solve the problem. Hopefully Gigabyte can start towards that goal once they can reproduce in their own labs.

Share this post


Link to post
Share on other sites

I have found another application for those whom have Windows Installed on their computers to manage the UEFI entries.

It's called VisualBCD and can be downloaded at: https://www.boyans.net

 

It is similar to EasyUEFI and works on Windows 10 Enterprise edition as well, unlike EasyUEFI's free version which can't operate on Windows 10 Enterprise version.

I'm not sure if it could solve the multiple entries building up in the BIOS but I tested it on another system which has a Dual Boot capacities with Mac OS X El Capitan and Windows 10 Enterprise version on a single hard disk and it's really easy to use. This system doesn't have the bug with multiple entries maybe because it has an older version of UEFI BIOS.

 

 

Since I don't have Windows on my GA-Z170X-Gaming 5 to test it and see if it could remove the multiple entries for good or not for those whom have access to windows on their buggy systems is worth a shot.

 

Maybe I install windows on my system later and give it a test myself but for now test it if you are interested and post your results.

 

Cheers 

Share this post


Link to post
Share on other sites

Another tip: if have accidentally also deleted the windows boot entry, and get a "Error code: 0xc0000034" from windows boot.

 

reason: deleted windows 10 uefi boot entry
======
your PC / Device needs to be repaired
File:\BCD Missing
Error code: 0xc0000034
======
* disconnect all other ESP partitions / UEFI disks

* Boot win10 install media --> click next --> click 'Repair computer'

* advanced options --> cmd prompt --> $ bootrec /rebuildbcd
======
 

Share this post


Link to post
Share on other sites

* Duplicated UEFI Boot Entries Bug is not unique to Clover

* It can be reproduced with other bootloaders

 

Today I have developed a method that:

 

* Can reproduce this bug with PASSMARK Memtext x86 6.2 Free Edition

* Full instructions here:

 

https://gist.github.com/anonymous/f5b09529f279348ac6e6

 

* Information has been passed to Gigabyte eSupport.

* I have asked them to reproduce it with Memtest x86.

 

Please be aware:

 

It is one thing to reproduce this BIOS bug reliably (not simple). However it is entirely another task to track down, and try to really solve the problem. Hopefully Gigabyte can start towards that goal once they can reproduce in their own labs.

This is good news since Gigabyte answered me they couldn't reproduce my problem. I believe it's best if all of us effected, open a ticket on Gigabyte pointing to this topic-problem.

Share this post


Link to post
Share on other sites

This is good news since Gigabyte answered me they couldn't reproduce my problem. I believe it's best if all of us effected, open a ticket on Gigabyte pointing to this topic-problem.

Where a bouts are you opening tickets and what exactly are you writing in these tickets?

Share this post


Link to post
Share on other sites

Hi guys, 

 

So, in early January, thanks to a lot of help from @cyberdevs, I was able to get Hackintosh up and running on my i5 6500 and Gigabyte Z170-Gaming 5 motherboard. Things have been working just fine for me. The only problem is that for some reason, OS X stops booting for me if I overclock my CPU. 

 

Since I have a non-K processor, I OC by changing my BCLK frequency from 100 to higher. Gigabyte uses a custom BCLK generation on the Gaming 5 mobo, so this method is totally fine. I make sure to change other relevant voltage and memory related settings as well. I have successfully managed to OC my i5-6500 to 3.7GHz and even tested it for stability and gaming under Windows 10.

 

OS X, however, just refuses to boot if I increase the BCLK frequency to more than 102. As soon as I do that, it gets stuck at this step. https://www.dropbox.com/s/tf1blvpmriqvxmx/IMG_20160223_095117.jpg?dl=0

 

I have tried quite a few things, including generating a new SSDT for my processor with the increased frequency and BCLK clock, playing around with various CPU and RAM settings in BIOS, to no avail. 

 

At this point, I am really pulling my hair out. I wish I could simply exchange my 6500 CPU with a 6600K, but that is not possible where I live. I have also been unable to find a buyer for it :(

 

So, I was wondering if anyone else with a non-K Skylake CPU has managed to OC under El Cap successfully? And if you have a K CPU that is OCed, can you actually OC the CPU using the BCLK frequency and not using the multiplier to see how things go? Any help in this matter will be greatly appreciated. Thanks!

Share this post


Link to post
Share on other sites

Hi Rajesh_Pandey,

 

What if you add the AppleIntelCPUPowerManagementInfo.kext in your EFI\CLOVER\KEXT\10.11 or adding it to \System\Library\Extensions

 

I'm not sure if we tried that earlier.

This kext is managing the SpeedStep of the processor and it might solve your problem.

 

 


dreamcat4 has more information on overclocking the CPU but as I recall he uses a 6600k processor and has a gaming 3 motherboard.

 

If using the kext doesn't solve the problem maybe he can shed some lights on the matter.

AppleIntelCPUPowerManagementInfo.kext.zip

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.

Announcements

  • Similar Content

    • 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.
       
      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:
       
      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
      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
       
      Audio Troubleshooting:
      If after running the audio_cloverHDMI-120_v1.0d.command you see the following statement
       
      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 -  I switched to AMD RX 580
      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 for macOS High Sierra
       
      Updated Folder For macOS Mojave 10.14
       
      OpenCore 0.6.0 Thanks to @5T33Z0
    • By dloprios97
      Hi everyone,

      I'm trying to install MacOS Catalina on the ACER C22-760 (i3 6100U, 520 HD)

      I did all the usual prep to install the system, especially as I've done hackintoshes with the same specs in the past.

      But after the moment it boots up, the screen goes black. So I decided to install the system booted in 0x12345678 and then fix the graphics.

      Long story short, with the installation done I've tried every single combination to fix the graphics and found out that:
      Booting with a 0x12345678, a 1080p monitor is detected, but obviously, no acceleration. Booting only with AAPL,ig-platform-id set to 19160000, the system boots with complete acceleration but no monitor attached into any framebuffer. About this Mac reports a 1280 x 1024 monitor (Found using Anydesk and ioreg remotely.) Changing the connector type to DP or HDMI, Internal o External, platform-id is useless. This system is getting me anxious. Because I don't find any fix for it.
      Someone can help me out? Love ya!
      PD: The system is an All In One with no HDMI port.
      Fernando’s MacBook Pro.ioreg
    • By tluck
      Lenovo T460 macOS with Clover Guide
      Latest Release on GitHub (March 2020) Updated to Clover r5105 Updated Lilu based kexts - Lilu, ALC, WEG Added AirportBrcmFixup.kext
        Various Tweaks over Last months The main branch in my github repo is a complete Clover ESP (/EFI) bundle and kext pack for the Lenovo T460. The current file bundle seems to work on Sierra, HighSierra, Mojave and Catalina. There is an OpenCore branch in the repo as an alternative to Clover. This guide was developed for a Clover implementation. But the thread has evolved to include discussion of both Clover and Opencore for these systems: T460 and T470 family of ThinkPads.
       
      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 (the 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
       
×