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

[uwcine]

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

System fully working! Video playback problem solved! Adobe Premiere did not work properly with voodoo audio. I connected an external USB audio card and now playback works on CS6. So premiere obviously needs audio to playback video!

 

[Janzwo]

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

Hello everybody,

just wanted to say that I updated to 10.10.1. Had to copy the patched kernel again and in my case delete the two IOBluetooth-Kexts again, but otherwise everything seems to be working just fine!

greetings

janzwo

 

[BoomR]

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

Has anyone been able to get wake after sleep working? My machine boots up after it goes into sleep/hibernate mode, but my monitor never comes back on when the machine wakes back up (I can use ARD to log into machine so it's fully functional - just no video on the machine itself).

Maybe one of the "darkwake= ??" boot flags?

 

[Octavean]

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

Has anyone been able to get wake after sleep working? My machine boots up after it goes into sleep/hibernate mode, but my monitor never comes back on when the machine wakes back up (I can use ARD to log into machine so it's fully functional - just no video on the machine itself).

Maybe one of the "darkwake= ??" boot flags?

Yeah I have made no progress there.


You are referring to the monitor only right? Typically I don't expect sleep to work so I disable sleep by going to system Preferences>Energy Saver and then setting the slider for "Computer sleep" to "Never". Then I set "Display sleep" to 20min. I also uncheck "Put hard disks to sleep when possible".

This has worked fine for me with previous versions of OS X but Yosemite not so much. Always a blank screen and this happens on a Yosemite install on my P9X79 Deluxe build as well.

I even tried the terminal command "caffeinate" but still a blank screen. Your assertion confirms my suspicion that its the screen itself not the system that isn't waking.

Hello everybody,

just wanted to say that I updated to 10.10.1. Had to copy the patched kernel again and in my case delete the two IOBluetooth-Kexts again, but otherwise everything seems to be working just fine!

greetings

janzwo

Very cool,...!!!

Good to hear.

So walk me through it if you will,.....

1) Repair Permissions

2) Install 10.10.1 update

3) boot from patched UniBeast USB stick and choose USB

4) Open Terminal and enter the following:

cp -R /Volumes/USB/System/Library/Kernels/kernel /Volumes/Yosemite/System/Library/Kernels/kernel

5) Boot from UniBeast again and choose Yosemite off of the installed HDD or SSD

6) Optionally delete IOBluetooth-Kexts (I know my Asus X99-A based system would need this step too / thanks again for that tip BTW)

7) repair permissions


Does that sound about right?

BTW, what USB audio solution are you using?

 

[BoomR]

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

Yeah I have made no progress there.


You are referring to the monitor only right? Typically I don't expect sleep to work so I disable sleep by going to system Preferences>Energy Saver and then setting the slider for "Computer sleep" to "Never". Then I set "Display sleep" to 20min. I also uncheck "Put hard disks to sleep when possible".

This has worked fine for me with previous versions of OS X but Yosemite not so much. Always a blank screen and this happens on a Yosemite install on my P9X79 Deluxe build as well.

I even tried the terminal command "caffeinate" but still a blank screen. Your assertion confirms my suspicion that its the screen itself not the system that isn't waking.

Thanks for that additional info. Typically I have that stuff all set like you do once the build is up & in production (since this will be my new music studio machine). But while I'm still putzing about, I forgot to disable all the powersaver stuff & then I get pulled away from my machine.

I just thought if there was a quick fix, I'd sure love to know. Hmmm...wonder if the update to 10.10 1 plus the updated NVIDIA Web drivers plus the new updated CUDA might fix my monitor issue? Will have to test that tonight when I get home...

 

[Janzwo]

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

So walk me through it if you will,.....

1) Repair Permissions

2) Install 10.10.1 update

3) boot from patched UniBeast USB stick and choose USB

4) Open Terminal and enter the following:



5) Boot from UniBeast again and choose Yosemite off of the installed HDD or SSD

6) Optionally delete IOBluetooth-Kexts (I know my Asus X99-A based system would need this step too / thanks again for that tip BTW)

7) repair permissions


Does that sound about right?

BTW, what USB audio solution are you using?

...yes, that worked for me (you don't need step 1 though)...

as for the audio -> I used the newest Voodoo2.8.7.kext (not in multibeast, but downloaded it via google) and it worked o.k.. I had to patch the input gain, because it was on 80 and made some strange noise in the background. The settings in Voodoo-systempreferences weren't saved after reboot, so I did the following to have inputgain consistently on 0:

-go to the voodoohd.kext in the S/L/P folder->right click->show package content-> copy the info.plist to your desktop-> open it and look for this section to set your parameters:



...as you can see I put 0 instead of 80 in iGain. Then save the edited file and copy it back to where it came from (you'll have to type in your password eventually)

Thats how I got my sound, which I lost today by trying to use the EFI-Boot method to get rid of my USB-Stick. I think I messed up a lot on the way and now I'm trying to repair my damage...

Anyway I'm (not just since my recent adventure) getting this without bootstick. So if anyone knows hot to handel it, I would be glad for some help (tried the tonymac booterror0 method and recently the EFI-Bootmethod):



all the best!

janzwo



EDIT:
@octavean I think I forgot something for the audio. I had to put this in my chameleon plist:


<key>HDAEnabler</key>
<string>Yes</string>
<key>HDEFLayoutID</key>
<string>01000000</string>


I'm not sure if you need it, but I jut put it back again and now my system is working fully (with stick) again. By the way: my system can wake up after sleepmode...

greetings

janzwo

 

[Janzwo]

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

...because of my boot error. does the fact that my partition is shown as "unknown id" have anything to do with it?



...I set it on active, but found a forum entry that said:


...but it looks like setting ID=AF would mean I have to create a new partition...? I'm a bit confused by this. Does anyone know about this?

Thanks a lot!

greetings

janzwo

 

[Octavean]

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

Janzwo its good to see that you have gotten a handle on some of those issues that popped up.

I was thinking about getting a new video card. I wouldn't mind an nVidia GTX 970 or AMD 280X but something like a GTX 760 should be technically easier to setup in a Hackintosh.

For what its worth I was able to go into and out of sleep mode on my P9X79 Deluxe system using a fresh install of Yosemite without any immediate issue. However, there was a problem if the system was in sleep mode for a prolonged period of time (monitor wouldn't wake). It was almost as if a deeper sleep mode was used after a specified time and that deeper sleep mode was the problem wherein the monitor wouldn't wake.

Edit:

So my X99-A Yosemite 10.10.0 install can go into and out of sleep mode as well (fans spin down and all). There was an error message about an improperly ejected disc and a "Safari web content quit unexpectedly" error message but it woke from sleep just fine with the monitor and all. My guess is if I leave it for an extended period of time it won't wake properly though.

I can test that later, after I try the 10.10.1 update.

 

[BoomR]

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

For what its worth I was able to go into and out of sleep mode on my P9X79 Deluxe system using a fresh install of Yosemite without any immediate issue. However, there was a problem if the system was in sleep mode for a prolonged period of time (monitor wouldn't wake). It was almost as if a deeper sleep mode was used after a specified time and that deeper sleep mode was the problem wherein the monitor wouldn't wake.

Same issue here with my X99 build with GTX 970 card... would love to know if anyone has found a dependable work-around (and a log of the steps to success). THANKS!!
--B

 

[lokicat]

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

Here is my suggestion for the easiest maintenance of the all of the 10.10.x updates (Clover installs only) we are likely to see in the coming months.

1) Use a small/cheap SSD for your permanent clover boot drive. Just install clover and all of your config and kexts on this drive. There is no OS on this drive. Only difference in clover install is save RT scripts on "other" drives. I use a m.2 SSD that I purchased from Amazon for $20. As much as you can, put all your kexts and injections on the boot drive so they can't be altered by any updates. My system has nothing in the S/L/E folder on my Yosemite drive.

2) Keep using your Yosemite drive as the OS drive. You don't need Clover installed on your Yosemite drive if you use a separate boot drive as I describe above (see optional note below). I am not an expert on this, but I worry about an update overwriting stuff on the EFI partition of the Yosemite drive so that is one of the reason why I decided to create a separate Clover boot drive.

3) Before you install any update, use a cloning tool like SuperDuper to create a backup of your Yosemite drive. This is mandatory since you don't know how the update will go. I am using RAID-0 so I have an even bigger reason to make frequent clones. You don't need to backup your clover boot drive. I use a spinning drive for this because SSD requires too much effort to secure erase before making clones. Plus spinning drives are cheap.

4) Go ahead and install the update on your Yosemite drive after you complete the clone copy.

5) Until we get an official kernel that supports Haswell-E, boot into your clone and copy the kernel from your clone to your updated Yosemite drive.

6) Boot to your updated Yosemite drive and cross your fingers.

I have also given up on audio and just use USB and BT audio devices. I have invested in some high end headphones so I would use an external USB DAC even if I had onboard audio working. For those who are curious, I use a FIIO USB DAC. Any of their models work so buy one that fits your budget. I have always experienced ground loop issues which produce some amount of background noise with onboard audio on perfectly working systems so I don't miss having onboard audio. In fact, I use the same USB DAC in Windows and have disabled onboard audio.

Optional - if you do want to backup your clover boot drive, it's very easy. First take a screen shot of your Clover installation options. Next, mount the EFI partition of your boot drive and copy the entire EFI folder to somewhere safe. You only need to repeat this if you make any changes to your clover configuration and/or kexts/injections. You can also install Clover on your Yosemite drive or clone drive and use that EFI partition to backup your boot drive. This way, if your boot drive ever fails, you can use your Yosemite drive as the clover boot drive.

So in brief, my backup routine is:

a) I use realtime cloud backup for my files. This is a Synology Cloud Station.
b) If I install a new application from a download or CD (not app store), I make a SuperDuper clone.
c) If I want to update a 10.10.x patch, I follow the steps above.
d) My backup drive has Clover installed on it as well so I copy the EFI folder from my Clover boot drive to my backup drive each time I make a clone.

This looks like a lot of work, but I don't install very many "big" apps like photoshop very often and I don't update clover unless it fixes something that is currently broken. On that note my list of "broken" things are:

No native support for Haswell-E
No CPU power management
No audio