Haswell-E 5820k 5930k installation guide with full speedstep working

macandrea · August 23, 2016

Can you please share those settings? Thank you!

nmano · August 24, 2016

XCPM_idle fix 10.11.6by Pike R. Alpha
Find 20B9E20000000F30
Replace 20B9E20000009090

xcpm performance fix 1 (wrsmr fix to get CPU max) © okrasit
Find 89D8C1E008B99901
Replace B800FF0000B99901 

xcpm_bootstrap 10.11.6 Haswell-E © Pike R. Alpha
find 83C3BB83FB09
replace 83C3B883FB09

_cpuid_set_info 10.11.6 © Pike R. Alpha
find 5D7F288D48BB83F902
replace 5D7F288D48B883F902

XCPM Haswell-E 10.11.6

I tested patched Kernel.

Last login: Wed Aug 24 07:49:00 on console

manoranjansPro2:~ manoranjan$ sudo -s

Password:

bash-3.2# chown -R 0:0 ~/Desktop/AppleIntelInfo.kext

bash-3.2# chmod -R 755 ~/Desktop/AppleIntelInfo.kext

bash-3.2# kextload ~/Desktop/AppleIntelInfo.kext

bash-3.2# cat /tmp/AppleIntelInfo.dat

Settings:

------------------------------------

logMSRs............................: 1

logIGPU............................: 0

logCStates.........................: 1

logIPGStyle........................: 1

InitialTSC.........................: 0x68e95ccd2ce

MWAIT C-States.....................: 8480

Model Specific Registers

-----------------------------------

MSR_CORE_THREAD_COUNT......(0x35) : 0x80010

MSR_PLATFORM_INFO..........(0xCE) : 0x80C3BF3811E00

MSR_PMG_CST_CONFIG_CONTROL.(0xE2) : 0x3

MSR_PMG_IO_CAPTURE_BASE....(0xE4) : 0x0

IA32_MPERF.................(0xE7) : 0x2DF8AF7610

IA32_APERF.................(0xE8) : 0x40C04819BD

MSR_FLEX_RATIO.............(0x194) : 0xE0000

MSR_IA32_PERF_STATUS.......(0x198) : 0x280400002B00

MSR_IA32_PERF_CONTROL......(0x199) : 0xFF00

IA32_CLOCK_MODULATION......(0x19A) : 0x0

IA32_THERM_STATUS..........(0x19C) : 0x883C0000

IA32_MISC_ENABLES..........(0x1A0) : 0x850089

MSR_MISC_PWR_MGMT..........(0x1AA) : 0x400001

MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x2B2B2B2B2B2B2B2B

IA32_ENERGY_PERF_BIAS......(0x1B0) : 0x1

MSR_POWER_CTL..............(0x1FC) : 0x2104005B

MSR_RAPL_POWER_UNIT........(0x606) : 0xA0E03

MSR_PKG_POWER_LIMIT........(0x610) : 0x7FFD00014EA82

MSR_PKG_ENERGY_STATUS......(0x611) : 0xD2ECF62

MSR_PKG_POWER_INFO.........(0x614) : 0x1280460

MSR_PP0_POWER_LIMIT........(0x638) : 0x14FFD0

MSR_PP0_ENERGY_STATUS......(0x639) : 0x0

MSR_PKGC6_IRTL.............(0x60b) : 0x0

MSR_PKG_C2_RESIDENCY.......(0x60d) : 0xEB3F2A262A

MSR_PKG_C6_RESIDENCY.......(0x3f9) : 0x1377E809722

IA32_TSC_DEADLINE..........(0x6E0) : 0x68E9785E804

CPU Ratio Info:

------------------------------------

CPU Low Frequency Mode.............: 1200 MHz

CPU Maximum non-Turbo Frequency....: 3000 MHz

CPU Maximum Turbo Frequency........: 4300 MHz

CPU P-States [ 39 (43) ]

CPU C6-Cores [ 0 1 2 4 6 9 10 12 14 ]

