From: Robert Kaiser <kairo@kairo.at>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] RFC: nct6776f support in the w83627ehf and fan RPM
Date: Thu, 10 Mar 2011 20:08:28 +0000 [thread overview]
Message-ID: <ilbb3t$sbb$1@dough.gmane.org> (raw)
In-Reply-To: <BE6F61DB46364D4B839ED3F50CDFDFAB@portable2>
Robert Kaiser schrieb:
> nct6775-isa-0290
> in1: +1.11 V (min = +0.00 V, max = +0.00 V) ALARM
> in4: +1.02 V (min = +0.00 V, max = +0.00 V) ALARM
> in5: +1.05 V (min = +0.00 V, max = +0.00 V) ALARM
> in6: +1.08 V (min = +0.00 V, max = +0.00 V) ALARM
So I guess we don't know what they are and therefore they have the
default names and probably "bogus" values, right?
> fan2: 1110 RPM (min = 0 RPM, div = 32) ALARM
This is the CPU fan here, FWIW.
> SYSTIN: +39.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = diode
> CPUTIN: +38.0°C (high = +80.0°C, hyst = +75.0°C) sensor = diode
> SMBUSMASTER 1: +54.0°C (high = +80.0°C, hyst = +75.0°C) sensor = diode
> PCH_CHIP_CPU_MAX_TEMP: +65.0°C
> SMBUSMASTER 2: +0.0°C (high = +80.0°C, hyst = +75.0°C)
What do those actually mean? Is there some doc about them that an
non-wizard like me can understand?
Robert Kaiser
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2011-03-10 20:08 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 12:38 [lm-sensors] RFC: nct6776f support in the w83627ehf and fan RPM Ian Dobson
2011-03-06 17:07 ` Guenter Roeck
2011-03-06 17:21 ` Ian Dobson
2011-03-06 18:47 ` Guenter Roeck
2011-03-06 19:40 ` Ian Dobson
2011-03-06 20:05 ` Guenter Roeck
2011-03-07 2:50 ` Robert Kaiser
2011-03-07 5:21 ` Guenter Roeck
2011-03-07 14:59 ` Robert Kaiser
2011-03-07 16:03 ` Guenter Roeck
2011-03-10 0:25 ` Robert Kaiser
2011-03-10 3:45 ` Guenter Roeck
2011-03-10 5:06 ` Guenter Roeck
2011-03-10 5:20 ` [lm-sensors] RFC: nct6776f support in the w83627ehf and fan Ian Dobson
2011-03-10 11:35 ` Guenter Roeck
2011-03-10 11:53 ` Guenter Roeck
2011-03-10 11:57 ` I.dobson
2011-03-10 13:10 ` I.dobson
2011-03-10 17:32 ` Guenter Roeck
2011-03-10 20:05 ` Robert Kaiser
2011-03-10 20:08 ` Robert Kaiser [this message]
2011-03-10 20:27 ` Ian Dobson
2011-03-10 21:03 ` Robert Kaiser
2011-03-10 22:11 ` Guenter Roeck
2011-03-10 22:15 ` Guenter Roeck
2011-03-10 23:17 ` Robert Kaiser
2011-03-10 23:38 ` Guenter Roeck
2011-03-11 0:04 ` Robert Kaiser
2011-03-11 0:29 ` Guenter Roeck
2011-03-11 0:58 ` Robert Kaiser
2011-03-11 1:07 ` Guenter Roeck
2011-03-11 17:09 ` Robert Kaiser
2011-03-11 17:47 ` Guenter Roeck
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='ilbb3t$sbb$1@dough.gmane.org' \
--to=kairo@kairo.at \
--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.