All of lore.kernel.org
 help / color / mirror / Atom feed
From: Reimundo Heluani <rheluani@gmail.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] HowTo Asus P5Q, W83667HG vs ATK0110 - fancontrol
Date: Sun, 09 Aug 2009 01:58:08 +0000	[thread overview]
Message-ID: <1249783088.3433.2.camel@campari.homeip.net> (raw)
In-Reply-To: <20090624094735.GA16670@punzenstreichler.doom>

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

      parent reply	other threads:[~2009-08-09  1:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 message]

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=1249783088.3433.2.camel@campari.homeip.net \
    --to=rheluani@gmail.com \
    --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.