-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different Output of SV12_Core from Zenmonitor #16
Comments
Hello, What kind of cpu governor are you using? It is possible that your CPU governor is too aggressive and the conky/sensors update function is causing enough load for CPU to rise voltage and clocks. I had similar problem with hardinfo (issue lpereira/hardinfo#312), but managed to change the code to be more effective and do not cause this issue anymore (lpereira/hardinfo#327) Anyway - the zenmonitor's update function is as lightweight as possible, that's why this is not an issue there. Can you tell me how are you reading sensor values for conky? If you are parsing sensors output, you can try watch only zenpower: Let me know if it helps. |
I was using ondemand cpu governor. And this is what I have for the conky:
And actually if I changed the governor to |
Try this:
|
It actually works great now, thanks! |
np |
Hello, I'm using Ryzen 5 3600 with Gigabyte B450 AORUS PRO motherboard. I have a conky script displaying the output on my desktop and my SV12_Core stays at 1.4 V constantly (not going down even on 2.5GHz idle). And I installed zenmonitor and I've got different result. In zenmonitor, the CPU Core Voltage (SV12) goes up and down depending on the CPU frequency (1.1 V on idle and 1.4 V on boost). So why is the core voltage displaying differently? Here's a screenshot showing it.
Here's a screencast showing it with
watch 0.5 sensors
command compared to zenmonitor:The text was updated successfully, but these errors were encountered: