i2c-ali1535.c:548: warning: initialization from incompatible pointer

i2c-ali1535.c:548: warning: initialization from incompatible pointer

[Florian Effenberger]

Hello list,

When compiling lm_sensors 2.9.0 with gcc 2.95.4, I receive the following 
error:

gcc  -DMODVERSIONS -include 
/root/linux-2.4.28/include/linux/modversions.h -D__KERNEL__ -DMODULE 
-DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include 
-I/usr/local/include  -I/root/linux-2.4.28/include -nostdinc -I 
/usr/lib/gcc-lib/i386-linux/2.95.4/include  -Wall -O2  -c 
kernel/busses/i2c-ali1535.c -o kernel/busses/i2c-ali1535.o
kernel/busses/i2c-ali1535.c:547: unknown field `inc_use' specified in 
initializer
kernel/busses/i2c-ali1535.c:548: unknown field `dec_use' specified in 
initializer
kernel/busses/i2c-ali1535.c:548: warning: initialization from 
incompatible pointer type
make: *** [kernel/busses/i2c-ali1535.o] Fehler 1

Have filed this as ticket 1857.

Florian

i2c-ali1535.c:548: warning: initialization from incompatible

[Florian Effenberger]

Hi Jean,

> Oops, my bad. You'd have to copy the file to /usr/local/include/linux,
> not /usr/local/include (please delete the one you copied there). While
> you're at it, you could copy kernel/i2c-algo-bit.h too, since some bus
> drivers in lm_sensors need it.

you were partially right. ;-) By doing

