[GUIDE] How to port AppleHDA to SL - Page 2

Pietruszka · #1 09-10-2009, 09:07 AM

yes I've patched DSDT

still doesn't work for me...maybe I do something wrong.....

anyway thanks for help

tokyovigilante · #2 09-16-2009, 03:55 AM

This is fantastic thanks. Had my AD1988B (Asus P5K-E) running with a plist injector kext, but this method allows use of my SPDIF output. Great stuff!

mstam · #3 09-29-2009, 05:49 PM

Thank you so much! I now have 5.1 surround sound working again over S/PDIF digital out!

airwalk776 · #4 10-26-2009, 01:23 AM

mormegil....

It shouldnt matter but as long as all the locations that state layout ID are 889 vs your 12 it should still work right ?

my dsdt is coded with layout-id as 79 03 00 00

and a codec-id of 89 08 EC 10

so I followed all your steps, hexedit found all 4 locations with 8508ec10 and replaced with 8908ec10

edited the two plists as show in the post.

still no go. the 1.5.7a24 AppleHDA and my dsdt file I get audio in SL. but the edited AppleHDA from a SL install does not work.

Any ideas? thanks

hassan · #5 06-28-2010, 11:14 PM

now this is an easy guide, however, I do not have a working applehda.kext, I'm basically starting from scratch. No other guide seems to have a clear method of doing this, I've read Kings guide but that's incomplete and all over the place.

arm1tage · #6 09-10-2009, 10:45 AM

This also did not work for me (Dell E6500, IDT audio byteflipped hex:8508EC10) even with pathed DSDT. However now I have a new mysterious New Interface Detected - PCI Serial Adapter (3) in my Network Prefs...

mormegil · #7 09-10-2009, 01:53 PM

Quote:

Originally Posted by arm1tage

This also did not work for me (Dell E6500, IDT audio byteflipped hex:8508EC10) even with pathed DSDT. However now I have a new mysterious New Interface Detected - PCI Serial Adapter (3) in my Network Prefs...

That codec address belongs to alc885/alc889a from realtek. Get your own dump with a linux live cd.

Gurruwiwi · #8 09-10-2009, 12:34 PM

Following your guide mormegil, now with all the info you helped me gather, I have "found" that ALL the "assertion "0"" verbose errors are gone, all except one! The system does not crash anymore or KP's, once in a while it triggers double verbose messages. An error I know I created, because I deleted an entry to make my plist as close in structure as your guide, and I'm pretty sure it had this name. I inside it was an entry called codecAddressMaskData. The whole verbose line reads

Code:

Sound assertion "0 == codecAddressMaskData" failed in "/sourceCache/AppleHDA/AppleHDA-174.1.1/AppleHDAcontroller.cpp" at line 1159 goto Exit

I will try again tonight from scratch, but I guess I cant just leave vanilla values, will try though.

You know where I can find this info regarding my chip?

mormegil · #9 09-10-2009, 01:56 PM

Quote:

Originally Posted by Gurruwiwi

Following your guide mormegil, now with all the info you helped me gather, I have "found" that ALL the "assertion "0"" verbose errors are gone, all except one! The system does not crash anymore or KP's, once in a while it triggers double verbose messages. An error I know I created, because I deleted an entry to make my plist as close in structure as your guide, and I'm pretty sure it had this name. I inside it was an entry called codecAddressMaskData. The whole verbose line reads

Code:

Sound assertion "0 == codecAddressMaskData" failed in "/sourceCache/AppleHDA/AppleHDA-174.1.1/AppleHDAcontroller.cpp" at line 1159 goto Exit

I will try again tonight from scratch, but I guess I cant just leave vanilla values, will try though.

You know where I can find this info regarding my chip?

Is your audio working in 10.5?

Gurruwiwi · #10 09-10-2009, 02:32 PM

Yes, but with voodooHDA.

I just went through it again, and I surely did something wrong the last time because I didnt find that codecAddress thing on the way. Started again and made double sure I had vanilla appleHDA.

I have my very own codec dumps from linux, the only guessing I did was pathmapID being 9. The rest is absolutely my system.

Rebooted and KP'd unfortunately.

Note: When I redid the steps, I noticed that when editing AppleHDA/macos/appleHDA hex to byte flip the codec, when you save, it created a text file (appleHDA.txt) and the hex is renamed "appleHDA~". So the second time I copied it out to another folder, edited, saved, created the same output, renamed and removed the "~" and copied it back in (just hex file). Dont know if this is relevant, but I thought it would be interesting to share.