[lm-sensors] testing "w83627ehf" and "k10temp" on ASRock E350M1

[lm-sensors] testing "w83627ehf" and "k10temp" on ASRock E350M1

[Aleksej Serdjukov]

Hi.

I've got this computer with ASRock E350M1, and have no idea what the 
temperatures should actually be.

This is on Debian 6.0:
Linux 2.6.32-5-amd64 #1 SMP Mon Mar 7 21:35:22 UTC 2011 x86_64 GNU/Linux


IIRC, UEFI Setup was showing about 52°C on the motherboard or chipset, 
and 49-52 on the CPU.

About a week ago I've installed the "w83627ehf" from 
<http://roeck-us.net/linux/drivers/w83627ehf/>, and saw that those 
temperatures don't go over 53 or 54°C. So I changed the UEFI setting 
more and more for slower fan speed (today it was 6). So the speed was 
about 4000, while the full speed is about 4900 and 9 is a hundred or a 
couple of hundred less. Temperatures didn't go over 54 (or maybe 55) °C. 
Idle CPU (at 800MHz thanks to Cool'n'Quiet) went down to 46°C more and more.

Today, however, while the CPU was not loaded much, the fan appeared to 
be full speed again (at least according to the sensors applet).

But the new sensors-detect was also mentioning "k10temp" (and the old 
one in Debian didn't work), so today I installed a new k10temp, and it 
showed 60°C for something.

Now I have set the fan speed to full in UEFI, and here is what "sensors" 
shows:


nct6775-isa-0290
Adapter: ISA adapter
Vcore:       +1.08 V  (min =  +0.00 V, max =  +1.74 V)
in1:         +1.03 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
AVCC:        +3.33 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:       +3.33 V  (min =  +2.98 V, max =  +3.63 V)
in4:         +1.39 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in5:         +1.86 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in6:         +1.66 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
3VSB:        +3.44 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:        +3.39 V  (min =  +2.70 V, max =  +3.30 V)   ALARM
fan1:          0 RPM  (min =    0 RPM, div = 128)
fan2:       4963 RPM  (min =    0 RPM, div = 8)  ALARM
fan3:          0 RPM  (min =    0 RPM, div = 128)
fan4:          0 RPM  (div = 128)
SYSTIN:      +51.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = 
thermistor
CPUTIN:      +45.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
AUXTIN:       -9.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
cpu0_vid:   +0.000 V

k10temp-pci-00c3
Adapter: PCI adapter
temp1:       +58.0°C  (high = +70.0°C, crit = +75.0°C)

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] testing "w83627ehf" and "k10temp" on ASRock E350M1

[Aleksej Serdjukov]

On 2011-04-06 21:38, Aleksej Serdjukov wrote:
> Now I have set the fan speed to full in UEFI, and here is what "sensors"
> shows:

(sensors version 3.2.0 with libsensors version 3.2.0)

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] testing "w83627ehf" and "k10temp" on ASRock E350M1

[Guenter Roeck]

