lm-sensors and Intel processor

[Scythe]

Good day,

 

I've got, according to my hmonitor (a Windows XP software) diagnostics information the following:

 

M/B Chipset: Intel 820

Main Snesor: THMC50

ISA Port Used: 290

SMB Port Used: FC00

 

Would thiis hardware be compatible with lm-sensors? If so, how would I go about installing lm-sensors, because doing $ urpmi lm-sensors doesn't return any results.

 

I saw in another thread a link to http://secure.netroedge.com/~lm78/ that said to install lm-sensors via urpmi, but I have no idea how to have urpmi use that link.

[ianw1974]

You would need to type:

 

urpmi lm_sensors

 

as it's underscore rather than hyphen. Then issue:

 

service lm_sensors start

 

to start the service. However, it should prompt you after installation to run the config utility, so do this first, and then start the service.

[Scythe]

 More information on package lm_sensors-2.9.1-4mdk.i586
* To use this package, you'll have to launch "sensors-detect" as root, and ask few questions.
 No need to modify startup files as shown at the end, all will be done.

* Special note for via686a and i2c-viapro : if you don t see the values, you probably have a PCI conflict.
 It will be corrected in next kernel. Change the /etc/sysconfig/lm_sensors to use i2c-isa + via686a
 (or i2c-viapro + another sensor)
----------------------------------------------------------------------
[root@localhost scythe]# sensors-detect

This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.

It is generally safe and recommended to accept the default answers to all
questions, unless you know what you're doing.

We can start with probing for (PCI) I2C or SMBus adapters.
You do not need any special privileges for this.
Do you want to probe now? (YES/no): yes
Probing for PCI bus adapters...
Use driver `rivatv' for device 01:00.0: GeForce2 MX
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Load `rivatv' (say NO if built into your kernel)? (YES/no): yes
Module loaded succesfully.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

To continue, we need module `i2c-dev' to be loaded.
If it is built-in into your kernel, you can safely skip this.
i2c-dev is not loaded. Do you want to load it now? (YES/no): yes
Module loaded succesfully.

We are now going to do the adapter probings. Some adapters may hang halfway
through; we can't really help that. Also, some chips will be double detected;
we choose the one with the highest confidence value in that case.
If you found that the adapter hung after probing a certain address, you can
specify that address to remain unprobed. That often
includes address 0x69 (clock chip).

Next adapter: NVIDIA display adapter bus 0
Do you want to scan it? (YES/no/selectively): yes
Segmentation fault
[root@localhost scythe]# sensors-detect

This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.

It is generally safe and recommended to accept the default answers to all
questions, unless you know what you're doing.

We can start with probing for (PCI) I2C or SMBus adapters.
You do not need any special privileges for this.
Do you want to probe now? (YES/no): yes
Probing for PCI bus adapters...
Use driver `rivatv' for device 01:00.0: GeForce2 MX
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Module `rivatv' already loaded.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

To continue, we need module `i2c-dev' to be loaded.
If it is built-in into your kernel, you can safely skip this.
i2c-dev is already loaded.

We are now going to do the adapter probings. Some adapters may hang halfway
through; we can't really help that. Also, some chips will be double detected;
we choose the one with the highest confidence value in that case.
If you found that the adapter hung after probing a certain address, you can
specify that address to remain unprobed. That often
includes address 0x69 (clock chip).

Next adapter: NVIDIA display adapter bus 0
Do you want to scan it? (YES/no/selectively): no

Next adapter: NVIDIA display adapter bus 1
Do you want to scan it? (YES/no/selectively): no

Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan the ISA bus? (YES/no): yes
Probing for `National Semiconductor LM78'
 Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
 Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
 Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
 Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
 Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
 Trying address 0x0290... Failed!
Probing for `Winbond W83627EHF'
 Trying address 0x0290... Failed!
Probing for `Winbond W83697HF'
 Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
 Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
 Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
 Trying general detect... Failed!
Probing for `ITE IT8712F'
 Trying address 0x0290... Failed!
Probing for `ITE IT8705F / SiS 950'
 Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
 Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
 Trying address 0x0ca8... Failed!

Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan for Super I/O sensors? (YES/no): yes
Probing for `ITE 8702F Super IO Sensors'
 Failed! (0x5604)
Probing for `ITE 8705F Super IO Sensors'
 Failed! (0x5604)
Probing for `ITE 8712F Super IO Sensors'
 Failed! (0x5604)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
 Failed! (0x56)
Probing for `Nat. Semi. PC87360 Super IO Fan Sensors'
 Failed! (0x56)
Probing for `Nat. Semi. PC87363 Super IO Fan Sensors'
 Failed! (0x56)
Probing for `Nat. Semi. PC87364 Super IO Fan Sensors'
 Failed! (0x56)
Probing for `Nat. Semi. PC87365 Super IO Fan Sensors'
 Failed! (0x56)
Probing for `Nat. Semi. PC87365 Super IO Voltage Sensors'
 Failed! (0x56)
Probing for `Nat. Semi. PC87365 Super IO Thermal Sensors'
 Failed! (0x56)
Probing for `Nat. Semi. PC87366 Super IO Fan Sensors'
 Failed! (0x56)
Probing for `Nat. Semi. PC87366 Super IO Voltage Sensors'
 Failed! (0x56)
Probing for `Nat. Semi. PC87366 Super IO Thermal Sensors'
 Failed! (0x56)
Probing for `Nat. Semi. PC87372 Super IO Fan Sensors'
 Failed! (0x56)
Probing for `Nat. Semi. PC87373 Super IO Fan Sensors'
 Failed! (0x56)
Probing for `Nat. Semi. PC87591 Super IO'
 Failed! (0x56)
Probing for `Nat. Semi. PC87371 Super IO'
 Failed! (0x56)
Probing for `Nat. Semi. PC97371 Super IO'
 Failed! (0x56)
Probing for `Nat. Semi. PC8739x Super IO'
 Failed! (0x56)
Probing for `Nat. Semi. PC8741x Super IO'
 Failed! (0x56)
Probing for `SMSC 47B27x Super IO Fan Sensors'
 Failed! (0x56)
Probing for `SMSC 47M10x/13x Super IO Fan Sensors'
 Failed! (0x56)
Probing for `SMSC 47M14x Super IO Fan Sensors'
 Failed! (0x56)
Probing for `SMSC 47M15x/192 Super IO Fan Sensors'
 Failed! (0x56)
Probing for `SMSC 47S42x Super IO Fan Sensors'
 Failed! (0x56)
Probing for `SMSC 47S45x Super IO Fan Sensors'
 Failed! (0x56)
Probing for `SMSC 47M172 Super IO'
 Failed! (0x56)
Probing for `SMSC LPC47B397-NC Super IO'
 Failed! (0x56)
Probing for `VT1211 Super IO Sensors'
 Failed! (skipping family)
Probing for `Winbond W83627EHF Super IO Sensors'
 Failed! (skipping family)

Do you want to scan for secondary Super I/O sensors? (YES/no): yes
Probing for `ITE 8702F Super IO Sensors'
 Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
 Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
 Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
 Failed! (skipping family)
Probing for `Winbond W83627EHF Super IO Sensors'
 Failed! (skipping family)

Sorry, no chips were detected.
Either your sensors are not supported, or they are
connected to an I2C bus adapter that we do not support.
See doc/FAQ, doc/lm_sensors-FAQ.html, or
http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/doc/lm_sensors-FAQ.html
(FAQ #4.24.3) for further information.
If you find out what chips are on your board, see
http://secure.netroedge.com/~lm78/newdrivers.html for driver status.

This is what I get after running

$ sensors-detect like the prompt specified.

[ianw1974]

At the beginning it finds devices, and then later on doesn't find anything. You can start the service, and then see if you can get some sort of functionality from it.

 

If not, then it seems your machine isn't supported for the lm_sensors.

[Scythe]

Ok, what kind of monitoring program should I use with lm-sensors now?

 

Or does it come wiht its own built-in monitoring gui?

[daniewicz]

I do not have any monitoring software insalled on my system, but I have seen others here at MUB discuss ksensors.

[AussieJohn]

You are correct daniel.

If you are using KDE then you can install Ksensors and it makes it very easy to set up desired displays on the Panel/kicker System Tray. I use it to show the CPU temperature and the Mainboard temp. in the System Tray.

I am certain there is an equivalent in Gnome for Gnome users.

 

Cheers. John.

 

Another point. Even though ksensors has an option for it to start automatically after reboot, for some reason it does not reliably do so.

Go to /usr/bin and look for ksensors and right click and select copy.

Go to /home/<your account>/.kde/Autostart and right click and paste ( to get to /.kde you will need to select View in Konqueror select Show Hidden Files.

 

JB

Edited February 24, 2006 by AussieJohn

[ianw1974]

There's also gkrellm which is Gnome based, and superkaramba for kde which has loads of features and quite nice. Both can be skinned too.

[jethro]

Another good one is: torsmo.

[iphitus]

Torsmo is unmaintained and has since been replaced by a substantially improved variant, conky.

 

John: Copying ksensors is not the best solution, as the copied file will not be updated when ksensors is. There's probably a 'link' or symlink option in KDE, which would be much more appropriate.

 

iphitus