cp kernel/*.h /usr/local/include/linux

it worked, the two files you mentioned were not enough. I checked my 
/usr/local/include/linux before, and it looked like

drwxr-sr-x    2 root     staff        4096 26. Nov 13:06 .
drwxrwsr-x   14 root     staff        4096  2. Jan 10:31 ..
-rw-r--r--    1 root     staff        2197 26. Nov 13:03 i2c-algo-bit.h
-rw-r--r--    1 root     staff        3140 26. Nov 13:03 i2c-algo-biths.h
-rw-r--r--    1 root     staff        1867 26. Nov 13:03 i2c-algo-pcf.h
-rw-r--r--    1 root     staff       12372 26. Nov 13:06 i2c-dev.h
-rw-r--r--    1 root     staff       23343 26. Nov 13:03 i2c.h
-rw-r--r--    1 root     staff       13330 26. Nov 13:03 i2c-id.h
-rw-r--r--    1 root     staff       19385 26. Nov 13:03 i2c-proc.h
-rw-r--r--    1 root     staff       53108 26. Nov 13:06 sensors.h

so the files were old. Might this be a bug in i2c 2.9.0, that it does 
not copy files? I definitely issued a make install and received a 
"Successful"...

However, somethings seems to be wrong nontheless. A "sensors" delivers me:

CPU Fan:  5818 RPM  (min = 84375 RPM, div = 8)          ALARM

look at the min RPM count...

Thanks
Florian

i2c-ali1535.c:548: warning: initialization from incompatible

[Jean Delvare]

> > If you did, please try to manually copy kernel/i2c.h from i2c 2.9.0
> > to /usr/local/include and see if it helps.
> 
> myhost:~/i2c-2.9.0# cp kernel/i2c.h /usr/local/include/
> myhost:~# cd ../lm_sensors-2.9.0/
> myhost:~/lm_sensors-2.9.0# make all
> gcc  -DMODVERSIONS -include 
> /root/linux-2.4.28/include/linux/modversions.h -D__KERNEL__ -DMODULE 
> -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include 
> -I/usr/local/include  -I/root/linux-2.4.28/include -nostdinc -I 
> /usr/lib/gcc-lib/i386-linux/2.95.4/include  -Wall -O2  -c 
> kernel/busses/i2c-ali1535.c -o kernel/busses/i2c-ali1535.o
> kernel/busses/i2c-ali1535.c:547: unknown field `inc_use' specified in 
> initializer
> kernel/busses/i2c-ali1535.c:548: unknown field `dec_use' specified in 
> initializer
> kernel/busses/i2c-ali1535.c:548: warning: initialization from 
> incompatible pointer type
> make: *** [kernel/busses/i2c-ali1535.o] Fehler 1
> 
> Doesn't work. :-(

Oops, my bad. You'd have to copy the file to /usr/local/include/linux,
not /usr/local/include (please delete the one you copied there). While
you're at it, you could copy kernel/i2c-algo-bit.h too, since some bus
drivers in lm_sensors need it.

-- 
Jean Delvare
http://khali.linux-fr.org/

i2c-ali1535.c:548: warning: initialization from incompatible

[Jean Delvare]

Hi Florian,

>When compiling lm_sensors 2.9.0 with gcc 2.95.4, I receive the following
>error:
>
>gcc  -DMODVERSIONS -include
>/root/linux-2.4.28/include/linux/modversions.h -D__KERNEL__ -DMODULE
>-DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include
>-I/usr/local/include  -I/root/linux-2.4.28/include -nostdinc -I
>/usr/lib/gcc-lib/i386-linux/2.95.4/include  -Wall -O2  -c
>kernel/busses/i2c-ali1535.c -o kernel/busses/i2c-ali1535.o
>kernel/busses/i2c-ali1535.c:547: unknown field `inc_use' specified in
>initializer
>kernel/busses/i2c-ali1535.c:548: unknown field `dec_use' specified in
>initializer
>kernel/busses/i2c-ali1535.c:548: warning: initialization from
>incompatible pointer type
>make: *** [kernel/busses/i2c-ali1535.o] Fehler 1

Did you install i2c 2.9.0? lm_sensors 2.9.0 needs it.

If you did, please try to manually copy kernel/i2c.h from i2c 2.9.0 to
/usr/local/include and see if it helps.

Thanks,
--
Jean Delvare

i2c-ali1535.c:548: warning: initialization from incompatible

[Florian Effenberger]

Hi Jean,

> Do you have "set fanN_min" lines at all in your via686a-* section? They
> are commented out by default, maybe you simply need to uncomment them
> and run "sensors -s".

I added

     set fan1_min 5000
     set fan2_min 5000

and it looked like

via686a-isa-0c00
Adapter: ISA adapter
CPU core:  +1.80 V  (min =  +0.06 V, max =  +3.10 V)
+2.5V:     +1.10 V  (min =  +2.37 V, max =  +2.62 V)   ALARM
I/O:       +3.36 V  (min =  +3.13 V, max =  +3.45 V)
+5V:       +5.23 V  (min =  +4.51 V, max =  +5.50 V)
+12V:     +11.89 V  (min = +10.81 V, max = +13.20 V)
CPU Fan:  5818 RPM  (min = 4963 RPM, div = 8)          ALARM
P/S Fan:     0 RPM  (min = 4963 RPM, div = 8)
SYS Temp:  +26.0?C  (high =   +45?C, hyst =   +40?C)
CPU Temp:  +21.8?C  (high =   +60?C, hyst =   +55?C)
SBr Temp:  +22.3?C  (high =   +65?C, hyst =   +60?C)

(even with 3.0.7). The interesting thing is, even when I comment that 
out again, re-run sensors -s and then sensors, still the 4963 minimum is 
there!

> You would delete libsensors.so.3.0.7 and then run "ldconfig", which will
> update the link properly.

I did

# mv libsensors.so.3.0.7 /root
# ldconfig
# ls /usr/local/lib/libsens* -ld

/usr/local/lib/libsensors.a
/usr/local/lib/libsensors.so -> libsensors.so.3
/usr/local/lib/libsensors.so.2 -> libsensors.so.2.0.1
/usr/local/lib/libsensors.so.2.0.1
/usr/local/lib/libsensors.so.3 -> libsensors.so.3.0.6
/usr/local/lib/libsensors.so.3.0.0
/usr/local/lib/libsensors.so.3.0.1
/usr/local/lib/libsensors.so.3.0.2
/usr/local/lib/libsensors.so.3.0.3
/usr/local/lib/libsensors.so.3.0.4
/usr/local/lib/libsensors.so.3.0.5
/usr/local/lib/libsensors.so.3.0.6

but the problem still persists:

# sensors -s
# sensors

via686a-isa-0c00
Adapter: ISA adapter
CPU core:  +1.80 V  (min =  +0.06 V, max =  +3.10 V)
+2.5V:     +1.10 V  (min =  +2.37 V, max =  +2.62 V)   ALARM
I/O:       +3.36 V  (min =  +3.13 V, max =  +3.45 V)
+5V:       +5.18 V  (min =  +4.51 V, max =  +5.50 V)
+12V:     +11.95 V  (min = +10.81 V, max = +13.20 V)
CPU Fan:  5818 RPM  (min = 84375 RPM, div = 8)          ALARM
P/S Fan:     0 RPM  (min = 1222 RPM, div = 8)
SYS Temp:  +26.4?C  (high =   +45?C, hyst =   +40?C)
CPU Temp:  +21.8?C  (high =   +60?C, hyst =   +55?C)
SBr Temp:  +22.3?C  (high =   +65?C, hyst =   +60?C)

Maybe 2.9.0 needs a newer gcc version? I only have 2.95.4

> In the meantime, I will try to reproduce the problem on my own system.

Thanks for your help! ;-)

Florian

i2c-ali1535.c:548: warning: initialization from incompatible

[Florian Effenberger]

Hi,

> Note that you don't really need i2c-viapro in this case (and it would
> even cause trouble if you were running a 2.6 kernel).

It was the proposal of sensors-detect some versions ago, so I inserted 
it. ;-) Kernel is still 2.4.

> Could you try not to run it after a cold reboot, and see what the
> initial value is? This will help us understand whether reading the value
> or writing the value is the problem.

I did a warm reboot (init 6; have no method of doing a cold reboot right 
now as this is a remote machine).

myhost:~# sensors
via686a-isa-0c00
Adapter: ISA adapter
CPU core:  +1.80 V  (min =  +0.06 V, max =  +3.10 V)
+2.5V:     +1.10 V  (min =  +0.06 V, max =  +3.10 V)
I/O:       +3.36 V  (min =  +0.08 V, max =  +4.14 V)
+5V:       +5.23 V  (min =  +0.13 V, max =  +6.44 V)
+12V:     +11.95 V  (min =  +0.32 V, max = +15.60 V)
CPU Fan:  5818 RPM  (min = 84375 RPM, div = 8)          ALARM
P/S Fan:     0 RPM  (min = 1222 RPM, div = 8)
SYS Temp:  +27.2?C  (high =   +45?C, hyst =   +40?C)
CPU Temp:  +21.6?C  (high =   +60?C, hyst =   +55?C)
SBr Temp:  +22.3?C  (high =   +65?C, hyst =   +60?C)

myhost:~# sensors -s
myhost:~# sensors
via686a-isa-0c00
Adapter: ISA adapter
CPU core:  +1.80 V  (min =  +0.06 V, max =  +3.10 V)
+2.5V:     +1.10 V  (min =  +2.37 V, max =  +2.62 V)
I/O:       +3.36 V  (min =  +3.13 V, max =  +3.45 V)
+5V:       +5.23 V  (min =  +4.51 V, max =  +5.50 V)
+12V:     +11.95 V  (min = +10.81 V, max = +13.20 V)
CPU Fan:  5443 RPM  (min = 84375 RPM, div = 8)          ALARM
P/S Fan:     0 RPM  (min = 1222 RPM, div = 8)
SYS Temp:  +27.3?C  (high =   +45?C, hyst =   +40?C)
CPU Temp:  +21.6?C  (high =   +60?C, hyst =   +55?C)
SBr Temp:  +22.3?C  (high =   +65?C, hyst =   +60?C)

> You can still try but I doubt it'll help. There is no reason why a
> working configuration file would suddenly stop working.

A newly installed sensors.conf didn't help.

> What you could do OTOH is manually delete the latest version of
> libsensors (3.0.7) in /usr/local/lib, so that the previous one is used
> instead (that would be 3.0.6 if you installed lm_sensors 2.8.8 before).
> If the readings are back to normal, then it has to be a library bug.

Here are the relevant files in my /usr/local/lib directory.
/usr/local/lib/libsensors.a
/usr/local/lib/libsensors.so -> libsensors.so.3
/usr/local/lib/libsensors.so.2 -> libsensors.so.2.0.1
/usr/local/lib/libsensors.so.2.0.1
/usr/local/lib/libsensors.so.3 -> libsensors.so.3.0.7
/usr/local/lib/libsensors.so.3.0.0
/usr/local/lib/libsensors.so.3.0.1
/usr/local/lib/libsensors.so.3.0.2
/usr/local/lib/libsensors.so.3.0.3
/usr/local/lib/libsensors.so.3.0.4
/usr/local/lib/libsensors.so.3.0.5
/usr/local/lib/libsensors.so.3.0.6
/usr/local/lib/libsensors.so.3.0.7

Shall I simply delete libsensors.so.3.0.7? Or do I have to change the 
libsensors.so.3 symlink as well?

Thanks
Florian

i2c-ali1535.c:548: warning: initialization from incompatible

[Florian Effenberger]

Hi there,

> Did you install i2c 2.9.0? lm_sensors 2.9.0 needs it.

I did and the install went smooth.

> If you did, please try to manually copy kernel/i2c.h from i2c 2.9.0 to
> /usr/local/include and see if it helps.

myhost:~/i2c-2.9.0# cp kernel/i2c.h /usr/local/include/
myhost:~# cd ../lm_sensors-2.9.0/
myhost:~/lm_sensors-2.9.0# make all
gcc  -DMODVERSIONS -include 
/root/linux-2.4.28/include/linux/modversions.h -D__KERNEL__ -DMODULE 
-DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include 
-I/usr/local/include  -I/root/linux-2.4.28/include -nostdinc -I 
/usr/lib/gcc-lib/i386-linux/2.95.4/include  -Wall -O2  -c 
kernel/busses/i2c-ali1535.c -o kernel/busses/i2c-ali1535.o
kernel/busses/i2c-ali1535.c:547: unknown field `inc_use' specified in 
initializer
kernel/busses/i2c-ali1535.c:548: unknown field `dec_use' specified in 
initializer
kernel/busses/i2c-ali1535.c:548: warning: initialization from 
incompatible pointer type
make: *** [kernel/busses/i2c-ali1535.o] Fehler 1

Doesn't work. :-(

Florian

i2c-ali1535.c:548: warning: initialization from incompatible

[Florian Effenberger]

Hi Jean,

> Yes, this is a bug, that will affect almost all users. My bad :(

No problem, thanks for confirming it so fast. :-)

> Which chip is this?

via686a-isa-0c00 (according to sensors). The modules I load are

	i2c-viapro
	i2c-isa
	via686a

> Did you run "sensors -s"?

Yes.

> Does the alarm wear off if you run "sensors" again?

No, it stays at this very high RPM value.

> You might simply need to set the min RPM count through the
> /etc/sensors.conf file and run "sensors -s" afterwards.

I have not changed sensors.conf for quite a while and the problems 
started to appear in 2.9.0. In 2.8.x, everything was fine.

I have checked on another system that had the some compile problems I 
fixed the same way (copying *.h to /usr/local/include/linux). It has 
w83627hf-isa-0290 as chip and also some weird values:

fan1:     5720 RPM  (min = 21093 RPM, div = 2)
fan2:        0 RPM  (min = 84375 RPM, div = 2)

What could that be? Maybe I shall erase the sensors.conf and let it 
re-install it?

Thanks
Florian

i2c-ali1535.c:548: warning: initialization from incompatible

[Jean Delvare]

> I did a warm reboot (init 6; have no method of doing a cold reboot
> right  now as this is a remote machine).
> 
> myhost:~# sensors
> via686a-isa-0c00
> Adapter: ISA adapter
> CPU core:  +1.80 V  (min =  +0.06 V, max =  +3.10 V)
> +2.5V:     +1.10 V  (min =  +0.06 V, max =  +3.10 V)
> I/O:       +3.36 V  (min =  +0.08 V, max =  +4.14 V)
> +5V:       +5.23 V  (min =  +0.13 V, max =  +6.44 V)
> +12V:     +11.95 V  (min =  +0.32 V, max = +15.60 V)
> CPU Fan:  5818 RPM  (min = 84375 RPM, div = 8)          ALARM
> P/S Fan:     0 RPM  (min = 1222 RPM, div = 8)
> SYS Temp:  +27.2?C  (high =   +45?C, hyst =   +40?C)
> CPU Temp:  +21.6?C  (high =   +60?C, hyst =   +55?C)
> SBr Temp:  +22.3?C  (high =   +65?C, hyst =   +60?C)
> 
> myhost:~# sensors -s
> myhost:~# sensors
> via686a-isa-0c00
> Adapter: ISA adapter
> CPU core:  +1.80 V  (min =  +0.06 V, max =  +3.10 V)
> +2.5V:     +1.10 V  (min =  +2.37 V, max =  +2.62 V)
> I/O:       +3.36 V  (min =  +3.13 V, max =  +3.45 V)
> +5V:       +5.23 V  (min =  +4.51 V, max =  +5.50 V)
> +12V:     +11.95 V  (min = +10.81 V, max = +13.20 V)
> CPU Fan:  5443 RPM  (min = 84375 RPM, div = 8)          ALARM
> P/S Fan:     0 RPM  (min = 1222 RPM, div = 8)
> SYS Temp:  +27.3?C  (high =   +45?C, hyst =   +40?C)
> CPU Temp:  +21.6?C  (high =   +60?C, hyst =   +55?C)
> SBr Temp:  +22.3?C  (high =   +65?C, hyst =   +60?C)

Do you have "set fanN_min" lines at all in your via686a-* section? They
are commented out by default, maybe you simply need to uncomment them
and run "sensors -s".

> Here are the relevant files in my /usr/local/lib directory.
> /usr/local/lib/libsensors.a
> /usr/local/lib/libsensors.so -> libsensors.so.3
> /usr/local/lib/libsensors.so.2 -> libsensors.so.2.0.1
> /usr/local/lib/libsensors.so.2.0.1
> /usr/local/lib/libsensors.so.3 -> libsensors.so.3.0.7
> /usr/local/lib/libsensors.so.3.0.0
> /usr/local/lib/libsensors.so.3.0.1
> /usr/local/lib/libsensors.so.3.0.2
> /usr/local/lib/libsensors.so.3.0.3
> /usr/local/lib/libsensors.so.3.0.4
> /usr/local/lib/libsensors.so.3.0.5
> /usr/local/lib/libsensors.so.3.0.6
> /usr/local/lib/libsensors.so.3.0.7
> 
> Shall I simply delete libsensors.so.3.0.7? Or do I have to change the 
> libsensors.so.3 symlink as well?

You would delete libsensors.so.3.0.7 and then run "ldconfig", which will
update the link properly.

In the meantime, I will try to reproduce the problem on my own system.

-- 
Jean Delvare
http://khali.linux-fr.org/

i2c-ali1535.c:548: warning: initialization from incompatible

[Jean Delvare]

> you were partially right. ;-) By doing
> cp kernel/*.h /usr/local/include/linux
> it worked, the two files you mentioned were not enough.
> (...)
> Might this be a bug in i2c 2.9.0, that it does
> not copy files? I definitely issued a make install and received a
> "Successful"...

Yes, this is a bug, that will affect almost all users. My bad :(

> However, somethings seems to be wrong nontheless. A "sensors" delivers me:
>
> CPU Fan:  5818 RPM  (min = 84375 RPM, div = 8)          ALARM
>
> look at the min RPM count...

Which chip is this?

Did you run "sensors -s"?

Does the alarm wear off if you run "sensors" again?

You might simply need to set the min RPM count through the
/etc/sensors.conf file and run "sensors -s" afterwards.

--
Jean Delvare

i2c-ali1535.c:548: warning: initialization from incompatible

[Jean Delvare]

> > Which chip is this?
> 
> via686a-isa-0c00 (according to sensors). The modules I load are
> 
> 	i2c-viapro
> 	i2c-isa
> 	via686a

Note that you don't really need i2c-viapro in this case (and it would
even cause trouble if you were running a 2.6 kernel).


> > Did you run "sensors -s"?
> 
> Yes.

Could you try not to run it after a cold reboot, and see what the
initial value is? This will help us understand whether reading the value
or writing the value is the problem.

> > You might simply need to set the min RPM count through the
> > /etc/sensors.conf file and run "sensors -s" afterwards.
> 
> I have not changed sensors.conf for quite a while and the problems 
> started to appear in 2.9.0. In 2.8.x, everything was fine.

OK, so this is definitely a new bug. This is strange, I can't remember
of anything similar.

> I have checked on another system that had the some compile problems I 
> fixed the same way (copying *.h to /usr/local/include/linux). It has 
> w83627hf-isa-0290 as chip and also some weird values:
> 
> fan1:     5720 RPM  (min = 21093 RPM, div = 2)
> fan2:        0 RPM  (min = 84375 RPM, div = 2)

And that's a different chip. This would suggest that the bug is in
libsensors and not in the drivers.

> What could that be? Maybe I shall erase the sensors.conf and let it 
> re-install it?

You can still try but I doubt it'll help. There is no reason why a
working configuration file would suddenly stop working.

What you could do OTOH is manually delete the latest version of
libsensors (3.0.7) in /usr/local/lib, so that the previous one is used
instead (that would be 3.0.6 if you installed lm_sensors 2.8.8 before).
If the readings are back to normal, then it has to be a library bug.

Thanks,
-- 
Jean Delvare
http://khali.linux-fr.org/

i2c-ali1535.c:548: warning: initialization from incompatible

[Jean Delvare]

> I added
> 
>      set fan1_min 5000
>      set fan2_min 5000
> 
> and it looked like
> 
> via686a-isa-0c00
> Adapter: ISA adapter
> CPU core:  +1.80 V  (min =  +0.06 V, max =  +3.10 V)
> +2.5V:     +1.10 V  (min =  +2.37 V, max =  +2.62 V)   ALARM
> I/O:       +3.36 V  (min =  +3.13 V, max =  +3.45 V)
> +5V:       +5.23 V  (min =  +4.51 V, max =  +5.50 V)
> +12V:     +11.89 V  (min = +10.81 V, max = +13.20 V)
> CPU Fan:  5818 RPM  (min = 4963 RPM, div = 8)          ALARM
> P/S Fan:     0 RPM  (min = 4963 RPM, div = 8)
> SYS Temp:  +26.0?C  (high =   +45?C, hyst =   +40?C)
> CPU Temp:  +21.8?C  (high =   +60?C, hyst =   +55?C)
> SBr Temp:  +22.3?C  (high =   +65?C, hyst =   +60?C)

So it works as expected.

> (even with 3.0.7). The interesting thing is, even when I comment that 
> out again, re-run sensors -s and then sensors, still the 4963 minimum
> is  there!

This is expected. "set" lines are only used when they are there.
"Missing" lines simply have no effect with "sensors -s", they are not
magically replaced by any kind of default.

> # mv libsensors.so.3.0.7 /root
> # ldconfig
> # ls /usr/local/lib/libsens* -ld
> 
> /usr/local/lib/libsensors.a
> /usr/local/lib/libsensors.so -> libsensors.so.3
> /usr/local/lib/libsensors.so.2 -> libsensors.so.2.0.1
> /usr/local/lib/libsensors.so.2.0.1
> /usr/local/lib/libsensors.so.3 -> libsensors.so.3.0.6
> /usr/local/lib/libsensors.so.3.0.0
> /usr/local/lib/libsensors.so.3.0.1
> /usr/local/lib/libsensors.so.3.0.2
> /usr/local/lib/libsensors.so.3.0.3
> /usr/local/lib/libsensors.so.3.0.4
> /usr/local/lib/libsensors.so.3.0.5
> /usr/local/lib/libsensors.so.3.0.6
> 
> but the problem still persists:
> 
> # sensors -s
> # sensors
> 
> via686a-isa-0c00
> Adapter: ISA adapter
> CPU core:  +1.80 V  (min =  +0.06 V, max =  +3.10 V)
> +2.5V:     +1.10 V  (min =  +2.37 V, max =  +2.62 V)   ALARM
> I/O:       +3.36 V  (min =  +3.13 V, max =  +3.45 V)
> +5V:       +5.18 V  (min =  +4.51 V, max =  +5.50 V)
> +12V:     +11.95 V  (min = +10.81 V, max = +13.20 V)
> CPU Fan:  5818 RPM  (min = 84375 RPM, div = 8)          ALARM
> P/S Fan:     0 RPM  (min = 1222 RPM, div = 8)
> SYS Temp:  +26.4?C  (high =   +45?C, hyst =   +40?C)
> CPU Temp:  +21.8?C  (high =   +60?C, hyst =   +55?C)
> SBr Temp:  +22.3?C  (high =   +65?C, hyst =   +60?C)
> 
> Maybe 2.9.0 needs a newer gcc version? I only have 2.95.4

The first test proves that the values are read and written properly, so
the only problem here is the default value, which is either set by your
BIOS or not set at all. There's not much lm_sensors could have done bad.

Can you check in sensors.conf if you explicitely set the fan clock
dividers to 8? I think that the default is 2. Maybe the divider change
affected the min value in an unexpected way.

Also, you said that previous versions of lm_sensors would yield a
different default min value. What was that value? What was the value of
the dividers?

> > In the meantime, I will try to reproduce the problem on my own
> > system.
> 
> Thanks for your help! ;-)

No problem. I just checked and can't see the problem you report on my
system. However it might not be relevant since my via686a chip is *not*
connected on my motherboard.

-- 
Jean Delvare
http://khali.linux-fr.org/

i2c-ali1535.c:548: warning: initialization from incompatible

[Florian Effenberger]

Hi Jean,

> The first test proves that the values are read and written properly, so
> the only problem here is the default value, which is either set by your
> BIOS or not set at all. There's not much lm_sensors could have done bad.

That still does not explain why it worked in 2.8.8. ;-)

> Can you check in sensors.conf if you explicitely set the fan clock
> dividers to 8? I think that the default is 2. Maybe the divider change
> affected the min value in an unexpected way.

Sorry, I don't understand. What exactly should I do?

> Also, you said that previous versions of lm_sensors would yield a
> different default min value. What was that value? What was the value of
> the dividers?

Unfortunately, I don't know, I don't have a system with the old version 
ready. :-( I never changed anything in sensors.conf, so the default 
values from older versions were there.

Thanks
Florian