macOS Native CPU/IGPU Power Management

[Edhawk]

This is the output from Intel Power Gadget for my i7-4790K CPU.



As you can see more than just the few Power settings you are seeing. This is running macOS Ventura on my iMac 1 system in my signature. Using the SSDT-PLUG.aml generated from my system DSDT.aml and Corpnewt's SSDTTime python script.

I can't use the PluginType option as I am using OpenCore not Clover.

I don't think your ideas of what CPU power management involves is wrong. It just isn't working on your system.

This could be due to another config.plist entry, which clashes with, or fails to implement the CPU PM settings. The most likely place for this is the KernelAndKextPatches section of your config.plist.

These are the Kernel Settings you are currently using.

All set to False.

These are the Kernel Settings I used with my Haswell systems.

Not all set to False.

You may want to try changing the three settings Enabled/True above in your setup. While using the Generate > PluginType=True option.

Revised config.plist for Haswell system.

I have attached a copy of a config.plist I would use with a Haswell system like yours. Have a look at it and see the differences between your and my config's.

The biggest differences are as follows:

1. I have the IGPU framebuffer (Headless) in the Device > Properties section of the config.plist, not the Graphics section.
2. The only entry in the Graphics section is the 'RadeonDeInit=true' option.
3. I use the iMac15,1 SMBIOS for macOS up to and including Big Sur (no serial etc. in the config), not the iMac14,2 SMBIOS.

If you want to try this config.plist just regenerate the iMac15,1 SMBIOS in Clover Configurator and check it against the Apple Services database using the Check Coverage button.

Copy your current EFI to the EFI partition on a spare USB drive, and replace your current config with this one, after renaming it to config.plist.

You may need to use the F11 key to clear NVRAM and reboot the system, when you reach the Clover boot screen. This needs to be done before you try to boot macOS, otherwise some settings from your current config may clash with the new settings.

If you post a copy of your system DSDT.aml I could generate an SSDT-PLUG.aml for your system.

 

[VirtualRecess]

Thank you for the help.

Though unfortunately there was no success in the suggestions you listed. Had been trialing them among others over the past few days. (Happy to drop my DSDT.aml for you to look at below as well)

This is the output from Intel Power Gadget for my i7-4790K CPU.

View attachment 560721

As you can see more than just the few Power settings you are seeing. This is running macOS Ventura on my iMac 1 system in my signature. Using the SSDT-PLUG.aml generated from my system DSDT.aml and Corpnewt's SSDTTime python script.

The thing thats got me running in circles reading through a lot of the reported working PM posts, is the use of the latest Intel Power Gadget. This version [v3.7.0] is only able to report the CPU Clock speed averages.

For example. This is what I can see If i load up Intel App v3.7.0 (Settings@150ms SUR + @150ms SR)

Could be seen as PM working ?

Now if i swish back to v3.5.5 which displays realtime CPU clock speeds [Settings@150ms SUR + @150ms SR]

Confirms PM is not working on the same config. It also now matches whats reported on HWMonitor.

If you still have access to your Haswell System. I would be curious if you could post the results of the Intel Power Gadget at the version and settings i mentioned above.

Starting to lose hope with this system of mine as no matter what i throw at it, nothing seems to get it to play ball.

Probably the last option might just be to switch to a new boot loader like OpenCore

 

[Edhawk]

This screenshot shows the power states available to your CPU (taken from your Hackintool_AppleIntelInfo.txt file.
CPU Power States, many more than you reported.

I have just now run through the CPU Power Management guide linked below.

Quick Guide to Generate a SSDT for CPU Power Management

Piker Alpha's ssdtPRGen script will generate a SSDT you can use to achieve the maximum amount of power states for your desktop CPU. Please note that desktop power management is not mandatory. Requirements: Working internet connection How to Generate a SSDT for Power Management 1. Configure...

www.tonymacx86.com

I have generated an SSDT.aml for power management on my i7-4790K, Asus Z97-K, RX580 system, iMacPro1,1 SMBIOS, running macOS Ventura 13.1.

A copy of the SSDT.aml is attached below.


The screenshot above is a sample of the Intel Power Gadget output v 3.7.0 with the new SSDT.aml table installed, in place of the SSDT-PLUG.aml. I would say that CPU Power Management was working.

Looking in my system IOReg, it shows all the expected attributes for CPU Power Management working.

CPU0 - X86PlatformPlugin etc. shown

Haven't got a copy of the AppleIntelInfo.dat yet, as I need to disable SIP and Reboot the system, which I am loathe to do at this time.

You can build your own SSDT.aml table or try using the one attached to this post.

 

[VirtualRecess]

Many thanks again for the response.

This screenshot shows the power states available to your CPU (taken from your Hackintool_AppleIntelInfo.txt file.
.... CPU Power States, many more than you reported.

This is exactly the issue I am referring to which has me stuck in a rut.

Everything on my system points to PM working from IOReg and AppleIntelInfo. But yet in realtime observations, I only ever see CPU running at 8x, 40x -> 44x multipliers.

The screenshot above is a sample of the Intel Power Gadget output v 3.7.0 with the new SSDT.aml table installed, in place of the SSDT-PLUG.aml. I would say that CPU Power Management was working.

If possible, could you instead install the older version Intel Power Gadget v 3.5.5 (found at the bottom of Intels download page) and set both options in preferences to 150ms and then post the results ?

Just for my sanity, it would be much more helpful to see your 4790K reporting the Core speed in realtime so to confirm the other working Core speeds.

 

[Edhawk]

Every time I try to install IPG v3.5.5 it fails. I think v3.5.5 doesn't work in Ventura.

I have another system using the same CPU, running Catalina. I will see what is working on that system, using IPG v3.5.5, tomorrow.