Hi Jean!

2007/5/14, Jean Delvare <[EMAIL PROTECTED]>:

> Sure. On 2.6.21.1:
>
> via686a-isa-6000
> Adapter: ISA adapter
> CPU core:  +1.63 V  (min =  +0.06 V, max =  +3.10 V)
> +2.5V:     +2.45 V  (min =  +0.06 V, max =  +3.10 V)
> I/O:       +3.52 V  (min =  +3.12 V, max =  +3.45 V)   ALARM
> +5V:       +5.05 V  (min =  +4.73 V, max =  +5.20 V)
> +12V:     +12.30 V  (min = +11.35 V, max = +12.48 V)
> CPU Fan:     0 RPM  (min = 42187 RPM, div = 2)
> P/S Fan:  2657 RPM  (min = 42187 RPM, div = 2)          ALARM

Hint: increase the fan clock dividers to 4.


I've not found an obvious way to set it in sensors.conf. Could you
point me to some doumentation, thanks.

> while on 2.6.22-rc1:
>
> via686a-i2c-9191-6000
>  ERROR: Can't get adapter or algorithm?!?

Ah, interesting. Could it be that the gnome applet quits because it
fails to get the adapter name? That wouldn't be very smart, but that's
possible.

Just for the record. Does not quit. It displays on the panel "Chip not found.".

This is a side effect of an i2c-core cleanup. This is already fixed in
lm_sensors 2.10.3 (libsensors.so.3.1.3). Care to give it a try and
confirm it fixes the problem? Note that it might be a bit tricky to get
the gnome applet to use your own libsensors rather than the system one.
You might need to set the LD_LIBRARY_PATH environment variable before
the applet starts, or something similar.

Luckily the 2.10.3 lm-sensors version is on unstable. The backport to
Debian Etch was straightforward. Now the applet works again! And the
P/S fan indicator (you may have noted that showed 0 in the 2.6.22-rc1
case) works too. Many thanks ;-).

Is this new version required only for the via686 chip or should be a
general advise for Debian Etch users to upgrade to lm-sensors >=
2.10.3 for kernels >= 2.6.22?


   ~ Antonio
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to