public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Justin Piszcz" <jpiszcz@lucidpixels.com>
To: "'Guenter Roeck'" <linux@roeck-us.net>
Cc: <linux-kernel@vger.kernel.org>, <lm-sensors@lm-sensors.org>
Subject: RE: [lm-sensors] 3.10: NCT6776F sensor question with Supermicro X9SRL-F motherboard
Date: Wed, 3 Jul 2013 12:47:47 -0400	[thread overview]
Message-ID: <008001ce780d$0d1a79f0$274f6dd0$@lucidpixels.com> (raw)
In-Reply-To: <20130703163311.GB12506@roeck-us.net>



-----Original Message-----
From: Guenter Roeck [mailto:linux@roeck-us.net] 
Sent: Wednesday, July 03, 2013 12:33 PM
To: Justin Piszcz
Cc: linux-kernel@vger.kernel.org; lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] 3.10: NCT6776F sensor question with Supermicro
X9SRL-F motherboard

[ .. ]
> 
Can you install superiotool and run "sudo superiotool -V -e" ?
I would like to see raw data from the superio chip.

# superiotool -V -e
superiotool r6637
..
Probing for Nuvoton Super I/O (sid=0xfc) at 0x164e...
Found Nuvoton WPCM450 (id=0x1a11, rev=0x00) at 0x164e
Probing for Nuvoton Super I/O at 0x2e...
Found Nuvoton NCT6776F (C) (id=0xc333) at 0x2e

[ .. ]

You have to specify the raw attribute names, not the symbolic ones.
You see the raw attribute names with "sensors -u".

# sensors -u
PCH_CHIP_TEMP:
  temp8_input: 0.000
PCH_CPU_TEMP:
  temp9_input: 0.000
PCH_MCH_TEMP:
  temp10_input: 0.000

Tried:
    ignore PCH_CHIP_TEMP
    ignore temp8_input

For some reason still can't get rid of it appearing:
PCH_CHIP_TEMP:   +0.0 C  
(..as well as the others)


> $ sensors  |tail -n 4
> PCH_CHIP_TEMP:   +0.0 C
> PCH_CPU_TEMP:    +0.0 C
> PCH_MCH_TEMP:    +0.0 C
> 
> Ignoring intrusion works though:
>     ignore intrusion0
>     ignore intrusion1
> 
Does the board have intrusion detection headers ? If so, you could close
(bridge) the header(s) which should get rid of the alarm.

ftp://ftp.supermicro.com/CDR-X9-UP_1.21_for_Intel_X9_UP_platform/MANUALS/X9S
RL-F/X9SRL-F.pdf
@ page 49 (2-23) [motherboard: JL1 2-pin header]

-




  reply	other threads:[~2013-07-03 16:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03 12:35 3.10: NCT6776F sensor question with Supermicro X9SRL-F motherboard Justin Piszcz
2013-07-03 14:42 ` [lm-sensors] " Guenter Roeck
2013-07-03 16:08   ` Justin Piszcz
2013-07-03 16:33     ` Guenter Roeck
2013-07-03 16:47       ` Justin Piszcz [this message]
2013-07-03 17:17         ` Guenter Roeck
2013-07-03 17:21           ` Justin Piszcz
2013-07-03 20:56             ` Guenter Roeck
     [not found]               ` <00ad01ce7830$3b135890$b13a09b0$@lucidpixels.com>
2013-07-03 21:00                 ` Justin Piszcz
2013-07-03 22:28                   ` Guenter Roeck
2013-07-11  8:47   ` Jean Delvare
2013-07-11 13:57     ` Justin Piszcz

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='008001ce780d$0d1a79f0$274f6dd0$@lucidpixels.com' \
    --to=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lm-sensors@lm-sensors.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