[gentoo-user] heat codes

[gentoo-user] heat codes

[James]

Hello,

I need to monitor this hardware for temperatures, including logging
of temperatures, on as wide array of temperaturr sensors that is
possible with kernel 3.18.6-gentoo.)

Gigabyte  GA-990FXA-UD3
AMD FX(tm)-8350 Eight-Core Processor (currently clocked at 4 GHz)
VGA compatible controller Cape Verde PRO [Radeon HD 7750 / R7 250E]


Any there any others?
The generic sensor scan stumbled on the radeon card:
probe the I2C/SMBus adapters:
Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies Inc
SB600/SB700/SB800 SMBus
modprobe: FATAL: Module i2c-piix4 not found.
Failed to load module i2c-piix4.
Next adapter: Radeon i2c bit bus 0x90 (i2c-0)
Do you want to scan it? (yes/NO/selectively): yes
{through (i2c-7) all failed.

So lm_sensors only found these modules:

MODULE_0=fam15h_power
MODULE_1=it87
MODULE_2=k10temp

Does anyone with similar hardware have a more extensive list?


What I'd really like is a very fast (real time?) gui to watch
these temperatures as certain portions of codes are compile or executed.
I'm working with a several classes of algorithms, like systolic-algorithms
that push hardware resources, particularly cpu, gpu and ram, to
it's limit; therefore the portions of the codes that cause excessive
thermal stresses on these hardware resources, are of keen interest to me.


A local code that puts significant (heat) stress on a system while
compiling, that anyone can test against is, sci-libs/openfoam

Comment, suggests and web based reading resources are all greatly
appreciated. I did find this interesting resource

https://wiki.archlinux.org/index.php/fan_speed_control


TIA,
James

[gentoo-user] Re: heat codes

[James]

James <wireless <at> tampabay.rr.com> writes:


> modprobe: FATAL: Module i2c-piix4 not found.
> Failed to load module i2c-piix4.

OK, so I found this code and added it to the kernel.


> Next adapter: Radeon i2c bit bus 0x90 (i2c-0)
> Do you want to scan it? (yes/NO/selectively): yes
> {through (i2c-7) all failed.

No luck on finding/configuring the radeon temperature
sensors.

> 
> So lm_sensors only found these modules:
> 
MODULE_0=fam15h_power   [ OK ]
MODULE_1=it87           [ OK ]
MODULE_2=k10temp        [ OK ]


> Does anyone with similar hardware have a more extensive list?

I'm not sure how to moinor the CPU (8 cores) temperature
and if it is a calculated (estimated value) or a real temp?

# sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +36.0°C  (crit = +120.0°C, hyst = +90.0°C)

fam15h_power-pci-00c4
Adapter: PCI adapter
power1:       19.97 W  (crit = 125.19 W)

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +24.9°C  (high = +70.0°C)
                       (crit = +90.0°C, hyst = +87.0°C)

> What I'd really like is a very fast (real time?) gui to watch
> these temperatures as certain portions of codes are compile or executed.

Right now I'm running lxde, but my migration to lxqt (QT5) should
begin very soon so any QT5_ish gui would be very cool too.

> https://wiki.archlinux.org/index.php/fan_speed_control

James

Re: [gentoo-user] Re: heat codes

[Volker Armin Hemmann]

Am 26.02.2015 um 21:13 schrieb James:
> James <wireless <at> tampabay.rr.com> writes:
>
>
>> modprobe: FATAL: Module i2c-piix4 not found.
>> Failed to load module i2c-piix4.
> OK, so I found this code and added it to the kernel.
>
>
>> Next adapter: Radeon i2c bit bus 0x90 (i2c-0)
>> Do you want to scan it? (yes/NO/selectively): yes
>> {through (i2c-7) all failed.
> No luck on finding/configuring the radeon temperature
> sensors.

em, but you are already monitoring it!

>
>> So lm_sensors only found these modules:
>>
> MODULE_0=fam15h_power   [ OK ]
> MODULE_1=it87           [ OK ]
> MODULE_2=k10temp        [ OK ]
which looks good.

>
>> Does anyone with similar hardware have a more extensive list?

no, that is all you got.

> I'm not sure how to moinor the CPU (8 cores) temperature
> and if it is a calculated (estimated value) or a real temp?
>
> # sensors
> radeon-pci-0100
> Adapter: PCI adapter
> temp1:        +36.0°C  (crit = +120.0°C, hyst = +90.0°C)

see? radeon. Monitored. Just move along.

>
> fam15h_power-pci-00c4
> Adapter: PCI adapter
> power1:       19.97 W  (crit = 125.19 W)
>
> k10temp-pci-00c3
> Adapter: PCI adapter
> temp1:        +24.9°C  (high = +70.0°C)
>                        (crit = +90.0°C, hyst = +87.0°C)
>
>> What I'd really like is a very fast (real time?) gui to watch
>> these temperatures as certain portions of codes are compile or executed.

you won't get that, because the senors don't update in 'realtime'.

> Right now I'm running lxde, but my migration to lxqt (QT5) should
> begin very soon so any QT5_ish gui would be very cool too.


watch -n1 sensors.

Works even without systemd. Shocking, I know.

Re: [gentoo-user] heat codes

[Dale]

James wrote:
> Hello,
>
> I need to monitor this hardware for temperatures, including logging
> of temperatures, on as wide array of temperaturr sensors that is
> possible with kernel 3.18.6-gentoo.)
>
> Gigabyte  GA-990FXA-UD3
> AMD FX(tm)-8350 Eight-Core Processor (currently clocked at 4 GHz)
> VGA compatible controller Cape Verde PRO [Radeon HD 7750 / R7 250E]
>
>
> Any there any others?
> The generic sensor scan stumbled on the radeon card:
> probe the I2C/SMBus adapters:
> Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies Inc
> SB600/SB700/SB800 SMBus
> modprobe: FATAL: Module i2c-piix4 not found.
> Failed to load module i2c-piix4.
> Next adapter: Radeon i2c bit bus 0x90 (i2c-0)
> Do you want to scan it? (yes/NO/selectively): yes
> {through (i2c-7) all failed.
>
> So lm_sensors only found these modules:
>
> MODULE_0=fam15h_power
> MODULE_1=it87
> MODULE_2=k10temp
>
> Does anyone with similar hardware have a more extensive list?
>
>
> What I'd really like is a very fast (real time?) gui to watch
> these temperatures as certain portions of codes are compile or executed.
> I'm working with a several classes of algorithms, like systolic-algorithms
> that push hardware resources, particularly cpu, gpu and ram, to
> it's limit; therefore the portions of the codes that cause excessive
> thermal stresses on these hardware resources, are of keen interest to me.
>
>
> A local code that puts significant (heat) stress on a system while
> compiling, that anyone can test against is, sci-libs/openfoam
>
> Comment, suggests and web based reading resources are all greatly
> appreciated. I did find this interesting resource
>
> https://wiki.archlinux.org/index.php/fan_speed_control
>
>
> TIA,
> James
>

I'm not sure if this is still available or not but doesn't gkrellm do
this sort of thing?  I used it to monitor another rig several years
ago.  May be worth looking into.

Dale

:-)  :-) 

[gentoo-user] Re: heat codes

[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.


> >> 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,
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

[gentoo-user] Re: heat codes

[James]

Dale <rdalek1967 <at> gmail.com> writes:


> > I need to monitor this hardware for temperatures, including logging
> > of temperatures, on as wide array of temperature sensors that is
> > possible with kernel 3.18.6-gentoo.)

> I'm not sure if this is still available or not but doesn't gkrellm do
> this sort of thing?  I used it to monitor another rig several years
> ago.  May be worth looking into.

> Dale


That (gkrellm) codebase looks old, un-maintained and  wee bit clumsy. It's
interesting to examine for ideas. I think I'm going with something a bit more
embedded inspired, for speed and portability reasons. I also have since
found this interesting piece of code;

sys-cluster/ganglia

First glance, it's a bit heavy-handed for my needs. I've gotta keep
looking before I decide on a path forward for RT temperature monitoring,
dB tracking and problem profiling. 

Thanks!
James

Re: [gentoo-user] Re: heat codes

[Dale]

James wrote:
> Dale <rdalek1967 <at> gmail.com> writes:
>
>
>>> I need to monitor this hardware for temperatures, including logging
>>> of temperatures, on as wide array of temperature sensors that is
>>> possible with kernel 3.18.6-gentoo.)
>> I'm not sure if this is still available or not but doesn't gkrellm do
>> this sort of thing?  I used it to monitor another rig several years
>> ago.  May be worth looking into.
>> Dale
>
> That (gkrellm) codebase looks old, un-maintained and  wee bit clumsy. It's
> interesting to examine for ideas. I think I'm going with something a bit more
> embedded inspired, for speed and portability reasons. I also have since
> found this interesting piece of code;
>
> sys-cluster/ganglia
>
> First glance, it's a bit heavy-handed for my needs. I've gotta keep
> looking before I decide on a path forward for RT temperature monitoring,
> dB tracking and problem profiling. 
>
> Thanks!
> James
>
>

While it has been a while since I used gkrellm to monitor a remote
system, I use it every day to monitor my system I sit at.  Keep in mind,
not much changes on how gkrellm works.  It looks for temp/fan/CPU/memory
etc info and displays it.  I'm not sure it requires a whole lot of
updating to do that especially given it has worked fine here for ages
and not much has really changed. 

It was the remote part that I wasn't sure about.  I know it used to have
that feature and if it still does, the remote part works just like the
local part does.  You just tell it to monitor something other than the
system you are sitting at. 

Sorry I wasn't more clear in my first message. 

Dale

:-)  :-) 

Re: [gentoo-user] Re: heat codes

[Peter Humphrey]

On Thursday 26 February 2015 19:48:06 Dale wrote:

> While it has been a while since I used gkrellm to monitor a remote
> system, I use it every day to monitor my system I sit at.  Keep in
> mind, not much changes on how gkrellm works.  It looks for
> temp/fan/CPU/memory etc info and displays it.  I'm not sure it
> requires a whole lot of updating to do that especially given it has
> worked fine here for ages and not much has really changed.

Yes, I have two instances of it running permanently too. Though I think 
James is right too, in that it does still have the odd bug.

> It was the remote part that I wasn't sure about.  I know it used to
> have that feature and if it still does, the remote part works just
> like the local part does.  You just tell it to monitor something
> other than the system you are sitting at.

$ gkrellm -s <host>

Then set it up the same way as you would the local one. KDE even knows 
to restart it along with other progs, which is more than can be said for 
Chromium.

-- 
Rgds
Peter.

Re: [gentoo-user] Re: heat codes

[Volker Armin Hemmann]

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
>
>
>
>

Re: [gentoo-user] Re: heat codes

[Dale]

Peter Humphrey wrote:
> On Thursday 26 February 2015 19:48:06 Dale wrote:
>
>> While it has been a while since I used gkrellm to monitor a remote
>> system, I use it every day to monitor my system I sit at.  Keep in
>> mind, not much changes on how gkrellm works.  It looks for
>> temp/fan/CPU/memory etc info and displays it.  I'm not sure it
>> requires a whole lot of updating to do that especially given it has
>> worked fine here for ages and not much has really changed.
> Yes, I have two instances of it running permanently too. Though I think 
> James is right too, in that it does still have the odd bug.
>
>

I haven't had any trouble with mine.  It just sits there and runs until
I logout.  What is this bug it suffers from? 

Dale

:-)  :-) 

Re: [gentoo-user] Re: heat codes

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 625 bytes --]

On Fri, 27 Feb 2015 02:27:03 -0600, Dale wrote:

> > Yes, I have two instances of it running permanently too. Though I
> > think James is right too, in that it does still have the odd bug.

> I haven't had any trouble with mine.  It just sits there and runs until
> I logout.  What is this bug it suffers from? 

Yay! We've finally found some software that works perfectly for Dale yet
shows bugs for other people!

You're slipping, Dale!


-- 
Neil Bothwick

In the begining, there was nothing.
And God said "Let there be light" and there was light.
There was still nothing, but you could see it better.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] Re: heat codes

[Peter Humphrey]

On Friday 27 February 2015 09:02:18 Neil Bothwick wrote:
> On Fri, 27 Feb 2015 02:27:03 -0600, Dale wrote:
> > > Yes, I have two instances of it running permanently too. Though I
> > > think James is right too, in that it does still have the odd bug.
> > 
> > I haven't had any trouble with mine.  It just sits there and runs
> > until I logout.  What is this bug it suffers from?
> 
> Yay! We've finally found some software that works perfectly for Dale
> yet shows bugs for other people!
> 
> You're slipping, Dale!

:)

Just a minor thing, Dale. Each curve plotted - of, say, traffic over 
eth0 - is supposed to show a numerical value in the upper left corner, 
but from time to time one of those will stop being shown. It then stays 
that way until I remove my .gkrellm2 directory and set the program up 
again.

