HOWTO:Gkrellm and lm sensors

From PardusWiki
(Difference between revisions)
Jump to: navigation, search
(→Which sensors are present?)
(Undo revision 3132 by Itycajofa (Talk) Spam.)
 
(16 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
{{UnderConstruction}}
 
−
 
 
== Introduction ==
 
== Introduction ==
 
Most modern motherboards are equiped with sensor(s) to measure (cpu)temperature, voltages and fanspeed.
 
Most modern motherboards are equiped with sensor(s) to measure (cpu)temperature, voltages and fanspeed.
Line 17: Line 15:
 
To detect which sensor is present we use the sensors-detect utility.
 
To detect which sensor is present we use the sensors-detect utility.
  
−
Open a terminal (konsole) and get administrator privileges with:
+
Open a terminal (konsole) and execute sensors-detect with administrator privileges with:
−
<pre>su</pre>
+
<pre>sudo sensors-detect</pre>
−
and start <pre>sensors-detect</pre>
+
 
We now get this output:
 
We now get this output:
 
<pre>
 
<pre>
−
....@....-pardus ~ $ su
+
....-pardus .... # sudo sensors-detect
−
Password:
+
Password:                          
−
....-pardus .... # sensors-detect
+
Useless use of private variable in void context at /usr/sbin/sensors-detect line 5425.
−
# sensors-detect revision 5249 (2008-05-11 22:56:25 +0200)
+
# sensors-detect revision 5729 (2009-06-02 15:51:29 +0200)                          
 +
# System: To Be Filled By O.E.M. 775Dual-VSTA                                       
  
 
This program will help you determine which kernel modules you need
 
This program will help you determine which kernel modules you need
−
to load to use lm_sensors most effectively. It is generally safe
+
to load to use lm_sensors most effectively. It is generally safe
−
and recommended to accept the default answers to all questions,
+
and recommended to accept the default answers to all questions,  
−
unless you know what you're doing.
+
unless you know what you're doing.                              
  
−
We can start with probing for (PCI) I2C or SMBus adapters.
+
Some south bridges, CPUs or memory controllers contain embedded sensors.
−
Do you want to probe now? (YES/no):
+
Do you want to scan for them? This is totally safe. (YES/no):
 
</pre>
 
</pre>
 
We get a number of these questions and answer them with [Enter] (=YES) until we reach the end with something like this:
 
We get a number of these questions and answer them with [Enter] (=YES) until we reach the end with something like this:
Line 39: Line 37:
 
.
 
.
 
.
 
.
−
Intel Core family thermal sensor...                         No
+
Next adapter: NVIDIA i2c adapter  (i2c-2)
−
Intel AMB FB-DIMM thermal sensor...                         No
+
Do you want to scan it? (YES/no/selectively):
 +
Client found at address 0x50
 +
Probing for `Analog Devices ADM1033'...                     No
 +
Probing for `Analog Devices ADM1034'...                     No
 +
Probing for `SPD EEPROM'...                                No
 +
Probing for `EDID EEPROM'...                                Yes
 +
    (confidence 8, not a hardware monitoring chip)
 +
 
 +
Next adapter: NVIDIA i2c adapter  (i2c-3)
 +
Do you want to scan it? (YES/no/selectively):
  
 
Now follows a summary of the probes I have just done.
 
Now follows a summary of the probes I have just done.
 
Just press ENTER to continue:
 
Just press ENTER to continue:
  
−
Driver `w83627hf' (should be inserted):
+
Driver `w83627hf':
−
  Detects correctly:
+
 
   * ISA bus, address 0x290
 
   * ISA bus, address 0x290
 
     Chip `Winbond W83697HF/F/HG Super IO Sensors' (confidence: 9)
 
     Chip `Winbond W83697HF/F/HG Super IO Sensors' (confidence: 9)
  
−
Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO):
+
Loading Modules
−
To load everything that is needed, add this to one of the system
+
  * w83627hf
−
initialization scripts (e.g. /etc/rc.d/rc.local):
+
Do you want to load these modules on startup (YES/no):
−
 
+
Unloading i2c-dev... OK
−
#----cut here----
+
−
# Chip drivers
+
−
modprobe w83627hf
+
−
/usr/bin/sensors -s
+
−
#----cut here----
+
−
 
+
−
If you have some drivers built into your kernel, the list above will
+
−
contain too many modules. Skip the appropriate ones! You really
+
−
should try these commands right now to make sure everything is
+
−
working properly. Monitoring programs won't work until the needed
+
−
modules are loaded.
+
  
 
....-pardus .... #
 
....-pardus .... #
 
</pre>
 
</pre>
  
−
This shows (IN THIS EXAMPLE) that chip `Winbond W83697HF' is present and that we need kernelmodule "w83627hf".
+
This shows (IN THIS EXAMPLE) that the chip `Winbond W83697HF' is present and that kernel module "w83627hf" is needed to read this sensor.
  
−
==Auto load of kernel module==
+
==Check auto-load of kernel module==
−
Add w83627hf (IN THIS EXAMPLE) to /etc/modules.autoload.d/kernel-2.6 with:
+
Check for the presents of the above found sensor (w83627hf in this example) in the file /etc/modules.autoload.d/kernel-2.6 with
−
  echo w83627hf>>/etc/modules.autoload.d/kernel-2.6
