Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

  1. New AppleHDA Patcher

    I was using a DummyHDA w/ clover I patched myself since yosemite and it worked fine until the 10.11.4 update. I then used the aDummyHDA generated with this app (providing my files from before) and it works great! Perhaps having the "a" in the beginning affects the load order or something. To anyone else having issues with this, maybe this will help. Great app guys!
  2. AppleHDA Patcher

    Fantastic Work. I've been using a DummyHDA kext for a while now and it's been buggy and temperamental but the aDummyHDA from here just works and it generates the files needed if I decide to use another method of applehda patching. Couldn't be happier
  3. I have the Radeon r9 279 graphics card and in order to get proper graphics accel, I have to patch the AMD7000Controller (bin and info.plist patch) and AMDRadeonX4000 (info.plist patch) kexts. For both, I need to replace on of the card ids with mine in the info.plists. For the AMD7000Controller, I need to patch the frame buffer with a custom one I made for my card. I've tried to do this with clover but it doesn't work. The only thing I've found on this is here: http://www.insanelymac.com/forum/topic/282787-clover-v2-instructions/page-3?do=findComment&comment=2108022 and I followed it but it still didn't seem to work. Any ideas?
  4. Is this with the applehda from the previous post or patching applehda yourself with the other files from the last post? If it still isn't working, voodoohda is always an option
  5. Ok, I'm thinking the binary patching or something isn't working right. Try this one. If it doesn't work, I've attached the codec config, modified layout3 and Platforms (all patched already) if you want to give it a shot with the compiling and stuff. Here's a good guide: http://www.insanelymac.com/forum/topic/295001-guide-to-patch-applehda-for-your-codec/ AppleHDA.kext.zip layout3.xml Platforms.xml codecconfig.txt
  6. That's exactly what I said I'm my previous post. Try the one I patched (see last post)
  7. So the first zip attached is the patched 10.10.4 AppleHDA from Mirone's github page (https://github.com/Mirone/AppleHDA_10.10.4). I think it'll still work in 10.10.5 but don't take my word for it. It doesn't appear that you're external mic/line in is enabled in it though so I took the 10.10.5 AppleHDA, implemented Mirone's config to it, and made a few changes to enable it (2nd attachment). You should have 4 devices: internal speakers, headphones, internal microphone, and external microphone (line in). All of those devices except the internal mic are EAPD devices so you'll probably need to use EAPDFix or CodecCommander in addition to this patched AppleHDA to get those to work properly. Try them both and let me know how they work. I believe that all but the ext mic should work with mirone's assuming 10.10.4 AppleHDA will work in the 5th update and hopefully all 4 will work with mine Btw, layout id = 3 in both kexts for any hdaenablers you're using (or dsdt or boot loader) AppleHDA-272.18.1-IDT92HD81B1X5.zip AppleHDA.kext.zip
  8. If voodoo works then great! If you still want to AppleHDA though, try this one. AppleHDA.kext.zip
  9. How does the sound work with voodoohda? Do all of the devices work properly? Which ones are disabled when others are plugged in? Also, after that, try deleting voodoohda and installing the AppleHDA from post #73 with kext wizard (repair cache and such after install and then reboot). Does everything work with it? There are some slight differences between how voodoo is tracing the nodes and how I am
  10. That means that you didn't install the getdump command. First of all, do you have an admin account? You shouldn't need sudo for this command. Second, to verify that it's not installed, type ls /usr/local/bin If you don't see getdump in the resulting list, then it's not installed.
  11. That means you didn't install the get dump command. It's installed automatically into usr/local/bin when you run the voodoohda installer package in my previous post. Here's are the steps: 1. Backup and Delete AppleHDA from S/L/E 2. Delete AppleHDADisabler from S/L/E 3. Install voodoohda2.8.4 package from previous #73 4. Install latest voodoohda (see attached) with kext wizard 5. Repair permissions and kext cache with kext wizard 6. Restart 7. After restart, open terminal and type: getdump > voodoodump.txt 8. Attach the voodoodump.txt file in your user folder I don't recommend using AppleHDADisabler kext and always repair permissions and cache after making any changes to S/L/ extensions VoodooHDA.kext.zip
  12. Try Sudo getdump > voodoodump.txt
  13. Hmmm, did you remove AppleHDADisabler and voodoohda? Install the voodoohda in my previous post, then reinstall the newer voodoohda kext you were using before along with AppleHDADisabler and run the get dump command so I can see what voodoo is doing.
  14. Sounds like you installed just the kext. Install this package to get a working get dump file, then reinstall your current voodoohda kext (the get dump command in the newer versions doesn't work). Also, I goofed in the Platforms.xml which is why the speaker was disabled when the subwoofer was plugged in. Try this one VoodooHDA-v2.8.4.pkg.zip AppleHDA.kext.zip
  15. Post your codec dumps and I can take a look at it later