InfiniteMac OSx86

InfiniteMac OSx86 (http://infinitemac.com/forum.php)
-   Snow Leopard 10.6 (http://infinitemac.com/forumdisplay.php?f=87)
-   -   [GUIDE] How to port AppleHDA to SL (http://infinitemac.com/showthread.php?t=3981)

blkhockeypro19 09-26-2009 02:51 PM

Quote:

Originally Posted by mormegil (Post 35904)
Have you personally tried that kext in Leopard and confirmed that it's really working for YOU?

I've been using the same kext in leopard for about a year now. It works, trust me =P And I'm using PC-EFIv10.3, is that ok?

mstam 09-29-2009 05:49 PM

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

xbx2usr 10-13-2009 02:43 PM

Someone ported Sigmatel STAC9274D ?
 
Hi all,

thanks for that guide !!
Very helpful and easy to follow.

Anyway, yesterday I tried to port the AppleHDA for a STAC9247D but failed.

I modified the ST9220 in the SL AppleHDA

STAC9220 0x83847680
to
STAC9274D 0x83847621

My DSDT points to that codec-id , and the pin-config is shown in SL system profiler.
Audio-LayoutID is 4 (not 12) but if DSDT shows layout-id "4" too, it should be ok to copy-paste the layout 4 parts into the SL kext.

Of course I also tried to modify that stuff with layout-id 12 and modified the DSDT to 12 (0x0c) too, but as expected, nothing better.

Anyone here with success on that chip and can post the kext ?
VoodooHDA is working here but suffers from sleep issues.

Cheers


leclercqr 10-15-2009 11:38 PM

Same issue as Jedric
 
2 Attachment(s)
Jedric (or anyone who can help),

I have a similar issue that you have in that I get the device ID as "0x1458A002".

Have you made any progress? I any case could you send me a copy of the DSDT your using prehaps it will help be debug the compile erros I'm getting. (my DSDT is attached if someone can help, it is compiled without the HDEF code changes and is fully functional for HPET, RTC, DTGP, USB fix and Snow Leopard is fully functional with the exception of sound and SATA requiring ACHIinject.kext [I'll fix the ACHI later])


However when I change the the 'generic' HDEF code on this thread I get
Quote:

/Users/Rowan/Desktop/Snow Leopard/DSDTv0.5/dsdt.dsl 374: Notify (\_SB.PCI0.HDEF, 0x02)
Error 4063 - Object does not exist ^ (\_SB.PCI0.HDEF)

/Users/Rowan/Desktop/Snow Leopard/DSDTv0.5/dsdt.dsl 5116: Return (BUFA)
Error 4063 - Object does not exist ^ (BUFA)

/Users/Rowan/Desktop/Snow Leopard/DSDTv0.5/dsdt.dsl 5159: Return (BUFA)
Error 4063 - Object does not exist ^ (BUFA)

/Users/Rowan/Desktop/Snow Leopard/DSDTv0.5/dsdt.dsl 5202: Return (BUFA)
Error 4063 - Object does not exist ^ (BUFA)

/Users/Rowan/Desktop/Snow Leopard/DSDTv0.5/dsdt.dsl 5245: Return (BUFA)
Error 4063 - Object does not exist ^ (BUFA)

/Users/Rowan/Desktop/Snow Leopard/DSDTv0.5/dsdt.dsl 5288: Return (BUFA)
Error 4063 - Object does not exist ^ (BUFA)

/Users/Rowan/Desktop/Snow Leopard/DSDTv0.5/dsdt.dsl 5331: Return (BUFA)
Error 4063 - Object does not exist ^ (BUFA)

/Users/Rowan/Desktop/Snow Leopard/DSDTv0.5/dsdt.dsl 5374: Return (BUFA)
Error 4063 - Object does not exist ^ (BUFA)

/Users/Rowan/Desktop/Snow Leopard/DSDTv0.5/dsdt.dsl 5417: Return (BUFA)
Error 4063 - Object does not exist ^ (BUFA)
I have attached the compiled_working_DSDT i am currently using which has a different HDEF code which results in the Audio being detected in system profiler as
"Intel High Definition Audio:

Device ID: 0x1458A002
Audio ID: 12
Available Devices: "


And the added_hdef_compile_erros_dsdt in which I have changed the HDEF code to that on this thread but get errors as listed above.

Any help would be great. Thanks in advance and apologies for my lack of understanding I have only started trying to patch my own DSDT a week ago so I'm still on a steep learning curve.

airwalk776 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

msf5042 10-26-2009 02:07 PM

mormegil-
I have been going down the same paths as airwalk over and over. Here are two messages that I get over and over on boot:
Quote:

Sound assertion "0 != createAudioEngines ( fPathMap_aDriverInstance )" failed in "/SourceCache/AppleHDA/AppleHDA-174.1.1/AppleHDA/AppleHDADriver.cpp"
&
Sound assertion "0 == pathMap_aDriverInstance" failed in "/SourceCache/AppleHDA/AppleHDA-174.1.1/AppleHDA/AppleHDADriver.cpp"
Any help is appreciated

mormegil 10-27-2009 09:19 AM

Yes. Layout id doesn't matter as long as you keep it consistent i.e: If your layout id in DSDT is 79 03 00 00 (byte-flipped) => 00 00 03 79 (hex) => 889 (decimal), you will need to use layout-id 889 in plist.

@airwalk: You sure that is your codec id? Have you dumped it yourself? ALC889 shares the same codec id as ALC885 afaik. Try not to hexedit the binary and see.

msf5042 10-27-2009 01:10 PM

1 Attachment(s)
mormegil-
airwalk and I have the same setup. check my linux dump below. we are 889, not 889a.

airwalk776 10-28-2009 02:07 AM

2 Attachment(s)
mormegil...

I am 100 % sure this is the correct codecID since the codec dump I have ( taken by using a linux live dvd) Vendor Id: 0x10ec0889 ie...283904137

which is what is coded in the working applehda.

take a look a these dumps I have from when I patched the applehda for 10.5.6 (these dumps are from my board not downloaded from someone else)



Codec: Realtek ALC889
Address: 2
Vendor Id: 0x10ec0889
Subsystem Id: 0x10de0175
Revision Id: 0x100004

Then based on the dump I generated the verbs.


Question could this be caused by config data not matching pathmaps data?

BTW I tested without changing the hex values and no luck.
thank you

mormegil 10-29-2009 04:49 AM

Hmm.. You're right.

Did you inject configdata into dsdt? Might be that or your pathmaps are wrong. Just to confirm, did you use the same PathMapID under "Layouts" and "Pathmaps" in AppleHDAPlatformDriver.kext?