Jump to content

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


nmano
 Share

1,954 posts in this topic

Recommended Posts

I also have problems with intel power gadget:
 
post-31099-0-46094900-1480697193_thumb.jpg
 

I created a new SSDT with MACPRO6,1 and frequencyvector iMac14,2 -Turbo 4600 

 

post-31099-0-04649200-1480697459_thumb.jpgpost-31099-0-86847900-1480702741_thumb.jpgpost-31099-0-82431200-1480702764_thumb.jpgpost-31099-0-72766700-1480702771_thumb.jpg

 

Everything seems to work properly, but in the system information - pci cards I do not find anything

post-31099-0-84852700-1480702751_thumb.jpg

 
I am attaching my configuration, can you tell me if everything is correct?

 

DarwinDumper : DarwinDumper_3.0.2_02.12_17.42.09_MacPro6,1_AMI_X64_3949_Sierra_16B2555_gabriele 17.45.42.zip

 

IoJones log : Gabriele’s Mac Pro.zip

 

EFI : http://jmp.sh/IYyVnj9

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...............................: 0x1875ee55a0ff (814 MHz)
MWAIT C-States...........................: 8480

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

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

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

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

MSR_PLATFORM_INFO................(0xCE)  : 0x20080C3BF3812100
------------------------------------------
 - Maximum Non-Turbo Ratio.............. : 0x21 (3300 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)  : 0x400
------------------------------------------
 - I/O MWAIT Redirection Enable......... : 1 (enabled, IO read of MSR(0xE4) mapped to MWAIT)
 - CFG Lock............................. : 0 (MSR not locked)
 - C3 State Auto Demotion............... : 0 (disabled/unsupported)
 - C1 State Auto Demotion............... : 0 (disabled/unsupported)
 - C3 State Undemotion.................. : 0 (disabled/unsupported)
 - C1 State Undemotion.................. : 0 (disabled/unsupported)
 - 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 (C6 is the max C-State to include)

IA32_MPERF.......................(0xE7)  : 0x7816B94448
IA32_APERF.......................(0xE8)  : 0xA56B947C59

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

MSR_IA32_PERF_STATUS.............(0x198) : 0x29F900002E00
------------------------------------------
 - Current Performance State Value...... : 0x2E00 (4600 MHz)

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

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

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

IA32_THERM_STATUS................(0x19C) : 0x88400000
------------------------------------------
 - 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...................... : 64
 - 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) : 0x670A00
------------------------------------------
 - Turbo Attenuation Units.............. : 0 
 - Temperature Target................... : 103
 - 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) : 0x22222E2E2E2E2E2E
------------------------------------------
 - Maximum Ratio Limit for C01.......... : 2E (4600 MHz) 
 - Maximum Ratio Limit for C02.......... : 2E (4600 MHz) 
 - Maximum Ratio Limit for C03.......... : 2E (4600 MHz) 
 - Maximum Ratio Limit for C04.......... : 2E (4600 MHz) 
 - Maximum Ratio Limit for C05.......... : 2E (4600 MHz) 
 - Maximum Ratio Limit for C06.......... : 2E (4600 MHz) 

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

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

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) : 0x7FFF80015FFF8
------------------------------------------
 - Package Power Limit #1............... : 4095 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....... : 10 (2560 milli-Seconds)
 - Package Power Limit #2............... : 4095 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) : 0x5E38F1
------------------------------------------
 - Total Energy Consumed................ : 376 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) : 0x21
MSR_CONFIG_TDP_LEVEL1............(0x649) : 0x940000001E0460
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) : 0x0
MSR_PKG_C6_RESIDENCY.............(0x3f9) : 0x0

IA32_TSC_DEADLINE................(0x6E0) : 0x1875F0F425B9

CPU Ratio Info:
------------------------------------------
Base Clock Frequency (BLCK)............. : 100 MHz
Maximum Efficiency Ratio/Frequency.......: 12 (1200 MHz)
Maximum non-Turbo Ratio/Frequency........: 33 (3300 MHz)
Maximum Turbo Ratio/Frequency............: 46 (4600 MHz)
P-State ratio * 100 = Frequency in MHz
------------------------------------------
CPU P-States [ (12) 43 46 ]
CPU C6-Cores [ 1 3 5 7 9 11 ]
CPU P-States [ (12) 19 43 46 ]
CPU C6-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 ]
CPU P-States [ (12) 19 23 43 46 ]
CPU P-States [ (12) 19 23 43 45 46 ]
CPU P-States [ (12) 19 23 32 43 45 46 ]
CPU P-States [ (12) 19 23 25 32 43 45 46 ]
CPU P-States [ (12) 19 21 23 25 32 43 45 46 ]
CPU P-States [ (12) 19 21 23 24 25 32 43 45 46 ]
CPU P-States [ 12 19 21 23 24 25 29 32 43 45 (46) ]
CPU P-States [ 12 19 21 23 24 25 28 29 32 43 45 (46) ]
CPU P-States [ (12) 19 21 22 23 24 25 28 29 32 43 45 46 ]
CPU P-States [ (12) 19 21 22 23 24 25 27 28 29 32 43 45 46 ]
CPU P-States [ (12) 19 21 22 23 24 25 27 28 29 32 35 43 45 46 ]
CPU P-States [ (12) 19 21 22 23 24 25 27 28 29 32 34 35 43 45 46 ]
CPU P-States [ (12) 19 21 22 23 24 25 27 28 29 32 34 35 36 43 45 46 ]
CPU P-States [ 12 19 21 22 23 24 25 27 28 29 32 34 35 36 38 43 45 (46) ]
CPU P-States [ (12) 19 21 22 23 24 25 27 28 29 31 32 34 35 36 38 43 45 46 ]
CPU P-States [ (12) 19 21 22 23 24 25 27 28 29 31 32 34 35 36 38 39 43 45 46 ]
CPU P-States [ 12 19 21 22 23 24 25 27 28 29 31 32 34 35 36 38 39 40 43 45 (46) ]
CPU P-States [ (12) 19 21 22 23 24 25 27 28 29 31 32 34 35 36 37 38 39 40 43 45 46 ]
CPU P-States [ 12 19 21 22 23 24 25 27 28 29 31 32 34 35 36 37 38 39 40 41 43 45 (46) ]
CPU P-States [ 12 19 21 22 23 24 25 27 28 29 31 32 34 35 36 37 38 39 40 41 43 44 45 (46) ]
CPU P-States [ 12 19 21 22 23 24 25 27 28 29 31 32 34 35 36 37 38 39 40 41 42 43 44 45 (46) ]
CPU P-States [ (12) 19 21 22 23 24 25 26 27 28 29 31 32 34 35 36 37 38 39 40 41 42 43 44 45 46 ]
CPU P-States [ 12 19 21 22 23 24 25 26 27 28 29 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 (46) ]
CPU P-States [ (12) 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 ]
CPU P-States [ (12) 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 ]
Link to comment
Share on other sites

So I am also building a system.

I am currently directly installing to a SSD from my old Hackintosh.

Basically the system will be

- ASUS Deluxe II X99

- Intel Core I7 6900k Processor

- 2 x 16 Gb DDR4 RAM

- 1 x 256 Gb Samsung 840 Evo

So my questions:

 

Is it advisable to install from my old Hack or better to use a USB installer?

 

I will use a unlocked bios, anyone has a EFI folder  could use as a starting point?

 

ASUS released a new bios version 1401.... is it save to patch with exiting UEFIpatch?

 

Any other reference point that might help?

 

For me the most important things are:

- sleep and speedstep to work as good as possible.

 

Any feedback and help appreciated.

 

Many thanks, Mike

 

I am currently reading through this thread but still all quite new.

  • Like 1
Link to comment
Share on other sites

 

I also have problems with intel power gadget:
 
Everything seems to work properly, but in the system information - pci cards I do not find anything

With Ai Overclock Tuner to manual, (or even change other overclock settings in the Uefi Bios), you have the same speed in all colors, but Intel Power Gadjet no longer quantifies the Power line.

In order to see PCI Devices in "About this Mac", you need a DSDT exclusively made for your Board and other Hardware you have.

User Nmano helped many of us create the DSDT.

So I am also building a system.

I am currently directly installing to a SSD from my old Hackintosh.

Basically the system will be

- ASUS Deluxe II X99

- Intel Core I7 6900k Processor

- 2 x 16 Gb DDR4 RAM

- 1 x 256 Gb Samsung 840 Evo

So my questions:

 

Is it advisable to install from my old Hack or better to use a USB installer?

 

I will use a unlocked bios, anyone has a EFI folder  could use as a starting point?

 

ASUS released a new bios version 1401.... is it save to patch with exiting UEFIpatch?

 

If I were to do it, I would undoubtedly create a new installation.

If you install the new Bios from the Asus site, you will no longer have Bios unlocked, unless you know how to unlock it again. Now I'm not in the Hack, but in mobile phone, but then I put my last EFI to post installation with everything working, if you choose to do new install. But yes, it is advisable to continue reading this whole topic. There are lots of info, plists, patchs, Efis, from users with Asus boards.

Link to comment
Share on other sites

Is it advisable to install from my old Hack or better to use a USB installer?

 

You can clone it if you want to save yourself time. I've cloned my SDDs many, many, many times and all have been initially--before any testing--stable (when using OsxAptioFix2Drv-free2000.efi). It's a great time saver, especially if you want to test out an OS update or ktext. No point in going thru the hassle of setting up a new station from scratch... just to have it bricked by an update, ktext, or clover patch.  

 

How I set up my system:

- Samsung 950 NVMe Pro - primary system (must be 100% stable--not necessarily 100% functional)

- Samsung 850 PRO - clone of primary for testing

- Samsung 830 EVO - clone of 850 for testing

- Samsung Hybrid 2TB - backup of primary just in case!

 

What I use (this will copy EVERYTHING, including the EFI boot folder):

Carbon Copy Cloner

 

Source:

950 Pro

 

Target:

850 Pro, 830 Evo, Hybrid

 

So... NEVER touch your primary set up unless you're 1000% sure the system is at the bare-minimum STABLE. And by stable, I mean... testing for it up to a week or even a month before committing to update the primary.

Link to comment
Share on other sites

 

You can clone it if you want to save yourself time. I've cloned my SDDs many, many, many times and all have been initially--before any testing--stable (when using OsxAptioFix2Drv-free2000.efi). It's a great time saver, especially if you want to test out an OS update or ktext. No point in going thru the hassle of setting up a new station from scratch... just to have it bricked by an update, ktext, or clover patch.  

 

How I set up my system:

- Samsung 950 NVMe Pro - primary system (must be 100% stable--not necessarily 100% functional)

- Samsung 850 PRO - clone of primary for testing

- Samsung 830 EVO - clone of 850 for testing

- Samsung Hybrid 2TB - backup of primary just in case!

 

What I use (this will copy EVERYTHING, including the EFI boot folder):

Carbon Copy Cloner

 

Source:

950 Pro

 

Target:

850 Pro, 830 Evo, Hybrid

 

So... NEVER touch your primary set up unless you're 1000% sure the system is at the bare-minimum STABLE. And by stable, I mean... testing for it up to a week or even a month before committing to update the primary.

Carbon Copy Cloner will not clone your EFI partition but only your primary partition and if you want the recovery partition. To copy your EFI in a cloned drive you must install clover again and set as destination the cloned ssd/hd

  • Like 1
Link to comment
Share on other sites

Thanks for the tips

My current Hackintosh is pretty old.... a Z77 chipset, about 4 years.

My spec above is now almost assembled.

 

So the thing I did was install Sierra 12.1 on a SSD by USB attachment.

This SSD I will then hookup to the new X99 machine.

 

So would it be possible to do all patching stuff for the first boot in the new machine from my old Hack (Z77) and then boot into the new one hooked up to the new machine.

What kind of patches are not possible to pre-install?

 

Obviously a pre-built efi folder would help a lot.

 

I plan to use the unlocked bios and flash it to my MB.

 

Cheers, Mike

  • Like 1
Link to comment
Share on other sites

Thanks for the tips

My current Hackintosh is pretty old.... a Z77 chipset, about 4 years.

My spec above is now almost assembled.

 

So the thing I did was install Sierra 12.1 on a SSD by USB attachment.

This SSD I will then hookup to the new X99 machine.

 

So would it be possible to do all patching stuff for the first boot in the new machine from my old Hack (Z77) and then boot into the new one hooked up to the new machine.

What kind of patches are not possible to pre-install?

 

Obviously a pre-built efi folder would help a lot.

 

I plan to use the unlocked bios and flash it to my MB.

 

Cheers, Mike

 

Hi Mike Ranger, this is Fergarth Marine. I'm not kidding, i´m a Portuguese Marine!

From what I understand, you'll use an Asus X-99. If you want, try my EFI. Just generate your serial number with Clover Configurator. 

But remember, my DSDT is specific to my hardware (see my signature). I refer to the mainly graphics card, because the board does not change much.

For all USB working, set this in Bios.

Intel XHCI Mode - Smart Auto

EHCI Legacy Support - Enable

XHCI Hand-off - Enable

EHCI Hand-off – Enable

EIST – Disable

Secure Boot – Other OS

The rest I have by default, because at the moment I do not use overclocking.

​Good luck!

EFI.rar

Link to comment
Share on other sites

Hi Fergarth

 

Very pleased to meet you here. I was not a marine, but was in the Swiss Army. Portugal is a great country with very friendly people.

 

Regarding your help:

Many thanks!! This is great!

I will start your EFI as a starting point and do as advised.

Furthermore, I will flash the unlocked bios.

 

Once I have a stable system, I will then try the next step which is the new Samsung 960 Evo NVME SSD.

But step after step.

I will use the system mainly for Photo-Editing and Movie Cutting.

I will report back.... will be some time until I have things up and running.

Another goal will be to have a very silent setup. So my whole system uses a silent case and special silent cooling.

 

Great forum!!

 

Cheers, Mike

  • Like 1
Link to comment
Share on other sites

Hi Fergarth

 

Very pleased to meet you here. I was not a marine, but was in the Swiss Army. Portugal is a great country with very friendly people.

 

Regarding your help:

Many thanks!! This is great!

I will start your EFI as a starting point and do as advised.

Furthermore, I will flash the unlocked bios.

 

Once I have a stable system, I will then try the next step which is the new Samsung 960 Evo NVME SSD.

But step after step.

I will use the system mainly for Photo-Editing and Movie Cutting.

I will report back.... will be some time until I have things up and running.

Another goal will be to have a very silent setup. So my whole system uses a silent case and special silent cooling.

 

Great forum!!

 

Cheers, Mike

Thank you Mike for the kind words! I have learned a lot here and I am happy to help those who need it in what I can.

Just one more warning, my SSDT for PM was generated for my processor. Creates a specific one for yours, which seems to be different.

For NVMe devices, see post #690 by mfc88. There you have access to his plist with several patches for NVMe SSDs.

Link to comment
Share on other sites

Carbon Copy Cloner will not clone your EFI partition but only your primary partition and if you want the recovery partition. To copy your EFI in a cloned drive you must install clover again and set as destination the cloned ssd/hd

Oops, been awhile since I had to do a copy on a fresh disk.

 

However, if I'm not mistaken, you'll only need to run EFI Boot Loader once on the fresh drive. If you reinstall, repartition, or re-clone, the EFI root folder remains intact, albeit emptied. You'll just have to mount the hidden EFI folder and copy over an EFI folder into its empty hidden EFI folder.

  • Like 1
Link to comment
Share on other sites

Oops, been awhile since I had to do a copy on a fresh disk.

 

However, if I'm not mistaken, you'll only need to run EFI Boot Loader once on the fresh drive. If you reinstall, repartition, or re-clone, the EFI root folder remains intact, albeit emptied. You'll just have to mount the hidden EFI folder and copy over an EFI folder into its empty hidden EFI folder.

Don't be confused....to clone your primary ssd/hd/nvme etc you must (i suggest you to use this) use Carbon Copy Cloner. It will make an exact copy of your ssd. But to have an EFI partition you must install clover in the new cloned drive then after created a new EFI partition in the new drive you can copy your original EFI into the new ssd. Remember CCC don't create or clone clover EFI partitions!

Link to comment
Share on other sites

Dear Forum mates.... this is a really helpful start for me.... 

I will do as advised but will take a couple of days for sure.... :)

 

Aiii..... I never created my own SSDT.aml...... thats another challenge I did not forsee.... :w00t:

 

Well.... I guess figuring out these things is the fun part right?

 

I read something about a PikerAlpha script for that.... I will investigate.... hopefully the script can be used without any further magic to be applied

 

Cheers, Mike

  • Like 1
Link to comment
Share on other sites

Don't be confused....to clone your primary ssd/hd/nvme etc you must (i suggest you to use this) use Carbon Copy Cloner. It will make an exact copy of your ssd. But to have an EFI partition you must install clover in the new cloned drive then after created a new EFI partition in the new drive you can copy your original EFI into the new ssd. Remember CCC don't create or clone clover EFI partitions!

 

Nonsense partitioning a drive GPT is what creates the EFI partition once that is done for a new install all that needs to be done after cloning is mount the hidden EFI on both drives and copy over the old EFI directory to the new partition. The EFI booting on the motherboard then takes care of the loading of the boot???.efi in that partition/folder contained in it when it starts up.

Link to comment
Share on other sites

Dear Forum mates.... this is a really helpful start for me....

