Causa il passaggio a Lucid-Lynx con conseguente rimessa di alcuni pacchetti riporto per motivi di memo qui la procedura di installazione di alcuni software che sfruttano l'
ACPI(Advanced Configuration and Power Interface)
- 1. lm sensors (un software di monitoraggio di salute dell' hardware del PC)
- 2. hddtemp(un software di monitoraggio di temperatura dei HD che prende i suoi dati da
S.M.A.R.T
)
- 3. sensors-applet un visore dei dati dei software precendenti(non è necessario in quanto si può usare la linea di comando ma è comodo) che si mette nel panel GNOME
sudo apt-get install lm-sensors hddtemp sensors-applet
nel qualcaso appare una dialog box che chiede se far partire
hddtemp come servizio rispondiamo con si(spuntando una casellina) e andiamo avanti fino alla sparizione della dialog box.Nel qualcaso ci confondiamo in questo passaggio e non spuntiamo il si non preoccupatevi si può fare pure a posteriori dando:
sudo dpks --reconfigure hddtemp
Lm_sensors - Linux hardware monitoring
Dapprima dobbiamo impostare
lm sensors dando:
. Dovremmo rispondere a delle domande(se non si sa di cosa si tratta rispondiamo Y a tutte) ottenendo un output simile(probabilmente non uguale perché dipende dall' hardware posseduto da ognuno di noi) a questo:
harrykar@harrysas:~$ sudo sensors-detect
[sudo] password for harrykar:
# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# System: EVGA 132-CK-NF78
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): YES
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
Intel Core family thermal sensor... Success!
(driver `coretemp')
Intel Atom thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): YES
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
Found `Winbond W83627DHG Super IO Sensors' Success!
(address 0x290, driver `w83627ehf')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): YES
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): yes
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): YES
Using driver `i2c-nforce2' for device 0000:00:0a.1: nVidia Corporation nForce SMBus (MCP55)
Module i2c-dev loaded successfully.
Next adapter: SMBus nForce2 adapter at f400 (i2c-0)
Do you want to scan it? (yes/NO/selectively): y
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Client found at address 0x53
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Next adapter: SMBus nForce2 adapter at f000 (i2c-1)
Do you want to scan it? (yes/NO/selectively): y
Client found at address 0x28
Probing for `National Semiconductor LM78'... No
Probing for `National Semiconductor LM79'... No
Probing for `National Semiconductor LM80'... No
Probing for `Winbond W83781D'... No
Probing for `Winbond W83782D'... No
Probing for `Winbond W83627HF'... No
Probing for `Winbond W83627EHF'... No
Probing for `Winbond W83627DHG/W83667HG/W83677HG'... Success!
(confidence 7, driver `use-isa-instead')
Probing for `Asus AS99127F (rev.1)'... No
Probing for `Asus AS99127F (rev.2)'... No
Probing for `Asus ASB100 Bach'... No
Probing for `Analog Devices ADM1029'... No
Probing for `ITE IT8712F'... No
Client found at address 0x49
Probing for `National Semiconductor LM75'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `National Semiconductor LM77'... No
Probing for `Dallas Semiconductor DS1621/DS1631'... No
Probing for `National Semiconductor LM73'... No
Probing for `National Semiconductor LM92'... No
Probing for `National Semiconductor LM76'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Next adapter: NVIDIA i2c adapter (i2c-2)
Do you want to scan it? (YES/no/selectively): y
Next adapter: NVIDIA i2c adapter (i2c-3)
Do you want to scan it? (YES/no/selectively): y
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)
Client found at address 0x51
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Client found at address 0x53
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Next adapter: NVIDIA i2c adapter (i2c-4)
Do you want to scan it? (YES/no/selectively): y
Now follows a summary of the probes I have just done.
Just press ENTER to continue: <ENTER>
Driver `w83627ehf':
* ISA bus, address 0x290
Chip `Winbond W83627DHG Super IO Sensors' (confidence: 9)
Driver `coretemp':
* Chip `Intel Core family thermal sensor' (confidence: 9)
To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
w83627ehf
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!
Do you want to add these lines automatically to /etc/modules? (yes/NO)y
Successful!
Monitoring programs won't work until the needed modules are
loaded. You may want to run '/etc/init.d/module-init-tools start'
to load them.
Unloading i2c-dev... OK
harrykar@harrysas:~$
poi diamo
sudo /etc/init.d/module-init-tools
e forse otterremmo qualche lamento(Ubuntu è la|(una delle) distro con le modifiche più sostanziose rispetto alla tradizione) ma vabbene lo stesso.
Per verificare la buona riuscita diamo il comando
dovremmo ottenere un output simile a:
harrykar@harrysas:~$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +54.0°C (high = +78.0°C, crit = +100.0°C)
coretemp-isa-0001
Adapter: ISA adapter
Core 1: +53.0°C (high = +78.0°C, crit = +100.0°C)
w83627dhg-isa-0290
Adapter: ISA adapter
Vcore: +1.19 V (min = +0.00 V, max = +1.74 V)
in1: +1.49 V (min = +0.10 V, max = +1.79 V)
AVCC: +3.26 V (min = +2.98 V, max = +3.63 V)
VCC: +3.25 V (min = +2.98 V, max = +3.63 V)
in4: +1.09 V (min = +1.42 V, max = +0.55 V) ALARM
in5: +1.58 V (min = +0.19 V, max = +1.31 V) ALARM
in6: +1.82 V (min = +0.02 V, max = +0.61 V) ALARM
3VSB: +3.26 V (min = +2.98 V, max = +3.63 V)
Vbat: +3.07 V (min = +2.70 V, max = +3.30 V)
fan1: 2884 RPM (min = 61363 RPM, div = 2) ALARM
fan2: 1739 RPM (min = 5273 RPM, div = 8) ALARM
fan3: 0 RPM (min = 10546 RPM, div = 128) ALARM
fan4: 0 RPM (min = 10546 RPM, div = 128) ALARM
fan5: 0 RPM (min = 10546 RPM, div = 128) ALARM
temp1: -65.0°C (high = +0.0°C, hyst = +127.0°C) sensor = diode
temp2: +52.0°C (high = +127.0°C, hyst = +0.0°C) ALARM sensor = diode
temp3: +32.0°C (high = +127.0°C, hyst = +0.0°C) sensor = thermistor
cpu0_vid: +2.500 V
i
coretemp si riferiscono ai sensori sulle CPU(nel mio caso sono 2 essendo un dual core per un quad core sarrebero ovviamente 4)
i parametri(non tutti hanno valori corretti. A proposito converrebbe entrare prima nella sezione del BIOS a boot time ove vengono riportate le misure dei sensori e prenderne nota per poi cambiare i nomi generici in1, fan1 ecc in
lm sensors) sotto
w83627dhg-isa-0290 invece si riferiscono ai sensori che stanno nella motherboard
harrykar@harrysas:~$ sudo hddtemp /dev/sda
[sudo] password for harrykar:
/dev/sda: WDC WD5000AAKS-22TMA0: 35°C
sensors-applet
per non riempire il panel con dati dei sensori conviene mettere nel panel un drawer e mettere l' applet(Hardware Sensors Monitor) dentro il drawer(guarda shot).
1. Clik destro sul panel p.e. superiore Add to panel > scegliere drawer
2. Clik destro sul drawer Add to drawer > scegliere Hardware Sensors Monitor
Il numero di parametri da visualizzare si può configurare con:
clik destro dentro il drawer > preferences > sensors (allarghiamo la window per scorgere la colonna enabled) e spuntiamo sui parametri che vogliamo siano visibili in sensors-applet. I nomi delle voci possono essere pure personalizzati sulla colonna
labels cliccando e sostiturndo p. e. fan1 > digitare CPUfan ecc.
PS: E' ben precisare che oltre all' installazione tramite il sistema di pachettizzazione debian's-like apt-get, aptitude(meglio perchè a differenza di apt-get al momento di disinstallazione disinstalla pure tutte le dipendenze) la procedura su riportata vale per tutte le flavor *nix-like
Riferimenti:
Lm_sensors - Linux hardware monitoring
lucidtips