All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Artem S. Tashkinov" <birdie@permonline.ru>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] A question regarding ASRock H55DE3 motherboard
Date: Thu, 18 Feb 2010 11:25:48 +0000	[thread overview]
Message-ID: <4B7D23BC.2070305@permonline.ru> (raw)
In-Reply-To: <4B7A403E.7000103@permonline.ru>

[-- Attachment #1: Type: text/plain, Size: 4373 bytes --]

On 02/18/2010 02:15 AM, Jean Delvare wrote:
> On Thu, 18 Feb 2010 01:08:04 +0500, Artem S. Tashkinov wrote:
>> On 02/18/2010 12:19 AM, Jean Delvare wrote:
>>   >  This driver should be available. If it's not there, this suggests that
>>   >  you did not set CONFIG_SENSORS_ADT7473=m when building your kernel. You
>>   >  should have...
>>
>> I will try to build this driver and report if it shows anything.
>
> Note: last time I checked (long ago), the binary nvidia driver which
> you appear to be using, did not let hwmon driver probe its I2C buses
> for devices. So you might have to instantiate the chip yourself with:
>
> # echo adt7473 0x2e>  /sys/class/i2c-adapter/i2c-<N>/device/new_device
>
> where<N>  is the bus number of the i2c bus in question.

echo adt7473 0x2e > /sys/class/i2c-adapter/i2c-3/new_device produced the 
desired results:

adt7473-i2c-3-2e
Adapter: NVIDIA i2c adapter
in1:         +3.00 V  (min =  +0.00 V, max =  +2.99 V)
+3.3V:       +3.33 V  (min =  +0.00 V, max =  +4.39 V)
fan1:        889 RPM  (min =    0 RPM)
fan2:          0 RPM  (min =    0 RPM)
fan3:          0 RPM  (min =  164 RPM)  ALARM
temp1:       +39.2°C  (low  = +65.0°C, high = +85.0°C)  ALARM
                       (crit = +100.0°C, hyst = +98.0°C)
Board Temp:  +33.8°C  (low  = +20.0°C, high = +60.0°C)
                       (crit = +100.0°C, hyst = +96.0°C)
temp3:       +39.2°C  (low  = +80.0°C, high = +105.0°C)  ALARM
                       (crit = +136.0°C, hyst = +132.0°C)

The output needs to be configured (via /etc/sensors.d/chipname.conf), 
but that's not a problem.

>
>> (...)
>> It looks like it's my own blunder: I have confused w83_2_627 to w83627
>> :) and taking into consideration ASRock's documentation my chip is
>> indeed made by Nuvoton and it's currently unsupported - I'm eagerly
>> awaiting patches to be merged.
>
> Hmm, does the W832627 actually exist? I thought it was a typo.
>

I apologize - it's my double blunder - HWMon shows Winbond W83627DHG 
chip. So I tried w83627dhg driver and it perfectly works on my system 
when loaded this way (as you suggested in a previous letter):

modprobe w83627ehf force_id=0xa020

w83627dhg-isa-0290
Adapter: ISA adapter
Vcore:       +0.82 V  (min =  +0.00 V, max =  +1.74 V)
in1:         +1.85 V  (min =  +0.69 V, max =  +1.91 V)
AVCC:        +3.39 V  (min =  +2.00 V, max =  +0.56 V)   ALARM
VCC:         +3.39 V  (min =  +2.86 V, max =  +1.76 V)   ALARM
in4:         +0.05 V  (min =  +1.53 V, max =  +1.94 V)   ALARM
in5:         +1.71 V  (min =  +1.32 V, max =  +1.86 V)
in6:         +0.05 V  (min =  +1.66 V, max =  +1.90 V)   ALARM
3VSB:        +3.49 V  (min =  +1.50 V, max =  +2.99 V)   ALARM
Vbat:        +3.34 V  (min =  +3.71 V, max =  +3.74 V)   ALARM
fan1:          0 RPM  (min =  217 RPM, div = 64)  ALARM
fan2:       1004 RPM  (min =  397 RPM, div = 32)
fan3:          0 RPM  (min =  357 RPM, div = 64)  ALARM
fan4:          0 RPM  (min =   84 RPM, div = 128)  ALARM
fan5:          0 RPM  (min =  703 RPM, div = 16)  ALARM
temp1:       +33.0°C  (high = -13.0°C, hyst = -46.0°C)  ALARM  sensor = 
thermistor
temp2:       +36.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
temp3:      +127.5°C  (high = +80.0°C, hyst = +75.0°C)  ALARM  sensor = 
thermistor
cpu0_vid:   +0.000 V

However this means two things, w83627ehf driver needs to be updated to 
work with my PC (I can send any system information if it's required) and 
sensors-detect script should also be modified to correctly identify my 
sensors (it missed coretemp driver altogether).

***

coretemp driver started working after I applied the attached patch, 
however the readings are wrong, so probably this driver is not yet 
capable of monitoring Intel Core i5 650 CPU (temperatures are all wrong, 
there are only two physical CPU cores):

coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +23.0°C  (high = +84.0°C, crit = +100.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1:      +26.0°C  (high = +84.0°C, crit = +100.0°C)

coretemp-isa-0002
Adapter: ISA adapter
Core 2:      +23.0°C  (high = +84.0°C, crit = +100.0°C)

coretemp-isa-0003
Adapter: ISA adapter
Core 3:      +26.0°C  (high = +84.0°C, crit = +100.0°C)

Thank you very much, Jean, for your invaluable help.

-- 

Best wishes,

Artem

[-- Attachment #2: coretemp.intel.core.i5.patch --]
[-- Type: text/plain, Size: 469 bytes --]

--- coretemp.c.default	2010-02-18 16:14:58.517835386 +0500
+++ coretemp.c	2010-02-18 15:54:35.128157728 +0500
@@ -460,7 +460,7 @@
 		    !((c->x86_model == 0xe) || (c->x86_model == 0xf) ||
 			(c->x86_model == 0x16) || (c->x86_model == 0x17) ||
 			(c->x86_model == 0x1a) || (c->x86_model == 0x1c) ||
-			(c->x86_model == 0x1e))) {
+			(c->x86_model == 0x1e) || (c->x86_model == 0x25))) {
 
 			/* supported CPU not found, but report the unknown
 			   family 6 CPU */

[-- Attachment #3: Type: text/plain, Size: 153 bytes --]

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

  parent reply	other threads:[~2010-02-18 11:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-16  6:50 [lm-sensors] A question regarding ASRock H55DE3 motherboard Artem S. Tashkinov
2010-02-17 19:19 ` Jean Delvare
2010-02-17 20:08 ` Artem S. Tashkinov
2010-02-17 21:15 ` Jean Delvare
2010-02-18 11:25 ` Artem S. Tashkinov [this message]
2010-02-19  9:52 ` Jean Delvare
2010-02-19 12:26 ` Artem S. Tashkinov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B7D23BC.2070305@permonline.ru \
    --to=birdie@permonline.ru \
    --cc=lm-sensors@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.