lm_sensors

[Yankee]

Ran sensors-detect today in terminal and it set up the
sensors and also found a new one.

When I run sensors command in the terminal...

Code: [Select]


[user@local ~]$ sensors
eeepc-isa-0000
Adapter: ISA adapter
fan1:        1034 RPM

acpitz-virtual-0
Adapter: Virtual device
temp1:        +55.0°C  (crit = +88.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +33.0°C  (crit = +90.0°C)


So, the fan1 sensor is obvious,  temp1 has always been the CPU,
so Core0 could be the GPU ?    What is a good way to positively
identify what the Core0 sensor is ?

THX

FF

[T6]

i had problems with lm sensors doing more weird things than that and i stopped looking at it

yes, core0 should be the first core on your cpu, at least is detecting mine that way but is not showing more sensors

to confirm, put some load on the cpu, to make it hot, compress something big like 4 or 5 gbs of images or mp3 and verify temperatures

[Yankee]

i had problems with lm sensors doing more weird things than that and i stopped looking at it

yes, core0 should be the first core on your cpu, at least is detecting mine that way but is not showing more sensors

to confirm, put some load on the cpu, to make it hot, compress something big like 4 or 5 gbs of images or mp3 and verify temperatures

Reading the lm_sensors page right now, and some others.    Apparently Core 0
is the CPU, but so is the acpitz sensor.    Reading what to do if the numbers are
way different between Core 0 and acpitz.   

thanks for the response,

later,

FF

[T6]

yes, i had in desktop similar problems, reporting 0 or the same value on multiple sensors or reporting sensors that doesn't exist with with impossible values, that i why i stopped using it

[JohnW_57]

Looks like sensors chipsets give you more or less information.

On my desktop:

[wim@localhost ~]$ sensors
atk0110-acpi-0
Adapter: ACPI interface
Vcore Voltage:       +1.14 V  (min =  +0.85 V, max =  +1.60 V)
 +3.3 Voltage:       +3.18 V  (min =  +2.97 V, max =  +3.63 V)
 +5 Voltage:         +4.97 V  (min =  +4.50 V, max =  +5.50 V)
 +12 Voltage:       +12.32 V  (min = +10.20 V, max = +13.80 V)
CPU FAN Speed:      2177 RPM  (min =  600 RPM, max = 7200 RPM)
CHASSIS1 FAN Speed: 1205 RPM  (min =  600 RPM, max = 7200 RPM)
CHASSIS2 FAN Speed: 1622 RPM  (min =  600 RPM, max = 7200 RPM)
POWER FAN Speed:       0 RPM  (min =  600 RPM, max = 7200 RPM)
CPU Temperature:     +43.0°C  (high = +60.0°C, crit = +95.0°C)
MB Temperature:      +47.0°C  (high = +45.0°C, crit = +95.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +54.0°C  (high = +82.0°C, crit = +100.0°C)
Core 1:       +51.0°C  (high = +82.0°C, crit = +100.0°C)
Core 2:       +46.0°C  (high = +82.0°C, crit = +100.0°C)
Core 3:       +47.0°C  (high = +82.0°C, crit = +100.0°C)


JohnW

[Yankee]

yes, i had in desktop similar problems, reporting 0 or the same value on multiple sensors or reporting sensors that doesn't exist with with impossible values, that i why i stopped using it

Well here's the choices fellas.

1) acpitz is under the CPU so it records the CPU socket base temp primarily,
Core 0 is actually the CPU core temp  (but a 20 degree difference ?   I guess so)

2) acpitz has bad code, it used to be OK, just be sure the critical temp is high
enough so acpi doesn't shut the computer off.

3) put thermal paste at the bottom of the CPU socket base and watch the temp
decrease.

4) turn off acpitz and just use coretemp's Core 0 temp for monitoring.


Some programs ran acpitz over 200 C, couldn't find how they resolved that.


regards,

FF