Jump to content
stinga11

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

372 posts in this topic

Recommended Posts

@nmano - yep your kernel patch works fine here though I don't see an advantage using it vers. having Clover patch it on boot. Am I missing something?  Thanks

Clover config patched not test.

Remove-FakeCPUID-No

Remove-KernelHaswellE-No

Bios setting

Eiest-Disabled

post-413859-0-37875000-1471696903_thumb.png

Share this post


Link to post
Share on other sites
Advertisement

I had some stability issues with all Sierra DP versions on my setup (i7 5820k, ASUS X99/A 3.1). I patched the Kernel as per Pike's blog comments in:

 

XCPM for unsupported Processor…

 

Specifically the comment below:

To get a stable system, please read this blog article. I would start by disabling the 0x01A0 and 0x01AA MSR’s. You can do that by replace DC 33 00 00 with 00 00 00 00

I disabled the 0x01A0 and 0x01AA MSRs and system seems to be very stable. XCMP enabled, Geekbench score >27000 (3k more than El Capitan) overclocked @4.6 GHz.

 

On a side note: Apple Logic performance issues disappeared with DP6 (I had CPU spikes resulting in overloads with DP5).

Share this post


Link to post
Share on other sites

I had some stability issues with all Sierra DP versions on my setup (i7 5820k, ASUS X99/A 3.1). I patched the Kernel as per Pike's blog comments in:

 

XCPM for unsupported Processor…

 

Specifically the comment below:

To get a stable system, please read this blog article. I would start by disabling the 0x01A0 and 0x01AA MSR’s. You can do that by replace DC 33 00 00 with 00 00 00 00

I disabled the 0x01A0 and 0x01AA MSRs and system seems to be very stable. XCMP enabled, Geekbench score >27000 (3k more than El Capitan) overclocked @4.6 GHz.

 

On a side note: Apple Logic performance issues disappeared with DP6 (I had CPU spikes resulting in overloads with DP5).

 

did you solve the reboots with this patch completely?

 

First i thought this will solve my reboots, but they are back. Not so often, but there are unexpected reboots. 

 

Is this a ASUS board problem? 

 

Have other users this problems with Sierra? 

Share this post


Link to post
Share on other sites

I also tried with stock speed and it happens anyway :(

No issues with El Capitan and Yosemite @4.6.

On sunday I've been working all day long on a huge Project in apple logic with a high stress on CPU wih no issues. On monday morning it rebooted after 10 mins almost idle... checking again as Soon as I get Back home.

Share this post


Link to post
Share on other sites
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

 

AppleIntelInfo.kext v1.5 Copyright © 2012-2016 Pike R. Alpha. All rights reserved

 

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

post-413859-0-92999800-1472040544_thumb.png

Share this post


Link to post
Share on other sites

 

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

 

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

 

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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)?

Share this post


Link to post
Share on other sites

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 ]

Share this post


Link to post
Share on other sites

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)?

Share this post


Link to post
Share on other sites

^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

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 necros
      Hi all, new user here.
      I followed the shilohh guide i7-4930k-asus-rampage-iv-extreme-32gb-ram-gtx-770-4gb-success(and some other guides fresh installing) and everything works great but my cpu is flat at 1.2Mhz. 
      I tried every guide here, in olarila and in "others" but nothing works. Surely I'm doing something wrong but I cannot guess what it is. Also tried nullcpu etc..
      My specs are:
      Rampage IV Extreme
      i7 3930k
      Gtx 980
      Mac OS X 10.12.6
      I made my own SSDT too.
      C1E is enabled.
      I leave my Clover Folder here in case someone can shed some light because I'm starting to be desperate.
      Thank you in advance
      Cheers
       
      CLOVER.zip
    • By Gregow
      Updated to High Sierra and installed the latest webdrivers from nVidia. I'm using a MacPro6,1 SMBIOS so I need the agdpfix to avoid black screen issues.
       
      When booting with nv_disable=1 I get the "GeForceSensors: still waiting for accelerator..." message. Booting with the webdrivers seems to resolve that issue, but I'm booting into a black screen so that doesn't really help...
       
      Any ideas what could be causing this and how to fix it?
       
      My system:
       
      Asus X99-A
      5820K
      Asus STRIX 1080Ti
    • By Gregow
      Trying to run USB-installer I get this kernel panic:
      https://imgur.com/ir2yzhq
       
      Seems to me like it fails to mount the image, but what could be the cause of that?
       
      Any ideas?
       
       
       
    • By Gregow
      So, I haven't been running Hackintosh for a while but decided I wanted to give it new shot. I had previously ran an El Capitan installation, but wasn't all too happy with the performance. Figured I'd go at it again and not give up until it's working well.
       
      Anyhow, I made some bastardization of the old El Capitan  USB; latest version of Clover, Sierra install and copied the old El Cap config files (kexts, config.plist, SSDT and so on). As I don't remember everything clearly I tried to change as little as possible.
       
      It seems to have installed fine and the performance is a bit better than on El Capitan. So that's where I'm at now.
       
      I know that's not very detailed information, but I'll be happy to provide more if I just know what would be of interest/relevant.
       
      Running some benchmarks the performance is not great. Geekbench gives a decent single core performance but the multi-core is just around 20k (clocked at 4Ghz). Cinebench R15 seems a little better with 1180 points on CPU, but a little tired GPU score of 118 (GTX 970).
       
      I'm using the NullCPUPowerManagement.kext so I'm assuming the CPU runs at full power.
       
      Where do I begin troubleshooting? Any suggestions?
       
      My system specs:
       
      Asus X99-A motherboard
      i7 5820K @4Ghz
      2x8Gb RAM
      Asus GTX 970
    • By holyfield
      How about native speedstep on Sierra?
       
      Sierra does not support older firmware id's
       
      The Macs that will run macOS Sierra
      iMac – all models from late 2009, iMac 10,1 – 17,1 MacBook – all models from late 2009, MacBook  6,1 – 9,1 MacBook Pro – all models from 2010, MacBook Pro   7,1 – 11,5 MacBookAir – all models from 2010, MacBook Air  3,1 – 7,2 Mac Mini – all models from 2010, Mac Mini  4,1 – 7,1 Mac Pro – all models from 2010, Mac Pro  5,1 – 6,1   macOS Sierra won’t run on iMac 4,1 – 9,1 MacBook  1,1 – 5,1 MacBook Pro 1,1 – 5,2 MacBookAir 1,1 – 2,1 Mac Mini 1,1 – 3,1 Mac Pro  1,1 – 4,1 Xserve  1,1 – 3,1 Any ideas?
×