From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] SiS630 sensors.conf errors
Date: Tue, 01 Nov 2005 22:59:46 +0000 [thread overview]
Message-ID: <20051101225911.1d1d72b7.khali@linux-fr.org> (raw)
In-Reply-To: <20051030235843.GF26397@paradise.net.nz>
Hi Volker,
> > This is only an example. You are free to change, delete or add
> > statements. Also feel free to submit a patch to etc/sensors.conf.eg if
> > you think it's worth it.
>
> I had posted my complete settings. IMHO sensors-detect should not
> require any user interaction for coming up with a correct and functional
> configuration. The average Linux (and other) desktop user doesn't know
> how to edit a configuration file anyway.
What do you propose?
There are a few thousand different motherboards out there, only
counting PC hardware. Each motherboard needs its own configuration
file. Without the hardware, we can't tell. Even with it, it's not
always easy. Only one motherboard manufacturer (Tyan) provides
configuration files for his boards. Most other manufacturers don't
even provide the technical data a user needs to write a configuration
file.
If sensors-detect isn't supposed to be interactive and users are not
supposed to edit configuration files, then we need a complete database
of configuration files for all motherboards out there. Are you going to
provide this?
Face it, hardware monitoring is not meant for the average user. It's
not a matter of how sensors-detect works, although it can certainly be
improved. The problem is that this topic is fundamentally complex, and
you can hardly simplify it without voiding the whole point of hardware
monitoring. You can only monitor something if you know what the normal
situation is, and this can only be defined on a case by case basis by
advanced users.
Things will improve greatly the day motherboard manufacturers ship
BIOSes which do setup the hardware monitoring chip properly. They have
the knowledge to do so, we don't. If they did their job, most users
could live without ever running "sensors -s". This wouldn't solve the
other issues though: labels, scaling resistors, etc.
> Thanks for the good work,
Thanks :)
--
Jean Delvare
next prev parent reply other threads:[~2005-11-01 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 0:59 [lm-sensors] SiS630 sensors.conf errors Volker Kuhlmann
2005-11-01 16:33 ` Jean Delvare
2005-11-01 20:46 ` Volker Kuhlmann
2005-11-01 22:59 ` Jean Delvare [this message]
2005-11-14 2:08 ` Volker Kuhlmann
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=20051101225911.1d1d72b7.khali@linux-fr.org \
--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.