From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] SuperMicro X7SPE-HF configuration
Date: Sat, 04 Sep 2010 13:42:28 +0000 [thread overview]
Message-ID: <20100904154228.36893ea3@hyperion.delvare> (raw)
In-Reply-To: <70021574-9260-4E1E-88F8-AE313D6A94B8@gmail.com>
Hi Scott,
On Mon, 30 Aug 2010 16:55:53 -0400, Scott Shanafelt wrote:
> chip "w83627dhg-*"
>
> label in0 "Vcore"
> label in1 "Vnbcore"
This is "+1.05V" in SuperMicro's configuration file.
> label in2 "AVCC"
> label in3 "3VCC"
> set in3_min 3.3 * 0.90
> set in3_max 3.3 * 1.10
> label in4 "VDIMM"
> label in5 "+5V"
> compute in5 @*4, @/4
> label in6 "+12V"
> compute in6 @*16, @/16
> set in6_min 12 * 0.90
> set in6_max 12 * 1.10
> label in7 "VSB"
Better labelled as "3V3B".
> label in8 "Vbat"
>
> label fan1 "fan1"
> ignore fan1
> label fan2 "fan2"
> ignore fan2
> label fan3 "fan3"
> ignore fan3
> label fan4 "Case Fan"
> label fan5 "fan5"
> ignore fan5
Most of these labels are pointless, they are double no-ops (once
because they don't carry any meaning, twice because you end up ignoring
the input anyway.) What we want is fan locations, like:
label fan2 "CPU Fan"
label fan4 "Case Fan"
We also don't want to ignore a fan which exists on the board but you
happen to not use. "ignore fan2" shouldn't be there.
>
> label temp1 "MB Temp"
> label temp2 "CPU Temp"
> label temp3 "Case Temp"
>
> ignore cpu0_vid
I've added an updated configuration file here:
http://www.lm-sensors.org/wiki/Configurations/SuperMicro/X7SPA
Thanks for your contribution.
--
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-09-04 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 20:55 [lm-sensors] SuperMicro X7SPE-HF configuration Scott Shanafelt
2010-08-30 22:18 ` Jeff Rickman
2010-09-04 13:42 ` Jean Delvare [this message]
2010-09-04 15:25 ` Scott Shanafelt
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=20100904154228.36893ea3@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.