* [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol
@ 2009-06-24 9:47 Konstantin Kletschke
2009-06-24 11:08 ` Luca Tettamanti
` (14 more replies)
0 siblings, 15 replies; 16+ messages in thread
From: Konstantin Kletschke @ 2009-06-24 9:47 UTC (permalink / raw)
To: lm-sensors
Hi Folks!
Recently I wanted to add userspace control of my CPU fan on
my Asus P5Q and due to this not working, I stumbled upon this:
http://ubuntuforums.org/showpost.php?sò405c8983cbae7023fde7333fce3e05&ph16455&postcount=6
The Chip on the Board is an W83667HG-A with id 0xa513 as sensors-detect
says:
Trying family `VIA/Winbond/Fintek'... Yes
Found unknown chip with ID 0xa513
(logical device B has address 0x290, could be sensors)
The effort done in
http://thread.gmane.org/gmane.linux.drivers.sensors/17253
Yields to an almost reasonable sensors output:
w83667hg-isa-0290
Adapter: ISA adapter
in0: +1.02 V (min = +0.00 V, max = +1.74 V)
in1: +1.76 V (min = +0.90 V, max = +0.05 V) ALARM
in2: +3.31 V (min = +3.95 V, max = +0.26 V) ALARM
in3: +3.28 V (min = +3.20 V, max = +2.37 V) ALARM
in4: +1.69 V (min = +0.64 V, max = +0.55 V) ALARM
in5: +2.04 V (min = +1.10 V, max = +1.42 V) ALARM
in7: +3.39 V (min = +0.06 V, max = +2.18 V) ALARM
in8: +3.28 V (min = +3.66 V, max = +0.32 V) ALARM
fan1: 0 RPM (min = 10546 RPM, div = 128) ALARM
fan2: 534 RPM (min = 2163 RPM, div = 16) ALARM
fan3: 0 RPM (min = 10546 RPM, div = 128) ALARM
fan4: 0 RPM (min = 10546 RPM, div = 128) ALARM
fan5: 0 RPM (min = 10546 RPM, div = 128) ALARM
temp1: +44.0°C (high = -112.0°C, hyst = -123.0°C) ALARM sensor = thermistor
temp2: +40.5°C (high = +80.0°C, hyst = +75.0°C) sensor = diode
temp3: +5.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
cpu0_vid: +2.700 V
insmod:
w83627ehf: Found W83667HG chip at 0x290
w83627ehf w83627ehf.656: Increasing fan1 clock divider from 32 to 64
w83627ehf w83627ehf.656: Increasing fan1 clock divider from 64 to 128
It is not possible to change the pwm of the CPU fan. Changing the value
of pwm2 results in changing pwm1. May be this is only a little tiny
offset in the amounts of pwms or another tiny little bit missing.
Is there any change to get a datasheet of this chip or can somebody
provide one?
> cat pwm1 pwm2 pwm3
66
55
255
> echo "77" >> pwm2
> cat pwm1 pwm2 pwm3
77
55
255
On my investigation I discovered some sort of acpi based atk0110 driver
for the asus boards, which works fine so far.
ATK0110 ATK0110:00: adding...
ATK0110 ATK0110:00: board ID = P5Q
ATK0110 ATK0110:00: Using old hwmon interface
ATK0110 ATK0110:00: voltage: 0x6020000 Vcore Voltage [800-1600] enabled
ATK0110 ATK0110:00: voltage: 0x6020001 +3.3 Voltage [2970-3630] enabled
ATK0110 ATK0110:00: voltage: 0x6020002 +5 Voltage [4500-5500] enabled
ATK0110 ATK0110:00: voltage: 0x6020003 +12 Voltage [10200-13800] enabled
ATK0110 ATK0110:00: temperature: 0x6030000 CPU Temperature [600-950] enabled
ATK0110 ATK0110:00: temperature: 0x6030001 MB Temperature [450-950] enabled
ATK0110 ATK0110:00: fan: 0x6040000 CPU FAN Speed [600-7200] enabled
ATK0110 ATK0110:00: fan: 0x6040001 CHASSIS1 FAN Speed [600-7200] enabled
ATK0110 ATK0110:00: fan: 0x6040002 CHASSIS2 FAN Speed [600-7200] enabled
ATK0110 ATK0110:00: fan: 0x6040003 POWER FAN Speed [600-7200] enabled
ATK0110 ATK0110:00: registering hwmon device
ATK0110 ATK0110:00: populating sysfs directory
The readings from fan1_[input|label] are reasonable:
> cat fan1_input fan1_label
534
CPU FAN Speed
Can fan pwm value controlled with this driver?
Does lm_sensors-3.1.0 still need to be patched to acces this driver?
Kind Regards, Konsti
--
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol
2009-06-24 9:47 [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol Konstantin Kletschke
@ 2009-06-24 11:08 ` Luca Tettamanti
2009-06-24 12:10 ` Jean Delvare
` (13 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Luca Tettamanti @ 2009-06-24 11:08 UTC (permalink / raw)
To: lm-sensors
On Wed, Jun 24, 2009 at 11:47 AM, Konstantin Kletschke<konsti@ku-gbr.de> wrote:
> On my investigation I discovered some sort of acpi based atk0110 driver
> for the asus boards, which works fine so far.
>
> ATK0110 ATK0110:00: adding...
> ATK0110 ATK0110:00: board ID = P5Q
> ATK0110 ATK0110:00: Using old hwmon interface
> ATK0110 ATK0110:00: voltage: 0x6020000 Vcore Voltage [800-1600] enabled
> ATK0110 ATK0110:00: voltage: 0x6020001 +3.3 Voltage [2970-3630] enabled
> ATK0110 ATK0110:00: voltage: 0x6020002 +5 Voltage [4500-5500] enabled
> ATK0110 ATK0110:00: voltage: 0x6020003 +12 Voltage [10200-13800] enabled
> ATK0110 ATK0110:00: temperature: 0x6030000 CPU Temperature [600-950] enabled
> ATK0110 ATK0110:00: temperature: 0x6030001 MB Temperature [450-950] enabled
> ATK0110 ATK0110:00: fan: 0x6040000 CPU FAN Speed [600-7200] enabled
> ATK0110 ATK0110:00: fan: 0x6040001 CHASSIS1 FAN Speed [600-7200] enabled
> ATK0110 ATK0110:00: fan: 0x6040002 CHASSIS2 FAN Speed [600-7200] enabled
> ATK0110 ATK0110:00: fan: 0x6040003 POWER FAN Speed [600-7200] enabled
> ATK0110 ATK0110:00: registering hwmon device
> ATK0110 ATK0110:00: populating sysfs directory
>
> The readings from fan1_[input|label] are reasonable:
>
>> cat fan1_input fan1_label
> 534
> CPU FAN Speed
>
> Can fan pwm value controlled with this driver?
Not directly, the relevant ACPI method doesn't actually touch the
hardware. It should be possible to use Q-FAN to switch between
different profiles, but I've yet to RE that interface.
> Does lm_sensors-3.1.0 still need to be patched to acces this driver?
No, it's fine as is.
Luca
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol
2009-06-24 9:47 [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol Konstantin Kletschke
2009-06-24 11:08 ` Luca Tettamanti
@ 2009-06-24 12:10 ` Jean Delvare
2009-06-24 12:32 ` Konstantin Kletschke
` (12 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Jean Delvare @ 2009-06-24 12:10 UTC (permalink / raw)
To: lm-sensors
Hi Konstantin,
On Wed, 24 Jun 2009 11:47:38 +0200, Konstantin Kletschke wrote:
> It is not possible to change the pwm of the CPU fan. Changing the value
> of pwm2 results in changing pwm1. May be this is only a little tiny
> offset in the amounts of pwms or another tiny little bit missing.
> Is there any change to get a datasheet of this chip or can somebody
> provide one?
>
> > cat pwm1 pwm2 pwm3
> 66
> 55
> 255
>
> > echo "77" >> pwm2
Note that the >> doesn't buy you anything, > is enough. These are
virtual files.
>
> > cat pwm1 pwm2 pwm3
> 77
> 55
> 255
This is very odd. Which kernel are you running exactly? I have a hard
time understanding how this can happen at all. Does writing to pwm3
change the value of pwm2, too?
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol
2009-06-24 9:47 [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol Konstantin Kletschke
2009-06-24 11:08 ` Luca Tettamanti
2009-06-24 12:10 ` Jean Delvare
@ 2009-06-24 12:32 ` Konstantin Kletschke
2009-06-24 12:34 ` Konstantin Kletschke
` (11 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Konstantin Kletschke @ 2009-06-24 12:32 UTC (permalink / raw)
To: lm-sensors
Hi Jean,
Am 2009-06-24 14:10 +0200 schrieb Jean Delvare:
> Note that the >> doesn't buy you anything, > is enough. These are
> virtual files.
My zsh has no_clobber enabled and the shell insists on >> even on
virtual files therefore :-)
> This is very odd. Which kernel are you running exactly? I have a hard
Exactly I am running 2.6.30-rc7, the guy reporting this in the ubuntu
forum did this februrary 28th, so on another kernel.
> time understanding how this can happen at all. Does writing to pwm3
> change the value of pwm2, too?
echo into pwm1 changes nothing:
> cat pwm1 pwm2 pwm3
77
55
78
> echo "99" >> pwm1
> cat pwm1 pwm2 pwm3
77
55
78
echo into pwm2 changes pwm1:
> cat pwm1 pwm2 pwm3
77
55
78
> echo "99" >> pwm2
> cat pwm1 pwm2 pwm3
99
55
78
echo into pwm3 changes pwm3:
> cat pwm1 pwm2 pwm3
99
55
78
> echo "100" >> pwm3
> cat pwm1 pwm2 pwm3
99
55
100
Regards, Konsti
--
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol
2009-06-24 9:47 [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol Konstantin Kletschke
` (2 preceding siblings ...)
2009-06-24 12:32 ` Konstantin Kletschke
@ 2009-06-24 12:34 ` Konstantin Kletschke
2009-06-24 12:38 ` Luca Tettamanti
` (10 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Konstantin Kletschke @ 2009-06-24 12:34 UTC (permalink / raw)
To: lm-sensors
Hi Luca,
Am 2009-06-24 13:08 +0200 schrieb Luca Tettamanti:
> > Can fan pwm value controlled with this driver?
>
> Not directly, the relevant ACPI method doesn't actually touch the
> hardware. It should be possible to use Q-FAN to switch between
> different profiles, but I've yet to RE that interface.
You mean the cooling profile (actually selectable in BIOS) could be
changed from acpi, if REed?
> > Does lm_sensors-3.1.0 still need to be patched to acces this driver?
>
> No, it's fine as is.
Okay, so the my problem remains to access pwm2 which not seems to be
possible at the moment.
Regards, Konsti
--
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol
2009-06-24 9:47 [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol Konstantin Kletschke
` (3 preceding siblings ...)
2009-06-24 12:34 ` Konstantin Kletschke
@ 2009-06-24 12:38 ` Luca Tettamanti
2009-06-24 12:53 ` Jean Delvare
` (9 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Luca Tettamanti @ 2009-06-24 12:38 UTC (permalink / raw)
To: lm-sensors
On Wed, Jun 24, 2009 at 2:34 PM, Konstantin Kletschke<konsti@ku-gbr.de> wrote:
> Hi Luca,
>
> Am 2009-06-24 13:08 +0200 schrieb Luca Tettamanti:
>
>> > Can fan pwm value controlled with this driver?
>>
>> Not directly, the relevant ACPI method doesn't actually touch the
>> hardware. It should be possible to use Q-FAN to switch between
>> different profiles, but I've yet to RE that interface.
>
> You mean the cooling profile (actually selectable in BIOS) could be
> changed from acpi, if REed?
Yes, that's what I meant.
L
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol
2009-06-24 9:47 [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol Konstantin Kletschke
` (4 preceding siblings ...)
2009-06-24 12:38 ` Luca Tettamanti
@ 2009-06-24 12:53 ` Jean Delvare
2009-06-24 13:44 ` Konstantin Kletschke
` (8 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Jean Delvare @ 2009-06-24 12:53 UTC (permalink / raw)
To: lm-sensors
On Wed, 24 Jun 2009 14:32:45 +0200, Konstantin Kletschke wrote:
> Hi Jean,
>
> Am 2009-06-24 14:10 +0200 schrieb Jean Delvare:
>
> > Note that the >> doesn't buy you anything, > is enough. These are
> > virtual files.
>
> My zsh has no_clobber enabled and the shell insists on >> even on
> virtual files therefore :-)
The usual way to counter no_clobber is >|, not >>.
> > This is very odd. Which kernel are you running exactly? I have a hard
>
> Exactly I am running 2.6.30-rc7, the guy reporting this in the ubuntu
> forum did this februrary 28th, so on another kernel.
Would you be able and willing to apply a patch to your kernel and
rebuild it, if I come up with something?
> > time understanding how this can happen at all. Does writing to pwm3
> > change the value of pwm2, too?
>
> echo into pwm1 changes nothing:
>
> > cat pwm1 pwm2 pwm3
> 77
> 55
> 78
> > echo "99" >> pwm1
> > cat pwm1 pwm2 pwm3
> 77
> 55
> 78
>
> echo into pwm2 changes pwm1:
>
> > cat pwm1 pwm2 pwm3
> 77
> 55
> 78
> > echo "99" >> pwm2
> > cat pwm1 pwm2 pwm3
> 99
> 55
> 78
>
> echo into pwm3 changes pwm3:
>
> > cat pwm1 pwm2 pwm3
> 99
> 55
> 78
> > echo "100" >> pwm3
> > cat pwm1 pwm2 pwm3
> 99
> 55
> 100
This is all very confusing, I admit. I would like you to unload the
w83627ehf driver and try to read from / write to the chip directly. For
this you'll need the isadump and isaset tools (part of lm-sensors.)
Registers pwm1, pwm2 and pwm3 are at 0x01, 0x03 and 0x11, respectively.
You can see their raw value using the following command (as root):
isaset 0x295 0x296 0x4e 0 # set bank to 0
isadump 0x295 0x296
Then I would like you to write to each register, then check the result.
The value written doesn't matter as long as it is different from the
current value of all 3 registers in question:
isaset 0x295 0x296 0x01 0xaa
isadump 0x295 0x296
isaset 0x295 0x296 0x03 0xbb
isadump 0x295 0x296
isaset 0x295 0x296 0x11 0xcc
isadump 0x295 0x296
If this works fine then that would be a bug in the driver. If it
doesn't, that would be a hardware bug.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol
2009-06-24 9:47 [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol Konstantin Kletschke
` (5 preceding siblings ...)
2009-06-24 12:53 ` Jean Delvare
@ 2009-06-24 13:44 ` Konstantin Kletschke
2009-06-24 14:23 ` Konstantin Kletschke
` (7 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Konstantin Kletschke @ 2009-06-24 13:44 UTC (permalink / raw)
To: lm-sensors
Am 2009-06-24 14:53 +0200 schrieb Jean Delvare:
> The usual way to counter no_clobber is >|, not >>.
I indeed did not knew this, thanks! :)
> Would you be able and willing to apply a patch to your kernel and
> rebuild it, if I come up with something?
Yes of course. I am quite firm even with this i2c stuff and kernel
programming (and watching running or dying when running :-)).
Also I know how things go in developing drivers (or a family of them)
and nobody has the entrire different hardware under his desk. So I have
this onw under my desk and fun in doing whatever you want to it :-)
> This is all very confusing, I admit. I would like you to unload the
> w83627ehf driver and try to read from / write to the chip directly. For
> this you'll need the isadump and isaset tools (part of lm-sensors.)
I will get my hand on these and report.
Konsti
--
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol
2009-06-24 9:47 [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol Konstantin Kletschke
` (6 preceding siblings ...)
2009-06-24 13:44 ` Konstantin Kletschke
@ 2009-06-24 14:23 ` Konstantin Kletschke
2009-06-25 8:31 ` Jean Delvare
` (6 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Konstantin Kletschke @ 2009-06-24 14:23 UTC (permalink / raw)
To: lm-sensors
Okay, I even moved the w83627ehf.ko and asus_atk0110.ko away and
rebooted.
Am 2009-06-24 14:53 +0200 schrieb Jean Delvare:
> isaset 0x295 0x296 0x4e 0 # set bank to 0
> isadump 0x295 0x296
>isaset 0x295 0x296 0x4e 0
>isadump 0x295 0x296
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 04 ff 04 3d 00 00 46 20 01 9b 01 01 3c 3c 04 04
10: 04 99 30 00 00 01 01 3c 43 17 00 00 32 ff ff c5
20: 80 dc cf cd d3 ff c3 2c ff 99 ff da 00 06 71 10
30: f7 94 c8 45 50 b2 8a 13 c1 90 85 01 27 01 01 ff
40: 03 00 00 ff ff 00 3f 35 2d 21 20 40 10 95 00 a3
50: ff ff 00 ff ff ff 00 80 c1 6f ff ff 19 45 04 05
60: 04 3d 50 00 01 01 3c ff 0a ff 01 ff ff ff ff 28
70: 46 46 46 46 46 37 ff ff ff ff ff 4b 22 00 2c ff
80: 04 ff 04 3d 00 00 46 20 01 9b 01 01 3c 3c 04 04
90: 04 99 30 00 00 01 01 3c 43 17 00 00 32 ff ff c5
a0: 80 dc cf cd d3 ff c3 2c ff 99 ff da 00 06 71 10
b0: f7 94 c8 45 50 b2 8a 13 c1 90 85 01 27 01 01 ff
c0: 03 00 00 ff ff 00 3f 35 2d 21 20 40 10 95 00 a3
d0: ff ff 00 ff ff ff 00 80 c1 6f ff ff 19 45 04 05
e0: 04 3d 50 00 01 01 3c ff 0a ff 01 ff ff ff ff 28
f0: 46 46 46 46 46 37 ff ff ff ff ff 4b 22 00 2c ff
> isaset 0x295 0x296 0x01 0xaa
> isadump 0x295 0x296
>isaset 0x295 0x296 0x01 0xaa
Data mismatch, wrote 0xaa, read 0xff back.
>isadump 0x295 0x296
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 04 ff 04 3d 00 00 46 20 01 9b 01 01 3c 3c 04 04
10: 04 99 30 00 00 01 01 3c 43 17 00 00 32 ff ff cf
20: 80 dc cf ce d3 ff c3 2c ff 99 ff da 00 06 71 10
30: f7 94 c8 45 50 b2 8a 13 c1 90 85 01 27 01 01 ff
40: 03 00 00 ff ff 00 3f 35 2d 21 20 40 10 95 00 a3
50: ff ff 00 ff ff ff 00 80 c1 6f ff ff 19 45 04 05
60: 04 3d 50 00 01 01 3c ff 0a ff 01 ff ff ff ff 28
70: 46 46 46 46 46 37 ff ff ff ff ff 4b 22 00 2c ff
80: 04 ff 04 3d 00 00 46 20 01 9b 01 01 3c 3c 04 04
90: 04 99 30 00 00 01 01 3c 43 17 00 00 32 ff ff cf
a0: 80 dc cf ce d3 ff c3 2c ff 99 ff da 00 06 71 10
b0: f7 94 c8 45 50 b2 8a 13 c1 90 85 01 27 01 01 ff
c0: 03 00 00 ff ff 00 3f 35 2d 21 20 40 10 95 00 a3
d0: ff ff 00 ff ff ff 00 80 c1 6f ff ff 19 45 04 05
e0: 04 3d 50 00 01 01 3c ff 0a ff 01 ff ff ff ff 28
f0: 46 46 46 46 46 37 ff ff ff ff ff 4b 22 00 2c ff
0x01 seems to be readonly.
> isaset 0x295 0x296 0x03 0xbb
> isadump 0x295 0x296
>isaset 0x295 0x296 0x03 0xbb
Data mismatch, wrote 0xbb, read 0x37 back.
>isadump 0x295 0x296
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 04 bb 04 37 00 00 46 20 01 9b 01 01 3c 3c 04 04
10: 04 99 30 00 00 01 01 3c 43 17 00 00 32 ff ff d1
20: 80 dc cf ce d3 ff c3 2b ff 9d ff da 00 06 71 10
30: f7 94 c8 45 50 b2 8a 13 c1 90 85 01 27 01 01 ff
40: 03 00 00 ff ff 00 3f 35 2d 21 20 40 10 95 00 a3
50: ff ff 00 ff ff ff 00 80 c1 6f ff ff 19 45 04 05
60: 04 37 50 00 01 01 3c ff 0a ff 01 ff ff ff ff 28
70: 46 46 46 46 46 37 ff ff ff ff ff 4b 22 00 2b ff
80: 04 bb 04 37 00 00 46 20 01 9b 01 01 3c 3c 04 04
90: 04 99 30 00 00 01 01 3c 43 17 00 00 32 ff ff d1
a0: 80 dc cf ce d3 ff c3 2b ff 9d ff da 00 06 71 10
b0: f7 94 c8 45 50 b2 8a 13 c1 90 85 01 27 01 01 ff
c0: 03 00 00 ff ff 00 3f 35 2d 21 20 40 10 95 00 a3
d0: ff ff 00 ff ff ff 00 80 c1 6f ff ff 19 45 04 05
e0: 04 37 50 00 01 01 3c ff 0a ff 01 ff ff ff ff 28
f0: 46 46 46 46 46 37 ff ff ff ff ff 4b 22 00 2b ff
0x03 writes to 0x01...
> isaset 0x295 0x296 0x11 0xcc
> isadump 0x295 0x296
>isaset 0x295 0x296 0x11 0xcc
>isadump 0x295 0x296
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 04 bb 04 37 00 00 46 20 01 9b 01 01 3c 3c 04 04
10: 04 cc 30 00 00 01 01 3c 43 17 00 00 32 ff ff d3
20: 80 dc cf ce d3 ff c3 2b ff 9d ff da 00 06 71 10
30: f7 94 c8 45 50 b2 8a 13 c1 90 85 01 27 01 01 ff
40: 03 00 00 ff ff 00 3f 35 2d 21 20 40 10 95 00 a3
50: ff ff 00 ff ff ff 00 80 c1 6f ff ff 19 45 04 05
60: 04 37 50 00 01 01 3c ff 0a ff 01 ff ff ff ff 28
70: 46 46 46 46 46 37 ff ff ff ff ff 4b 22 00 2b ff
80: 04 bb 04 37 00 00 46 20 01 9b 01 01 3c 3c 04 04
90: 04 cc 30 00 00 01 01 3c 43 17 00 00 32 ff ff d3
a0: 80 dc cf ce d3 ff c3 2b ff 9d ff da 00 06 71 10
b0: f7 94 c8 45 50 b2 8a 13 c1 90 85 01 27 01 01 ff
c0: 03 00 00 ff ff 00 3f 35 2d 21 20 40 10 95 00 a3
d0: ff ff 00 ff ff ff 00 80 c1 6f ff ff 19 45 04 05
e0: 04 37 50 00 01 01 3c ff 0a ff 01 ff ff ff ff 28
f0: 46 46 46 46 46 37 ff ff ff ff ff 4b 22 00 2b ff
0x11 indeed writes to 0x11.
This reflects somehow how echo into the /sys filesystem reacts.
> If this works fine then that would be a bug in the driver. If it
> doesn't, that would be a hardware bug.
What I wonder, is there any success report pwm controlling cpu fan from
userspace with this W83667HG-A chip?
Meanwhile I read many reports not achieving this. There are two other
fan header (3-PIN non PWM) and many people connect their fans there and
doing DC regulation, even on windows platform (the other pin on some
p5q-xxx boards are able to do DC regulating there, I don't know if mine
is able to do yet).
Kind Regards, Konsti
--
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol
2009-06-24 9:47 [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol Konstantin Kletschke
` (7 preceding siblings ...)
2009-06-24 14:23 ` Konstantin Kletschke
@ 2009-06-25 8:31 ` Jean Delvare
2009-06-25 9:21 ` Jean Delvare
` (5 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Jean Delvare @ 2009-06-25 8:31 UTC (permalink / raw)
To: lm-sensors
Hallo Konstantin,
On Wed, 24 Jun 2009 16:23:50 +0200, Konstantin Kletschke wrote:
> Okay, I even moved the w83627ehf.ko and asus_atk0110.ko away and
> rebooted.
>
> Am 2009-06-24 14:53 +0200 schrieb Jean Delvare:
>
> > isaset 0x295 0x296 0x4e 0 # set bank to 0
> > isadump 0x295 0x296
>
> >isaset 0x295 0x296 0x4e 0
> >isadump 0x295 0x296
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: 04 ff 04 3d 00 00 46 20 01 9b 01 01 3c 3c 04 04
> 10: 04 99 30 00 00 01 01 3c 43 17 00 00 32 ff ff c5
> 20: 80 dc cf cd d3 ff c3 2c ff 99 ff da 00 06 71 10
> 30: f7 94 c8 45 50 b2 8a 13 c1 90 85 01 27 01 01 ff
> 40: 03 00 00 ff ff 00 3f 35 2d 21 20 40 10 95 00 a3
> 50: ff ff 00 ff ff ff 00 80 c1 6f ff ff 19 45 04 05
> 60: 04 3d 50 00 01 01 3c ff 0a ff 01 ff ff ff ff 28
> 70: 46 46 46 46 46 37 ff ff ff ff ff 4b 22 00 2c ff
> 80: 04 ff 04 3d 00 00 46 20 01 9b 01 01 3c 3c 04 04
> 90: 04 99 30 00 00 01 01 3c 43 17 00 00 32 ff ff c5
> a0: 80 dc cf cd d3 ff c3 2c ff 99 ff da 00 06 71 10
> b0: f7 94 c8 45 50 b2 8a 13 c1 90 85 01 27 01 01 ff
> c0: 03 00 00 ff ff 00 3f 35 2d 21 20 40 10 95 00 a3
> d0: ff ff 00 ff ff ff 00 80 c1 6f ff ff 19 45 04 05
> e0: 04 3d 50 00 01 01 3c ff 0a ff 01 ff ff ff ff 28
> f0: 46 46 46 46 46 37 ff ff ff ff ff 4b 22 00 2c ff
>
> > isaset 0x295 0x296 0x01 0xaa
> > isadump 0x295 0x296
>
> >isaset 0x295 0x296 0x01 0xaa
> Data mismatch, wrote 0xaa, read 0xff back.
> >isadump 0x295 0x296
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: 04 ff 04 3d 00 00 46 20 01 9b 01 01 3c 3c 04 04
> 10: 04 99 30 00 00 01 01 3c 43 17 00 00 32 ff ff cf
> 20: 80 dc cf ce d3 ff c3 2c ff 99 ff da 00 06 71 10
> 30: f7 94 c8 45 50 b2 8a 13 c1 90 85 01 27 01 01 ff
> 40: 03 00 00 ff ff 00 3f 35 2d 21 20 40 10 95 00 a3
> 50: ff ff 00 ff ff ff 00 80 c1 6f ff ff 19 45 04 05
> 60: 04 3d 50 00 01 01 3c ff 0a ff 01 ff ff ff ff 28
> 70: 46 46 46 46 46 37 ff ff ff ff ff 4b 22 00 2c ff
> 80: 04 ff 04 3d 00 00 46 20 01 9b 01 01 3c 3c 04 04
> 90: 04 99 30 00 00 01 01 3c 43 17 00 00 32 ff ff cf
> a0: 80 dc cf ce d3 ff c3 2c ff 99 ff da 00 06 71 10
> b0: f7 94 c8 45 50 b2 8a 13 c1 90 85 01 27 01 01 ff
> c0: 03 00 00 ff ff 00 3f 35 2d 21 20 40 10 95 00 a3
> d0: ff ff 00 ff ff ff 00 80 c1 6f ff ff 19 45 04 05
> e0: 04 3d 50 00 01 01 3c ff 0a ff 01 ff ff ff ff 28
> f0: 46 46 46 46 46 37 ff ff ff ff ff 4b 22 00 2c ff
>
> 0x01 seems to be readonly.
>
> > isaset 0x295 0x296 0x03 0xbb
> > isadump 0x295 0x296
>
> >isaset 0x295 0x296 0x03 0xbb
> Data mismatch, wrote 0xbb, read 0x37 back.
> >isadump 0x295 0x296
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: 04 bb 04 37 00 00 46 20 01 9b 01 01 3c 3c 04 04
> 10: 04 99 30 00 00 01 01 3c 43 17 00 00 32 ff ff d1
> 20: 80 dc cf ce d3 ff c3 2b ff 9d ff da 00 06 71 10
> 30: f7 94 c8 45 50 b2 8a 13 c1 90 85 01 27 01 01 ff
> 40: 03 00 00 ff ff 00 3f 35 2d 21 20 40 10 95 00 a3
> 50: ff ff 00 ff ff ff 00 80 c1 6f ff ff 19 45 04 05
> 60: 04 37 50 00 01 01 3c ff 0a ff 01 ff ff ff ff 28
> 70: 46 46 46 46 46 37 ff ff ff ff ff 4b 22 00 2b ff
> 80: 04 bb 04 37 00 00 46 20 01 9b 01 01 3c 3c 04 04
> 90: 04 99 30 00 00 01 01 3c 43 17 00 00 32 ff ff d1
> a0: 80 dc cf ce d3 ff c3 2b ff 9d ff da 00 06 71 10
> b0: f7 94 c8 45 50 b2 8a 13 c1 90 85 01 27 01 01 ff
> c0: 03 00 00 ff ff 00 3f 35 2d 21 20 40 10 95 00 a3
> d0: ff ff 00 ff ff ff 00 80 c1 6f ff ff 19 45 04 05
> e0: 04 37 50 00 01 01 3c ff 0a ff 01 ff ff ff ff 28
> f0: 46 46 46 46 46 37 ff ff ff ff ff 4b 22 00 2b ff
>
> 0x03 writes to 0x01...
>
> > isaset 0x295 0x296 0x11 0xcc
> > isadump 0x295 0x296
>
> >isaset 0x295 0x296 0x11 0xcc
> >isadump 0x295 0x296
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: 04 bb 04 37 00 00 46 20 01 9b 01 01 3c 3c 04 04
> 10: 04 cc 30 00 00 01 01 3c 43 17 00 00 32 ff ff d3
> 20: 80 dc cf ce d3 ff c3 2b ff 9d ff da 00 06 71 10
> 30: f7 94 c8 45 50 b2 8a 13 c1 90 85 01 27 01 01 ff
> 40: 03 00 00 ff ff 00 3f 35 2d 21 20 40 10 95 00 a3
> 50: ff ff 00 ff ff ff 00 80 c1 6f ff ff 19 45 04 05
> 60: 04 37 50 00 01 01 3c ff 0a ff 01 ff ff ff ff 28
> 70: 46 46 46 46 46 37 ff ff ff ff ff 4b 22 00 2b ff
> 80: 04 bb 04 37 00 00 46 20 01 9b 01 01 3c 3c 04 04
> 90: 04 cc 30 00 00 01 01 3c 43 17 00 00 32 ff ff d3
> a0: 80 dc cf ce d3 ff c3 2b ff 9d ff da 00 06 71 10
> b0: f7 94 c8 45 50 b2 8a 13 c1 90 85 01 27 01 01 ff
> c0: 03 00 00 ff ff 00 3f 35 2d 21 20 40 10 95 00 a3
> d0: ff ff 00 ff ff ff 00 80 c1 6f ff ff 19 45 04 05
> e0: 04 37 50 00 01 01 3c ff 0a ff 01 ff ff ff ff 28
> f0: 46 46 46 46 46 37 ff ff ff ff ff 4b 22 00 2b ff
>
> 0x11 indeed writes to 0x11.
>
> This reflects somehow how echo into the /sys filesystem reacts.
Indeed. So this is not a bug in the driver, but rather the hardware
misbehaving. I'll ask out contact at Nuvoton about this.
> > If this works fine then that would be a bug in the driver. If it
> > doesn't, that would be a hardware bug.
>
> What I wonder, is there any success report pwm controlling cpu fan from
> userspace with this W83667HG-A chip?
Support for the W83667HG is still relatively new. Officially this chip
is only supported since kernel 2.6.30 which was released just 2 weeks
ago. So we didn't have much feedback yet.
> Meanwhile I read many reports not achieving this. There are two other
> fan header (3-PIN non PWM) and many people connect their fans there and
> doing DC regulation, even on windows platform (the other pin on some
> p5q-xxx boards are able to do DC regulating there, I don't know if mine
> is able to do yet).
Could as well be that the chip has a silicon bug...
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol
2009-06-24 9:47 [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol Konstantin Kletschke
` (8 preceding siblings ...)
2009-06-25 8:31 ` Jean Delvare
@ 2009-06-25 9:21 ` Jean Delvare
2009-06-29 8:44 ` Konstantin Kletschke
` (4 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Jean Delvare @ 2009-06-25 9:21 UTC (permalink / raw)
To: lm-sensors
On Wed, 24 Jun 2009 16:23:50 +0200, Konstantin Kletschke wrote:
> What I wonder, is there any success report pwm controlling cpu fan from
> userspace with this W83667HG-A chip?
>
> Meanwhile I read many reports not achieving this. There are two other
> fan header (3-PIN non PWM) and many people connect their fans there and
> doing DC regulation, even on windows platform (the other pin on some
> p5q-xxx boards are able to do DC regulating there, I don't know if mine
> is able to do yet).
Additional question: does the BIOS offer options to enable/disable
automatic fan speed control? If so, please list them all, and check
what is their effect on the pwm* values (including pwm*_enable)
reported by the w83627ehf driver.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol
2009-06-24 9:47 [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol Konstantin Kletschke
` (9 preceding siblings ...)
2009-06-25 9:21 ` Jean Delvare
@ 2009-06-29 8:44 ` Konstantin Kletschke
2009-06-29 8:47 ` Konstantin Kletschke
` (3 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Konstantin Kletschke @ 2009-06-29 8:44 UTC (permalink / raw)
To: lm-sensors
After a delay, hello again!
Am 2009-06-25 10:31 +0200 schrieb Jean Delvare:
> > This reflects somehow how echo into the /sys filesystem reacts.
>
> Indeed. So this is not a bug in the driver, but rather the hardware
> misbehaving. I'll ask out contact at Nuvoton about this.
That would be very interesting. Do you know if I could also get a
datasheet from them for this chip? I read stuff of NDA or so (which
shuold be no Problem to sign).
I don't know whome they give one and
to whome not Since I am not unexperienced fiddling out such stuff this
is bad with me sitting here with nothing.
> Support for the W83667HG is still relatively new. Officially this chip
Indeed, because of that I poked in here to play with it. Or is W83667HG-A
a special revision behavin different?
> is only supported since kernel 2.6.30 which was released just 2 weeks
> ago. So we didn't have much feedback yet.
:-) Here it is.
> Could as well be that the chip has a silicon bug...
That would be a mess!
Kind Regards, Konsti
--
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol
2009-06-24 9:47 [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol Konstantin Kletschke
` (10 preceding siblings ...)
2009-06-29 8:44 ` Konstantin Kletschke
@ 2009-06-29 8:47 ` Konstantin Kletschke
2009-07-12 22:11 ` Marco Chiappero
` (2 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Konstantin Kletschke @ 2009-06-29 8:47 UTC (permalink / raw)
To: lm-sensors
Am 2009-06-25 11:21 +0200 schrieb Jean Delvare:
> Additional question: does the BIOS offer options to enable/disable
> automatic fan speed control? If so, please list them all, and check
Yes, the BIOS offer disabling Q-Fan and enabling it. If enabled I can
chosse between Turbo, normal or silent mode.
I use Q-Fan now enabled, when I switch it off the driver behaves
identical.
> what is their effect on the pwm* values (including pwm*_enable)
> reported by the w83627ehf driver.
Also pwm*_enable shows "1" any time trying this.
Konsti
--
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 16+ messages in thread
* [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol
2009-06-24 9:47 [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol Konstantin Kletschke
` (11 preceding siblings ...)
2009-06-29 8:47 ` Konstantin Kletschke
@ 2009-07-12 22:11 ` Marco Chiappero
2009-08-08 22:13 ` Reimundo Heluani
2009-08-09 1:58 ` Reimundo Heluani
14 siblings, 0 replies; 16+ messages in thread
From: Marco Chiappero @ 2009-07-12 22:11 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1: Type: text/plain, Size: 2198 bytes --]
Hi,
sorry for not noticing this thread before!
> > 0x11 indeed writes to 0x11.
> > This reflects somehow how echo into the /sys filesystem reacts.
>
> Indeed. So this is not a bug in the driver, but rather the hardware
> misbehaving. I'll ask out contact at Nuvoton about this.
Same behavior here with another Asus board (Maximus II Formula -
W83667HG-A).
A few words about the topic W83667HG vs ATK0110.
I'm currently using the atk0110 driver [1] and I'm happy with it since I
don't need a fine grain control for my fans and the default hw control
looks pretty good to me. As you know, the Asus software for Windows
indeed uses the ACPI interface, so I suggest the Asus owners to move to
the ATK0110 driver. However I'd like to implement or to see implemented
the fan profile switching for the Q-Fan mode, allowing minimum fan
control but still sufficient for most users. I had a quick look at the
driver code and at my dsdt and it seems easy enought.
I'd like to put attention on another aspect of many recent board from
Asus, the power management, aka EPU. Today I gave another try to Everest
on Windows and made a sensors dump (attached). As you can see from the
bus scan many chips are present, the Winbond, the two unidentified ICs
at 0x38 and 0x40, and, among others, an IC at 0x20. Accordingly with a
scan from the previous model of this board, the Maxiums Formula (Sensor
Type W83627DHG + W83791D + ADT7475 + ADP3228 (ISA 290h, SMB
2Ch/2Eh/20h)) and the Everest output, it is the ASP0800, a custom VRM
control chip from AD, providing (I suppose) the current CPU wattage
reading. I don't know the right indexes for this information but it's
somehow possibile. I think it's interesting for the Asus owners to add
this reading as well, if possible, isn't it?
It would be great to receive further informations from Asus in order to
have some power tuning capabilities like the Windows 6-Engine software
provides, but it's out of the hwmon scope and need good contacts at Asus.
[1] Well, to tell the true I would have no choice since most readings
are provided by two unknown ICs.
http://lists.lm-sensors.org/pipermail/lm-sensors/2008-September/024163.html
[-- Attachment #2: everest.txt --]
[-- Type: text/plain, Size: 29618 bytes --]
Propriet��� sensore
Tipo sensore Winbond W83667HG (ISA 290h)
Tipo sensore GPU Diode (ATI-Diode)
Nome scheda madre Asus Maximus II Series
Rilevata intrusione nello chassis No
Temperature
Scheda madre 40 ���C (104 ���F)
Processore 32 ���C (90 ���F)
Processore 1 / core 1 39 ���C (102 ���F)
Processore 1 / core 2 39 ���C (102 ���F)
North Bridge 51 ���C (124 ���F)
South Bridge 54 ���C (129 ���F)
PWM 42 ���C (108 ���F)
Diodo GPU 49 ���C (120 ���F)
Temperatura 1 26 ���C (79 ���F)
Temperatura 2 38 ���C (100 ���F)
Temperatura 3 40 ���C (104 ���F)
WDC WD6401AALS-00L3B2 [ TRIAL VERSION ]
Ventoline
Processore 981 RPM
Chassis 1 672 RPM
Chassis 2 802 RPM
Chassis 3 842 RPM
Valori voltaggio
Core processore 0.94 V
+3.3 V 3.34 V
+5 V 5.11 V
+12 V [ TRIAL VERSION ]
Standby V +5 5.12 V
CPU VTT 1.12 V
CPU PLL 1.53 V
North Bridge +1.1 V 1.12 V
South Bridge +1.1 V 1.12 V
South Bridge +1.5 V 1.50 V
DIMM 2.11 V
DIMM VTT 1.05 V
Valori dissipazione di potenza
Processore 4.14 W
Debug Info F D3 55 FF D4 0C
Debug Info T 40 33 26
Debug Info V 75 D9 D3 D1 D6 FF 9B (03)
Debug Info I C1 A513
------[ Motherboard Info ]------
Motherboard ID : 65-1901-000001-00101111-121708-Eaglelake$A1007001_BIOS DATE: 12/17/08 12:28:08 VER: 08.00.14
Motherboard Model : Asus Maximus II Formula
Motherboard Chipset : Intel Eaglelake P45
DMI MB Manufacturer : ASUSTeK Computer INC.
DMI MB Product : Maximus II Formula
DMI MB Version : Rev 1.xx
DMI MB Serial : MS1C86B22000429
DMI SYS Manufacturer: System manufacturer
DMI SYS Product : Maximus II Formula
DMI SYS Version : System Version
DMI SYS Serial : System Serial Number
DMI BIOS Version : 1901
------[ GPIO @ isa 0500 ]------
0000 C2 75 FD 19 C3 7F 6F E0 00 00 00 00 FD FE FD E2
0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0020 00 00 08 00 00 00 00 00 00 00 00 00 C0 24 00 00
0030 FF 00 03 03 50 FF 55 0D 83 FF FE 1F 00 00 00 00
ITE 87xx HWMonitor Port 0000h
ITE 87xx Device ID 0000h
ITE 87xx Version 00h
Winbond SuperIO HWMonitor Port 0290h
Winbond SuperIO Device ID A513h
Fintek SuperIO HWMonitor Port 0000h
Fintek SuperIO Device ID 0000h
LPC47 SuperIO HWMonitor Port 0000h
LPC47 SuperIO Device ID FFFFh
------[ LM78 ISA Sensor Device at 0290 ]------
0000 04 7F 04 4A 30 00 3C 20 01 9B 01 01 3C 3C 04 04
0010 04 FF 30 00 00 01 01 3C 43 17 00 00 2A FF FF CF
0020 7C D9 D2 D0 D5 FF 9B 28 D4 55 FF DA 00 0D 12 9A
0030 C2 14 04 B0 71 89 61 00 32 25 40 88 80 32 37 D5
0040 03 DE 00 FF FF 00 3F 35 2D 21 20 C0 10 95 00 A3
0050 FF FF 00 FF FF FF 00 80 C1 7F FF FF 19 C4 04 05
0060 04 4A 50 00 01 01 3C FF 0A FF 01 FF FF FF FF 1E
0070 3C 3C 3C 3C 3C 37 FF FF FF FF FF 4B 22 00 28 FF
0080 04 7F 04 4A 30 00 3C 20 01 9B 01 01 3C 3C 04 04
0090 04 FF 30 00 00 01 01 3C 43 17 00 00 2A FF FF CF
00A0 7C D9 D2 D0 D5 FF 9B 28 D4 55 FF DA 00 0D 12 9A
00B0 C2 14 04 B0 71 89 61 00 32 25 40 88 80 32 37 D5
00C0 03 00 00 FF FF 00 3F 35 2D 21 20 C0 10 95 00 A3
00D0 FF FF 00 FF FF FF 00 80 C1 7F FF FF 19 C4 04 05
00E0 04 4A 50 00 01 01 3C FF 0A FF 01 FF FF FF FF 1E
00F0 3C 3C 3C 3C 3C 37 FF FF FF FF FF 4B 22 00 28 FF
------[ ACPI Temperatures & Fans ]------
_TZ_.THM0._TMP :
_TZ_.THM1._TMP :
_TZ_.THR0._TMP :
_TZ_.THR1._TMP :
_TZ_.TZ00._TMP :
_TZ_.TZ01._TMP :
_TZ_.RFAN :
_TZ_.RFAN(0) :
_TZ_.RFAN(1) :
_SB_.ATKD.TMPR :
_SB_.PCI0.LPC0.EC0_.CCTV :
_SB_.PCI0.LPC0.EC0_.LRPM :
_SB_.PCI0.LPC0.EC0_.HRPM :
_SB_.PCI0.SBRG.EC0_.ECPU :
_SB_.PCI0.SBRG.EC0_.TACH(0):
_SB_.PCI0.SBRG.EC0_.TACH(1):
_SB_.PCI0.SBRG.EC0_.TAH0 :
_SB_.PCI0.SBRG.EC0_.TAH1 :
_SB_.PCI0.SBRG.EC0_.ST00 :
_SB_.PCI0.SBRG.EC0_.SC01 :
_SB_.PCI0.SBRG.EC0_.SC02 :
_SB_.PCI0.SBRG.EC0_.SC03 :
_SB_.PCI0.SBRG.EC0_.SC04 :
_SB_.PCI0.SBRG.EC0_.SC05 :
_SB_.PCI0.SBRG.EC0_.SC06 :
_SB_.PCI0.PIB_.EC0_.TCRT :
_SB_.PCI0.SBRG.EC0_.CTPM :
_SB_.PCI0.SBRG.EC__.CPUT :
_SB_.PCI0.SBRG.EC__.SYST :
_SB_.PCI0.LPC_.EC0_.CTMP :
_SB_.PCI0.LPCB.EC0_.CTMP :
_SB_.PCI0.LPC_.EC0_.TMP1 :
_SB_.PCI0.LPC_.EC0_.TMP2 :
_SB_.PCI0.LPC_.EC0_.TMPI :
_SB_.PCI0.LPC_.EC0_.TMPV :
------[ Asus ATK0110 ]------
Motherboard ID: P5Q-Deluxe
ICPU/VCPU/PCPU: 10 / 82 / 54142
CPU Temperature 33.5 C
MB Temperature 40.0 C
NB Temperature 51.0 C
OPT_FAN1 Temperature 26.0 C
OPT_FAN2 Temperature 38.0 C
OPT_FAN3 Temperature 40.0 C
POWER Temperature 42.0 C
SB Temperature 54.0 C
CH_FAN1 Speed 671 RPM
CH_FAN2 Speed 802 RPM
CH_FAN3 Speed 841 RPM
CPU FAN Speed 992 RPM
OPT1_FAN Speed 0 RPM
OPT2_FAN Speed 0 RPM
OPT3_FAN Speed 0 RPM
Power_FAN Speed 0 RPM
+12 Voltage 12.152 V
+3.3 Voltage 3.328 V
+5 Voltage 5.112 V
CPUPLL Voltage 1.528 V
DDR Voltage 2.110 V
Dram VTT Volt 1.052 V
NB11 Voltage 1.118 V
SB11 Voltage 1.124 V
SB15 Voltage 1.501 V
Vcore Voltage 1.078 V
VTTCPU Voltage 1.124 V
CPU Temperature 153.7 C
MB Temperature 154.4 C
Chassis FAN Speed 1539 RPM
CPU FAN Speed 1538 RPM
Power FAN Speed 1540 RPM
+12V Voltage 1.541 V
+3.3V Voltage 1.543 V
+5V Voltage 1.542 V
Vcore Voltage 1.536 V
==========================================================================
------[ 1 SMBus detected ]------
------[ SMBus #0 ]------
SMBus Type : Intel ICH
SMBus Port : 0400
Can Have SPD: Yes
Scan Type : Full
------[ SMBus Device B00-D20 ]------
0000 FF 80 17 7F FF FF FF FF FF FF FF FF FF FF FF FF ...\x7f............
0010 00 FF FF FF FF FF FF FF FF B0 FF FF FF FF FF FF ................
0020 20 00 FF FF FF 20 B2 FF FF FF FF FF FF FF FF FF .... ..........
0030 FF FF FF FF FF FF FF FF 74 03 FF FF FF FF FF FF ........t.......
0040 FF FF FF FF FF FF FF FF FF FF 64 FF FF FF FF FF ..........d.....
0050 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0060 FF FF FF FF FF FF FF FF FF FF 2C FF FF FF FF FF ..........,.....
0070 FF FF FF FF FF FF FF FF 02 08 00 00 FF FF 80 FF ................
0080 00 FF FF FF FF FF FF FF FF FF FF 52 04 FF FF FF ...........R....
0090 FF FF FF FF FF FF 80 FF FF 41 98 01 FF FF FF FF .........A......
00A0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00B0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00C0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00D0 00 03 72 72 03 02 01 33 43 00 00 00 00 28 00 07 ..rr...3C....(..
00E0 00 00 10 0C 10 10 17 10 10 10 10 FF 07 FF 00 00 ................
00F0 FF 0A FF FF FF 01 02 FF FF 00 00 50 FF FF FF FF ...........P....
------[ SMBus Device B00-D20 ]------
0000 FFFF 3780 6617 FF7F FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0010 7700 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 54B0 FFFF FFFF FFFF FFFF FFFF FFFF
0020 7620 0000 FFFF FFFF FFFF 0020 00B2 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0030 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0074 0003 FFFF FFFF FFFF FFFF FFFF FFFF
0040 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0064 FFFF FFFF FFFF FFFF FFFF
0050 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0060 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 012C FFFF FFFF FFFF FFFF FFFF
0070 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF ED02 0208 3500 5E00 FFFF FFFF 1982 FFFF
0080 DE00 FFFF FFFF FFFF FFFF FFFF FFFF D35E FFFF FFFF FFFF 0052 D304 FFFF FFFF FFFF
0090 FFFF FFFF FFFF FFFF FFFF FFFF D353 FFFF FFFF 8641 3298 9701 FFFF FFFF FFFF FFFF
00A0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00B0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00C0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00D0 FA00 9803 7572 1E72 5803 3402 8001 BA35 BA43 C000 7D00 1600 0000 B328 D600 A807
00E0 1B00 7000 BD10 820C C010 AB10 0317 7D10 3A10 5110 EC10 FFFF F407 FFFF 3700 5C00
00F0 4AFF E40A FFFF FFFF FFFF 7E01 0002 FFFF FFFF 8300 3E00 E250 B0FF FFFF FFFF FFFF
------[ SMBus Device B00-D30 ]------
0000 03 C0 40 00 00 40 00 00 FF FF FF FF FF FF FF FF ..@..@..........
0010 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0020 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0030 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0040 FF C0 40 00 00 40 00 00 FF FF FF FF FF FF FF FF ..@..@..........
0050 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0060 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0070 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0080 FF C0 40 00 00 40 00 00 FF FF FF FF FF FF FF FF ..@..@..........
0090 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00A0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00B0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00C0 FF C0 40 00 00 40 00 00 FF FF FF FF FF FF FF FF ..@..@..........
00D0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00E0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00F0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
------[ SMBus Device B00-D30 ]------
0000 C003 40C0 0040 0000 FF00 FF40 FF00 FF00 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0010 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0020 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0030 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0040 C0FF 40C0 0040 0000 FF00 FF40 FF00 FF00 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0050 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0060 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0070 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0080 C0FF 40C0 0040 0000 FF00 FF40 FF00 FF00 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0090 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00A0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00B0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00C0 C0FF 40C0 0040 0000 FF00 FF40 FF00 FF00 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00D0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00E0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00F0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
------[ SMBus Device B00-D32 ]------
0000 03 40 40 00 00 40 00 00 FF FF FF FF FF FF FF FF .@@..@..........
0010 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0020 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0030 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0040 FF 40 40 00 00 40 00 00 FF FF FF FF FF FF FF FF .@@..@..........
0050 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0060 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0070 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0080 FF 40 40 00 00 40 00 00 FF FF FF FF FF FF FF FF .@@..@..........
0090 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00A0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00B0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00C0 FF 40 40 00 00 40 00 00 FF FF FF FF FF FF FF FF .@@..@..........
00D0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00E0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00F0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
------[ SMBus Device B00-D32 ]------
0000 4003 4040 0040 0000 FF00 FF40 FF00 FF00 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0010 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0020 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0030 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0040 40FF 4040 0040 0000 FF00 FF40 FF00 FF00 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0050 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0060 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0070 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0080 40FF 4040 0040 0000 FF00 FF40 FF00 FF00 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0090 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00A0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00B0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00C0 40FF 4040 0040 0000 FF00 FF40 FF00 FF00 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00D0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00E0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00F0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
------[ SMBus Device B00-D33 ]------
0000 03 C0 C0 00 00 C0 00 00 FF FF FF FF FF FF FF FF ................
0010 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0020 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0030 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0040 FF C0 C0 00 00 C0 00 00 FF FF FF FF FF FF FF FF ................
0050 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0060 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0070 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0080 FF C0 C0 00 00 C0 FF 00 FF FF FF FF FF FF FF FF ................
0090 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00A0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00B0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00C0 FF C0 C0 00 00 C0 00 00 FF FF FF FF FF FF FF FF ................
00D0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00E0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00F0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
------[ SMBus Device B00-D33 ]------
0000 C003 C0C0 00C0 0000 FF00 FFC0 FF00 FF00 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0010 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0020 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0030 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0040 C0FF C0C0 00C0 0000 FF00 FFC0 FF00 FF00 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0050 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0060 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0070 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0080 C0FF C0C0 00C0 0000 FF00 FFC0 FF00 FF00 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0090 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00A0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00B0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00C0 C0FF C0C0 00C0 0000 FF00 FFC0 FF00 FF00 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00D0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00E0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00F0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
------[ SMBus Device B00-D35 ]------
0000 03 C0 C0 00 00 C0 00 00 FF FF FF FF FF FF FF FF ................
0010 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0020 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0030 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0040 FF C0 C0 00 00 C0 00 00 FF FF FF FF FF FF FF FF ................
0050 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0060 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0070 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0080 FF C0 C0 00 00 C0 00 00 FF FF FF FF FF FF FF FF ................
0090 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00A0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00B0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00C0 FF C0 C0 00 00 C0 00 00 FF FF FF FF FF FF FF FF ................
00D0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00E0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00F0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
------[ SMBus Device B00-D35 ]------
0000 C003 C0C0 00C0 0000 FF00 FFC0 FF00 FF00 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0010 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0020 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0030 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0040 C0FF C0C0 00C0 0000 FF00 FFC0 FF00 FF00 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0050 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0060 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0070 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0080 C0FF C0C0 00C0 0000 FF00 FFC0 FF00 FF00 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0090 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00A0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00B0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00C0 C0FF C0C0 00C0 0000 FF00 FFC0 FF00 FF00 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00D0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00E0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00F0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
------[ SMBus Device B00-D38 ]------
0000 FF 55 A0 55 74 72 55 3F FF FF FF 01 00 FF FF FF .U.UtrU?........
0010 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0020 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0030 00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0040 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0050 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0060 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0070 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0080 FF FF FF FF FF FF FF FF FF FF 69 43 44 00 56 A1 ..........iCD.V.
0090 36 04 3E 08 64 04 DD 05 FF 05 64 04 1C 04 5E 04 6.>.d.....d...^.
00A0 00 00 E8 03 23 03 A0 02 FF FF FF FF 04 FF FF FF ....#...........
00B0 FF 9A 00 03 16 00 00 03 05 FF FF FF FF FF FF FF ................
00C0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00D0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00E0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00F0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
------[ SMBus Device B00-D38 ]------
0000 FFFF 5555 A0A0 5555 7474 7272 5555 3F3F FFFF FFFF FFFF 0101 0000 FFFF FFFF FFFF
0010 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0020 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0030 0000 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0040 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0050 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0000 FFFF FFFF FFFF FFFF FFFF FFFF 0064
0060 FFFF FFFF FFFF FFFF 00DD FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0005 FFFF FFFF FFFF
0070 FFFF 0005 FFFF 001C FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0080 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 4343 4444 0000 0026 A1A1
0090 FFFF 0404 3E3E 00A0 FFFF 0202 DDDD FFFF F8F8 FFFF 5E5E 0404 FFFF 0404 5E5E 0404
00A0 0000 0003 E8E8 0000 FFFF 0000 A0A0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00B0 FFFF 0000 FFFF 0303 1616 0000 0000 0303 0505 FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00C0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00D0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00E0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00F0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
------[ SMBus Device B00-D40 ]------
0000 FF FF FF FF FF FF FF 00 00 00 00 FF FF FF FF FF ................
0010 FF 50 46 FF FF FF FF FF FF FF FF FF FF FF FF FF .PF.............
0020 FF FF FF FF FF FF FF 00 FF FF FF FF FF FF FF FF ................
0030 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0040 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0050 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0060 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0070 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0080 FF FF FF FF FF FF FF FF FF FF 50 CC 29 00 56 EC ..........P.).V.
0090 00 00 00 00 00 00 4A 03 FF FF FF FF FF FF FF FF ......J.........
00A0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00B0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00C0 28 36 33 2A 28 26 1A FF FF FF FF FF FF FF FF 00 (63*(&..........
00D0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00E0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00F0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
------[ SMBus Device B00-D40 ]------
0000 FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0000 0000 0000 0000 FFFF FFFF FFFF FFFF FFFF
0010 FFFF 5050 4646 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0020 FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0000 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0030 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0040 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0050 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0060 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0070 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0080 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 5050 CCCC 2929 0000 5656 ECEC
0090 0000 0000 0000 0000 0000 0000 4949 0303 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00A0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00B0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00C0 2828 3636 3333 2A2A 2828 2626 1A1A FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0000
00D0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00E0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
00F0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
------[ SMBus Device B00-D44 ]------
0000 00 00 00 04 00 00 00 00 00 16 10 17 07 12 07 09 ................
0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
------[ SMBus Device B00-D44 ]------
0000 FF00 FF00 FF00 FF04 FF00 FF00 FF00 FF00 FF00 FF16 FF10 FF17 FF07 FF12 FF07 FF09
0010 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
0020 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
0030 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
0040 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
0050 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
0060 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
0070 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
0080 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
0090 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
00A0 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
00B0 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
00C0 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
00D0 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
00E0 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
00F0 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
------[ SMBus Device B00-D50 ]------
0000 80 08 08 0E 0A 61 40 00 05 25 40 00 82 08 00 00 .....a@..%@.....
0010 0C 08 30 03 02 00 03 37 50 00 00 32 1E 32 2D 01 ..0....7P..2.2-.
0020 17 25 05 12 3C 1E 1E 00 06 39 7F 80 14 1E 00 00 .%..<....9\x7f.....
0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 12 0D ................
0040 7F 7F 9E 00 00 00 00 00 01 43 4D 32 58 32 30 34 \x7f\x7f.......CM2X204
0050 38 2D 38 35 30 30 43 35 44 20 20 20 20 00 00 00 8-8500C5D ...
0060 00 00 00 6D 56 4E B1 21 FF FF FF FF FF FF FF FF ...mVN.!........
0070 FF FF FF FF 8C 50 01 20 25 1E 20 25 25 1C 3C 29 .....P. %. %%.<)
0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
------[ SMBus Device B00-D52 ]------
0000 80 08 08 0E 0A 61 40 00 05 25 40 00 82 08 00 00 .....a@..%@.....
0010 0C 08 30 03 02 00 03 37 50 00 00 32 1E 32 2D 01 ..0....7P..2.2-.
0020 17 25 05 12 3C 1E 1E 00 06 39 7F 80 14 1E 00 00 .%..<....9\x7f.....
0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 12 0D ................
0040 7F 7F 9E 00 00 00 00 00 01 43 4D 32 58 32 30 34 \x7f\x7f.......CM2X204
0050 38 2D 38 35 30 30 43 35 44 20 20 20 20 00 00 00 8-8500C5D ...
0060 00 00 00 6D 56 4E B1 21 FF FF FF FF FF FF FF FF ...mVN.!........
0070 FF FF FF FF 8C 50 01 20 25 1E 20 25 25 1C 3C 29 .....P. %. %%.<)
0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
------[ Chips Found ]------
B00-D20: Analog Devices ASP0800 (Asus EPU2)
[-- 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
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol
2009-06-24 9:47 [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol Konstantin Kletschke
` (12 preceding siblings ...)
2009-07-12 22:11 ` Marco Chiappero
@ 2009-08-08 22:13 ` Reimundo Heluani
2009-08-09 1:58 ` Reimundo Heluani
14 siblings, 0 replies; 16+ messages in thread
From: Reimundo Heluani @ 2009-08-08 22:13 UTC (permalink / raw)
To: lm-sensors
On Wed, 24 Jun 2009 14:32:45 +0200, Konstantin Kletschke wrote:
>
> Exactly I am running 2.6.30-rc7, the guy reporting this in the ubuntu
> forum did this februrary 28th, so on another kernel.
I think that was probably me :)
>> Would you be able and willing to apply a patch to your kernel and
>> rebuild it, if I come up with something?
I know this is a (not so) old thread, but where can I find the Kernel patches from
2.6.29.5 to 2.6.30.4 for support with the 283667hg-A chipset in an asus
P5q3-Deluxe? I can't really run 2.6.30.4 as it kills audio which I can't
solve apparently, so I'd like to patch my 2.6.29 kernel directly.
By the way, my readings on the p5q3 when running 2.6.30.4 also can't be
correct:
w83667hg-isa-0290
Adapter: ISA adapter
in0: +1.11 V (min = +0.00 V, max = +1.74 V)
in1: +1.75 V (min = +0.79 V, max = +0.05 V) ALARM
in2: +3.36 V (min = +0.53 V, max = +0.51 V) ALARM
in3: +3.33 V (min = +2.14 V, max = +0.51 V) ALARM
in4: +1.70 V (min = +0.82 V, max = +0.51 V) ALARM
in5: +2.04 V (min = +0.27 V, max = +0.51 V) ALARM
in7: +3.41 V (min = +2.05 V, max = +0.22 V) ALARM
in8: +3.30 V (min = +0.64 V, max = +0.02 V) ALARM
fan1: 760 RPM (min = 2410 RPM, div = 8) ALARM
fan2: 1298 RPM (min = 2636 RPM, div = 16) ALARM
fan3: 0 RPM (min = 0 RPM, div = 128) ALARM
fan4: 753 RPM (min = 12980 RPM, div = 8) ALARM
fan5: 756 RPM (min = 981 RPM, div = 8) ALARM
temp1: +37.0°C (high = +102.0°C, hyst = +19.0°C) sensor thermistor
temp2: +25.5°C (high = +80.0°C, hyst = +75.0°C) sensor = diode
temp3: +21.0°C (high = +80.0°C, hyst = +75.0°C) sensor thermistor
cpu0_vid: +1.163 V
I'm also more than willing to try whatever you want on this machine :)
Thanks
R.
> > time understanding how this can happen at all. Does writing to pwm3
> > change the value of pwm2, too?
>
> echo into pwm1 changes nothing:
>
> > cat pwm1 pwm2 pwm3
> 77
> 55
> 78
> > echo "99" >> pwm1
> > cat pwm1 pwm2 pwm3
> 77
> 55
> 78
>
> echo into pwm2 changes pwm1:
>
> > cat pwm1 pwm2 pwm3
> 77
> 55
> 78
> > echo "99" >> pwm2
> > cat pwm1 pwm2 pwm3
> 99
> 55
> 78
>
> echo into pwm3 changes pwm3:
>
> > cat pwm1 pwm2 pwm3
> 99
> 55
> 78
> > echo "100" >> pwm3
> > cat pwm1 pwm2 pwm3
> 99
> 55
> 100
This is all very confusing, I admit. I would like you to unload the
w83627ehf driver and try to read from / write to the chip directly. For
this you'll need the isadump and isaset tools (part of lm-sensors.)
Registers pwm1, pwm2 and pwm3 are at 0x01, 0x03 and 0x11, respectively.
You can see their raw value using the following command (as root):
isaset 0x295 0x296 0x4e 0 # set bank to 0
isadump 0x295 0x296
Then I would like you to write to each register, then check the result.
The value written doesn't matter as long as it is different from the
current value of all 3 registers in question:
isaset 0x295 0x296 0x01 0xaa
isadump 0x295 0x296
isaset 0x295 0x296 0x03 0xbb
isadump 0x295 0x296
isaset 0x295 0x296 0x11 0xcc
isadump 0x295 0x296
If this works fine then that would be a bug in the driver. If it
doesn't, that would be a hardware bug.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol
2009-06-24 9:47 [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol Konstantin Kletschke
` (13 preceding siblings ...)
2009-08-08 22:13 ` Reimundo Heluani
@ 2009-08-09 1:58 ` Reimundo Heluani
14 siblings, 0 replies; 16+ messages in thread
From: Reimundo Heluani @ 2009-08-09 1:58 UTC (permalink / raw)
To: lm-sensors
On Sat, 2009-08-08 at 15:13 -0700, Reimundo Heluani wrote:
> On Wed, 24 Jun 2009 14:32:45 +0200, Konstantin Kletschke wrote:
>
> >
> > Exactly I am running 2.6.30-rc7, the guy reporting this in the ubuntu
> > forum did this februrary 28th, so on another kernel.
>
> I think that was probably me :)
>
>
> >> Would you be able and willing to apply a patch to your kernel and
> >> rebuild it, if I come up with something?
>
> I know this is a (not so) old thread, but where can I find the Kernel patches from
> 2.6.29.5 to 2.6.30.4 for support with the 283667hg-A chipset in an asus
> P5q3-Deluxe? I can't really run 2.6.30.4 as it kills audio which I can't
> solve apparently, so I'd like to patch my 2.6.29 kernel directly.
Ok so I just changed the driver in the 2.6.29.5 kernel and compiled it
as a module again, now I can see the fan readings on 2.6.29 but I wander
if this message should be scary or not:
[ 28.246687] w83627ehf: Found W83667HG chip at 0x290
[ 28.246854] ACPI: I/O resource w83627ehf [0x295-0x296] conflicts with
ACPI region HWRE [0x290-0x299]
[ 28.247106] ACPI: Device needs an ACPI driver
Thanks,
R.
>
> By the way, my readings on the p5q3 when running 2.6.30.4 also can't be
> correct:
>
> w83667hg-isa-0290
> Adapter: ISA adapter
> in0: +1.11 V (min = +0.00 V, max = +1.74 V)
> in1: +1.75 V (min = +0.79 V, max = +0.05 V) ALARM
> in2: +3.36 V (min = +0.53 V, max = +0.51 V) ALARM
> in3: +3.33 V (min = +2.14 V, max = +0.51 V) ALARM
> in4: +1.70 V (min = +0.82 V, max = +0.51 V) ALARM
> in5: +2.04 V (min = +0.27 V, max = +0.51 V) ALARM
> in7: +3.41 V (min = +2.05 V, max = +0.22 V) ALARM
> in8: +3.30 V (min = +0.64 V, max = +0.02 V) ALARM
> fan1: 760 RPM (min = 2410 RPM, div = 8) ALARM
> fan2: 1298 RPM (min = 2636 RPM, div = 16) ALARM
> fan3: 0 RPM (min = 0 RPM, div = 128) ALARM
> fan4: 753 RPM (min = 12980 RPM, div = 8) ALARM
> fan5: 756 RPM (min = 981 RPM, div = 8) ALARM
> temp1: +37.0°C (high = +102.0°C, hyst = +19.0°C) sensor > thermistor
> temp2: +25.5°C (high = +80.0°C, hyst = +75.0°C) sensor = diode
> temp3: +21.0°C (high = +80.0°C, hyst = +75.0°C) sensor > thermistor
> cpu0_vid: +1.163 V
>
> I'm also more than willing to try whatever you want on this machine :)
>
> Thanks
>
> R.
>
> > > time understanding how this can happen at all. Does writing to pwm3
> > > change the value of pwm2, too?
> >
> > echo into pwm1 changes nothing:
> >
> > > cat pwm1 pwm2 pwm3
> > 77
> > 55
> > 78
> > > echo "99" >> pwm1
> > > cat pwm1 pwm2 pwm3
> > 77
> > 55
> > 78
> >
> > echo into pwm2 changes pwm1:
> >
> > > cat pwm1 pwm2 pwm3
> > 77
> > 55
> > 78
> > > echo "99" >> pwm2
> > > cat pwm1 pwm2 pwm3
> > 99
> > 55
> > 78
> >
> > echo into pwm3 changes pwm3:
> >
> > > cat pwm1 pwm2 pwm3
> > 99
> > 55
> > 78
> > > echo "100" >> pwm3
> > > cat pwm1 pwm2 pwm3
> > 99
> > 55
> > 100
>
> This is all very confusing, I admit. I would like you to unload the
> w83627ehf driver and try to read from / write to the chip directly. For
> this you'll need the isadump and isaset tools (part of lm-sensors.)
>
> Registers pwm1, pwm2 and pwm3 are at 0x01, 0x03 and 0x11, respectively.
> You can see their raw value using the following command (as root):
>
> isaset 0x295 0x296 0x4e 0 # set bank to 0
> isadump 0x295 0x296
>
> Then I would like you to write to each register, then check the result.
> The value written doesn't matter as long as it is different from the
> current value of all 3 registers in question:
>
> isaset 0x295 0x296 0x01 0xaa
> isadump 0x295 0x296
>
> isaset 0x295 0x296 0x03 0xbb
> isadump 0x295 0x296
>
> isaset 0x295 0x296 0x11 0xcc
> isadump 0x295 0x296
>
> If this works fine then that would be a bug in the driver. If it
> doesn't, that would be a hardware bug.
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2009-08-09 1:58 UTC | newest]
Thread overview: 16+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-06-24 9:47 [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol Konstantin Kletschke
2009-06-24 11:08 ` Luca Tettamanti
2009-06-24 12:10 ` Jean Delvare
2009-06-24 12:32 ` Konstantin Kletschke
2009-06-24 12:34 ` Konstantin Kletschke
2009-06-24 12:38 ` Luca Tettamanti
2009-06-24 12:53 ` Jean Delvare
2009-06-24 13:44 ` Konstantin Kletschke
2009-06-24 14:23 ` Konstantin Kletschke
2009-06-25 8:31 ` Jean Delvare
2009-06-25 9:21 ` Jean Delvare
2009-06-29 8:44 ` Konstantin Kletschke
2009-06-29 8:47 ` Konstantin Kletschke
2009-07-12 22:11 ` Marco Chiappero
2009-08-08 22:13 ` Reimundo Heluani
2009-08-09 1:58 ` Reimundo Heluani
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.