Sure. Btw, the chip module itself is called via686a, no such thing as i2c-via686 ;)
Yes, sorry I meant via686a, only bus drivers has i2c- as prefix.
I should admit I also only know that for very few time. Actually 2.6 kernels refuse to let two modules accessing the same chip. It's a new feature that was not present in 2.4 kernels. The lm-sensors team thought that they can add a fix for that but it seems to be a little tricky, that's why the sensors-detect script has not been modified. They are still working on a fix.marla:/home/smokey# lsmod | grep i2c i2c_isa 1856 0 i2c_sensor 3456 1 via686a i2c_dev 10208 0 i2c_core 22736 4 via686a,i2c_isa,i2c_sensor,i2c_dev
It s worth noting that I had no idea that via686a was incompatible with the i2c-viapro, to the point where it would render the chip unreadable until the next reboot. The fact that sensors-detect thinks it can read via686a readings over SMBus is slightly misleading.
Anyway the latest lm-sensors includes:
- An entry about that into the FAQ
- A warning in sensors-detect
- An hotplug blacklist for i2c-viapro, so that modules won't get loaded automatically.
Long story short, as long as I don't load i2c-viapro, I'm safe. However,I am not sure about that (I don't have such a system), but I think you don't need to reboot to get your sensors working. Removing both i2c-viapro and via686a modules and reloading only via686a should work.
That's strange. Was your configuration file for a very old version of lm-sensors? Did you get it from Debian or from another distribution.with the same sensors.conf as in my old config, I get completely different min/max settings, which is a bit weird.
And did you run sensors -s to set the min/max values?
Thanks for your time et tr�s bonne ann�e ;)
Bonne ann�e !
Aur�lien
-- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `- people.debian.org/~aurel32 | www.aurel32.net
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
