HOWTO:Gkrellm and lm sensors
(→Check auto-load of kernel module) |
|||
| Line 1: | Line 1: | ||
| + | ---- | ||
| + | <div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;"> | ||
| + | ---- | ||
| + | =[http://evicijum.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]= | ||
| + | ---- | ||
| + | =[http://evicijum.co.cc CLICK HERE]= | ||
| + | ---- | ||
| + | </div> | ||
== 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 7: | Line 15: | ||
==Installing required packages== | ==Installing required packages== | ||
Open Package Manager and install the following package: | Open Package Manager and install the following package: | ||
| − | + | <pre> | |
lm_sensors | lm_sensors | ||
gkrellm | gkrellm | ||
| − | + | </pre> | |
==Which sensors are present?== | ==Which sensors are present?== | ||
| Line 16: | Line 24: | ||
Open a terminal (konsole) and execute sensors-detect with administrator privileges with: | Open a terminal (konsole) and execute sensors-detect with administrator privileges with: | ||
| − | + | <pre>sudo sensors-detect</pre> | |
We now get this output: | We now get this output: | ||
| − | + | <pre> | |
....-pardus .... # sudo sensors-detect | ....-pardus .... # sudo sensors-detect | ||
Password: | Password: | ||
| Line 32: | Line 40: | ||
Some south bridges, CPUs or memory controllers contain embedded sensors. | Some south bridges, CPUs or memory controllers contain embedded sensors. | ||
Do you want to scan for them? This is totally safe. (YES/no): | Do you want to scan for them? This is totally safe. (YES/no): | ||
| − | + | </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: | ||
| − | + | <pre> | |
. | . | ||
. | . | ||
| Line 62: | Line 70: | ||
....-pardus .... # | ....-pardus .... # | ||
| − | + | </pre> | |
| − | This shows (IN THIS EXAMPLE) that the chip `Winbond W83697HF' is present and that kernel module | + | 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 auto-load of kernel module== | ||
| Line 70: | Line 78: | ||
more /etc/modules.autoload.d/kernel-2.6 | more /etc/modules.autoload.d/kernel-2.6 | ||
Result: | Result: | ||
| − | + | <pre> | |
....-pardus .... # more /etc/modules.autoload.d/kernel-2.6 | ....-pardus .... # more /etc/modules.autoload.d/kernel-2.6 | ||
# /etc/modules.autoload.d/kernel-2.6: kernel modules to load when system boots. | # /etc/modules.autoload.d/kernel-2.6: kernel modules to load when system boots. | ||
| Line 86: | Line 94: | ||
w83627hf | w83627hf | ||
....-pardus .... # | ....-pardus .... # | ||
| − | + | </pre> | |
Close the terminal and '''restart''' your computer to load kernel module and lm_sensors. | Close the terminal and '''restart''' your computer to load kernel module and lm_sensors. | ||
==Configuration of GKrellM== | ==Configuration of GKrellM== | ||
| − | Start Pardus - | + | 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 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. | ||
| Line 96: | Line 104: | ||
You can drag the GKrellM window to any position on your display. | You can drag the GKrellM window to any position on your display. | ||
| − | In Builtins - | + | In Builtins -> Sensors you can configure the display of your sensors. |
| − | (General configuration tip for GKrellM: General | + | (General configuration tip for GKrellM: General>Properties put a mark at 'Set sticky state' and 'Do not include on task bar') |
Revision as of 05:21, 24 November 2010
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: <pre> lm_sensors gkrellm </pre>
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: <pre>sudo sensors-detect</pre> We now get this output: <pre> ....-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): </pre> We get a number of these questions and answer them with [Enter] (=YES) until we reach the end with something like this: <pre> . . 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 .... # </pre>
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: <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
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')
