All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Schulthess <fsch@truthbox.ch>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Fan Control on 6027R TRF running Debian Wheezy
Date: Sun, 12 Oct 2014 16:12:23 +0000	[thread overview]
Message-ID: <543AA867.9010906@truthbox.ch> (raw)
In-Reply-To: <5437E87B.8030206@truthbox.ch>


[-- Attachment #1.1: Type: text/plain, Size: 1872 bytes --]

Dear Phil,

thanks a lot for the quick reply! Great to see that this mailing list is
so active.

On 10/10/2014 04:53 PM, Phil Pokorny wrote:
> 
> On Friday, October 10, 2014, Felix Schulthess <fsch@truthbox.ch
> <mailto:fsch@truthbox.ch>> wrote:
> 
>     Dear lm-sensors Team,
> 
>     on a 6027R TRF, I run the latest Debian Wheezy. I have a problem with
>     the server, because I cannot control fan speed anymore.
> 
> 
> Your system has an onboard management processor which supports IPMI. You
> should not use lm-sensors. Install IPMITOOL or FreeIPMI and use those
> tools ( or super doctor ) to read sensors.
> 
> You cannot control the fan speeds. They are managed by the onboard
> controller. You can choose one of several profiles in the bios but that
> is it.

That explains a lot. Thank you for your help, I am going to do some
further research in this direction and read up on FreeIPMI.

Still, if I can't control the fan speeds but they are instead controlled
by some onboard controller, then how could the installation on the
fancontrol and lm-sensors mess up the control loop so bad? This still
keeps me wondering.

Maybe, the sensors somehow blocked the CPU temperature readout. This
could have caused the superdoctor program to resort to some failsafe
behavior (i.e. spinning the fans up to max RPM). Just wondering.

>     Since then I didn't manage to regain control of the fans. Even after a
>     reboot the fans start to speed. Also, removing the installed packages
>     again does not help.
> 
> 
> You probably need to reset the management controller. The easiest way is
> to shutdown the system and unplug it for several MINUTES to discharge
> all the capacitors and insure everything resets.  Then plug in and turn
> on again.

Thank you, I already tried that -- without success.

Best, Felix


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

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

  parent reply	other threads:[~2014-10-12 16:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-10 14:08 [lm-sensors] Fan Control on 6027R TRF running Debian Wheezy Felix Schulthess
2014-10-10 14:53 ` Phil Pokorny
2014-10-12 16:12 ` Felix Schulthess [this message]
2014-10-12 16:53 ` Felix Schulthess
2014-10-12 17:15 ` Phil Pokorny
2014-10-12 17:20 ` 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=543AA867.9010906@truthbox.ch \
    --to=fsch@truthbox.ch \
    --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.