Contribute
Register

PluginType=1 option?

Status
Not open for further replies.

the-braveknight

Moderator
Joined
Nov 24, 2015
Messages
1,220
Motherboard
Lenovo Legion Y520 (Clover)
CPU
i7-7700HQ
Graphics
HD 630 (1920x1080) + Nvidia GTX 1060
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Hello all,
Anyone knows if it's reliable to use "plugin-type"=1 to enable power management via native CPU SSDTs on Haswell systems? Or it's better to stuck with SSDT.aml generated by ssdtPRGen.sh script?
 
Hello all,
Anyone knows if it's reliable to use "plugin-type"=1 to enable power management via native CPU SSDTs on Haswell systems? Or it's better to stuck with SSDT.aml generated by ssdtPRGen.sh script?

Evidence suggests you need both "plugin-type"=1 inject and APSS, ACST, etc.
 
Evidence suggests you need both "plugin-type"=1 inject and APSS, ACST, etc.

I see... that means I still have to use the SSDT generated by the script.
 
Last edited:
I landed on this thread when trying to diagnose "vanilla" PowerManagement for my old Xeon E5450 on a Gigabyte GA-G31M-S2L (Socket 771->775 conversion). Setting PluginType=1 in Clover r4439 config.plist enabled SpeedStep. Prior to enabling PluginType=1, I had installed NullCPUPowerManagement.kext. Now that PluginType=1 is set, I no longer need NullCPUPM.kext.

I don't understand why, but for others who land here, PluginType=1 may solve power management issues on your legacy systems.
 
Status
Not open for further replies.
Back
Top