On Wed, Apr 06, 2011 at 01:38:56PM -0400, Aleksej Serdjukov wrote:
> Hi.
> 
> I've got this computer with ASRock E350M1, and have no idea what the 
> temperatures should actually be.
> 
> This is on Debian 6.0:
> Linux 2.6.32-5-amd64 #1 SMP Mon Mar 7 21:35:22 UTC 2011 x86_64 GNU/Linux
> 
> 
> IIRC, UEFI Setup was showing about 52°C on the motherboard or chipset, 
> and 49-52 on the CPU.
> 
> About a week ago I've installed the "w83627ehf" from 
> <http://roeck-us.net/linux/drivers/w83627ehf/>, and saw that those 
> temperatures don't go over 53 or 54°C. So I changed the UEFI setting 
> more and more for slower fan speed (today it was 6). So the speed was 
> about 4000, while the full speed is about 4900 and 9 is a hundred or a 
> couple of hundred less. Temperatures didn't go over 54 (or maybe 55) °C. 
> Idle CPU (at 800MHz thanks to Cool'n'Quiet) went down to 46°C more and more.
> 
> Today, however, while the CPU was not loaded much, the fan appeared to 
> be full speed again (at least according to the sensors applet).
> 
> But the new sensors-detect was also mentioning "k10temp" (and the old 
> one in Debian didn't work), so today I installed a new k10temp, and it 
> showed 60°C for something.
> 
> Now I have set the fan speed to full in UEFI, and here is what "sensors" 
> shows:
> 
> 
> nct6775-isa-0290
> Adapter: ISA adapter
> Vcore:       +1.08 V  (min =  +0.00 V, max =  +1.74 V)
> in1:         +1.03 V  (min =  +0.00 V, max =  +0.00 V)   ALARM

	Possibly 12V (*12)

> AVCC:        +3.33 V  (min =  +2.98 V, max =  +3.63 V)
> +3.3V:       +3.33 V  (min =  +2.98 V, max =  +3.63 V)
> in4:         +1.39 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in5:         +1.86 V  (min =  +0.00 V, max =  +0.00 V)   ALARM

No idea what in4/in5 might be.

> in6:         +1.66 V  (min =  +0.00 V, max =  +0.00 V)   ALARM

	This one might be 5V (*3)

Guenter

> 3VSB:        +3.44 V  (min =  +2.98 V, max =  +3.63 V)
> Vbat:        +3.39 V  (min =  +2.70 V, max =  +3.30 V)   ALARM
> fan1:          0 RPM  (min =    0 RPM, div = 128)
> fan2:       4963 RPM  (min =    0 RPM, div = 8)  ALARM
> fan3:          0 RPM  (min =    0 RPM, div = 128)
> fan4:          0 RPM  (div = 128)
> SYSTIN:      +51.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = 
> thermistor
> CPUTIN:      +45.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
> AUXTIN:       -9.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
> cpu0_vid:   +0.000 V
> 
> k10temp-pci-00c3
> Adapter: PCI adapter
> temp1:       +58.0°C  (high = +70.0°C, crit = +75.0°C)
> 
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] testing "w83627ehf" and "k10temp" on ASRock E350M1

[Jean Delvare]

Hi Aleksej, Guenter,

On Wed, 6 Apr 2011 15:54:56 -0700, Guenter Roeck wrote:
> On Wed, Apr 06, 2011 at 01:38:56PM -0400, Aleksej Serdjukov wrote:
> > I've got this computer with ASRock E350M1, and have no idea what the 
> > temperatures should actually be.
> > 
> > This is on Debian 6.0:
> > Linux 2.6.32-5-amd64 #1 SMP Mon Mar 7 21:35:22 UTC 2011 x86_64 GNU/Linux
> > 
> > 
> > IIRC, UEFI Setup was showing about 52°C on the motherboard or chipset, 
> > and 49-52 on the CPU.
> > 
> > About a week ago I've installed the "w83627ehf" from 
> > <http://roeck-us.net/linux/drivers/w83627ehf/>, and saw that those 
> > temperatures don't go over 53 or 54°C. So I changed the UEFI setting 
> > more and more for slower fan speed (today it was 6). So the speed was 
> > about 4000, while the full speed is about 4900 and 9 is a hundred or a 
> > couple of hundred less. Temperatures didn't go over 54 (or maybe 55) °C. 
> > Idle CPU (at 800MHz thanks to Cool'n'Quiet) went down to 46°C more and more.
> > 
> > Today, however, while the CPU was not loaded much, the fan appeared to 
> > be full speed again (at least according to the sensors applet).

It's always nice to get user reports, but... what is your problem
exactly? Do you have an actual question?

> > But the new sensors-detect was also mentioning "k10temp" (and the old 
> > one in Debian didn't work), so today I installed a new k10temp, and it 
> > showed 60°C for something.

Please note that the internal sensors in AMD CPUs have never need
considered accurate. Some models are better than others but it general
the temperature reported by k8temp or k10temp should be taken with a
grain of salt. Also note that the internal digital sensor is not
located as the same place as the analog sensors used by the external
monitoring chip, so it is expected that the reported temperatures are
different.

> > 
> > Now I have set the fan speed to full in UEFI, and here is what "sensors" 
> > shows:
> > 
> > 
> > nct6775-isa-0290
> > Adapter: ISA adapter
> > Vcore:       +1.08 V  (min =  +0.00 V, max =  +1.74 V)
> > in1:         +1.03 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> 
> 	Possibly 12V (*12)
> 
> > AVCC:        +3.33 V  (min =  +2.98 V, max =  +3.63 V)
> > +3.3V:       +3.33 V  (min =  +2.98 V, max =  +3.63 V)
> > in4:         +1.39 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> > in5:         +1.86 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> 
> No idea what in4/in5 might be.

DDR3 runs at +1.8V so in5 could be Vdimm. Best is to check what the
BIOS is printing, and compare.

> 
> > in6:         +1.66 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> 
> 	This one might be 5V (*3)
> 
> Guenter
> 
> > 3VSB:        +3.44 V  (min =  +2.98 V, max =  +3.63 V)
> > Vbat:        +3.39 V  (min =  +2.70 V, max =  +3.30 V)   ALARM
> > fan1:          0 RPM  (min =    0 RPM, div = 128)
> > fan2:       4963 RPM  (min =    0 RPM, div = 8)  ALARM
> > fan3:          0 RPM  (min =    0 RPM, div = 128)
> > fan4:          0 RPM  (div = 128)
> > SYSTIN:      +51.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor =  thermistor
> > CPUTIN:      +45.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor

These temperatures look reasonable to me. Find out which is the CPU
temperature by putting some load on the CPU: the CPU temperature will
raise faster and higher. You should also set appropriate limits for
temp1 and write them to the chip with "sensors -s".

> > AUXTIN:       -9.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor

Can obviously be ignored.

> > cpu0_vid:   +0.000 V

Same here... unless this is a bug in the driver.

Makes me wonder if we should have our driver check for VID = 0V and
disable the cpuN_vid file in this case.

> > k10temp-pci-00c3
> > Adapter: PCI adapter
> > temp1:       +58.0°C  (high = +70.0°C, crit = +75.0°C)

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] testing "w83627ehf" and "k10temp" on ASRock E350M1

[Aleksej Serdjukov]

(sorry, the CCs seem to have confused Thunderbird)
On 2011-04-07 11:26, Jean Delvare wrote:
 > Hi Aleksej, Guenter,
 >
 > On Wed, 6 Apr 2011 15:54:56 -0700, Guenter Roeck wrote:
 >> On Wed, Apr 06, 2011 at 01:38:56PM -0400, Aleksej Serdjukov wrote:
 >>> Today, however, while the CPU was not loaded much, the fan appeared to
 >>> be full speed again (at least according to the sensors applet).
 >
 > It's always nice to get user reports, but...

The wiki says the driver "needs testing" (though as of 2011-02-01).  I 
thought that at least AUXTIN being negative was something worth reporting.

 > what is your problem exactly? Do you have an actual question?

My problem is the noise the fan is making at full-on speed. I want it to 
be reasonably quiet, but I don't know why it is following the speed 
chosen (between 1 and 9) and not just trying to keep the chosen CPU 
temperature; and why yesterday it suddenly got to maximum without me 
changing the setting or the non-temp1 temperatures being ordinary.


Since k10temp shown 60-65°C, I set the fan speed to full and posted here.

