charliebounce Posted May 31, 2014 Share Posted May 31, 2014 Hi! My question is how do you know that your p-states are working property? Have do you checked with a software? THanks! Hi Picasso, I used the the AppleCPUPowerManagementInfo.kext from PikerAlpha. To check the P-States. See the terminal extract i have just generated. May 31 20:25:28 macpro kernel[0]: AICPUPMI: v3.2 Copyright © 2012-2014 Pike R. Alpha. All rights reserved May 31 20:25:28 macpro kernel[0]: AICPUPMI: logMSRs............................: 1 May 31 20:25:28 macpro kernel[0]: AICPUPMI: logIGPU............................: 0 May 31 20:25:28 macpro kernel[0]: AICPUPMI: logCStates.........................: 1 May 31 20:25:28 macpro kernel[0]: AICPUPMI: logIPGStyle........................: 1 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MWAIT C-States.....................: 4384 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_CORE_THREAD_COUNT......(0x35) : 0x40008 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PLATFORM_INFO..........(0xCE) : 0x81010F0012300 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PMG_CST_CONFIG_CONTROL.(0xE2) : 0x1E008401 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PMG_IO_CAPTURE_BASE....(0xE4) : 0x414 May 31 20:25:28 macpro kernel[0]: AICPUPMI: IA32_MPERF.................(0xE7) : 0x9D6AD8C May 31 20:25:28 macpro kernel[0]: AICPUPMI: IA32_APERF.................(0xE8) : 0xA9CB905 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_FLEX_RATIO.............(0x194) : 0xE0000 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_IA32_PERF_STATUS.......(0x198) : 0x24D400003000 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_IA32_PERF_CONTROL......(0x199) : 0x3000 May 31 20:25:28 macpro kernel[0]: AICPUPMI: IA32_CLOCK_MODULATION......(0x19A) : 0x0 May 31 20:25:28 macpro kernel[0]: AICPUPMI: IA32_THERM_STATUS..........(0x19C) : 0x88300000 May 31 20:25:28 macpro kernel[0]: AICPUPMI: IA32_MISC_ENABLES..........(0x1A0) : 0x850089 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_MISC_PWR_MGMT..........(0x1AA) : 0x400001 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x30303030 May 31 20:25:28 macpro kernel[0]: AICPUPMI: IA32_ENERGY_PERF_BIAS......(0x1B0) : 0xF May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_POWER_CTL..............(0x1FC) : 0x4005F May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_RAPL_POWER_UNIT........(0x606) : 0xA1003 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PKG_POWER_LIMIT........(0x610) : 0x800087F8001487F8 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PKG_ENERGY_STATUS......(0x611) : 0x1AF52520 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PKGC3_IRTL.............(0x60a) : 0x883B May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PKGC6_IRTL.............(0x60b) : 0x8850 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PKGC7_IRTL.............(0x60c) : 0x8857 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PP0_CURRENT_CONFIG.....(0x601) : 0x1814149480001FFF May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PP0_POWER_LIMIT........(0x638) : 0x0 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PP0_ENERGY_STATUS......(0x639) : 0xD264D78 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PP0_POLICY.............(0x63a) : 0x0 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_CONFIG_TDP_NOMINAL.....(0x648) : 0x23 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_CONFIG_TDP_LEVEL1......(0x649) : 0x1E0000000000000 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_CONFIG_TDP_LEVEL2......(0x64a) : 0x1E0000000000000 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_CONFIG_TDP_CONTROL.....(0x64b) : 0x80000000 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_TURBO_ACTIVATION_RATIO.(0x64c) : 0x0 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PKG_C2_RESIDENCY.......(0x60d) : 0x1513960C120 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PKG_C3_RESIDENCY.......(0x3f8) : 0x0 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PKG_C6_RESIDENCY.......(0x3f9) : 0x0 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PKG_C7_RESIDENCY.......(0x3fa) : 0x0 May 31 20:25:28 macpro kernel[0]: AICPUPMI: CPU Low Frequency Mode.............: 1600 MHz May 31 20:25:28 macpro kernel[0]: AICPUPMI: CPU Maximum non-Turbo Frequency....: 3500 MHz May 31 20:25:28 macpro kernel[0]: AICPUPMI: CPU Maximum Turbo Frequency........: 4800 MHz May 31 20:25:29 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 19 48 ] May 31 20:25:29 macpro kernel[0]: AICPUPMI: CPU C3-Cores [ 1 2 3 4 ] May 31 20:25:29 macpro kernel[0]: AICPUPMI: CPU C6-Cores [ 0 1 2 3 4 5 ] May 31 20:25:29 macpro kernel[0]: AICPUPMI: CPU C7-Cores [ 0 1 2 3 4 5 7 ] May 31 20:25:30 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 48 ] May 31 20:25:30 macpro kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 ] May 31 20:25:30 macpro kernel[0]: AICPUPMI: CPU C6-Cores [ 0 1 2 3 4 5 6 7 ] May 31 20:25:30 macpro kernel[0]: AICPUPMI: CPU C7-Cores [ 0 1 2 3 4 5 6 7 ] May 31 20:25:30 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 25 48 ] May 31 20:25:31 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 21 25 48 ] May 31 20:25:31 macpro kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 5 ] May 31 20:25:31 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 20 21 25 48 ] May 31 20:25:32 macpro kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 5 6 7 ] May 31 20:25:33 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 20 21 24 25 48 ] May 31 20:25:36 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 20 21 22 24 25 48 ] May 31 20:25:37 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 20 21 22 24 25 26 48 ] May 31 20:25:39 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 24 (25) 26 32 48 ] May 31 20:25:41 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 24 25 26 (30) 32 48 ] May 31 20:25:44 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 24 25 26 28 (30) 32 48 ] May 31 20:25:47 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 20 21 22 23 24 25 26 28 30 32 48 ] May 31 20:26:02 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 20 21 22 23 24 25 26 27 28 30 32 48 ] May 31 20:26:15 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 (25) 26 27 28 30 31 32 48 ] May 31 20:26:18 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 30 31 32 47 (48) ] May 31 20:26:20 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 30 31 32 42 47 (48) ] May 31 20:26:26 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 30 31 32 42 44 47 (48) ] May 31 20:26:46 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 30 31 32 42 44 46 47 (48) ] May 31 20:26:51 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 42 44 46 47 48 ] May 31 20:26:52 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 39 42 44 46 47 48 ] May 31 20:26:52 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 39 (41) 42 44 46 47 48 ] May 31 20:26:53 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 (35) 39 41 42 44 46 47 48 ] May 31 20:26:53 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 29 (30) 31 32 34 35 39 41 42 44 46 47 48 ] May 31 20:27:31 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 34 35 37 39 41 42 44 46 47 48 ] May 31 20:29:07 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 (25) 26 27 28 29 30 31 32 33 34 35 37 39 41 42 44 46 47 48 ] May 31 20:31:02 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 (35) 37 39 41 42 43 44 46 47 48 ] May 31 20:31:26 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 37 39 41 42 43 44 45 46 47 (48) ] May 31 20:33:36 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 37 38 39 41 42 43 44 45 46 47 (48) ] May 31 20:33:42 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 41 42 43 44 45 46 47 (48) ] May 31 20:34:29 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 29 (30) 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 ] 2 Link to comment Share on other sites More sharing options...
Picasso Posted May 31, 2014 Share Posted May 31, 2014 Hi Picasso, I used the the AppleCPUPowerManagementInfo.kext from PikerAlpha. To check the P-States. See the terminal extract i have just generated. May 31 20:25:28 macpro kernel[0]: AICPUPMI: v3.2 Copyright © 2012-2014 Pike R. Alpha. All rights reserved May 31 20:25:28 macpro kernel[0]: AICPUPMI: logMSRs............................: 1 May 31 20:25:28 macpro kernel[0]: AICPUPMI: logIGPU............................: 0 May 31 20:25:28 macpro kernel[0]: AICPUPMI: logCStates.........................: 1 May 31 20:25:28 macpro kernel[0]: AICPUPMI: logIPGStyle........................: 1 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MWAIT C-States.....................: 4384 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_CORE_THREAD_COUNT......(0x35) : 0x40008 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PLATFORM_INFO..........(0xCE) : 0x81010F0012300 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PMG_CST_CONFIG_CONTROL.(0xE2) : 0x1E008401 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PMG_IO_CAPTURE_BASE....(0xE4) : 0x414 May 31 20:25:28 macpro kernel[0]: AICPUPMI: IA32_MPERF.................(0xE7) : 0x9D6AD8C May 31 20:25:28 macpro kernel[0]: AICPUPMI: IA32_APERF.................(0xE8) : 0xA9CB905 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_FLEX_RATIO.............(0x194) : 0xE0000 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_IA32_PERF_STATUS.......(0x198) : 0x24D400003000 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_IA32_PERF_CONTROL......(0x199) : 0x3000 May 31 20:25:28 macpro kernel[0]: AICPUPMI: IA32_CLOCK_MODULATION......(0x19A) : 0x0 May 31 20:25:28 macpro kernel[0]: AICPUPMI: IA32_THERM_STATUS..........(0x19C) : 0x88300000 May 31 20:25:28 macpro kernel[0]: AICPUPMI: IA32_MISC_ENABLES..........(0x1A0) : 0x850089 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_MISC_PWR_MGMT..........(0x1AA) : 0x400001 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x30303030 May 31 20:25:28 macpro kernel[0]: AICPUPMI: IA32_ENERGY_PERF_BIAS......(0x1B0) : 0xF May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_POWER_CTL..............(0x1FC) : 0x4005F May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_RAPL_POWER_UNIT........(0x606) : 0xA1003 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PKG_POWER_LIMIT........(0x610) : 0x800087F8001487F8 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PKG_ENERGY_STATUS......(0x611) : 0x1AF52520 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PKGC3_IRTL.............(0x60a) : 0x883B May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PKGC6_IRTL.............(0x60b) : 0x8850 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PKGC7_IRTL.............(0x60c) : 0x8857 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PP0_CURRENT_CONFIG.....(0x601) : 0x1814149480001FFF May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PP0_POWER_LIMIT........(0x638) : 0x0 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PP0_ENERGY_STATUS......(0x639) : 0xD264D78 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PP0_POLICY.............(0x63a) : 0x0 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_CONFIG_TDP_NOMINAL.....(0x648) : 0x23 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_CONFIG_TDP_LEVEL1......(0x649) : 0x1E0000000000000 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_CONFIG_TDP_LEVEL2......(0x64a) : 0x1E0000000000000 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_CONFIG_TDP_CONTROL.....(0x64b) : 0x80000000 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_TURBO_ACTIVATION_RATIO.(0x64c) : 0x0 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PKG_C2_RESIDENCY.......(0x60d) : 0x1513960C120 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PKG_C3_RESIDENCY.......(0x3f8) : 0x0 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PKG_C6_RESIDENCY.......(0x3f9) : 0x0 May 31 20:25:28 macpro kernel[0]: AICPUPMI: MSR_PKG_C7_RESIDENCY.......(0x3fa) : 0x0 May 31 20:25:28 macpro kernel[0]: AICPUPMI: CPU Low Frequency Mode.............: 1600 MHz May 31 20:25:28 macpro kernel[0]: AICPUPMI: CPU Maximum non-Turbo Frequency....: 3500 MHz May 31 20:25:28 macpro kernel[0]: AICPUPMI: CPU Maximum Turbo Frequency........: 4800 MHz May 31 20:25:29 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 19 48 ] May 31 20:25:29 macpro kernel[0]: AICPUPMI: CPU C3-Cores [ 1 2 3 4 ] May 31 20:25:29 macpro kernel[0]: AICPUPMI: CPU C6-Cores [ 0 1 2 3 4 5 ] May 31 20:25:29 macpro kernel[0]: AICPUPMI: CPU C7-Cores [ 0 1 2 3 4 5 7 ] May 31 20:25:30 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 48 ] May 31 20:25:30 macpro kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 ] May 31 20:25:30 macpro kernel[0]: AICPUPMI: CPU C6-Cores [ 0 1 2 3 4 5 6 7 ] May 31 20:25:30 macpro kernel[0]: AICPUPMI: CPU C7-Cores [ 0 1 2 3 4 5 6 7 ] May 31 20:25:30 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 25 48 ] May 31 20:25:31 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 21 25 48 ] May 31 20:25:31 macpro kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 5 ] May 31 20:25:31 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 20 21 25 48 ] May 31 20:25:32 macpro kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 5 6 7 ] May 31 20:25:33 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 20 21 24 25 48 ] May 31 20:25:36 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 20 21 22 24 25 48 ] May 31 20:25:37 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 20 21 22 24 25 26 48 ] May 31 20:25:39 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 24 (25) 26 32 48 ] May 31 20:25:41 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 24 25 26 (30) 32 48 ] May 31 20:25:44 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 24 25 26 28 (30) 32 48 ] May 31 20:25:47 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 20 21 22 23 24 25 26 28 30 32 48 ] May 31 20:26:02 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 20 21 22 23 24 25 26 27 28 30 32 48 ] May 31 20:26:15 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 (25) 26 27 28 30 31 32 48 ] May 31 20:26:18 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 30 31 32 47 (48) ] May 31 20:26:20 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 30 31 32 42 47 (48) ] May 31 20:26:26 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 30 31 32 42 44 47 (48) ] May 31 20:26:46 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 30 31 32 42 44 46 47 (48) ] May 31 20:26:51 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 42 44 46 47 48 ] May 31 20:26:52 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 39 42 44 46 47 48 ] May 31 20:26:52 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 39 (41) 42 44 46 47 48 ] May 31 20:26:53 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 (35) 39 41 42 44 46 47 48 ] May 31 20:26:53 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 29 (30) 31 32 34 35 39 41 42 44 46 47 48 ] May 31 20:27:31 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 34 35 37 39 41 42 44 46 47 48 ] May 31 20:29:07 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 (25) 26 27 28 29 30 31 32 33 34 35 37 39 41 42 44 46 47 48 ] May 31 20:31:02 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 (35) 37 39 41 42 43 44 46 47 48 ] May 31 20:31:26 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 37 39 41 42 43 44 45 46 47 (48) ] May 31 20:33:36 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 37 38 39 41 42 43 44 45 46 47 (48) ] May 31 20:33:42 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 41 42 43 44 45 46 47 (48) ] May 31 20:34:29 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 29 (30) 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 ] Excelent! I will find the kext and the way to apply and get my results. Thanks again! Link to comment Share on other sites More sharing options...
charliebounce Posted May 31, 2014 Share Posted May 31, 2014 Excelent! I will find the kext and the way to apply and get my results. Thanks again! Just noticed the 17 P-States was missing... May 31 20:34:29 macpro kernel[0]: AICPUPMI: CPU P-States [ 16 18 19 20 21 22 23 24 25 26 27 28 29 (30) 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 ] May 31 20:50:55 macpro kernel[0]: AICPUPMI: CPU P-States [ (16) 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 ] Link to comment Share on other sites More sharing options...
Tatocr Posted June 5, 2014 Share Posted June 5, 2014 Now copy this perl code if you use version 10.9 or 10.9.1 sudo perl -pi -e 's|\x74\x6c(\x48\x83\xc7\x28\x90\x8b\x05..\x5e\x00\x85\x47\xdc)\x74\x54(\x8b\x4f\xd8\x45\x85\xc0\x74\x08\x44\x39\xc1\x44\x89\xc1)\x75\x44(\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x57\xf8\x48\x8b\x47\xe8\x48\x85\xc0\x74\x06\x48\xf7\xd0\x48\x21\xc2\x48\x0b\x57\xf0\x49\x89\xd1\x49\xc1\xe9\x20\x89\xd0\x8b\x4f\xd8\x4c\x89\xca)(\x0f\x30\x8b\x4f\xd8\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x17\x48\x83\xc7\x30\xff\xce)\x75\x99(\x5d\xc3)\x90{7}|\x74\x73${1}\x74\x5b${2}\x75\x4b${3}\x66\x81\xf9\xe2\x00\x74\x02${4}\x75\x92${5}|g' mach_kernel Good morning. These codes would be good for 10.9.3? thanks Link to comment Share on other sites More sharing options...
Picasso Posted June 6, 2014 Share Posted June 6, 2014 Now copy this perl code if you use version 10.9 or 10.9.1 sudo perl -pi -e 's|\x74\x6c(\x48\x83\xc7\x28\x90\x8b\x05..\x5e\x00\x85\x47\xdc)\x74\x54(\x8b\x4f\xd8\x45\x85\xc0\x74\x08\x44\x39\xc1\x44\x89\xc1)\x75\x44(\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x57\xf8\x48\x8b\x47\xe8\x48\x85\xc0\x74\x06\x48\xf7\xd0\x48\x21\xc2\x48\x0b\x57\xf0\x49\x89\xd1\x49\xc1\xe9\x20\x89\xd0\x8b\x4f\xd8\x4c\x89\xca)(\x0f\x30\x8b\x4f\xd8\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x17\x48\x83\xc7\x30\xff\xce)\x75\x99(\x5d\xc3)\x90{7}|\x74\x73${1}\x74\x5b${2}\x75\x4b${3}\x66\x81\xf9\xe2\x00\x74\x02${4}\x75\x92${5}|g' mach_kernel Good morning. These codes would be good for 10.9.3? thanks WTF is this? Link to comment Share on other sites More sharing options...
Slice Posted June 14, 2014 Share Posted June 14, 2014 Hello Of Course, but ACPI_SMC_PlatformPlugin isn't a kext, it's a plugin of a kext IOPlatformPluginFamily. No, this is a kext. $ sudo kextstat | grep SMC Password: 13 4 0xffffff7f80c3d000 0xd000 0xd000 org.netkas.FakeSMC (3.3.1) <10 7 5 4 3> 79 2 0xffffff7f81157000 0x15000 0x15000 com.apple.driver.AppleSMC (3.1.8) <10 7 5 4 3 1> 88 0 0xffffff7f8113e000 0x3000 0x3000 com.apple.driver.AppleSMCPDRC (1.0.0) <87 11 6 4 3> 93 0 0xffffff7f8116c000 0x10000 0x10000 com.apple.driver.ACPI_SMC_PlatformPlugin (1.0.0) <92 87 79 11 10 7 6 5 4 3> 1 Link to comment Share on other sites More sharing options...
Jonathan Chagas Posted June 22, 2014 Share Posted June 22, 2014 I FIX IT!!!! The problem always was the SSDT file of this script. I don't know why in my laptop never works.... I use google and i found the SSDT for all intel processors included the SSDT for my CPU (i3 2330M). The steps i follow for get the SSDT works: 1.- replace de SSDT file with the SSDT for my CPU. I attach the file for all SSDT for i3, i5 and i7 processor in this post. 2.- Patch AppleIntelCPUPowermanagement (for this guide) 3.- repair cache and system with kextwizard. reboot and now my computer feels faster. i run a geek bench and i get this score: BEFORE http://browser.primatelabs.com/geekbench2/2398165 NOW http://browser.primatelabs.com/geekbench2/2426915 but now i have a question. I need information about the p-states in my laptop. where i can get this info??? Hydra, I have the same notebook that you applied the patch correctly and I can run without NullCPM.kext and without kernel panic. However, my result in Geekbench continues for 2030 ... You can make the SSDT and DSDT specific for your Dell? I think that's the problem ... (Sorry my bad English, is the fault of Google Translator kkk) Link to comment Share on other sites More sharing options...
Allan Posted June 22, 2014 Share Posted June 22, 2014 Hello @jonathan.chagas. Did you try create a SSDT for you? Use this command: curl -o ssdtPRGen.sh https://raw.githubusercontent.com/Piker-Alpha/ssdtPRGen.sh/master/ssdtPRGen.sh chmod +x ssdtPRGen.sh ./ssdtPRGen.sh Link to comment Share on other sites More sharing options...
Jonathan Chagas Posted June 23, 2014 Share Posted June 23, 2014 Hello @jonathan.chagas. Did you try create a SSDT for you? Use this command: curl -o ssdtPRGen.sh https://raw.githubusercontent.com/Piker-Alpha/ssdtPRGen.sh/master/ssdtPRGen.sh chmod +x ssdtPRGen.sh ./ssdtPRGen.sh Yes! I also applied a patch in DSDT to load AppleLTC.kext. The PStates is always 8 :/ Ps: A gnt n pode falar em português não? xD Link to comment Share on other sites More sharing options...
Allan Posted June 23, 2014 Share Posted June 23, 2014 I've seen what happens to your states in Olarila forum. Ps: Vamos dar continuidade no Olarila, ou se ainda tiver duvidas sobre isso, abra um topico no Forum Portugues, esse guia tem lá também: Gerenciamento de energia para Sandy Bridge/Ivy Bridge/Haswell CPU 1 Link to comment Share on other sites More sharing options...
Hackintosher1 Posted June 23, 2014 Share Posted June 23, 2014 I've seen what happens to your states in Olarila forum. Ps: Vamos dar continuidade no Olarila, ou se ainda tiver duvidas sobre isso, abra um topico no Forum Portugues, esse guia tem lá também: Gerenciamento de energia para Sandy Bridge/Ivy Bridge/Haswell CPU Hi Allan I have same specs as one of the members here but his score was 5000 after fixing his SSDT. http://www.insanelymac.com/forum/topic/295587-power-management-for-sandyivy-bridgehaswell-cpus/page-2?do=findComment&comment=1996810 I tried the guide but unluckily I only get 3000 with geek bench.. Is it possible for me to get higher scores? I need help to understand SSDT and eventually fix performance.. http://browser.primatelabs.com/geekbench3/631506 Specs in signature. Link to comment Share on other sites More sharing options...
Allan Posted June 24, 2014 Share Posted June 24, 2014 Apply patch in AICPM: http://www.insanelymac.com/forum/topic/295587-power-management-for-sandyivy-bridgehaswell-cpus/?p=1988633 After this, delete NullCPUPM, if you have. About SSDT, read here: DSDT/SSDT: Everything you need to know SSDT 1 Link to comment Share on other sites More sharing options...
ergot Posted June 24, 2014 Share Posted June 24, 2014 HI, when running the second command I'm getting: chmod: ssdtPRGen.sh: No such file or directory Link to comment Share on other sites More sharing options...
Hackintosher1 Posted June 24, 2014 Share Posted June 24, 2014 HI, when running the second command I'm getting: chmod: ssdtPRGen.sh: No such file or directory Hi Try this guide http://olarila.com/forum/viewtopic.php?f=28&t=1703 Same thing happened to me. Its same but this one worked 1 Link to comment Share on other sites More sharing options...
marco.pisellonio80 Posted June 28, 2014 Share Posted June 28, 2014 Hi, My desktop in signature has sandy-bridge, with 10.9.3 and fixed and patched DSDT. In my o.c.b.p. I have generate P and C states. Should I follow this guide? What benefits do I have? Thank you Link to comment Share on other sites More sharing options...
Picasso Posted June 29, 2014 Share Posted June 29, 2014 Just a few more of P-States, values form the PowerManager between the minimum and the maximum clock speed, a little less of temperature. I read is useful to get more balance between CPU and GPU. In my test the result are the same, but de degrees are lower, not too much. Link to comment Share on other sites More sharing options...
marco.pisellonio80 Posted June 29, 2014 Share Posted June 29, 2014 Lower degrees are a good reason to try. Thank you Link to comment Share on other sites More sharing options...
Pimentel Posted June 30, 2014 Author Share Posted June 30, 2014 Hello Picasso To get more P-Sates try use another different DSDT model... i use MacBook pro 8,1 amd work better than iMac 12.... Don't forget to create SSDT, path ACPUPM if you need and make tests to see what really work fo you... Link to comment Share on other sites More sharing options...
step1step2 Posted July 25, 2014 Share Posted July 25, 2014 Mainboard: Asus Z87-A (C2) Intel Z87 So.1150 Dual Channel DDR3 ATX Retail CPU: Intel Core i5 4670K 4x 3.40GHz So.1150 EFI Folder: http://www.filedropper.com/efi My speed steep is not working good. Link to comment Share on other sites More sharing options...
Allan Posted July 25, 2014 Share Posted July 25, 2014 iMac only have 4 p-states. For you i recommend MacPro6,1. 1 Link to comment Share on other sites More sharing options...
Picasso Posted July 25, 2014 Share Posted July 25, 2014 Hello Picasso To get more P-Sates try use another different DSDT model... i use MacBook pro 8,1 amd work better than iMac 12.... Don't forget to create SSDT, path ACPUPM if you need and make tests to see what really work fo you... Thanks. I did a research and it's not very important to the Power Management which Mac Model do you use, if not copy and paste the Privacy Policy from Mac Pro 6.1 to the others. The problem using Mac Pro 6.1 it's the discrete graphics, not work fine. And - for other thread of course - the only way I get the video Power Management working - not full load all the time after use Final Cut or Cs6, Preview or Vlc -is using the Nvidia drivers (If you have Nvidia). My source of information was Piker Alpha's site and Toleda guide. Thanks again Pimentel! Link to comment Share on other sites More sharing options...
step1step2 Posted July 25, 2014 Share Posted July 25, 2014 The problem not solved. Whit SSDT and change of SMBIOS doesn't work. Link to comment Share on other sites More sharing options...
Allan Posted July 25, 2014 Share Posted July 25, 2014 U use Clover or Chameleon? Link to comment Share on other sites More sharing options...
Pimentel Posted July 26, 2014 Author Share Posted July 26, 2014 Hello The problem not solved. Whit SSDT and change of SMBIOS doesn't work. You can use a mobile SMbios model... try MacBookPro 11,1 Maybe work... Thanks. I did a research and it's not very important to the Power Management which Mac Model do you use, if not copy and paste the Privacy Policy from Mac Pro 6.1 to the others. The problem using Mac Pro 6.1 it's the discrete graphics, not work fine. Look, i noted that with different model identifier a got diferents P-States... i just noted this with my experience and i think that this can be used for others users... if work or not, depends of the situation... but with me work But thanks by the info Hello The problem not solved. Whit SSDT and change of SMBIOS doesn't work. You can use a mobile SMbios model... try MacBookPro 11,1 Maybe work... Thanks. I did a research and it's not very important to the Power Management which Mac Model do you use, if not copy and paste the Privacy Policy from Mac Pro 6.1 to the others. The problem using Mac Pro 6.1 it's the discrete graphics, not work fine. Look, i noted that wit 1 Link to comment Share on other sites More sharing options...
styrian Posted July 26, 2014 Share Posted July 26, 2014 Hello! I think, that it is not very useful, to generate more C-states, then a desktop cpu by given specs has. The values should be correctly recognized by Pike´s ssdtPreGen script or by Clover. Look at the data sheets at intel for the values of your cpu. Mobile cpus have for sure more states to extened the time of usage with battery power. More important is to use the correct SMBios for the platform of your cpu architecture and fake a not existing mac model based on this personality, but you have to exclude the not matching cpu management parts and add a to your used gfx-card corresponding AGPM control part. Take a look at the original posts of Masterchief here: http://www.insanelym...e-pr/?p=1287021 http://www.insanelym...e-pr/?p=1289092 I know, that this is a bit old school, but worth every cent. You don´t need to touch orignal system kexts on every update and edit them again. If you have got your Legacy kexts working, you can use them as long as the used original SMBios personality is supported on OSX systems. I have added example kexts for faking a not existing MacPro 5,2, based on the SMBios of an iMac 12,2 with the graphics control ID of the SMBios of MacPro 5,1. If you want to try them, you have to reinstall the untouched versions of the AGPM and the IOPlatformFamily.kext. You have also to rename your SMBios product name to MacPro 5,2, but generate your SN for the real iMac 12,2. (or edit the plists of the attached kexts to your preffered fake name) In the attachment are versions for NVidia gfx-cards on desktop systems with Sandybridge CPU`s. You have only to edit the LegacyAGPM.kext with your ID by exchanging the xxxx digits with it. If you have gfx-performance leaks, you can adapt the Treshold values. For AMD cards you have to edit the LegacyAGPM.kext with your Vendor and Device ID´s and the til now used values without changing the control ID. I personally have made the experience, that it is for Clover a basic requirement to get AGPM working, having generated a valid Board SN for the used and by Clover recognized real SMBios personality. I think more or less C-states, don´t really matter on a desktop system. More important is to have a smooth and stable running system without being suffered from KP with full and proper working PM. The lowest and highest C-states should get available reached, when needed. For other used SMBios personalities you can for sure adapt the attached kexts. Have fun. Master Chiefs Legacy-kexts.zip 1 Link to comment Share on other sites More sharing options...
Recommended Posts