| 1 |
Am 27.02.2015 um 02:23 schrieb James: |
| 2 |
> Volker Armin Hemmann <volkerarmin <at> googlemail.com> writes: |
| 3 |
> |
| 4 |
> |
| 5 |
>> em, but you are already monitoring it! |
| 6 |
> Maybe. It hard to tell if there are more than one |
| 7 |
> temperature sensor, what buss interfacet they are on |
| 8 |
> and if it is a calculated or esitmated or actual temperature |
| 9 |
> sensor. |
| 10 |
|
| 11 |
it pretty much tells you all that with its name. And for radeon - there |
| 12 |
is only one. |
| 13 |
> |
| 14 |
> |
| 15 |
>>>> Does anyone with similar hardware have a more extensive list? |
| 16 |
>> no, that is all you got. |
| 17 |
> That's pretty sad. All that hardware and 3 temps.... |
| 18 |
> |
| 19 |
> |
| 20 |
>>>> What I'd really like is a very fast (real time?) gui to watch |
| 21 |
>> you won't get that, because the senors don't update in 'realtime'. |
| 22 |
> Sure. But if I knew of a relatively consistent delay semantic, |
| 23 |
use the command below and watch for changes. Some boards update every |
| 24 |
second, some every three seconds. |
| 25 |
|
| 26 |
> I could align the delays in temperature sensing with what's going |
| 27 |
> on with code compiling or execution; even if it is a rough estimate. |
| 28 |
> |
| 29 |
> |
| 30 |
>> watch -n1 sensors. |
| 31 |
> |
| 32 |
> not bad. for quick checks. |
| 33 |
> |
| 34 |
>> Works even without systemd. Shocking, I know. |
| 35 |
> As usual, your insight and singular wit makes for pleasurable reading. |
| 36 |
> |
| 37 |
> thx, |
| 38 |
> James |
| 39 |
> |
| 40 |
> |
| 41 |
> |
| 42 |
> |
Archives