All of lore.kernel.org
 help / color / mirror / Atom feed
From: garman@raw-sewage.net (Matt Garman)
To: lm-sensors@vger.kernel.org
Subject: what exactly does DISCONNECT mean?
Date: Thu, 19 May 2005 06:25:27 +0000	[thread overview]
Message-ID: <20041227070416.GA7771@raw-sewage.net> (raw)


The output of "sensors" looks like this:

lm90-i2c-2-4c
Adapter: SMBus nForce2 adapter at 5100
M/B Temp:    +28 C  (low  =    +0 C, high =   +70 C)   
CPU Temp: +127.0 C  (low  =  +0.0 C, high = +70.0 C)   DISCONNECT
M/B Crit:    +85 C  (hyst =   +75 C)                   
CPU Crit:    +85 C  (hyst =   +75 C)                   

I'm not sure what "DISCONNECT" means, exactly.  
The output of "sensors" looks like this:

lm90-i2c-2-4c
Adapter: SMBus nForce2 adapter at 5100
M/B Temp:    +28 C  (low  =    +0 C, high =   +70 C)   
CPU Temp: +127.0 C  (low  =  +0.0 C, high = +70.0 C)   DISCONNECT
M/B Crit:    +85 C  (hyst =   +75 C)                   
CPU Crit:    +85 C  (hyst =   +75 C)                   

I'm not sure what "DISCONNECT" means, exactly... my guess is that
lm-sensors is not getting any kind of meaningful response from the
hardware.

For what it's worth, the CPU Temp reading in the BIOS also shows
127.0 degrees C.  So at least it's consistent :)

But if a sensor is truly "not connected", do you happen to know
where I can "connect" the sensor, i.e. remedy this problem?  Can
this kind of thing be fixed in software, the BIOS or on the board
itself, or is this sensor just broken?  ...or does it all depend on
my particular hardware?

If it helps, the board is a brand-new Chaintech 7NIF2 "Summit".
Everything else appears to be working correctly.

If you have any insights or suggestions, I'd appreciate it!

Thank you,
Matt

-- 
Matt Garman
email at: http://raw-sewage.net/index.php?file=email

             reply	other threads:[~2005-05-19  6:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:25 Matt Garman [this message]
2005-05-19  6:25 ` what exactly does DISCONNECT mean? Matt Garman
2005-05-19  6:25 ` 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=20041227070416.GA7771@raw-sewage.net \
    --to=garman@raw-sewage.net \
    --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.