SSDT generation script (Ivybridge PM)

[xojiostou]

I was trying to overclock my CPU Xeon E5 1650v2 and used SSDT generation script. Now HWmonitor shows me weird numbers like 4.6GHz and I have only 2p states 12 and 36 when it used to be 12 and 35. Please take a look and tell what can I do to fix it. I am afraid that is not working properly right now.



Last login: Mon Jan 26 21:13:07 on ttys000
Alexs-Mac-Pro:~ xojiostou$ /Users/xojiostou/ssdtPRGen.command ; exit;



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


gDataPath: /Users/xojiostou/Library/ssdtPRGen/Data
System information: Mac OS X 10.10.1 (14B25)
Brandstring 'Intel(R) Xeon(R) CPU E5-1650 v2 @ 3.50GHz'


Scope (_SB_) {23608 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]
Ivy Bridge Core E5-1650 v2 processor [0x306E4] setup [0x0a01]
With a maximum TDP of 130 Watt, as specified by Intel
Number logical CPU's: 12 (Core Frequency: 3500 MHz)
Number of Turbo States: 4 (3600-3900 MHz)
Number of P-States: 28 (1200-3900 MHz)
Injected C-States for C000 (C1,C3,C6)
Injected C-States for C001 (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


ASL Input: /Users/xojiostou/Library/ssdtPRGen/ssdt.dsl - 366 lines, 10810 bytes, 96 keywords
AML Output: /Users/xojiostou/Library/ssdtPRGen/ssdt.aml - 2585 bytes, 40 named objects, 56 executable opcodes


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


Do you want to copy /Users/xojiostou/Library/ssdtPRGen/ssdt.aml to /Extra/ssdt.aml? (y/n)? y
Creating temporarily mount point: /Volumes/EFI
Password:
Mounting EFI partition...
mount_hfs: Resource busy
umount: /Volumes/EFI: not currently mounted
Do you want to open ssdt.dsl (y/n)? y
logout


[Process completed]





and here is ssdt.dsl:







/*
* Intel ACPI Component Architecture
* AML Disassembler version 20140210-00 [Feb 10 2014]
* Copyright (c) 2000 - 2014 Intel Corporation
*
* Original Table Header:
* Signature "SSDT"
* Length 0x0000036A (874)
* Revision 0x01
* Checksum 0x00
* OEM ID "APPLE "
* OEM Table ID "CpuPm"
* OEM Revision 0x00015600 (87552)
* Compiler ID "INTL"
* Compiler Version 0x20140210 (538182160)
*/


DefinitionBlock ("ssdt.aml", "SSDT", 1, "APPLE ", "CpuPm", 0x00015600)
{
External (\_SB_.C000, DeviceObj)
External (\_SB_.C001, DeviceObj)
External (\_SB_.C002, DeviceObj)
External (\_SB_.C003, DeviceObj)
External (\_SB_.C004, DeviceObj)
External (\_SB_.C005, DeviceObj)
External (\_SB_.C006, DeviceObj)
External (\_SB_.C007, DeviceObj)
External (\_SB_.C008, DeviceObj)
External (\_SB_.C009, DeviceObj)
External (\_SB_.C00A, DeviceObj)
External (\_SB_.C00B, DeviceObj)


Scope (\_SB_.C000)
{
Method (_INI, 0, NotSerialized)
{
Store ("ssdtPRGen version....: 15.6 / Mac OS X 10.10.1 (14B25)", Debug)
Store ("target processor.....: E5-1650 v2", Debug)
Store ("running processor....: Intel(R) Xeon(R) CPU E5-1650 v2 @ 3.50GHz", Debug)
Store ("baseFrequency........: 1200", Debug)
Store ("frequency............: 3500", Debug)
Store ("busFrequency.........: 100", Debug)
Store ("logicalCPUs..........: 12", Debug)
Store ("maximum TDP..........: 130", Debug)
Store ("packageLength........: 28", Debug)
Store ("turboStates..........: 4", Debug)
Store ("maxTurboFrequency....: 3900", Debug)
Store ("IvyWorkArounds.......: 3", Debug)
Store ("machdep.xcpm.mode....: 0", Debug)
}


Name (APLF, 0x04)
Name (APSN, 0x05)
Name (APSS, Package (0x21)
{
/* Workaround for the Ivy Bridge PM 'bug' */
Package (0x06) { 0x0F3D, 0x01FBD0, 0x0A, 0x0A, 0x2800, 0x2800 },
/* High Frequency Modes (turbo) */
Package (0x06) { 0x0F3C, 0x01FBD0, 0x0A, 0x0A, 0x2700, 0x2700 },
Package (0x06) { 0x0ED8, 0x01FBD0, 0x0A, 0x0A, 0x2600, 0x2600 },
Package (0x06) { 0x0E74, 0x01FBD0, 0x0A, 0x0A, 0x2500, 0x2500 },
Package (0x06) { 0x0E10, 0x01FBD0, 0x0A, 0x0A, 0x2400, 0x2400 },
/* High Frequency Modes (non-turbo) */
Package (0x06) { 0x0DAC, 0x01FBD0, 0x0A, 0x0A, 0x2300, 0x2300 },
Package (0x06) { 0x0D48, 0x01E7B6, 0x0A, 0x0A, 0x2200, 0x2200 },
Package (0x06) { 0x0CE4, 0x01D3F9, 0x0A, 0x0A, 0x2100, 0x2100 },
Package (0x06) { 0x0C80, 0x01C097, 0x0A, 0x0A, 0x2000, 0x2000 },
Package (0x06) { 0x0C1C, 0x01AD90, 0x0A, 0x0A, 0x1F00, 0x1F00 },
Package (0x06) { 0x0BB8, 0x019AE2, 0x0A, 0x0A, 0x1E00, 0x1E00 },
Package (0x06) { 0x0B54, 0x01888F, 0x0A, 0x0A, 0x1D00, 0x1D00 },
Package (0x06) { 0x0AF0, 0x017693, 0x0A, 0x0A, 0x1C00, 0x1C00 },
Package (0x06) { 0x0A8C, 0x0164EF, 0x0A, 0x0A, 0x1B00, 0x1B00 },
Package (0x06) { 0x0A28, 0x0153A2, 0x0A, 0x0A, 0x1A00, 0x1A00 },
Package (0x06) { 0x09C4, 0x0142AC, 0x0A, 0x0A, 0x1900, 0x1900 },
Package (0x06) { 0x0960, 0x01320C, 0x0A, 0x0A, 0x1800, 0x1800 },
Package (0x06) { 0x08FC, 0x0121C0, 0x0A, 0x0A, 0x1700, 0x1700 },
Package (0x06) { 0x0898, 0x0111C8, 0x0A, 0x0A, 0x1600, 0x1600 },
Package (0x06) { 0x0834, 0x010224, 0x0A, 0x0A, 0x1500, 0x1500 },
Package (0x06) { 0x07D0, 0x00F2D2, 0x0A, 0x0A, 0x1400, 0x1400 },
Package (0x06) { 0x076C, 0x00E3D3, 0x0A, 0x0A, 0x1300, 0x1300 },
Package (0x06) { 0x0708, 0x00D525, 0x0A, 0x0A, 0x1200, 0x1200 },
Package (0x06) { 0x06A4, 0x00C6C7, 0x0A, 0x0A, 0x1100, 0x1100 },
Package (0x06) { 0x0640, 0x00B8B9, 0x0A, 0x0A, 0x1000, 0x1000 },
Package (0x06) { 0x05DC, 0x00AAFB, 0x0A, 0x0A, 0x0F00, 0x0F00 },
Package (0x06) { 0x0578, 0x009D8B, 0x0A, 0x0A, 0x0E00, 0x0E00 },
Package (0x06) { 0x0514, 0x009068, 0x0A, 0x0A, 0x0D00, 0x0D00 },
/* Low Frequency Mode */
Package (0x06) { 0x04B0, 0x008393, 0x0A, 0x0A, 0x0C00, 0x0C00 },
Package (0x06) { 0x044C, Zero, 0x0A, 0x0A, 0x0B00, 0x0B00 },
Package (0x06) { 0x03E8, Zero, 0x0A, 0x0A, 0x0A00, 0x0A00 },
Package (0x06) { 0x0384, Zero, 0x0A, 0x0A, 0x0900, 0x0900 },
Package (0x06) { 0x0320, Zero, 0x0A, 0x0A, 0x0800, 0x0800 }


Edit: solved! all works now.

 

[N00Bster]

I'm writing from my hackintosh.

I just overclocked it so that the turbo goes up to 4.5ghz. after overclock I lost my generated c and p states and was not able to boot up correctly. After I booted my c and p states were 16 and 34. I tried to regenerate my c and p states but I got this message,

"Warning: 'cpu-type' may be set improperly (0x0703 instead of 0x0603)

Error: board-id [Mac-FC02E91DDD3FA6A4] not supported by Sandy Bridge – check SMBIOS data / use the -c option"

I do not understand what exactly this means.

So I then used chameleon wizard to fix up my smbios and changed it from 3,1 to 13,2 and added all the clock speeds and memory names and all of that including the random serial number. Hoping that would fix the problem but it did not and now I still get that same warning and error message. What am I doing wrong and how can I fix it?

 

[TpwUK]

Can't help much without knowing the CPU architecture ... Ivy, Sandy or Haswell. But -c is for the bridge type.

Martin

 

[TpwUK]

Need some help here if possible ...
Using dual E5-2620 v2 processors here and I have Speedstep and Turbo working but not according to CPU specs. Low load should be 1.2Ghz, medium load = 2.1Ghz, max load = 2.4Ghz with a BIOS assigned target speed of 2.6Ghz.



As can be seen using HWMonitor, the cpus are maxing at 2.1Ghz instead of the 2.4Ghz (which has been tested and achieved with win7). I have a sneaky suspicion that the BIOS has biased things as it has a non adjustable Max Speed setting of 2100. I have tried all versions of my motherboards BIOS from 5404 - 5701 and have unlocked the MSR's manually but have no idea if the mods have been successful.

I am that close to having a perfectly running ASUS Z9PE-D8 WS that i can taste it.

Do i need to fine tweak the SSDT generated to achieve the all so allusive 2.4Ghz Turbo ? I have included the SSDT as I have absolutely no idea if it can be edited or where those edits should be to achieve the max turbo setting. Can any body help ?

Martin

 

[giacomoleopardo]

Do i need to fine tweak the SSDT generated to achieve the all so allusive 2.4Ghz Turbo ? I have included the SSDT as I have absolutely no idea if it can be edited or where those edits should be to achieve the max turbo setting. Can any body help ?

I would try Shilohh's guide. Please post results.

 

[TpwUK]

Thanks for the reply Giacomoleopardo - I did see that thread and did indeed use some of the tools mentioned therein, but that motherboard is different from my Z9PE-D8 WS.

• PikeRAlphas' AICPM patch was successful, I no longer need NullPowerManagement
• PikeRAlphas' IvyBridgeSSDT script was used with -c 1 -w 3 -Turbo 2400 -p "E5-2620 v2" - SSDT generated provided with original post.
• I can't use a BIOS lower than 5404 as that's the earliest my CPU's were supported but I have pure versions with locked MSR and modded versions of 5701, 5601, 5404 etc and I have tried all of them. All with newly generated DSDT and SSDT for every BIOS swap or change in settings
• The results given by HWMonitor show idle @ 1200 and maxed out using keyshot5 @ 2100.

here are the script results for ssdtPRgen and RunAICPUPM, is there anything else i should include ?


Martin

 

[giacomoleopardo]

The results given by HWMonitor show idle @ 1200 and maxed out using keyshot5 @ 2100

Wich bootloader? Boot flags? Did you try Intel Power Gadget to see if there are other frequencies beside 1200 and 2100?
Did you use X79X86PlatformPlugin.kext as per Shilohh guide?
It seems that PM is not working on your rig

 

[TpwUK]

Thanks for the reply again Giacomoleopardo

Did you try Intel Power Gadget to see if there are other frequencies beside 1200 and 2100?

Can't use this on Dual CPU's, however, windows can quiet happily push the cpu's to 2400

Did you use X79X86PlatformPlugin.kext

No, not sure if it is compatible with my Motherboard, I am x64 and not running on ASUS X79, I have scoured through the manual and can find no mention of X79 - I assume this is based on a chipset ID, my motherboard is C602. Guess there is no harm in trying it, might need a further install if it screws up.

It seems that PM is not working on your rig

Agreed - This does indeed seem to be the case.

Boot loader is chameleon ... Here's my Boot.plist if you think it may help

 

[giacomoleopardo]

I am x64 and not running on ASUS X79, I have scoured through the manual and can find no mention of X79 - I assume this is based on a chipset ID, my motherboard is C602. Guess there is no harm in trying it, might need a further install if it screws up

X79 and C602 are strictly related. I would go for X79X86PlatformPlugin.kext (reported for IvyBridge E, but still, your cpu is IvyBridge EP), and I would give "dropSSDT=Yes" a shot, why not? Or maybe GenerateC and PStates=Yes... this is totally empirical, of course, I'm not an expert in power management, nor in workstation.
According to Shilohh here, maybe Pike's SSDT needs to be fully loaded (like for example in Z97/87/77), instead of just adding CPU states to the OEM ssdt.

 

[TpwUK]

X79X86PlatformPlugin.kext Just locked out my hard drives and I am now replying from a live Linux DVD - Guess that one does not work - lol

I have tried drop DSDT before, some say drop it others say not to as the SSDT script does not generate a full SSDT just the power management section.

Might not be back on for a while as the USB installer can't even see the drives now, so will see what i can do from the Live DVD

Martin