Skip to content
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

temperature input value of feature 'temp2' of chip 'thinkpad-isa-0000' is unavailable #222

Open
plkrnr opened this issue Jan 15, 2023 · 1 comment
Assignees
Labels
bug Behavior not as intended can't repro Developer can't reproduce described behavior usability Unnecessarily confusing or complicated user interaction

Comments

@plkrnr
Copy link

plkrnr commented Jan 15, 2023

Hi,
small issue I think, but it's a confusing one. Using latest code in the repo.

(relevant) sensors:

thinkpad-isa-0000
Adapter: ISA adapter
fan1:           0 RPM
CPU:          +40.0°C  
GPU:              N/A  
temp3:        +40.0°C  
temp4:         +0.0°C  
temp5:        +40.0°C  
temp6:        +40.0°C  
temp7:        +40.0°C  
temp8:            N/A 

(relevant) config:

sensors:
  - chip: thinkpad-isa-0000
    ids: [ CPU, GPU, temp3, temp4, temp5, temp6, temp7, temp8 ]

output:

sudo thinkfan -nv
ERROR: temperature input value of feature 'temp2' of chip 'thinkpad-isa-0000' is unavailable: Can't read

expected output: ERROR: temperature input value of feature 'GPU' (GPU instead of temp2)

(if I would put GPU at the end of the ids array it would also say 'temp2')
(removing GPU and temp8 from my config fixed the issue for me)

@vmatare vmatare self-assigned this Oct 15, 2024
@vmatare
Copy link
Owner

vmatare commented Oct 15, 2024

That sounds very weird. From a code review (currently have no hardware available to reproduce this) I'd say this must be a libsensors bug, because we first lookup the feature by name (i.e. GPU in this case), but then continue on with the libsensors representation of the feature. In the error message, we then use whatever libsensors says the offending feature's name is. So it looks to me like libsensors just has the wrong feature name in its internal data structure.

@vmatare vmatare added bug Behavior not as intended can't repro Developer can't reproduce described behavior usability Unnecessarily confusing or complicated user interaction labels Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Behavior not as intended can't repro Developer can't reproduce described behavior usability Unnecessarily confusing or complicated user interaction
Projects
None yet
Development

No branches or pull requests

2 participants