[Guide] Mac OSX 10.12 and 10.13 with X99 Broadwell-E family and Haswell-E family

[Fergarth]

Yep ?

Not test yet if it applies only in Kernel to Patch or in Kext to Patch too.

[k1n4]

I can confirm - Clover 3994 has serious bug. I returned to older version of Clover from 3994 and now everything is just fine again on 10.12.3 - but on boot system writing XCPM: registered instead of IOPPF: XCPM mode also I have problems to load freq vectors again... damnt on 10.12.2 was everything awesome... 5820K.

 

If someone has still 10.12.2 installation file I will be very happy if someone can post link to download because I can´t find any source on web.

I've got an headquake too testing xcpm power management on my machine; the vector count doesn't load for this reason.

I've an SSD as backup. What install file do you want bro?

 

 

Inviato dal mio iPhone utilizzando Tapatalk

[mfc88]

Recommended list of CPUs/Vectors:

Sandy Bridge System Definitions: 
Mac-942B5BF58194151B:iMac12,1
Mac-942B59F58194171B:iMac12,2
Mac-8ED6AF5B48C039E1:Macmini5,1
Mac-4BC72D62AD45599E:Macmini5,2
Mac-7BA5B2794B2CDB12:Macmini5,3
Mac-94245B3640C91C81:MacBookPro8,1
Mac-94245A3940C91C80:MacBookPro8,2
Mac-942459F5819B171B:MacBookPro8,3
Mac-C08A6BB70A942AC2:MacBookAir4,1
Mac-742912EFDBEE19B3:MacBookAir4,2

Sandy Bridge CPUs
i7-2700K
i7-2600K
i7-2600
i7-2600S
i5-2300
i5-2310
i5-2320
i5-2380P
i5-2390T
i5-2400S
i5-2405S
i5-2400
i5-2450P
i5-2500T
i5-2500S
i5-2500
i5-2500K
i5-2550K
i3-2130
i3-2125
i3-2120T
i3-2120
i3-2115C
i3-2105
i3-2102
i3-2100T
i3-2100

Sandy Bridge E

i7-3970X
i7-3960X
i7-3930K
i7-3820 

Ivy Bridge System Definitions: 
Mac-00BE6ED71E35EB86:iMac13,1
Mac-FC02E91DDD3FA6A4:iMac13,2
Mac-031AEE4D24BFF0B1:Macmini6,1
Mac-F65AE981FFA204ED:Macmini6,2
Mac-4B7AC7E43945597E:MacBookPro9,1
Mac-6F01561E16C75D06:MacBookPro9,2
Mac-C3EC7CD22292981F:MacBookPro10,1
Mac-AFD8A9D944EA4843:MacBookPro10,2
Mac-66F35F19FE2A0D05:MacBookAir5,1
Mac-2E6FAB96566FE58C:MacBookAir5,2
Mac-F60DEB81FF30ACF6:MacPro6,1

Ivy Bridge CPUs
i7-3770
i7-3770K
i7-3770S
i7-3770T
i5-3570T
i5-3570K
i5-3570S
i5-3570
i5-3550S
i5-3550
i5-3475S
i5-3470S
i5-3470
i5-3470T
i5-3450S
i5-3450
i5-3350P
i5-3330S
i5-3333S
i5-3330S
i5-3330
i3-3250
i3-3250T
i3-3245
i3-3240
i3-3240T
i3-3225
i3-3220
i3-3220T
i3-3210

Ivy Bridge E
i7-4960X
i7-4930K
i7-4820K


Haswell System Definitions:
Mac-031B6874CF7F642A:iMac14,1
Mac-27ADBB7B4CEE8E61:iMac14,2
Mac-77EB7D7DAF985301:iMac14,3
Mac-81E3E92DD6088272:iMac14,4

Intel Core i5-4690 @ 3.50 GHz
Mac-42FD25EABCABB274:iMac15,1
Intel Core i7-4790K @ 4.0 GHz
Mac-FA842E06C61E91C5:iMac15,1

Mac-189A3D4F975D5FFC:MacBookPro11,1
Mac-3CBD00234E554E41:MacBookPro11,2
Mac-2BD1B31983FE1663:MacBookPro11,3
Mac-06F11FD93F0323C5:MacBookPro11,4
Mac-06F11F11946D27C5:MacBookPro11,5
Mac-35C1E88140C3E6CF:MacBookAir6,1
Mac-7DF21CB3ED6977E5:MacBookAir6,2
Mac-F60DEB81FF30ACF6:MacPro6,1
Mac-35C5E08120C7EEAF:Macmini7,1

Haswell
i7-4770K
i7-4790
i5-4690K
i7-4790K
i5-4430S
i7-4771
i7-4770
i5-4590K
i5-4590
i5-4670K
i5-4670
i5-4570
i5-4440
i5-4440S
i5-4430
i7-4790S
i7-4790T
i7-4785T
i7-4770R
i7-4770S
i7-4770T
i7-4765T
i5-4670R
i5-4690
i5-4690S
i5-4690T
i5-4670S
i5-4670T
i5-4590
i5-4590S
i5-4590T
i5-4570S
i5-4570T
i5-4570TE
i5-4460
i5-4460T
i5-4460S
i3-4130
i3-4130T
i3-4150
i3-4150T
i3-4160
i3-4160T
i3-4330
i3-4330T
i3-4330TE
i3-4340
i3-4340TE
i3-4350
i3-4350T
i3-4360
i3-4360T
i3-4370

Haswell E
i7-5960X
i7-5930K
i7-5820K


Broadwell System Definitions:
Mac-9F18E312C5C2BF0B:MacBookAir7,1
Mac-937CB26E2E02BB01:MacBookAir7,2
Mac-E43C1C25D4880AD6:MacBookPro12,1

Non-Retina 21.5-inch, Intel Core i5-5250U @ 1.60 GHz 
Mac-A369DDC4E67F1C45:iMac16,1
Non-Retina 21.5-inch, Intel Core i5-5575R @ 2.80 GHz 
Mac-FFE5EF870D7BA81A:iMac16,2
Retina 4K, 21.5-inch, Intel Core i5-5675R 3.1GHz 
Mac-FFE5EF870D7BA81A:iMac16,2
Retina 4K, 21.5-inch, Intel Core i7-5775R @ 3.30 GHz 
Mac-FFE5EF870D7BA81A:iMac16,2

Broadwell
i7-5775R
i7-5775C
i5-5675R
i5-5675C
i5-5575R

Skylake System Definitions:
Retina 5K, 27-inch, Intel Core i7-6700K 4.0GHz
Mac-65CE76090165799A:iMac17,1
Retina 5K, 27-inch, Intel Core i5-6600 3.3GHz
Mac-B809C3757DA9BB8D:iMac17,1
Retina 5K, 27-inch, Intel Core i5-6500 3.2GHz
Mac-DB15BD556843C820:iMac17,1

Skylake
i7-6700T
i7-6700K 
i7-6700 
i5-6600T 
i5-6600K 
i5-6600 
i5-6500T 
i5-6500 
i5-6400T
i5-6400 
i3-6320 
i3-6300T 
i3-6300 
i3-6100T
i3-6100

AppleIntelInfo output:

AppleIntelInfo.kext v2.0 Copyright © 2012-2016 Pike R. Alpha. All rights reserved
enableHWP................................: 0

Settings:
------------------------------------------
logMSRs..................................: 1
logIGPU..................................: 0
logCStates...............................: 1
logIPGStyle..............................: 1
InitialTSC...............................: 0x10d0f63859f2 (528 MHz)
MWAIT C-States...........................: 8480

Processor Brandstring....................: Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz

Processor Signature..................... : 0x306F2
------------------------------------------
 - Family............................... : 6
 - Stepping............................. : 2
 - Model................................ : 0x3F (63)

Model Specific Registers (MSRs)
------------------------------------------

MSR_CORE_THREAD_COUNT............(0x35)  : 0xFFFFFF804C366500
------------------------------------------
 - Core Count........................... : 6
 - Thread Count......................... : 12

MSR_PLATFORM_INFO................(0xCE)  : 0x20080C3BF3812300
------------------------------------------
 - Maximum Non-Turbo Ratio.............. : 0x23 (3500 MHz)
 - Ratio Limit for Turbo Mode........... : 1 (programmable)
 - TDP Limit for Turbo Mode............. : 1 (programmable)
 - Low Power Mode Support............... : 1 (LPM supported)
 - Number of ConfigTDP Levels........... : 1 (additional TDP level(s) available)
 - Maximum Efficiency Ratio............. : 12
 - Minimum Operating Ratio.............. : 8

MSR_PMG_CST_CONFIG_CONTROL.......(0xE2)  : 0x1E000005
------------------------------------------
 - I/O MWAIT Redirection Enable......... : 0 (not enabled)
 - CFG Lock............................. : 0 (MSR not locked)
 - C3 State Auto Demotion............... : 1 (enabled)
 - C1 State Auto Demotion............... : 1 (enabled)
 - C3 State Undemotion.................. : 1 (enabled)
 - C1 State Undemotion.................. : 1 (enabled)
 - Package C-State Auto Demotion........ : 0 (disabled/unsupported)
 - Package C-State Undemotion........... : 0 (disabled/unsupported)

MSR_PMG_IO_CAPTURE_BASE..........(0xE4)  : 0x10414
------------------------------------------
 - LVL_2 Base Address................... : 0x414
 - C-state Range........................ : 1 (C-States not included, I/O MWAIT redirection not enabled)

IA32_MPERF.......................(0xE7)  : 0x741358112
IA32_APERF.......................(0xE8)  : 0x74F4F4F56

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

MSR_IA32_PERF_STATUS.............(0x198) : 0x229300002500
------------------------------------------
 - Current Performance State Value...... : 0x2500 (3700 MHz)

MSR_IA32_PERF_CONTROL............(0x199) : 0xC00
------------------------------------------
 - Target performance State Value....... : 0xC00 (1200 MHz)
 - Intel Dynamic Acceleration........... : 0 (IDA engaged)

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

IA32_THERM_INTERRUPT.............(0x19B) : 0x0

IA32_THERM_STATUS................(0x19C) : 0x88430000
------------------------------------------
 - Thermal Status....................... : 0
 - Thermal Log.......................... : 0
 - PROCHOT # or FORCEPR# event.......... : 0
 - PROCHOT # or FORCEPR# log............ : 0
 - Critical Temperature Status.......... : 0
 - Critical Temperature log............. : 0
 - Thermal Threshold #1 Status.......... : 0
 - Thermal Threshold #1 log............. : 0
 - Thermal Threshold #2 Status.......... : 0
 - Thermal Threshold #2 log............. : 0
 - Power Limitation Status.............. : 0
 - Power Limitation log................. : 0
 - Current Limit Status................. : 0
 - Current Limit log.................... : 0
 - Cross Domain Limit Status............ : 0
 - Cross Domain Limit log............... : 0
 - Digital Readout...................... : 67
 - Resolution in Degrees Celsius........ : 1
 - Reading Valid........................ : 1 (valid)

MSR_THERM2_CTL...................(0x19D) : 0x0

IA32_MISC_ENABLES................(0x1A0) : 0x840089
------------------------------------------
 - Fast-Strings......................... : 1 (enabled)
 - FOPCODE compatibility mode Enable.... : 0
 - Automatic Thermal Control Circuit.... : 1 (enabled)
 - Split-lock Disable................... : 0
 - Performance Monitoring............... : 1 (available)
 - Bus Lock On Cache Line Splits Disable : 0
 - Hardware prefetch Disable............ : 0
 - Processor Event Based Sampling....... : 0 (PEBS supported)
 - GV1/2 legacy Enable.................. : 0
 - Enhanced Intel SpeedStep Technology.. : 0 (disabled)
 - MONITOR FSM.......................... : 1 (MONITOR/MWAIT supported)
 - Adjacent sector prefetch Disable..... : 0
 - CFG Lock............................. : 0 (MSR not locked)
 - xTPR Message Disable................. : 1 (disabled)

MSR_TEMPERATURE_TARGET...........(0x1A2) : 0x690A00
------------------------------------------
 - Turbo Attenuation Units.............. : 0 
 - Temperature Target................... : 105
 - TCC Activation Offset................ : 0

MSR_MISC_PWR_MGMT................(0x1AA) : 0x400000
------------------------------------------
 - EIST Hardware Coordination........... : 0 (hardware coordination enabled)
 - Energy/Performance Bias support...... : 1
 - Energy/Performance Bias.............. : 0 (disabled/MSR not visible to software)
 - Thermal Interrupt Coordination Enable : 1 (thermal interrupt routed to all cores)

MSR_TURBO_RATIO_LIMIT............(0x1AD) : 0x2424252525252525
------------------------------------------
 - Maximum Ratio Limit for C01.......... : 25 (3700 MHz) 
 - Maximum Ratio Limit for C02.......... : 25 (3700 MHz) 
 - Maximum Ratio Limit for C03.......... : 25 (3700 MHz) 
 - Maximum Ratio Limit for C04.......... : 25 (3700 MHz) 
 - Maximum Ratio Limit for C05.......... : 25 (3700 MHz) 
 - Maximum Ratio Limit for C06.......... : 25 (3700 MHz) 

IA32_ENERGY_PERF_BIAS............(0x1B0) : 0x0

MSR_POWER_CTL....................(0x1FC) : 0x2904005B
------------------------------------------
 - Bi-Directional Processor Hot..........: 1 (enabled)
 - C1E Enable............................: 1 (enabled)

MSR_RAPL_POWER_UNIT..............(0x606) : 0xA0E03
------------------------------------------
 - Power Units.......................... : 3 (1/8 Watt)
 - Energy Status Units.................. : 14 (61 micro-Joules)
 - Time Units .......................... : 10 (976.6 micro-Seconds)

MSR_PKG_POWER_LIMIT..............(0x610) : 0x7854000DF8460
------------------------------------------
 - Package Power Limit #1............... : 140 Watt
 - Enable Power Limit #1................ : 1 (enabled)
 - Package Clamping Limitation #1....... : 1 (allow going below OS-requested P/T state during Time Window for Power Limit #1)
 - Time Window for Power Limit #1....... : 111 (327680 milli-Seconds)
 - Package Power Limit #2............... : 168 Watt
 - Enable Power Limit #2................ : 1 (enabled)
 - Package Clamping Limitation #2....... : 1 (allow going below OS-requested P/T state setting Time Window for Power Limit #2)
 - Time Window for Power Limit #2....... : 3 (20 milli-Seconds)
 - Lock................................. : 0 (MSR not locked)

MSR_PKG_ENERGY_STATUS............(0x611) : 0x178F77B
------------------------------------------
 - Total Energy Consumed................ : 1507 Joules (Watt = Joules / seconds)

MSR_PKG_POWER_INFO...............(0x614) : 0x1280460
------------------------------------------
 - Thermal Spec Power................... : 140 Watt
 - Minimum Power........................ : 0
 - Maximum Power........................ : 0
 - Maximum Time Window.................. : 0

MSR_PP0_POWER_LIMIT..............(0x638) : 0x0

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

MSR_TURBO_ACTIVATION_RATIO.......(0x64C) : 0x0

MSR_CONFIG_TDP_NOMINAL...........(0x648) : 0x23
MSR_CONFIG_TDP_LEVEL1............(0x649) : 0x94000000200460
MSR_CONFIG_TDP_LEVEL2............(0x64a) : 0x94000000000000
MSR_CONFIG_TDP_CONTROL...........(0x64b) : 0x0
MSR_TURBO_ACTIVATION_RATIO.......(0x64c) : 0x0
MSR_PKGC6_IRTL...................(0x60b) : 0x0
MSR_PKG_C2_RESIDENCY.............(0x60d) : 0x3C16F96E9
MSR_PKG_C3_RESIDENCY.............(0x3f8) : 0xB85D8
MSR_PKG_C6_RESIDENCY.............(0x3f9) : 0x2B28AB2FE

IA32_TSC_DEADLINE................(0x6E0) : 0x10D0FB81281B

CPU Ratio Info:
------------------------------------------
Base Clock Frequency (BLCK)............. : 100 MHz
Maximum Efficiency Ratio/Frequency.......: 12 (1200 MHz)
Maximum non-Turbo Ratio/Frequency........: 35 (3500 MHz)
Maximum Turbo Ratio/Frequency............: 37 (3700 MHz)
P-State ratio * 100 = Frequency in MHz
------------------------------------------
CPU P-States [ 30 (37) ]
CPU C3-Cores [ 0 9 10 ]
CPU C6-Cores [ 1 3 5 7 8 11 ]
CPU P-States [ (12) 24 30 37 ]
CPU C6-Cores [ 1 2 3 5 7 8 9 10 11 ]
CPU P-States [ (12) 24 30 32 37 ]
CPU C3-Cores [ 0 1 8 9 10 11 ]
CPU C6-Cores [ 1 2 3 4 5 6 7 8 9 10 11 ]
CPU P-States [ (12) 22 24 30 32 37 ]
CPU C6-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 ]
CPU P-States [ (12) 22 24 25 30 32 37 ]
CPU P-States [ 12 22 24 25 30 32 35 (37) ]
CPU P-States [ (12) 22 24 25 30 32 35 36 37 ]
CPU P-States [ (12) 22 24 25 30 31 32 35 36 37 ]
CPU P-States [ (12) 22 24 25 30 31 32 34 35 36 37 ]
CPU P-States [ 12 22 24 25 29 30 31 32 34 35 36 (37) ]
CPU P-States [ 12 22 24 25 29 30 31 32 33 34 35 36 (37) ]
CPU P-States [ (12) 21 22 24 25 29 30 31 32 33 34 35 36 37 ]
CPU P-States [ 12 21 22 24 25 28 29 30 31 32 33 34 35 36 (37) ]
CPU P-States [ (12) 21 22 24 25 27 28 29 30 31 32 33 34 35 36 37 ]
CPU P-States [ (12) 21 22 23 24 25 27 28 29 30 31 32 33 34 35 36 37 ]
CPU P-States [ 12 17 21 22 23 24 25 27 28 29 30 31 32 33 34 35 36 (37) ]
CPU P-States [ (12) 17 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 ]
CPU P-States [ (12) 17 18 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 ]
CPU P-States [ (12) 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 ]
CPU P-States [ 12 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 (37) ]
CPU P-States [ 12 15 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 (37) ]
CPU P-States [ 12 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 (37) ]
CPU P-States [ (12) 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 ]
CPU P-States [ (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 ]
CPU C3-Cores [ 0 1 2 4 8 9 10 11 ]
CPU C3-Cores [ 0 1 2 3 4 5 8 9 10 11 ]
CPU C3-Cores [ 0 1 2 3 4 5 6 8 9 10 11 ] 

AppleIntelInfo Notes:

Notes:
MSR_PMG_CST_CONFIG_CONTROL.......(0xE2)  : 0x1E000005
------------------------------------------
 - CFG Lock............................. : 0 (MSR not locked) // if locked (1), may cause random reboots
 - C3 State Auto Demotion............... : 1 (enabled) // if any of these are supported by CPU, but are 0 (disabled), then you *MAY* not be getting full CPU PM
 - C1 State Auto Demotion............... : 1 (enabled)
 - C3 State Undemotion.................. : 1 (enabled)
 - C1 State Undemotion.................. : 1 (enabled)

MSR_IA32_PERF_CONTROL............(0x199) : 0xC00
------------------------------------------
 - Target performance State Value....... : 0xC00 (1200 MHz) // target should be lowest CPU state

MSR_MISC_PWR_MGMT................(0x1AA) : 0x400000
------------------------------------------
 - EIST Hardware Coordination........... : 0 (hardware coordination enabled) // should be 0, not disabled (1) (if 1, disable BIOS Enhanced Intel Speedstep Technology (EIST) in Advanced/CPU Configuration)

MSR_TURBO_RATIO_LIMIT............(0x1AD) : 0x2424252525252525
------------------------------------------
 - Maximum Ratio Limit for C01.......... : 25 (3700 MHz) // ideally, all cores should be sync'd to max turbo multiplier (in my case - x37) (in BIOS in AI Tweaker, set CPU Cores to "Sync All Cores" and specify the max turbo accordingly)
 - Maximum Ratio Limit for C02.......... : 25 (3700 MHz) 
 - Maximum Ratio Limit for C03.......... : 25 (3700 MHz) 
 - Maximum Ratio Limit for C04.......... : 25 (3700 MHz) 
 - Maximum Ratio Limit for C05.......... : 25 (3700 MHz) 
 - Maximum Ratio Limit for C06.......... : 25 (3700 MHz) 

MSR_PKG_POWER_LIMIT..............(0x610) : 0x7854000DF8460
------------------------------------------
 - Package Power Limit #1............... : 140 Watt // set this according to your CPU's max TDP in BIOS, Ai Tweaker/Internal CPU Power Management => "Long Duration Package Limiter"
 - Enable Power Limit #1................ : 1 (enabled)
 - Package Clamping Limitation #1....... : 1 (allow going below OS-requested P/T state during Time Window for Power Limit #1)
 - Time Window for Power Limit #1....... : 111 (327680 milli-Seconds) // set to 1-127mS in BIOS, Ai Tweaker/Internal CPU Power Management => "Power Package Time Window"
 - Package Power Limit #2............... : 168 Watt // set according to your CPU's max TDP + 20% in BIOS, Ai Tweaker/Internal CPU Power Management => "Short Duration Package Limiter"
 - Enable Power Limit #2................ : 1 (enabled)
 - Package Clamping Limitation #2....... : 1 (allow going below OS-requested P/T state setting Time Window for Power Limit #2)
 - Time Window for Power Limit #2....... : 3 (20 milli-Seconds)
 - Lock................................. : 0 (MSR not locked)

MSR_PKG_POWER_INFO...............(0x614) : 0x1280460
------------------------------------------
MSR_PKG_C2_RESIDENCY.............(0x60d) : 0x3C16F96E9 // if supported by CPU, should be greater than 0x0
MSR_PKG_C3_RESIDENCY.............(0x3f8) : 0xB85D8 // if supported by CPU, should be greater than 0x0
MSR_PKG_C6_RESIDENCY.............(0x3f9) : 0x2B28AB2FE // if supported by CPU, should be greater than 0x0

How to fix MSR_PKG_POWER_LIMIT package limits

 

 

Check and make sure vectors are loaded by running this command:

sysctl machdep.xcpm 

Results:

machdep.xcpm.epp_override: 0
machdep.xcpm.io_epp_boost_enabled: 0
machdep.xcpm.ring_boost_enabled: 0
machdep.xcpm.io_cst_control_enabled: 0
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: 1
machdep.xcpm.mbd_mode: 1
machdep.xcpm.maxintdelay: 0
machdep.xcpm.maxbusdelay: 71680
machdep.xcpm.ratio_changes_total: 47640
machdep.xcpm.ratio_change_ratelimit_ns: 500000
machdep.xcpm.vectors_loaded_count: 1
machdep.xcpm.tuib_ns: 0
machdep.xcpm.bootpst: 37
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: 37
machdep.xcpm.soft_plimit_min_100mhz_ratio: 8
machdep.xcpm.soft_plimit_max_100mhz_ratio: 37
machdep.xcpm.hard_plimit_min_100mhz_ratio: 8
machdep.xcpm.hard_plimit_max_100mhz_ratio: 37
machdep.xcpm.mode: 1

You'll want to focus on these results:

machdep.xcpm.vectors_loaded_count: 1 // injected frequency vectors 0=>none, 1=>loaded
machdep.xcpm.bootpst: 37 // max turbo boost according to chip specs and/or overclock specs
machdep.xcpm.mode: 1 // xcpm stepping/pm, 0=>not loaded, 1=>loaded 

If still 0, try other frequency vectors and/or look into dropping tables (if you haven't already) and/or see if you need Pike's XCPM Bootstrap KernelToPatch patches for your particular CPU.
 
Head over to Pike's Universum for XCPM questions/answers.

[k1n4]

Here's my EFI folder for any random lurkers/registered (intermediate/advanced) users who share the same setup as me and who want a 100% functional set up for their Asus PRO 3.1 USB board running 10.12.3! Please note that EFI folder is still in testing, so please use carefully (in other words, not as a daily driver... yet)!

 

- Highly recommend that you do a FRESH install of 10.12.3. I found that updating/upgrading from a previous installed OS can cause some OS issues afterward (random crashes/errors).

 

Update for 1/30/17 @ 10:50PM -- OsxAptioFixDrv.efi: Kernel Panic during shutdown. Looking into what caused it...

- Diskarbitrationd ==> Mounting/Unmounting Disks -- likely culprit, as this when the KP happened during unmounting

 

Possible KP solution:

Run these commands (this should reduce shutdown/restart timeout from 20 seconds to 1 second):
sudo defaults write /System/Library/LaunchDaemons/com.apple.coreservices.appleevents ExitTimeOut -int 1

sudo defaults write /System/Library/LaunchDaemons/com.apple.securityd ExitTimeOut -int 1

sudo defaults write /System/Library/LaunchDaemons/com.apple.mDNSResponder ExitTimeOut -int 1

sudo defaults write /System/Library/LaunchDaemons/com.apple.diskarbitrationd ExitTimeOut -int 1

sudo defaults write /System/Library/LaunchAgents/com.apple.coreservices.appleid.authentication ExitTimeOut -int 1

Afterward, go to Disk Utility and run first aid on the drive. Restart/shutdown after completion.

 ***If you run anything higher than 10.12.3, the patches inside the "Kernel and Ktext Patches" config.plist may not work.

 

What this EFI folder currently has:

-  Should automatically boot into your default volume (if it's named "Mac OS") after a 3-second countdown when at the Clover screen; if not, edit the config.plist with Clover Configurator-> under Boot tab -> under Default Boot Volume, type the name of your harddrive with OS installed, save and restart

-  Generated CPU PM SSDT (speed step/power management) for a Mac Pro 6,1 SMBIOS with injected 14,2 frequency vectors for an i7 5930K***

-  Generated SSDTs and modified DSDT for ALZA, BR3A, EVSS, GLAN, HECI, NVMe-Pcc, RP04, SAT1, SMBS, UIAC (Click here for SSDT notes)***

-  IntelMausiEthernet for internet

-  OsxAptioFix2Drv-free2000.efi OR OsxAptioFixDrv.efi (after preliminary testing, I was able to get OsxAptioFixDrv.efi to not reboot after 10-15 mins -- might need patched BIOS to work).

- Supports:

• Bluetooth devices (100% functional!)
• Video and Audio over HDMI/DisplayPort
• USB 2.0, 3.0 and 3.1 ports all functional
• Wifi 2.4ghz/5ghz
• Sleep

Other Setup:

- 3402 Patched BIOS (may not be needed with OsxAptioFix2Drv-free2000.efi) -- use at your own risk -- if you decide to use these BIOS via Asus Flashback, rename the file to the following before placing it on a USB stick: X99PU31.CAP

 

My BIOS Setup:

- Under Advanced:

/USB Configuration:

• Intel XHCI Mode - Enable
• EHCI Legacy Support - Disabled
• XHCI Hand-off - Disabled
• EHCI Hand-off - Disabled

- In Ai Tweaker:

• AI Overclock Tuner - Auto (just make sure your CPU is set to: Sync All Cores, otherwise, you may different turbo boosts for each core)
• Internal CPU Power Management (EIST) - Disabled

-In Boot 

/ Secure Boot:

• Os Type - Other OS

/ CSM:

• UEFI and legacy support (the rest of the options are set to: Legacy only)

***Special notes:

- This EFI has a heavily modified DSDT and SSDTs to work with my board AND my case. If you want to create your own to match your specs, which I highly recommend, then you can follow my:

- SSDT notes

- Info on GPU injection via DSDT

- More info on GPU injection via DSDT

- Info on GPU injection via SSDT

- Common MaciASL errors

 

SSDTs specified to my setup:

* SSDT-BR3A.aml

* SSDT-NVMe-Pcc.aml

* SSDT-UIAC.aml 

* SSDT.aml

 

- If you're using a Corsair H100i GTX AIO cooler (or similar Corsair AIO cooler) that connects to an internal USB device, it will prevent your system from sleeping! I recommend you either unplug the USB cable portion or switch to a different cooler!

 

- If you plan on using a NVMe to install 10.12.3 on, then follow my guide on how to generate a spoofed HackrNVMeFamily.kext OR use Pike's IONVMEFamily patches I've provided in my old efi folder's config.plist (the provided EFI below contains support for a Samsung 950 Pro only -- if you don't want it, remove SSDT-NVMe-pcc.aml from CLOVER->ACPI->patched and HackrNVMeFamily-10_12_3.kext from CLOVER->kexts->Other ).

 

- In order to get Wifi to work, you'll need to use the AirPortBrcm4360 patches inside this EFI config.plist and the patched FakeSMC.kext.

 

- If you're not using a 5930k, you'll have to generate your own SSDT:

1. Configure system with appropriate MAC 6,1 SMBIOS(should already be set up if you use either of my EFI folders).

 

2. Open Terminal and download Piker Alpha's ssdtPRGen.sh

 

curl -o ~/ssdtPRGen.sh https://raw.githubusercontent.com/Piker-Alpha/ssdtPRGen.sh/master/ssdtPRGen.sh

3. That will download ssdtPRGen.sh to your user directory. The next step is to change the file mode (+x) with:

chmod +x ~/ssdtPRGen.sh

4. For default SSDT generation with xcpm enabled, type:

sudo ~/ssdtPRGen.sh x -1

Find the file in: ~/Library/ssdtPRGen/ (you want the SSDT.aml) and then copy/paste it in EFI->CLOVER->ACPI->patched.

 

- When 10.12.3 is installed, your SSDT CPU PM may not have any frequency vectors loaded, you can run these commands to check. If it comes back as 0, then you'll need to use Pike's FrequencyVectors.sh (I used 14,2 vectors (#5)). You can use this list (second code box) to determine which SMBIOS version will be the best suited for your particular CPU.

 

 

I've your same system setup and from are day still testing XCPM PM... My MOBO is the Asus X99 Sabertooth with bios 3402patched.

One question; in Clover wiki says that with DSDT and SSDTs it's necessary to check Drop OEM in SSDT panel in ACPI Section. I see that you uncheck it.

testing you EFI and review. Greetings

[Fergarth]

 

Now using OsxAptioFixDrv.efi for 10.12.3. So far, so good. Updated post above.

Yes, most of the time I've used OsxAptioFixDrv-64.efi and never had any problems.

But it's curious! The few root installations I've done, the installer runs better with AptioFix2, but after installation, it starts to give memory allocation error and forces me to use OsxAptioFixDrv-64.efi

Regarding OsxAptioFix2Drv-free2000.efi, I have never tested it or used it.

[thenightflyer]

Yes, most of the time I've used OsxAptioFixDrv-64.efi and never had any problems.

But it's curious! The few root installations I've done, the installer runs better with AptioFix2, but after installation, it starts to give memory allocation error and forces me to use OsxAptioFixDrv-64.efi

Regarding OsxAptioFix2Drv-free2000.efi, I have never tested it or used it.

Enable 4G decode in Bios...i've no more memory allocation errors...consider i use thunderbolt ex dual card with both raid and audio card connected!

[mfc88]

Enable 4G decode in Bios...i've no more memory allocation errors...consider i use thunderbolt ex dual card with both raid and audio card connected!

Tested. Memory Alloc. error during boot despite 4G Decode being enabled.

 

I've your same system setup and from are day still testing XCPM PM... My MOBO is the Asus X99 Sabertooth with bios 3402patched.

One question; in Clover wiki says that with DSDT and SSDTs it's necessary to check Drop OEM in SSDT panel in ACPI Section. I see that you uncheck it.

testing you EFI and review. Greetings

Some motherboards (laptops and older computers) use the same TableID when injecting SSDTS. Mine doesn't:

4:818  0:000    Tables in Rsdt: 15
4:818  0:000    0. BB233140: 'FACP', 'A M I ', Rev: 2, Len: 132
4:818  0:000        (Dsdt: BB2331C8, Facs: BD47FF40)
4:818  0:000        BB2331C8: 'DSDT', 'A M I ', Rev: 2, Len: 221153
4:821  0:003        BD47FF40: 'FACS', Ver: 0, Len: 64
4:821  0:000    1. BB2692C0: 'APIC', 'A M I ', Rev: 3, Len: 256
4:821  0:000    2. BB2693C0: 'FPDT', 'A M I ', Rev: 1, Len: 68
4:821  0:000    3. BB269408: 'FIDT', 'A M I ', Rev: 1, Len: 156
4:821  0:000    4. BB2694A8: 'MCFG', 'A M I', Rev: 1, Len: 60
4:821  0:000    5. BB27F820: 'ASF!', ' HCG', Rev: 32, Len: 160
4:821  0:000    6. BB269540: 'SSDT', 'SataTabl', Rev: 1, Len: 877
4:821  0:000    7. BB2698B0: 'UEFI', 'A M I ', Rev: 1, Len: 66
4:821  0:000    8. BB2698F8: 'HPET', 'A M I ', Rev: 1, Len: 56
4:821  0:000    9. BB269930: 'MSCT', 'A M I ', Rev: 1, Len: 144
4:821  0:000    10. BB2699C0: 'SLIT', 'A M I ', Rev: 1, Len: 45
4:821  0:000    11. BB2699F0: 'SRAT', 'A M I ', Rev: 3, Len: 4440
4:821  0:000    12. BB26AB48: 'WDDT', 'A M I ', Rev: 1, Len: 64
4:821  0:000    13. BB26AB88: 'SSDT', 'PmMgt', Rev: 2, Len: 85085
4:821  0:000    14. BB27F7E8: 'BGRT', 'A M I ', Rev: 1, Len: 56

Drop tables specify order of SSDT installation and which SSDT will be injected first, second, third...etc. From what I've gathered, the Drop Tables option is needed if you have incomplete P-States/C-States and/or CPU stability issues. You could drop SSDT.aml (CpuPM) to make sure it gets loaded, but in my testing, I found it worked just fine without loading first.

[k1n4]

Some motherboards (laptops and older computers) use the same TableID when injecting SSDTS. Mine doesn't:

4:818  0:000    Tables in Rsdt: 15
4:818  0:000    0. BB233140: 'FACP', 'A M I ', Rev: 2, Len: 132
4:818  0:000        (Dsdt: BB2331C8, Facs: BD47FF40)
4:818  0:000        BB2331C8: 'DSDT', 'A M I ', Rev: 2, Len: 221153
4:821  0:003        BD47FF40: 'FACS', Ver: 0, Len: 64
4:821  0:000    1. BB2692C0: 'APIC', 'A M I ', Rev: 3, Len: 256
4:821  0:000    2. BB2693C0: 'FPDT', 'A M I ', Rev: 1, Len: 68
4:821  0:000    3. BB269408: 'FIDT', 'A M I ', Rev: 1, Len: 156
4:821  0:000    4. BB2694A8: 'MCFG', 'A M I', Rev: 1, Len: 60
4:821  0:000    5. BB27F820: 'ASF!', ' HCG', Rev: 32, Len: 160
4:821  0:000    6. BB269540: 'SSDT', 'SataTabl', Rev: 1, Len: 877
4:821  0:000    7. BB2698B0: 'UEFI', 'A M I ', Rev: 1, Len: 66
4:821  0:000    8. BB2698F8: 'HPET', 'A M I ', Rev: 1, Len: 56
4:821  0:000    9. BB269930: 'MSCT', 'A M I ', Rev: 1, Len: 144
4:821  0:000    10. BB2699C0: 'SLIT', 'A M I ', Rev: 1, Len: 45
4:821  0:000    11. BB2699F0: 'SRAT', 'A M I ', Rev: 3, Len: 4440
4:821  0:000    12. BB26AB48: 'WDDT', 'A M I ', Rev: 1, Len: 64
4:821  0:000    13. BB26AB88: 'SSDT', 'PmMgt', Rev: 2, Len: 85085
4:821  0:000    14. BB27F7E8: 'BGRT', 'A M I ', Rev: 1, Len: 56

 

Ok... So I'll check my default SSDTs from clover (F4 at the bootloader) and find the difference with yours with IOREG.

Thank's a lot bro.

If you've any suggestion thanks again.

 

 

Inviato dal mio iPad utilizzando Tapatalk

[thenightflyer]

@mfc

Try with aptiofree-2000 instead of yours...other users like me using 4g decode have no more allocation errors

[mfc88]

@mfc

Try with aptiofree-2000 instead of yours...other users like me using 4g decode have no more allocation errors

With osxdrv2-free, I don't need 4g decode enabled (it's what I've been using as my daily driver).

[Balamut]

<key>KernelToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>patch max cpu init (from 63 to 87)</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				gAA//bZIg/k/
				</data>
				<key>MatchOS</key>
				<string>10.12.x</string>
				<key>Replace</key>
				<data>
				gAA//bZIg/lX
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>10.12 Broadwell-E CPUID Patch</string>
				<key>Disabled</key>
				<true/>
				<key>Find</key>
				<data>
				g8Dp
				</data>
				<key>MatchOS</key>
				<string>10.12.x</string>
				<key>Replace</key>
				<data>
				g8Dh
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>10.12 xcpm_core_scope_msrs</string>
				<key>Disabled</key>
				<true/>
				<key>Find</key>
				<data>
				vgIAAAAx0uhs/P//
				</data>
				<key>MatchOS</key>
				<string>10.12.x</string>
				<key>Replace</key>
				<data>
				vgIAAAAx0pCQkJCQ
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>10.12 xcpm_pkg_scope_msr</string>
				<key>Disabled</key>
				<true/>
				<key>Find</key>
				<data>
				vgcAAAAx0uiU/P//
				</data>
				<key>MatchOS</key>
				<string>10.12.x</string>
				<key>Replace</key>
				<data>
				vgcAAAAx0pCQkJCQ
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>10.12 xcpm_idle</string>
				<key>Disabled</key>
				<true/>
				<key>Find</key>
				<data>
				ILniAAAADzA=
				</data>
				<key>MatchOS</key>
				<string>10.12.x</string>
				<key>Replace</key>
				<data>
				ILniAAAAkJA=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>(wrsmr fix to get CPU max) © okrasit</string>
				<key>Disabled</key>
				<true/>
				<key>Find</key>
				<data>
				idjB4Ai5mQE=
				</data>
				<key>MatchOS</key>
				<string>10.12.x</string>
				<key>Replace</key>
				<data>
				uAAxAAC5mQE=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>10.12 xcpm_bootstrap</string>
				<key>Disabled</key>
				<true/>
				<key>Find</key>
				<data>
				g8PEg/si
				</data>
				<key>MatchOS</key>
				<string>10.12.x</string>
				<key>Replace</key>
				<data>
				g8O8g/si
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>Kext inject allowed</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				6CUAAADrBeieBQAA
				</data>
				<key>MatchOS</key>
				<string>10.12.x</string>
				<key>Replace</key>
				<data>
				6CUAAACQkOieBQAA
				</data>
			</dict>
		</array>

But I have 6850k

 

 

 

patch max cpu init (from 63 to 87) ??

 

Anyone tried this?

[thenightflyer]

With osxdrv2-free, I don't need 4g decode enabled (it's what I've been using as my daily driver).

With osxaptiofix2drv-free2000 i had less random memory allocation errors than the original provided by clover. This was due because i have thunderbolt card. All users with a thunderbolt card have random allocation memory errors even with free2000 drv too. You haven't any thunderbolt card so you had no errors with that drv. Enable 4g decode is a solution for users like me with a thundebolt card that can still cause random errors with aptio drv (version free2000 or not).

The best solution for me is free2000+4g decode...in this way i've no more random errors and raid is more stable than before (no disconnection or timeout errors when i try to unrar or unzip a big archive)

[mfc88]

Just a question for anyone lurking: Would it be worthwhile to create a rather extensive "In-depth x99 Mac OS 10.12.3 Pre-Installation, Installation, and Post-Installation" Youtube video? Covering everything from USB pre-install, to BIOS settings, to EFI setup, to Kexts, to SSDT/DSDT injection...etc? Or is there enough information out there that it'd be a waste of time?   

 

Not doing. Lack of interest.

[Balamut]

For general purpose it is worth it, but since hackintosh is unique to each even with the near exact same system, you might wanna state that

[Fljagd]

Hello,
So now with the clover 3998 the kernel patch bug to disappeared.
Patches must be active for CPU steps
friendly

config.plist.zip

[mfc88]

Okie pokie, understanding what the config.plist "Drop Tables" does...
 
Basically, when you use Clover to dump ACPI tables (via F4 at boot manager screen), you'll notice you'll have several SSDTs (SSDT-0, SSDT-1...etc) in your EFI->CLOVER->ACPI->origin folder. These SSDTs are provided by the manufacturer and may cause conflicts with your custom SSDTs and/or DSDT edits. Your board may not have all these (mine doesn't), but here's a list of what I've found by looking at other member's EFI folders:
 
For example:
Table Id: "EInkApp" ==> affects ????
Table Id: "sensrhub" ==> affects I2C bus for I2C devices???
Table Id: "Ther_Rvp" ==> affects thermals and cooling policies???
Table Id: "PtidDevc" ==> affects device sensors (voltages/fan speeds) and/or laptop batteries sensors
Table Id: "xh_rvp10" ==> affects XHC RHUB
Table Id: "SaSsdt" ==> affects GPU/Audio
Table Id: "Cpu0Ist" ==> affects CPU Power Management
Table Id: "Cpu0Cst" ==> affects CPU Power Management
Table Id: "PmMgt" ==> affects CPU Power Management
Table Id: "CpuSsdt" ==> affects CPU Power Management
Table Id: "ApIst" ==> affects CPU Power Management
Table Id: "ApCst" ==> affects CPU Power Management
Table Id: "Cpu0Hwp" ==> affects CPU Power Management
Table Id: "ApHwp" ==> affects CPU Power Management
Table Id: "PmRef" ==> affects CPU Power Management
DMAR ==> *MAY* affect CPU temps readings (eg. Intel Power Gadget won't show temps)
 
...etc.
 
You can find out which ones you'll need to drop by simply dumping your ACPI tables and then opening up each one in MaciASL. At the top of the file will be the name of the Table Id (highlighted below):

These will vary from board to board, manufacturer to manufacturer. Sometimes these can cause issues (kernel panics/not being able to boot). Therefore, you'll want to "Drop" (prevent) ALL of them from being used, so that your SSDTs/DSDT injections will be used instead. However, dropping them may cause issues, so you should add one at a time and check for stability. If stable, add the next one, if not stable, then leave it alone and do not drop it. The basic idea is to drop ones that will affect your custom SSDTs.
 
OEM SSDT scopes that may affect custom SSDTs (specifically if there are _DSMs)...
x99:
ALZA => _SB.PCI0.ALZA/HDEF
EVSS => _SB.PCI0.EVSS
GFX1 => _SB.PCIX.BRXA.XXXX, _SB.PCIX.RPXX.XXXX
GLAN => _SB.PCI0.GLAN
HECI => _SB.PCI0.HECI/IMEI 
LPC0 => _SB.PCI0.LPC0
SAT1 => _SB.PCI0.SAT1
XHC => _SB.PCI0.XHC(I)
 
x170:
EVSS => _SB.PCI0.EVSS
GFX1 => _SB.PCIX.PEGX.XXXX
GLAN => _SB.PCI0.GLAN
HDAS => _SB.PCI0.HDAS/HDEF
HECI => _SB.PCI0.HECI/IMEI 
LPCB => _SB.PCIB.LPCB
SAT0 => _SB.PCI0.SAT0
XHC => _SB.PCI0.XHC(I)
 
My particular board only has two SSDTs:
Table Id: "SataTabl" ==> affects SATA controller (SSDT-0.aml) *Mine was specifically scoped to SB.PCI0.SAT0, yours may be scoped to SB.PCI0.SAT1
Table Id: "PmMgt" ==> affects CPU Power Management (SSDT-1.aml) * Mine was scope to _SB.SCKX.CPXX
 
So, as far as I'm concerned, I'll add "PmMgt" to the Drop Tables to achieve CPU Power Management (via a generated ssdtPRGen SSDT.aml) and SataTabl (SSDT-1.aml) can be dropped or left alone as it doesn't have any use in my case (using SAT1, not SAT0):

Drop Tables
----
Signature: SSDT
Type/key: TableId
String/number: PmMgt 

Signature: SSDT
Type/key: TableId
String/number: SataTabl 

 

So it'll basically mean... drop OEM SSDT-1.aml (the manufacturer supplied SSDT "PmMgt") and instead use Pike's SSDT.aml (ssdtPRGen SSDT "PmMgt") in the patched folder...etc.
 
 
"Sorted order" on the other hand then allows you to load the SSDTs in a user specified order, for example (pay attention to the naming convention!):
SSDT.aml
SSDT-0.aml
SSDT-1.aml

SSDT-2.aml
...etc
 
or
 
SSDT.aml
SSDT-GFX1.aml
SSDT-NVME.aml
SSDT-GLAN.aml
...etc
 
Since Clover 3835?, you don't have to follow a SSDT-(0-20).aml naming pattern. Instead, you can use names like "SSDT-Nvme-Pcc.aml" or "SSDT-RP04.aml" (in your ACPI patched folder) and so on. For some boards, they don't have to be in a particular order to be loaded correctly (mine doesn't and therefore I DON'T). However, other boards may expect certain SSDTs to be loaded first, second, third...etc and may require a sorted table, otherwise you may have stability issues. 

[Fergarth]

 

Ahhh... so it's not really disabling them?

 

Here's the ones I have listed in my Clover setup (running 4.36.0 -- found anything above ^4.36.0 prevents mounting other SSDs correctly):

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

BE0200000031D2E86CFCFFFF
BE0200000031D29090909090
_xcpm_core_scope_msrs  © Pike R. Alpha

BE0B00000031D2E859FCFFFF
BE0B00000031D29090909090
_xcpm_SMT_scope_msrs  © Pike R. Alpha

BE0B0000005DE908000000
BE0B0000005DC390909090
_xcpm_SMT_scope_msrs  © Pike R. Alpha

BE0700000031D2E894FCFFFF
BE0700000031D29090909090
_xcpm_pkg_scope_msr  © Pike R. Alpha

20B9E20000000F30
20B9E20000009090
XCPM_idle Replace All fix by Pike R. Alpha

83C3C483FB22
83C3C183FB22
_xcpm_bootstrap Sierra © Pike R. Alpha

83C0E9
83C0E6
Haswell-E CPUID Patch

Hi mcf,

At this time it is not necessary to have Haswell-E CPUID Patch on the plist.

Actually this made no difference on Haswell-E processors, it was just required by Broadwell-E. It was told me by a Coder and confirm that I do not need and no longer use it.

By the way, the Clover r3994 bug (enable/disable reversed) has been fixed with the installation of the last Clover r3998.

[mfc88]

Hi mcf,

At this time it is not necessary to have Haswell-E CPUID Patch on the plist.

Actually this made no difference on Haswell-E processors, it was just required by Broadwell-E. It was told me by a Coder and confirm that I do not need and no longer use it.

By the way, the Clover r3994 bug (enable/disable reversed) has been fixed with the installation of the last Clover r3998.

Thanks, will do more extensive testing.

 

 

In the meantime, I ran into memory mapping issues as soon as I started to install apps to my 10.12.3 setup running Clover's OsxAptioFixDrv.efi:

 

What was installed:

-- Atom Editor

-- Carbon Copy Cloner

-- CleanMyMac3

-- Intel Power Gadget (*Uninstalled*)

-- NodeJs (v. 3.9.5)

-- MongoDB (v3.4.2)

-- RoboMongo

 

Update 2/4/17 @ 4:30PM: Updated Clover EFI to r3998 and that seamed to resolve the memory issues for now. Also removed Haswell CPU ID from config.plist as it doesn't seem to affect XCPM. Updated my 10.12.3 EFI post to reflect new findings.

 

Update 2/4/17 @ 8:30PM: Getting random reboots. Stepping away from OsxAptioFixDrv and moving back to OsxAptioFix2Drv-free. Too unstable/unpredictable. 

[Fergarth]

Thanks, will do more extensive testing.

 

In the meantime, I ran into memory mapping issues as soon as I started to install apps to my 10.12.3 setup running OsxAptioFixDrv.efi:

What was installed:

-- Atom Editor

-- Carbon Copy Cloner

-- CleanMyMac3

-- Intel Power Gadget (*Uninstalled*)

-- NodeJs (v. 3.9.5)

-- MongoDB (v3.4.2)

-- RoboMongo

 

Update 2/4/17 @ 4:30PM: Updated Clover EFI to r3998 and that seamed to resolve the memory issues for now. Also removed Haswell CPU ID from config.plist as it doesn't seem to affect XCPM. Updated my 10.12.3 EFI post to reflect new findings.

 

Update 2/4/17 @ 8:30PM: Getting random reboots. Stepping away from OsxAptioFixDrv and moving back to OsxAptioFix2Drv-free. Too unstable/unpredictable. 

Memory allocation problems certainly will not have to do with the applications you have installed. I think it's a matter of choosing which drive OsxAptioFix is best suited to your system. But I read somewhere that for those who have peripherals (graphics card) with more than 4GB, should activate 4g decode to avoid these problems. Anyway, I've never tried or even had to do it because my system is stable.

[thenightflyer]

Memory allocation problems certainly will not have to do with the applications you have installed. I think it's a matter of choosing which drive OsxAptioFix is best suited to your system. But I read somewhere that for those who have peripherals (graphics card) with more than 4GB, should activate 4g decode to avoid these problems. Anyway, I've never tried or even had to do it because my system is stable.

I solved random memory allocation errors with OsxAptioFix2Drv-free2000.efi + enabled 4g decode in bios....i've a thunderbolt card in my rig that is to say it's usual to have random or permanent memory allocation errors at boot!

[mfc88]

Memory allocation problems certainly will not have to do with the applications you have installed. I think it's a matter of choosing which drive OsxAptioFix is best suited to your system. But I read somewhere that for those who have peripherals (graphics card) with more than 4GB, should activate 4g decode to avoid these problems. Anyway, I've never tried or even had to do it because my system is stable.

Will be in testing this weekend (OsxDrvFix + 4g decode).

 

Noticed I was mainly getting random restarts when running Chrome. I've since switched to Firefox. Will post updates if needed.

 

Currently running OsxDrv2Fix-free + 4G decode.

[Balamut]

Odd, I have complete opposite, issues with Firefox, none with Chrome.

 

Will be in testing this weekend (OsxDrvFix + 4g decode).

 

Noticed I was mainly getting random restarts when running Chrome. I've since switched to Firefox. Will post updates if needed.

 

Currently running OsxDrv2Fix-free + 4G decode.

[mfc88]

Odd, I have complete opposite, issues with Firefox, none with Chrome.

What kind of issues?

 

So far, the only issue I've had is that it's a bit slow. So I did some "about:config" tweaks and it seems to be running faster (although, admittedly, not as fast as Chrome).

 

As for Chrome issues: I was getting a lot of update crashes. For some reason they set their update interval to something stupidly low (triggered quite a bit of update requests).

[PMheart]

Hi. Please excuse me. I don't have the desktops that are discussed at this topic but I have some ideas...

 

Aptio-free2000 could be not reliable. I think OsxAptioFixDrv-64.efi (Aptio fix v1) can be a better choice. But I don't think the vanilla one which is contained in Clover pkg installer is okay enough cuz it has only too low memory size... And thus I enlarged it. (Enlarged to 512Mb instead of the original 128Mb.) Here it is.

 

OsxAptioFixDrv-64.efi.zip

 

To use this, some important notes:

1. Aptiofix v1 is not compatible with hibernation. So don't enable hibernating at all! (IMHO for desktops we always don't need it...) To disable hibernation, please run the following command in Terminal:

sudo pmset -a hibernatemode 0

2. You need to replace my OsxAptioFixDrv-64.efi after updating Clover via Clover PKG Installer. Or try my simple trick:

  1) Rename OsxAptioFixDrv-64.efi to any name with *.efi, for me I renamed it to OsxAptioFixDrv.efi. (Removed '-64')

  2) Don't install OsxAptioFixDrv-64.efi from Clover PKG. Like this:

  

  Note: You must place my OsxAptioFixDrv-64.efi (and renamed to OsxAptioFixDrv.efi) into /EFI/CLOVER/drivers64UEFI !!!

 

3. Remove all other *Aptiofix* drivers!

[Matthew82]

 

OsxAptioFixDrv-64.efi.zip

 

Working good on Asus x99