Kingston 8GB*2 DDR3 1600 (the RAM oc to 1866 automatically)
Giga GTX760 4GB
840 EVO 120G SSD
Hello everyone, that is my guide to successfully install OS X Yosemite for the Gigabyte GA-Z97X-UD3H. It works everything except iMessage and FaceTime, you can enable them following this guide How to Fix iMessage
First of all, remove all the RAM sticks except one.
Follow this guide http://www.tonymacx86.com/445-unibea…-based-pc.html from step 1 to step 4.
IMPORTANT: when you will boot for the 1st time and when you just installed Yosemite (before installing drivers with MultiBeast) boot with these flags: “-x GraphicsEnabler=No”
Install MultiBeast with these options:
Quick Start > DSDT Free
Drivers > Audio > Realtek ALCxxx > ALC1150 (because that’s the audio card we have in our motherboard)
Drivers > Disk > 3rd Party SATA
Drivers > Misc > FakeSMC v6.11.1328
Drivers > Network > Intel > AppleIntelE1000e v3.1.0 (to enable the ethernet connection correctly)
Drivers > AppleRTC Patch for CMOS Reset
Bootloaders > Chimera v4.0.0
Customize > Boot Options > 1080p Display Mode (of course just if you have a 1080p display)
Customize > Boot Options > Basic Boot Options
Customize > Boot Options > Hibernate Mode – Desktop
Customize > Boot Options > IGPEnabler=No
Customize > Boot Options > Kext Dev Mode
Customize > Boot Options > Use KernelCache
Customize > System Definitions > Mac Pro > Mac Pro 3,1 (usually it’s better choose this to avoid kernel panic)
Customize > Themes > tonymacx86 Black (you can choose the one you want)
Then, just in case you have an SSD, check this option:
Drivers > Disk > TRIM Enabler > 10.10.0 TRIM Patch
Now cross your fingers and reboot! Press F12 when the PC is restarting and boot from the drive you installed Yosemite, everything should work fine! I’ll post the guide to enable HDMI audio ASAP. Hope this will help!
EDIT: just in case you have a kernel panic, boot up with -x in safe mode and install this MultiBeast driver:
Drivers > Misc > NullCPUPowerManagement
It is important that the USB3.0 driver must be installed. Otherwise the SD card reading via USB2.0 hub will cause freeze/panic definitely.
PS: The USB2.0 hub is connected to USB3.0 port on the motherboard. If your USB2.0 hub is connected with USB2.0 port on the motherboard, no such freeze/panic.
I ordered the same motherboard/cpu as you have in your computer, so I’m glad I found your guide, because I’m quite a noob when it comes to computers . I will install everything sometime this weekend.
Just wondering, why remove the RAM-sticks except one?
Actually, I don’t know! If you won’t remove the RAM sticks except one, a kernel panic will pop up
I got two 8GB RAM sticks. So your advice would be to wait with installing the second one until I completed the entire installation?
Thank you, agavasan You’re so great.
I follow your method and it works. Yes, the issue is the 16GB of RAM. And there is actually no need to disable on board graphics card (which will make the audio function abnormal).
And the boot flags of “-x GraphicsEnabler=No” is needed before the setup of MultiBeast. Otherwise you will not be able to reach the installer (both the 1st installation and the 2nd installation after the reboot).
Thank you so much. And after the setup of MultiBeast, I shut down my PC then plugged the other 8GB of RAM back then boot again. It’s a miracle that I am able to enter the system. But everyone should be patient that int the Apple bar screen it takes about 2 minute to start so do not turn off your PC. Finally, enjoy your Yosemite.
However, I found a issue that after installation and multibeast setup and then I plugged the other RAM of 8GB back.
Today I modified a kext file in the SLE folder. I had to add my wireless card’s VEN and DEV ID into the IO80211Family.kext’s plist.
After I clicked “More to Tash” of IO80211Family.kext file in the SLE folder, my system freezes. So I wonder if this freeze is caused by the RAM of 8GB*2?
So next time, if I am going to change the SLE folder, I have to unplug a RAM first, then after the installation of the kext files, just plug the RAM back.
Have anyone experienced the same issue?