Instalei recentemente lm-sensors
e executei o comando (conforme instruído aqui ):
sudo sensors-detect
Mas então eu li a página man
que dizia:
DESCRIPTION
sensors-detect is an interactive program that will walk you through the process of scanning your system for various hardware monitor‐
ing chips, or sensors, supported by libsensors(3), or more generally by the lm_sensors tool suite.
sensors-detect will look for the following devices, in order:
· Sensors embedded in CPUs, south bridges and memory controllers.
· Sensors embedded in Super I/O chips.
· Hardware monitoring chips accessed through ISA I/O ports.
· Hardware monitoring chips reachable over the SMBus or more generally any I2C bus on your system.
As the last two detection steps can cause trouble on some systems, they are normally not attempted if the second detection step led
to the discovery of a Super I/O chip with complete hardware monitoring features. However, the user is always free to ask for all
detection steps if so is his/her wish. This can be useful if a given system has more than one hardware monitoring chip. Some vendors
are known to do this, most notably Asus and Tyan.
E:
WARNING
sensors-detect needs to access the hardware for most of the chip detections. By definition, it doesn't know which chips are there
before it manages to identify them. This means that it can access chips in a way these chips do not like, causing problems ranging
from SMBus lockup to permanent hardware damage (a rare case, thankfully.)
The authors made their best to make the detection as safe as possible, and it turns out to work just fine in most cases, however it
is impossible to guarantee that sensors-detect will not lock or kill a specific system. So, as a rule of thumb, you should not run
sensors-detect on production servers, and you should not run sensors-detect if can't afford replacing a random part of your system.
Also, it is recommended to not force a detection step which would have been skipped by default, unless you know what you are doing.
Mas como eu realmente não tinha avisado quando estava executando a primeira última parte, eu corri, e o resultado foi:
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
Embora a segunda parte tenha sido devidamente avisada, eu não a executei. Mas o fato de que diz No
para o primeiro último, isso significa alguma coisa, ou há alguma maneira de dizer (além de esperar) se algum dano foi feito ao meu sistema? O programa teria indicado se algo de ruim tivesse acontecido? Ou há alguma maneira de verificar?
Eu tenho um Lenovo B590.
Informações do sistema operacional:
Description: Ubuntu 15.04
Release: 15.04