Hi Stefan, On Sat, 11 Aug 2007 00:29:36 +0200, Stefan Richter wrote: > Jean Delvare wrote: > > I just tried 2.6.23-rc2 on a system where I use the w83627ehf hardware > > monitoring driver, and was not able to reproduce the problem you > > described. Fan speeds are reported properly for me. Which I kind of > > expected, as I tested all my w83627ehf patches on this system before > > submitting them. > > Thanks that you are still after it. I was busy with other stuff the > whole week, hence no git bisect result from me yet. > > > Please try using sensors instead of ksensors, and confirm that the > > behavior is the same. I'd like to rule out a problem in ksensors > > itself. sensors will also report the fan divs, this is a useful > > information given the problem you have. > > # sensors > w83627ehf-isa-0290 > Adapter: ISA adapter > VCore: +0.95 V (min = +0.00 V, max = +1.74 V) > in1: +12.30 V (min = +1.64 V, max = +3.22 V) ALARM > AVCC: +3.28 V (min = +1.89 V, max = +1.94 V) ALARM > 3VCC: +3.26 V (min = +0.18 V, max = +0.72 V) ALARM > in4: +1.58 V (min = +0.57 V, max = +0.90 V) ALARM > in5: +1.70 V (min = +0.41 V, max = +1.19 V) ALARM > in6: +3.43 V (min = +0.31 V, max = +3.05 V) ALARM > VSB: +3.25 V (min = +0.37 V, max = +3.01 V) ALARM > VBAT: +3.18 V (min = +3.94 V, max = +0.74 V) ALARM > in9: +1.88 V (min = +0.79 V, max = +1.40 V) ALARM > Case Fan: 0 RPM (min = 753 RPM, div = 128) ALARM > CPU Fan: 88 RPM (min = 659 RPM, div = 64) ALARM > Aux Fan: 0 RPM (min = 10546 RPM, div = 128) ALARM > fan5: 0 RPM (min = 753 RPM, div = 128) ALARM > Sys Temp: +44 C (high = -5 C, hyst = -34 C) ALARM > CPU Temp: +38.0 C (high = +80.0 C, hyst = +75.0 C) > AUX Temp: +43.5 C (high = +80.0 C, hyst = +75.0 C) > > coretemp-isa-0000 > Adapter: ISA adapter > > coretemp-isa-0001 > Adapter: ISA adapter Note: a more recent version of lm-sensors would give you additional temperature values here. > > (The aux fan and fan5 are not connected.) > > > Your original post suggests that the fan speed is supposed to change > > depending on the system load? Or temperature? Please describe the > > mechanism used to achieve this. Could it be that this mechanism isn't > > working properly, and the reported (low) speeds are actually true? > > The motherboard controls the CPU fan and I believe also the case fan, > probably based on temperatures. (The manual is buried somewhere and > MSI's download site is down right in this moment.) I would like to know what it is doing exactly, and how. Can this feature be disabled? If the BIOS accesses the W83627EHG chip in our back, this can cause lots of trouble, such as what you are seeing. > The low speeds or the dividers incorrect. I'll reboot in a minute into > 2.6.22(-rc5) and post the "sensors" output. > > > What fan inputs are used by your CPU and system fans? "sensors > > -c /dev/null" will tell. > > ... > fan1: 484 RPM (min = 12053 RPM, div = 16) ALARM > fan2: 89 RPM (min = 659 RPM, div = 64) ALARM > fan3: 0 RPM (min = 10546 RPM, div = 128) ALARM > fan5: 0 RPM (min = 1506 RPM, div = 128) ALARM > ... Note: 89 RPM with div=64 corresponds to the same register value as 1424 RPM with div=4 (as shown in your next post). As if the chip and the driver didn't agree on what the actual divider is. > Hmm, interesting. When I now re-run sensors I get > ... > Case Fan: 484 RPM (min = 12053 RPM, div = 16) ALARM > CPU Fan: 89 RPM (min = 659 RPM, div = 64) ALARM > Aux Fan: 0 RPM (min = 10546 RPM, div = 128) ALARM > fan5: 0 RPM (min = 1506 RPM, div = 128) ALARM > ... > > (I'm still in 2.6.23-rc2. Ksensors picked the 484 RPM of the case fan > up too, and that's most certainly the correct speed. Just the CPU fan's > speed is still wrong; or rather its divider should be 16 rather than 64.) Divider should be 4,not 16, methinks. You can dump the chip registers using the following command: isadump 0x295 0x296
