All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Vickers <daehenoc@optusnet.com.au>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] sensors report all zero readings on Dell PowerEdge
Date: Wed, 24 Oct 2007 10:29:19 +0000	[thread overview]
Message-ID: <471F1E7F.9070907@optusnet.com.au> (raw)
In-Reply-To: <471C8AA4.7090903@optusnet.com.au>

Hi,

Frank Phillips wrote:
> On 10/22/07, Greg Vickers <daehenoc@optusnet.com.au> wrote:
>> Hi,
>>
>> I have installed lm-sensors v2.10.1-3 on a Dell PowerEdge 830 with
>> Debian Etch (stable) installed on it.  (This version is the version of
>> lm-sensors that is part of Debian Etch.)  sensors-detect works and
> Try running a more recent version of the script:
> 
> http://www.lm-sensors.org/browser/lm-sensors/trunk/prog/detect/sensors-detect?revI66&format=txt

I ran that script and it didn't detect any extra modules apart from the 
ones that I have already loaded.

> By looking at the specs, the Poweredge 830 is an IPMI-controlled
> machine. The Baseboard Management Controller controls all the sensors.
> You will need support in your kernel for IPMI and ipmisensors. The
> patch for ipmisensors is here if it is not already in your distro
> kernel (CONFIG_SENSORS_IPMI):

Huh, CONFIG_SENSORS_IPMI is not present in 2.6.18 on Debian.

> http://bmcsensors-26.sourceforge.net/

Ah, thanks.  In the meantime I've found ipmitool for Debian and 
check_ipmi_sensors.pl for Nagios, which hopefully will do what I want it 
to do.

Thanks,
Greg

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

      parent reply	other threads:[~2007-10-24 10:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-22 11:33 [lm-sensors] sensors report all zero readings on Dell PowerEdge 830 Greg Vickers
2007-10-23 22:42 ` [lm-sensors] sensors report all zero readings on Dell PowerEdge Frank Phillips
2007-10-24 10:29 ` Greg Vickers [this message]

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=471F1E7F.9070907@optusnet.com.au \
    --to=daehenoc@optusnet.com.au \
    --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.