Jump to content

DSDT - Vanilla Speedstep - Generic Scope (_PR)

FKA

By FKA,
in Power Management

 Share
1,949 posts in this topic

Recommended Posts

FKA
FKA
Posted
  • Author
Posted

try something along these lines under Scope (PR

 

    Scope (_PR.CPU0)
   {
	    Method (_PSS, 0, NotSerialized) // P-states
	    {
	        Return (Package(0x07) // this reads 0x05 because I have 5 x P-states. This number should match you total P-states.
	        {
	            Package (0x06) { 1992, 1250, 10, 10, 0x0C2B, 0x0 },
	            Package (0x06) { 1826, 1200, 10, 10, 0x0B27, 0x1 }, 
	            Package (0x06) { 1660, 1150, 10, 10, 0x0A23, 0x2 }, 
	            Package (0x06) { 1494, 1100, 10, 10, 0x091F, 0x3 },
	            Package (0x06) { 1328, 1050, 10, 10, 0x081B, 0x4 },
				Package (0x06) { 1162, 1000, 10, 10, 0x0717, 0x5 }, 
	            Package (0x06) { 996, 950, 10, 10, 0x0613, 0x6 } 
	        })
	    }

	    Method (_PSD, 0, NotSerialized)
	    {
            	Return (Package (0x05)
            	{
               	0x05,
               	0x00,
               	0x00,
               	0xFC, // Double-checked the 0xFC value with ACPISpec v4.0 pdf
               	0x02  // Number of Processors - Again if you have a Quad core CPU then this value should read 0x04
            	})
       	   }

       Method (_CST, 0, NotSerialized)
       {
           Return (Package (0x02)
           {
               One, 
               Package (0x04)
               {
                   ResourceTemplate ()
                   {
                       Register (FFixedHW, 
                           0x01,               // Bit Width
                           0x02,               // Bit Offset
                           0x0000000000000000, // Address
                           0x01,               // Access Size
                           )
                   }, 

                   One, 
                   0x9D, 
                   0x03E8
               }
           })
       }
   }

   Scope (_PR.CPU1)
   {
       Method (_PSS, 0, NotSerialized)
       {
           Return (^^CPU0._PSS ())
       }

       Method (_PSD, 0, NotSerialized)
       {
           Return (^^CPU0._PSD ())
       }

       Method (_CST, 0, NotSerialized)
       {
           Return (Package (0x04)
           {
               0x03, 
               Package (0x04)
               {
                   ResourceTemplate ()
                   {
                       Register (FFixedHW, 
                           0x01,               // Bit Width
                           0x02,               // Bit Offset
                           0x0000000000000000, // Address
                           ,)
                   }, 

                   One, 
                   One, 
                   0x03E8
               }, 

               Package (0x04)
               {
                   ResourceTemplate ()
                   {
                       Register (FFixedHW, 
                           0x08,               // Bit Width
                           0x00,               // Bit Offset
                           0x0000000000001014, // Address
                           ,)
                   }, 

                   0x02, 
                   One, 
                   0x01F4
               }, 

               Package (0x04)
               {
                   ResourceTemplate ()
                   {
                       Register (FFixedHW, 
                           0x08,               // Bit Width
                           0x00,               // Bit Offset
                           0x0000000000001015, // Address
                           ,)
                   }, 

                   0x03, 
                   0x11, 
                   0xFA
               }
           })
       }
   }

 

D

Link to comment
Share on other sites
manmal
manmal
Posted
Posted

Hi FormerlyKnownAs,

thanks for your suggestion.

I tried compiling my dsdt.dsl including all ssdt tables at the end. I did all the work and since it gave me a lot of errors, i tried to "organize" it a bit better , reducing some stuff too ... but compiling it , it results giving me 14 errors . IT's the minimum errors i achieved.

May you (or anyone who wants to help me) try to give a look correcting such errors (assuming it works when it will compile fine)?

In attachment you will find .dsl and ACPITables (MAL1)

Thanks!

Mal

ACPITABLES_MAL1.zip

dsdt_MAL1.dsl.zip

Link to comment
Share on other sites
Beerkex'd
Beerkex'd
Posted
Posted
I tried to extract SSDT tables in osx, but it says could not find or something. Then I went a head to ubuntu and used acpidump. but I could get only one ssdt file which is containing the CPU0IST and CPU0CST addresses. please see attached.

With "C1E" and "Intel C-State Tech" enabled in the BIOS i get 5 SSDT tables when extracting with Lavalys Everest Corporate Edition in Windows.

The trial version works fine for this purpose. Right-click the bottom of the main window to access the ACPI dumping tool.

 

http://www.lavalys.com/support/downloads

Link to comment
Share on other sites
valv
valv
Posted
Posted

In my case I did not need to join my SSDTs into DSDTable. Using Andy's Chameleon Branch helped me loading those tables from Efi/Extra/

 

As we may have same specs, I suggest u, Manmal, do the same thing as I've done; (till a step-by-step guide is in place) :D

Manmal, why didn't u patched your LPCB device

Link to comment
Share on other sites
manmal
manmal
Posted
Posted

Hi valv,

thanks for replying .

 

Since i like to learn to do things manually (i use terminal much more than you think, even for moving or copying Stuff) I think it's much more important understanding how it has to be done correcting my errors I do by myself ...

 

About lpcb and other fixes, i planned to do it after i had a proper 'combo' dsdt with embedded ssdt tables . I guess the instructions in first post here is enough...

 

Mal

Link to comment
Share on other sites
valv
valv
Posted
Posted

I don't understand why u need loading your SSDTs from DSDT, if u can get them loaded directly from memory (precisely in your case)? Is it also to feel doing things "the real way" ?

As a network admin, I know what the pleasure to work in terminal means to most of us, but I doubt this to be related to ACPI tables loading process. Sure you can dump your tables from linux and use iasl (the way most of us had chosen), this is not the question.

 

btw: learning from your mistakes is fine as long as you don't spend your time re-inventing the wheel.

we can also work together you know. I can learn from ur mistakes. after all, this is a forum for the rest of us. doing what u like, is up to u. learning things together is up to us. ;)

Link to comment
Share on other sites
manmal
manmal
Posted
Posted

hi valv,

thanks again for your reply!

 

Yes, you are right ... the wheel is already there nowadays :)

 

... so will you suggest me to use the chameleon ssdt-variant by Andy (ab__73) and put all ssdt tables in one folder like you did ? How did you out SMBIOS without using smbios.plist, since ab__73 bootloader does not support it?

 

I did not understand this : "...if u can get them loaded directly from memory (precisely in your case)? " . Do you mean that it will load p-states, c-states and t-states without any problem without any modification to my ssdt tables ?

 

BTW , since we have similar systems, would you be so nice to put here as an attachment your dsdt / ssdt tables you are using now with all your fixes? I will learn from it, i won't use it in my system of course... i know i may risk to damage everything!

 

Thanks, i'd appreciate it a lot !!

Mal

Link to comment
Share on other sites
valv
valv
Posted
Posted
... so will you suggest me to use the chameleon ssdt-variant by Andy (ab__73) and put all ssdt tables in one folder like you did ? How did you out SMBIOS without using smbios.plist, since ab__73 bootloader does not support it?

Dear Mal,

no, I compiled from Chameleon sources of the Andy's Branch (tell me if u need a package of it) and sure it supports smbios injection.

I did not understand this : "...if u can get them loaded directly from memory (precisely in your case)? " . Do you mean that it will load p-states, c-states and t-states without any problem without any modification to my ssdt tables ?

not really, u will need to load your tables from other memory addresses than the hardcoded ones. for this u will need to edit SSDTables.

 

if u don't understand how take a look over here, to see how I edited mine.

 

BTW , since we have similar systems, would you be so nice to put here as an attachment your dsdt / ssdt tables you are using now with all your fixes? I will learn from it, i won't use it in my system of course... i know i may risk to damage everything!

 

Thanks, i'd appreciate it a lot !!

Mal

just keep an eye over here, I am putting a guide in place that will hold all my modifications (be patient though ;) a work in progress).

ACPI.zip

 

EDIT: link to guide added

Link to comment
Share on other sites
manmal
manmal
Posted
Posted

Thanks a lot valv for your files and for your guide !

It will be useful to many ppl , me too!!

 

Yes, i am VERY interested to such bootloader package ! Did you recompile latest chameleon RC5beta with Andy's branch for SSDT-*.AML load? The main reason why i did not use it yet (ab__73 bootloader) is because it does not support smbios injection. How did you workaround to such <64k-block boot limit recompiling your own?

 

Thanks again!

 

Mal

Link to comment
Share on other sites
valv
valv
Posted
Posted
Thanks a lot valv for your files and for your guide !

It will be useful to many ppl , me too!!

 

