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

jacoweb · January 29, 2017

Welcome to thunderbolt club

The only way a thunderbolt (thunderbolt3/USB-c) peripheral (hd, raid or audio card) can work in osx is that it's attached and switched on at system boot. If you switch on or connect your thunderbolt peripherals when osx is started (same for windows) it will not be recognized.

It's not your issue but it's a common thunderbolt users issue. In my case i must switch on my clarett 2pre and then my hackintosh. Same for my raid....

ah.

That sux. Then i need to live with it hehe.

Fergarth · January 29, 2017

Update from 12.3 Final to 12.4 Beta (16E144f)
I lost the onboard sound on the ALC1150, but I'm still not sure if it was the OS or the Clover update for v3.2k_r3994, which changed the ALC patches, erasing the AppleHDAControler patch. (I'm studying the case)
The Nvidia Web Driver, editing NVDAStartup.kext form 16D to 16E, recognizes the graphics card and allows some resolutions (not all), but without full acceleration.
Bluetooth, WiFi and USB's remained ok.
XPCM and speedsteps have stopped working and I think it requires new patches... but as I said above, I am studying the case! :yes:

thenightflyer · January 29, 2017

Update from 12.3 Final to 12.4 Beta (16E144f)

I lost the onboard sound on the ALC1150, but I'm still not sure if it was the OS or the Clover update for v3.2k_r3994, which changed the ALC patches, erasing the AppleHDAControler patch. (I'm studying the case)

The Nvidia Web Driver, editing NVDAStartup.kext form 16D to 16E, recognizes the graphics card and allows some resolutions (not all), but without full acceleration.

Bluetooth, WiFi and USB's remained ok.

XPCM and speedsteps have stopped working and I think it requires new patches... but as I said above, I am studying the case!

You are in advance mate Now we should solve patch problems with 10.12.3...then it will be time to think about 10.12.4 final.....

Mike Ranger · January 29, 2017

It's in the third slot starting from the first near cpu slot. It's the only where it can works (i refer to Deluxe II).

About settings i changed only to legacy mode to allow osx to see peropherals. Everything else is not different from default values. Consider i've "4g decode£ enabled in bios. In this way i've no more allocation memory errors.

Hmmm... when I boot in 4g mode enabled.... it will not fully boot but reboot / crash.

That is really strange.

Can I confirm if Thunderbolt is working without any device attached?

Will I see something in System Information?

Thanks, Mike

thenightflyer · January 29, 2017

Hmmm... when I boot in 4g mode enabled.... it will not fully boot but reboot / crash.

That is really strange.

Can I confirm if Thunderbolt is working without any device attached?

Will I see something in System Information?

Thanks, Mike

I'm with Xeon CPU and i've no problem with 4g decode enabled, but when i had 5960X cpu my system didn't boot when i enabled 4G

Toooorch · January 29, 2017

I'm with Xeon CPU and i've no problem with 4g decode enabled, but when i had 5960X cpu my system didn't boot when i enabled 4G

I can confirm this. 4G solved all my problems with allocation. Using X99 Deluxe II with 5820K. Thank you for advice this!

Balamut · January 29, 2017

Needs or doesn't need?

Hello everyone
For information, with 10.12.3 more needs patches for the kernel

Fergarth · January 29, 2017

You are in advance mate Now we should solve patch problems with 10.12.3...then it will be time to think about 10.12.4 final.....

Yes I understand, but I also think that everything here can be useful. And in this case, for those who are like me and like to try new versions, I advise you not to make updates to 12.4 for now, even though I know that there will be a solution to the small problems as always!

Needs or doesn't need?

Although we have different hardware, what I can say is that from 12.2 to 12.3 Final (including all betas), I never needed additional patches and everything worked flawlessly. But yes, at this point with 12.4 beta, I confirm that new patches are needed for XCPM to work.

Fljagd · January 29, 2017

Needs or doesn't need?

i m sorry for my english

Doesn't need

mfc88 · January 29, 2017

i m sorry for my english

Doesn't need

Still need... testing with 10.12.3...

✖ Without:

sysctl machdep.xcpm 

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: 0
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: 0
machdep.xcpm.ratio_change_ratelimit_ns: 500000
machdep.xcpm.vectors_loaded_count: 0
machdep.xcpm.tuib_ns: 0
machdep.xcpm.bootpst: 0
machdep.xcpm.bootplim: 0
machdep.xcpm.power_source: 0
machdep.xcpm.tuib_enabled: 0
machdep.xcpm.tuib_plimit_min_100mhz_ratio: 0
machdep.xcpm.tuib_plimit_max_100mhz_ratio: 0
machdep.xcpm.soft_plimit_min_100mhz_ratio: 0
machdep.xcpm.soft_plimit_max_100mhz_ratio: 0
machdep.xcpm.hard_plimit_min_100mhz_ratio: 0
machdep.xcpm.hard_plimit_max_100mhz_ratio: 0
machdep.xcpm.mode: 0

✓ With:

sysctl machdep.xcpm 

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

On that note, 10.12.3 is super unstable for me. Reinstalled it and now I'm getting random crashes from Apple apps (no reboots though). Had the same issue when I tried to update to 10.12.1 (clean install and upgrade). Guess my system specs aren't compatible with anything above 10.12.

xelanaiznac · January 30, 2017

hi guys.

one simple question. I've seen, and maybe someone else, that there are a lot of topics regarding power management for x99.

and there are contrasting infos. is it possible to have a simply guide, step by step to have a 100% working system?

I think that the part that is more complicated is the clover config.plist.

a part from this, can we all agree with these steps?

1.bios must be patched (especially with asus mobo)

2.intel speed step must be disabled in bios (EIST)

3.we have to use macpro6,1 system def and we have to create the ssdt using vectorlist imac14,2

4.we don't have to use fakecpuid anymore

5.we don't have to use nullcpupowermanagement anymore

6.voodoosync is still needed for sleep

can you please share your config.plist?

the contrasting infos that I found regard acpi values and then kernel and kext patches.

thank you and sorry for my English

Fljagd · January 30, 2017

Still need... testing with 10.12.3...

✖ Without:

sysctl machdep.xcpm 

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: 0
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: 0
machdep.xcpm.ratio_change_ratelimit_ns: 500000
machdep.xcpm.vectors_loaded_count: 0
machdep.xcpm.tuib_ns: 0
machdep.xcpm.bootpst: 0
machdep.xcpm.bootplim: 0
machdep.xcpm.power_source: 0
machdep.xcpm.tuib_enabled: 0
machdep.xcpm.tuib_plimit_min_100mhz_ratio: 0
machdep.xcpm.tuib_plimit_max_100mhz_ratio: 0
machdep.xcpm.soft_plimit_min_100mhz_ratio: 0
machdep.xcpm.soft_plimit_max_100mhz_ratio: 0
machdep.xcpm.hard_plimit_min_100mhz_ratio: 0
machdep.xcpm.hard_plimit_max_100mhz_ratio: 0
machdep.xcpm.mode: 0

✓ With:

sysctl machdep.xcpm 

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: 0
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

On that note, 10.12.3 is super unstable for me. Reinstalled it and now I'm getting random crashes from Apple apps (no reboots though). Had the same issue when I tried to update to 10.12.1 (clean install and upgrade). Guess my system specs aren't compatible with anything above 10.12.

Hi,

No problem for me

Stable and no untimely reboot

Last login: Mon Jan 30 18:26:12 on console
Mac-Pro-de-Fljagd:~ fljagd$ sysctl machdep.xcpm 
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: 2
machdep.xcpm.mbd_applications: 333
machdep.xcpm.mbd_mode: 1
machdep.xcpm.maxintdelay: 0
machdep.xcpm.maxbusdelay: 71680
machdep.xcpm.ratio_changes_total: 469673
machdep.xcpm.ratio_change_ratelimit_ns: 500000
machdep.xcpm.vectors_loaded_count: 1
machdep.xcpm.tuib_ns: 0
machdep.xcpm.bootpst: 43
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: 43
machdep.xcpm.soft_plimit_min_100mhz_ratio: 8
machdep.xcpm.soft_plimit_max_100mhz_ratio: 43
machdep.xcpm.hard_plimit_min_100mhz_ratio: 8
machdep.xcpm.hard_plimit_max_100mhz_ratio: 43
machdep.xcpm.mode: 1
Mac-Pro-de-Fljagd:~ fljagd$

DarwinDumper_3.0.2_30.01_18.51.51_MacPro6,1_AMI_X64_3994_Sierra_16D32_fljagd 2.zip

Edited January 30, 2017 by Fljagd

Fergarth · January 30, 2017

Hello everyone

For information, with 10.12.3 not needs anymore patches for the kernel

~~I just confirmed this! It works perfectly for me too!~~

In 12.2 and 12.3 (including all betas) I did not have any problems, but now in 12.4 with the latest Clover I was without XCPM. I turned all XCPM Patchs off and everything went back to normal.

XCPM working

Speedsteps working

Freq.Vectors Loaded

Everything Loaded

EIST Disabled (but if Enabled, apparently works the same)

~~Each time my EFI is thinner and my Plist cleaner, as I like it!~~

~~Tanks Fljagd~~

EDIT: Do not mind this, it was due to a recent Clover bug (activaded / desactivated) were reverted.

mfc88 · January 30, 2017

I just confirmed this! It works perfectly for me too!

In 12.2 and 12.3 (including all betas) I did not have any problems, but now in 12.4 with the latest Clover I was without XCPM. I turned all XCPM Patchs off and everything went back to normal.

XCPM working

Speedsteps working

Freq.Vectors Loaded

Everything Loaded

EIST Disabled (but if Enabled, apparently works the same)

Each time my EFI is thinner and my Plist cleaner, as I like it!

Tanks Fljagd

Must be native support for 5820k? Are you still loading Pike's SSDT?

Curious if anyone else has success with their processor (other than a 5820k)...

On that note, did a refresh install of 10.12.3 (required some tweaking):

✓ Audio over HDMI/DP

✓ Bluetooth

✓ CPU Power Management/Stepping

✓ Ethernet

✓ GPU recognition/usage

✓ NVMe recognition and R/W/E permissions (updated SSDT NVMe to 10.12.3)

✓ Sleep

✓ USB 2.0, 3.0, 3.1 recognition/usage

✓ WIFI 2.4ghz/5ghz

Still not sure if it's 100% stable... will continue to test.

Matthew82 · January 30, 2017

Must be native support for 5820k? Are you still loading Pike's SSDT?

Curious if anyone else has success with their processor (other than a 5820k)...

On that note, did a refresh install of 10.12.3 (required some tweaking):

✓ Audio over HDMI/DP

✓ Bluetooth

✓ CPU Power Management/Stepping

✓ Ethernet

✓ GPU recognition/usage

✓ NVMe recognition and R/W/E permissions (updated SSDT NVMe to 10.12.3)

✓ Sleep

✓ USB 2.0, 3.0, 3.1 recognition/usage

✓ WIFI 2.4ghz/5ghz

Still not sure if it's 100% stable... will continue to test.

This is Clover issue. Patch must be tu run OS X but, when it is disabled it working. If you delete the patches computer will not load system.

mfc88 · January 30, 2017

This is Clover issue. Patch must be tu run OS X but, when it is disabled it working. If you delete the patches computer will not load system.

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

Matthew82 · January 30, 2017



<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

Fljagd · January 30, 2017

This is Clover issue. Patch must be tu run OS X but, when it is disabled it working. If you delete the patches computer will not load system.

Indeed it is strange if I delete the patches of config.plist

The steps of the cpu are blocked at the maximum frequency

mfc88 · January 30, 2017

Indeed it is strange if I delete the patches of config.plist

The steps of the cpu are blocked at the maximum frequency

Leaves me to believe that it's not really disabling the patches then... what version of Clover Configurator as you using?

Fergarth · January 30, 2017

As I said I am with the last Clover r3994 and in fact, everything worked again as soon as I deactivated all xcpm patches. Although the patches are disabled, now I will delete them from the plist and test to see how it behaves

mfc88 · January 30, 2017

Here's my EFI folder for any random lurkers/registered (intermediate/advanced) users who share the same setup as me and who want a mostly functional set up for their Asus PRO 3.1 USB board running 10.12.3! Please note that the EFI folders are 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).

************************************************
* Important Updates: *
************************************************

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 occurred when the KP happened (during unmounting)

Possible KP fix (run Disk Utility->First Aid on main drive after running commands):

sudo defaults write /System/Library/LaunchDaemons/c\
om.apple.coreservices.appleevents ExitTimeOut -int 1

sudo defaults write /System/Library/LaunchDaemons/c\
om.apple.securityd ExitTimeOut -int 1

sudo defaults write /System/Library/LaunchDaemons/c\
om.apple.mDNSResponder ExitTimeOut -int 1

sudo defaults write /System/Library/LaunchDaemons/c\
om.apple.diskarbitrationd ExitTimeOut -int 1

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

Update for 2/4/17 @ 3:00PM -  OsxAptioFixDrv.efi: After installing apps, I now have memory mapping issues upon boot. Looking for solution.

Update for 2/4/17 @ 4:30PM -  OsxAptioFixDrv.efi: I updated my Clover EFI to r3998, no more memory issues to report. For now, it's working. Removed EFI_ASUS-PRO-USB3.1_10.12.3_FIXDRV.zip and added EFI_ASUS-PRO-USB3.1_10.12.3_FIXDRV-r3998.zip (I also removed the Haswell CPU ID patch from config.plist's KernelToPatch -- doesn't seem to affect XCPM and therefore not needed). On that note, EFI_ASUS-PRO-USB3.1_10.12.3_FIX2DRV-FREE.zip is running on Clover r3859 and won't be updated (it's stable as is -- no use updating something that isn't broken).

Update 2/4/17 @ 8:30PM: OsxAptioFixDrv.efi: Getting random reboots. Stepping away from OsxAptioFixDrv and moving back to OsxAptioFix2Drv-free. EFI_ASUS-PRO-USB3.1_10.12.3_FIXDRV-r3998.zip has been removed. Too unstable.

Update 2/11/17 @ 8:45AM: Since PMHeart has graciously provided a OsxAptioFixDrv with 512MB of free space, I've been allowed to continue to test a OsxAptioFixDrv.efi over the past 3 days.  So far, I haven't had any stability issues with my current Clover revision. However, do note, that I was having stability issues when running Clover EFI r3899+, and therefore had to revert back to using what I've been using already: r3859. It may just be my particular setup doesn't like the newer Clover versions, but its hard to say which is at fault (Clover, my system or the efi). Anyway, update at your own risk. Added a new EFI folder called: EFI_ASUS-PRO-USB3.1_10.12.3_FIXDRV-512MB.zip which includes my EFI and the modded .efi.

Update 2/12/17 @ 9:30PM: OsxAptioFixDrv.efi: Sleep appears to be partially broken. Power nap works, but putting the Mac to sleep manually results in a black screen on wake up (no video signal). Also, power nap, while working, tends to mess up Keychain permissions. I'd avoid any sleep/nap features for the time being.

Warning: If you use a Logitech Performance MX mouse (or similar) and are using Logitech Control Center Driver 3.9.5.66 it will cause random reboots in 10.12.3! Symptoms: After 5-10 minutes, the mouse will freeze, then the system will reboot.

Update 3/20/17 @ 7:15AM: I've since switched my CPU from a 5930k to a 6950x and as such will no longer be supporting/updating these files. The majority of my current EFI has been optimized for S/L/E usage and has been heavily modified to work with my current system specs.

************************************************

***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 and OsxAptioFixDrv.efi (not from Clover, but from a modified .efi)
- 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 (partially broken -- works for power nap, but not for manually putting to sleep (no video signal on wake) -- recommended not use it)

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 (depends on your system whether or not you want to enable/disable)

-In Boot
/ Secure Boot:

Os Type - Other OS

/ CSM:

UEFI and UEFI driver first

***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 (also includes self-contained DSDT.aml that doesn't require SSDTs to work -- still need Pike's CPU PM SSDT)
- Info on GPU injection via DSDT
- More info on GPU injection via DSDT
- Info on GPU injection via SSDT
- Using X99 Injector USB 3.kext instead of SSDT-UIAC.aml (don't recommend since it requires the 15 to 20 USB port limit patch to be active, but OK to use for now)
- Utilizing "Drop Tables" for your config.plist
- Common MaciASL errors

- Build and run AppleIntelInfo.kext (for checking CPU PM states)

- Checking for XCPM properties and FrequencyVectors (for checking that CPU PM is active)

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 located at _SB.PCI0.BR1B.H000 -- 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/Beta/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 to determine which SMBIOS version will be the best suited for your particular CPU.

EFI_ASUS-PRO-USB3.1_10.12.3_FIX2DRV-FREE.zip

EFI_ASUS-PRO-USB3.1_10.12.3_FIXDRV-512MB.zip

mfc88 · January 30, 2017

As I said I am with the last Clover r3994 and in fact, everything worked again as soon as I deactivated all xcpm patches. Although the patches are disabled, now I will delete them from the plist and test to see how it behaves

Let me know what your results are. Curious if this is just a Clover bug or if your CPU is natively supported.

Fergarth · January 30, 2017

I just tested and confirmed that it is a Clover bug. As I mentioned before, with 12.2 and 12.3 and with the previous Clover I had no stress. I started having it from the moment I updated to 12.4 and upgraded to the Clover r3994, since the previous version of Clover did not finish the boot in 12.4

And the result was this:

With all xcpm patchs enabled in Plist - Cpu blocks at maximum frequency.
With all xcpm patchs disabled in Plist - Everything works normally and loaded.
With all xcpm patchs deleted in Plist - Cpu blocks at maximum frequency.

Toooorch · January 30, 2017

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.

mfc88 · January 30, 2017

I just tested and confirmed that it is a Clover bug. As I mentioned before, with 12.2 and 12.3 and with the previous Clover I had no stress. I started having it from the moment I updated to 12.4 and upgraded to the Clover r3994, since the previous version of Clover did not finish the boot in 12.4

And the result was this:

With all xcpm patchs enabled in Plist - Cpu blocks at maximum frequency.

With all xcpm patchs disable in Plist - Everything works normally and loaded.

With all xcpm patchs deleted in Plist - Cpu blocks at maximum frequency.

Sounds like they reversed the disabled/enabled flags.

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

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