-
Notifications
You must be signed in to change notification settings - Fork 524
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
[Sensors@claudiux] User's values (high, crit) must take precedence over those sent by sensors #6766
Comments
Thank you for reporting this issue. These values are those sent by the |
Thank you for the fast response. This is a spare system so no emergency.
Let's hope they are not the actual sensor readings. Unless some devices
send limits along with the current value.
Topic change...
Are you planning support newer devices such as Ryzen socket 5 motherboards?
The one I just purchased is already 2 years old
- AND -
The manufacturer is still releasing a "support suite" that makes the OS
buggy. 😡
…On Thu, Jan 16, 2025, 13:46 claudiux ***@***.***> wrote:
Thank you for reporting this issue. These values are those sent by the
sensors program. I'll make sure that user values take precedence over
these.
—
Reply to this email directly, view it on GitHub
<#6766 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVKX6JTPVK6Z3STYQEYROGL2LAD73AVCNFSM6AAAAABVJ63VCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJWG42DOOBSGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I'm not a member of the
I can't do anything about it, alas! |
Pardon my confusion. I forgot the division of functionality.
Well, of course you can do something! You and the lm-sensors folks.
Continue on with your great work and we can dismiss the need to rely on
buggy, ad infested, Spyware that tries to pass as thermal monitoring and
control suites. 😉
If I understand correctly, one brand has a special hardware monitoring
"chip" that when read - even by their own software utilities - can and does
cause system instability. 🤦♂️
…On Thu, Jan 16, 2025, 14:22 claudiux ***@***.***> wrote:
Are you planning support newer devices such as Ryzen socket 5 motherboards?
The one I just purchased is already 2 years old
I'm not a member of the lm-sensors dev community. Please open an issue on
https://github.com/lm-sensors/lm-sensors/issues
The manufacturer is still releasing a "support suite" that makes the OS
buggy. 😡
I can't do anything about it, alas!
—
Reply to this email directly, view it on GitHub
<#6766 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVKX6JSDZATG7ZWMVAJQMTD2LAIGVAVCNFSM6AAAAABVJ63VCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJWHAYTSMZSGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Applet version/Build date
Version 4.0.1 (2025-01-14 15:43:10)
Cinnamon version
6.2.9 and a few earlier
Distribution
Mint 21.3 & Mint 22
Graphics hardware and driver used
NVIDIA GeForce GTX 1060 rev 550
Applet name and maintainer
Sensors@claudiux @claudiux
What happened?
Hello, setting up the app parameters has always been quirky. Back in Linux Mint 21.3, the limits and thresholds seem to have a life of their own. On my last build, I seem to have hit the jackpot and it started working correctly - without any further intervention.
For instance:
I'd set:
cpu High 50C Critical 60C
mb1 High 45C Critical 50C
mb2 High 45C Critical 50C
and so on...
Update the display and it would show:
cpu High 70C Critical 90C
mb1 High 9.0C Critical 10.0C
mb2 High 48.0C Critical 53.0C
(the same for fan speeds - both minimum rpm were set to 300)
After saving the config to a file (sensors.caudiux.json) in my home directory, I find the correct settings I entered. (see below)
I tried to import the same file, hoping that it might correct the issue, without success.
Compare the json clip to the tooltip display (see image below) and note that this does cause errors.
I would appreciate any help and/or suggestions you can offer.
Steps I have taken:
Uninstall and reinstall
Rebooting
Go back, do it again.
[edit]
I also cleared all the parameters and they persisted after reloading the json. I found this very strange.
No change.
I really like this applet, when it behaves itself. :)
Thank you for your hard work, I hope the problem is something simple.
Other information
Temperature info from the saved json
{ "sensor": "PCI adapter k10temp-pci-00c3: temp1", "show_in_panel": true, "show_in_tooltip": true, "shown_name": "cpu", "high_by_user": "50", "crit_by_user": "60", "user_formula": "" }, { "sensor": "ISA adapter it8721-isa-0290: temp1", "show_in_panel": true, "show_in_tooltip": true, "shown_name": "mb1", "high_by_user": "45", "crit_by_user": "50", "user_formula": "" }, { "sensor": "ISA adapter it8721-isa-0290: temp2", "show_in_panel": true, "show_in_tooltip": true, "shown_name": "mb2", "high_by_user": "45", "crit_by_user": "50", "user_formula": "" }, { "sensor": "NVIDIA GeForce GTX 1060 6GB 00000000:01:00.0: temp1", "show_in_panel": true, "show_in_tooltip": true, "shown_name": "GTX1060", "high_by_user": "65", "crit_by_user": "70", "user_formula": "" },
Fan speed settings from the saved json:
{ "sensor": "ISA adapter it8721-isa-0290: fan1", "show_in_panel": false, "show_in_tooltip": true, "shown_name": "fan1?", "min_by_user": "300", "user_formula": "" }, { "sensor": "ISA adapter it8721-isa-0290: fan2", "show_in_panel": true, "show_in_tooltip": true, "shown_name": "fan2?", "min_by_user": "300", "user_formula": "" }
sensors.claudiux.json
The text was updated successfully, but these errors were encountered: