xsensors com temperatura errada

1. xsensors com temperatura errada

erich8
erich8

(usa Ubuntu)

Enviado em 24/01/2013 - 23:46h

Meu xsensors só mostra uma temperatura nada mais! E a temperatura sempre esta no 30.0C.
o que fazer?



  


2. Re: xsensors com temperatura errada

Alberto Federman Neto.
albfneto

(usa openSUSE)

Enviado em 25/01/2013 - 00:05h

Devem estar faltando pacotes relacionados aos sensores.
instale o pacote lm_sensors, e se quiser, pode tentar usar sensores gráficos,
como GKrellm, Conky, Cairo-Dock, AWN, widgets sensores de KDE, Screenlets, GDesklets etc...


3. Re: xsensors com temperatura errada

erich8
erich8

(usa Ubuntu)

Enviado em 25/01/2013 - 08:07h

instalei o GKrellm mas acho que ele só mostra a temperatura de um item e mesmo assim em "K" sei la o que é "K"!
estou na mesma!



4. Re: xsensors com temperatura errada

Alberto Federman Neto.
albfneto

(usa openSUSE)

Enviado em 25/01/2013 - 08:22h

além de estarem faltando pacotes, o GKrellm seu não está configurado, está em medida Inglêsa, graus Kelvin. Clique com o botão esquerdo do mouse. e configure o GKrellm, e se quiser procure pelos plugins dele, instalando todos os pacotes que começam com GK.
Completo, fica assim, como está na imagem a Direita da minha Tela:

http://imgur.com/MWpK8EG

Vc instalou o pacote lm_sensors?

Tente também os comandos abaixo:

$ sudo sensors-detect
$ sensors (usuário comum,sem sudo)

Se estiver completo, tem que ter uma saída como a dos meus:


albfneto@sabayon ~ $ sensors
atk0110-acpi-0
Adapter: ACPI interface
Vcore Voltage: +1.14 V (min = +0.85 V, max = +1.60 V)
+3.3 Voltage: +3.23 V (min = +2.97 V, max = +3.63 V)
+5 Voltage: +4.92 V (min = +4.50 V, max = +5.50 V)
+12 Voltage: +11.97 V (min = +10.20 V, max = +13.80 V)
CPU FAN Speed: 3139 RPM (min = 600 RPM, max = 7200 RPM)
CHASSIS FAN Speed: 0 RPM (min = 600 RPM, max = 7200 RPM)
CPU Temperature: +46.0°C (high = +60.0°C, crit = +95.0°C)
MB Temperature: +48.0°C (high = +45.0°C, crit = +75.0°C)
k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp: +46.0°C
Core1 Temp: +43.0°C

albfneto@sabayon ~ $ sudo sensor-detect
Senha:
sudo: sensor-detect: command not found
albfneto@sabayon ~ $ sudo sensors-detect
# sensors-detect revision 6085 (2012-10-30 18:18:45 +0100)
# Board: ASUSTeK Computer INC. M4A785-M

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):



Outra coisa que precisa ver é se os sensores são módulos ativados em seu Kernel:

# cat /proc/modules




5. Re: xsensors com temperatura errada

erich8
erich8

(usa Ubuntu)

Enviado em 25/01/2013 - 08:32h

