From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to
Date: Tue, 09 Mar 2010 09:30:38 +0000 [thread overview]
Message-ID: <20100309103038.54cdd147@hyperion.delvare> (raw)
In-Reply-To: <20100305222015.GR11436@alpha.zimage.com>
On Tue, 9 Mar 2010 01:05:58 -0800, Phillip Pi wrote:
> > Please be specific. What chip is it, which voltages are missing?
>
> AMD Athlon X2 939 CPU 4600+ and MSI K8N NEO4-F (MS-7125) motherboard
> (NVIDIA nForce4). See my secondary computer details at:
> http://alpha.zimage.com/~ant/antfarm/about/computers.txt
>
> As for voltages, Kernel 2.6.30 and earlier said something like:
> $ sensors -f
> k8temp-pci-00c3
> Adapter: PCI adapter
> Core0 Temp: +80.6°F
> ...
Please stop editing outputs. You are stripping exactly the information
I asked for (what chip it is.)
> Adapter: ISA adapter
> VCore: +1.12 V (min = +2.11 V, max = +2.48 V)
> +3.3V: +3.28 V (min = +1.46 V, max = +0.21 V)
> +5V: +4.97 V (min = +0.89 V, max = +0.22 V)
> +12V: +11.43 V (min = +0.24 V, max = +9.67 V)
> -12V: +0.72 V (min = -5.37 V, max = +0.63 V)
> -5V: +5.10 V (min = +1.18 V, max = -7.66 V)
> V5SB: +5.59 V (min = +0.13 V, max = +0.48 V)
> VBat: +1.55 V (min = +2.24 V, max = +3.46 V)
> fan1: 2360 RPM (min = 1622 RPM, div = 4)
> fan2: 2376 RPM (min = 1985 RPM, div = 4)
> temp1: +82.4°F (high = +201.2°F, hyst = +221.0°F) sensor =
> thermistor
> temp2: +86.0°F (high = +176.0°F, hyst = +167.0°F) sensor =
> thermistor
> beep_enable:enabled
OK, and how do I compare this with 2.6.32 if you do not provide the
output there?
> > Remember that the output of sensors is influenced by the contents of
> > libsensors configuration files (/etc/sensors.conf, /etc/sensors3.conf
> > and/or /etc/sensors.d/* depending on your libsensors version and
> > distribution choices.)
>
> I always keep my lm_sensors packages updated so whatever they gave me is
> what I use. The only I edited was /etc/modules based on sensors-detect
> results (w83627ehf). I do not recall editing sensors*.conf files or
> being asked to do so.
This doesn't mean they haven't changed. We ship a default configuration
file, which does change over time. That being said, it does _not_
contain arbitrary ignore statements, so should not be responsible for
inputs mysteriously disappearing.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2010-03-09 9:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 22:20 [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to Phillip Pi
2010-03-06 0:02 ` Luca Tettamanti
2010-03-08 20:57 ` Luca Tettamanti
2010-03-08 21:10 ` Phillip Pi
2010-03-08 21:17 ` Jean Delvare
2010-03-08 21:28 ` Luca Tettamanti
2010-03-08 21:28 ` Phillip Pi
2010-03-08 21:31 ` Phillip Pi
2010-03-08 21:34 ` Luca Tettamanti
2010-03-08 21:38 ` Jean Delvare
2010-03-08 21:39 ` Phillip Pi
2010-03-08 21:43 ` Phillip Pi
2010-03-08 21:44 ` Luca Tettamanti
2010-03-09 8:40 ` Jean Delvare
2010-03-09 8:45 ` Jean Delvare
2010-03-09 8:48 ` Jean Delvare
2010-03-09 9:05 ` Phillip Pi
2010-03-09 9:30 ` Jean Delvare [this message]
2010-03-09 14:20 ` Phillip Pi
2010-03-09 16:35 ` Jean Delvare
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=20100309103038.54cdd147@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=lm-sensors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.