Yes, i am VERY interested to such bootloader package ! Did you recompile latest chameleon RC5beta with Andy's branch for SSDT-*.AML load? The main reason why i did not use it yet (ab__73 bootloader) is because it does not support smbios injection. How did you workaround to such <64k-block boot limit recompiling your own?

 

Thanks again!

 

Mal

u'r mistakin' here, it's not ab__73's bootloader. and it is latest chameleon 2.0-RC5pre7 recompile (really good job from Andy on this :D )

Link to comment
Share on other sites
dlach
dlach
Posted
Posted
u'r mistakin' here, it's not ab__73's bootloader. and it is latest chameleon 2.0-RC5pre7 recompile (really good job from Andy on this :) )

 

valv,

 

I'm very interested in your work. I'm keeping an eye on your guide. You offered a package of your recompiled RC5 pre of Andy's changes. Yes please!

 

Couple of questions (I can ask over on your guide thread if you prefer). Why do you need VoodooBattery? The latest Chameleon stuff supposedly provides it if you set SystemType (or system-type for AsereBLN's patch) to 2.

 

What is CPUinjector kext for? If you have to dump your tables you should already have this no?

Link to comment
Share on other sites
valv
valv
Posted
Posted
Why do you need VoodooBattery? The latest Chameleon stuff supposedly provides it if you set SystemType (or system-type for AsereBLN's patch) to 2.

done this already, Battery meter doesn't show without the kext though

What is CPUinjector kext for? If you have to dump your tables you should already have this no?

this is cosmetically speaking to correct the "unknown cpu" string. I know we can do it without a kext, but I need to keep my system totally vanilla.

 

DigitalDJ: "There are several “hacks” out there on the web that tell you to edit the About This Mac strings or the System Profiler strings, however, these are purely cosmetic, the actual operating system still thinks your CPU is Unknown. Proof of this is the Microsoft Silverlight installer. Without hacking the installer, the installer will not detect your CPU and will fail to install. This cures such problems by injecting a “cpu-type” into IORegistry."

 

sorry for this off-topic Formerly, :) I move on.

Link to comment
Share on other sites
Kasakka
Kasakka
Posted
Posted

How do I check if speedstep is actually working?

 

I patched my DSDT according to the instructions in the first post in this thread and the system does boot just fine without NullCPUPowerManagement. However I can't really tell if my system is running at the full 3.4 GHz or speedstepping down to 2.4 GHz since all my fans are on a manual fan controller and my system is watercooled so there are no fans ramping up and temps don't change much.

 

Using Abit IP35 board, Q9550 overclocked to 3.4 GHz. It had 6 power states, all added to DSDT.

Link to comment
Share on other sites
valv
valv
Posted
Posted
How do I check if speedstep is actually working?

 

I patched my DSDT according to the instructions in the first post in this thread and the system does boot just fine without NullCPUPowerManagement. However I can't really tell if my system is running at the full 3.4 GHz or speedstepping down to 2.4 GHz since all my fans are on a manual fan controller and my system is watercooled so there are no fans ramping up and temps don't change much.

 

Using Abit IP35 board, Q9550 overclocked to 3.4 GHz. It had 6 power states, all added to DSDT.

 

OnTerminal type this ioreg -lw0 | grep CSTInfo

if u get something like this

"CSTInfo" = 11463184

the u have CST successfully loaded

 

later type this

ioreg -lw0 | grep PerformanceStateArray

if u get something like this

"PerformanceStateArray" = (<8a0500004..

then u have p-states working :)

if not, good luck

greetz

Link to comment
Share on other sites
Kasakka
Kasakka
Posted
Posted

Thanks!

 

Got the following:

ioreg -lw0 | grep CSTInfo
| |   |	 "CSTInfo" = 19136773
ioreg -lw0 | grep PerformanceStateArray
| |   |	 "PerformanceStateArray" = (<000000000000000010000000100000002248000000000000>,<000000000000000010000000100000002008000001000000>,
<000000000000000010000000100000001e47000002000000>,<000000000000000010000000100000001b07000003000000>,
<000000000000000010000000100000001946000004000000>,<000000000000000010000000100000001606000005000000>)

Link to comment
Share on other sites
manmal
manmal
Posted
Posted

hi valv, thanks ! I thought there were only ab__73 work about it.

Can you please provide us such package or a link to that in a discussion or thread? I think many of us will be interested in that!

Thanks again for your work!

Mal

Link to comment
Share on other sites
valv
valv
Posted
Posted
Thanks!

 

Got the following:

ioreg -lw0 | grep CSTInfo
| |   |	 "CSTInfo" = 19136773
ioreg -lw0 | grep PerformanceStateArray
| |   |	 "PerformanceStateArray" = (<000000000000000010000000100000002248000000000000>,<000000000000000010000000100000002008000001000000>,
<000000000000000010000000100000001e47000002000000>,<000000000000000010000000100000001b07000003000000>,
<000000000000000010000000100000001946000004000000>,<000000000000000010000000100000001606000005000000>)

 

Also try seeing what voodoomonitor (on first post) shows

 

hi valv, thanks ! I thought there were only ab__73 work about it.

Can you please provide us such package or a link to that in a discussion or thread? I think many of us will be interested in that!

Thanks again for your work!

Mal

 

sure I'll be posting this, but not on this topic, as Formerly is such a good guy (we should not abuse from his friendliness).

Please don't go off-topic.

I promise u everything will be posted where it should. just give me a little time to organize things and free myself from real life (job, family and so).

Link to comment
Share on other sites
Kasakka
Kasakka
Posted
Posted
Also try seeing what voodoomonitor (on first post) shows

 

It seems to flick between 2400 MHz (x 6.0 multiplier) and the full 3400 MHz (x 8.5 multiplier) constantly, sometimes staying at either for a few moments with nothing but a few Path Finder windows and Safari open. Is this normal?

 

Never seems to use any of the other P-states, but on the other hand even in Windows using CPU-Z I've never seen it do anything but either stay at 2400 or jump to the full 3400. The P-states seem to be listed correctly (multipliers and voltages in nice even increments). Manual throttle control seems to do nothing.

 

Starting a 720p video in Movist or VLC doesn't seem to do much, but then again this system is powerful enough that something like that won't really make it even break a sweat. Don't have any truly punishing apps installed right now. :(

Link to comment
Share on other sites
valv
valv
Posted
Posted
It seems to flick between 2400 MHz (x 6.0 multiplier) and the full 3400 MHz (x 8.5 multiplier) constantly, sometimes staying at either for a few moments with nothing but a few Path Finder windows and Safari open. Is this normal?

 

Never seems to use any of the other P-states, but on the other hand even in Windows using CPU-Z I've never seen it do anything but either stay at 2400 or jump to the full 3400. The P-states seem to be listed correctly (multipliers and voltages in nice even increments). Manual throttle control seems to do nothing.

 

Starting a 720p video in Movist or VLC doesn't seem to do much, but then again this system is powerful enough that something like that won't really make it even break a sweat. Don't have any truly punishing apps installed right now. :)

 

Congratulations, u have fully working vanilla speed-step.

Link to comment
Share on other sites
uho
uho
Posted
Posted

I followed the steps outlined in the thread and it looks like my pstates are being loaded but my clock speed is still the same even when I stress it for some reason. I'm using coolbook to report the clock speeds.

 

-pc:speedstep$ ioreg -lw0 | grep CSTInfo
-pc:speedstep$ ioreg -lw0 | grep PerformanceStateArray
| |   |	 "PerformanceStateArray" = (<00000000000000000a0000000a0000002b0b...)

 

I don't think there is a conflicting kext but I have included a list just in case. Also, I have attached the DSDT that I am using.

 

M1530: Intel Core 2 Duo, T7500

 

Thanks for your time

 

Update: problem was with smbios.plist. I'm not sure why the attachments aren't showing up. meh, problem solved anyway

Link to comment
Share on other sites
  • 2 weeks later...
TheOriginalPol
TheOriginalPol
Posted
Posted

Okay, I give up.

 

Compile errors galore:

 

Intel ACPI Component Architecture
ASL Optimizing Compiler version 20091214 [Dec 16 2009]
Copyright (C) 2000 - 2009 Intel Corporation
Supports ACPI Specification Revision 4.0

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  1321:				 If (PICM)
Error	4064 -																	Object does not exist ^  (PICM)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  2267:							 TRAP (TRTI, GCDD)
Error	4064 -																			Object does not exist ^  (TRAP)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  2325:							 TRAP (TRTI, GCDD)
Error	4064 -																			Object does not exist ^  (TRAP)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  2389:								 TRAP (TRTI, GCDD)
Error	4064 -																				Object does not exist ^  (TRAP)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  2454:								 TRAP (TRTI, GCDD)
Error	4064 -																				Object does not exist ^  (TRAP)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  2519:								 TRAP (TRTI, GCDD)
Error	4064 -																				Object does not exist ^  (TRAP)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  3170:					 Store (One, SCIS)
Error	4064 -																				Object does not exist ^  (SCIS)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  3438:					 If (PICM)
Error	4064 -																		Object does not exist ^  (PICM)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4540:						 Store (0x19, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4546:						 Store (0x5C, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4552:						 Store (0x10, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4570:						 Store (0x13, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4576:						 Store (0x14, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4582:						 Store (0x15, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4588:						 Store (0x1C, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4608:						 Store (0x1D, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4628:						 Store (0x23, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4646:						 Store (0x32, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4653:						 Store (0x33, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4660:						 Store (0x34, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4667:						 Store (0x35, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4674:						 Store (0x36, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4682:						 Store (0x37, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4689:						 Store (0x38, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4696:						 Store (0x40, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4703:						 Store (0x41, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4710:						 Store (0x48, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4716:						 Store (0x4C, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4725:						 Store (0x50, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4731:						 Store (0x51, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4737:						 Store (0x52, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4743:						 Store (0x53, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4749:						 Notify (\_TZ.TZS0, 0x80)
Error	4064 -																					 Object does not exist ^  (\_TZ.TZS0)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4750:						 Notify (\_TZ.TZS1, 0x80)
Error	4064 -																					 Object does not exist ^  (\_TZ.TZS1)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  4755:						 Store (0x5D, P80H)
Error	4064 -																					 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  5204:						 Method (_WED, 1, NotSerialized)
Warning  1088 -																 Not all control paths return a value ^  (_WED)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  5204:						 Method (_WED, 1, NotSerialized)
Warning  1081 -																  Reserved method must return a value ^  (_WED)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  5206:							 Store (Arg0, P80H)
Error	4064 -																						 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  5215:							 Store (0xAA, P80H)
Error	4064 -																						 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  5221:							 Store (0xA1, P80H)
Error	4064 -																						 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  5232:							 Store (0xAB, P80H)
Error	4064 -																						 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  5240:							 Store (0xAC, P80H)
Error	4064 -																						 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  5441:						 Method (WB15, 6, NotSerialized)
Warning  1088 -																 Not all control paths return a value ^  (WB15)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  5659:							 If (HPAE)
Error	4064 -																				Object does not exist ^  (HPAE)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  5666:							 If (HPAE)
Error	4064 -																				Object does not exist ^  (HPAE)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  5677:						 If (HPAE)
Error	4064 -																			Object does not exist ^  (HPAE)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  5680:							 If (LEqual (HPAS, One))
Error	4064 -																						Object does not exist ^  (HPAS)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  5685:							 If (LEqual (HPAS, 0x02))
Error	4064 -																						Object does not exist ^  (HPAS)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  5690:							 If (LEqual (HPAS, 0x03))
Error	4064 -																						Object does not exist ^  (HPAS)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  6356:					 If (PICM)
Error	4064 -																		Object does not exist ^  (PICM)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  6398:					 If (PICM)
Error	4064 -																		Object does not exist ^  (PICM)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  6440:					 If (PICM)
Error	4064 -																		Object does not exist ^  (PICM)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  6482:					 If (PICM)
Error	4064 -																		Object does not exist ^  (PICM)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  6525:					 If (PICM)
Error	4064 -																		Object does not exist ^  (PICM)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  6593:	 OperationRegion (PRT0, SystemIO, 0x80, 0x04)
Error	4096 -									syntax error, unexpected PARSEOP_OPERATIONREGION ^ 

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  6606:		 If (LEqual (Arg0, One))
Error	4096 -										syntax error, unexpected PARSEOP_IF ^ 

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  6612:		 If (LEqual (Arg0, 0x02))
Remark   5113 -											   Local or Arg used outside a control method ^ 

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  6624:		 Store (P80D, P80H)
Error	4064 -																	 Object does not exist ^  (P80H)

/Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl  6627:	 OperationRegion		   {
Error	4096 -					syntax error, unexpected PARSEOP_OPERATIONREGION, expecting $end ^ 

ASL Input:  /Users/Pol/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl - 7641 lines, 265717 bytes, 2428 keywords
Compilation complete. 55 Errors, 3 Warnings, 1 Remarks, 35 Optimizations

 

I'm not amazing with DSDT editing, but I've been working at this for quite a few hours. I'm sure it's just a stupid mistake or two on my part. Attached is my DSDT.dsl. Any love, anyone?

 

 

P.S. if I remove the comma at the end of the third P-state value set (0x02), it drops the error count down to 52. Lol.

 

 

EDIT: sorry for the super long code, I thought it would wrap it in a scroll box :-(

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...