Oh, and the Invisible theme stopped being invisible when KDE-4.0 was 
first allowed to escape. I reported it at the time, but nothing's 
happened as far as I can see.

Nothing major, as I said. I can live with it.

-- 
Rgds
Peter.

Re: [gentoo-user] Re: heat codes

[Dale]

Neil Bothwick wrote:
> On Fri, 27 Feb 2015 02:27:03 -0600, Dale wrote:
>
>>> Yes, I have two instances of it running permanently too. Though I
>>> think James is right too, in that it does still have the odd bug.
>> I haven't had any trouble with mine.  It just sits there and runs until
>> I logout.  What is this bug it suffers from? 
> Yay! We've finally found some software that works perfectly for Dale yet
> shows bugs for other people!
>
> You're slipping, Dale!
>
>

I was wanting to test it to see if it would screw up with me too.  ROFL 
I figure I must have left something out somewhere.  ;-)

Dale

:-)  :-) 

Re: [gentoo-user] Re: heat codes

[wabenbau]

Am Freitag, 27.02.2015 um 09:43
schrieb Peter Humphrey <peter@prh.myzen.co.uk>:

> On Friday 27 February 2015 09:02:18 Neil Bothwick wrote:
> > On Fri, 27 Feb 2015 02:27:03 -0600, Dale wrote:
> > > > Yes, I have two instances of it running permanently too. Though
> > > > I think James is right too, in that it does still have the odd
> > > > bug.
> > > 
> > > I haven't had any trouble with mine.  It just sits there and runs
> > > until I logout.  What is this bug it suffers from?
> > 
> > Yay! We've finally found some software that works perfectly for Dale
> > yet shows bugs for other people!
> > 
> > You're slipping, Dale!
> 
> :)
> 
> Just a minor thing, Dale. Each curve plotted - of, say, traffic over 
> eth0 - is supposed to show a numerical value in the upper left
> corner, but from time to time one of those will stop being shown. It
> then stays that way until I remove my .gkrellm2 directory and set the
> program up again.

You can switch the numerics on and off by left mouse click into the
respective monitor.

Regards
wabe

Re: [gentoo-user] Re: heat codes

[Peter Humphrey]

On Friday 27 February 2015 21:41:33 wabenbau@gmail.com wrote:

> You can switch the numerics on and off by left mouse click into the
> respective monitor.

Well, I'll be damned! I never found that out for myself, not in all 
those years of using it.

So no bug here then. Sorry Dale :)

-- 
Rgds
Peter.

Re: [gentoo-user] Re: heat codes

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 721 bytes --]

On Thursday 26 Feb 2015 20:13:07 James wrote:
> I'm not sure how to moinor the CPU (8 cores) temperature
> and if it is a calculated (estimated value) or a real temp?
> 
> # sensors
> radeon-pci-0100
> Adapter: PCI adapter
> temp1:        +36.0°C  (crit = +120.0°C, hyst = +90.0°C)
> 
> fam15h_power-pci-00c4
> Adapter: PCI adapter
> power1:       19.97 W  (crit = 125.19 W)
> 
> k10temp-pci-00c3
> Adapter: PCI adapter
> temp1:        +24.9°C  (high = +70.0°C)
>                        (crit = +90.0°C, hyst = +87.0°C)

There should be more after these, showing your voltages and various MoBo 
sensors.  Can you check that it87 is actually loaded?  lsmod will tell you.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

Re: [gentoo-user] Re: heat codes

[Dale]

Peter Humphrey wrote:
> On Friday 27 February 2015 21:41:33 wabenbau@gmail.com wrote:
>
>> You can switch the numerics on and off by left mouse click into the
>> respective monitor.
> Well, I'll be damned! I never found that out for myself, not in all 
> those years of using it.
>
> So no bug here then. Sorry Dale :)
>

This is funny.  I accidentally clicked the thing and later on,
accidentally clicked it again to turn it back on.   Now, first time,
makes me go hmmmmmm.  Second time, hair puller.  It took me a while to
figure out what I was accidentally doing to fix it.  For a bit, I was
scared to put my mouse anywhere near the thing.  I wasn't sure what else
I might accidentally mess up. 

Well, now you know.  ;-)

Dale

:-)  :-) 

Re: [gentoo-user] Re: heat codes

[Peter Humphrey]

On Thursday 12 March 2015 14:40:09 Dale wrote:
> Peter Humphrey wrote:
> > On Friday 27 February 2015 21:41:33 wabenbau@gmail.com wrote:
> >> You can switch the numerics on and off by left mouse click into the
> >> respective monitor.
> > 
> > Well, I'll be damned! I never found that out for myself, not in all
> > those years of using it.
> > 
> > So no bug here then. Sorry Dale :)
> 
> This is funny.  I accidentally clicked the thing and later on,
> accidentally clicked it again to turn it back on.   Now, first time,
> makes me go hmmmmmm.  Second time, hair puller.  It took me a while to
> figure out what I was accidentally doing to fix it.  For a bit, I was
> scared to put my mouse anywhere near the thing.  I wasn't sure what
> else I might accidentally mess up.
> 
> Well, now you know.  ;-)

Well, it's just as I always say: you learn something new every day - if 
you're not careful! :-)

-- 
Rgds
Peter.

Re: [gentoo-user] Re: heat codes

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 314 bytes --]

On Thu, 12 Mar 2015 22:38:33 +0000, Peter Humphrey wrote:

> Well, it's just as I always say: you learn something new every day - if 
> you're not careful! :-)

As the old saying goes: experience is what you get when you didn't get
what you wanted :)


-- 
Neil Bothwick

I'm Pink, Therefore I'm Spam

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] Re: heat codes

[wabenbau]

Am Donnerstag, 12.03.2015 um 14:40
schrieb Dale <rdalek1967@gmail.com>:

> Peter Humphrey wrote:
> > On Friday 27 February 2015 21:41:33 wabenbau@gmail.com wrote:
> >
> >> You can switch the numerics on and off by left mouse click into the
> >> respective monitor.
> > Well, I'll be damned! I never found that out for myself, not in all 
> > those years of using it.
> >
> > So no bug here then. Sorry Dale :)
> >
> 
> This is funny.  I accidentally clicked the thing and later on,
> accidentally clicked it again to turn it back on.   Now, first time,
> makes me go hmmmmmm.  Second time, hair puller.  It took me a while to
> figure out what I was accidentally doing to fix it.  For a bit, I was
> scared to put my mouse anywhere near the thing.  I wasn't sure what
> else I might accidentally mess up. 
> 
> Well, now you know.  ;-)