I will do as advised but will take a couple of days for sure.... :)

 

Aiii..... I never created my own SSDT.aml...... thats another challenge I did not forsee.... :w00t:

 

Well.... I guess figuring out these things is the fun part right?

 

I read something about a PikerAlpha script for that.... I will investigate.... hopefully the script can be used without any further magic to be applied

 

Cheers, Mike

To generate your own SSDT, download the latest ssdtPRGen.sh beta by entering the following command in terminal:

 

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

 

After the download is done, run these two commands on the terminal:

 

chmod +x ~/ssdtPRGen.sh

 

sudo ./ssdtPRGen.sh -x 1

 

Follow the instructions answering n, n.

 
To access the generated ssdt.aml, open Finder and in menubar choose Go/Go to Folder and type:

 

~/Library/ssdtPRGen/

 

Mount EFI partition and copy the ssdt.aml to EFI/EFI/CLOVER/ACPI/patched.

 

More info here:

https://github.com/Piker-Alpha/ssdtPRGen.sh/blob/Beta/README.md

 

To add freqvectors read this:

https://github.com/Piker-Alpha/freqVectorsEdit.sh

  • Like 1
Link to comment
Share on other sites

In order to generate your SSDT, you can download the latest ssdtPRGen.sh beta by entering the following command in terminal:

 

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

 

After the Sript donwload, run this in terminal:

 

sudo ./ssdtPRGen.sh -x 1

 

Then follow the instructions answering N, N.

 

Open Finder and in menubar choose Go/Go to Folder...

 

Type ~/Library/ssdtPRGen/ to acess the generated ssdt.aml

 

Mount EFI partition and copy the ssdt.aml to EFI/EFI/CLOVER/ACPI/patched.

 

More info here:

https://github.com/Piker-Alpha/ssdtPRGen.sh/blob/Beta/README.md

 

To add freqvectors read this:

https://github.com/Piker-Alpha/freqVectorsEdit.sh

 

After you download (curl) you'll want to run this necessary command to make the file executable by the user (else, you'll get the "permission denied" error):

chmod +x ~/ssdtPRGen.sh
  • Like 1
Link to comment
Share on other sites

 

 

After you download (curl) you'll want to run this necessary command to make the file executable by the user (else, you'll get the "permission denied" error):

chmod +x ~/ssdtPRGen.sh
Tanks, I forgot, but I've already corrected it.
Link to comment
Share on other sites

Nonsense partitioning a drive GPT is what creates the EFI partition once that is done for a new install all that needs to be done after cloning is mount the hidden EFI on both drives and copy over the old EFI directory to the new partition. The EFI booting on the motherboard then takes care of the loading of the boot???.efi in that partition/folder contained in it when it starts up.

My post was a reply to an user who assumed that with CCC clover EFI partition would be cloned too....i know that partitioning a drive GPT will create an EFI partition!! My EFI "text" was referred to Clover EFI partition...not physical EFI partition on drive!

  • Like 1
Link to comment
Share on other sites

Small update: Sleep is broken if I use a Display Port connector to plug in my monitor versus HDMI! Everything goes to sleep, but upon wake, it immediately resets my computer OR I just get a "no signal detected" screen. Weird...    :wallbash:  

Link to comment
Share on other sites

What options do you have in: Settings - saving energy?

On my pc there is only the option to turn off the monitor but there is no option for standby pc...

 

I set SMBIOS macpro6,1 and frequencyvector macbookpro12,1

I also tried frequencyvector iMac14,2 ...

 

it seems that there are no problems with the management of the P and C states, but I'd like to manage standby when I want.

Link to comment
Share on other sites

Small update: Sleep is broken if I use a Display Port connector to plug in my monitor versus HDMI! Everything goes to sleep, but upon wake, it immediately resets my computer OR I just get a "no signal detected" screen. Weird...    :wallbash:

 

That's weird! I always had my 4K connected by DP and it works correctly after waking up! Maybe you have some definition or patch to interfere with it. If you think it might be useful, take a look at my last plist and compare the settings and patches.
Link to comment
Share on other sites

What options do you have in: Settings - saving energy?

On my pc there is only the option to turn off the monitor but there is no option for standby pc...

 

I set SMBIOS macpro6,1 and frequencyvector macbookpro12,1

I also tried frequencyvector iMac14,2 ...

 

it seems that there are no problems with the management of the P and C states, but I'd like to manage standby when I want.

 

Just "Prevent computer from sleeping when the display is off" (can't uncheck since I set "Turn off display after: Never"). This option doesn't interrupt manual sleep!

 

I manually sleep by going here:

 

792kEzO.png

 

That's weird! I always had my 4K connected by DP and it works correctly after waking up! Maybe you have some definition or patch to interfere with it. If you think it might be useful, take a look at my last plist and compare the settings and patches.

I think my monitor is just acting up in general. Might need to replace it (I get random "Out of range" errors and now I'm getting random black screens that resolve after a few seconds). The damn thing is only a few months old!!!

 

I talked to EVGA (my GPU manufacturer) and they said it could be: Monitor, power supply, graphics card or motherboard... so, I've been putting off trying to fix it so I can continue to work!

 

For now, the HDMI port works 99% (displaying a signal) of the time and I can continue to use sleep with it. 

 

EDIT: Sleep causes KP and immediate restart now. OHHHH WELLL.

  • Like 1
Link to comment
Share on other sites

#X99_Gold pack

#X99 DSDT with sleep+SSDT with devices patches.

#ACPI/DSDT/Patches and add DTGP in config.plist

#Add your SSDT files in EFI(Make your Devices and patches)

#Restart

#Open MaciASL.app patch to DSDT /just compile and sleep

#Drop your DSDT in EFI

#Restart

#Now DSDT and SSDT hack devices and make sleep.

#I made X99_Injector LPC.kext this kext no need any LPC patch.

#Don't forget to like  posts

#too many restart but Fixed.

#test each ssdt (you have to rename api-path)

#check your  path (IOACPIPlane:/_SB/PCI0@0/HDEF@1b0000)

#I made 18 SSDT

#If you want SSDT with sleep ask rehapman He is king.

#Enjoy.

 

 

X99_Gold.zip

post-413859-0-21211000-1480909768_thumb.jpg

post-413859-0-50442400-1480909775_thumb.png

  • Like 3
Link to comment
Share on other sites

@nmano:

Are you suggesting this is a universal solution for all X99 boards for 10.12?

What do I need to consider for my setup if I go your path?

 

Processor: i7 6900K

Board: Asus Deluxe II X99

Graphics: Gigabyte 980Ti

RAM: 2x 16 Gb DDR 4

SSD: Samsung 850 Evo 256 Gb

 

Thanks, Mikel

  • Like 1
Link to comment
Share on other sites

I'm lost at line 4.
I'm sorry but I'm a beginner on dsdt and co.

 

let's start:
 

 

#X99_Gold pack

#X99 DSDT with sleep+SSDT with devices patches.

#ACPI/DSDT/Patches and add DTGP in config.plist

Should I include in my config.plist the following patches from your config.plist ?:

 
DSDT Patches
AddDTGP And FixTMR
The Drop Tables
DropOEM
KextsToPatch
KernelToPatch
_________________________________________
 

 

#Add your SSDT files in EFI(Make your Devices and patches)

#Restart

Now in the efi folder which SSDT files I need to add?
The only SSDT I have is that I generated for p and c states.
MaciASL 1.4 can not open your SSDT files. Only MaciASL 1.3 succeeds but returns errors during processing in "external method".
_________________________________________
 

 

#Open MaciASL.app patch to DSDT /just comfile and sleep

#Drop your DSDT in EFI

#Restart

#Now DSDT and SSDT hack devices and make sleep.

Should I apply the patch "X99_comfile and sleep" to original DSDT extracted with clover?

Now, the new files into the efi folder overwriting the old?
_________________________________________
 

 

#I made X99_Injector LPC.kext this kext no need any LPC patch.

#Don't forget to like  posts

#too many restart but Fixed.

#test each ssdt (you have to rename api-path)

#check your  path (IOACPIPlane:/_SB/PCI0@0/HDEF@1b0000)

#I made 18 SSDT

#If you want SSDT with sleep ask rehapman He is king.

#Enjoy.

 

 

X99_Gold.zip

"X99_Injector LPC.kext" in the efi folder.
 
How many things I did wrong if not all?
  • Like 1
Link to comment
Share on other sites

nmano notices more of DSDT, SSDT and MaciasL than we all together, but has the strange habit of dropping the bomb and then disappear lol. Do not misunderstand nmano, I was kidding, because it is not true and you have helped many of us to have a DSDT, but if you can, explain in more detail what we should do if you please.

Greetings nmano :D 

  • Like 1
Link to comment
Share on other sites

 Share

×
×
  • Create New...