[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: lm-sensors



hi ya frederik

you probably want to see the cpu temp measurements ???

its at /proc/sys/dev/sensors/<*sis5595*>/temp1

you can see all the stuff its recording in the /proc tree

and if you're nuts like me.... i run a cron job to copy the cpu 
temperature every 5 minutes ....copy it into a web directory that
i can casually browse to see what the temp did over the past day/night etc
	- for the 1U boxes i running

if your cpu/chassis fans is a 3-wire fan ( with a tach )..gues yu
can also write a perl script to send an alarm when the fan dies

- consider yourself lucky if your motherboard's sensors is detected
  by lm-sensors

have fun
alvin
http://www.Linux-Consulting.com/1U/LCD/	- lm-sensor stuff + Lcd display


On Tue, 5 Sep 2000, Frederik wrote:

> I've installed lm-sensors using apt-get install lm-sensors-source,
> recompiled the kernel, installed the new kernel with dpkg -i, installed
> the 2 created .debs (i2c and lm-sensors) and rebooted.
> I ran sensors-detect, and modified /etc/modules:
> 
> i2c-isa
> sis5595
> 
> This is what sensors report:
> frederik@maui:/lahaina$ sensors
> sis5595-isa-0290
> Adapter: ISA adapter
> Algorithm: ISA algorithm
> VCore 1:   +2.04 V  (min =  +2.84 V, max =  +3.45 V)   ALARM
> VCore 2:   +1.96 V  (min =  +2.68 V, max =  +3.26 V)   ALARM
> +3.3V:     +1.23 V  (min =  +2.97 V, max =  +3.63 V)   ALARM
> +5V:       +0.82 V  (min =  +3.78 V, max =  +4.62 V)   ALARM
> fan1:        0 RPM  (min = 3000 RPM, div = 2)          ALARM
> fan2:        0 RPM  (min = 3000 RPM, div = 2)          ALARM
> temp:     +127 C     (limit = +60 C,  hysteresis = +50 C) 
> alarms:   Board temperature input (usually LM75 chips) ALARM
> 
> Funny, but not what i had in mind of course. Through the bios at bootup,
> i can see the correct temperature...
> Any ideas what i should change? I have a sis 5595 chip, and run woody.
> 
> 
> -- 
> Unsubscribe?  mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
> 



Reply to: