Quick Guide to Generate a SSDT for CPU Power Management

telepati · Feb 23, 2017

Here is the new v2.4 AppleIntelInfo.kext. I compile it.

Roberbond · Feb 23, 2017

locmer said:
@Roberbond Do you have the latest version from https://github.com/Piker-Alpha/ssdtPRGen.sh ?

You should be getting different warning messages with a i7 6700K (I have one too)

If I download that file I get this:

Code:

iMac-de-Roberto:~ roberto$ sudo ~/ssdtPRGen.sh


ssdtPRGen.sh v0.9  Copyright (c) 2011-2012 by † RevoGirl
             v6.6  Copyright (c) 2013 by † Jeroen
             v21.5 Copyright (c) 2013-2017 by Pike R. Alpha
-----------------------------------------------------------
Bugs > https://github.com/Piker-Alpha/ssdtPRGen.sh/issues <

System information: Mac OS X 10.12.3 (16D32)
Brandstring: "Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz"

Version: models.cfg v160 / Skylake.cfg v193


Scope (_PR_) {222 bytes} with ACPI Processor declarations found in DSDT (ACPI 1.0 compliant)
Generating ssdt.dsl for a 'iMac14,2' with board-id [Mac-27ADBB7B4CEE8E61]
Skylake Core i7-6700K processor [0x506E3] setup [0x0705]
With a maximum TDP of 91 Watt, as specified by Intel
Number logical CPU's: 8 (Core Frequency: 4000 MHz)
Number of Turbo States: 2 (4100-4200 MHz)
Number of P-States: 35 (800-4200 MHz)
Injected C-States for CPU0 (C1,C3,C6,C7,C8,C9,C10)
Injected C-States for CPU1 (C1,C2,C3,C6,C7)
Warning: 'cpu-type' may be set improperly (0x0705 instead of 0x0905)
     - Clover users should read https://clover-wiki.zetam.org/Configuration/CPU#cpu_type
Error: board-id [Mac-27ADBB7B4CEE8E61] not supported by Skylake – check SMBIOS data / use the -target option

Do you want to continue (y/n)? y
Warning: 'system-type' may be set improperly (1 instead of 2)
     - Clover users should read https://clover-wiki.zetam.org/Configuration/ACPI#acpi_smartups
Compiling: ssdt_pr.dsl
Intel ACPI Component Architecture
ASL Optimizing Compiler version 20140926-64 [Nov  6 2014]
Copyright (c) 2000 - 2014 Intel Corporation

ASL Input:     /Users/roberto/Library/ssdtPRGen/ssdt.dsl - 364 lines, 11348 bytes, 73 keywords
AML Output:    /Users/roberto/Library/ssdtPRGen/ssdt.aml - 2389 bytes, 28 named objects, 45 executable opcodes

Compilation complete. 0 Errors, 0 Warnings, 0 Remarks, 0 Optimizations

I got an error, but If I continue I could compile it. it is alright? do I need the ssdt.dsl file?

This is what I get:

Code:

CPU Ratio Info:
------------------------------------------
Base Clock Frequency (BLCK)............. : 100 MHz
Maximum Efficiency Ratio/Frequency.......:  8 ( 800 MHz)
Maximum non-Turbo Ratio/Frequency........: 40 (4000 MHz)
Maximum Turbo Ratio/Frequency............: 42 (4200 MHz)

IGPU Info:
------------------------------------------
IGPU Current Frequency...................:    0 MHz
IGPU Minimum Frequency...................:  350 MHz
IGPU Maximum Non-Turbo Frequency.........:  350 MHz
IGPU Maximum Turbo Frequency.............: 1150 MHz
IGPU Maximum limit.......................: 3000 MHz

P-State ratio * 100 = Frequency in MHz
------------------------------------------
CPU P-States [ (9) 37 40 ] iGPU P-States [ ]
CPU C6-Cores [ 0 1 3 4 5 7 ]
CPU P-States [ (9) 26 37 40 ] iGPU P-States [ ]
CPU P-States [ (9) 26 30 37 40 ] iGPU P-States [ ]
CPU C6-Cores [ 0 1 3 4 5 6 7 ]
CPU P-States [ 9 26 30 33 37 (40) ] iGPU P-States [ ]
CPU C6-Cores [ 0 1 2 3 4 5 6 7 ]
CPU P-States [ (9) 26 28 30 33 37 40 ] iGPU P-States [ ]
CPU P-States [ (9) 23 26 28 30 33 37 40 ] iGPU P-States [ ]
CPU P-States [ (9) 22 23 26 28 30 33 37 40 ] iGPU P-States [ ]
CPU P-States [ (9) 20 22 23 26 28 30 33 37 40 ] iGPU P-States [ ]
CPU P-States [ (9) 20 22 23 26 27 28 30 33 37 40 ] iGPU P-States [ ]
CPU P-States [ (9) 19 20 22 23 26 27 28 30 33 37 40 ] iGPU P-States [ ]
CPU P-States [ (9) 19 20 22 23 26 27 28 30 33 34 37 40 ] iGPU P-States [ ]
CPU P-States [ 9 19 20 22 23 26 27 28 30 33 34 37 40 (42) ] iGPU P-States [ ]
CPU P-States [ (9) 19 20 22 23 24 26 27 28 30 33 34 37 40 42 ] iGPU P-States [ ]

are they ok?

locmer · Feb 24, 2017

Roberbond said:

If I download that file I get this:

Code:

iMac-de-Roberto:~ roberto$ sudo ~/ssdtPRGen.sh


ssdtPRGen.sh v0.9  Copyright (c) 2011-2012 by † RevoGirl
             v6.6  Copyright (c) 2013 by † Jeroen
             v21.5 Copyright (c) 2013-2017 by Pike R. Alpha
-----------------------------------------------------------
Bugs > https://github.com/Piker-Alpha/ssdtPRGen.sh/issues <

System information: Mac OS X 10.12.3 (16D32)
Brandstring: "Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz"

Version: models.cfg v160 / Skylake.cfg v193


Scope (_PR_) {222 bytes} with ACPI Processor declarations found in DSDT (ACPI 1.0 compliant)
Generating ssdt.dsl for a 'iMac14,2' with board-id [Mac-27ADBB7B4CEE8E61]
Skylake Core i7-6700K processor [0x506E3] setup [0x0705]
With a maximum TDP of 91 Watt, as specified by Intel
Number logical CPU's: 8 (Core Frequency: 4000 MHz)
Number of Turbo States: 2 (4100-4200 MHz)
Number of P-States: 35 (800-4200 MHz)
Injected C-States for CPU0 (C1,C3,C6,C7,C8,C9,C10)
Injected C-States for CPU1 (C1,C2,C3,C6,C7)
Warning: 'cpu-type' may be set improperly (0x0705 instead of 0x0905)
     - Clover users should read https://clover-wiki.zetam.org/Configuration/CPU#cpu_type
Error: board-id [Mac-27ADBB7B4CEE8E61] not supported by Skylake – check SMBIOS data / use the -target option

Do you want to continue (y/n)? y
Warning: 'system-type' may be set improperly (1 instead of 2)
     - Clover users should read https://clover-wiki.zetam.org/Configuration/ACPI#acpi_smartups
Compiling: ssdt_pr.dsl
Intel ACPI Component Architecture
ASL Optimizing Compiler version 20140926-64 [Nov  6 2014]
Copyright (c) 2000 - 2014 Intel Corporation

ASL Input:     /Users/roberto/Library/ssdtPRGen/ssdt.dsl - 364 lines, 11348 bytes, 73 keywords
AML Output:    /Users/roberto/Library/ssdtPRGen/ssdt.aml - 2389 bytes, 28 named objects, 45 executable opcodes

Compilation complete. 0 Errors, 0 Warnings, 0 Remarks, 0 Optimizations

I got an error, but If I continue I could compile it. it is alright? do I need the ssdt.dsl file?

This is what I get:

Code:

CPU Ratio Info:
------------------------------------------
Base Clock Frequency (BLCK)............. : 100 MHz
Maximum Efficiency Ratio/Frequency.......:  8 ( 800 MHz)
Maximum non-Turbo Ratio/Frequency........: 40 (4000 MHz)
Maximum Turbo Ratio/Frequency............: 42 (4200 MHz)

IGPU Info:
------------------------------------------
IGPU Current Frequency...................:    0 MHz
IGPU Minimum Frequency...................:  350 MHz
IGPU Maximum Non-Turbo Frequency.........:  350 MHz
IGPU Maximum Turbo Frequency.............: 1150 MHz
IGPU Maximum limit.......................: 3000 MHz

P-State ratio * 100 = Frequency in MHz
------------------------------------------
CPU P-States [ (9) 37 40 ] iGPU P-States [ ]
CPU C6-Cores [ 0 1 3 4 5 7 ]
CPU P-States [ (9) 26 37 40 ] iGPU P-States [ ]
CPU P-States [ (9) 26 30 37 40 ] iGPU P-States [ ]
CPU C6-Cores [ 0 1 3 4 5 6 7 ]
CPU P-States [ 9 26 30 33 37 (40) ] iGPU P-States [ ]
CPU C6-Cores [ 0 1 2 3 4 5 6 7 ]
CPU P-States [ (9) 26 28 30 33 37 40 ] iGPU P-States [ ]
CPU P-States [ (9) 23 26 28 30 33 37 40 ] iGPU P-States [ ]
CPU P-States [ (9) 22 23 26 28 30 33 37 40 ] iGPU P-States [ ]
CPU P-States [ (9) 20 22 23 26 28 30 33 37 40 ] iGPU P-States [ ]
CPU P-States [ (9) 20 22 23 26 27 28 30 33 37 40 ] iGPU P-States [ ]
CPU P-States [ (9) 19 20 22 23 26 27 28 30 33 37 40 ] iGPU P-States [ ]
CPU P-States [ (9) 19 20 22 23 26 27 28 30 33 34 37 40 ] iGPU P-States [ ]
CPU P-States [ 9 19 20 22 23 26 27 28 30 33 34 37 40 (42) ] iGPU P-States [ ]
CPU P-States [ (9) 19 20 22 23 24 26 27 28 30 33 34 37 40 42 ] iGPU P-States [ ]

are they ok?

The are like the ones I get with the same processor and they seem to work. Having said that I do not see a lot of difference between not putting it in place. My CPU goes nicely to 4200 regardless. But with or without these setting I never see lower then 1.5 Ghz and the cpu could be throttling down to 800 Mhz. So I have my doubts if all is perfect, but it works ok nonetheless. One of the warnings is this: https://github.com/Piker-Alpha/ssdtPRGen.sh/issues/289

HackToshNoob · Feb 25, 2017

tonymacx86 said:
The amount of power states will then show in the Terminal window.

References:
http://www.tonymacx86.com/mavericks...vericks-native-cpu-igpu-power-management.html
http://www.tonymacx86.com/el-capita...01-guide-native-power-management-laptops.html
https://github.com/Piker-Alpha/ssdtPRGen.sh
https://github.com/Piker-Alpha/AppleIntelInfo

I just completed this on my Hackintosh, Gigabyte Z170X Designaire, Core i7 6700K, Gigabyte GTX 980Ti, 32mb Ram, RM850. Can someone look at the upload and tell me if this looks correct for my custom power management? Thank you.

hackmefrancis · Feb 25, 2017

I have a very few P-States regardless if I put the ssdt on my EFI. Maybe it's because of the CPU & SMBIOS configuration? I have following specs:
Asus Z170i Pro Gaming
Intel i5-6500
Gigabyte RX 460 4GB (no 6-pin power)
8GB 2400 DDR4 RAM
128 Kingston SSD
SMBIOS 14,2

Question:
With this config, board + proc + gpu, would it be better to change my SMBIOS to 17,1 instead of 14,2?

Note:
With 14,2, iMessages & FaceTime works perfect. I would say everything is working fine other than the random times that apps aren't opening. Apps like Photos, Chrome, Atom Editor, and sometimes Youtube videos will not play. Can't find out why.

I have set darkwake=0. Setting it to any other number would let the system "deep sleep" but monitor won't wake, only cpu. With darkwake=0, I have normal sleep working fine.

CaptainKernelPanic · Feb 26, 2017

hackmefrancis said:
I have a very few P-States regardless if I put the ssdt on my EFI. Maybe it's because of the CPU & SMBIOS configuration? I have following specs:
Asus Z170i Pro Gaming
Intel i5-6500
Gigabyte RX 460 4GB (no 6-pin power)
8GB 2400 DDR4 RAM
128 Kingston SSD
SMBIOS 14,2

Question:
With this config, board + proc + gpu, would it be better to change my SMBIOS to 17,1 instead of 14,2?

Note:
With 14,2, iMessages & FaceTime works perfect. I would say everything is working fine other than the random times that apps aren't opening. Apps like Photos, Chrome, Atom Editor, and sometimes Youtube videos will not play. Can't find out why.

I have set darkwake=0. Setting it to any other number would let the system "deep sleep" but monitor won't wake, only cpu. With darkwake=0, I have normal sleep working fine.

14,2 is much more stable than 17,2.

HackToshNoob · Feb 27, 2017

hackmefrancis said:
I have a very few P-States regardless if I put the ssdt on my EFI. Maybe it's because of the CPU & SMBIOS configuration? I have following specs:
Asus Z170i Pro Gaming
Intel i5-6500
Gigabyte RX 460 4GB (no 6-pin power)
8GB 2400 DDR4 RAM
128 Kingston SSD
SMBIOS 14,2

Question:
With this config, board + proc + gpu, would it be better to change my SMBIOS to 17,1 instead of 14,2?

Note:
With 14,2, iMessages & FaceTime works perfect. I would say everything is working fine other than the random times that apps aren't opening. Apps like Photos, Chrome, Atom Editor, and sometimes Youtube videos will not play. Can't find out why.

I have set darkwake=0. Setting it to any other number would let the system "deep sleep" but monitor won't wake, only cpu. With darkwake=0, I have normal sleep working fine.

What is this "Darkwake_0?" I have some sleep issues but realized if I put my computer into sleep and push the power button I wake fine. If I try to wake the computer using keyboard or mouse, the monitor won't wake. Help a noob out. Thanks.

rain.nguyen · Feb 27, 2017

Any one got this when load kext? plz help me fix this

dude05 · Feb 28, 2017

First time trying to generate ssdt.

I get this error. what am i doing wrong?
I see that my cpu is detected proper.
I am on Z10PE-D8. Dual 2687W v3 Sierra 10.12.3

Thanks for your help.

Code:

EDIT02:~ edit02$ ./ssdtPRGen.sh


ssdtPRGen.sh v0.9 Copyright (c) 2011-2012 by † RevoGirl
             v6.6 Copyright (c) 2013 by † Jeroen
             v15.6 Copyright (c) 2013-2017 by Pike R. Alpha
-----------------------------------------------------------
Bugs > https://github.com/Piker-Alpha/ssdtPRGen.sh/issues <

gDataPath: /Users/edit02/Library/ssdtPRGen/Data
System information: Mac OS X 10.12.3 (16D32)
Brandstring 'Intel(R) Xeon(R) CPU E5-2687W v3 @ 3.10GHz'

Scope (\_SB_) {70958 bytes} with ACPI Processor declarations found in the DSDT (ACPI 1.0 compliant)
Generating ssdt.dsl for a 'MacPro6,1' with board-id [Mac-F60DEB81FF30ACF6]
Haswell Core E5-2687W v3 processor [0x306F2] setup [0x0507]
With a maximum TDP of 160 Watt, as specified by Intel
Number logical CPU's: 40 (Core Frequency: 3100 MHz)
Number of Turbo States: 4 (3200-3500 MHz)
Number of P-States: 24 (1200-3500 MHz)
Injected C-States for CP00 (C1,C3,C6)
Injected C-States for CP01 (C1,C3,C6)
Warning: 'system-type' may be set improperly (1 instead of 3)

Intel ACPI Component Architecture
ASL Optimizing Compiler version 20140926-64 [Nov  6 2014]
Copyright (c) 2000 - 2014 Intel Corporation

ACPI Warning: NsLookup: Type mismatch on APSS (Package), searching for (Method) (20140926/nsaccess-729)
/Users/edit02/Library/ssdtPRGen/ssdt.dsl     40:     External (\_SB_.CP00, DeviceObj)
Error    6074 -                                       Name already exists in scope ^  (\_SB_.CP00)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl     41:     External (\_SB_.CP01, DeviceObj)
Error    6074 -                                       Name already exists in scope ^  (\_SB_.CP01)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl     42:     External (\_SB_.CP02, DeviceObj)
Error    6074 -                                       Name already exists in scope ^  (\_SB_.CP02)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl     43:     External (\_SB_.CP03, DeviceObj)
Error    6074 -                                       Name already exists in scope ^  (\_SB_.CP03)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl     44:     External (\_SB_.CP04, DeviceObj)
Error    6074 -                                       Name already exists in scope ^  (\_SB_.CP04)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl     45:     External (\_SB_.CP05, DeviceObj)
Error    6074 -                                       Name already exists in scope ^  (\_SB_.CP05)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl     46:     External (\_SB_.CP06, DeviceObj)
Error    6074 -                                       Name already exists in scope ^  (\_SB_.CP06)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl     47:     External (\_SB_.CP07, DeviceObj)
Error    6074 -                                       Name already exists in scope ^  (\_SB_.CP07)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl     48:     External (\_SB_.CP08, DeviceObj)
Error    6074 -                                       Name already exists in scope ^  (\_SB_.CP08)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl     49:     External (\_SB_.CP09, DeviceObj)
Error    6074 -                                       Name already exists in scope ^  (\_SB_.CP09)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl     50:     External (\_SB_.CP0A, DeviceObj)
Error    6074 -                                       Name already exists in scope ^  (\_SB_.CP0A)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl     51:     External (\_SB_.CP0B, DeviceObj)
Error    6074 -                                       Name already exists in scope ^  (\_SB_.CP0B)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl     52:     External (\_SB_.CP0C, DeviceObj)
Error    6074 -                                       Name already exists in scope ^  (\_SB_.CP0C)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl     53:     External (\_SB_.CP0D, DeviceObj)
Error    6074 -                                       Name already exists in scope ^  (\_SB_.CP0D)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl     54:     External (\_SB_.CP0E, DeviceObj)
Error    6074 -                                       Name already exists in scope ^  (\_SB_.CP0E)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl     55:     External (\_SB_.CP0F, DeviceObj)
Error    6074 -                                       Name already exists in scope ^  (\_SB_.CP0F)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl     56:     External (\_SB_.CP10, DeviceObj)
Error    6074 -                                       Name already exists in scope ^  (\_SB_.CP10)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl     57:     External (\_SB_.CP11, DeviceObj)
Error    6074 -                                       Name already exists in scope ^  (\_SB_.CP11)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl     58:     External (\_SB_.CP12, DeviceObj)
Error    6074 -                                       Name already exists in scope ^  (\_SB_.CP12)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl     59:     External (\_SB_.CP13, DeviceObj)
Error    6074 -                                       Name already exists in scope ^  (\_SB_.CP13)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    480:         Method (APSS, 0, NotSerialized)
Error    6074 -                       Name already exists in scope ^  (APSS)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    492:         Method (APSS, 0, NotSerialized)
Error    6074 -                       Name already exists in scope ^  (APSS)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    499:         Method (ACST, 0, NotSerialized) { Return (\_SB_.CP01.ACST ()) }
Error    6074 -                       Name already exists in scope ^  (ACST)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    499:         Method (ACST, 0, NotSerialized) { Return (\_SB_.CP01.ACST ()) }
Remark   2098 -                                                                           Recursive method call ^  (\_SB_.CP01.ACST)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    504:         Method (APSS, 0, NotSerialized)
Error    6074 -                       Name already exists in scope ^  (APSS)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    511:         Method (ACST, 0, NotSerialized) { Return (\_SB_.CP01.ACST ()) }
Error    6074 -                       Name already exists in scope ^  (ACST)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    516:         Method (APSS, 0, NotSerialized)
Error    6074 -                       Name already exists in scope ^  (APSS)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    523:         Method (ACST, 0, NotSerialized) { Return (\_SB_.CP01.ACST ()) }
Error    6074 -                       Name already exists in scope ^  (ACST)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    528:         Method (APSS, 0, NotSerialized)
Error    6074 -                       Name already exists in scope ^  (APSS)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    535:         Method (ACST, 0, NotSerialized) { Return (\_SB_.CP01.ACST ()) }
Error    6074 -                       Name already exists in scope ^  (ACST)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    540:         Method (APSS, 0, NotSerialized)
Error    6074 -                       Name already exists in scope ^  (APSS)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    547:         Method (ACST, 0, NotSerialized) { Return (\_SB_.CP01.ACST ()) }
Error    6074 -                       Name already exists in scope ^  (ACST)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    552:         Method (APSS, 0, NotSerialized)
Error    6074 -                       Name already exists in scope ^  (APSS)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    559:         Method (ACST, 0, NotSerialized) { Return (\_SB_.CP01.ACST ()) }
Error    6074 -                       Name already exists in scope ^  (ACST)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    564:         Method (APSS, 0, NotSerialized)
Error    6074 -                       Name already exists in scope ^  (APSS)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    571:         Method (ACST, 0, NotSerialized) { Return (\_SB_.CP01.ACST ()) }
Error    6074 -                       Name already exists in scope ^  (ACST)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    576:         Method (APSS, 0, NotSerialized)
Error    6074 -                       Name already exists in scope ^  (APSS)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    583:         Method (ACST, 0, NotSerialized) { Return (\_SB_.CP01.ACST ()) }
Error    6074 -                       Name already exists in scope ^  (ACST)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    588:         Method (APSS, 0, NotSerialized)
Error    6074 -                       Name already exists in scope ^  (APSS)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    595:         Method (ACST, 0, NotSerialized) { Return (\_SB_.CP01.ACST ()) }
Error    6074 -                       Name already exists in scope ^  (ACST)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    600:         Method (APSS, 0, NotSerialized)
Error    6074 -                       Name already exists in scope ^  (APSS)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    607:         Method (ACST, 0, NotSerialized) { Return (\_SB_.CP01.ACST ()) }
Error    6074 -                       Name already exists in scope ^  (ACST)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    612:         Method (APSS, 0, NotSerialized)
Error    6074 -                       Name already exists in scope ^  (APSS)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    619:         Method (ACST, 0, NotSerialized) { Return (\_SB_.CP01.ACST ()) }
Error    6074 -                       Name already exists in scope ^  (ACST)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    624:         Method (APSS, 0, NotSerialized)
Error    6074 -                       Name already exists in scope ^  (APSS)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    631:         Method (ACST, 0, NotSerialized) { Return (\_SB_.CP01.ACST ()) }
Error    6074 -                       Name already exists in scope ^  (ACST)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    636:         Method (APSS, 0, NotSerialized)
Error    6074 -                       Name already exists in scope ^  (APSS)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    643:         Method (ACST, 0, NotSerialized) { Return (\_SB_.CP01.ACST ()) }
Error    6074 -                       Name already exists in scope ^  (ACST)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    648:         Method (APSS, 0, NotSerialized)
Error    6074 -                       Name already exists in scope ^  (APSS)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    655:         Method (ACST, 0, NotSerialized) { Return (\_SB_.CP01.ACST ()) }
Error    6074 -                       Name already exists in scope ^  (ACST)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    660:         Method (APSS, 0, NotSerialized)
Error    6074 -                       Name already exists in scope ^  (APSS)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    667:         Method (ACST, 0, NotSerialized) { Return (\_SB_.CP01.ACST ()) }
Error    6074 -                       Name already exists in scope ^  (ACST)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    672:         Method (APSS, 0, NotSerialized)
Error    6074 -                       Name already exists in scope ^  (APSS)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    679:         Method (ACST, 0, NotSerialized) { Return (\_SB_.CP01.ACST ()) }
Error    6074 -                       Name already exists in scope ^  (ACST)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    684:         Method (APSS, 0, NotSerialized)
Error    6074 -                       Name already exists in scope ^  (APSS)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    691:         Method (ACST, 0, NotSerialized) { Return (\_SB_.CP01.ACST ()) }
Error    6074 -                       Name already exists in scope ^  (ACST)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    696:         Method (APSS, 0, NotSerialized)
Error    6074 -                       Name already exists in scope ^  (APSS)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    703:         Method (ACST, 0, NotSerialized) { Return (\_SB_.CP01.ACST ()) }
Error    6074 -                       Name already exists in scope ^  (ACST)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    708:         Method (APSS, 0, NotSerialized)
Error    6074 -                       Name already exists in scope ^  (APSS)

/Users/edit02/Library/ssdtPRGen/ssdt.dsl    715:         Method (ACST, 0, NotSerialized) { Return (\_SB_.CP01.ACST ()) }
Error    6074 -                       Name already exists in scope ^  (ACST)

ASL Input:     /Users/edit02/Library/ssdtPRGen/ssdt.dsl - 719 lines, 18437 bytes, 263 keywords

Compilation complete. 59 Errors, 0 Warnings, 1 Remarks, 0 Optimizations
Do you want to open ssdt.dsl (y/n)? y

******update i downloaded the zip file and run ssdtprgen from inside ~library/ssdtprgen and i get this. is this progress?? no of logical cpu now shows 80

Code:

EDIT02:ssdtPRGen edit02$ ./ssdtPRGen.sh -xcpm 1 -cpus 2
ssdtPRGen.sh v0.9  Copyright (c) 2011-2012 by † RevoGirl
             v6.6  Copyright (c) 2013 by † Jeroen
             v21.5 Copyright (c) 2013-2017 by Pike R. Alpha
-----------------------------------------------------------
Bugs > https://github.com/Piker-Alpha/ssdtPRGen.sh/issues <

System information: Mac OS X 10.12.3 (16D32)
Brandstring: "Intel(R) Xeon(R) CPU E5-2687W v3 @ 3.10GHz"

Override value: (-x) XCPM mode, now set to: 1!
Override value: (-cpus) number of processors, now using: 2!

Version: models.cfg v170 / Haswell.cfg v151



Generating ssdt.dsl for a 'MacPro6,1' with board-id [Mac-F60DEB81FF30ACF6]
Haswell Core E5-2687W v3 processor [0x306F2] setup [0x0507]
With a maximum TDP of 160 Watt, as specified by Intel
Number logical CPU's: 80 (Core Frequency: 3100 MHz)
Number of Turbo States: 4 (3200-3500 MHz)
Number of P-States: 24 (1200-3500 MHz)


Warning: You must use the -xcpm_ipi boot argument instead of -xcpm on multiprocessor systems.



Injected C-States for CP00 (C1,C3,C6)
Injected C-States for CP01 (C1,C3,C6)
Warning..: FrequencyVectors missing in Mac-F60DEB81FF30ACF6.plist
     Download https://github.com/Piker-Alpha/freqVectorsEdit.sh to fix this
Warning: 'system-type' may be set improperly (1 instead of 3)
     - Clover users should read https://clover-wiki.zetam.org/Configuration/ACPI#acpi_smartups
Compiling: ssdt_pr.dsl
Intel ACPI Component Architecture
ASL Optimizing Compiler version 20140926-64 [Nov  6 2014]
Copyright (c) 2000 - 2014 Intel Corporation

ASL Input:     /Users/edit02/Library/ssdtPRGen/ssdt.dsl - 1386 lines, 37790 bytes, 510 keywords
AML Output:    /Users/edit02/Library/ssdtPRGen/ssdt.aml - 11026 bytes, 246 named objects, 264 executable opcodes

Compilation complete. 0 Errors, 0 Warnings, 0 Remarks, 0 Optimizations

Applementalist · Mar 1, 2017

SO today i have generatet a ssdt with the above script.

Here are two pics. The first is bevor the patch .

Before After

What you guys think about it ?

Search

Quick Guide to Generate a SSDT for CPU Power Management

telepati

Attachments

Roberbond

locmer

HackToshNoob

Attachments

hackmefrancis

CaptainKernelPanic

HackToshNoob

rain.nguyen

dude05

Applementalist

Forum

Guides

Downloads