From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: heat codes
Date: Thu, 26 Feb 2015 20:13:07 +0000 (UTC) [thread overview]
Message-ID: <loom.20150226T210209-533@post.gmane.org> (raw)
In-Reply-To: loom.20150226T190630-278@post.gmane.org
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
next prev parent reply other threads:[~2015-02-26 20:13 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 ` James [this message]
2015-02-26 23:02 ` [gentoo-user] " 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 ` [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=loom.20150226T210209-533@post.gmane.org \
--to=wireless@tampabay.rr.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