Also, the only clear statement about temperatures of E-350 I found is 
that the maximum is 90. Reviews talk about 30 or 50. Where should I stop 
with the quietness?


 >>> But the new sensors-detect was also mentioning "k10temp" (and the old
 >>> one in Debian didn't work), so today I installed a new k10temp, and it
 >>> showed 60°C for something.
 >
 > Please note that the internal sensors in AMD CPUs have never need
 > considered accurate. Some models are better than others but it general

So can I ignore it when choosing fan speed? Or see that it doesn't go to 
the 90°C maximum?


 >>> in1:         +1.03 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
 >>
 >> 	Possibly 12V (*12)
 >>
 >>> AVCC:        +3.33 V  (min =  +2.98 V, max =  +3.63 V)
 >>> +3.3V:       +3.33 V  (min =  +2.98 V, max =  +3.63 V)
 >>> in4:         +1.39 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
 >>> in5:         +1.86 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
 >>
 >> No idea what in4/in5 might be.
 >
 > DDR3 runs at +1.8V so in5 could be Vdimm. Best is to check what the
 > BIOS is printing, and compare.

Settings in UEFI:
DRAM : 1.507
+1V  : 1.10
FCH  : 1.10
+1.8V: 1.85



== START COMPARISON #1 =======================
UEFI's H/W pane said:

CPU Temp: 44  (got there from 40 since reboot)
M/B Temp: 44  (got there from 43 since reboot)

Vcore: 1.304 V
+12 V: 12.196 V
+5.00: 4.992 V
+3.30: 3.328 V


sensors after boot:

k10temp-pci-00c3
Adapter: PCI adapter
temp1:       +57.5°C  (high = +70.0°C, crit = +75.0°C)

nct6775-isa-0290
Adapter: ISA adapter
Vcore:       +1.13 V  (min =  +0.00 V, max =  +1.74 V)
in1:         +1.00 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
AVCC:        +3.33 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:       +3.33 V  (min =  +2.98 V, max =  +3.63 V)
in4:         +1.38 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in5:         +1.86 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in6:         +1.66 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
3VSB:        +3.44 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:        +3.39 V  (min =  +2.70 V, max =  +3.30 V)   ALARM
fan1:          0 RPM  (min =    0 RPM, div = 64)
fan2:       4963 RPM  (min =    0 RPM, div = 8)  ALARM
fan3:          0 RPM  (min =    0 RPM, div = 128)
fan4:          0 RPM  (div = 128)
SYSTIN:      +45.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = 
thermistor
CPUTIN:      +43.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
AUXTIN:       -8.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
cpu0_vid:   +0.000 V

== END #1 =============================



== START COMPARISON #2 =======================

UEFI's H/W Monitor pane said:

VCore: 1.304
+12  : 12.144
+5   : 4.9?2
+3.3 : 3.328


sensors after boot:

k10temp-pci-00c3
Adapter: PCI adapter
temp1:       +63.0°C  (high = +70.0°C, crit = +75.0°C)

nct6775-isa-0290
Adapter: ISA adapter
Vcore:       +1.08 V  (min =  +0.00 V, max =  +1.74 V)
in1:         +1.02 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
AVCC:        +3.33 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:       +3.33 V  (min =  +2.98 V, max =  +3.63 V)
in4:         +1.39 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in5:         +1.86 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in6:         +1.66 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
3VSB:        +3.44 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:        +3.39 V  (min =  +2.70 V, max =  +3.30 V)   ALARM
fan1:          0 RPM  (min =    0 RPM, div = 32)
fan2:       5113 RPM  (min =    0 RPM, div = 8)  ALARM
fan3:          0 RPM  (min =    0 RPM, div = 128)
fan4:          0 RPM  (div = 128)
SYSTIN:      +53.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = 
thermistor
CPUTIN:      +50.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
AUXTIN:       -9.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
cpu0_vid:   +0.000 V

== END #2 =============================


 >>> in6:         +1.66 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
 >>
 >> 	This one might be 5V (*3)

UEFI: +5.00: 4.992 V

4.992 / 3 = 1.664
1.66 * 3 = 4.98


 >>> SYSTIN:      +51.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM 
sensor =  thermistor
 >>> CPUTIN:      +45.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = 
thermistor
 >
 > These temperatures look reasonable to me. Find out which is the CPU
 > temperature by putting some load on the CPU: the CPU temperature will
 > raise faster and higher. You should also set appropriate limits for
 > temp1 and write them to the chip with "sensors -s".

CPUTIN and temp1 slowly increased (CPUTIN from 44-46 to 48-49, temp1 
from 56 to 67-69).


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] testing "w83627ehf" and "k10temp" on ASRock E350M1

[Jean Delvare]

On Thu, 07 Apr 2011 13:11:44 +0400, Aleksej Serdjukov wrote:
> (sorry, the CCs seem to have confused Thunderbird)
> On 2011-04-07 11:26, Jean Delvare wrote:
>  > Hi Aleksej, Guenter,
>  >
>  > On Wed, 6 Apr 2011 15:54:56 -0700, Guenter Roeck wrote:
>  >> On Wed, Apr 06, 2011 at 01:38:56PM -0400, Aleksej Serdjukov wrote:
>  >>> Today, however, while the CPU was not loaded much, the fan appeared to
>  >>> be full speed again (at least according to the sensors applet).
>  >
>  > It's always nice to get user reports, but...
> 
> The wiki says the driver "needs testing" (though as of 2011-02-01).  I 
> thought that at least AUXTIN being negative was something worth reporting.

Yes, support for the NCT677x is relatively recent, so reports are
definitely welcome.

Negative temperature are relatively common and usually mean that the
thermal sensor in question is missing (temperature monitoring channel
is unused.) Nothing to worry about, just ignore the reading. We will
only investigate if you have an evidence that the temperature value
should be reported correctly (the BIOS or another OS is reporting it.)

>  > what is your problem exactly? Do you have an actual question?
> 
> My problem is the noise the fan is making at full-on speed. I want it to 
> be reasonably quiet, but I don't know why it is following the speed 
> chosen (between 1 and 9) and not just trying to keep the chosen CPU 
> temperature; and why yesterday it suddenly got to maximum without me 
> changing the setting or the non-temp1 temperatures being ordinary.

You should have explained this upfront!

> Since k10temp shown 60-65°C, I set the fan speed to full and posted here.
> 
> Also, the only clear statement about temperatures of E-350 I found is 
> that the maximum is 90. Reviews talk about 30 or 50. Where should I stop 
> with the quietness?

Where did you get the maximum temperature from? The k10temp driver
seems to disagree - it says 75°C max.

>  >>> But the new sensors-detect was also mentioning "k10temp" (and the old
>  >>> one in Debian didn't work), so today I installed a new k10temp, and it
>  >>> showed 60°C for something.
>  >
>  > Please note that the internal sensors in AMD CPUs have never need
>  > considered accurate. Some models are better than others but it general
> 
> So can I ignore it when choosing fan speed? Or see that it doesn't go to 
> the 90°C maximum?

In your specific case, the k10temp driver seems to report reasonable
values so there is no reason to ignore it.

>  >>> in1:         +1.03 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>  >>
>  >> 	Possibly 12V (*12)
>  >>
>  >>> AVCC:        +3.33 V  (min =  +2.98 V, max =  +3.63 V)
>  >>> +3.3V:       +3.33 V  (min =  +2.98 V, max =  +3.63 V)
>  >>> in4:         +1.39 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>  >>> in5:         +1.86 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>  >>
>  >> No idea what in4/in5 might be.
>  >
>  > DDR3 runs at +1.8V so in5 could be Vdimm. Best is to check what the
>  > BIOS is printing, and compare.
> 
> Settings in UEFI:
> DRAM : 1.507
> +1V  : 1.10
> FCH  : 1.10
> +1.8V: 1.85

Err, sorry I messed up. DDR3 is definitely +1.5V, +1.8V was DDR2. Not
sure what I was up to this morning. But anyway, in5 seems to match
+1.8V in UEFI, whatever it is used for.

Are these settings as in "you can decide the values"? Or measurements?
It is strange that there is no match for DRAM, +1V nor FCH in the
sensors output.

> == START COMPARISON #1 =======================> 
> UEFI's H/W pane said:
> 
> CPU Temp: 44  (got there from 40 since reboot)
> M/B Temp: 44  (got there from 43 since reboot)
> 
> Vcore: 1.304 V
> +12 V: 12.196 V
> +5.00: 4.992 V
> +3.30: 3.328 V
>
> sensors after boot:
> 
> k10temp-pci-00c3
> Adapter: PCI adapter
> temp1:       +57.5°C  (high = +70.0°C, crit = +75.0°C)
> 
> nct6775-isa-0290
> Adapter: ISA adapter
> Vcore:       +1.13 V  (min =  +0.00 V, max =  +1.74 V)

Does this value increase if you put much load on the CPU? It's quite
different from the 1.304 V reported by UEFI.

> in1:         +1.00 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> AVCC:        +3.33 V  (min =  +2.98 V, max =  +3.63 V)
> +3.3V:       +3.33 V  (min =  +2.98 V, max =  +3.63 V)
> in4:         +1.38 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in5:         +1.86 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in6:         +1.66 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> 3VSB:        +3.44 V  (min =  +2.98 V, max =  +3.63 V)
> Vbat:        +3.39 V  (min =  +2.70 V, max =  +3.30 V)   ALARM
> fan1:          0 RPM  (min =    0 RPM, div = 64)
> fan2:       4963 RPM  (min =    0 RPM, div = 8)  ALARM
> fan3:          0 RPM  (min =    0 RPM, div = 128)
> fan4:          0 RPM  (div = 128)
> SYSTIN:      +45.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = 
> thermistor
> CPUTIN:      +43.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
> AUXTIN:       -8.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
> cpu0_vid:   +0.000 V
> 
> == END #1 =============================
> 
> 
> 
> == START COMPARISON #2 =======================> 
> 
> UEFI's H/W Monitor pane said:
> 
> VCore: 1.304
> +12  : 12.144

Previous value printed for +12V was 12.196. 12.196 - 12.144 = 0.052.
Assuming this difference represents one LSB at the register level,
which has a weight of 8 mV on the W83627EHF-compatible chips, this
means a scaling factor of ~6.5. 12.144 / 6.5 = 1.868. Which seems to
match in5. So I'm no longer sure if in5 is +12V or +1.8V...

> +5   : 4.9?2
> +3.3 : 3.328
> 
> 
> sensors after boot:
> 
> k10temp-pci-00c3
> Adapter: PCI adapter
> temp1:       +63.0°C  (high = +70.0°C, crit = +75.0°C)
> 
> nct6775-isa-0290
> Adapter: ISA adapter
> Vcore:       +1.08 V  (min =  +0.00 V, max =  +1.74 V)
> in1:         +1.02 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> AVCC:        +3.33 V  (min =  +2.98 V, max =  +3.63 V)
> +3.3V:       +3.33 V  (min =  +2.98 V, max =  +3.63 V)
> in4:         +1.39 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in5:         +1.86 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in6:         +1.66 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> 3VSB:        +3.44 V  (min =  +2.98 V, max =  +3.63 V)
> Vbat:        +3.39 V  (min =  +2.70 V, max =  +3.30 V)   ALARM
> fan1:          0 RPM  (min =    0 RPM, div = 32)
> fan2:       5113 RPM  (min =    0 RPM, div = 8)  ALARM
> fan3:          0 RPM  (min =    0 RPM, div = 128)
> fan4:          0 RPM  (div = 128)
> SYSTIN:      +53.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = 
> thermistor
> CPUTIN:      +50.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
> AUXTIN:       -9.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
> cpu0_vid:   +0.000 V
> 
> == END #2 =============================
> 
> 
>  >>> in6:         +1.66 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>  >>
>  >> 	This one might be 5V (*3)
> 
> UEFI: +5.00: 4.992 V
> 
> 4.992 / 3 = 1.664
> 1.66 * 3 = 4.98

This is one possibility, yes. It could be confirmed by capturing at
least one other +5V value in UEFI.

> 
> 
>  >>> SYSTIN:      +51.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM 
> sensor =  thermistor
>  >>> CPUTIN:      +45.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = 
> thermistor
>  >
>  > These temperatures look reasonable to me. Find out which is the CPU
>  > temperature by putting some load on the CPU: the CPU temperature will
>  > raise faster and higher. You should also set appropriate limits for
>  > temp1 and write them to the chip with "sensors -s".
> 
> CPUTIN and temp1 slowly increased (CPUTIN from 44-46 to 48-49, temp1 
> from 56 to 67-69).

69°C is dangerously close to the limits. Which is odd given the high
fan speed. Are you sure the case gets enough cooling from the outside /
can get the hot air evacuated properly?

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] testing "w83627ehf" and "k10temp" on ASRock E350M1

