Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #267687

Re: 'sensors -j' and "ERROR: Can't get value of subfeature in0_input: Can't read"

From Dan Ritter <dsr@randomstring.org>
Newsgroups linux.debian.user
Subject Re: 'sensors -j' and "ERROR: Can't get value of subfeature in0_input: Can't read"
Date 2024-02-22 15:50 +0100
Message-ID <IaiyB-bSge-1@gated-at.bofh.it> (permalink)
References <IagwO-bR6G-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Emanuel Berg wrote: 
> sensors(1) and in particular the command 'sensors -j' now
> reports
> 
>   ERROR: Can't get value of subfeature in0_input: Can't read
>   ERROR: Can't get value of subfeature in1_input: Can't read
> 
> for the CPU and GPU temperatures.
> 
> This previously worked so I don't know why it doesn't all of
> a sudden. Some sysfs driver issue? Or hardware
> malfunction? Unlikely?

In general, the first thing you should try is running
sensors-detect again, as root.

It is possible that your kernel is not loading some particular
sensor module which would be recommended by sensors-detect.

Depending on the hardware, there can also be BIOS or equivalent
features which turn on or off various sensors.

-dsr-

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

'sensors -j' and "ERROR: Can't get value of subfeature in0_input: Can't read" Emanuel Berg <incal@dataswamp.org> - 2024-02-22 13:40 +0100
  Re: 'sensors -j' and "ERROR: Can't get value of subfeature  in0_input: Can't read" Dan Ritter <dsr@randomstring.org> - 2024-02-22 15:50 +0100
    Re: 'sensors -j' and "ERROR: Can't get value of subfeature in0_input: Can't read" Emanuel Berg <incal@dataswamp.org> - 2024-02-22 21:50 +0100
      Re: 'sensors -j' and "ERROR: Can't get value of subfeature in0_input: Can't read" Emanuel Berg <incal@dataswamp.org> - 2024-02-24 14:50 +0100

csiph-web