All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH] On n2100 systems,
Date: Fri, 19 Oct 2007 15:36:05 +0000	[thread overview]
Message-ID: <20071019173605.1cfcb233@hyperion.delvare> (raw)
In-Reply-To: <20071016100857.GA25544@kos.to>

Hi Riku, Lennert,

On Thu, 18 Oct 2007 11:56:04 +0300, Riku Voipio wrote:
> Redboot does not touch the fans. The problem is that the fanspeed
> reading isn't reliable. The "speed" mode tries to adjust pwm to get
> the fanspeed to match whatever is requested in "expect" registers,
> but never to enough to get the fans to run.

I see. I have to admit that it isn't very smart from Fintek to set the
"speed mode" by default on this chip. It would be safer to default to
full speed. OTOH the default speed target seems to be 4297 RPM if I
read the datasheet correctly, which is high enough. If the fan speed
reading isn't reliable (which admittedly is a bad thing to start with)
I'd expect the chip to set the fan output to the max. Isn't it the case?

> As Lennert mentioned, Software provided by Thecus
> does set the fans running by default (by combination of
> a kernel driver and userland scripts). It's not sold as a
> general purpose PC.
> 
> In my experience the risk of literal "frying" is very very low,
> but even with just one one disk inside and finnish cool weather,
> smartmontools have reported the hard drive going over the
> operating temperature limit (60c).
> 
> With, say, 2x10 rpm disks inside the case, I'd say the risk of
> disks breaking down prematurely is very real. And I do not
> want to take the responsibility of people reporting that "installing
> Debian caused my hardware to break down"

I see. But I can't think of a reason why this can't be simply solved in
user-space, as Thecus is doing in their own product. This would be much
easier than the kernel patches you've been sending.

> > Can I see a dump of the chip before the Linux driver is loaded?
>
> I'll grab it, but see the first paragraph I wrote.

I'm still interested.

Thanks,
-- 
Jean Delvare

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

  parent reply	other threads:[~2007-10-19 15:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16 10:08 [lm-sensors] [PATCH] On n2100 systems, Riku Voipio
2007-10-16 11:40 ` Lennert Buytenhek
2007-10-17 14:57 ` Jean Delvare
2007-10-17 15:19 ` Lennert Buytenhek
2007-10-17 21:42 ` Jean Delvare
2007-10-17 22:51 ` Lennert Buytenhek
2007-10-18  8:56 ` Riku Voipio
2007-10-19 15:36 ` Jean Delvare [this message]
2007-10-24 14:03 ` Riku Voipio
2007-10-25 11:45 ` Mark M. Hoffman
2007-10-25 11:59 ` 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=20071019173605.1cfcb233@hyperion.delvare \
    --to=khali@linux-fr.org \
    --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.