Need help editing SSDT files and free from errors!

[davidm71]

Hi,

 

I have been following dsdt making guides and I am stuck with my SSDT files in that one of them doesn't compile correctly as I probably must make edits but not sure how. I ran a script inside a Ubuntu boot CD to get these tables and I have three SSDT files denoted by AMI-CST, AMI-IST, and AMICPU. The latter AMICPU fails to compile or compiles with errors in DSDT-SE.

 

The guide I'm following asks that all SSDT files be appended to the end of the DSDT Master file. Not sure if thats right as some people use separate SSDT file..

 

Any help would be appreciated,

 

Thanks.

 

Heres the file:

 

 

*
* Intel ACPI Component Architecture
* AML Disassembler version 20091214
*
* Disassembly of ./dsdt.aml, Tue Nov 22 01:11:46 2011
*
*
* Original Table Header:
*	 Signature		"SSDT"
*	 Length		   0x000001D6 (470)
*	 Revision		 0x01
*	 Checksum		 0x10
*	 OEM ID		   "AMICPU"
*	 OEM Table ID	 "PROC"
*	 OEM Revision	 0x00000001 (1)
*	 Compiler ID	  "MSFT"
*	 Compiler Version 0x03000001 (50331649)
*/
DefinitionBlock ("./dsdt.aml", "SSDT", 1, "AMICPU", "PROC", 0x00000001)
{
External (\_PR_.OSC_, IntObj)
External (\_PR_.PDC_, MethodObj)	// 1 Arguments

Scope (\_PR)
{
	Processor (P000, 0x01, 0x00000410, 0x06)
	{
		Method (_PDC, 1, NotSerialized)
		{
			\_PR.PDC (Arg0)
		}

		Method (_OSC, 4, NotSerialized)
		{
			Return (\_PR.OSC)
			Arg0
			Arg1
			Arg2
			Arg3
		}
	}

	Processor (P001, 0x02, 0x00000410, 0x06)
	{
		Method (_PDC, 1, NotSerialized)
		{
			\_PR.PDC (Arg0)
		}

		Method (_OSC, 4, NotSerialized)
		{
			Return (\_PR.OSC)
			Arg0
			Arg1
			Arg2
			Arg3
		}
	}

	Processor (P002, 0x03, 0x00000410, 0x06)
	{
		Method (_PDC, 1, NotSerialized)
		{
			\_PR.PDC (Arg0)
		}

		Method (_OSC, 4, NotSerialized)
		{
			Return (\_PR.OSC)
			Arg0
			Arg1
			Arg2
			Arg3
		}
	}

	Processor (P003, 0x04, 0x00000410, 0x06)
	{
		Method (_PDC, 1, NotSerialized)
		{
			\_PR.PDC (Arg0)
		}

		Method (_OSC, 4, NotSerialized)
		{
			Return (\_PR.OSC)
			Arg0
			Arg1
			Arg2
			Arg3
		}
	}

	Processor (P004, 0x05, 0x00000410, 0x06)
	{
		Method (_PDC, 1, NotSerialized)
		{
			\_PR.PDC (Arg0)
		}

		Method (_OSC, 4, NotSerialized)
		{
			Return (\_PR.OSC)
			Arg0
			Arg1
			Arg2
			Arg3
		}
	}

	Processor (P005, 0x06, 0x00000410, 0x06)
	{
		Method (_PDC, 1, NotSerialized)
		{
			\_PR.PDC (Arg0)
		}

		Method (_OSC, 4, NotSerialized)
		{
			Return (\_PR.OSC)
			Arg0
			Arg1
			Arg2
			Arg3
		}
	}

	Processor (P006, 0x07, 0x00000410, 0x06)
	{
		Method (_PDC, 1, NotSerialized)
		{
			\_PR.PDC (Arg0)
		}

		Method (_OSC, 4, NotSerialized)
		{
			Return (\_PR.OSC)
			Arg0
			Arg1
			Arg2
			Arg3
		}
	}

	Processor (P007, 0x08, 0x00000410, 0x06)
	{
		Method (_PDC, 1, NotSerialized)
		{
			\_PR.PDC (Arg0)
		}

		Method (_OSC, 4, NotSerialized)
		{
			Return (\_PR.OSC)
			Arg0
			Arg1
			Arg2
			Arg3
		}
	}
}
}

[LatinMcG]

fail to compile.. what errors ??

 

what mobo ? im sure u can check someones dsdt.dsl with textwrangler to compare.

 

just add from

Scope (\_PR) and bellow to dsdt. (notice above scope has a { so remove one } at end when copying to dsdt.)

 

im curious why u doing it this way.. chameleon2 rc5 or higher can do GenerateCStates and PStates

[Gringo Vermelho]

The guide I'm following asks that all SSDT files be appended to the end of the DSDT Master file.

Yeah, I agree with LMG, don't do that. Must be a very old guide.

 

Read about how to load your SSDT tables with Chameleon here:

http://www.insanelymac.com/forum/index.php?showtopic=225766

Note that Chameleon is now at 2.1, don't use the old version from that thread.

 

If you for some reason want to modify your DSDT processor scope (you shouldn't have to) make sure to make the same modifications where the processor scope is referenced in your SSDT tables, otherwise CPU power management will not work correctly.

[davidm71]

fail to compile.. what errors ??

 

what mobo ? im sure u can check someones dsdt.dsl with textwrangler to compare.

 

just add from

Scope (\_PR) and bellow to dsdt. (notice above scope has a { so remove one } at end when copying to dsdt.)

 

im curious why u doing it this way.. chameleon2 rc5 or higher can do GenerateCStates and PStates

 

 

Guess its an old guide though was a sticky thread on this forum. So you guys are saying you don't need to make a SSDT file anymore? I thought you did to enable proper sleep and speedstep modes and such. Though I did add Generate P + C state commands into com.chameleon.boot.plist and the start up verbose messages said can't generate those p + c states. Have those options all set to enabled and not auto also. I haven't tried to put the machine into sleep however as I just assumed it wouldn't work as it did on my last motherboard that was a P8P67 Deluxe. Since then I upgraded to a P8Z68 Deluxe and am using a DSDT I found on a Tonymacx86 guide by vdmesis and twosixy. I mean is a dsdt even necessary anymore? The only thing I gained was eSata support with the loss of ps2 keyboard support (ps2 keyboard works without dsdt not with). And my audio which is an ALC889 works with HDAenabler kext. Couldn't get a dsdt injection to work. So I'm wondering what real worth is there to a dsdt then if the latest Chameleon is baked in with P + C support?

 

Thanks.

 

PS: Using the latest Chimera from [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] Lion edition 4.1.