public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: heat codes
Date: Thu, 12 Mar 2015 19:38:56 -0500	[thread overview]
Message-ID: <550231A0.5060604@gmail.com> (raw)
In-Reply-To: <loom.20150313T005242-32@post.gmane.org>

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

:-)  :-) 



  reply	other threads:[~2015-03-13  0:39 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
2015-02-28 11:33   ` Mick
2015-03-12 23:53     ` James
2015-03-13  0:38       ` Dale [this message]
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=550231A0.5060604@gmail.com \
    --to=rdalek1967@gmail.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