Jump to content

Haswell E Powermanagement yet another option


Brumbaer
 Share

109 posts in this topic

Recommended Posts

  • 5 months later...
  • 5 months later...
  • 1 month later...
  • 6 months later...

Hello

THANK YOU for this Kext. Very good performance and very low consumption in idle.

 

I'm using it with Opencore, and it's the only way for me to have good performance and good speedsteps. On my machine, Opencore XCPM does not work very good, idle is fine but poor performance during load. This problem is solved with the use of this Kext.

 

Some things:

  • During load, Intel Power Gadget display a wrong information about Core Util., 50 instead of 100. Strange but minor problem.
  • Is there anything I have to check to use it with Opencore? Don't want to create conflicts or hardware issues. Should I disable CPU SSDT or CPU Fake ID in Opencore?

load.png

Link to comment
Share on other sites

I confirm that this patch works well on X99 / 5820k / 10.15.4 / Opencore 0.5.6.

The only problem is that Intel Power Gadget display wrong information about the "CORE Utilization". The information on activity monitor are correct.

Link to comment
Share on other sites

  • 4 months later...

With the PMDrv.kex driver without mask as Haswell and quirk AppleXcpmExtraMsrs in OpenCore, I have only 4 p-states. And the highest of them is only 2900 MHz. With the PMDrv.kext driver, but with mask as Haswell and quirk AppleXcpmExtraMsrs, I already have 9 p-states. Moreover, the highest state is 3300 MHz. It is very important!
Before (just with PMDrv):

585651167_Screenshot2020-08-21at20_14_42.thumb.png.7630f9add228903cf0a8b0901adbfbb7.png

After (with PMDrv + mask and quirk):

2113987236_Screenshot2020-08-21at20_08_08.thumb.png.991a16c67d63fe3a597478e56ac984d0.png

 

Is it possible to do something so that with the PMDrv.kext driver all states work without kernel patches?

 

P.S. Only I did not understand one thing. Why does not the multithread rate increase with increasing single thread???

Link to comment
Share on other sites

  • 2 months later...
  • 3 months later...

I found that the boot stop, which is often called by the PMDrv.kext driver in bigsur, is identical to the stop that is observed if npci = 0x2000 is removed from bootargs, i.e. the loading stops at exactly the same place. 

photo_2021-02-03_19-46-21.thumb.jpg.5f6dcf357769fd27d7d197ad2551a7f7.jpg

 

How can this be related?

  • Like 1
Link to comment
Share on other sites

 Share

×
×
  • Create New...