[Guide] CustoMac 2013 | Z77X-UD5H | i7-3770K | GT 640 x2 | OS X 10.11

[jhhaze]

SPECS | Z77X-UD5H | i7-3770K | DUAL GT 640 | 16GB Memory | 250GB SSD

UniBeast 6.0 | Clover r3292 | OS X 10.11 El Cap

POST INSTALLATION
​

View attachment 157425

CloverALC
Finally, to get audio working. The full guide relating to this subject can be found here: http://www.tonymacx86.com/audio/143757-audio-realtek-alc-applehda-guide.html. First thing you want to do is download (Raw) audio_cloverALC-110.command.
View attachment 157971​

Great guide and thank you.

I have a very similar system ga-z77n-wifi, 3770k and I'm currently using HD4000, but, plan on adding a gtx 950. Thank you so much for posting your SSDT for the 3770k processor, Hopefully, someone can post an SSDT for the simple overclocking that you can done with this and my Mobo at say 4.2 or 4.3.

For what it's worth, I have the following questions and comments:

1) Following a different but similar guide I was instructed to install osxaptiofix2drv-64 instead of osxaptiofixdrv... as anyone know or tested the difference? Not sure is this is a small difference between the your mobo and my slightly different z77n-wifi mobo. I believe that when using the clover-uefi.pkg that tonymac has created it goes with the osxaptiofix2drv-64 if I remember correctly.

2) I understand that the 3770k using hd4000 and not hd4600 graphics. However, I read on a couple different posts that I should still select yes to the toleda script question "Enable 4600 HDMI audio" and then select yes to 3. I also ran a secondary toleda script that generated an SSDT to enable HDMI audio on 1 of the 2 hdmi ports. I did have to rename this ssdt to ssdt-1.aml, so that my power management ssdt could be named ssdt.aml. Any thoughts? The reasoning is that the toleda script is detecting the the audio kext and the gpu, so the default is yes to the questions, unless there is some kind of error. In an effort to streamline the script it says 4600 for both 4600 and 4000, instead of different lines for each. I know in version b, it said 4000, but now that we are up to version j, a chance has been made somewhere along the way.

3) In order to load the SSDT isn't there a option or options in clover config that you need to enable? Unless I missed it, I don't think I saw this step in your guide. Also, just to be sure, since the 3770k has native apple power management, are you saying that the ssdt is not even necessary and you will have the same speed steps with or without the ssdt or are speed steps and power management two different things all together?

4) I know while not necessary, some people still love their dsdt's. For this mobo you decided that it was not necessary or worth it to have a dsdt? The reason I ask it I believe the lack of dsdt's are causing some people usb 3.0 issues in el cap.

Thank you again for taking the time to prepare such and informative and helpful guide. Hopefully, my questions above will help the community.

Cheers!

 

[n3oNLit3]

Great guide and thank you.

I have a very similar system ga-z77n-wifi, 3770k and I'm currently using HD4000, but, plan on adding a gtx 950. Thank you so much for posting your SSDT for the 3770k processor, Hopefully, someone can post an SSDT for the simple overclocking that you can done with this and my Mobo at say 4.2 or 4.3.

For what it's worth, I have the following questions and comments:

1) Following a different but similar guide I was instructed to install osxaptiofix2drv-64 instead of osxaptiofixdrv... as anyone know or tested the difference? Not sure is this is a small difference between the your mobo and my slightly different z77n-wifi mobo. I believe that when using the clover-uefi.pkg that tonymac has created it goes with the osxaptiofix2drv-64 if I remember correctly.

OsxAptioFix2Drv-64 is simply a 2nd fix (option) for memory problems on UEFI firmware. One could alternatively also try OsxLowMemFixDrv-64 which is a simplified version of OsxAptioFixDrv. According to the Clover wiki "It is up to the user to decide which drivers are needed and which not." Which is not very helpful. I have always used OsxAptioFixDrv without issue. You are correct that the tonymacx86 UEFI pkg uses OsxAptioFix2Drv-64. It was found in testing that this option worked best for most systems across all 5-9 series boards

2) I understand that the 3770k using hd4000 and not hd4600 graphics. However, I read on a couple different posts that I should still select yes to the toleda script question "Enable 4600 HDMI audio" and then select yes to 3. I also ran a secondary toleda script that generated an SSDT to enable HDMI audio on 1 of the 2 hdmi ports. I did have to rename this ssdt to ssdt-1.aml, so that my power management ssdt could be named ssdt.aml. Any thoughts? The reasoning is that the toleda script is detecting the the audio kext and the gpu, so the default is yes to the questions, unless there is some kind of error. In an effort to streamline the script it says 4600 for both 4600 and 4000, instead of different lines for each. I know in version b, it said 4000, but now that we are up to version j, a chance has been made somewhere along the way.

You were correct in renaming you HDMI SSDT to SSDT-1.aml as PM SSDT should always be first. As far as the 4000 vs. 4600, I cant accurately speak to this. I will ask toleda and comment back, as well as update the guide if need be.

3) In order to load the SSDT isn't there a option or options in clover config that you need to enable? Unless I missed it, I don't think I saw this step in your guide. Also, just to be sure, since the 3770k has native apple power management, are you saying that the ssdt is not even necessary and you will have the same speed steps with or without the ssdt or are speed steps and power management two different things all together?

There are two ACPI tables that need to be dropped. Clover natively drops SSDT/CpuPm and Cpu0Ist. Clover adds the PM SSDT whether or not native tables have been dropped. For native PM, a processor specific PM SSDT is necessary. Without a PM SSDT you will not see all P-States available. For example prior to PM SSDT, AICPUPMI returned: CPU P-States [ (16) 24 31 35 36 ]. You can see my results post PM SSDT installation in Post #1. SpeedStep is an Intel term. They are used interchangeably throughout this and other sites - to mean the same thing

4) I know while not necessary, some people still love their dsdt's. For this mobo you decided that it was not necessary or worth it to have a dsdt? The reason I ask it I believe the lack of dsdt's are causing some people usb 3.0 issues in el cap.

A native DSDT has always had a needed. It is a Differentiated System Description Table held in your motherboards BIOS. Patch's to said DSDT are used to change/alter different aspects of your system. I have not patched my DSDT as I have native USB 3.0 working. I am looking into what giacomoleopardo posted earlier today with regards to getting the 2 non functioning USB 2.0 ports working.

Thank you again for taking the time to prepare such and informative and helpful guide. Hopefully, my questions above will help the community.

Cheers!

Thanks for the kind words and questions

 

[alex2tony]

If you set SMBIOS to MacPro3,1 you'll get your front USB2 working again.

 

[bulibasha75]

Long story short, I tried your guide today, everything went smooth and fast. No issues during install or after, USB and sound working great! (Btw, I have same motherboard and cpu as you + a GTX680 graphics card.)


Hi. Quick question . for gtx 680 video card When you install osx el capitan on usb flash drive, and you get to the screen where you have to check a box inject 3000 , inject nvidia inject intel ... do you check any of the boxes or leave it alone ?

 

[n3oNLit3]

If you set SMBIOS to MacPro3,1 you'll get your front USB2 working again.

That may be true, but MacPro 3,1 nowhere near matches the hardware, and is not recommended for proper PM

Long story short, I tried your guide today, everything went smooth and fast. No issues during install or after, USB and sound working great! (Btw, I have same motherboard and cpu as you + a GTX680 graphics card.)

Hi. Quick question . for gtx 680 video card When you install osx el capitan on usb flash drive, and you get to the screen where you have to check a box inject 3000 , inject nvidia inject intel ... do you check any of the boxes or leave it alone ?

No, as "Inject nvidia" is the same thing as Graphics Enabler=yes... Only needed for GPU's ≤ GT630

Edit**

---

If you wanted both Internal and Discrete for ≥ GT640 you would want to select "Inject Intel" as it is the same thing as IGPEnabler=yes

For GPU's ≤ GT630 to have both Internal and Discrete graphics, it would be "Inject Intel" and "Inject nvidia"

 

[bulibasha75]

That may be true, but MacPro 3,1 nowhere near matches the hardware, and is not recommended for proper PM



No, as "Inject nvidia" is the same thing as Graphics Enabler=yes... Only needed for GPU's ≤ GT630

Thank you n3oNLit3 .

 

[alex2tony]

That may be true, but MacPro 3,1 nowhere near matches the hardware, and is not recommended for proper PM


Here is my Geekbench with MacPro 3,1 and USB2 working properly. Can you compare to what you have?

thanks

 

[chadthman]

For getting the all the USB 2.0 ports working I found the fix by patching the info.plist in the AppleUSBEHCIPCI.kext. However I haven't had any luck yet getting all the USB 3.0 ports working yet. I use the smbios of iMac13,2 with no SSDT and I have full power management with all my p-states at an overclock of 4.2 Ghz.

In your config.plist in clover under the section:

<key>KextsToPatch</key>
<array>

paste this text and restart and you should be good to go:

<dict>
    <key>Comment</key>
    <string>USB 2.0</string>
    <key>Find</key>
    <data>RUhDMQ==</data>
    <key>InfoPlistPatch</key>
    <true/>
    <key>Name</key>
    <string>AppleUSBEHCIPCI</string>
    <key>Replace</key>
    <data>RUgwMQ==</data>
</dict>

 

[tallgeese04]

For getting the all the USB 2.0 ports working I found the fix by patching the info.plist in the AppleUSBEHCIPCI.kext. However I haven't had any luck yet getting all the USB 3.0 ports working yet. I use the smbios of iMac13,2 with no SSDT and I have full power management with all my p-states at an overclock of 4.2 Ghz.

How did you managed to overclock with iMac 13,2? When I tried it didn't work out so I returned to Mac Pro 3,1.
Thanks!

 

[chadthman]

Upon looking I guess I forgot I did this long ago but I am using an SSDT although being generated by Clover at startup.

In my config.plist:

<key>SSDT</key>
<dict>
    <key>C3Latency</key>
    <string>0xfa</string>
    <key>DropOem</key>
    <true/>
    <key>EnableC6</key>
    <true/>
    <key>Generate</key>
    <true/>
    <key>PLimitDict</key>
    <integer>0</integer>
    <key>PluginType</key>
    <integer>1</integer>
    <key>UnderVoltStep</key>
    <integer>0</integer>
</dict>

This gives me:

Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: v3.3 Copyright © 2012-2014 Pike R. Alpha. All rights reserved
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: logMSRs............................: 1
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: logIGPU............................: 0
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: logCStates.........................: 1
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: logIPGStyle........................: 1
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MWAIT C-States.....................: 4384
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_CORE_THREAD_COUNT......(0x35)  : 0x40008
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_PLATFORM_INFO..........(0xCE)  : 0x81010F0012300
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_PMG_CST_CONFIG_CONTROL.(0xE2)  : 0x1E000403
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_PMG_IO_CAPTURE_BASE....(0xE4)  : 0x10414
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: IA32_MPERF.................(0xE7)  : 0x100248D549
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: IA32_APERF.................(0xE8)  : 0xFB760988C
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_FLEX_RATIO.............(0x194) : 0xE0000
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_IA32_PERF_STATUS.......(0x198) : 0x21C900002300
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_IA32_PERF_CONTROL......(0x199) : 0x2300
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: IA32_CLOCK_MODULATION......(0x19A) : 0x0
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: IA32_THERM_STATUS..........(0x19C) : 0x88430000
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: IA32_MISC_ENABLES..........(0x1A0) : 0x850089
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_MISC_PWR_MGMT..........(0x1AA) : 0x400000
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x2A2A2A2A
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: IA32_ENERGY_PERF_BIAS......(0x1B0) : 0x0
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_POWER_CTL..............(0x1FC) : 0x14005F
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_RAPL_POWER_UNIT........(0x606) : 0xA1003
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_PKG_POWER_LIMIT........(0x610) : 0xA58000009F40
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_PKG_ENERGY_STATUS......(0x611) : 0x17C4CDC
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_PKGC3_IRTL.............(0x60a) : 0x883B
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_PKGC6_IRTL.............(0x60b) : 0x8850
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_PKGC7_IRTL.............(0x60c) : 0x8857
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_PP0_CURRENT_CONFIG.....(0x601) : 0x1814149400000960
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_PP0_POWER_LIMIT........(0x638) : 0xA580
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_PP0_ENERGY_STATUS......(0x639) : 0x1191441
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_PP0_POLICY.............(0x63a) : 0x0
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_CONFIG_TDP_NOMINAL.....(0x648) : 0x23
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_CONFIG_TDP_LEVEL1......(0x649) : 0x1E0000000000000
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_CONFIG_TDP_LEVEL2......(0x64a) : 0x1E0000000000000
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_CONFIG_TDP_CONTROL.....(0x64b) : 0x80000000
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_TURBO_ACTIVATION_RATIO.(0x64c) : 0x0
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_PKG_C2_RESIDENCY.......(0x60d) : 0x0
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_PKG_C3_RESIDENCY.......(0x3f8) : 0x0
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_PKG_C6_RESIDENCY.......(0x3f9) : 0x0
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: MSR_PKG_C7_RESIDENCY.......(0x3fa) : 0x0
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: CPU Low Frequency Mode.............: 1600 MHz
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: CPU Maximum non-Turbo Frequency....: 3500 MHz
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: CPU Maximum Turbo Frequency........: 4200 MHz
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: CPU P-States [ (35) 41 ]
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: CPU C6-Cores [ 2 3 5 6 ]
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: CPU P-States [ (16) 35 40 41 ]
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: CPU C6-Cores [ 2 3 5 6 7 ]
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: CPU P-States [ 16 34 (35) 40 41 ]
Nov  8 11:00:11 localhost kernel[0]: AICPUPMI: CPU C6-Cores [ 2 3 4 5 6 7 ]
Nov  8 11:00:12 Monolith kernel[0]: AICPUPMI: CPU P-States [ 16 34 35 37 40 41 ]
Nov  8 11:00:13 Monolith kernel[0]: AICPUPMI: CPU P-States [ 16 34 35 37 40 41 ]
Nov  8 11:00:13 Monolith kernel[0]: AICPUPMI: CPU P-States [ 16 34 35 37 40 41 ]
Nov  8 11:00:14 Monolith kernel[0]: AICPUPMI: CPU P-States [ 16 18 34 35 37 40 41 ]
Nov  8 11:00:14 Monolith kernel[0]: AICPUPMI: CPU P-States [ 16 18 31 34 35 37 40 41 ]
Nov  8 11:00:15 Monolith kernel[0]: AICPUPMI: CPU P-States [ 16 18 25 31 34 35 37 40 41 ]
Nov  8 11:00:15 Monolith kernel[0]: AICPUPMI: CPU C6-Cores [ 0 1 2 3 4 5 6 7 ]
Nov  8 11:00:16 Monolith kernel[0]: AICPUPMI: CPU P-States [ 16 18 25 31 34 35 37 40 41 ]
Nov  8 11:00:22 Monolith kernel[0]: AICPUPMI: CPU C3-Cores [ 6 7 ]
Nov  8 11:00:23 Monolith kernel[0]: AICPUPMI: CPU C3-Cores [ 4 6 7 ]
Nov  8 11:00:23 Monolith kernel[0]: AICPUPMI: CPU C3-Cores [ 0 2 3 4 6 7 ]
Nov  8 11:00:24 Monolith kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 6 7 ]
Nov  8 11:00:26 Monolith kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 5 6 7 ]
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: v3.3 Copyright © 2012-2014 Pike R. Alpha. All rights reserved
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: logMSRs............................: 1
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: logIGPU............................: 0
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: logCStates.........................: 1
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: logIPGStyle........................: 1
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MWAIT C-States.....................: 4384
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_CORE_THREAD_COUNT......(0x35)  : 0x40008
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_PLATFORM_INFO..........(0xCE)  : 0x81010F0012300
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_PMG_CST_CONFIG_CONTROL.(0xE2)  : 0x1E000403
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_PMG_IO_CAPTURE_BASE....(0xE4)  : 0x10414
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: IA32_MPERF.................(0xE7)  : 0xE8C1F1AC9
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: IA32_APERF.................(0xE8)  : 0xE41651E10
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_FLEX_RATIO.............(0x194) : 0xE0000
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_IA32_PERF_STATUS.......(0x198) : 0x21C900002300
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_IA32_PERF_CONTROL......(0x199) : 0x2300
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: IA32_CLOCK_MODULATION......(0x19A) : 0x0
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: IA32_THERM_STATUS..........(0x19C) : 0x88430000
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: IA32_MISC_ENABLES..........(0x1A0) : 0x850089
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_MISC_PWR_MGMT..........(0x1AA) : 0x400000
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x2A2A2A2A
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: IA32_ENERGY_PERF_BIAS......(0x1B0) : 0x0
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_POWER_CTL..............(0x1FC) : 0x14005F
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_RAPL_POWER_UNIT........(0x606) : 0xA1003
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_PKG_POWER_LIMIT........(0x610) : 0xA58000009F40
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_PKG_ENERGY_STATUS......(0x611) : 0x15D3B67
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_PKGC3_IRTL.............(0x60a) : 0x883B
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_PKGC6_IRTL.............(0x60b) : 0x8850
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_PKGC7_IRTL.............(0x60c) : 0x8857
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_PP0_CURRENT_CONFIG.....(0x601) : 0x1814149400000960
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_PP0_POWER_LIMIT........(0x638) : 0xA580
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_PP0_ENERGY_STATUS......(0x639) : 0x104868B
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_PP0_POLICY.............(0x63a) : 0x0
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_CONFIG_TDP_NOMINAL.....(0x648) : 0x23
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_CONFIG_TDP_LEVEL1......(0x649) : 0x1E0000000000000
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_CONFIG_TDP_LEVEL2......(0x64a) : 0x1E0000000000000
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_CONFIG_TDP_CONTROL.....(0x64b) : 0x80000000
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_TURBO_ACTIVATION_RATIO.(0x64c) : 0x0
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_PKG_C2_RESIDENCY.......(0x60d) : 0x0
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_PKG_C3_RESIDENCY.......(0x3f8) : 0x0
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_PKG_C6_RESIDENCY.......(0x3f9) : 0x0
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: MSR_PKG_C7_RESIDENCY.......(0x3fa) : 0x0
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: CPU Low Frequency Mode.............: 1600 MHz
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: CPU Maximum non-Turbo Frequency....: 3500 MHz
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: CPU Maximum Turbo Frequency........: 4200 MHz
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: CPU P-States [ 34 (35) ]
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: CPU C6-Cores [ 2 3 4 5 6 ]
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: CPU P-States [ 34 (35) 41 ]
Nov  8 11:07:42 localhost kernel[0]: AICPUPMI: CPU C6-Cores [ 2 3 4 5 6 7 ]
Nov  8 11:07:43 localhost kernel[0]: AICPUPMI: CPU P-States [ (16) 33 34 35 41 ]
Nov  8 11:07:43 Monolith kernel[0]: AICPUPMI: CPU P-States [ 16 33 34 35 39 41 (42) ]
Nov  8 11:07:44 Monolith kernel[0]: AICPUPMI: CPU C6-Cores [ 0 1 2 3 4 5 6 7 ]
Nov  8 11:07:44 Monolith kernel[0]: AICPUPMI: CPU C3-Cores [ 2 3 ]
Nov  8 11:07:45 Monolith kernel[0]: AICPUPMI: CPU P-States [ (16) 30 33 34 35 39 41 42 ]
Nov  8 11:07:45 Monolith kernel[0]: AICPUPMI: CPU C3-Cores [ 2 3 4 5 6 ]
Nov  8 11:07:45 Monolith kernel[0]: AICPUPMI: CPU P-States [ 16 24 30 33 34 35 39 41 (42) ]
Nov  8 11:07:45 Monolith kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 5 6 7 ]
Nov  8 11:07:46 Monolith kernel[0]: AICPUPMI: CPU P-States [ 16 24 30 33 34 35 37 39 41 (42) ]
Nov  8 11:07:46 Monolith kernel[0]: AICPUPMI: CPU P-States [ (16) 18 24 30 33 34 35 37 39 41 42 ]
Nov  8 11:07:47 Monolith kernel[0]: AICPUPMI: CPU P-States [ (16) 17 18 24 30 33 34 35 37 39 41 42 ]
Nov  8 11:07:49 Monolith kernel[0]: AICPUPMI: CPU P-States [ 16 17 18 24 30 33 34 35 37 39 40 41 (42) ]
Nov  8 11:07:49 Monolith kernel[0]: AICPUPMI: CPU P-States [ 16 17 18 24 30 33 34 35 37 38 39 40 41 (42) ]
Nov  8 11:07:53 Monolith kernel[0]: AICPUPMI: CPU P-States [ (16) 17 18 24 30 31 33 34 35 37 38 39 40 41 42 ]
Nov  8 11:07:54 Monolith kernel[0]: AICPUPMI: CPU P-States [ (16) 17 18 20 24 30 31 33 34 35 37 38 39 40 41 42 ]
Nov  8 11:07:55 Monolith kernel[0]: AICPUPMI: CPU P-States [ (16) 17 18 20 22 24 30 31 33 34 35 37 38 39 40 41 42 ]
Nov  8 11:07:55 Monolith kernel[0]: AICPUPMI: CPU P-States [ (16) 17 18 20 22 24 26 30 31 33 34 35 37 38 39 40 41 42 ]
Nov  8 11:07:56 Monolith kernel[0]: AICPUPMI: CPU P-States [ (16) 17 18 20 22 24 26 29 30 31 33 34 35 37 38 39 40 41 42 ]
Nov  8 11:08:47 Monolith kernel[0]: AICPUPMI: CPU P-States [ (16) 17 18 20 22 24 26 29 30 31 33 34 35 36 37 38 39 40 41 42 ]
Nov  8 11:09:16 Monolith kernel[0]: AICPUPMI: CPU P-States [ (16) 17 18 20 22 23 24 26 29 30 31 33 34 35 36 37 38 39 40 41 42 ]
Nov  8 11:09:20 Monolith kernel[0]: AICPUPMI: CPU P-States [ (16) 17 18 20 22 23 24 26 28 29 30 31 33 34 35 36 37 38 39 40 41 42 ]
Nov  8 11:09:42 Monolith kernel[0]: AICPUPMI: CPU P-States [ (16) 17 18 20 22 23 24 26 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 ]
Nov  8 11:09:58 Monolith kernel[0]: AICPUPMI: CPU P-States [ (16) 17 18 20 22 23 24 25 26 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 ]
Nov  8 11:10:07 Monolith kernel[0]: AICPUPMI: CPU P-States [ (16) 17 18 20 21 22 23 24 25 26 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 ]
Nov  8 11:10:39 Monolith kernel[0]: AICPUPMI: CPU P-States [ (16) 17 18 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 ]
Nov  8 11:13:03 Monolith 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 ]