From: Harm Geerts <harmgeerts@home.nl>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: lm_sensors problem
Date: Mon, 13 Feb 2006 03:51:14 +0100 [thread overview]
Message-ID: <200602130351.14879.harmgeerts@home.nl> (raw)
In-Reply-To: <1cc2dc830602121826o89bba75g1695a78bc9e687f@mail.gmail.com>
On Monday 13 February 2006 03:26, Allan Spagnol Comar wrote:
> Hi all,
>
> I had installed lm_sensors and kernel modules, now when I run sensors
> command I got:
>
> monstro ~ # sensors
> it8712-isa-0290
> Adapter: ISA adapter
> VCore 1: +1.41 V (min = +1.42 V, max = +1.57 V) ALARM
> VCore 2: +0.00 V (min = +2.40 V, max = +2.61 V) ALARM
> +3.3V: +6.53 V (min = +3.14 V, max = +3.46 V) ALARM
> +5V: +5.00 V (min = +4.76 V, max = +5.24 V)
> +12V: +11.84 V (min = +11.39 V, max = +12.61 V)
> -12V: -4.17 V (min = -12.63 V, max = -11.41 V) ALARM
> -5V: -13.64 V (min = -5.26 V, max = -4.77 V) ALARM
> Stdby: +4.89 V (min = +4.76 V, max = +5.24 V)
> VBat: +3.12 V
> fan1: 0 RPM (min = 0 RPM, div = 8)
> fan2: 0 RPM (min = 3013 RPM, div = 8) ALARM
> fan3: 6750 RPM (min = 3013 RPM, div = 8)
> M/B Temp: +35 C (low = +15 C, high = +40 C) sensor = thermistor
> CPU Temp: +40 C (low = +15 C, high = +45 C) sensor = thermistor
> Temp3: +27 C (low = +15 C, high = +45 C) sensor = thermistor
>
> how you all can see VCore2 is unavailable and -5 and -12 information
> seems to be switched,
>
> does anyone had a clue about it, I am running on a nvidia4 base
> motherboard.
You'll need to change some settings in /etc/sensors.conf for your sensor chip.
Your output seems a lot like mine with a default config so I'll paste the
relevant part of my config, I have a Asus A8N SLI-Deluxe with a
it8712-isa-0290.
After you've modified /etc/sensors.conf you need to run `sensors -s` for the
changes to take effect. You also need to run `sensors -s` after a reboot.
Unless you use the sensors init.d script you can add that command
to /etc/conf.d/local.start
# cat /etc/sensors.conf
chip "it87-*" "it8712-*"
# Modified for Asus A8N SLI-Deluxe
# Voltage monitors as advised in the It8705 data sheet
label in0 "VCore 1"
label in1 "VCore 2"
label in2 "+3.3V"
label in3 "+5V"
label in4 "+12V"
label in5 "-5V"
label in6 "-12V"
label in7 "Stdby"
label in8 "VBat"
# vid is not monitored by IT8705F
# comment out if you have IT8712
ignore vid
ignore in1
# Incubus Saturnus reports that the IT87 chip on Asus A7V8X-X seems
# to report the VCORE voltage approximately 0.05V higher than the board's
# BIOS does. Although it doesn't make much sense physically, uncommenting
# the next line should bring the readings in line with the BIOS' ones in
# this case.
# compute in0 -0.05+@ , @+0.05
# If 3.3V reads 2X too high (Soyo Dragon and Asus A7V8X-X, for example),
# comment out following line.
# compute in2 2*@ , @/2
#
compute in3 ((6.8/10)+1)*@ , @/((6.8/10)+1)
compute in4 ((30/10) +1)*@ , @/((30/10) +1)
# For this family of chips the negative voltage equation is different from
# the lm78. The chip uses two external resistor for scaling but one is
# tied to a positive reference voltage. See ITE8705/12 datasheet (SIS950
# data sheet is wrong)
# Vs = (1 + Rin/Rf) * Vin - (Rin/Rf) * Vref.
# Vref = 4.096 volts, Vin is voltage measured, Vs is actual voltage.
# The next two are negative voltages (-12 and -5).
# The following formulas must be used. Unfortunately the datasheet
# does not give recommendations for Rin, Rf, but we can back into
# them based on a nominal +2V input to the chip, together with a 4.096V Vref.
# Formula:
# actual V = (Vmeasured * (1 + Rin/Rf)) - (Vref * (Rin/Rf))
# For -12V input use Rin/Rf = 6.68
# For -5V input use Rin/Rf = 3.33
# Then you can convert the forumula to a standard form like:
compute in5 (7.67 * @) - 27.36 , (@ + 27.36) / 7.67
compute in6 (4.33 * @) - 13.64 , (@ + 13.64) / 4.33
#
# this much simpler version is reported to work for a
# Elite Group K7S5A board
#
# compute in5 -(36/10)*@, -@/(36/10)
# compute in6 -(56/10)*@, -@/(56/10)
#
compute in7 ((6.8/10)+1)*@ , @/((6.8/10)+1)
set in0_min 1.4 * 0.95
set in0_max 1.4 * 1.05
set in1_min 2.4
set in1_max 2.6
set in2_min 3.3 * 0.95
set in2_max 3.3 * 1.05
set in3_min 5.0 * 0.95
set in3_max 5.0 * 1.05
set in4_min 12 * 0.95
set in4_max 12 * 1.05
set in5_max -5 * 0.95
set in5_min -5 * 1.05
set in6_max -12 * 0.95
set in6_min -12 * 1.05
set in7_min 5 * 0.95
set in7_max 5 * 1.05
#the chip does not support in8 min/max
# Temperature
#
# Important - if your temperature readings are completely whacky
# you probably need to change the sensor type.
# Adujst and uncomment the appropriate lines below.
# The old method (modprobe it87 temp_type=0xXX) is no longer supported.
#
# 2 = thermistor; 3 = thermal diode; 0 = unused
# set sensor1 3
# set sensor2 3
# set sensor3 3
# If a given sensor isn't used, you will probably want to ignore it
# (see ignore statement right below).
label temp1 "CPU Temp"
set temp1_over 50
set temp1_low 15
label temp2 "MB Temp"
set temp2_over 45
set temp2_low 15
# ignore temp3
label temp3 "Temp3"
set temp3_over 40
set temp3_low 15
# The A7V8X-X has temperatures inverted, and needs a conversion for
# CPU temp. Thanks to Preben Randhol for the formula.
# label temp1 "CPU Temp"
# label temp2 "M/B Temp"
# compute temp1 (-15.096+1.4893*@), (@+15.096)/1.4893
# The A7V600 also has temperatures inverted, and needs a different
# conversion for CPU temp. Thanks to Dariusz Jaszkowski for the formula.
# label temp1 "CPU Temp"
# label temp2 "M/B Temp"
# compute temp1 (@+128)/3, (3*@-128)
# Fans
set fan1_min 0
set fan2_min 3000
ignore fan2
ignore fan3
set fan3_min 3000
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-02-13 2:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 2:26 [gentoo-user] lm_sensors problem Allan Spagnol Comar
2006-02-13 2:51 ` Harm Geerts [this message]
2006-02-13 11:40 ` [gentoo-user] " Allan Spagnol Comar
2006-02-14 2:00 ` Allan Spagnol Comar
2006-02-14 17:56 ` [gentoo-user] " Jarry
2006-02-14 18:14 ` Holly Bostick
2006-02-14 18:41 ` Jarry
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=200602130351.14879.harmgeerts@home.nl \
--to=harmgeerts@home.nl \
--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