[Aleksej Serdjukov]

On 2011-04-07 16:24, Jean Delvare wrote:
> On Thu, 07 Apr 2011 13:11:44 +0400, Aleksej Serdjukov wrote:
>> (sorry, the CCs seem to have confused Thunderbird)
>> On 2011-04-07 11:26, Jean Delvare wrote:
>>   >  what is your problem exactly? Do you have an actual question?
>>
>> My problem is the noise the fan is making at full-on speed. I want it to
>> be reasonably quiet, but I don't know why it is following the speed
>> chosen (between 1 and 9) and not just trying to keep the chosen CPU
>> temperature; and why yesterday it suddenly got to maximum without me
>> changing the setting or the non-temp1 temperatures being ordinary.
>
> You should have explained this upfront!

Sorry, maybe it's because I don't know what the temperature should be.


>> Since k10temp shown 60-65°C, I set the fan speed to full and posted here.
>>
>> Also, the only clear statement about temperatures of E-350 I found is
>> that the maximum is 90. Reviews talk about 30 or 50. Where should I stop
>> with the quietness?
>
> Where did you get the maximum temperature from? The k10temp driver
> seems to disagree - it says 75°C max.

http://products.amd.com/%28X%281%29S%28q5r43t55n5rep1j4u3pjcf45%29%29/pages/desktopapudetail.aspx?id=1&f1=AMD+Dual-Core+Processor+E-350&f2=E-350+with+AMD+Radeon%E2%84%A2+HD+6310+Graphics&f3\x1600&f4=2&f5=FT1+BGA&f6\x18+W&AspxAutoDetectCookieSupport=1

Maybe 75 is when UEFI would shut it down?


>> Settings in UEFI:
>> DRAM : 1.507
>> +1V  : 1.10
>> FCH  : 1.10
>> +1.8V: 1.85
>
> Err, sorry I messed up. DDR3 is definitely +1.5V, +1.8V was DDR2. Not
> sure what I was up to this morning. But anyway, in5 seems to match
> +1.8V in UEFI, whatever it is used for.
>
> Are these settings as in "you can decide the values"? Or measurements?
> It is strange that there is no match for DRAM, +1V nor FCH in the
> sensors output.

The former, I guess. The numbers are next to drop-down lists of values 
where "Auto" is selected.


>> == START COMPARISON #1 =======================>>
>> UEFI's H/W pane said:
>>
>> CPU Temp: 44  (got there from 40 since reboot)
>> M/B Temp: 44  (got there from 43 since reboot)
>>
>> Vcore: 1.304 V
>> +12 V: 12.196 V
>> +5.00: 4.992 V
>> +3.30: 3.328 V
>>
>> sensors after boot:
>>
>> k10temp-pci-00c3
>> Adapter: PCI adapter
>> temp1:       +57.5°C  (high = +70.0°C, crit = +75.0°C)
>>
>> nct6775-isa-0290
>> Adapter: ISA adapter
>> Vcore:       +1.13 V  (min =  +0.00 V, max =  +1.74 V)
>
> Does this value increase if you put much load on the CPU? It's quite
> different from the 1.304 V reported by UEFI.

In UEFI, Vcore is switching between 1.256 and 1.304.
In sensors (with fan auto control at 7 or 8, 48°), Vcore mostly stays at 
1.08, and under load at 1.30 V.


