Jump to content
qbru

GA-Z97MX Gaming 5 Build - OS X Yosemite Beta 3

7 posts in this topic

Recommended Posts

Edit: Updated to Beta 4 just fine, BTW  :)

 

I love this board! It takes a bit of work to get going, but the GA-Z97MX Gaming 5 is a wonderful board for your own, bulkier version of the iMac. Indeed, I just taped mine to the back of my Cinema Display and I can't see the difference. From the front, at least. 

 

It's not perfect, at least not yet. I have issues with kernel panics at boot (related to kernel cache and/or patching—I welcome any thoughts or suggestions). I'm not sure if I can fully utilize Apple's online services. And perhaps most importantly for the novice, Yosemite throws in some instability issues and graphical glitches (I didn't experience them in Mavericks). It's not the easiest or most welcoming build and will require patience. But if you can stomach those things it's a superb choice of quality and features. Let's just hope we get full support and stability when Yosemite is released, and that OS X will see official 9-series chipset support before Apple switches everything to ARM or some craziness.

 

The Specs

  • Haswell Core i5 3.5 Ghz CPU
  • 16 GB Corsair 1866 Mhz RAM
  • GeForce 760 MSI ITX Gaming GPU 

The Features

  • Z97 chipset (As of writing, not used in any Mac but seems to work like a Z87)
  • ALC1150 audio with swappable op-amp
  • Atheros Killer E2201 (I think) gigabit networking
  • 6 SATA III ports, a SATA Express port and I think an M.2 port as well

My UEFI BIOS Settings

  • Load optimized defaults (unless you really know what you're doing)
  • XMP #1 Enabled (enabling my 1866 RAM)
  • All boot options set to UEFI or UEFI Only
  • Optional: Enable ErP, ASPM and other features if desired, but only after you've successfully installed and booted (save yourself the headache ^_^  )

None of what follows is my original work, so I'll be sure to credit the source and provide relevant links.

 

Preparation

  1. Obtain the latest version of Clover, the wonderful UEFI boot loader that makes the rest possible.
  2. Follow the directions in any Yosemite guide to prepare a USB drive for installation.
  3. Install Clover to that drive, following the "For UEFI Motherboards" instructions. Use my config.plist.zip, or take care creating or modifying your own.
  4. Store Mieze's superb AtherosE2200Ethernet.kext, toleda's clever CloverALC script, rampagedev's SSDT and of course FakeSMC.kext from HWSensors on your drive. You'll recall the last from the Yosemite guide, no doubt!
  5. Build and boot your machine to UEFI/BIOS, and configure your settings (note mine above).
  6. Boot your USB drive to the OS X Installer. Refer to Clover's documentation on fixes and kernel boot options if you're having trouble.

Post-Installation

  1. Installation should run without issue. I recommend partitioning your drive with Disk Utility first, using GPT.
  2. After installation, feel free to reboot. Keeping your installer USB attached should allow you to boot your newly installed OS, but...
  3. ... You'll need to install Clover on the system drive, so be sure to do so and remember to include your FakeSMC and netwokring kexts for injection.
  4. toleda's script should take care of everything for you regarding audio, except he currently requires a manual patch for this particular CODEC. It isn't hard, and the necessary patch is in my config.plist.zip.

And you're done! Or at least you're as far as I am :D . Enjoy.!

 

Troubleshooting

 

I still get kernel panics that I cannot attribute to any particular source (likely audio—it was a pain to get working in Yosemite for me). Sometimes networking doesn't come up. Don't even ask me about Messages, "Convection" or whatever new Apple services are coming out. No guarantees that this build will be easy or worth your time, but I sure enjoyed getting it running. That said, a few considerations for troubleshooting:

  • I start by trying to Safe Boot (hit spacebar in Clover with proper OS selected). Does that work? If not, where are you getting stuck? Check your kernel boot options and other Clover settings, and make sure your kexts are present and in the appropriate directory on your boot drive.
  • Can't get audio to work? I often have to rebuild the kernel cache then reboot.
sudo touch /System/Library/Extensions
sudo kextcache -Boot -U /
  • Networking is pretty solid thanks to Mieze's kext. But I do sometimes have issues that a reboot or reloading of the kext seems to resolve. Go figure.

Share this post


Link to post
Share on other sites
Advertisement

no problems here, great board! i went with gaming 5 because it was $80 cheaper the the genie 7 from asus. this is my first gigabyte board and it completely changed my opinions about the company 

Share this post


Link to post
Share on other sites

 

Edit: Updated to Beta 4 just fine, BTW  :)

 

I love this board! It takes a bit of work to get going, but the GA-Z97MX Gaming 5 is a wonderful board for your own, bulkier version of the iMac. Indeed, I just taped mine to the back of my Cinema Display and I can't see the difference. From the front, at least. 

 

It's not perfect, at least not yet. I have issues with kernel panics at boot (related to kernel cache and/or patching—I welcome any thoughts or suggestions). I'm not sure if I can fully utilize Apple's online services. And perhaps most importantly for the novice, Yosemite throws in some instability issues and graphical glitches (I didn't experience them in Mavericks). It's not the easiest or most welcoming build and will require patience. But if you can stomach those things it's a superb choice of quality and features. Let's just hope we get full support and stability when Yosemite is released, and that OS X will see official 9-series chipset support before Apple switches everything to ARM or some craziness.

 

The Specs

  • Haswell Core i5 3.5 Ghz CPU
  • 16 GB Corsair 1866 Mhz RAM
  • GeForce 760 MSI ITX Gaming GPU 

The Features

  • Z97 chipset (As of writing, not used in any Mac but seems to work like a Z87)
  • ALC1150 audio with swappable op-amp
  • Atheros Killer E2201 (I think) gigabit networking
  • 6 SATA III ports, a SATA Express port and I think an M.2 port as well

My UEFI BIOS Settings

  • Load optimized defaults (unless you really know what you're doing)
  • XMP #1 Enabled (enabling my 1866 RAM)
  • All boot options set to UEFI or UEFI Only
  • Optional: Enable ErP, ASPM and other features if desired, but only after you've successfully installed and booted (save yourself the headache ^_^  )

None of what follows is my original work, so I'll be sure to credit the source and provide relevant links.

 

Preparation

  1. Obtain the latest version of Clover, the wonderful UEFI boot loader that makes the rest possible.
  2. Follow the directions in any Yosemite guide to prepare a USB drive for installation.
  3. Install Clover to that drive, following the "For UEFI Motherboards" instructions. Use my attachicon.gifconfig.plist.zip, or take care creating or modifying your own.
  4. Store Mieze's superb AtherosE2200Ethernet.kext, toleda's clever CloverALC script, rampagedev's SSDT and of course FakeSMC.kext from HWSensors on your drive. You'll recall the last from the Yosemite guide, no doubt!
  5. Build and boot your machine to UEFI/BIOS, and configure your settings (note mine above).
  6. Boot your USB drive to the OS X Installer. Refer to Clover's documentation on fixes and kernel boot options if you're having trouble.

Post-Installation

  1. Installation should run without issue. I recommend partitioning your drive with Disk Utility first, using GPT.
  2. After installation, feel free to reboot. Keeping your installer USB attached should allow you to boot your newly installed OS, but...
  3. ... You'll need to install Clover on the system drive, so be sure to do so and remember to include your FakeSMC and netwokring kexts for injection.
  4. toleda's script should take care of everything for you regarding audio, except he currently requires a manual patch for this particular CODEC. It isn't hard, and the necessary patch is in my attachicon.gifconfig.plist.zip.

And you're done! Or at least you're as far as I am :D . Enjoy.!

 

Troubleshooting

 

I still get kernel panics that I cannot attribute to any particular source (likely audio—it was a pain to get working in Yosemite for me). Sometimes networking doesn't come up. Don't even ask me about Messages, "Convection" or whatever new Apple services are coming out. No guarantees that this build will be easy or worth your time, but I sure enjoyed getting it running. That said, a few considerations for troubleshooting:

  • I start by trying to Safe Boot (hit spacebar in Clover with proper OS selected). Does that work? If not, where are you getting stuck? Check your kernel boot options and other Clover settings, and make sure your kexts are present and in the appropriate directory on your boot drive.
  • Can't get audio to work? I often have to rebuild the kernel cache then reboot.
sudo touch /System/Library/Extensions
sudo kextcache -Boot -U /
  • Networking is pretty solid thanks to Mieze's kext. But I do sometimes have issues that a reboot or reloading of the kext seems to resolve. Go figure.

 

 

 

Please attach DSDT and all kexts.

Thanks in advanced.

Share this post


Link to post
Share on other sites

No dsdt patching is needed and the only kexts are fakesmc and e2200 

 

Please give me AppleHDA and kext to patch for Clover.

I have a Yosemite.

Thanks in advanced.

Share this post


Link to post
Share on other sites

I don't use applehda and would recommend the latest voodoohda. I use the vHDA in Oz and don't patch applehda. Use toledas patcher for AppleHDA with clover if thats what you want to do.

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 glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      So at boot you will have two options: boot macOS Mojave or Windows 10 
       
       
       
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Using a drive without Windows 10 installed
       
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
       
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
       
       
      OR
       
       
       
      STEP 2 - Using a drive with Windows 10 already installed
       
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 
       

       
       
      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
       
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
       
       
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
       
      Video summary:
       
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
       
      STEP 3 - Stop Windows Boot manager from overriding Clover boot manager
       
      How to stop Windows boot manager from overriding your Hackintosh Clover boot manager when using dual booting between macOS and Windows
       
       
       
       
       
       
    • By SoThOr
      This was spurred on from a discussion in the Clover General thread. Where there was a debate on bcdedit being able create/read/edit (U)EFI Boot entries. I didn't think it appropriate to post all this information there and somebody may want to make use of this and its likely to get lost in that massive thread.
       
      Out of curiosity I decided to see if I could create an EFI entry using bcdedit. What can I say I like a challenge.  Whilst is not a documented method by Microsoft, as it turns out in a round about way it IS possible to create an EFI entry using bcdedit and these are the steps I went through to add UEFI Shell located on a USB stick to the EFI entries. 
       
      Third party software is available that can create and edit UEFI entries from Windows with better support and more features. I'm just making this information available in case those options are unavailable. 
       
      DISCLAIMER - This is not a supported method. Use at your own risk. I recommend backing up your BCD/Firmware variables/settings beforehand.
       
      1) Copy {bootmgr} entry.
      C:\Windows\System32>bcdedit /copy {bootmgr} /d "UEFI Shell" The entry was successfully copied to {34e8383c-73a7-11e9-9cb0-94de8078a7b5}. 2) Edit the new entry using the new GUID bcdedit generated in the copy step.
        a) Set the device and path for UEFI shell on my USB stick.
      bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} device partition=G: bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} path \EFI\SHELL\SHELLX64.efi   b) Clean up some of the stuff that was copied from {bootmgr} (optional as far as I can tell, just makes things tidier in bcdedit)
      3) Put the new EFI entry first in boot order. (optional)
       
      After completing the steps above, here is what "bcdedit /enum firmware" shows:
       
      I shutdown my computer and when I turned my computer back on it booted up into UEFI Shell. After exiting the shell my PC went on to boot Windows.
      Here is the resulting dump using "bcfg boot dump -v" from that shell:
       
      You may notice that the shell shows as "Windows Boot Manager" in the bcdedit output. This I believe is because of the "WINDOWS" at the beginning of the option data that bcdedit added to the EFI Boot entry. I also believe this why bcdedit shows my Windows 8 installation as "Firmware Application" because it has no option data. I don't know how to remove this data using bcdedit nor do I know how the option data, that bcdedit adds, will affect other EFI applications.

      There might be a way to create the EFI entry without copying the Windows entry but if there is I'm unable to find any documentation on how one would do so. If you use the create command then it just puts it in the BCD and I'm unaware of a way to tell it to create it in EFI instead, other than by doing the above.
    • By cvad
      Small tool to download, compile and build the latest Clover X64 package.
       
       
       

      The script inside is editable.

       
      Enjoy...
       
      Many thanks to the comrade SunKi for help with creating the script.
       
       
       
       
       
      Best thanks - click "Rate File".
       
    • By blxkspell
      Hey!
      As I have 3 Monitors connected, my RX 570 gets arround 50°C while ideling/ web browsing etc. The problem is, that this temp is apparently just the threshold, when the fans start to spin. So the fans start spinning for a minute then they stop for a while again... This is very annoying for me as the rest of my hackintosh is nearly quiet (SSD, 120mm low RPM cpu fan, nearly silent PSU,...), especially when Im using the pc to revise for school. Does somebody know wether its possible to "change" the threshold till the fans start spinning? Like it would probably not be a problem for the gpu at all, if the temp rises to 55°C but therefore be soundless....
       
       
×