From: David VANTYGHEM <david.vantyghem@infolib.re>
To: lm-sensors@vger.kernel.org
Subject: Re: Is a temperature missing in sensors ?
Date: Fri, 17 Jan 2020 13:54:33 +0000 [thread overview]
Message-ID: <7824b66f-c6d8-a759-9dfb-e39d903cd9d7@infolib.re> (raw)
In-Reply-To: <288394b8-1afd-0ad1-e193-69fa169d090c@infolib.re>
Thank you for your answer.
Le 17/01/2020 à 14:42, Ondřej Lysoněk a écrit :
> Hi,
>
> David VANTYGHEM <david.vantyghem@infolib.re> writes:
>
>> Hello,
>>
>> With https://github.com/lpereira/hardinfo, I've got 6 temperatures : 1
>> for the GPU and 5 for the CPU (coretemp/temp1 to 5 and
>> thermal/thermal_zone0).
>>
>> With sensors, i've got only 5 temperatures (temp1 for GPU and Core 0 to
>> Core 3 for CPU). Is it a bug with HardInfo or is a temperature missing
>> in sensors ?
>>
>> https://framapic.org/SPID9PhB2KDJ/KaV6FdY6uvSW.png
> Hi,
>
> the 'sensors' output is missing the 'thermal/thermal_zone0' temperature,
> as shown by hardinfo. This is because lm_sensors only handles the hwmon
> subsystem (/sys/class/hwmon), not thermal (/sys/class/thermal).
>
> Ondrej
>
>> --
>> Signez la pétition pour le retrait du projet de réforme des retraites : https://onestla.tech
>>
>> Installer facilement Linux : http://infolib.re
>>
>> .--.
>> |o_o |
>> ||_/ |
>> // \\ Envoyé depuis mon Linux
>> (| |)
>> / \_ _/ \
>> \___)=(___/
--
Signez la pétition pour le retrait du projet de réforme des retraites : https://onestla.tech
Installer facilement Linux : http://infolib.re
.--.
|o_o |
||_/ |
// \\ Envoyé depuis mon Linux
(| |)
/ \_ _/ \
\___)=(___/
prev parent reply other threads:[~2020-01-17 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 12:52 Is a temperature missing in sensors ? David VANTYGHEM
2020-01-17 13:42 ` Ondřej Lysoněk
2020-01-17 13:54 ` David VANTYGHEM [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7824b66f-c6d8-a759-9dfb-e39d903cd9d7@infolib.re \
--to=david.vantyghem@infolib.re \
--cc=lm-sensors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).