x99 12 core Xeon E5-2670 power management issue

[Grubersky]

Hi community,

I got my x99 Hackintosh, after a lot of trial and error, finally with Yosemite running. It performs quite stable, yet the CPU can't perform its full potential. The score I get in Geekbench is mostly around 27'000, but goes sometimes randomly down to around 20'000-25'000. On a windows installation, I get always a score around 28'000. DPCI Manager tells me that the CPU multiplier is always 25, so I guess there's a lack of cpu power management. Sleep also doesn't work, I guess that's related?

My post installation is based on robinqu's instruction:
http://www.tonymacx86.com/threads/12-core-x99-hackintosh-pro-build.170818/

He says that he couldn't activate the cpu power management at that time, is this still the case or is there a specific approach to do so?

My hardware:

Gigabyte x99p-sli
12 core Xeon E5-2670 (Haswell-E) base clock 2200/2500 turbo 2800
8x8GB HyperX 2666
Titan X (Maxwell)
Samsung SM951 NVME 512GB M2

OSX: Yosemite 10.10.5 Build 14F27

Installed kexts in System/Library/Extensions are:
- AppleACPIPlatform.kext
- fakesmc.kext
- IOPCIFamily.kext
- VoodooTSCSync.kext

Installed kexts and efis in clover plus settings of config.plist are shown in the attached pictures.


It's my first Hackintosh and I figured out a lot by myself, but I just can't get the hang of this.
A clue in the right direction would be highly appreciated.

Best,
Marco

 

[Grubersky]

A little update:
I discovered that the OpenGL performance is pretty poor. (Got like 34 fps in Cinebench) Also playing a h.264 clip with Quicktime has issues. (stuttering, drop frames and these kinda things)

Cuda computing on the other hand works like a charm. Though Cuda is only related to the GPU anyway, but I don't know how OpenGL is implemented and if this issue is related to this whole CPU power management thing?

I also got audio half working. I have sound on the front panel, go figure... I thought normally the opposite is the case...

Best,
Marco

 

[Grubersky]

Would extracting an SSDT from a Windows installation may be the right approach? Or is this only an option for OSX nativ supported cpu architectures?

Marco