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

To: debian-user@lists.debian.org
Subject: Re: 'sensors -j' and "ERROR: Can't get value of subfeature in0_input: Can't read"
From: Emanuel Berg <incal@dataswamp.org>
Date: Thu, 22 Feb 2024 21:40:02 +0100
Message-id: <[🔎] 8734tk2py5.fsf@dataswamp.org>
Mail-followup-to: debian-user@lists.debian.org
References: <[🔎] 878r3c3c87.fsf@dataswamp.org> <[🔎] 20240222143008.wj3vgphhapdwvntr@randomstring.org>

Dan Ritter wrote:

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

Okay, I did that ('sudo sensors-detect') and answered with the
default value to all questions, after that I did 'sensors -j'
but it displayed the same error.

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

So I should reboot? Let's do that.

-- 
underground experts united
https://dataswamp.org/~incal

Reply to:

Follow-Ups:
- Re: 'sensors -j' and "ERROR: Can't get value of subfeature in0_input: Can't read"
  - From: Emanuel Berg <incal@dataswamp.org>

References:
- 'sensors -j' and "ERROR: Can't get value of subfeature in0_input: Can't read"
  - From: Emanuel Berg <incal@dataswamp.org>
- Re: 'sensors -j' and "ERROR: Can't get value of subfeature in0_input: Can't read"
  - From: Dan Ritter <dsr@randomstring.org>

Prev by Date: Re: which package to file a bug report ?
Next by Date: Re: Inclusive terminology (instead of master/slave) for network bonding/LACP
Previous by thread: Re: 'sensors -j' and "ERROR: Can't get value of subfeature in0_input: Can't read"
Next by thread: Re: 'sensors -j' and "ERROR: Can't get value of subfeature in0_input: Can't read"
Index(es):
- Date
- Thread