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

2024-02-24 Thread Emanuel Berg
>> 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

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

2024-02-22 Thread Emanuel Berg
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

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

2024-02-22 Thread Dan Ritter
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

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

2024-02-22 Thread Emanuel Berg
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.