[GUIDE] ALC889a (with analog 5.1 surround)

[mormegil]

What do you see in outputs?

[monsieur.d]

I have 3 line outs and 1 Digital out. The first line out works fine with the speakers that are connected in the back panel.

I used to have speakers AND headphones working in Leopard (10.5.6) with patched AppleHDA. I know I can't use Leopard's AppleHDA, but can I somehow copy its setup (considering that now I have a patched DSDT and patched AppleHDA according to this thread)?

[mormegil]

Originally Posted by monsieur.d I have 3 line outs and 1 Digital out. The first line out works fine with the speakers that are connected in the back panel. I used to have speakers AND headphones working in Leopard (10.5.6) with patched AppleHDA. I know I can't use Leopard's AppleHDA, but can I somehow copy its setup (considering that now I have a patched DSDT and patched AppleHDA according to this thread)?

http://www.infinitemac.com/f57/guide...a-to-sl-t3981/

Anyway, by headphone do you mean the front jack? If so, have you tried plugging in a headphone? It might have jack-sensing enabled. Plugging in a headphone to front port will mute line out at the back. Try this and check in sound pref if one of your outputs change into 'headphone' once you plug it in.

[monsieur.d]

Yes, by headphones I mean the front jack.

I tried connecting the headphones both in the headphone out and the mic in and nothing happened.

I'll try your guide and post back. thanks

[monsieur.d]

Dear mormegil,

Thanks for the orientation. All I needed to do was to edit the "plist" files using the plists I had working under Leopard.

Now I have "Headphones" (front jack) in the sound preferences and it works just fine.

D

[MiniHack]

I have a quick question about what I do and do not need to include in my HDEF mod.s in the DSDT.
On the initial pages and guide in first post, it seems that Pinconfig/Configdata is not needed in the DSDT itself as it will read that from the plists in AppleHDA.kext. However, in later posts I see a lot of DSDTs with that data inserted. So......if the AppleHDA is correct does the DSDT really need these info.s also? If the answer is no, then this will give me one less variable to work with in my experiments.
Thanks for the excellent guide by the way and I promise not to be a serial re-poster about this. Just want to get this one point clear.
Thank you.

[mormegil]

Originally Posted by MiniHack I have a quick question about what I do and do not need to include in my HDEF mod.s in the DSDT. On the initial pages and guide in first post, it seems that Pinconfig/Configdata is not needed in the DSDT itself as it will read that from the plists in AppleHDA.kext. However, in later posts I see a lot of DSDTs with that data inserted. So......if the AppleHDA is correct does the DSDT really need these info.s also? If the answer is no, then this will give me one less variable to work with in my experiments. Thanks for the excellent guide by the way and I promise not to be a serial re-poster about this. Just want to get this one point clear. Thank you.

Here

You DON'T need pinconfig in dsdt. You DO however need Configdata in plist.

[MiniHack]

Thanks Mormegil and Snow. I now have working audio in Snow Leopard from DSDT and modded AppleHDA.kext with my Zotac board....took a while, but finally figured things out.

[Elventanis]

I tried this using Ubuntu installed in a Virtual Machine via Sun Virtual Box. Maybe that is the reason I am having the issue. I will try to boot off the Ubuntu CD directly and see if that makes a difference I suppose.

When I type the commands, I actually get an error message that the directory/codec#1 etc does not exist. So the dump file is useless, cause the command errors out.

[will1384]

Originally Posted by Elventanis I tried this using Ubuntu installed in a Virtual Machine via Sun Virtual Box. Maybe that is the reason I am having the issue. I will try to boot off the Ubuntu CD directly and see if that makes a difference I suppose. When I type the commands, I actually get an error message that the directory/codec#1 etc does not exist. So the dump file is useless, cause the command errors out.

Virtual Machine wont work, the Virtual Machine sets up a fake environment,
Linux has to be running directly on your hardware.