>> UEFI's H/W Monitor pane said:
>>
>> VCore: 1.304
>> +12  : 12.144
>
> Previous value printed for +12V was 12.196. 12.196 - 12.144 = 0.052.

12V is switching ("like" Vcore).

>>   >>>  in6:         +1.66 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>>   >>
>>   >>  	This one might be 5V (*3)
>>
>> UEFI: +5.00: 4.992 V
>>
>> 4.992 / 3 = 1.664
>> 1.66 * 3 = 4.98
>
> This is one possibility, yes. It could be confirmed by capturing at
> least one other +5V value in UEFI.

+5 V seems to always be 4.992 (unless I miswrote 4.982 in #2)

>>   >>>  SYSTIN:      +51.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM
>> sensor =  thermistor
>>   >>>  CPUTIN:      +45.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor >> thermistor
>>   >
>>   >  These temperatures look reasonable to me. Find out which is the CPU
>>   >  temperature by putting some load on the CPU: the CPU temperature will
>>   >  raise faster and higher. You should also set appropriate limits for
>>   >  temp1 and write them to the chip with "sensors -s".
>>
>> CPUTIN and temp1 slowly increased (CPUTIN from 44-46 to 48-49, temp1
>> from 56 to 67-69).
>
> 69°C is dangerously close to the limits. Which is odd given the high
> fan speed.

That was with burnK7. Maybe I shouldn't have used that. But then (fan 
auto control at speed 7 or 8, 48°) p7zip gets it to 66 immediately and 
then to 68.

> Are you sure the case gets enough cooling from the outside /
> can get the hot air evacuated properly?

It is in 15-25 cm from walls, and in 30 cm from a heating pipe. Air 
temperature there is 22-24°C.

The case is IN WIN BQ656BL.

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] testing "w83627ehf" and "k10temp" on ASRock E350M1

[Aleksej Serdjukov]

On 2011-04-07 16:24, Jean Delvare wrote:
> On Thu, 07 Apr 2011 13:11:44 +0400, Aleksej Serdjukov wrote:
> Negative temperature are relatively common and usually mean that the
> thermal sensor in question is missing (temperature monitoring channel
> is unused.) Nothing to worry about, just ignore the reading. We will
> only investigate if you have an evidence that the temperature value
> should be reported correctly (the BIOS or another OS is reporting it.)

I've seen AUXTIN have values of -9.5, -9, -8.5 (changes with no restart 
needed).

>> So can I ignore it when choosing fan speed? Or see that it doesn't go to
>> the 90째C maximum?
>
> In your specific case, the k10temp driver seems to report reasonable
> values so there is no reason to ignore it.

Yesterday I watched the fan speed while compressing, and it switched 
from being auto-controlled (~4000-4300) to full-speed after temp1 shown 
68째C (then compression ended). The temperatures went down quickly, but 
the fan speed seemed to never go below 4800 after that (unless I missed 
another heat-up).


>> Vcore:       +1.13 V  (min =  +0.00 V, max =  +1.74 V)
>
> Does this value increase if you put much load on the CPU? It's quite
> different from the 1.304 V reported by UEFI.

Since I turned C6 on in UEFI, Vcore in sensors is about 0.5-0.6 V when 
idle (that is mentioned in a Russian review with a screenshot: 
<http://www.overclockers.ua/motherboard/amd-apu-zacate/).


>> CPUTIN and temp1 slowly increased (CPUTIN from 44-46 to 48-49, temp1
>> from 56 to 67-69).
>
> 69째C is dangerously close to the limits. Which is odd given the high
> fan speed. Are you sure the case gets enough cooling from the outside /
> can get the hot air evacuated properly?

So, is it dangerous with the table maximum for the APU being 90째, and 
with the MSI E350IA-E45 auto mode starting the fan at 70 (same review, 
page 3)?


FWIW, in <http://patchwork.coreboot.org/patch/2687/> Scott wrote "The 
SIO is Nuvoton NCT5572D."


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors