Would you mind sharing what Clover did behind the scenes? Does it have anything to do with HWP? Personally speaking, I prefer HWP over EIST. HWP provides faster response and keep in lower states when idle.
If you look at your patchmatic -extract output, you will see the SSDT that Clover generated. Or you can view the SSDT in MaciASL (it is usually the last SSDT in the extract).
It is essentially the same content as SSDT-XCPM.dsl.
Nothing to do with HWP. HWP enablement is determined by SMBIOS in use, nothing else.
I didn't generate an SSDT since I use i7 8550u, my output in the terminal is in the next lines, but is something wrong with my IGPU or its normal those values?
Code:
CPU Ratio Info:
------------------------------------
CPU Low Frequency Mode.............: 400 MHz
CPU Maximum non-Turbo Frequency....: 2000 MHz
CPU Maximum Turbo Frequency........: 4000 MHz
IGPU Info:
------------------------------------
IGPU Current Frequency.............: 0 MHz
IGPU Minimum Frequency.............: 300 MHz
IGPU Maximum Non-Turbo Frequency...: 300 MHz
IGPU Maximum Turbo Frequency.......: 1150 MHz
IGPU Maximum limit.................: No Limit
CPU P-States [ (13) 27 37 ] iGPU P-States [ ]
CPU C3-Cores [ 0 2 5 ]
CPU P-States [ (13) 15 27 37 ] iGPU P-States [ ]
CPU C3-Cores [ 0 1 2 4 5 6 ]
CPU P-States [ (13) 15 18 27 37 ] iGPU P-States [ ]
CPU C3-Cores [ 0 1 2 3 4 5 6 7 ]
CPU P-States [ (13) 15 18 21 27 37 ] iGPU P-States [ ]
CPU P-States [ (13) 14 15 18 21 27 37 ] iGPU P-States [ ]
CPU P-States [ 13 14 15 18 (20) 21 24 27 37 ] iGPU P-States [ ]
CPU P-States [ (13) 14 15 18 19 20 21 24 27 37 ] iGPU P-States [ ]
CPU P-States [ 13 14 15 16 18 19 (20) 21 24 27 37 ] iGPU P-States [ ]
CPU P-States [ (13) 14 15 16 17 18 19 20 21 24 27 37 ] iGPU P-States [ ]
Edit:
I used the method with SSDT-XCPM.aml and now my output is this:
(It's finally correct? I have more P-States)
The 1st scenario was incomplete because I skipped one part of the tutorial by mistake, in my 2nd I did everything as it was supposed.
So, the PR files are from the 2nd scenario and according to the files, is everything working as expected?
The 1st scenario was incomplete because I skipped one part of the tutorial by mistake, in my 2nd I did everything as it was supposed.
So, the PR files are from the 2nd scenario and according to the files, is everything working as expected?
If you look at your patchmatic -extract output, you will see the SSDT that Clover generated. Or you can view the SSDT in MaciASL (it is usually the last SSDT in the extract).
It is essentially the same content as SSDT-XCPM.dsl.
Nothing to do with HWP. HWP enablement is determined by SMBIOS in use, nothing else.
Since my build is 8700K, I choose the newly released Mac Mini as my model. It enables HWP. I wonder how these two power management cope with each other.
Since my build is 8700K, I choose the newly released Mac Mini as my model. It enables HWP. I wonder how these two power management cope with each other.
My question is who takes the charge for CPU power management if they both are enabled and working. With my past experience with Pentium G4600, you have to fake cpuid to 0306A0 and use NullIntelCPU to disable EIST completely so that HWP takes the charge here.
My question is who takes the charge for CPU power management if they both are enabled and working. With my past experience with Pentium G4600, you have to fake cpuid to 0306A0 and use NullIntelCPU to disable EIST completely so that HWP takes the charge here.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.