-
Notifications
You must be signed in to change notification settings - Fork 26
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
cpu temperature showing as n/a #129
Comments
Thanks for reporting these, sorry it's taken me so long to investigate them. To fix the temperature reporting, please run the following to see all of the temperature sensors on the system:
For example, on my system this yields
Yours will look different, and you might need to figure out which name corresponds to your CPU. For modern AMD systems this is Next, list the files inside the CPU temperature sensor directory. This will be named
Finally, issue one more command to show the contents of those files:
If you post the results of those commands here, I should be able to get temperature monitoring for your CPU working in TopHat. In order to fix the CPU identification, could you also post the contents of /proc/cpuinfo? |
In the meantime I switched to another laptop, running arch this time and it works without issues... If the problem occurs again I'll pop back in! |
Since I have the same issue I followed the steps you described above. Please let me know if you need anything else.
Apparently I have no
These are the files in that directory:
And finally, |
Thank you! This is exactly what I was looking for, I'll work on getting the zenpower module supported for the next release. Regarding /proc/cpu, yep, that was a typo on my part; /proc/cpuinfo is the right file. |
|
I think I've got this working now. If you'd like to test it before the next release, here's a beta: (It will still show as v19 so that GNOME Extensions doesn't try to auto-update it. There are some minor issues with the filesystem menu, but otherwise it should be stable.) |
Can confirm, it's working now. Thanks :) |
The text was updated successfully, but these errors were encountered: