Dominik Geyer | 1 Jun 12:15 2008
Picon
Picon

Re: [Bug?] W83697: Broken readings for fan speed 10% of the time

Bruno Prémont <bonbons <at> linux-vserver.org> writes:

> 
> On a Commell LE-365 I get readings for fan speed that are broken about
> 10% of the time.
> The board has a Winbond W83697 chip (I can't check the exact chip name
> on the board as it's hidden by a heatsink, the photo from Commell, as
> as well as the manual indicate a HG, the kenrel reports:
>   [    3.572831] w83627hf: Found W83697HF chip at 0x290
>   [    3.572831] WDT driver for the Winbond(TM) W83627HF/THF/HG Super I/O 
chip initialising.
>   [    3.572831] w83627hf/thf/hg WDT: Watchdog already running. Resetting 
timeout to 60 sec
>   [    3.572831] w83627hf/thf/hg WDT: initialized. timeout=60 sec 
(nowayout=0)
> )

Hm, thats strange. I've got a VIA-EPIA-EK8000EG with a W83697HG as well and 
didn't have any wrong readings with fan_input (2.6.25.3 kernel).

By the way: I noticed that you are using the w83627hf_wdt in your 
kernel-config. Did you already test the watchdog? On my board the w83627hf_wdt 
loads correctly but does not work. I'm using the w83697_wdt instead. 

--
Dominik Geyer

_______________________________________________
lm-sensors mailing list
lm-sensors <at> lm-sensors.org
(Continue reading)

James Dietrich | 2 Jun 01:45 2008
Picon

sensors3.conf for Intel DG35EC motherboard

I recently purchased an Intel DG35EC motherboard, and am trying to
figure out the hardware monitoring capability included on that
motherboard. It seems that the hardware is being detected ok; I just
need help setting up sensors3.conf properly.

Here is the output from near the end of sensors-detect:
Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `w83627ehf' (should be inserted):
  Detects correctly:
  * ISA bus, address 0x6e0
    Chip `Winbond W83627DHG Super IO Sensors' (confidence: 9)

Driver `coretemp' (should be inserted):
  Detects correctly:
  * Chip `Intel Core family thermal sensor' (confidence: 9)

So I compiled those drivers into my kernel, and dmesg reports this:
coretemp coretemp.0: Using relative temperature scale!
coretemp coretemp.1: Using relative temperature scale!
w83627ehf: Found W83627DHG chip at 0x6e0

I have checked on the motherboard, and there is a Winbond 83627DHG-A
chip on there.

I have successfully adjusted the Fans section, but I'm having trouble
with the Voltage and Temperature readings. Running 'sensors' gives
values, but they don't seem to be right.

(Continue reading)

simon | 2 Jun 07:00 2008
Picon

Re: Reported fan speed oscillates 730 RPM -> 337500 RPM/675000 RPM

Hi Jean, 
Thank you.

Your analysis appears absolutely correct. The fan is speed controlled
and problem is pronounced when it is running slowly. Normal speed is
around 750-800rpm. The problem appears to diminish as the speed rises;
above ~1000 rpm, the readings appear stable.

I would assume that Gigabyte have used the automatic control facilities
of the it8718 chip. Where is this going to be set up - from the bios? Is
there anywhere in the linux system that this can be done? Or is it all
automatic.

At any rate the thing seems to work, so I don't really want to play with
it (let sleeping dogs lie etc). It's just the oscillating reading is a
bit annoying. Wouldn't there be anyway of filtering out such values in
lm-sensors? (Maybe a configuration setting)

Many thanks,

Simon

On Sat, 2008-05-31 at 23:18 +0200, Jean Delvare wrote:
> Hi Simon,
> 
> On Wed, 28 May 2008 09:39:45 +0200, simon wrote:
> > The following output shows periodic output from sensors for my CPU
> > cooler over a short period.
> > 
> > The value continually oscillates between a real value (around 720-750
(Continue reading)

Jean Delvare | 2 Jun 10:10 2008

Re: Reported fan speed oscillates 730 RPM -> 337500 RPM/675000 RPM

Hi Simon,

On Mon, 02 Jun 2008 07:00:19 +0200, simon wrote:
> Your analysis appears absolutely correct. The fan is speed controlled
> and problem is pronounced when it is running slowly. Normal speed is
> around 750-800rpm. The problem appears to diminish as the speed rises;
> above ~1000 rpm, the readings appear stable.
>  
> I would assume that Gigabyte have used the automatic control facilities
> of the it8718 chip. Where is this going to be set up - from the bios? Is
> there anywhere in the linux system that this can be done? Or is it all
> automatic.

Yes, most probably the BIOS is setting things up at boot time. The
Linux it87 driver doesn't let the user control the settings yet. That's
somewhere deep in my to-do list... All you can do is disable the
automatic control mode by writing 0 to pwmN_enable sysfs files - but I
doubt you want to do that other than for testing purposes.

You might also be able to mitigate the problem by changing the
frequency of the PWM signal (sysfs files pwmN_freq, since kernel
2.6.21). I guess that lower frequencies should help the chip monitor
the speed.

> At any rate the thing seems to work, so I don't really want to play with
> it (let sleeping dogs lie etc). It's just the oscillating reading is a
> bit annoying. Wouldn't there be anyway of filtering out such values in
> lm-sensors? (Maybe a configuration setting)

This has been discussed many times but was never implemented. I'm not
(Continue reading)

Jean Delvare | 2 Jun 11:18 2008

Re: LM93, info about tempX parameters in a Supermicro X6DH8-XG2

Hi Santi,

On Wed, 28 May 2008 10:52:35 +0200, Santi Saez wrote:
> I want to monitor some temperatures in a server with a Supermicro  
> X6DH8-XG2 motherboard with 2 Xeon processors, running Linux 2.6.25.4  
> and lm-sensors v3.0.2, in a Debian Etch box.
> 
> LM93 and PC87427 Super I/O sensor chips are detected, according to  
> the wiki only LM93 is fully supported by lm-sensors, in PC87427 fan  
> monitoring only is available, this is an example of the command output:

Did you load the pc87427 driver nevertheless? If you did, what did it
say? I have patches improving this driver and I am looking for testers.

> ======================================================================== 
> # sensors
> lm93-i2c-0-2e
> Adapter: SMBus I801 adapter at 1100
> in1:         +0.94 V  (min =  +0.83 V, max =  +1.02 V)
> in2:         +0.94 V  (min =  +0.83 V, max =  +1.02 V)
> in3:         +0.94 V  (min =  +0.83 V, max =  +1.02 V)
> in4:         +1.21 V  (min =  +1.08 V, max =  +1.32 V)
> in5:         +1.49 V  (min =  +1.35 V, max =  +1.66 V)
> in6:         +1.50 V  (min =  +1.35 V, max =  +1.66 V)
> in7:         +1.35 V  (min =  +1.02 V, max =  +1.54 V)
> in8:         +1.36 V  (min =  +1.02 V, max =  +1.54 V)
> in9:         +3.35 V  (min =  +2.97 V, max =  +3.64 V)
> in10:        +5.02 V  (min =  +4.47 V, max =  +5.49 V)
> in11:        +0.00 V  (min =  +2.25 V, max =  +2.76 V)
> in12:        +1.79 V  (min =  +1.77 V, max =  +2.17 V)
(Continue reading)

Jean Delvare | 2 Jun 12:32 2008

Re: [Bug?] W83697: Broken readings for fan speed 10% of the time

Hi Bruno,

On Sat, 31 May 2008 22:03:39 +0200, Bruno Prémont wrote:
> On a Commell LE-365 I get readings for fan speed that are broken about
> 10% of the time.
> The board has a Winbond W83697 chip (I can't check the exact chip name
> on the board as it's hidden by a heatsink, the photo from Commell, as
> as well as the manual indicate a HG, the kenrel reports:
>   [    3.572831] w83627hf: Found W83697HF chip at 0x290
>   [    3.572831] WDT driver for the Winbond(TM) W83627HF/THF/HG Super I/O chip initialising.
>   [    3.572831] w83627hf/thf/hg WDT: Watchdog already running. Resetting timeout to 60 sec
>   [    3.572831] w83627hf/thf/hg WDT: initialized. timeout=60 sec (nowayout=0)
> )
> 
> Below a sample (reformatted) output of
>   while sleep 1; do
>     date;
>     cat /sys/class/hwmon/hwmon0/device/fan1_input;
>   done
> :
> Sat May 31 21:11:23 CEST 2008    2070
> Sat May 31 21:11:24 CEST 2008    2070
> Sat May 31 21:11:25 CEST 2008    2070
> Sat May 31 21:11:26 CEST 2008    2070
> Sat May 31 21:11:27 CEST 2008    2070
> Sat May 31 21:11:28 CEST 2008    2070
> Sat May 31 21:11:29 CEST 2008    2057
> Sat May 31 21:11:30 CEST 2008    2057
> Sat May 31 21:11:31 CEST 2008    2070
> Sat May 31 21:11:32 CEST 2008    2070
(Continue reading)

Warrick Lacey | 2 Jun 20:54 2008

adm1021 in 2.6.9 question..

Hello,

We have recently transitioned for a 2.4.x based kernel to the 2.6.9 
kernel and I'm trying to get the onboard temperature sensor working 
under the 2.6.9 kernel. Under the 2.4.x kernel, we needed i2c-core, 
i2c-dev, i2c-proc, dmi-scan, i2c-piix4 and adm1021.

We have not changed hardware (basically a 6U VR7 board), will/should the 
adm1021 device be an ISA device or an I2C device?.

I see that the adm1021 driver is now part of the kernel in 2.6.x but 
what steps to I have to take to get the kernel to recognize and access 
this device under 2.6.9.

Thanks for any help.
Warrick Lacey

Attachment (wlacey.vcf): text/x-vcard, 325 bytes
_______________________________________________
lm-sensors mailing list
lm-sensors <at> lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
Jean Delvare | 2 Jun 21:02 2008

Re: adm1021 in 2.6.9 question..

Hi Warrick,

On Mon, 02 Jun 2008 14:54:45 -0400, Warrick Lacey wrote:
> We have recently transitioned for a 2.4.x based kernel to the 2.6.9 
> kernel and I'm trying to get the onboard temperature sensor working 
> under the 2.6.9 kernel. Under the 2.4.x kernel, we needed i2c-core, 
> i2c-dev, i2c-proc, dmi-scan, i2c-piix4 and adm1021.
> 
> We have not changed hardware (basically a 6U VR7 board), will/should the 
> adm1021 device be an ISA device or an I2C device?.

I2C.

> I see that the adm1021 driver is now part of the kernel in 2.6.x but 
> what steps to I have to take to get the kernel to recognize and access 
> this device under 2.6.9.

Exactly the same as you were doing before:

$ modprobe i2c-piix4
$ modprobe adm1021
$ sensors

--

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors <at> lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
(Continue reading)

Bruno Prémont | 2 Jun 21:09 2008

Re: [Bug?] W83697: Broken readings for fan speed 10% of the time

Hi Jean,

On Mon, 02 June 2008 Jean Delvare <khali <at> linux-fr.org> wrote:
> Hi Bruno,
> 
> On Sat, 31 May 2008 22:03:39 +0200, Bruno Prémont wrote:
> > On a Commell LE-365 I get readings for fan speed that are broken
> > about 10% of the time.
> > The board has a Winbond W83697 chip (I can't check the exact chip
> > name on the board as it's hidden by a heatsink, the photo from
> > Commell, as as well as the manual indicate a HG, the kenrel reports:
> >   [    3.572831] w83627hf: Found W83697HF chip at 0x290
> >   [    3.572831] WDT driver for the Winbond(TM) W83627HF/THF/HG
> > Super I/O chip initialising. [    3.572831] w83627hf/thf/hg WDT:
> > Watchdog already running. Resetting timeout to 60 sec
> > [    3.572831] w83627hf/thf/hg WDT: initialized. timeout=60 sec
> > (nowayout=0) )
> > 
> > Below a sample (reformatted) output of
> >   while sleep 1; do
> >     date;
> >     cat /sys/class/hwmon/hwmon0/device/fan1_input;
> >   done
> > :
> > Sat May 31 21:11:23 CEST 2008    2070
> > <snip>
> > Sat May 31 21:11:34 CEST 2008      -1
> > <snip>
> > Sat May 31 21:12:14 CEST 2008  337500
> > <snip>
(Continue reading)

Jean Delvare | 2 Jun 21:35 2008

Re: [Bug?] W83697: Broken readings for fan speed 10% of the time

On Mon, 2 Jun 2008 21:09:41 +0200, Bruno Prémont wrote:
> On Mon, 02 June 2008 Jean Delvare <khali <at> linux-fr.org> wrote:
> > Is the fan's speed controlled in any way, either by the W83697HG chip,
> > or maybe it is a self-regulated fan? Just check if the fan's speed
> > increases with the temperature (i.e. with CPU load).
> 
> Yes, the fan has a built-in thermal sensor and regulates it's speed
> based on temperature.
> It's running either at its lowest speed or the speed just above.

Note that I've never seen this behavior on self-regulated fans... But I
guess it depends on the implementation.

> > (...)
> > One patch you may want to apply it this one:
> >   http://lists.lm-sensors.org/pipermail/lm-sensors/2008-May/023189.html
> > It will let you switch the W83697HG chip from automatic fan speed
> > control to manual control and back - might be useful to investigate
> > the issue you have.
> 
> I will try this one, maybe the board is capable of doing speed control
> but its not implemented in vanilla driver.

It is. The w83627hf driver can do manual fan speed control for a very
long time. What it is missing is support for automatic fan speed
control.

> Until now setting pwm_enable to any values and changing PWM value did
> not influence fan speed

(Continue reading)


Gmane