[GUIDE] ALC889a (with analog 5.1 surround) - Page 4

mormegil · #31 09-02-2009, 12:34 AM

Simple.

Either use the 2 plist's I made for Snow and insert them into your SL AppleHDA (rename them first)

or

go here. tmonkol's unified plist or so called LegacyHDA.kext should be the easier way out. Look for the latest package dated 6-8-2009. Don't really have to go through King's tutorial since your audio chipset has already been excellently documented.

Next step is DSDT. Don't really think it's that complicated. Again, tmongkol has a link to DSDT Patcher by fassl. Just a matter of running it once to generate your dsdt.aml.

Decompile it:

Quote:

iasl -d dsdt.aml

Insert HDEF code into dsdt.dsl
Recompile it:

Quote:

iasl -ta dsdt.dsl

CyCLoBoT · #32 09-02-2009, 11:45 PM

I finally got sound to work on my EP45-DQ6 motherboard but I am noticing that more sound is coming out of one of the speakers than the other. I only have 2.1 speakers. Anyone noticed something similar?

Gurruwiwi · #33 09-03-2009, 02:33 AM

Mormegil,

Thanks for the help!

I've tried everything, nothing works. I finally manage to get a stable fully operational SL, but no audio

Irritating as hell because just two days ago while starting to experiment with kexts, it worked nice.

I generated a new dsdt.aml with DSDT Patcher GUI 1.02, forcing compile and new HPET.

From that, the dsdt.dsl file.

I tried following a couple of guides, for example "search for AZAL and substitute with HDEF" - but I have no AZAL entries. Or "copy this over that" but I dont get how long is "over that" without knocking out necessary code.

I also have another issue, from one guide I managed to substitute a code entry, and wanted to test that. Saved dsdt.dsl, then with iaslME.app I couldnt generate the .aml file because I cant find it. Says everything worked fine, got 1 error (is that ok?), but it didnt output any dsdt.aml file back. I used this app to generate the dsl file and it worked ok.

Mind taking a look please?

Snow · #34 09-03-2009, 06:47 AM

Error isn't ok since it doesn't output an aml file m8.

Is it DTGP related? (check log) because if so go back a few pages for a fix.

mormegil · #35 09-03-2009, 12:02 PM

You have to insert the code if it's not present. Was the same as me. Just copy and paste the whole "Device (HDEF)" block of code so that it appears under "Device (PCI0)" (i.e. subset of it). Read the guide by King again.

Gurruwiwi · #36 09-03-2009, 01:02 PM

Guys,

Some progress, but not that much.

I've substituted everything under HDEF to be exactly as Kings tutorial PDF.

Checked three or four times, line by line. I save dsdt.dsl, drag to iasl me, and it says

Code:

Copyright (C) 2000 - 2008 Intel Corporation
Supports ACPI Specification Revision 3.0a

/Users/bigbang/Desktop/DSDT dsl to aml/dsdt.dsl  9592: [*** iASL: Read error on source code temp file /Users/bigbang/Desktop/DSDT dsl to aml/Sessions/2009-09-03-125900/dsdt.src ***]
Error    4095 -         syntax error, unexpected $end ^ 

ASL Input:  /Users/bigbang/Desktop/DSDT dsl to aml/dsdt.dsl - 9593 lines, 326239 bytes, 4052 keywords
Compilation complete. 1 Errors, 0 Warnings, 0 Remarks, 0 Optimizations

        All done.
        Enjoy ...

but the only file present in the "sessions" directory is log.txt that reads

Code:

Intel ACPI Component Architecture
ASL Optimizing Compiler version 20080926 [Oct  4 2008]
Copyright (C) 2000 - 2008 Intel Corporation
Supports ACPI Specification Revision 3.0a

/Users/bigbang/Desktop/DSDT dsl to aml/dsdt.dsl  9592: [*** iASL: Read error on source code temp file /Users/bigbang/Desktop/DSDT dsl to aml/Sessions/2009-09-03-125900/dsdt.src ***]
Error    4095 -         syntax error, unexpected $end ^ 

ASL Input:  /Users/bigbang/Desktop/DSDT dsl to aml/dsdt.dsl - 9593 lines, 326239 bytes, 4052 keywords
Compilation complete. 1 Errors, 0 Warnings, 0 Remarks, 0 Optimizations

So what am I doing wrong?

attached is the dsdt.dsl with the copied code...

Snow · #37 09-03-2009, 01:34 PM

I've tried to mod your dsl file but it even gives me more errors (6) so I'm afraid I cannot help you with this m8.

mormegil · #38 09-03-2009, 04:49 PM

I just force compiled and ignored the warnings. All errors I've corrected.

Gurruwiwi · #39 09-03-2009, 08:11 PM

Thanks Snow and momergil! but it broke the system.

Copied dsdt.aml to root. Rebooted and AppleHDA panic'ed. during boot (just -v)

Reboot again in verbose, no KP, but AppleHDA gave back "assertion 0" error codes, went to desktop, and in desktop, "warm" KP. Just before, I managed to see that device ID is Device ID: 0x10250146, Audio ID: 12 and all ports show up.

In Leo and SL Install stage, it reads

DEVICE ID: 0x1458A002
Audio ID: 12

So, that may be a clue.

Anyway, tried rebooting again, and when the screen goes black to wake up again and show desktop... it flashes black and blues in 5 second intervals, and stays like that, same symptom as my previous attempts with SL.
I go in Leo and put SL in an enclosure, delete dsdt.aml from root and verify disk just in case one of my "power shutdowns" went bad, but drive seems ok.
Tried rebooting with SL in -x and -x32 and -x -x32... same symptom.
So basically, my install broke. Thank God I have a base image of it !
The first and second dsl file I uploaded here, I already tried editing a bit, only below the HDEF entry, just as per first King's tutorial, the rest I didn't dare do.

I will upload in this post an un-edited file from my recently patched aml file that was forced compiled and newHPET using GUI patcher 1.02

Why would this file break my install? and What did it do, that removing it still screws with SL?
I'll try cloning it again and try fresh with this dsdt.aml again...
I have gfx string in com.apple.Boot.plist, but we did nothing in dsdt for gfxs, this symptom happened before and I dont know how to recoup from it.

Ideas?

mormegil · #40 09-03-2009, 10:00 PM

Nothing to do with dsdt I think. Perhaps your gfx string that's the issue. I've heard EFI string which works in Leopard might not always work with SL. You're using the plists I posted in this thread correct? Rename to Info.plist and replace the original ones? Repair permissions etc.?