lm-sensors

[L.T.]

Salve,
ho ubuntu e non riesco ad configurare bene lm-sensors.
Ho letto alcune guide su internet per configurare lm-sensors ma il risultato che
ottengo è questo:

root@lt-All-Series:~# sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +27.8°C (crit = +105.0°C)
temp2: +29.8°C (crit = +105.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +34.0°C (high = +80.0°C, crit = +100.0°C)
Core 0: +32.0°C (high = +80.0°C, crit = +100.0°C)
Core 1: +34.0°C (high = +80.0°C, crit = +100.0°C)
Core 2: +32.0°C (high = +80.0°C, crit = +100.0°C)
Core 3: +33.0°C (high = +80.0°C, crit = +100.0°C)

Cosa significa temp1 e temp2 e Physical id 0?
Io ho una scheda madre asus z97 pro e ho trovato che il chip che controlla la
temperatura e ventole è Nuvoton NCT6791D.
Devo configurare manualmente questo tipo di chip? Se è si come posso fare?
Grazie 100

[kernelex]

penso... 1 e 2 dovrebbero essere chip e mobo.
psical id il package della cpu.


sudo sensor-detect da terminale.

rispondi sempre si, poi enter, e poi ancora si.
dopo un reboot dovresti avere le temperature di tutto il bagarozzo e velocità delle ventole.

mauro@mauro-HTPC:~$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +46.0°C (high = +85.0°C, crit = +105.0°C)
Core 0: +45.0°C (high = +85.0°C, crit = +105.0°C)
Core 1: +46.0°C (high = +85.0°C, crit = +105.0°C)

nct6776-isa-0290
Adapter: ISA adapter
Vcore: +0.78 V (min = +0.00 V, max = +1.74 V)
in1: +0.18 V (min = +0.00 V, max = +0.00 V) ALARM
AVCC: +3.42 V (min = +2.98 V, max = +3.63 V)
+3.3V: +3.41 V (min = +2.98 V, max = +3.63 V)
in4: +0.56 V (min = +0.00 V, max = +0.00 V) ALARM
in5: +1.72 V (min = +0.00 V, max = +0.00 V) ALARM
in6: +1.80 V (min = +0.00 V, max = +0.00 V) ALARM
3VSB: +3.42 V (min = +2.98 V, max = +3.63 V)
Vbat: +3.31 V (min = +2.70 V, max = +3.63 V)
fan1: 752 RPM (min = 0 RPM)
fan2: 0 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
fan4: 0 RPM (min = 0 RPM)
fan5: 0 RPM (min = 0 RPM)
SYSTIN: +42.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = thermistor
CPUTIN: +54.5°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
AUXTIN: -22.5°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
PECI Agent 0: +46.0°C (high = +80.0°C, hyst = +75.0°C)
(crit = +105.0°C)
PCH_CHIP_TEMP: +0.0°C
PCH_CPU_TEMP: +0.0°C
PCH_MCH_TEMP: +0.0°C
intrusion0: OK
intrusion1: OK
beep_enable: disabled

[L.T.]

Originariamente inviato da kernelex

penso... 1 e 2 dovrebbero essere chip e mobo.
psical id il package della cpu.


sudo sensor-detect da terminale.

rispondi sempre si, poi enter, e poi ancora si.
dopo un reboot dovresti avere le temperature di tutto il bagarozzo e velocità delle ventole.

Grazie
Ho fatto questo:

lt@lt-All-Series:~$ sudo sensors-detect
# sensors-detect revision 6170 (2013-05-20 21:25:22 +0200)
# System: ASUS All Series
# Board: ASUSTeK COMPUTER INC. Z97-PRO

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
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
AMD Family 16h 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): YES
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
Found unknown chip with ID 0xc803
(logical device B has address 0x290, could be sensors)
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): 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
Found unknown SMBus adapter 8086:8ca2 at 0000:00:1f.3.
Sorry, no supported PCI bus adapters found.
Module i2c-dev loaded successfully.

Next adapter: i915 gmbus ssc (i2c-0)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus vga (i2c-1)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus panel (i2c-2)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus dpc (i2c-3)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus dpb (i2c-4)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus dpd (i2c-5)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: DPDDC-C (i2c-6)
Do you want to scan it? (YES/no/selectively): YES

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

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
#----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)yes
Successful!

Monitoring programs won't work until the needed modules are
loaded. You may want to run 'service kmod start'
to load them.

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

Poi ho riavviato e ho lanciato sensors e il risultato è questo:
lt@lt-All-Series:~$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +27.8°C (crit = +105.0°C)
temp2: +29.8°C (crit = +105.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +35.0°C (high = +80.0°C, crit = +100.0°C)
Core 0: +34.0°C (high = +80.0°C, crit = +100.0°C)
Core 1: +34.0°C (high = +80.0°C, crit = +100.0°C)
Core 2: +31.0°C (high = +80.0°C, crit = +100.0°C)
Core 3: +35.0°C (high = +80.0°C, crit = +100.0°C)

Non capisco perchè non ho lo stesso risultato di sensors come quello indicato da te!
ciao

[kernelex]

hai riavviato il pc?
se non vedi lo stesso risultato, o sime, la tua macchina non è pienamente supportata da lm-sensor.

nulla di grave eh.

[L.T.]

Originariamente inviato da kernelex

hai riavviato il pc?
se non vedi lo stesso risultato, o sime, la tua macchina non è pienamente supportata da lm-sensor.

nulla di grave eh.

Si ho riavviato ma esce fuori sempre lo stesso risultato!
Se la mia macchina non è pienamente supportata da lm-sensor, c'è un'altro programma
inerente a lm-sensor? Oppure bisognerebbe configurare tutto a mano?
grazie
ciao

[kernelex]

dopo lm-sensor il vuoto.
prova psensor e avvia la GUI.

la tua situazione mi capitò con kubuntu, e poi, con una fedora live vedevo tutto, ventole e temperature varie.

p.s.
se stai su ubuntu o derivate:

sudo add-apt-repository ppa:jfi/psensor-unstable
sudo apt-get update
sudo apt-get install psensor

[L.T.]

Originariamente inviato da kernelex

dopo lm-sensor il vuoto.
prova psensor e avvia la GUI.

la tua situazione mi capitò con kubuntu, e poi, con una fedora live vedevo tutto, ventole e temperature varie.

p.s.
se stai su ubuntu o derivate:

Installato, visualizza tutto come lm-sensor ma in più ci sono temperature dei disci
e CPU usage, free memory.
Ma poi su fedora c'è sempre lm-sensor?
Tu pensi che devo provare con un'altra distro?
Grazie
ciao