+
  more /etc/modules.autoload.d/kernel-2.6
−
Close the terminal and restart your computer to load kernel module and lm_sensors.
+
Result:
 +
<pre>
 +
....-pardus .... # more /etc/modules.autoload.d/kernel-2.6
 +
# /etc/modules.autoload.d/kernel-2.6:  kernel modules to load when system boots.
 +
#
 +
# Note that this file is for 2.6 kernels.
 +
#
 +
# Add the names of modules that you'd like to load when the system
 +
# starts into this file, one per line.  Comments begin with # and
 +
# are ignored.  Read man modules.autoload for additional details.
 +
 
 +
# For example:
 +
# 3c59x
 +
vboxdrv
 +
paviautopatch
 +
w83627hf
 +
....-pardus .... #
 +
</pre>
 +
Close the terminal and '''restart''' your computer to load kernel module and lm_sensors.
  
−
==Configuration of Gkrellm==
+
==Configuration of GKrellM==
 
Start Pardus -> Programs -> System -> GKrellM
 
Start Pardus -> Programs -> System -> GKrellM
  
−
You can configure your monitors by right clicking on the top frame or the various monitors of GKrellM or by hitting the F1 key with the mouse in the GKrellM window.
+
You can configure your monitors by right clicking on the top frame or on the various monitors of GKrellM or by hitting the F1 key with the mouse in the GKrellM window.
  
 
You can drag the GKrellM window to any position on your display.
 
You can drag the GKrellM window to any position on your display.
Line 85: Line 98:
 
In Builtins -> Sensors you can configure the display of your sensors.
 
In Builtins -> Sensors you can configure the display of your sensors.
  
−
(General configuration tip: General>Properties put a mark at 'Set sticky state' and 'Do not include on task bar')
+
(General configuration tip for GKrellM: General>Properties put a mark at 'Set sticky state' and 'Do not include on task bar')

Latest revision as of 14:07, 30 November 2010

Contents

Introduction

Most modern motherboards are equiped with sensor(s) to measure (cpu)temperature, voltages and fanspeed. When your motherboard has a sensor most of the time you can see the readout values in one of the setup screens of the bios (not always). This is a manual to make these values visible on the desktop of Pardus. On http://www.lm-sensors.org/ there is more information.

Installing required packages

Open Package Manager and install the following package: 

lm_sensors
gkrellm

Which sensors are present?

To detect which sensor is present we use the sensors-detect utility.

Open a terminal (konsole) and execute sensors-detect with administrator privileges with: 

sudo sensors-detect

We now get this output: 

....-pardus .... # sudo sensors-detect
Password:                           
Useless use of private variable in void context at /usr/sbin/sensors-detect line 5425.
# sensors-detect revision 5729 (2009-06-02 15:51:29 +0200)                            
# System: To Be Filled By O.E.M. 775Dual-VSTA                                         

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe  
and recommended to accept the default answers to all questions,   
unless you know what you're doing.                                

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):

We get a number of these questions and answer them with [Enter] (=YES) until we reach the end with something like this: 

.
.
Next adapter: NVIDIA i2c adapter  (i2c-2)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                Yes
    (confidence 8, not a hardware monitoring chip)

Next adapter: NVIDIA i2c adapter  (i2c-3)
Do you want to scan it? (YES/no/selectively):

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `w83627hf':
  * ISA bus, address 0x290
    Chip `Winbond W83697HF/F/HG Super IO Sensors' (confidence: 9)

Loading Modules
  * w83627hf
Do you want to load these modules on startup (YES/no):
Unloading i2c-dev... OK

....-pardus .... #

This shows (IN THIS EXAMPLE) that the chip `Winbond W83697HF' is present and that kernel module "w83627hf" is needed to read this sensor.

Check auto-load of kernel module

Check for the presents of the above found sensor (w83627hf in this example) in the file /etc/modules.autoload.d/kernel-2.6 with 

more /etc/modules.autoload.d/kernel-2.6

Result: 

....-pardus .... # more /etc/modules.autoload.d/kernel-2.6
# /etc/modules.autoload.d/kernel-2.6:  kernel modules to load when system boots.
#
# Note that this file is for 2.6 kernels.
#
# Add the names of modules that you'd like to load when the system
# starts into this file, one per line.  Comments begin with # and
# are ignored.  Read man modules.autoload for additional details.

# For example:
# 3c59x
vboxdrv
paviautopatch
w83627hf
....-pardus .... #

Close the terminal and restart your computer to load kernel module and lm_sensors.

Configuration of GKrellM

Start Pardus -> Programs -> System -> GKrellM

You can configure your monitors by right clicking on the top frame or on the various monitors of GKrellM or by hitting the F1 key with the mouse in the GKrellM window.

You can drag the GKrellM window to any position on your display.

In Builtins -> Sensors you can configure the display of your sensors.

(General configuration tip for GKrellM: General>Properties put a mark at 'Set sticky state' and 'Do not include on task bar')

Retrieved from "http://en.pardus-wiki.org/HOWTO:Gkrellm_and_lm_sensors"
Personal tools
Namespaces
Variants
Actions
Navigation
Print/export
Toolbox