Contribute
Register

Quick Guide to Generate a SSDT for CPU Power Management

AFIK if you have a CPU and smBIOS that matches a real mac you will get the native frequencies required to get full power-management without any assistance from Clover or from an SSDT.

Martin
 
AFIK if you have a CPU and smBIOS that matches a real mac you will get the native frequencies required to get full power-management without any assistance from Clover or from an SSDT.

Martin

I'm not sure thats quite the case, I think the SSDT is always required, but I'll happily stand corrected if thats not the case.
 
Hello,

Sorry for the Noob question - but does this seem right? Also, ssdt.aml attached if that matters.

Thanks for your help!

Something to remember is that it can take quite a while to reach all available states. After loading the kext, go about your normal business with your hack and check the ouput after 30 minues or so, then again after an hour.
 
Hello,

Just did my first build (GA-H110N, Core i3-6700, 8 GB RAM, 250 GB M.2 SSD) - followed the Sierra Installation guide step-by-step. I'm in MacOS fine and all seems to be functional (WiFi/Bluetooth card has not arrived yet).

Anyway, I ran the current ssdtPRGen.sh tool, it complained about my board (14,2) not supporting Skylake. I used -target 4 to override. I checked the power states (with the AppleIntelInfo.kext) before and after and this is what I got

Before Installing my ssdt.aml:

Code:
CPU Ratio Info:

------------------------------------
CPU Low Frequency Mode.............: 800 MHz
CPU Maximum non-Turbo Frequency....: 3700 MHz
CPU Maximum Turbo Frequency........: 3700 MHz

IGPU Info:
------------------------------------
IGPU Current Frequency.............:    0 MHz
IGPU Minimum Frequency.............:  350 MHz
IGPU Maximum Non-Turbo Frequency...:  350 MHz
IGPU Maximum Turbo Frequency.......: 1050 MHz
IGPU Maximum limit.................: No Limit

CPU P-States [ (10) 21 37 ] iGPU P-States [ ]
CPU C3-Cores [ 0 1 2 3 ]
CPU C6-Cores [ 0 1 2 3 ]
CPU C7-Cores [ 2 3 ]
CPU P-States [ 10 (13) 21 37 ] iGPU P-States [ ]
CPU P-States [ 10 12 (13) 21 37 ] iGPU P-States [ ]
CPU P-States [ (10) 12 13 17 21 37 ] iGPU P-States [ ]
CPU P-States [ 10 12 (13) 15 17 21 37 ] iGPU P-States [ ]
CPU P-States [ 10 12 (13) 14 15 17 21 37 ] iGPU P-States [ ]
CPU P-States [ (10) 12 13 14 15 17 21 23 37 ] iGPU P-States [ ]
CPU P-States [ (10) 12 13 14 15 17 21 23 24 37 ] iGPU P-States [ ]
CPU P-States [ (10) 12 13 14 15 16 17 21 23 24 37 ] iGPU P-States [ ]
CPU P-States [ (10) 12 13 14 15 16 17 21 23 24 26 37 ] iGPU P-States [ ]
CPU P-States [ (10) 11 12 13 14 15 16 17 21 23 24 26 37 ] iGPU P-States [ ]

After:

Code:
CPU Ratio Info:
------------------------------------
CPU Low Frequency Mode.............: 800 MHz
CPU Maximum non-Turbo Frequency....: 3700 MHz
CPU Maximum Turbo Frequency........: 3700 MHz

IGPU Info:
------------------------------------
IGPU Current Frequency.............:    0 MHz
IGPU Minimum Frequency.............:  350 MHz
IGPU Maximum Non-Turbo Frequency...:  350 MHz
IGPU Maximum Turbo Frequency.......: 1050 MHz
IGPU Maximum limit.................: No Limit

CPU P-States [ 36 (37) ] iGPU P-States [ ]
CPU C3-Cores [ 0 1 2 ]
CPU C6-Cores [ 0 1 2 3 ]
CPU C7-Cores [ 2 3 ]
CPU P-States [ (8) 33 36 37 ] iGPU P-States [ (21) ]
CPU C3-Cores [ 0 1 2 3 ]
CPU P-States [ 8 31 33 36 (37) ] iGPU P-States [ 21 ]
CPU P-States [ 8 30 31 33 36 (37) ] iGPU P-States [ (21) ]
CPU P-States [ (8) 22 30 31 33 36 37 ] iGPU P-States [ 21 ]
CPU P-States [ 8 22 30 31 32 33 36 (37) ] iGPU P-States [ 21 ]
CPU P-States [ 8 22 30 31 32 33 35 36 (37) ] iGPU P-States [ 21 ]
CPU P-States [ (8) 22 29 30 31 32 33 35 36 37 ] iGPU P-States [ 21 ]
CPU P-States [ (8) 22 25 29 30 31 32 33 35 36 37 ] iGPU P-States [ 21 ]
CPU P-States [ (8) 22 24 25 29 30 31 32 33 35 36 37 ] iGPU P-States [ 21 ]
CPU P-States [ (8) 13 22 24 25 29 30 31 32 33 35 36 37 ] iGPU P-States [ 21 ]
CPU P-States [ (8) 13 18 22 24 25 29 30 31 32 33 35 36 37 ] iGPU P-States [ 21 ]

Sorry for the Noob question - but does this seem right? Also, ssdt.aml attached if that matters.

Thanks for your help!

Looks fine to me. Which SMBIOS are you using?
 
I'm not sure thats quite the case, I think the SSDT is always required, but I'll happily stand corrected if thats not the case.
Yes, same here for standing to be corrected, my assumption is based off PA's researching with unsupported processors. His hack works on his ssdtprgen generated SSDT for the unsupported processor plus having to apply the frequency vectors from another Mac board ID, this makes me think that you shouldn't require either if you have an smBIOS and an Apple supported CPU that match.

Martin
 
I'm not sure thats quite the case, I think the SSDT is always required, but I'll happily stand corrected if thats not the case.
Since I don't fully understand what the implications were of the differences in my before and after above, I was hoping I could get someone to let me know... And I think in my case, iMac14,2 never had an i3, so I think that's why it complained when I ran the script.
 
Yes, same here for standing to be corrected, my assumption is based off PA's researching with unsupported processors. His hack works on his ssdtprgen generated SSDT for the unsupported processor plus having to apply the frequency vectors from another Mac board ID, this makes me think that you shouldn't require either if you have an smBIOS and an Apple supported CPU that match.

Martin

Without a SSDT you will notice that X86PlatformPlugin is not loaded.
 
building went fine. when i try the check routine comp reboots... where should i start to search whats wrong...
 
in the pos where it is explained step by step how to make a SSDT...

https://www.tonymacx86.com/threads/quick-guide-to-generate-a-ssdt-for-cpu-power-management.177456/

Screen Shot 2017-05-03 at 17.29.45.png

i have a i7-5820K which is in this list
 
Back
Top