CPU P-States [ 35 39 (43) ]

CPU C6-Cores [ 0 1 2 4 6 9 10 12 13 14 ]

CPU C6-Cores [ 0 1 2 4 6 8 9 10 12 13 14 ]

CPU P-States [ (12) 32 35 39 43 ]

CPU C6-Cores [ 0 1 2 4 5 6 8 9 10 12 13 14 ]

CPU P-States [ (12) 32 35 39 42 43 ]

CPU P-States [ (12) 32 35 37 39 42 43 ]

CPU P-States [ 12 32 33 35 37 39 42 (43) ]

CPU C6-Cores [ 0 1 2 3 4 5 6 8 9 10 11 12 13 14 ]

CPU C6-Cores [ 0 1 2 3 4 5 6 8 9 10 11 12 13 14 15 ]

CPU P-States [ 12 28 32 33 35 37 39 42 (43) ]

CPU P-States [ (12) 28 32 33 35 36 37 39 42 43 ]

CPU P-States [ 12 26 28 32 33 35 36 37 39 42 (43) ]

CPU P-States [ 12 26 28 32 33 34 35 36 37 39 42 (43) ]

CPU P-States [ (12) 26 28 29 32 33 34 35 36 37 39 42 43 ]

bash-3.2#

Thanks guys.

I need fix this

MSR_PMG_CST_CONFIG_CONTROL.(0xE2) : 0x3

MSR_PMG_IO_CAPTURE_BASE....(0xE4) : 0x0

get 15 bit MSR

kernel.zip

cmanns · August 26, 2016

Williams-Mac-Pro:~ cmanns$  sysctl machdep.xcpm
machdep.xcpm.io_filtered_reads: 0
machdep.xcpm.io_control_disengages: 1
machdep.xcpm.io_control_engages: 0
machdep.xcpm.io_thermal_level: 0
machdep.xcpm.gpu_thermal_level: 0
machdep.xcpm.cpu_thermal_level: 0
machdep.xcpm.deep_idle_total_stats: n/a
machdep.xcpm.deep_idle_last_stats: n/a
machdep.xcpm.deep_idle_count: 0
machdep.xcpm.qos_txfr: 1
machdep.xcpm.deep_idle_log: 0
machdep.xcpm.forced_idle_period: 30000000
machdep.xcpm.forced_idle_ratio: 100
machdep.xcpm.mbd_relaxations: 0
machdep.xcpm.mbd_applications: 0
machdep.xcpm.mbd_mode: 1
machdep.xcpm.maxintdelay: 0
machdep.xcpm.maxbusdelay: 0
machdep.xcpm.ratio_changes_total: 1404937
machdep.xcpm.vectors_loaded_count: 0
machdep.xcpm.tuib_ns: 0
machdep.xcpm.bootpst: 42
machdep.xcpm.bootplim: 0
machdep.xcpm.power_source: 0
machdep.xcpm.tuib_enabled: 0
machdep.xcpm.tuib_plimit_min_100mhz_ratio: 8
machdep.xcpm.tuib_plimit_max_100mhz_ratio: 42
machdep.xcpm.soft_plimit_min_100mhz_ratio: 8
machdep.xcpm.soft_plimit_max_100mhz_ratio: 42
machdep.xcpm.hard_plimit_min_100mhz_ratio: 8
machdep.xcpm.hard_plimit_max_100mhz_ratio: 42
machdep.xcpm.mode: 1
Williams-Mac-Pro:~ cmanns$ kextstat -l | grep -y applelpc
Williams-Mac-Pro:~ cmanns$ kextstat -l | grep -y x86plat
   77    1 0xffffff7f8202d000 0x17000    0x17000    com.apple.driver.X86PlatformPlugin (1.0.0) 737E5937-A52E-32C0-A6C2-4C026B96848C <76 75 45 42 11 7 6 5 4 3 1>
  103    1 0xffffff7f828e7000 0x7000     0x7000     com.apple.driver.X86PlatformShim (1.0.0) 60DA68BB-E888-37A1-BCA6-9930A920A266 <77 76 75 7 4 3>
Williams-Mac-Pro:~ cmanns$ kextstat -l | grep -y acpiplat
   13    2 0xffffff7f81ea6000 0x60000    0x60000    com.apple.driver.AppleACPIPlatform (5.0) D748FA50-380C-3F0D-BAD9-EB7A15848EA8 <12 11 7 6 5 4 3 1>

I rarely get x419 in hw monitor max mult is x43 in bios

During Geekbench 4 beta it wont flatline much, constantly hangs around x18/x30 and never goes lower during idle like on El Capitan it stayed at x12 to x18 mostly under moderate workloads with low cpu %.

This is on sierra

maleorderbride · August 26, 2016

Can anyone provide information on using Coderush's UEFI Patch to unlock the 0xE2 MSR on ASUS X99 boards? I am not seeing a link to it, or patch information.

Per Pike's hints, it seems as if that is what lies behind the random reboots. While we could continue to accrue OS version specific kernel patches in Clover, it seems best to address the fundamental problem.

AsusFreak · August 27, 2016

ASUS X99 aren't locked. If they were you could still patch in Clover:

        <key>AsusAICPUPM</key>
        <true/>

maleorderbride · August 27, 2016

ASUS X99 aren't locked. If they were you could still patch in Clover:
        <key>AsusAICPUPM</key>
        <true/>

What is your support for this statement?

This is the output I get from Clover on both X99 Deluxe and an X99-A USB 3.1:

0:104 0:000 MSR 0xE2 before patch 00008400

0:104 0:000 MSR 0xE2 is locked, PM patches will be turned on

0:104 0:000 MSR 0xE4 00010414

0:104 0:000 MSR 0xCE 20080C3B_F3811E00

0:104 0:000 MSR 0x1B0 00000000

Does that not mean that 0xE2 is locked?

Furthermore, Pike claims that his ASUS X99-E has a locked MSRs in the comments of his blog: https://pikeralpha.wordpress.com/2016/07/26/xcpm-for-unsupported-processor/#comments

A locked MSR, accordingly to Pike, can lead to sudden reboots when the OS attempts to write to the MSR, hence his advice (and kernel patches) which disable writing to select MSRs.

I am not certain that Clover truly is unlocking that MSR, but it does not seem to also be unlocking other MSRs that the OS might try to write to, such as MSR 0x1aa or MSR 0x1a0

Edit: Thanks for challenging me on that! (but you are wrong ;p)

That led to me noticing dgsga's comment that provides instructions:

"PpmInitialize Dxe unlocks the MSR 0xE2 on Asus X99 boards. Extract the body of the module using UEFITool, patch in Hexedit then replace with UEFITool. Flash the modded bios by renaming the bios file to the name appropriate for your board (for my X99M-WS it’s X99MWS.CAP) then flash using USB Flashback (bios file on FAT32 stick plugged into your rear white USB port, press and hold USB flashback button next to it until light starts flashing."

Edit #2: So it appears that the unlocking procedure for 0xE2 differs depending upon if you are Haswell-E/P or Broadwell-E/P.

For Haswell: (take from realFlow's comment)

-downgrade your BIOS to a lower version than the latest (3101)

-patch the latest BIOS (3301) with CodeRushs UEFIPatch:https://github.com/LongSoft/UEFITool/releases/tag/0.21.5

Note: thanks to Piker CodeRush updated the containing patches.txt. You have to exchange the file with the latest one in GitHub

Command to patch: UEFIPatch.exe

-copy the resulting file with the name X99AU31.CAP (important!) on an usb stick (fat format) and plug it in the Flashback usb port, which is outlined green

-press the flashback button a couple of seconds until it starts blinking and wait until it stops

-config your bios, which will be reseted during the procedure….

Broadwell either requires the updated patches.txt, or perhaps manually patching as in my Edit #1.

AsusFreak · August 27, 2016

No worries, I've been wrong before. Asus stopped locking MSR with the Z87 chipset and I've never done a X99 build with anything but Gigabyte so maybe there's a surprise here... I haven't seen a Asus X99 post anywhere stating that MSR was locked... Throw out all Pikes patches, load null and show me one ounce of difference in GB scores, sleep/wake or anything else, there isn't any... (Random reboots will probably stop as well). I'm not looking for an argument here so please continue on the path you're on, I don't have a horse in the race. IMO, X99 issues will get resolved only if/when Apple decides to support it... Surely there's more to running X99 correctly in OSX than Pikes XCPM patches.

maleorderbride · August 27, 2016

No worries, I've been wrong before. Asus stopped locking MSR with the Z87 chipset and I've never done a X99 build with anything but Gigabyte so maybe there's a surprise here... I haven't seen a Asus X99 post anywhere stating that MSR was locked... Throw out all Pikes patches, load null and show me one ounce of difference in GB scores, sleep/wake or anything else, there isn't any... (Random reboots will probably stop as well). I'm not looking for an argument here so please continue on the path you're on, I don't have a horse in the race. IMO, X99 issues will get resolved only if/when Apple decides to support it... Surely there's more to running X99 correctly in OSX than Pikes XCPM patches.

Starting with 10.10 my ASUS X99 builds started having a random reboot problem (with Null). It lessened in 10.11, but still remains. I just want to track that down. I am not interested in looking for problems, just solutions! (FYI, most GB X99 boards have E2 unlocked)

Performance-wise, I have been getting very close to the same performance Pike does for quite some time now without using XCPM, so I mostly agree with you there. I am only venturing into XCPM to try to stop the reboots.

Yes, I wish Apple would hurry the hell up and release the MacPro7,1 so we could just get this {censored} working without so many messy hacks ;(

On a side note, I am not convinced that the clover AsusAICPUPM or KernelPM do anything for Haswell-E/P or Broadwell-E/P. Even back in SB-E there are documented instances on here of X79 CPU related problems that Clover does not solve.

13parsecs · August 28, 2016

No worries, I've been wrong before. Asus stopped locking MSR with the Z87 chipset and I've never done a X99 build with anything but Gigabyte so maybe there's a surprise here... I haven't seen a Asus X99 post anywhere stating that MSR was locked... Throw out all Pikes patches, load null and show me one ounce of difference in GB scores, sleep/wake or anything else, there isn't any... (Random reboots will probably stop as well). I'm not looking for an argument here so please continue on the path you're on, I don't have a horse in the race. IMO, X99 issues will get resolved only if/when Apple decides to support it... Surely there's more to running X99 correctly in OSX than Pikes XCPM patches.

the *other* variable is that Pike uses his own bootloader - RevoBoot...?

Know any revoboot guides for us mortals? (ie non programmers)?

maleorderbride · August 28, 2016

I unlocked the MSR and re-flashed my BIOS. We shall see if I get any more random restarts. If so, then I will see if I can block some other MSRs from writing with kernel patches.

VoodooTSCSync is no longer needed to wake from sleep after flashing, and you will notice that the Initial TSC and TSC Deadline changes with this BIOS modification.

If you would like to do this then you need to use CodeRush's utility: https://github.com/L...ases/tag/0.21.5

It requires this added line in the Patch.txt:

# PpmInitialize | Broadwell-E

3FFCAE95-23CF-4967-94F5-16352F68E43B 10 P:0FBA6C24400F:0FBA7424400F

Current CPU BIOS settings;

Sync All Cores: Auto

C-States: Enabled

C3 & C6 Reporting: Enabled

Package C-State Limit: C6 (Retention)

Current AppleIntelInfo output: https://github.com/Piker-Alpha/AppleIntelInfo

sudo chown -R 0:0 ~/Desktop/AppleIntelInfo.kext

sudo chmod -R 755 ~/Desktop/AppleIntelInfo.kext

sudo kextload ~/Desktop/AppleIntelInfo.kext

sudo cat /tmp/AppleIntelInfo.dat

MSR_PMG_CST_CONFIG_CONTROL.(0xE2) is the line that will change after flashing (from 8400->400), then change C-State BIOS settings to get 403 & C2 & C6 Residency to be a non-zero output.

logMSRs............................: 1
logIGPU............................: 0
logCStates.........................: 1
logIPGStyle........................: 1
InitialTSC.........................: 0x5414ab6e377
MWAIT C-States.....................: 8480

Model Specific Registers
-----------------------------------
MSR_CORE_THREAD_COUNT......(0x35)  : 0xE001C
MSR_PLATFORM_INFO..........(0xCE)  : 0x20080C33FB811B00
MSR_PMG_CST_CONFIG_CONTROL.(0xE2)  : 0x403
MSR_PMG_IO_CAPTURE_BASE....(0xE4)  : 0x10414
IA32_MPERF.................(0xE7)  : 0x26AC73FAA6
IA32_APERF.................(0xE8)  : 0x2241F1B173
MSR_FLEX_RATIO.............(0x194) : 0x0
MSR_IA32_PERF_STATUS.......(0x198) : 0x1E2100001B00
MSR_IA32_PERF_CONTROL......(0x199) : 0xFF00
IA32_CLOCK_MODULATION......(0x19A) : 0x0
IA32_THERM_STATUS..........(0x19C) : 0x88370000
IA32_MISC_ENABLES..........(0x1A0) : 0x850089
MSR_MISC_PWR_MGMT..........(0x1AA) : 0x400000
MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x2323232323232323
IA32_ENERGY_PERF_BIAS......(0x1B0) : 0x0
MSR_POWER_CTL..............(0x1FC) : 0x2904005B
MSR_RAPL_POWER_UNIT........(0x606) : 0xA0E03
MSR_PKG_POWER_LIMIT........(0x610) : 0x7857000158488
MSR_PKG_ENERGY_STATUS......(0x611) : 0x4BAA69D
MSR_PKG_POWER_INFO.........(0x614) : 0x2F091003200488
MSR_PP0_POWER_LIMIT........(0x638) : 0x0
MSR_PP0_ENERGY_STATUS......(0x639) : 0x0
MSR_PKGC6_IRTL.............(0x60b) : 0x0
MSR_PKG_C2_RESIDENCY.......(0x60d) : 0x4F4112354
MSR_PKG_C6_RESIDENCY.......(0x3f9) : 0x16B8D6453C
IA32_TSC_DEADLINE..........(0x6E0) : 0x541552FE0D1

CPU Ratio Info:
------------------------------------
CPU Low Frequency Mode.............: 1200 MHz
CPU Maximum non-Turbo Frequency....: 2700 MHz
CPU Maximum Turbo Frequency........: 3500 MHz
CPU P-States [ (12) 24 35 ]
CPU C6-Cores [ 0 3 4 6 10 12 14 ]
CPU P-States [ 12 24 26 (35) ]
CPU C6-Cores [ 0 1 3 4 5 6 9 10 12 14 ]
CPU P-States [ (12) 23 24 26 35 ]
CPU C6-Cores [ 0 1 3 4 5 6 9 10 11 12 13 14 16 ]

macandrea · August 29, 2016

Hi,

I've tried nearly all settings and patched BIOS, but the system occasionally reboots. Strange thing is:

- sometimes system is stable for the whole day

- sometimes the system reboots after a few minutes (<5) after login

If random reboot does not take place within 5 minutes, the system is (very) stable - I've left it on for more than one day without any issue...

@SammierG: is your system ok or are you experiencing reboots after your changes? If no reboots, can you please share your BIOS settings (the AUTO options you set manually mentioned in your post)?

cmanns · August 29, 2016

^I maybe face what you do

Sometimes I boot up hack and it reboots before I login

Otherwise it's stable all day, when I was first configuring this X99 hack with 10.11/10.12 I saw some reboots while in the OS doing things quite alarming. Since fresh installs with better clover/EFI/etc I notice this so rare yet to see it as I'm using it.

*keeps eyes peeled for fix* I'm on 3005 bios

macandrea · August 29, 2016

I've just installed the new 10.12 Beta (16A313a). Let's see if we get some kind of improvement. I'm using 3301 patched BIOS.

cmanns · August 30, 2016

Guys how do I name my i7 5820k properly to run intel gadget ?

cmanns · August 30, 2016

I've just installed the new 10.12 Beta (16A313a). Let's see if we get some kind of improvement. I'm using 3301 patched BIOS.

mind sharing that BIOS / link to method of patching?

Have X99-A/USB3.1 I'll stick on 3005 a bit more though, so far DP7/DP8 seem entirely reboot free though I faced this so rarely not sure how else to trigger, abunch of reboots?

macandrea · August 30, 2016

the procedure I've followed to patch the BIOS is the one in #293 , exactly the same procedure explained in the realFlow commentson Piker's blog.

cmanns · August 30, 2016

the procedure I've followed to patch the BIOS is the one in #293 , exactly the same procedure explained in the realFlow commentson Piker's blog.

Thanks, noted that post.

I wonder if my BIOS ver is less affected by random reboots.

ekwipt · August 31, 2016

I've tried to patch via kernel using maleorderbride methods on post #190, to no avail

Motherboard: Gigabyte-X99P-SLI

Cpu - Broadwell-E 6800k

I copied 4 patches straight from the comments section in PikerAlpha blogpost:

xcpm_bootstrap (OS X 10.11.6)

find…: 83C3BB83FB09
replace: 83C3B383FB09

cpuid_set_info (OS X 10.11.6)

find…: 5D7F288D48BB83F902
replace: 5D7F288D48B383F902

You may also need to patch _xcpm_idle (see patches in blog article):

find…: 300f000000e2b920
replace: 9090000000e2b920

PikerAlpha also talks about the byte order maybe being different in clover (is it???)

FakeCPUID - 0x0306a0

Apple RTC, KernelPM and KernelHaswellE checked in Clover

Deleted: NullCPUPowerManagement, VoodooTSCSync kexts out of kexts folder

Deleted patched SSDT.aml (in case it was causing me conflicts)

Ran FrequencyVectorEdit.sh (not i'm not sure i did this properly) but it says on Pikeralphas blog that it

Note: What this update does that the previous versions didn’t do is that it checks for the FrequencyVectors array, and it will add it when it is missing.

Ran the MacPro 6.1 plist [ 25 ] Mac-F60DEB81FF30ACF6.plist (MacPro6,1)

and got the following screenshot:

and after all that i'm getting kernel panics (com.apple.driver.AppleIntelCPUPower-Management)

SammlerG · August 31, 2016

0x306A0 is IvyBridge.

This is not working with xcpm! To use 0x306A0 you need NullCPUpm kext

If you read the blogs and posts, then you should know: don´t use FakeCPUID for IvyBridge CPU with this patches.

Working FakeCPUID for 10.12 xcpm has changed.

maleorderbride · August 31, 2016

I've tried to patch via kernel using maleorderbride methods on post #190, to no avail

FakeCPUID - 0x0306a0

Apple RTC, KernelPM and KernelHaswellE checked in Clover

You should not be using any FakeCPUID. You also do not need any of those Clover patches enabled assuming you are in El Capitan.

Since you do not have your signature filled out, I am not sure if you are using a Haswell-E or Broadwell-E CPU. That might be good info to provide.

ekwipt · August 31, 2016

0x306A0 is IvyBridge.

This is not working with xcpm! To use 0x306A0 you need NullCPUpm kext

If you read the blogs and posts, then you should know: don´t use FakeCPUID for IvyBridge CPU with this patches.

Working FakeCPUID for 10.12 xcpm has changed.

You should not be using any FakeCPUID. You also do not need any of those Clover patches enabled assuming you are in El Capitan.

Since you do not have your signature filled out, I am not sure if you are using a Haswell-E or Broadwell-E CPU. That might be good info to provide.

Sorry guys have filled in my signature, I also did mention what CPU i was using at start of my post. I've tried to delete the fakecpuid and unticking the flags but now faced with the following screen.

maleorderbride · August 31, 2016

Sorry, I have a Haswell-E CPU. I have not tried this on Broadwell-EP.

grunge888 · September 1, 2016

Hi everyone,

It seems my 5820k with xcpm run way better with the patch and I wanted to run a test with intel gadget but I cannot have the power consumption in the graph.

Any idea why ?

the command sysctl machdep.xcpm seems to say that's everything is good ?

machdep.xcpm.io_filtered_reads: 0

machdep.xcpm.io_control_disengages: 1

machdep.xcpm.io_control_engages: 0

machdep.xcpm.io_thermal_level: 0

machdep.xcpm.gpu_thermal_level: 0

machdep.xcpm.cpu_thermal_level: 0

machdep.xcpm.deep_idle_total_stats: n/a

machdep.xcpm.deep_idle_last_stats: n/a

machdep.xcpm.deep_idle_count: 0

machdep.xcpm.qos_txfr: 1

machdep.xcpm.deep_idle_log: 0

machdep.xcpm.forced_idle_period: 30000000

machdep.xcpm.forced_idle_ratio: 100

machdep.xcpm.mbd_relaxations: 0

machdep.xcpm.mbd_applications: 0

machdep.xcpm.mbd_mode: 1

machdep.xcpm.maxintdelay: 0

machdep.xcpm.maxbusdelay: 0

machdep.xcpm.ratio_changes_total: 50140

machdep.xcpm.ratio_change_ratelimit_ns: 500000

machdep.xcpm.vectors_loaded_count: 1

machdep.xcpm.tuib_ns: 0

machdep.xcpm.bootpst: 36

machdep.xcpm.bootplim: 0

machdep.xcpm.power_source: 0

machdep.xcpm.tuib_enabled: 0

machdep.xcpm.tuib_plimit_min_100mhz_ratio: 8

machdep.xcpm.tuib_plimit_max_100mhz_ratio: 36

machdep.xcpm.soft_plimit_min_100mhz_ratio: 8

machdep.xcpm.soft_plimit_max_100mhz_ratio: 36

machdep.xcpm.hard_plimit_min_100mhz_ratio: 8

machdep.xcpm.hard_plimit_max_100mhz_ratio: 36

machdep.xcpm.mode: 1

Thanks for your help.

ergot · September 1, 2016

For me its look like this:

first pic is with patch and NullCPU and Voodoo in 10.12 folder

Second pic without NullCPU and voodoo kexts

Is this make any difference?

maleorderbride · September 1, 2016

Ergot, if you are using the method I wrote out, then you are not using AICPUPM, so Null is doing nothing. You can keep it removed.

If you also unlocked the MSR, then you do not need VoodooTSCSync to wake from sleep (VodooTSCSync has not been necessary to boot since 10.10.3).

I have not been using my other build lately, but if anyone wants to test the following patches to kernel in 10.11.6, then feel free. Please let me know if it helps with their reboots. I could not have found what to patch without Pike, of course.

Keep whatever patches you currently have, but just add these to them.

**I have not tested these yet, no idea if they really work or cause any problems. Have a way to recover if this renders your install unbootable.**

		<key>KernelToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>nop MSR #1</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>3hcAAAAAAA==</data>
				<key>Replace</key>
				<data>AAAAAAAAAA==</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>nop MSR #2</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>3BMAAAAAAA==</data>
				<key>Replace</key>
				<data>AAAAAAAAAA==</data>
			</dict>
		</array>

Haswell-E 5820k 5930k installation guide with full speedstep working

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites