You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 26, 2022. It is now read-only.
On a new Alder Lake CPU, Core temperatures and voltage are displaying as 0 for all cores.
After a bit of trial and error it seems like [MeasureCpuTempHwinfoCoreX] in CoreMeasuresX.inc are being set to Disabled from the (#cpuCores# / #threadsPerCore# < X)) expressions.
My guess would be threadsPerCore is not being set correctly due to the fact that Alder Lake CPUs have two threads per P-core but only a single thread for their E-cores.
The text was updated successfully, but these errors were encountered:
The latest Gadget CPU Meter works with Alder Lake and even 128-thread Threadrippers, but it required a ton of changes to make it work. 😢 Check out the ActiveNet plugin's CpuLogicalCoreMap option; it should simplify the logic you will need.
I just need to get around to it. I don't use Windows anymore, so I have almost zero motivation to work on this project. It's at the bottom of my list. I'm sorry.
On a new Alder Lake CPU, Core temperatures and voltage are displaying as 0 for all cores.
After a bit of trial and error it seems like [MeasureCpuTempHwinfoCoreX] in CoreMeasuresX.inc are being set to Disabled from the (#cpuCores# / #threadsPerCore# < X)) expressions.
My guess would be threadsPerCore is not being set correctly due to the fact that Alder Lake CPUs have two threads per P-core but only a single thread for their E-cores.
The text was updated successfully, but these errors were encountered: