Jump to content
InsanelyMac Forum
rawmassen

Mystery: SpeedStep - Clover - z97x - 4790K

Recommended Posts

Hi (I can't post in the Clover boot loader section for some reason, I hope this is OK here),

I'm running a Gigabyte Z97 UD5H + 4790K combo (Yosemite 10.10.1).

Clover is set to not generate C/P states (turned on in the BIOS, however), yet SpeedStep is fully working (checking with the Intel Power Gadget).

I do not have an SSDT installed either.

It crashes very rarely (if left overnight, awake or asleep) - would it be better to install a custom SSDT, or just leave it? BIOS tweaks might make it more stable.

It seems to be generating quite a few states...

0.8
1.12
1.15
1.19
1.44
1.76
2.08
2.40
2.72
3.04
3.36
...

Any ideas why its working automagically, and if an SSDT is worth it?

Thanks!

 

Share this post


Link to post
Share on other sites
Advertisement

I think that getting a 3.36 state means that you need to calculate the correct FreequencyMHz,BusSpeedkHz and QPI  in CPU section in config.plist for your machine. If all were correct, your state would be 3.40 instead of 3.36 etc.. I bet your About this Mac window says you have 3.39 CPU :P

Share this post


Link to post
Share on other sites

I think that getting a 3.36 state means that you need to calculate the correct FreequencyMHz,BusSpeedkHz and QPI  in CPU section in config.plist for your machine. If all were correct, your state would be 3.40 instead of 3.36 etc.. I bet your About this Mac window says you have 3.39 CPU :P

 

About this Mac states 4Ghz :¬)

 

The states go higher than that (I just didn't list them), all the way to 4.7Ghz which is my turbo overlock.

 

Don't understand why it works without being set in either Clover config or via SSDT!

Share this post


Link to post
Share on other sites

I believe the Intel Power Gadget shows the average frequency of all cores. So you may have 3 cores @0,8 (base freq) + 1 @4 (max freq or turbo) and it will show the frequency as 1,6GHz. To really see what steps it uses try the AppleIntelInfo kext by Pike.

Share this post


Link to post
Share on other sites

I believe the Intel Power Gadget shows the average frequency of all cores. So you may have 3 cores @0,8 (base freq) + 1 @4 (max freq or turbo) and it will show the frequency as 1,6GHz. To really see what steps it uses try the AppleIntelInfo kext by Pike.

 

Thanks, nabbed and tested. It appears to match the Intel Gadget.

 

Here's a paste from the log, does that look normal?

 

 

Jan 21 20:45:19 Rosss-iMac kernel[0]: AICPUPMI: CPU Low Frequency Mode.............: 800 MHz
Jan 21 20:45:19 Rosss-iMac kernel[0]: AICPUPMI: CPU Maximum non-Turbo Frequency....: 4000 MHz
Jan 21 20:45:19 Rosss-iMac kernel[0]: AICPUPMI: CPU Maximum Turbo Frequency........: 4700 MHz
Jan 21 20:45:20 Rosss-iMac kernel[0]: AICPUPMI: CPU P-States [ (8) 29 47 ]
Jan 21 20:45:20 Rosss-iMac kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 4 ]
Jan 21 20:45:20 Rosss-iMac kernel[0]: AICPUPMI: CPU C6-Cores [ 1 3 4 7 ]
Jan 21 20:45:20 Rosss-iMac kernel[0]: AICPUPMI: CPU C7-Cores [ 2 3 4 6 7 ]
Jan 21 20:45:20 Rosss-iMac kernel[0]: AICPUPMI: CPU P-States [ (8) 29 35 47 ]
Jan 21 20:45:20 Rosss-iMac kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 ]
Jan 21 20:45:20 Rosss-iMac kernel[0]: AICPUPMI: CPU C6-Cores [ 1 2 3 4 5 7 ]
Jan 21 20:45:20 Rosss-iMac kernel[0]: AICPUPMI: CPU C7-Cores [ 0 1 2 3 4 5 6 7 ]
Jan 21 20:45:21 Rosss-iMac kernel[0]: AICPUPMI: CPU P-States [ 8 29 35 (40) 47 ]
Jan 21 20:45:21 Rosss-iMac kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 5 ]
Jan 21 20:45:21 Rosss-iMac kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 5 6 ]
Jan 21 20:45:21 Rosss-iMac kernel[0]: AICPUPMI: CPU C6-Cores [ 0 1 2 3 4 5 6 7 ]
Jan 21 20:45:22 Rosss-iMac kernel[0]: AICPUPMI: CPU P-States [ (8) 23 29 35 40 47 ]
Jan 21 20:45:22 Rosss-iMac kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 5 6 7 ]
Jan 21 20:45:22 Rosss-iMac kernel[0]: AICPUPMI: CPU P-States [ (8) 23 29 32 35 40 47 ]
Jan 21 20:45:23 Rosss-iMac kernel[0]: AICPUPMI: CPU P-States [ (8) 23 28 29 32 35 40 47 ]
Jan 21 20:45:23 Rosss-iMac kernel[0]: AICPUPMI: CPU P-States [ (8) 23 27 28 29 32 35 40 47 ]
Jan 21 20:45:24 Rosss-iMac kernel[0]: AICPUPMI: CPU P-States [ (8) 23 26 27 28 29 32 35 40 47 ]
Jan 21 20:45:24 Rosss-iMac kernel[0]: AICPUPMI: CPU P-States [ (8) 23 26 27 28 29 31 32 35 40 47 ]
Jan 21 20:45:25 Rosss-iMac kernel[0]: AICPUPMI: CPU P-States [ (8) 23 25 26 27 28 29 31 32 35 40 47 ]
Jan 21 20:45:25 Rosss-iMac kernel[0]: AICPUPMI: CPU P-States [ 8 23 25 26 27 28 29 31 32 33 35 (40) 47 ]
Jan 21 20:45:27 Rosss-iMac kernel[0]: AICPUPMI: CPU P-States [ (8) 23 24 25 26 27 28 29 31 32 33 35 40 47 ]
Jan 21 20:45:28 Rosss-iMac kernel[0]: AICPUPMI: CPU P-States [ (8) 20 23 24 25 26 27 28 29 31 32 33 35 40 47 ]
Jan 21 20:45:30 Rosss-iMac kernel[0]: AICPUPMI: CPU P-States [ (8) 20 23 24 25 26 27 28 29 30 31 32 33 35 40 47 ]
Jan 21 20:45:39 Rosss-iMac kernel[0]: AICPUPMI: CPU P-States [ (8) 20 21 23 24 25 26 27 28 29 30 31 32 33 35 40 47 ]
Jan 21 20:45:51 Rosss-iMac kernel[0]: AICPUPMI: CPU P-States [ (8) 20 21 22 23 24 25 26 27 28 29 30 31 32 33 35 40 47 ]
Jan 21 20:46:02 Rosss-iMac kernel[0]: AICPUPMI: CPU P-States [ 8 17 20 21 22 23 24 25 26 27 28 29 30 31 32 33 35 (40) 47 ]
Jan 21 20:46:06 Rosss-iMac kernel[0]: AICPUPMI: CPU P-States [ (8) 17 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 40 47 ]
Jan 21 20:46:07 Rosss-iMac kernel[0]: AICPUPMI: CPU P-States [ 8 17 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 (40) 47 ]
Jan 21 20:46:09 Rosss-iMac kernel[0]: AICPUPMI: CPU P-States [ 8 17 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 (40) 47 ]
Jan 21 20:46:14 Rosss-iMac kernel[0]: AICPUPMI: CPU P-States [ 8 17 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 (40) 47 ]
Jan 21 20:46:15 Rosss-iMac kernel[0]: AICPUPMI: CPU P-States [ 8 17 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 (40) 47 ]
Jan 21 20:46:30 Rosss-iMac kernel[0]: AICPUPMI: CPU P-States [ (8) 17 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 47 ]

Share this post


Link to post
Share on other sites

Let it run for a while, try a benchmark app like Cinebench or something else and look at the log again. For now I can see it using only the 8 and 40 multipliers (the ones in parenthesis), the rest are "discovered" but not used. Then enable the P&C state generators (or load an SSDT) and test again.

 

And I'm not sure but you might need to enable the KernelPm patch or add the -xcpm kernel argument to get proper power management on your Haswell CPU.

Share this post


Link to post
Share on other sites

Let it run for a while, try a benchmark app like Cinebench or something else and look at the log again. For now I can see it using only the 8 and 40 multipliers (the ones in parenthesis), the rest are "discovered" but not used. Then enable the P&C state generators (or load an SSDT) and test again.

 

And I'm not sure but you might need to enable the KernelPm patch or add the -xcpm kernel argument to get proper power management on your Haswell CPU.

 

It hits 8, 40 and 47 (idle, core and turbo), just nothing in between. Intel gadget shows the in-between values though.

 

In all the examples of AppleIntelInfo I've seen, that's all that happens (3 states). Do you have examples of it selecting multiple?

 

SMBIOS is set to iMac if that makes a difference.

 

Thank you, by the way, adding -xcpm to Clover boot has reduced my boot time (from cold) to about 13 seconds :¬)

Share this post


Link to post
Share on other sites

In my system I've seen up to 7 states with AppleIntelInfo (min 16 + 20-25-30 + max 34 + turbos 44-45), but it's a Sandy Bridge, no idea about Haswells. And next time try to post a Clover boot log or a DarwinDumper report to see what's going on.

Share this post


Link to post
Share on other sites

I think that getting a 3.36 state means that you need to calculate the correct FreequencyMHz,BusSpeedkHz and QPI  in CPU section in config.plist for your machine. If all were correct, your state would be 3.40 instead of 3.36 etc.. I bet your About this Mac window says you have 3.39 CPU :P

Hello ! My first post on the forum, so first things first, thanks for all the ressources available here ! :)

 

My question is that I have the strange 3,69ghz in "about my mac". I'm not using clover but Chameleon. My profile is an iMac, can you tell me why I have this strange frequency, instead of the 3,5Ghz that is officially the frequency of my (non OCable) CPU when not in turbo mode ? I have an SSDT generated with ssdtPRGen. And here is my AICPUPMI log in case ... Thanks a lot, trying to figure that out for a few weeks but ... :)

     cat /var/log/system.log | grep "AICPUPMI:"
Feb 10 22:55:18 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ 8 33 35 36 37 38 (39) ]
Feb 10 22:55:21 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ 8 27 33 35 36 37 38 (39) ]
Feb 10 22:55:22 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 27 31 33 35 36 37 38 39 ]
Feb 10 22:55:23 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ 8 27 28 31 33 (35) 36 37 38 39 ]
Feb 10 22:55:25 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ 8 24 27 28 31 33 35 36 37 38 (39) ]
Feb 10 22:55:25 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 24 26 27 28 31 33 35 36 37 38 39 ]
Feb 10 22:55:27 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 24 25 26 27 28 31 33 35 36 37 38 39 ]
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: v3.3 Copyright © 2012-2014 Pike R. Alpha. All rights reserved
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: logMSRs............................: 1
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: logIGPU............................: 0
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: logCStates.........................: 1
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: logIPGStyle........................: 1
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MWAIT C-States.....................: 270624
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_CORE_THREAD_COUNT......(0x35)  : 0x40004
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_PLATFORM_INFO..........(0xCE)  : 0x80838F3012300
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_PMG_CST_CONFIG_CONTROL.(0xE2)  : 0x1E000005
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_PMG_IO_CAPTURE_BASE....(0xE4)  : 0x1814
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: IA32_MPERF.................(0xE7)  : 0xD8B5095F7
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: IA32_APERF.................(0xE8)  : 0xB16ECEB60
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_FLEX_RATIO.............(0x194) : 0x0
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_IA32_PERF_STATUS.......(0x198) : 0x20DD00002500
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_IA32_PERF_CONTROL......(0x199) : 0x2700
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: IA32_CLOCK_MODULATION......(0x19A) : 0x0
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: IA32_THERM_STATUS..........(0x19C) : 0x88440000
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: IA32_MISC_ENABLES..........(0x1A0) : 0x850089
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_MISC_PWR_MGMT..........(0x1AA) : 0x1
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x27272727
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: IA32_ENERGY_PERF_BIAS......(0x1B0) : 0x5
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_POWER_CTL..............(0x1FC) : 0x4005F
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_RAPL_POWER_UNIT........(0x606) : 0xA0E03
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_PKG_POWER_LIMIT........(0x610) : 0xFFD00000EA82
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_PKG_ENERGY_STATUS......(0x611) : 0x6750E8
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_PKGC3_IRTL.............(0x60a) : 0x8842
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_PKGC6_IRTL.............(0x60b) : 0x8873
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_PKGC7_IRTL.............(0x60c) : 0x8891
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_PP0_CURRENT_CONFIG.....(0x601) : 0x1F40
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_PP0_POWER_LIMIT........(0x638) : 0xFFD0
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_PP0_ENERGY_STATUS......(0x639) : 0x3C2496
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_PP0_POLICY.............(0x63a) : 0x0
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_CONFIG_TDP_NOMINAL.....(0x648) : 0x23
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_CONFIG_TDP_LEVEL1......(0x649) : 0x0
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_CONFIG_TDP_LEVEL2......(0x64a) : 0x0
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_CONFIG_TDP_CONTROL.....(0x64b) : 0x80000000
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_TURBO_ACTIVATION_RATIO.(0x64c) : 0x0
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_PKG_C2_RESIDENCY.......(0x60d) : 0x0
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_PKG_C3_RESIDENCY.......(0x3f8) : 0x0
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_PKG_C6_RESIDENCY.......(0x3f9) : 0x0
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: MSR_PKG_C7_RESIDENCY.......(0x3fa) : 0x0
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: CPU Low Frequency Mode.............: 800 MHz
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: CPU Maximum non-Turbo Frequency....: 3500 MHz
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: CPU Maximum Turbo Frequency........: 3900 MHz
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: CPU P-States [ (8) 29 37 ]
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 3 ]
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: CPU C7-Cores [ 0 1 3 ]
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: CPU P-States [ (8) 29 33 37 ]
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 ]
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: CPU C7-Cores [ 0 1 2 3 ]
Feb 11 07:04:45 localhost kernel[0]: AICPUPMI: CPU P-States [ (8) 29 33 34 37 ]
Feb 11 07:04:46 localhost kernel[0]: AICPUPMI: CPU P-States [ (8) 29 33 34 36 37 ]
Feb 11 07:04:46 localhost kernel[0]: AICPUPMI: CPU P-States [ (8) 29 30 33 34 36 37 ]
Feb 11 07:04:48 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ 8 29 30 33 34 36 37 (38) ]
Feb 11 07:04:49 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ 8 29 30 33 34 36 37 38 (39) ]
Feb 11 07:04:51 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ 8 29 30 33 34 (35) 36 37 38 39 ]
Feb 11 07:04:53 Barbatruc-2 kernel[0]: AICPUPMI: CPU C6-Cores [ 1 ]
Feb 11 07:04:53 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ 8 29 30 32 33 34 (35) 36 37 38 39 ]
Feb 11 07:04:54 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 28 29 30 32 33 34 35 36 37 38 39 ]
Feb 11 07:04:55 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 27 28 29 30 32 33 34 35 36 37 38 39 ]
Feb 11 07:04:55 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ 8 26 27 28 29 30 32 33 34 (35) 36 37 38 39 ]
Feb 11 07:04:56 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 25 26 27 28 29 30 32 33 34 35 36 37 38 39 ]
Feb 11 07:05:07 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 24 25 26 27 28 29 30 32 33 34 35 36 37 38 39 ]
Feb 11 07:05:10 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 07:05:11 Barbatruc-2 kernel[0]: AICPUPMI: CPU C6-Cores [ 0 1 ]
Feb 11 07:06:00 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 20 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 07:06:01 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 14 20 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 07:06:02 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 12 14 20 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 07:06:02 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 12 14 15 20 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 07:06:05 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 12 13 14 15 20 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 07:06:14 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 12 13 14 15 17 20 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 07:06:21 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 12 13 14 15 16 17 20 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 07:06:43 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 12 13 14 15 16 17 20 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 07:06:54 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 12 13 14 15 16 17 19 20 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 07:07:23 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 12 13 14 15 16 17 19 20 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 07:07:28 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 12 13 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 07:07:44 Barbatruc-2 kernel[0]: AICPUPMI: CPU C6-Cores [ 0 1 2 ]
Feb 11 07:07:56 Barbatruc-2 kernel[0]: AICPUPMI: CPU C6-Cores [ 0 1 2 3 ]
Feb 11 07:08:41 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 07:09:44 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 07:09:57 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: v3.3 Copyright © 2012-2014 Pike R. Alpha. All rights reserved
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: logMSRs............................: 1
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: logIGPU............................: 0
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: logCStates.........................: 1
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: logIPGStyle........................: 1
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MWAIT C-States.....................: 270624
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_CORE_THREAD_COUNT......(0x35)  : 0x40004
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_PLATFORM_INFO..........(0xCE)  : 0x80838F3012300
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_PMG_CST_CONFIG_CONTROL.(0xE2)  : 0x1E000005
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_PMG_IO_CAPTURE_BASE....(0xE4)  : 0x1814
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: IA32_MPERF.................(0xE7)  : 0xD8C3E5B38
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: IA32_APERF.................(0xE8)  : 0xB18DD7911
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_FLEX_RATIO.............(0x194) : 0x0
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_IA32_PERF_STATUS.......(0x198) : 0x20B500002500
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_IA32_PERF_CONTROL......(0x199) : 0x2700
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: IA32_CLOCK_MODULATION......(0x19A) : 0x0
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: IA32_THERM_STATUS..........(0x19C) : 0x88430000
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: IA32_MISC_ENABLES..........(0x1A0) : 0x850089
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_MISC_PWR_MGMT..........(0x1AA) : 0x1
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x27272727
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: IA32_ENERGY_PERF_BIAS......(0x1B0) : 0x5
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_POWER_CTL..............(0x1FC) : 0x4005F
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_RAPL_POWER_UNIT........(0x606) : 0xA0E03
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_PKG_POWER_LIMIT........(0x610) : 0xFFD00000EA82
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_PKG_ENERGY_STATUS......(0x611) : 0x65FF7A
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_PKGC3_IRTL.............(0x60a) : 0x8842
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_PKGC6_IRTL.............(0x60b) : 0x8873
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_PKGC7_IRTL.............(0x60c) : 0x8891
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_PP0_CURRENT_CONFIG.....(0x601) : 0x1F40
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_PP0_POWER_LIMIT........(0x638) : 0xFFD0
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_PP0_ENERGY_STATUS......(0x639) : 0x3BB918
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_PP0_POLICY.............(0x63a) : 0x0
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_CONFIG_TDP_NOMINAL.....(0x648) : 0x23
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_CONFIG_TDP_LEVEL1......(0x649) : 0x0
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_CONFIG_TDP_LEVEL2......(0x64a) : 0x0
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_CONFIG_TDP_CONTROL.....(0x64b) : 0x80000000
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_TURBO_ACTIVATION_RATIO.(0x64c) : 0x0
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_PKG_C2_RESIDENCY.......(0x60d) : 0x0
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_PKG_C3_RESIDENCY.......(0x3f8) : 0x0
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_PKG_C6_RESIDENCY.......(0x3f9) : 0x0
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: MSR_PKG_C7_RESIDENCY.......(0x3fa) : 0x0
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: CPU Low Frequency Mode.............: 800 MHz
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: CPU Maximum non-Turbo Frequency....: 3500 MHz
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: CPU Maximum Turbo Frequency........: 3900 MHz
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: CPU P-States [ (8) 29 37 ]
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 3 ]
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: CPU C7-Cores [ 0 2 3 ]
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 29 33 (35) 37 ]
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: CPU C7-Cores [ 0 1 2 3 ]
Feb 11 12:49:34 localhost kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 ]
Feb 11 12:49:35 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 29 33 35 36 37 (39) ]
Feb 11 12:49:37 Barbatruc-2 kernel[0]: AICPUPMI: CPU C6-Cores [ 2 ]
Feb 11 12:49:39 Barbatruc-2 kernel[0]: AICPUPMI: CPU C6-Cores [ 2 3 ]
Feb 11 12:49:42 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ 8 29 33 35 36 37 (38) 39 ]
Feb 11 12:49:43 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ 8 28 29 33 35 36 37 38 (39) ]
Feb 11 12:49:43 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 28 29 31 33 35 36 37 38 39 ]
Feb 11 12:49:44 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 27 28 29 31 33 35 36 37 38 39 ]
Feb 11 12:49:46 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 26 27 28 29 31 33 35 36 37 38 39 ]
Feb 11 12:49:53 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 26 27 28 29 31 33 34 35 36 37 38 39 ]
Feb 11 12:49:56 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 25 26 27 28 29 31 33 34 35 36 37 38 39 ]
Feb 11 12:50:01 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 25 26 27 28 29 31 32 33 34 35 36 37 38 39 ]
Feb 11 12:50:15 Barbatruc-2 kernel[0]: AICPUPMI: CPU C6-Cores [ 0 2 3 ]
Feb 11 12:50:20 Barbatruc-2 kernel[0]: AICPUPMI: CPU C6-Cores [ 0 1 2 3 ]
Feb 11 12:52:20 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 12:57:21 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ 8 21 25 26 27 28 29 30 31 32 33 34 (35) 36 37 38 39 ]
Feb 11 12:57:22 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ 8 15 21 25 26 27 28 29 30 31 32 33 34 35 36 37 38 (39) ]
Feb 11 12:57:22 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ 8 15 18 21 25 26 27 28 29 30 31 32 33 34 (35) 36 37 38 39 ]
Feb 11 12:57:23 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 15 17 18 21 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 12:57:24 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ 8 15 17 18 20 21 25 26 27 28 29 30 31 32 33 34 (35) 36 37 38 39 ]
Feb 11 12:57:24 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 14 15 17 18 20 21 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 12:57:26 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 14 15 17 18 20 21 22 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 12:57:27 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 14 15 16 17 18 20 21 22 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 12:57:32 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 13 14 15 16 17 18 20 21 22 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 12:57:33 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 12 13 14 15 16 17 18 20 21 22 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 12:57:38 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 12 13 14 15 16 17 18 20 21 22 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 12:57:39 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 12 13 14 15 16 17 18 19 20 21 22 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 12:57:59 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]
Feb 11 14:44:10 Barbatruc-2 kernel[0]: AICPUPMI: CPU P-States [ (8) 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 ]

captur31.png

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.



  • Similar Content

    • By frankiee
      Hi there, time for my first guide after asking so many things
       
      Updated for newer Clover versions and with additional instructions for more apps: gdisk and RU.
       
      So what may be overlooked sometimes in the whole boot loader discussion is the ability of UEFI to do more than just loading an OS. This is why I see ".efi" files as "apps" because in fact they just are, built on a special kind of API: UEFI. So, you can actually do stuff like editing, diagnosing, testing certain stuff at the lowest possible system level without booting to any OS.
       
      DISCLAIMER: Use this guide at your own risk! For educational purposes only! Should do not any harm, but remember you are dealing with rather low level stuff. But at least for me everything went flawless.
       
      Prerequisites:
      Working clover installation Clover Configurator or some app to edit the config.plist  
      1) Memtest
       
      This is how to install the UEFI version of Memtest with Clover:
      Download memtest, I used this link: Image for creating boot-able USB Drive Open the archive by double clicking on it. Mount the file memtest86-usb.img within by double clicking again. Now, you should see a folder named EFI in this volume, containing a folder BOOT. Open it. The files containing it are the actual app, in 32 and 64 bit versions. Think in almost all cases we want to use the 64 bit version. Now, mount your EFI partition, using Clover configurator. Create a folder named MemTest86 in the EFI folder on your main drive. Copy all files in the EFI/BOOT folder from the mounted image to your newly created folder. That ends the basic setup! Now, we add the correct Menu entry to the clover boot menu, so that we can actually start this app.
       
      Get into clover configurator, open your standard config.plist from your boot drive and go to the GUI section. Under "Custom Entries", add an entry like this:
       

       
      Please note while the path you enter is not case sensitive, you must make sure you use the backslash "\" for entering paths, and not a slash. So basically what we do is tell clover where it can find the app, give it a name, and tell clover it is a "Windows" app. Note: with older Clover versions we had to set this to "Linux", but for now "Windows" is the setting that works.
       
      If you prefer to do a manual config, add this entry to your config.plist, under GUI/Custom/Entries:
      <dict> <key>CustomLogo</key> <true/> <key>Disabled</key> <false/> <key>FullTitle</key> <string>MemTest86</string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>Image</key> <string>\EFI\CLOVER\themes\Icons\os_mint.png</string> <key>Path</key> <string>\EFI\MemTest86\BOOTX64.efi</string> <key>Type</key> <string>Windows</string> <key>VolumeType</key> <string>Internal</string> </dict> Now, save and reboot and you should see the newly created entry. Note that I also used a custom Icon - this is optional - in case you don't you will just see a generic windows icon instead:
       

       
      And this is how it looks like:
       

       

       
      PS: also noticeably faster and you get also more features with this version than with the older version, for example it does now write a log file. For more Information, see: http://www.passmark.com/forum/showthread.php?4315-Memtest86-Version-5-Beta-%28Pure-UEFI%29
       
       
      2) gdisk
       
      Another app you can use is the UEFI version of gdisk (aka GPT fdisk), which you can use to edit and change your partitions.
       
      Warning! Install and use this app at your own risk! If you do something wrong here you might nuke your drive(s), so only use that if you know what you are doing.
       
      This is how to do it (even easier):
      Download here: https://sourceforge.net/projects/gptfdisk/files/gptfdisk/1.0.1/gdisk-binaries/gdisk-efi-1.0.1.zip/download Mount your EFI partition Unzip the file and copy the resulting folder to your EFI Folder, so your path goes like this "/Volumes/EFI/EFI/gdisk-efi" Get into clover configurator, open your standard config.plist from your boot drive and go to the GUI section. Add an entry like this:  
      If you prefer to do a manual config, add this entry to your config.plist, under GUI/Custom/Entries:
      <dict> <key>CustomLogo</key> <false/> <key>Disabled</key> <false/> <key>FullTitle</key> <string>GDisk</string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>Image</key> <string></string> <key>Path</key> <string>\EFI\gdisk-efi\gdisk_x64.efi</string> <key>Type</key> <string>Windows</string> <key>VolumeType</key> <string>Internal</string> </dict> When everything went OK you should see this after selecting the respective entry in Clover:
       

       
       
      3) RU
       
      I recently found one more app that might be interesting to some, and thats "Read Universal" or in short "RU". This is a tool that enables you to debug your BIOS and read (and modify!) every imaginable data, including UEFI variables, ACPI Tables etc.
       
      Warning, again! I think blindly messing around with this app is even more dangerous, but on the other hand it gives you access to a lot of potentially interesting stuff.
      Download here: http://ruexe.blogspot.de/ The next steps are basically the same as above so make a folder in your EFI partition, copy the .EFI files and make another custom entry in your config.plist Here are some screens:
       

       

       

       
       
      So this is what you also can do with UEFI and clover. I am curious which other useful applications might exist!
       
      Anybody who knows, maybe post it here?
    • By TimNeumann
      MB: Asus X99 A-II
      RAM: G.Skill Ripjaws V F4-3200C16D-32GVK (3200MHz, 4x 16GB DIMMs, so Total 64GB) in quad-channel configuration.
      CPU: i7 6800k @4.0Ghz
      GPUs: GTX 1080 Ti and GTX 1060 3GB
      (each one a monitor, because I can't get DVI to run parallel with DP on the 1080Ti, and my second monitor only has DVI/VGA)
      OS: High Sierra 10.13.2 (17C88) / Clover revision: 4392
       
      Hello everybody,
      I occasionally have system crashes and suspect that it is related to RAM. However, this RAM is completely new, and a run with MemTest86+ from the USB stick showed no errors. However, if I use Memtest on MacOS, I get a bunch of error messages, but sometimes none (I restart the computer between tests).  
      As I just discovered, my RAM is not on the recommended vendor list of my motherboard, nor is it on the manufacturer side of the RAM. I have read several times that the RAM may not have been tested by the manufacturer on this platform. Not a single X99 motherboard is listed for this RAM.
      So I also suspect that my RAM is not compatible.
      But if that were the case, how could it sometimes work completely error-free?
       
      During RAM tests in summer 2017 (a slightly different setup, 4x8GB but still G.Skill Ripjaws V) I had no errors at Memtest under MacOS, if I remember correctly. At that time it ran under Sierra 10.12.6. AptioMemoryFix.efi could also cause problems.
      I am appreciative for any help!
       
      Here is an excerpt from a faulty test.
      It is noticeable that it is always the same address during the test, but a different one after each test.
      Memtest version 4.22 (64-bit) Copyright (C) 2004 Charles Cazabon Copyright (C) 2004-2008 Tony Scaminaci (Macintosh port) Licensed under the GNU General Public License version 2 only Mac OS X 10.13.2 (17C88) running in multiuser mode Memory Page Size: 4096 System has 12 Intel core(s) with SSE Requested memory: 57232MB (60012990464 bytes) Available memory: 57232MB (60012990464 bytes) Allocated memory: 57232MB (60012990464 bytes) at local address 0x00000001033e1000 Attempting memory lock... locked successfully Partitioning memory into 2 comparison buffers... Buffer A: 28616MB (30006495232 bytes) starts at local address 0x00000001033e1000 Buffer B: 28616MB (30006495232 bytes) starts at local address 0x00000007ffc4d800 Running 1 test sequence... (CTRL-C to quit) Test sequence 1 of 1: Running tests on full 57232MB region... Stuck Address : ok Linear PRN : testing 7 of 16 FAILURE! Data mismatch at local address 0x0000000e88133d30 Expected Data: 0xc4c340079ac9a645, Actual Data: 0xc4c3400788468846 Running comparison tests using 28616MB buffers... Random Value : ok Compare XOR : ok Compare SUB : ok Compare MUL : ok Compare DIV : ok Compare OR : ok Compare AND : ok Sequential Increment: ok Solid Bits : ok Block Sequential : testing 80 of 256 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x4f4f4f4f4f4f4f4f, BUFB Data: 0x4f4f4f4f88468846 Checkerboard : testing 3 of 64 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x5555555555555555, BUFB Data: 0x5555555588468846 Bit Spread : testing 1 of 128 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x0000000000000005, BUFB Data: 0x0000000088468846 Bit Flip : testing 74 of 512 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x0000000000000200, BUFB Data: 0x0000000088468846 Walking Ones : testing 40 of 128 Clover Files attached
      config.plist
      drivers64UEFI.zip
      kexts.zip
      ACPI.zip
    • By BurpSuite
      screenshot:
       

       
      description:
      github: https://github.com/burpsuite/clover_theme
    • By anka97
      Hello everyone! I'm a newbie !
       
      I tried to set up my USB installer, but I cannot. 
       
      Would u like to be so kind if u help me to setup my clover EFI partition. I'm stuck here and I cannot boot to USB.
       
      Everything is OK. Just about my Clover configuration! 
       
       
       
       
       
      My model profile:
       
       
      CPU : Intel Core i3 6100U Skylake-U/Y 
       
      RAM: 4.00GB Single-Channel DDR3 @ 532MHz (7-8-8-28)
       
      Motherboard: ASUSTeK COMPUTER INC. TP501UA (U3E1)
       
      Graphics: Intel HD Graphics 520 (ASUStek Computer Inc) 
       
      Monitor: Generic PnP Monitor (1920x1080@60Hz)                 
       
      Storage HDD: 465GB Seagate ST500LT012-1DG142 (SATA)
       
      Audio: Realtek
       
      Network: Qualcomm Atheros AR946x Wireless Network Adapter
×