erich@erich-MW-G31T-M7:~$ sudo sensors-detect
[sudo] password for erich:
# sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)
# System: MEGAWARE MW-G31T-M7

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): y
Module cpuid loaded successfully.
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
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 15h power sensors... No
Intel digital thermal sensor... Success!
(driver `coretemp')
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): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... Yes
Found `ITE IT8718F Super IO Sensors' Success!
(address 0xa10, driver `it87')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'... 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): y
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): y
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): y
Using driver `i2c-i801' for device 0000:00:1f.3: Intel 82801G ICH7
Module i2c-i801 loaded successfully.
Module i2c-dev loaded successfully.

Next adapter: i915 gmbus disabled (i2c-0)
Do you want to scan it? (YES/no/selectively): y

Next adapter: i915 gmbus ssc (i2c-1)
Do you want to scan it? (YES/no/selectively): y

Next adapter: i915 GPIOB (i2c-2)
Do you want to scan it? (YES/no/selectively): y

Next adapter: i915 gmbus vga (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: i915 GPIOA (i2c-4)
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: i915 gmbus panel (i2c-5)
Do you want to scan it? (YES/no/selectively): y

Next adapter: i915 GPIOC (i2c-6)
Do you want to scan it? (YES/no/selectively): y

Next adapter: i915 gmbus dpc (i2c-7)
Do you want to scan it? (YES/no/selectively): y

Next adapter: i915 GPIOD (i2c-8)
Do you want to scan it? (YES/no/selectively): y

Next adapter: i915 gmbus dpb (i2c-9)
Do you want to scan it? (YES/no/selectively): y

Next adapter: i915 GPIOE (i2c-10)
Do you want to scan it? (YES/no/selectively): y

Next adapter: i915 gmbus reserved (i2c-11)
Do you want to scan it? (YES/no/selectively): y

Next adapter: i915 gmbus dpd (i2c-12)
Do you want to scan it? (YES/no/selectively): y

Next adapter: i915 GPIOF (i2c-13)
Do you want to scan it? (YES/no/selectively): y

Next adapter: SMBus I801 adapter at 0400 (i2c-14)
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'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
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)

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

Driver `it87':
* ISA bus, address 0xa10
Chip `ITE IT8718F Super IO Sensors' (confidence: 9)

Driver `coretemp':
* Chip `Intel digital thermal sensor' (confidence: 9)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
it87
#----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 'service module-init-tools start'
to load them.

Unloading i2c-dev... OK
Unloading i2c-i801... OK
Unloading cpuid... OK

erich@erich-MW-G31T-M7:~$



6. Re: xsensors com temperatura errada

Alberto Federman Neto.
albfneto

(usa openSUSE)

Enviado em 25/01/2013 - 09:03h

veja, aparentemente você só tem um sensor de temperatura de Mobo, Intel.
ou vc não tem os sensores no hardware,ou está sem os módulos de kernel.

saidas dos outros comandos:

$ sensors
$ cat /proc/modules


7. Re: xsensors com temperatura errada

erich8
erich8

(usa Ubuntu)

Enviado em 25/01/2013 - 09:45h

erich@erich-MW-G31T-M7:~$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +30.0°C (crit = +110.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Core 0: +44.0°C (high = +76.0°C, crit = +100.0°C)
Core 1: +33.0°C (high = +76.0°C, crit = +100.0°C)

it8718-isa-0a10
Adapter: ISA adapter
in0: +1.06 V (min = +0.00 V, max = +4.08 V)
in1: +2.11 V (min = +0.00 V, max = +4.08 V)
in2: +1.84 V (min = +0.00 V, max = +4.08 V)
+5V: +2.94 V (min = +0.00 V, max = +4.08 V)
in4: +2.11 V (min = +0.00 V, max = +4.08 V)
in5: +0.05 V (min = +0.00 V, max = +4.08 V)
in6: +0.08 V (min = +0.00 V, max = +4.08 V)
5VSB: +2.98 V (min = +0.00 V, max = +4.08 V)
Vbat: +3.31 V
fan1: 0 RPM (min = 0 RPM)
fan2: 859 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
temp1: -128.0°C (low = -1.0°C, high = +127.0°C) sensor = disabled
temp2: -128.0°C (low = -1.0°C, high = +127.0°C) sensor = disabled
temp3: -56.0°C (low = +127.0°C, high = +80.0°C) sensor = thermal diode
cpu0_vid: +1.600 V
intrusion0: OK

erich@erich-MW-G31T-M7:~$


legal! o xsensors ja este encontrando mais coisas.

notou que tem 3 temps com -C?
temp1: -128.0°C
temp2: -128.0°C
temp3: -56.0°C

estranho! no Windows tbm tem!



8. Re: xsensors com temperatura errada

Alberto Federman Neto.
albfneto

(usa openSUSE)

Enviado em 25/01/2013 - 10:00h

Notou também, sensor disabled. Checou as configs do ACPI e do barramento ISA na BIOS?


9. Re: xsensors com temperatura errada

erich8
erich8

(usa Ubuntu)

Enviado em 25/01/2013 - 11:11h

então é só entrar na Bios e ativar ACPI e ISA?

O ACPI tem as opções S1, S3 e auto. esta no S1.







Patrocínio

Site hospedado pelo provedor RedeHost.
Linux banner

Destaques

Artigos

Dicas

Tópicos

Top 10 do mês

Scripts