Contribute
Register

Haswell-E + X99 Motherboard Temporary Guide - OS X 10.10

Asus X99 Deluxe & 5820k & GTX960 running with Yosemite

Hello to everyone,

I wanted to chime in on the setup of an X-99 rig. Here are the components:
Asus X-99 Deluxe
i7-5820K
Crucial 2x8GB 2133 DDR4
Gainward GTX760 Phantom 2GB
Currently plus traditional spinning disk, will upgrade to SSD as soon as I have it :)
Yosemite 10.10.2

I am using the Nvidia WebDrivers for graphics output.
What is not working (yet): Ethernet and Audio, I have not tested Bluetooth yet - this is a work in progress after all.

Basically I followed the steps outlined by winston in post 109 here: #109.
As mentioned there I had to use additionally the boot flag nv_disable=1 for the UniBeast install and all reboots until I installed the WebDrivers from Nvidia. Note though that the system was _extremly_ sluggish with this and the cpus=1 flag set. Especially using MultiBeast like this resulted in waits of several minutes between two clicks - a pain to get through.
I also had a kernel panic when using the "ElliotForceLegacyRTC" kext installed (as is selected when using the EasyBeast option) so I removed that.
Then I ran into the "boot0 error" when trying to boot from the HD, but the post here helped remedy this: boot0 Error: The Official Guide (Maybe I should mention that this is my first hack attempt).

Thanks to everyone for the great shoulder to stand on! :)

Regards,
sahnetorti
 
After installing AppleIntelE1000 3.1.0a and Realtek ALC1150 (audio still not working), my 2nd monitor stopped working...???

ASUS x99 Deluxe
5930k
64GB RAM
nVidia 970 in SLI (2x)

Previously, I had both monitors installed flawlessly. A little puzzled as there doesn't seem to be any connection. Any ideas? Thank you!

EDIT: Oddly enough, is worked over DisplayPort for awhile, then stopped. 2nd Monitor is working over DVI.

Any advice/help on the x99 audio problem? I've seen a few posts, but I'm still not sure how to implement them.
 
Last edited:
@1pp1k10k4m1 -

You'll need to use a different ALC1150 kext because the one that is included in Multibeast does not work. On the X99 chipset, the device ID was changed, meaning we need to use a different kext or injector. Toleda has an excellent guide here in the forum, and on his Github.

~~~~~~~~~~~~~~~~~~~~

On another note, my SSDT - er - stopped working? Randomly? No changes to the system, just one day noticed that it wasn't doing it's job. Easy fix, just reinstalled the SSDT, but just reporting an oddity.

-IC
 
Thanks again InsaneCultist...I get this:

File: File: audio_realtekALC-100.command_v1.0.4b
Verify kext-dev-mode=1 boot flag/argument
Password:
Sorry, try again.
Password:


No audio codec detected
To save a Copy to this Terminal session: Terminal/Shell/Export Text As ...
logout


[Process completed]

From some posts in the forums it looks like I have to reinstall Yosemite...??? Is that true? No way around it?

Thank you!


UPDATE:

Reinstalled Yosemite, went to apply Toleda's patch right after installing nVidia Web Drivers. My setup shows no audio devices under Preferences, and this is the output (any advice??):

File: File: audio_realtekALC-100.command_v1.0.4b
Verify kext-dev-mode=1 boot flag/argument


WARNING: Improper use of the sudo command could lead to data loss
or the deletion of important system files. Please double-check your
typing when using sudo. Type "man sudo" for more information.


To proceed, enter your password, or type Ctrl-C to abort.


Password:
/Users/userremoved/Downloads/audio_realtekALC-100_v1.0.4b.command: line 248: [: ==: unary operator expected
Error: no IOReg/HDEF; BIOS/audio/disabled or ACPI problem
No system files were changed
To save a Copy to this Terminal session: Terminal/Shell/Export Text As ...
logout


 
Last edited:
I think people are reinstalling to get a native copy of AppleHDA.kext. You could use Pacifist and extract it from the installer package.
 
My bad - forgot to mention that the X99 platform requires a KEXT HDAEnabler, not the traditional .dylib that works with most boards. They are readily available in Toleda's github I linked earlier. Install this FIRST, then patch your codec.
 
Hello everyone,

I had been following this thread for quite a long time and reading through basically all the posts (Thank you very much for all that information!) before I decided two weeks ago to build a Hackintosh based on the X99 platform.
The basic configuration is finished and I've been quite happy with the results so far, OSX running without any crashes or reboots and of course a major performance improvement over my Mid 2010 Macbook Pro.

There are a few things I haven't been able to resolve though:

*I used the SSDT for my i5820k (non OC) and placed it in the respective folder (ACPI/patched), set DropOEM True in Clover but still the CPU frequency isn't going down. (DPCIManager displays 34 P states but running at 34 all the time)

*sleep is only working sometimes

*I didn't get built-in Audio to work even though I followed all of Toleda's github guides and read the forum troubleshooting threads. (Which is just a minor problem for me since I'm using my external Focusrite Saffire Pro Firewire audio interface)


I've attached a screenshot of my geekbench 3 64 benchmark (which appears to be lower than it should be) and my clover configuration.
It would be great if someone could check out my config.plist. screenshot.pngView attachment config.plistDPCIManager.pngioreg.png

I'm planning on submitting my build to the user builds forum section once everything works.

Thank you very much!
 
Henry
GA-X99-UD4 |  i7 5820K |  GTX 970 G1 Gaming
The SSDT does not change the P states or frequency that your CPU will run at - just helps to divide the workload over all 6 cores. It is yet to be determined if the alteration in frequency is cosmetic or not, but from what I've experienced, using the SSDT is the best way to achieve optimal performance without native power management, something that is beyond our control.
 
InsaneCultist said:
The SSDT does not change the P states or frequency that your CPU will run at - just helps to divide the workload over all 6 cores. It is yet to be determined if the alteration in frequency is cosmetic or not, but from what I've experienced, using the SSDT is the best way to achieve optimal performance without native power management, something that is beyond our control.
Click to expand...
It's clearly more than cosmetic or temps and power usage wouldn't be dropping with p-states. Of course real power management will come from Apple support.
http://www.insanelymac.com/forum/to...ver-uefi-behavior-f8-key-on-boot-5960x/page-2
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top