public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: heat codes
Date: Fri, 27 Feb 2015 07:27:05 +0100	[thread overview]
Message-ID: <54F00E39.60102@googlemail.com> (raw)
In-Reply-To: <loom.20150227T021559-579@post.gmane.org>

Am 27.02.2015 um 02:23 schrieb James:
> Volker Armin Hemmann <volkerarmin <at> googlemail.com> writes:
>
>
>> em, but you are already monitoring it!
> Maybe. It hard to tell if there are more than one
> temperature sensor, what buss interfacet they are on
> and if it is a calculated or esitmated or actual temperature
> sensor.

it pretty much tells you all that with its name. And for radeon - there
is only one.
>
>
>>>> Does anyone with similar hardware have a more extensive list?
>> no, that is all you got.
> That's pretty sad. All that hardware and 3 temps....
>
>
>>>> What I'd really like is a very fast (real time?) gui to watch
>> you won't get that, because the senors don't update in 'realtime'.
> Sure. But if I knew of a relatively consistent delay semantic,
use the command below and watch for changes. Some boards update every
second, some every three seconds.

> I could align the delays in temperature sensing with what's going
> on with code compiling or execution; even if it is a rough estimate.
>
>
>> watch -n1 sensors.
>  
> not bad. for quick checks.
>
>> Works even without systemd. Shocking, I know.
> As usual, your insight and singular wit makes for pleasurable reading.
>
> thx,
> James
>
>
>
>



  reply	other threads:[~2015-02-27  6:27 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26 18:53 [gentoo-user] heat codes James
2015-02-26 20:13 ` [gentoo-user] " James
2015-02-26 23:02   ` Volker Armin Hemmann
2015-02-27  1:23     ` James
2015-02-27  6:27       ` Volker Armin Hemmann [this message]
2015-02-28 11:33   ` Mick
2015-03-12 23:53     ` James
2015-03-13  0:38       ` Dale
2015-03-13  6:20         ` Mick
2015-03-13 11:23           ` Dale
2015-03-13  9:13         ` Peter Humphrey
2015-03-13 11:27           ` Dale
2015-03-13 12:06             ` Peter Humphrey
2015-03-13 15:49               ` Dale
2015-03-13 16:10                 ` Mick
2015-02-26 23:26 ` [gentoo-user] " Dale
2015-02-27  1:31   ` [gentoo-user] " James
2015-02-27  1:48     ` Dale
2015-02-27  5:40       ` Peter Humphrey
2015-02-27  8:27         ` Dale
2015-02-27  9:02           ` Neil Bothwick
2015-02-27  9:43             ` Peter Humphrey
2015-02-27 20:41               ` wabenbau
2015-02-28  9:48                 ` Peter Humphrey
2015-03-12 19:40                   ` Dale
2015-03-12 22:38                     ` Peter Humphrey
2015-03-12 23:12                       ` Neil Bothwick
2015-03-12 23:29                     ` wabenbau
2015-03-12 23:35                       ` Dale
2015-03-13  5:23                         ` Tuomo Hartikainen
2015-03-13 11:31                           ` Dale
2015-02-27  9:57             ` Dale

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=54F00E39.60102@googlemail.com \
    --to=volkerarmin@googlemail.com \
    --cc=gentoo-user@lists.gentoo.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