From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] heat codes
Date: Thu, 26 Feb 2015 17:26:44 -0600 [thread overview]
Message-ID: <54EFABB4.7050104@gmail.com> (raw)
In-Reply-To: <loom.20150226T190630-278@post.gmane.org>
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
:-) :-)
next prev parent reply other threads:[~2015-02-26 23:26 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
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 ` Dale [this message]
2015-02-27 1:31 ` 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=54EFABB4.7050104@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