You can obtain this program from the KDE project's ftp server, ftp://ftp.kde.org/, or from the project homepage at http://homepages.mni.fh-giessen.de/~hg7229/khealthcare/index.html, which is always the appropriate source for the most current version, as well as binary distributions.
To successfully compile KHealthcare, you should have KDE 1.1.1 or later, as well as the Qt development package. KHealthcare is being developed under KDE 1.1.1 with Qt 1.44, so this is guaranteed to work. KHealthcare does not make use of any features too special, so earlier versions may work, too. However, this has not been tested, so try at your own risk.
This program isn't written for Qt 2.0 and / or KDE 2 yet. When KDE 2 is out, you may expect a port coming very quickly.
Since KHealthcare utilizes the lm_sensors library for monitoring the mainboard status, you must have the library installed and setup properly. You need at least version 2.4.2 As long as it's not yet an official part of the Linux kernel, you can get lm_sensors here. For special configuration issues, please refer to the 'lm_sensors interaction' section. To assure lm_sensors is working, you can use its own test applications. For details about installing and configuring lm_sensors, see the documentation of this library.
Note: You must have the config file for lm_sensors under /etc/sensors.conf. KHealthCare must run SUID root. It will work without these special permissions, but you won't be able to make any settings for alarm limits and sensors types etc. The reason for this has to be searched in the lm_sensors library.
This application relies on a hardware nonitoring chip built into your mainboard. It won't work without one. Version 0.1 of this program did only work with ISA chips. Later versions also work with chips communicating via the I2C bus ( or PIIX4 SMBus ).
Chips currently supported are:
National Semiconductors LM 75, 78, 78-J, 79, 80, 81
Winbond w83781d, w83782d, w83783s
Analog Devices adm9240
Dallas Semiconductor ds1780
Genesys Logic GL518SM, GL520SM
In order to compile and install KHealthcare on your system, type the following in the base directory of the KHealthcare distribution:
% ./configure
% make
% make install
Since KHealthcare uses
autoconfyou should have no trouble compiling it. Should you run into problems please report them to the the author: Ruediger Anlauf@gmx.net
As stated above, this program relies on lm_sensors for communication with your hardware. To get things straight, you should assure a few things.
1. You must provide a configuration file for lm_sensors, which includes your chip type
2. This file must be named sensors.conf and be located in /etc
3. lm_sensors has an internal name for each feature a chip provides. Those names can be the same for several supported chips, but do not necessarily have the same meaning. So you must help KHealthCare by setting the proper labels for each sensor feature in the above config file.
These labels must be *literally*:
"fan1", "fan2", "fan3" for the fan speeds
"temp1", "temp2", "temp3" for temperatures, or "temp" if there is only one temp sensor
"vid" for voltage ID, "VCore 1", "VCore 2" for CPU core voltages,
"+3.3V", "+5V", "-5V", "+12V", "-12V" for the remaining voltages.
and must be correlated with the proper sensor features as can be seen in the example config file lm_sensors installs. In fact, for the chips currently supported, this sample config file will probably work.
This procedure may seem clumsy and difficult to handle, but there is a good reason for this approach: KHealthCare supports chip types, and not mainboards. There is a large variety of mainboards on the market, and although there are certain recommendations from the chip manufacturers as for how to connect the inputs of the chip, the mainboard manufacturers do not necessarily take them to heart. So it is unwise to hardcode the names of the inputs into the program. In case you, the user, encounter something non standard, you must have some way to reconfigure the program.