Hi I've got a Linux distro called Linux SME, have installed a system monitoring software called sme7admin: http://wiki.contribs.org/Sme7admin I've been working on smeadmin to get the CPU, M/B and HDD temps displayed on sme7admin. am able to get the network data details etc but sensor info has been a struggle. Got it sorted last week and correct CPU was being displayed- confirmed via BIOS output. For whatever reason the CPU temp is now being displayed as 70 degrees Centigrade. Bios shows 45 degrees centigrade. this is displayed via sme7admin and "sensors" display. Unsure where to start. Any suggestions appreciated as my admin email box is clogged with full of alerts. login as: root root at 192.168.0.254's password: Last login: Fri Apr 17 22:27:30 2009 from 192.168.0.153 [root at server ~]# ls /media/ cdrom floppy NO_NAME usbdisk [root at server ~]# ls /media/NO_NAME/ [root at server ~]# ls /media/usbdisk/ [root at server ~]# ls /media/NO_NAME/ [root at server ~]# ls /media/NO_NAME/ [root at server ~]# sen -bash: sen: command not found [root at server ~]# root -bash: root: command not found [root at server ~]# 1cheon -bash: 1cheon: command not found [root at server ~]# [root at server ~]# sensors w83697hf-isa-0290 Adapter: ISA adapter VCore: +1.58 V (min = +1.71 V, max = +1.89 V) +3.3V: +3.26 V (min = +3.14 V, max = +3.46 V) +5V: +4.95 V (min = +4.73 V, max = +5.24 V) ALARM +12V: +11.92 V (min = +10.82 V, max = +13.19 V) -12V: -14.91 V (min = -13.18 V, max = -10.88 V) -5V: -7.71 V (min = -5.25 V, max = -4.75 V) V5SB: +5.24 V (min = +4.73 V, max = +5.24 V) VBat: +0.00 V (min = +2.40 V, max = +3.60 V) fan1: 2721 RPM (min = 337500 RPM, div = 2) fan2: 0 RPM (min = 3169 RPM, div = 2) temp1: +70?C (high = +64?C, hyst = +4?C) sensor = thermistor temp2: +36.0?C (high = +80?C, hyst = +75?C) sensor = thermistor alarms: beep_enable: Sound alarm disabled eeprom-i2c-0-51 Adapter: SiS96x SMBus adapter at 0x0c00 Memory type: DDR SDRAM DIMM Memory size (MB): 512 eeprom-i2c-0-50 Adapter: SiS96x SMBus adapter at 0x0c00 Memory type: DDR SDRAM DIMM Memory size (MB): 512 [root at server ~]# sensors-detect This program will help you determine which I2C/SMBus modules you need to load to use lm_sensors most effectively. You need to have i2c and lm_sensors installed before running this program. Also, you need to be `root', or at least have access to the /dev/i2c-* files, for most things. If you have patched your kernel and have some drivers built in, you can safely answer NO if asked to load some modules. In this case, things may seem a bit confusing, but they will still work. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. We can start with probing for (PCI) I2C or SMBus adapters. You do not need any special privileges for this. Do you want to probe now? (YES/no): y Probing for PCI bus adapters... Use driver `i2c-sis96x' for device 00:02.1: Silicon Integrated Systems SMBus Controller Probe succesfully concluded. We will now try to load each adapter module in turn. Module `i2c-sis96x' already loaded. If you have undetectable or unsupported adapters, you can have them scanned by manually loading the modules before running this script. To continue, we need module `i2c-dev' to be loaded. If it is built-in into your kernel, you can safely skip this. i2c-dev is not loaded. Do you want to load it now? (YES/no): y Module loaded succesfully. We are now going to do the adapter probings. Some adapters may hang halfway through; we can't really help that. Also, some chips will be double detected; we choose the one with the highest confidence value in that case. If you found that the adapter hung after probing a certain address, you can specify that address to remain unprobed. That often includes address 0x69 (clock chip). Next adapter: SiS96x SMBus adapter at 0x0c00 (Algorithm unavailable) Do you want to scan it? (YES/no/selectively): y Client found at address 0x08 Client found at address 0x10 Client found at address 0x31 Client at address 0x50 can not be probed - unload all client drivers first! Client at address 0x51 can not be probed - unload all client drivers first! Client found at address 0x69 Some chips are also accessible through the ISA bus. ISA probes are typically a bit more dangerous, as we have to write to I/O ports to do this. This is usually safe though. Do you want to scan the ISA bus? (YES/no): ISA Probing for `National Semiconductor LM78' Trying address 0x0290... Failed! Probing for `National Semiconductor LM78-J' Trying address 0x0290... Failed! Probing for `National Semiconductor LM79' Trying address 0x0290... Failed! Probing for `Winbond W83781D' Trying address 0x0290... Failed! Probing for `Winbond W83782D' Trying address 0x0290... Failed! Probing for `Winbond W83627HF' Trying address 0x0290... Failed! Probing for `Winbond W83697HF' Trying address 0x0290... Success! (confidence 8, driver `w83781d') Probing for `Silicon Integrated Systems SIS5595' Trying general detect... Failed! Probing for `VIA Technologies VT82C686 Integrated Sensors' Trying general detect... Failed! Probing for `VIA Technologies VT8231 Integrated Sensors' Trying general detect... Failed! Probing for `ITE IT8705F / IT8712F / SiS 950' Trying address 0x0290... Failed! Probing for `IPMI BMC KCS' Trying address 0x0ca0... Failed! Probing for `IPMI BMC SMIC' Trying address 0x0ca8... Failed! Some Super I/O chips may also contain sensors. Super I/O probes are typically a bit more dangerous, as we have to write to I/O ports to do this. This is usually safe though. Do you want to scan for Super I/O sensors? (YES/no): y Probing for `ITE 8702F Super IO Sensors' Failed! (skipping family) Probing for `Nat. Semi. PC87351 Super IO Fan Sensors' Failed! (skipping family) Probing for `SMSC 47B27x Super IO Fan Sensors' Failed! (skipping family) Probing for `VT1211 Super IO Sensors' Failed! (0x60) Probing for `Winbond W83627HF Super IO Sensors' Failed! (0x60) Probing for `Winbond W83627THF Super IO Sensors' Failed! (0x60) Probing for `Winbond W83637HF Super IO Sensors' Failed! (0x60) Probing for `Winbond W83697HF Super IO Sensors' Success... found at address 0x0295 Probing for `Winbond W83697SF/UF Super IO PWM' Failed! (0x60) Probing for `Winbond W83L517D Super IO' Failed! (0x60) Do you want to scan for secondary Super I/O sensors? (YES/no): y Probing for `ITE 8702F Super IO Sensors' Failed! (skipping family) Probing for `Nat. Semi. PC87351 Super IO Fan Sensors' Failed! (skipping family) Probing for `SMSC 47B27x Super IO Fan Sensors' Failed! (skipping family) Probing for `VT1211 Super IO Sensors' Failed! (skipping family) Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `w83781d' (should be inserted): Detects correctly: * ISA bus address 0x0290 (Busdriver `i2c-isa') Chip `Winbond W83697HF' (confidence: 8) <http://forums.contribs.org/Smileys/default/cool.gif> Driver `w83627hf' (should be inserted): Detects correctly: * ISA bus address 0x0295 (Busdriver `i2c-isa') Chip `Winbond W83697HF Super IO Sensors' (confidence: 9) I will now generate the commands needed to load the I2C modules. Sometimes, a chip is available both through the ISA bus and an I2C bus. ISA bus access is faster, but you need to load an additional driver module for it. If you have the choice, do you want to use the ISA bus or the I2C/SMBus (ISA/smbus)? ISA To make the sensors modules behave correctly, add these lines to /etc/modules.conf: #----cut here---- # I2C module options alias char-major-89 i2c-dev #----cut here---- To load everything that is needed, add this to some /etc/rc* file: #----cut here---- # I2C adapter drivers modprobe i2c-isa # I2C chip drivers modprobe w83781d modprobe w83627hf # sleep 2 # optional /usr/bin/sensors -s # recommended #----cut here---- WARNING! If you have some things built into your kernel, the list above will contain too many modules. Skip the appropriate ones! You really should try these commands right now to make sure everything is working properly. Monitoring programs won't work until it's done. Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): y Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors for initialization at boot time. [root at server ~]# Kind Regards ---------------------------------------------------------------------------- ------- Email: john at ber.net.nz ---------------------------------------------------------------------------- -------- Email disclaimer: Emails from me, and any attached files are intended only for the person, persons, entity, or entities to which they are addressed. It may contain confidential and/or privileged materials, which should not be retransmitted or otherwise disseminated. If you receive an email in error from me, please let me know, and delete the material from your computer. Thank you. ---------------------------------------------------------------------------- -------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20090420/022ce62a/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 172 bytes Desc: not available Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20090420/022ce62a/attachment.gif
