Jump to content

maleorderbride

maleorderbride

Member Since 17 Jan 2009
Offline Last Active Dec 03 2016 10:00 PM
-----

Posts I've Made

In Topic: [Guide] Mac OSX 10.12 with X99 Broadwell-E family and Haswell-E family

13 November 2016 - 11:59 PM

The only thing that proves what I said is these prints. Whether OSX supports it or not, it seems to me it supports. And as I said, it takes the maximum RAM speed and increases the GB score if I select XMP in Profile 1. With XMP disabled, it shows only the base speed 2333Mhz and the GB obviously decreases!

Doubts? :P

 

Can you post your extended GB changes pre and post XMP?

I have always been curious about the impact.

In Topic: [Guide] Mac OSX 10.12 with X99 Broadwell-E family and Haswell-E family

13 November 2016 - 05:51 PM

My computer hangs on startup now.

 

Removing SMC patch.

 

Perhaps you can post your FakeSMC.kext + DSDT so we can look directly?

In Topic: Haswell E Powermanagement yet another option

13 November 2016 - 05:49 PM

After sleep, GB runs will no longer max cpu, loses 'bout 4000 point in GB score.

http://www.insanelym...mily/?p=2316786

 

Looks like a GB BIOS setting.

In Topic: [Guide] Mac OSX 10.12 with X99 Broadwell-E family and Haswell-E family

13 November 2016 - 05:33 PM

Its come like this

 

What edits do you make to DSDT in total? What effect do they have?

 

 

Why not add this SMC device via SSDT? It seems easier and would be compatible with any motherboard then.

In Topic: Haswell E Powermanagement yet another option

12 November 2016 - 03:41 AM

Thanks for this great work Brumbaer.

 

This allows me to reach all of the same P-states with all core turbo that I can with other methods, however it appears that my single-core multiplier is not going above non-turbo. Energy usage and temps appear normal with ~20W at idle and often near 1.2GHz.

 

I have a very uncommon CPU in this build, it is an E5-2693 V3, which is some sort of early ES that never made it to market. It is a 2.8Ghz 12-core, 3.1GHz all core turbo (no method in MacOS ever gets me higher than 3.0GHz all core), and 3.4GHz turbo single core.

 

This method seems to cap my single core turbo at 2.8GHz instead, or perhaps even lower.

 

I have EIST, C-States, Turbo, and C1E enabled in the BIOS. I will try modifying other BIOS settings, but it looks like the kext does not handle my single core P-states properly.

© 2016 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy