[lm-sensors] SiS630 sensors.conf errors

[lm-sensors] SiS630 sensors.conf errors

[Volker Kuhlmann]

Minor bugs, but can be confusing:

  # The following is for the Inside Technologies 786LCD which uses either a
  # IT8705F or a SIS950 for monitoring with the SIS630.
  # You will need to load the it87 module as follows to select the correct
  # temperature sensor type.
  # modprobe it87 temp_type=0x31

Module it87 doesn't have a temp_type option.

The settings for low and high temperature values are missing for all
temperatures.

Volker

-- 
Volker Kuhlmann			is possibly list0570 with the domain in header
http://volker.dnsalias.net/		Please do not CC list postings to me.

[lm-sensors] SiS630 sensors.conf errors

[Jean Delvare]

Hi Volker,

> Minor bugs, but can be confusing:
> 
>   # The following is for the Inside Technologies 786LCD which uses either a
>   # IT8705F or a SIS950 for monitoring with the SIS630.
>   # You will need to load the it87 module as follows to select the correct
>   # temperature sensor type.
>   # modprobe it87 temp_type=0x31
> 
> Module it87 doesn't have a temp_type option.

It used to, but has no more. Thanks for reporting. I've dropped that
part, as well as the comment about the misdetection in the paragraph
right after, as I believe this is no more true.

> The settings for low and high temperature values are missing for all
> temperatures.

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.

Thanks,
-- 
Jean Delvare

[lm-sensors] SiS630 sensors.conf errors

[Volker Kuhlmann]

Thanks Jean.

> 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.

Thanks for the good work,

Volker

-- 
Volker Kuhlmann			is possibly list0570 with the domain in header
http://volker.dnsalias.net/		Please do not CC list postings to me.

[lm-sensors] SiS630 sensors.conf errors

[Jean Delvare]

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

[lm-sensors] SiS630 sensors.conf errors

[Volker Kuhlmann]

On Wed 02 Nov 2005 10:59:11 NZDT +1300, Jean Delvare wrote:

Hi Jean,

Thanks for your reply.

> > 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.

> 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?

I was unclear. What I meant was that running sensors-detect should
always find a functional configuration, or it's not much use for the
desktop user. Of course it's not going to happen any time soon,
unfortunately. In view of the lack of support from the board makers I
don't see how this goal can be achieved without a collection of
information on the various board models. Collecting functional
configuration files for boards would not be too difficult, and
sensors-detect should be capable of picking the correct one, if
available. This prevents duplication of effort, and really helps the
majority of users who don't have the education to be able to construct
their own. Ship the board config files with the software, and have a
"get the latest from". It's not so different from scanModem, and lspci
and lsusb work the same way.

> Face it, hardware monitoring is not meant for the average user.

Sure, I can see it is not for the average user. But it should be, and
regardless of whether it is like that under you-know-OS.

> Things will improve greatly the day motherboard manufacturers ship
> BIOSes which do setup the hardware monitoring chip properly.

Oh yes. Blast them.

Volker

-- 
Volker Kuhlmann			is possibly list0570 with the domain in header
http://volker.dnsalias.net/		Please do not CC list postings to me.