Something similar happened to me. I accidentally pressed F6 while
focused gkrellm but didn't noticed it. Some time later I realized that
the fontsize of gkrellm was increased so that it's height doesn't fit
to the screen anymore. Fist I thought that it has something to do with
the latest update. It took some time till I recognized that I simply
had to press F7 to restore the fontsize to its former height. :-)

--
Regards
wabe

Re: [gentoo-user] Re: heat codes

[Dale]

wabenbau@gmail.com wrote:
> Am Donnerstag, 12.03.2015 um 14:40
> schrieb Dale <rdalek1967@gmail.com>:
>
>> Peter Humphrey wrote:
>>> On Friday 27 February 2015 21:41:33 wabenbau@gmail.com wrote:
>>>
>>>> You can switch the numerics on and off by left mouse click into the
>>>> respective monitor.
>>> Well, I'll be damned! I never found that out for myself, not in all 
>>> those years of using it.
>>>
>>> So no bug here then. Sorry Dale :)
>>>
>> This is funny.  I accidentally clicked the thing and later on,
>> accidentally clicked it again to turn it back on.   Now, first time,
>> makes me go hmmmmmm.  Second time, hair puller.  It took me a while to
>> figure out what I was accidentally doing to fix it.  For a bit, I was
>> scared to put my mouse anywhere near the thing.  I wasn't sure what
>> else I might accidentally mess up. 
>>
>> Well, now you know.  ;-)
> Something similar happened to me. I accidentally pressed F6 while
> focused gkrellm but didn't noticed it. Some time later I realized that
> the fontsize of gkrellm was increased so that it's height doesn't fit
> to the screen anymore. Fist I thought that it has something to do with
> the latest update. It took some time till I recognized that I simply
> had to press F7 to restore the fontsize to its former height. :-)
>
> --
> Regards
> wabe
>
>

Well, you should have seen the look on my face the other day when
Firefox went FULL SCREEN.  I mean full screen like it does when I hit F
and am watching a video.  Heck, I didn't have a menu at the top,  To
this day, I have no clue what I did.  I was typing a comment on a social
site and all of the sudden, it went sucky.  Still no clue but thank
goodness it fixed itself after I killed it and restarted. 

Dale

:-)  :-)

[gentoo-user] Re: heat codes

[James]

Mick <michaelkintzios <at> gmail.com> writes:


> > # sensors
> > radeon-pci-0100
> > Adapter: PCI adapter
> > temp1:        +36.0°C  (crit = +120.0°C, hyst = +90.0°C) 
> > fam15h_power-pci-00c4
> > Adapter: PCI adapter
> > power1:       19.97 W  (crit = 125.19 W)
 
> > k10temp-pci-00c3
> > Adapter: PCI adapter
> > temp1:        +24.9°C  (high = +70.0°C)
> >                        (crit = +90.0°C, hyst = +87.0°C)

> There should be more after these, showing your voltages and various MoBo 
> sensors.  Can you check that it87 is actually loaded?  lsmod will tell you.


Oh, I just noticed this posting; Dale's latest posting caused me to 
look at the thread again.

rc-status shows lm_sensors running, as does ps.

but  lsmod  is empty:
Module                  Size  Used by

/etc/conf.d/lm_sensors shows:

MODULE_0=fam15h_power
MODULE_1=it87
MODULE_2=k10temp


I think I have it 'compiled in'. Are you sure I should be
seeing more information?

"GA-990FXA-UD3" is the mobo.


James

Re: [gentoo-user] Re: heat codes

[Dale]

James wrote:
> Mick <michaelkintzios <at> gmail.com> writes:
>
>
>>> # sensors
>>> radeon-pci-0100
>>> Adapter: PCI adapter
>>> temp1:        +36.0°C  (crit = +120.0°C, hyst = +90.0°C) 
>>> fam15h_power-pci-00c4
>>> Adapter: PCI adapter
>>> power1:       19.97 W  (crit = 125.19 W)
>  
>>> k10temp-pci-00c3
>>> Adapter: PCI adapter
>>> temp1:        +24.9°C  (high = +70.0°C)
>>>                        (crit = +90.0°C, hyst = +87.0°C)
>> There should be more after these, showing your voltages and various MoBo 
>> sensors.  Can you check that it87 is actually loaded?  lsmod will tell you.
>
> Oh, I just noticed this posting; Dale's latest posting caused me to 
> look at the thread again.
>
> rc-status shows lm_sensors running, as does ps.
>
> but  lsmod  is empty:
> Module                  Size  Used by
>
> /etc/conf.d/lm_sensors shows:
>
> MODULE_0=fam15h_power
> MODULE_1=it87
> MODULE_2=k10temp
>
>
> I think I have it 'compiled in'. Are you sure I should be
> seeing more information?
>
> "GA-990FXA-UD3" is the mobo.
>
>
> James

I have a 970A-UD3P mobo and I use this under Hardware Monitoring support:

AMD Family 10h+ temperature sensor
AMD Family 15h processor power
ITE IT87xx and compatibles

Under bus support:

Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)

Our mobo isn't exactly the same but if they use the same chips, those
should get you all the info you need. 

I might add, I build everything into the kernel and I don't even install
lm_sensors. I haven't installed that in ages. 

Hope that helps.

Dale

:-)  :-) 

Re: [gentoo-user] Re: heat codes

[Tuomo Hartikainen]

On 150312 1835, Dale wrote:
> wabenbau@gmail.com wrote:
> > Something similar happened to me. I accidentally pressed F6 while
> > focused gkrellm but didn't noticed it. Some time later I realized that
> > the fontsize of gkrellm was increased so that it's height doesn't fit
> > to the screen anymore. Fist I thought that it has something to do with
> > the latest update. It took some time till I recognized that I simply
> > had to press F7 to restore the fontsize to its former height. :-)
> >
> > --
> > Regards
> > wabe
> >
> Well, you should have seen the look on my face the other day when
> Firefox went FULL SCREEN.  I mean full screen like it does when I hit F
> and am watching a video.  Heck, I didn't have a menu at the top,  To
> this day, I have no clue what I did.  I was typing a comment on a social
> site and all of the sudden, it went sucky.  Still no clue but thank
> goodness it fixed itself after I killed it and restarted. 
> 
> Dale

Try pressing F11 in Firefox? ;)
-- 
Tuomo Hartikainen

Re: [gentoo-user] Re: heat codes

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 4397 bytes --]

On Friday 13 Mar 2015 00:38:56 Dale wrote:
> James wrote:
> > Mick <michaelkintzios <at> gmail.com> writes:
> >>> # sensors
> >>> radeon-pci-0100
> >>> Adapter: PCI adapter
> >>> temp1:        +36.0°C  (crit = +120.0°C, hyst = +90.0°C)
> >>> fam15h_power-pci-00c4
> >>> Adapter: PCI adapter
> >>> power1:       19.97 W  (crit = 125.19 W)
> >>> 
> >>> k10temp-pci-00c3
> >>> Adapter: PCI adapter
> >>> temp1:        +24.9°C  (high = +70.0°C)
> >>> 
> >>>                        (crit = +90.0°C, hyst = +87.0°C)
> >> 
> >> There should be more after these, showing your voltages and various MoBo
> >> sensors.  Can you check that it87 is actually loaded?  lsmod will tell
> >> you.
> > 
> > Oh, I just noticed this posting; Dale's latest posting caused me to
> > look at the thread again.
> > 
> > rc-status shows lm_sensors running, as does ps.
> > 
> > but  lsmod  is empty:
> > Module                  Size  Used by
> > 
> > /etc/conf.d/lm_sensors shows:
> > 
> > MODULE_0=fam15h_power
> > MODULE_1=it87
> > MODULE_2=k10temp
> > 
> > 
> > I think I have it 'compiled in'. Are you sure I should be
> > seeing more information?
> > 
> > "GA-990FXA-UD3" is the mobo.
> > 
> > 
> > James
> 
> I have a 970A-UD3P mobo and I use this under Hardware Monitoring support:
> 
> AMD Family 10h+ temperature sensor
> AMD Family 15h processor power
> ITE IT87xx and compatibles
> 
> Under bus support:
> 
> Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)
> 
> Our mobo isn't exactly the same but if they use the same chips, those
> should get you all the info you need.
> 
> I might add, I build everything into the kernel and I don't even install
> lm_sensors. I haven't installed that in ages.
> 
> Hope that helps.
> 
> Dale
> 
> :-)  :-)

I don't have the same MoBo and have compiled my corresponding chipset sensor 
driver as a module.  It doesn't load unless I manually modprobe it or set it 
up in /etc/conf.d/modules.  This is how many readings I get:

$ sensors
radeon-pci-0008 
Adapter: PCI adapter 
temp1:        +37.0°C  (crit = +120.0°C, hyst = +90.0°C) 

k10temp-pci-00c3 
Adapter: PCI adapter 
temp1:        +36.8°C  (high = +70.0°C) 
                       (crit = +70.0°C, hyst = +69.0°C) 

fam15h_power-pci-00c4 
Adapter: PCI adapter 
power1:           N/A  (crit =  95.09 W) 

nct6791-isa-0290 
Adapter: ISA adapter 
in0:                    +1.38 V  (min =  +0.00 V, max =  +1.74 V) 
in1:                    +1.03 V  (min =  +0.00 V, max =  +0.00 V)  ALARM 
in2:                    +3.34 V  (min =  +0.00 V, max =  +0.00 V)  ALARM 
in3:                    +3.34 V  (min =  +0.00 V, max =  +0.00 V)  ALARM 
in4:                    +1.01 V  (min =  +0.00 V, max =  +0.00 V)  ALARM 
in5:                    +2.04 V  (min =  +0.00 V, max =  +0.00 V)  ALARM 
in6:                    +0.28 V  (min =  +0.00 V, max =  +0.00 V)  ALARM 
in7:                    +3.44 V  (min =  +0.00 V, max =  +0.00 V)  ALARM 
in8:                    +3.33 V  (min =  +0.00 V, max =  +0.00 V)  ALARM 
in9:                    +0.00 V  (min =  +0.00 V, max =  +0.00 V) 
in10:                   +0.17 V  (min =  +0.00 V, max =  +0.00 V)  ALARM 
in11:                   +0.17 V  (min =  +0.00 V, max =  +0.00 V)  ALARM 
in12:                   +1.01 V  (min =  +0.00 V, max =  +0.00 V)  ALARM 
in13:                   +1.03 V  (min =  +0.00 V, max =  +0.00 V)  ALARM 
in14:                   +0.21 V  (min =  +0.00 V, max =  +0.00 V)  ALARM 
fan1:                  1036 RPM  (min =    0 RPM) 
fan2:                  1695 RPM  (min =    0 RPM) 
fan3:                  1001 RPM  (min =    0 RPM) 
SYSTIN:                 +31.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  
sensor = thermistor 
CPUTIN:                 +47.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = 
thermistor 
AUXTIN0:               +106.0°C    sensor = thermistor 
AUXTIN1:               +105.0°C    sensor = thermistor 
AUXTIN2:               +105.0°C    sensor = thermistor 
AUXTIN3:               +106.0°C    sensor = thermistor 
PCH_CHIP_CPU_MAX_TEMP:   +0.0°C 
PCH_CHIP_TEMP:           +0.0°C 
PCH_CPU_TEMP:            +0.0°C 
PCH_MCH_TEMP:            +0.0°C 
intrusion0:            ALARM 
intrusion1:            ALARM 
beep_enable:           disabled

HTH.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

Re: [gentoo-user] Re: heat codes

[Peter Humphrey]

On Thursday 12 March 2015 19:38:56 Dale wrote:

> I build everything into the kernel and I don't even install
> lm_sensors. I haven't installed that in ages.

Does that mean that your gkrellm can't display temperatures?

-- 
Rgds
Peter.

Re: [gentoo-user] Re: heat codes

[Dale]

[-- Attachment #1: Type: text/plain, Size: 8719 bytes --]

Mick wrote:
>
>
>
> I don't have the same MoBo and have compiled my corresponding chipset
sensor
> driver as a module.  It doesn't load unless I manually modprobe it or
set it
> up in /etc/conf.d/modules.  This is how many readings I get:
>
> $ sensors
> radeon-pci-0008
> Adapter: PCI adapter
> temp1:        +37.0°C  (crit = +120.0°C, hyst = +90.0°C)
>
> k10temp-pci-00c3
> Adapter: PCI adapter
> temp1:        +36.8°C  (high = +70.0°C)
>                        (crit = +70.0°C, hyst = +69.0°C)
>
> fam15h_power-pci-00c4
> Adapter: PCI adapter
> power1:           N/A  (crit =  95.09 W)
>
> nct6791-isa-0290
> Adapter: ISA adapter
> in0:                    +1.38 V  (min =  +0.00 V, max =  +1.74 V)
> in1:                    +1.03 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in2:                    +3.34 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in3:                    +3.34 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in4:                    +1.01 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in5:                    +2.04 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in6:                    +0.28 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in7:                    +3.44 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in8:                    +3.33 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in9:                    +0.00 V  (min =  +0.00 V, max =  +0.00 V)
> in10:                   +0.17 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in11:                   +0.17 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in12:                   +1.01 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in13:                   +1.03 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in14:                   +0.21 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> fan1:                  1036 RPM  (min =    0 RPM)
> fan2:                  1695 RPM  (min =    0 RPM)
> fan3:                  1001 RPM  (min =    0 RPM)
> SYSTIN:                 +31.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM 
> sensor = thermistor
> CPUTIN:                 +47.0°C  (high = +80.0°C, hyst = +75.0°C) 
sensor =
> thermistor
> AUXTIN0:               +106.0°C    sensor = thermistor
> AUXTIN1:               +105.0°C    sensor = thermistor
> AUXTIN2:               +105.0°C    sensor = thermistor
> AUXTIN3:               +106.0°C    sensor = thermistor
> PCH_CHIP_CPU_MAX_TEMP:   +0.0°C
> PCH_CHIP_TEMP:           +0.0°C
> PCH_CPU_TEMP:            +0.0°C
> PCH_MCH_TEMP:            +0.0°C
> intrusion0:            ALARM
> intrusion1:            ALARM
> beep_enable:           disabled
>
> HTH.


I get things like this:

root@fireball / # ls -al /sys/devices/platform/it87.552/
total 0
drwxr-xr-x  4 root root    0 Mar 11 19:25 .
drwxr-xr-x 12 root root    0 Mar 11 19:25 ..
-r--r--r--  1 root root 4096 Mar 13 06:16 alarms
lrwxrwxrwx  1 root root    0 Mar 11 19:25 driver ->
../../../bus/platform/drivers/it87
-rw-r--r--  1 root root 4096 Mar 13 06:16 driver_override
-r--r--r--  1 root root 4096 Mar 13 06:16 fan1_alarm
-rw-r--r--  1 root root 4096 Mar  4 15:11 fan1_beep
-r--r--r--  1 root root 4096 Mar 11 19:26 fan1_input
-rw-r--r--  1 root root 4096 Mar 13 06:16 fan1_min
-r--r--r--  1 root root 4096 Mar 13 06:16 fan2_alarm
-r--r--r--  1 root root 4096 Mar 13 06:16 fan2_beep
-r--r--r--  1 root root 4096 Mar 11 19:26 fan2_input
-rw-r--r--  1 root root 4096 Mar 13 06:16 fan2_min
-r--r--r--  1 root root 4096 Mar 13 06:16 fan3_alarm
-r--r--r--  1 root root 4096 Mar 13 06:16 fan3_beep
-r--r--r--  1 root root 4096 Mar 11 19:26 fan3_input
-rw-r--r--  1 root root 4096 Mar 13 06:16 fan3_min
-r--r--r--  1 root root 4096 Mar 13 06:16 fan4_alarm
-r--r--r--  1 root root 4096 Mar 13 06:16 fan4_beep
-r--r--r--  1 root root 4096 Mar 13 06:16 fan4_input
-rw-r--r--  1 root root 4096 Mar 13 06:16 fan4_min
-r--r--r--  1 root root 4096 Mar 13 06:16 fan5_alarm
-r--r--r--  1 root root 4096 Mar 13 06:16 fan5_beep
-r--r--r--  1 root root 4096 Mar 11 19:26 fan5_input
-rw-r--r--  1 root root 4096 Mar 13 06:16 fan5_min
drwxr-xr-x  3 root root    0 Mar 11 19:25 hwmon
-r--r--r--  1 root root 4096 Mar 13 06:16 in0_alarm
-rw-r--r--  1 root root 4096 Mar 13 06:16 in0_beep
-r--r--r--  1 root root 4096 Mar 13 06:16 in0_input
-rw-r--r--  1 root root 4096 Mar 13 06:16 in0_max
-rw-r--r--  1 root root 4096 Mar 13 06:16 in0_min
-r--r--r--  1 root root 4096 Mar 13 06:16 in1_alarm
-r--r--r--  1 root root 4096 Mar 13 06:16 in1_beep
-r--r--r--  1 root root 4096 Mar 13 06:16 in1_input
-rw-r--r--  1 root root 4096 Mar 13 06:16 in1_max
-rw-r--r--  1 root root 4096 Mar 13 06:16 in1_min
-r--r--r--  1 root root 4096 Mar 13 06:16 in2_alarm
-r--r--r--  1 root root 4096 Mar 13 06:16 in2_beep
-r--r--r--  1 root root 4096 Mar 13 06:16 in2_input
-rw-r--r--  1 root root 4096 Mar 13 06:16 in2_max
-rw-r--r--  1 root root 4096 Mar 13 06:16 in2_min
-r--r--r--  1 root root 4096 Mar 13 06:16 in3_alarm
-r--r--r--  1 root root 4096 Mar 13 06:16 in3_beep
-r--r--r--  1 root root 4096 Mar 13 06:16 in3_input
-rw-r--r--  1 root root 4096 Mar 13 06:16 in3_max
-rw-r--r--  1 root root 4096 Mar 13 06:16 in3_min
-r--r--r--  1 root root 4096 Mar 13 06:16 in4_alarm
-r--r--r--  1 root root 4096 Mar 13 06:16 in4_beep
-r--r--r--  1 root root 4096 Mar 13 06:16 in4_input
-rw-r--r--  1 root root 4096 Mar 13 06:16 in4_max
-rw-r--r--  1 root root 4096 Mar 13 06:16 in4_min
-r--r--r--  1 root root 4096 Mar 13 06:16 in5_alarm
-r--r--r--  1 root root 4096 Mar 13 06:16 in5_beep
-r--r--r--  1 root root 4096 Mar 13 06:16 in5_input
-rw-r--r--  1 root root 4096 Mar 13 06:16 in5_max
-rw-r--r--  1 root root 4096 Mar 13 06:16 in5_min
-r--r--r--  1 root root 4096 Mar 13 06:16 in6_alarm
-r--r--r--  1 root root 4096 Mar 13 06:16 in6_beep
-r--r--r--  1 root root 4096 Mar 13 06:16 in6_input
-rw-r--r--  1 root root 4096 Mar 13 06:16 in6_max
-rw-r--r--  1 root root 4096 Mar 13 06:16 in6_min
-r--r--r--  1 root root 4096 Mar 13 06:16 in7_alarm
-r--r--r--  1 root root 4096 Mar 13 06:16 in7_beep
-r--r--r--  1 root root 4096 Mar 13 06:16 in7_input
-r--r--r--  1 root root 4096 Mar 13 06:16 in7_label
-rw-r--r--  1 root root 4096 Mar 13 06:16 in7_max
-rw-r--r--  1 root root 4096 Mar 13 06:16 in7_min
-r--r--r--  1 root root 4096 Mar 13 06:16 in8_input
-r--r--r--  1 root root 4096 Mar 13 06:16 in8_label
-rw-r--r--  1 root root 4096 Mar 13 06:16 intrusion0_alarm
-r--r--r--  1 root root 4096 Mar 13 06:16 modalias
-r--r--r--  1 root root 4096 Mar 11 19:26 name
drwxr-xr-x  2 root root    0 Mar 13 06:16 power
-rw-r--r--  1 root root 4096 Mar 13 06:16 pwm1
-rw-r--r--  1 root root 4096 Mar 13 06:16 pwm1_auto_channels_temp
-rw-r--r--  1 root root 4096 Mar 13 06:16 pwm1_enable
-rw-r--r--  1 root root 4096 Mar 13 06:16 pwm1_freq
-rw-r--r--  1 root root 4096 Mar 13 06:16 pwm2
-rw-r--r--  1 root root 4096 Mar 13 06:16 pwm2_auto_channels_temp
-rw-r--r--  1 root root 4096 Mar 13 06:16 pwm2_enable
-r--r--r--  1 root root 4096 Mar 13 06:16 pwm2_freq
-rw-r--r--  1 root root 4096 Mar 13 06:16 pwm3
-rw-r--r--  1 root root 4096 Mar 13 06:16 pwm3_auto_channels_temp
-rw-r--r--  1 root root 4096 Mar 13 06:16 pwm3_enable
-r--r--r--  1 root root 4096 Mar 13 06:16 pwm3_freq
lrwxrwxrwx  1 root root    0 Mar 11 19:25 subsystem -> ../../../bus/platform
-r--r--r--  1 root root 4096 Mar 13 06:16 temp1_alarm
-rw-r--r--  1 root root 4096 Mar 13 06:16 temp1_beep
-r--r--r--  1 root root 4096 Mar 11 19:26 temp1_input
-rw-r--r--  1 root root 4096 Mar 13 06:16 temp1_max
-rw-r--r--  1 root root 4096 Mar 13 06:16 temp1_min
-rw-r--r--  1 root root 4096 Mar 13 06:16 temp1_offset
-rw-r--r--  1 root root 4096 Mar 13 06:16 temp1_type
-r--r--r--  1 root root 4096 Mar 13 06:16 temp2_alarm
-r--r--r--  1 root root 4096 Mar 13 06:16 temp2_beep
-r--r--r--  1 root root 4096 Mar 11 19:26 temp2_input
-rw-r--r--  1 root root 4096 Mar 13 06:16 temp2_max
-rw-r--r--  1 root root 4096 Mar 13 06:16 temp2_min
-rw-r--r--  1 root root 4096 Mar 13 06:16 temp2_offset
-rw-r--r--  1 root root 4096 Mar 13 06:16 temp2_type
-r--r--r--  1 root root 4096 Mar 13 06:16 temp3_alarm
-r--r--r--  1 root root 4096 Mar 13 06:16 temp3_beep
-r--r--r--  1 root root 4096 Mar 11 19:26 temp3_input
-rw-r--r--  1 root root 4096 Mar 13 06:16 temp3_max
-rw-r--r--  1 root root 4096 Mar 13 06:16 temp3_min
-rw-r--r--  1 root root 4096 Mar 13 06:16 temp3_offset
-rw-r--r--  1 root root 4096 Mar 13 06:16 temp3_type
-rw-r--r--  1 root root 4096 Mar 11 19:25 uevent
root@fireball / #
 

I've used the kernel drivers for ages and have had no issues with it so
I keep using it.  I get all the fans speeds, temps and such that I have
sensors for.  If I enable the setting in my BIOS, I can even alter the
way the fans are temp controlled.  Since the mobo does such a good job
on that, I never had the reason to use that.

Dale

:-)  :-)


[-- Attachment #2: Type: text/html, Size: 11610 bytes --]

Re: [gentoo-user] Re: heat codes

[Dale]

Peter Humphrey wrote:
> On Thursday 12 March 2015 19:38:56 Dale wrote:
>
>> I build everything into the kernel and I don't even install
>> lm_sensors. I haven't installed that in ages.
> Does that mean that your gkrellm can't display temperatures?
>

It's been displaying temps for many years.  I posted a list in my reply
to Mick.  I also can get voltages but don't have it set to show them.  I
do also monitor temps on the hard drives.  That's done through the smart
thingy. 

Dale

:-)  :-) 

Re: [gentoo-user] Re: heat codes

[Dale]

Tuomo Hartikainen wrote:
> On 150312 1835, Dale wrote:
>> wabenbau@gmail.com wrote:
>>> Something similar happened to me. I accidentally pressed F6 while
>>> focused gkrellm but didn't noticed it. Some time later I realized that
>>> the fontsize of gkrellm was increased so that it's height doesn't fit
>>> to the screen anymore. Fist I thought that it has something to do with
>>> the latest update. It took some time till I recognized that I simply
>>> had to press F7 to restore the fontsize to its former height. :-)
>>>
>>> --
>>> Regards
>>> wabe
>>>
>> Well, you should have seen the look on my face the other day when
>> Firefox went FULL SCREEN.  I mean full screen like it does when I hit F
>> and am watching a video.  Heck, I didn't have a menu at the top,  To
>> this day, I have no clue what I did.  I was typing a comment on a social
>> site and all of the sudden, it went sucky.  Still no clue but thank
>> goodness it fixed itself after I killed it and restarted. 
>>
>> Dale
> Try pressing F11 in Firefox? ;)

I think I tried that.  I think I tried all the F* keys.  I was also able
to ctrl F* to get to another desktop and use a second browser to try and
figure the thing out.  I tried a few things I found online but none of
them worked.  Also weird, I was typing normal characters when it went
weird on me just like I am in this email.  No ctrl, alt or other keys. 
The closest I got to those was the shift key for capitol letters. 

I just hope I never run into that again.  o_O 

Dale

:-)  :-) 

Re: [gentoo-user] Re: heat codes

[Peter Humphrey]

On Friday 13 March 2015 06:27:00 Dale wrote:
> Peter Humphrey wrote:
> > On Thursday 12 March 2015 19:38:56 Dale wrote:
> >> I build everything into the kernel and I don't even install
> >> lm_sensors. I haven't installed that in ages.
> > 
> > Does that mean that your gkrellm can't display temperatures?
> 
> It's been displaying temps for many years.  I posted a list in my
> reply to Mick.  I also can get voltages but don't have it set to show
> them.  I do also monitor temps on the hard drives.  That's done
> through the smart thingy.

I don't know what led you to list that directory, but now that I look 
into my own setup I see I'm using kernel modules too. I know I used to 
use lm_sensors at one time, but genlop doesn't know about it so I must 
have omitted it when I last reinstalled.

# ls -l /sys/devices/platform
total 0
drwxr-xr-x 3 root root    0 Mar 13 11:49 alarmtimer
drwxr-xr-x 4 root root    0 Mar 13 11:49 coretemp.0
drwxr-xr-x 5 root root    0 Mar 13 11:49 i8042
drwxr-xr-x 3 root root    0 Mar 13 11:49 pcspkr
drwxr-xr-x 3 root root    0 Mar 13 11:49 platform-framebuffer.0
drwxr-xr-x 3 root root    0 Mar 13 11:49 PNP0C0C:00
drwxr-xr-x 2 root root    0 Mar 13 11:49 power
-rw-r--r-- 1 root root 4.0K Mar 13 11:49 uevent
drwxr-xr-x 3 root root    0 Mar 13 11:49 vboxdrv.0

-- 
Rgds
Peter.

Re: [gentoo-user] Re: heat codes

[Dale]

Peter Humphrey wrote:
> On Friday 13 March 2015 06:27:00 Dale wrote:
>> Peter Humphrey wrote:
>>> On Thursday 12 March 2015 19:38:56 Dale wrote:
>>>> I build everything into the kernel and I don't even install
>>>> lm_sensors. I haven't installed that in ages.
>>> Does that mean that your gkrellm can't display temperatures?
>> It's been displaying temps for many years.  I posted a list in my
>> reply to Mick.  I also can get voltages but don't have it set to show
>> them.  I do also monitor temps on the hard drives.  That's done
>> through the smart thingy.
> I don't know what led you to list that directory, but now that I look 
> into my own setup I see I'm using kernel modules too. I know I used to 
> use lm_sensors at one time, but genlop doesn't know about it so I must 
> have omitted it when I last reinstalled.
>
> # ls -l /sys/devices/platform
> total 0
> drwxr-xr-x 3 root root    0 Mar 13 11:49 alarmtimer
> drwxr-xr-x 4 root root    0 Mar 13 11:49 coretemp.0
> drwxr-xr-x 5 root root    0 Mar 13 11:49 i8042
> drwxr-xr-x 3 root root    0 Mar 13 11:49 pcspkr
> drwxr-xr-x 3 root root    0 Mar 13 11:49 platform-framebuffer.0
> drwxr-xr-x 3 root root    0 Mar 13 11:49 PNP0C0C:00
> drwxr-xr-x 2 root root    0 Mar 13 11:49 power
> -rw-r--r-- 1 root root 4.0K Mar 13 11:49 uevent
> drwxr-xr-x 3 root root    0 Mar 13 11:49 vboxdrv.0
>


From my understanding, you can use either the kernel drivers or
lm-sensors.  Many years ago, I sort of got bored installing lm-sensors
and running the setup stuff all the time.  I seem to recall, you have to
do it again when you upgrade the kernel too.  Anyway, I started using
the kernel drivers and I've been doing it that way ever since.  Hey, it
works.  It also gets updated with each kernel upgrade too. 

I'm all for what works.  It works for me and seems it works for you as
well so, yeppie!!!   Given I been battling the flu for a few weeks,
yeppie is about as good as it gets right now.  I never could dance
anyway.  ;-)

Oh, I listed my sensor stuff because Mick listed his.  I thought we
could compare what we each get.  It looks the same to me.  I just didn't
see the need in posting it twice when odds are you will see both posts
anyway.  :-) 

Dale

:-)  :-) 

Re: [gentoo-user] Re: heat codes

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 2108 bytes --]

On Friday 13 Mar 2015 15:49:38 Dale wrote:
> Peter Humphrey wrote:
> > On Friday 13 March 2015 06:27:00 Dale wrote:
> >> Peter Humphrey wrote:
> >>> On Thursday 12 March 2015 19:38:56 Dale wrote:
> >>>> I build everything into the kernel and I don't even install
> >>>> lm_sensors. I haven't installed that in ages.
> >>> 
> >>> Does that mean that your gkrellm can't display temperatures?
> >> 
> >> It's been displaying temps for many years.  I posted a list in my
> >> reply to Mick.  I also can get voltages but don't have it set to show
> >> them.  I do also monitor temps on the hard drives.  That's done
> >> through the smart thingy.
> > 
> > I don't know what led you to list that directory, but now that I look
> > into my own setup I see I'm using kernel modules too. I know I used to
> > use lm_sensors at one time, but genlop doesn't know about it so I must
> > have omitted it when I last reinstalled.
> > 
> > # ls -l /sys/devices/platform
> > total 0
> > drwxr-xr-x 3 root root    0 Mar 13 11:49 alarmtimer
> > drwxr-xr-x 4 root root    0 Mar 13 11:49 coretemp.0
> > drwxr-xr-x 5 root root    0 Mar 13 11:49 i8042
> > drwxr-xr-x 3 root root    0 Mar 13 11:49 pcspkr
> > drwxr-xr-x 3 root root    0 Mar 13 11:49 platform-framebuffer.0
> > drwxr-xr-x 3 root root    0 Mar 13 11:49 PNP0C0C:00
> > drwxr-xr-x 2 root root    0 Mar 13 11:49 power
> > -rw-r--r-- 1 root root 4.0K Mar 13 11:49 uevent
> > drwxr-xr-x 3 root root    0 Mar 13 11:49 vboxdrv.0
> 
> From my understanding, you can use either the kernel drivers or
> lm-sensors.  

Really?

I didn't know this.  I have installed both, seemingly without any ill effects.


> Many years ago, I sort of got bored installing lm-sensors
> and running the setup stuff all the time.  I seem to recall, you have to
> do it again when you upgrade the kernel too.  

I didn't know this either.  Anyway, gkrellm works happily which is what I 
primarily use, unless I'm login in remotely in which case I just run 'watch -d 
sensors' if I want to check what's happening on the MoBo.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]