VoodooHDA is an open source audio driver for devices compliant with the Intel High Definition Audio specification. It is intended as an Intel-only replacement for AppleHDA on Mac OS X with support for a wide range of audio controllers and codecs (Wiki). The following guide will show how to properly key VoodooHDA so that VoodooHDA and AppleHDA can be loaded at the same time. This allows for AppleHDA to be used for HDMI Audio on systems with Onboard Audio Codex that can not be enabled using a patched AppleHDA.

Index:

Accreditation
Section 1: Downloading VoodooHDA
Section 2: Identifying Audio Device ID
Section 3: Editing VoodooHDA
Section 4: Verification

Guide:

Accreditation:

Andrew Kern – Publisher
Nick Smith – Editor
Oldnapalm’s post found here.

Section 1: Downloading VoodooHDA

1. Download the latest standalone VoodooHDA.Kext here.

2. Open the Download Folder:

Screen Shot 2014-12-07 at 12.07.00 PM

3. Locate VoodooHDA.kext

Screen Shot 2014-11-29 at 9.33.06 PM

4. Move VoodooHDA.kext to the Desktop.

5. Continue to Section 2.

Section 2: Identifying Audio Device ID 

1. Obtain IORegistryExplorer here.

2. Open IORegistryExplorer:

IORegistryExplorer

3. Locate the Audio Device:

Screen Shot 2014-12-21 at 2.31.59 PM

4. On the Right Side, identify the Audio Device IOName:

Screen Shot 2014-12-21 at 2.34.57 PM

5. Record the full IOName:

pci8086,9c20

6. Identify the sections as shown below:

pci8086,9c20

7. Convert the IOName as shown below:

0x9C208086

8. Continue to Section 3.

Section 3: Editing VoodooHDA

1. Right Click on VoodooHDA.

2. Select Show Package Contents:

Screen Shot 2014-11-29 at 9.34.19 PM

3. Open Contents Folder:

Screen Shot 2014-11-29 at 9.35.55 PM

4. Open Info.plist:

Screen Shot 2014-11-29 at 9.36.45 PM

5. Locate the following:

<key>IOPCIClassMatch</key>
<string>0x04020000&amp;0xfffe0000</string>

6. Replace this code with the following:

<key>IOPCIPrimaryMatch</key>
<string>0x43831002</string>

7. Replace 0x43831002 with the converted IOName found in Section 2:

0x9C208086

8. Save the Info.plist.

9. Install VoodooHDA.kext using Kext Helper B7.

10. Restart.

11. Continue to Section 4.

Section 4: Verification

1. Test audio for functionality at this time.

27 Comments on "VoodooHDA Editing"

  1. Hi! For some reason, mute doesn’t work for me. I applied the mute fix in the .plist file but it still doesn’t work. Any ideas?

    Reply
  2. Record the full IOName:

    pci8086,9c20

    6. Convert the IOName:

    0x9C208086

    could you explain how this is done please

    thanks

    Reply
  3. Well I have audio working with VooDoo on my z97x Gaming G1, but there’s totally no volume control at all

    Reply
    • Try changing enabling the volume fix in the Plist. Will be added to the Guide when we have time.

      Reply
      • So I did a totally fresh install and no audio installs whatsoever and just used a USB DAC that I tested in a real MacBook Pro.

        On this fresh Haswell install, the audio works but when you change the volume the HUD pops up showing the volume level going up and down but the *actual* volume level isn’t going up and down.

        I know it’s not the USB DAC since I tested it on the real MacBook Pro and on that machine the volume up and down controls (keyboard) perfectly changed the volume from the DAC as you’d expect.

        I did this to test that it wasn’t VooDoo at all.

        Any idea why a fresh Haswell install with Clover & kexts all installed and up and running is doing this?

        Sound works from the USB DAC, and the volume control is “controlled” just fine, but the actual sound output volume itself isn’t being changed?

        Thanks!

        Reply
  4. It’s on a USB 2 port actually

    Also – The email notification of replies for the site here isn’t working (just fyi)

    Reply
  5. No no.
    I’m going to use a different MoBo and *not* use Voodoo

    Reply
  6. Hey Andrew,

    I have set up my Mackintosh using two of your guides here, one for a Fusion Drive and the other one for setting everything else up.

    My sound is working but every once in a while I get the Kernel Panics I have provided in the link down below:
    I’m not sure if they’re all the same.

    I hope you can help me out with that. If you tell me that it’d be better to use this guide to make audio work, what kexts would I have to remove before following this guide?

    https://www.dropbox.com/sh/x0hazjt9mgf0ur1/AAAUlDY4v2q-KelgL-NtxEKha?dl=0
    I have the following components:
    ASUS P7Z68-V/GEN3 Motherboard
    Realtek® ALC892 Audio
    Intel I5 2400
    ATI Radeon 5770
    HyperX Fury DDR3 Ram (4GB)
    Fusion Drive

    Reply
    • Why are you not just patching AppleHDA for your Audio Codex? Or do you have a 3xxx Series BIOS Flashed?

      Reply
      • No I don’t have a Flashed BIOS as far as I remember. I know that I had one but I’m pretty sure that I have changed it back to an official BIOS as I had problems.

        I will probably update to the newest BIOS which is 8302 or something. I have 6… something.

        I will be patching the codec as you described in the Tutorial but I guess I will have to remove some old ones before as they’re causing problems.

        Should I just delete the ones that appear in the Kernel Panic?
        After that patching the VoodooHDA.kext should be a working solution for me?

        Reply
  7. I did. There are three pictures in the Dropbox Link I have provided in the first comment.

    Reply
  8. Hey, aren’t you going to tell me what I have to do 😀
    I guess you just forgot about me.

    I have one more question which is not about the Audio.
    I have just run a Cinebench Test to compare my Hackintosh to my MacBook Pro 15″ late 2014 and I found out that Cinebench only used 2 Cores with 4 Threads, my CPU is an Intel i5 2400 which is actually supposed to have 4 Cores. What’s going on there?

    Reply
    • Not sure about the CPU issue.

      Reply
      • I still need assistance with the Audio.
        Did you look up the picture?

        The CPU is a rather small problem since in “about this Mac” the system is showing 4 Cores.

        Reply
        • The CPU is not a problem. A CPU is physical so anything regarding that would be cosmetic so forget the CPU.

          Also you never answered my question from before about the BIOS. So that is why you did not get any response.

  9. I did :O

    “No I don’t have a Flashed BIOS as far as I remember. I know that I had one but I’m pretty sure that I have changed it back to an official BIOS as I had problems.”

    That’s a no for me.

    Reply

Leave a Reply

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

Time limit is exhausted. Please reload the CAPTCHA.