About:

 

Today we are releasing the new Haswell DMG updated that includes updated SSDT’s for MSI and Asus 9-Series Motherboards. This update enables onboard audio for MSI motherboards and Asus motherboards running with the latest BIOS Release.

To patch audio you will need to make some changes with the script. I am going to see if the script can be changed for the long term so the following steps are not always needed. Download the script via the link on the DMG. Unpack the correct script. Right Click on the script and then find all HDEF and replace them with HDAU. Then save and then run the script. Then the script will patch audio. Enjoy.

Please post IOREGS after the update so that we can inject Ethernet onto every boards SSDT.

57 Comments on "Haswell DMG Updated for MSI and Asus"

  1. It’s worth noting that the user will need to reboot using the supplied SSDT in order for the modified script to work — if I’m following the process correctly during install for my Asus Gryphon z97; the HDEF device you may have will be changed to HDAU by virtue of the SSDT being present, and *then* a modified version of Toleda’s script will snag the right devices when it looks in the device tree.

    So two reboots and you’re done. Audio device shows up for me now, will do more testing later but I’m glad to see it.

    Reply
    • I’m assuming that people are already using Mac OS X and have since updated the BIOS. A supplemental guide will be added to the DMG later on this week on how to fix the script.

      Reply
      • Sure, but if they weren’t renaming devices via a functional SSDT the device will register as HDEF, at least it did on my workstation. Once I had booted with your SSDT the device reports as HDAU and then a modified script (use sed(1) imo) fixed up a driver extension as expected.

        Reply
        • Im killing HDEF in the SSDT update. See the status being returned? The issue is the HDEF on the board has DSM methods already in place and the way to make the SSDT injection work is to kill them so I have to remake the device using HDAU.

          You can run the script un-edited before the SSDT is installed but the script will prompt you about having a pin layout of 0.

  2. SSDT v1.2 not booting for me. Z97-Deluxe. had to revert back to v1.1.

    See Ioreg and System.log here:

    https://www.dropbox.com/s/qy2ghzsrvuej7nw/Ioreg_system.log.zip?dl=0

    Thanks

    Reply
  3. Hey Andrew you find the fix for 5Ghz fix for z97-deluxe
    in 10.10.2 ?

    Reply
  4. I have no idea what is going on I will do more testing tonight. There was one issue my fault I forgot to change a setting in clover when I was setting up Audio I put device ID in clover. Once I removed that it got all the way to the point where I could see X79 Platform Plugin loaded. Now it just reboots instead of getting stuck. I’ll verify I have only the needed clover drivers installed. Next I will remove all hardware and maybe even put in a Nvidia GT 640 instead to test. Thanks

    Reply
    • You failed to follow my install guide and also failed to follow the set instructons on the DMG READ ME. Also this post is for Haswell and not x79. I can not help you if you will not follow the DMG READ ME as what you just posted tells everyone and myself you have not done so. Wipe the System and follow the Install Guide and DMG READ ME post install to correct your Errors. Else you will have a broken System. Do not Change or install anything on the DMG and do not install any onther Kext that is not found on there.

      Reply
  5. Andrew that was a clerical error that should have said X86 not X79. That is the Native Apple driver that loads. I did not load any kexts outside of what comes in the Haswell.dmg. I did follow your instructions every step. I will go back and repeat just to make sure. You SSDT v1.1 works fine you SSDT v1.2 does not.

    Reply
  6. Ok I started over same issue with SSDT. Here the last thing I see before the reboot. Feb 6 09:47:16 localhost kernel[0]: X86PlatformShim::sendPStates – Success! Thats what I meant not X79 sorry.

    Reply
  7. Question about modifying the audio script. Mine would be the “audio_alc_9series-hda-93_patch.command”, unless I am incorrect for the haswell, Z97-deluxe. The script is very short nothing at all like the other scripts. I do not see anything regarding HDEF in that script? The script “audio_realtekALC-100_v1.0.4.command” for example does have the HDEF inside.

    Thanks

    Reply
  8. so the script we have to modify is the audio_realtekALC-100_v1.0.4.command?

    Reply
  9. Ah, so this may explain why I noticed audio wouldn’t work on some boots (or the volume would be very low – near inaudible) with my ASUS Z97-DELUXE running the latest BIOS and VoodooHDA (since the AppleHDA patches didn’t work at the time for me as it didn’t detect any audio codec). Nonetheless, updated the DSDT and I’ll test. Should I remove VoodooHDA and try a AppleHDA patch even though VoodooHDA seems to be working pretty great for me?

    Reply
    • Drop VoodooHDA and Forget it exists in your case. Remove it and then reinstall the 10.10.2 Combo update and then apply the Audio patch and new SSDT.

      Then if Audio is low on some boots there is a NVRAM fix you can write to the NVRAM to address this if needed.

      Reply
      • I tried the audio patch and it works fine. But, there’s one issue with using it for me. For whatever reason the green line out/speaker port doesn’t work – you need to use the black rear port instead. That’s all fine and dandy when using both Mac and Ubuntu at the same time as they work fine that way. However, with my tri-boot setup Windows (and the Realtek drivers) won’t allow me to use the black rear port as a secondary speaker/line out port no matter what I do so I had to drop back to using VoodooHDA as a workaround. What I might try doing is purchasing an optical cable and use optical for Mac and the green speaker/line out port for Windows and Ubuntu.

        Very interested in the NVRAM fix, where it it located?

        Thanks a lot! 🙂

        Reply
        • This issue is now corrected for me, as I bought a USB DAC and I don’t need to patch AppleHDA anymore or use VoodooHDA.

  10. SSDT v1.2 made my system to not boot. No errors were showed, the system just rebooted everytime.
    My motherboard is an Asus Z97M-Plus and Intel processor is a i5 4690 with a GTX 770.
    When I reverted back to v1.1 it booted fine. I don’t know if you want a ioreg file with the new update because I can’t make as the system can’t even boot, but here’s the ioreg of the ssdt which works(v1.1): http://a.pomf.se/qmhnhn.ioreg

    Reply
  11. For the ASUS Z97-DELUXE board, a new BIOS (2205) was released today.

    Reply
  12. Is ALXEthernet.kext needed on a normal Gigabyte 1150 mobo?

    Reply
  13. The audio on my Asus Z97 is not ideal, but I may have done something to influence the outcome. It looks like everything is stereo-only and the optical SPDIF output isn’t usable. I can see it in System Preferences and use it as an output device, but it never sends signal.

    I don’t use HDMI audio at all, I’d much rather have an optical output, but I don’t know if my path to resolution is removing the HDEF/HDAU from your SSDT and going alone or if I did something wrong.

    Reply
  14. Hey Andrew i’m trying to get audio working on the MSI z97 gaming 7, in regards to the patch can you be more specific which line of code and were exactly do we change HDEF to HDAU? thanx

    Reply
  15. Never mind I figured it out I used text edit then Edit/Find/Find and Replace. window opens up and under find type in HDEF and Replace with HDAU then press All button and save script and then run it now sound works. thanks Andrew for your hard work. 🙂

    Reply
  16. Andrew thanks for sharing all of this incredible wealth of information and invaluable downloads. I have the Asus Z97-Deluxe with Haswell I7-4790K. After installing 10.10.5 the only issue I ran across was with my samsung 2k Monitor LU28D590 with either the Display port or HDMI connection. I would get a reboot every time right after the NVDAGK100Hal loaded and registered, XCPM Registered and IOPPF Mode: XCPM. Those are the messages I see in verbose right before I get to the desktop from a successful boot. Once I connect my Samsung 22 inch LCD (DVI) I was able to boot to the desktop as normal. I thought it might be my EVGA GTX 770 at first but found out that just switching monitors and connections would get me to the desktop and then after that connecting the 2k monitor back onto the display port, would allow normal booting. This was the only very strange behavor I have seen when upgrading and only specific to 10.10.5!

    Reply
    • I have had that monitor for 1-1/2 years and have never seen that issue. I have had some motherboards (older) not showing any splash screen when booting the first time on the monitor. Try disabling onboard graphics and go from there. Report back.

      Reply
  17. Sorry the 2K is actually a 4k monitor my mistake

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload the CAPTCHA.

About Andrew Kern