Hi, and thanks for all your work on lm sensors and i2c! I am running Mandrake Linux 9.1 with a lot of Cooker additions. Mandrake's Kernel 2.4.21-0.13 with Win4Lin hook. My system is a homemade one with a Soyo SY-Kt400 (Dragon Ultra Black) with Phoenix Bios updated as of April 2003 with an AMD XP 2000 CPU. I compiled and successfully installed the CVS versions of I2C and lm_sensors2. After performing sensors-detect, On MY system, the loading of the driver ADM1021 causes a catostrophic system failure which requires a complete restore of the hard drive partition that Linux is on. In the sensors-detect messages, it DOES say that this driver can cause problems. After some thinking and many system restores, I removed the ADM1021 driver modprobe line in rc.local, and the corresponding line in modules.conf and the sensors program seems to run fine. I get both the die temperature of the CPU accurately and the system temperature also (which is all I am interested in). I am attaching 3 files for you to review. 1) sensors-output.txt which shows my system info -- alarms and all (which I ignore) from the sensors program 2) sensors-detect-output.txt which shows your program's analysis of my system 3) i2cdetect-i2cdump-output.txt which shows the I2C dumps of devices uncovered by your program. Of course, there is no I2C support in my kernel, and as I mentioned, the sensors output runs rine. Best wishes, and thank you for your efforts. If I can help clarify anything, or provide you with additional details, please let me know! -- Peter Hyman Home:(609)395-1211 Office: (609)655-1184, Fax:(609)655-0285 Stop Telemarketers. Sign up for Do Not Call at http://donotcall.gov -------------- next part -------------- [I2CDETECT OUTPUT] bash-2.05b# prog/detect/i2cdetect Error: No i2c-bus specified! Syntax: i2cdetect I2CBUS I2CBUS is an integer Installed I2C busses: i2c-0 smbus SMBus Via Pro adapter at 5000 Non-I2C SMBus adapter bash-2.05b# prog/detect/i2cdetect 0 WARNING! This program can confuse your I2C bus, cause data loss and worse! I will probe file /dev/i2c-0 You have five seconds to reconsider and press CTRL-C! 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX 10: XX XX XX XX XX XX XX XX 18 XX XX XX XX XX XX XX 20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX 30: XX XX XX XX XX XX XX 37 XX XX XX XX XX XX XX XX 40: XX XX XX XX XX XX XX XX XX XX XX XX 4c XX 4e XX 50: XX XX 52 XX XX XX XX XX XX XX XX XX XX XX XX XX 60: XX XX XX XX XX XX XX XX XX 69 XX XX XX XX XX XX 70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX bash-2.05b# prog/dump/i2cdump 0 0x18 No size specified (using byte-data access) WARNING! This program can confuse your I2C bus, cause data loss and worse! I will probe file /dev/i2c-0, address 0x18, mode byte You have five seconds to reconsider and press CTRL-C! 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef 00: d7 d7 00 00 00 ef ff ff 7f 7f 00 60 00 00 ff ff ??...?..??.`.... 10: 00 00 00 00 00 00 00 ff ff ff ff ff ff ff ff ff ................ 20: 60 13 ff ff ff ff ff ff ff ff ff ff ff ff ff ff `?.............. 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ bash-2.05b# prog/dump/i2cdump 0 0x37 No size specified (using byte-data access) WARNING! This program can confuse your I2C bus, cause data loss and worse! I will probe file /dev/i2c-0, address 0x37, mode byte You have five seconds to reconsider and press CTRL-C! 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef 00: 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f ???????????????? 10: 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f ???????????????? 20: 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f ???????????????? 30: 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f ???????????????? 40: 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f ???????????????? 50: 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f ???????????????? 60: 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f ???????????????? 70: 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f ???????????????? 80: 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f ???????????????? 90: 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f ???????????????? a0: 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f ???????????????? b0: 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f ???????????????? c0: 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f ???????????????? d0: 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f ???????????????? e0: 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f ???????????????? f0: 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f 3f ???????????????? bash-2.05b# prog/dump/i2cdump 0 0x4c No size specified (using byte-data access) WARNING! This program can confuse your I2C bus, cause data loss and worse! I will probe file /dev/i2c-0, address 0x4c, mode byte You have five seconds to reconsider and press CTRL-C! 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef 00: 29 3e 00 00 05 46 05 46 05 00 00 00 00 00 00 00 )>..?F?F?....... 10: e0 00 00 00 00 00 00 00 00 55 00 00 00 00 00 00 ?........U...... 20: 55 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 U?.............. 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ b0: 2a 20 0f b3 ab 00 0d 00 00 4b 4b 00 00 00 00 00 * ???.?..KK..... c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 21 ..............?! bash-2.05b# prog/dump/i2cdump 0 0x4e No size specified (using byte-data access) WARNING! This program can confuse your I2C bus, cause data loss and worse! I will probe file /dev/i2c-0, address 0x4e, mode byte You have five seconds to reconsider and press CTRL-C! 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef 00: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 ???????????????? 10: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 ???????????????? 20: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 ???????????????? 30: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 ???????????????? 40: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 ???????????????? 50: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 ???????????????? 60: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 ???????????????? 70: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 ???????????????? 80: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 ???????????????? 90: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 ???????????????? a0: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 ???????????????? b0: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 ???????????????? c0: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 ???????????????? d0: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 ???????????????? e0: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 ???????????????? f0: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 ???????????????? bash-2.05b# prog/dump/i2cdump 0 0x52 No size specified (using byte-data access) WARNING! This program can confuse your I2C bus, cause data loss and worse! I will probe file /dev/i2c-0, address 0x52, mode byte You have five seconds to reconsider and press CTRL-C! 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef 00: 80 08 07 0d 0a 02 40 00 04 60 70 00 82 08 00 01 ??????@.?`p.??.? 10: 0e 04 0c 01 02 20 00 75 70 00 00 48 30 48 2a 40 ????? .up..H0H*@ 20: 75 75 45 45 00 00 00 00 00 3c 48 30 2d 60 00 00 uuEE.....<H0-`.. 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4c ...............L 40: 7f 98 00 00 00 00 00 00 04 4b 00 00 00 00 00 00 ??......?K...... 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 03 21 06 .............?!? 60: 2a 75 de 00 00 00 00 00 00 00 00 00 00 00 00 00 *u?............. 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ f0: 39 39 30 35 32 31 36 2d 30 30 33 2e 41 30 33 00 9905216-003.A03. bash-2.05b# prog/dump/i2cdump 0 0x69 No size specified (using byte-data access) WARNING! This program can confuse your I2C bus, cause data loss and worse! I will probe file /dev/i2c-0, address 0x69, mode byte You have five seconds to reconsider and press CTRL-C! 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef 00: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 ???????????????? 10: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 ???????????????? 20: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 ???????????????? 30: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 ???????????????? 40: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 ???????????????? 50: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 ???????????????? 60: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 ???????????????? 70: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 ???????????????? 80: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 ???????????????? 90: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 ???????????????? a0: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 ???????????????? b0: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 ???????????????? c0: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 ???????????????? d0: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 ???????????????? e0: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 ???????????????? f0: 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 ???????????????? bash-2.05b# -------------- next part -------------- [SENSORS-DETECT OUTPUT] bash-2.05b# prog/detect/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. BIOS vendor (ACPI): KT400 System vendor (DMI): VIA Technologies, Inc. BIOS version (DMI): 6.00 PG 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): Probing for PCI bus adapters... Use driver `i2c-viapro' for device 00:11.0: VIA Technologies VT8233A/8235 South Bridge Probe succesfully concluded. We will now try to load each adapter module in turn. Load `i2c-viapro' (say NO if built into your kernel)? (YES/no): Module loaded succesfully. Do you now want to be prompted for non-detectable adapters? (yes/NO): 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): 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: SMBus Via Pro adapter at 5000 (Non-I2C SMBus adapter) Do you want to scan it? (YES/no/selectively): Client found at address 0x18 Probing for `Analog Devices ADM1021'... Failed! Probing for `Analog Devices ADM1021A/ADM1023'... Failed! Probing for `Maxim MAX1617'... Success! (confidence 3, driver `adm1021') Probing for `Maxim MAX1617A'... Failed! Probing for `TI THMC10'... Failed! Probing for `National Semiconductor LM84'... Success! (confidence 6, driver `adm1021') Probing for `Genesys Logic GL523SM'... Failed! Probing for `Onsemi MC1066'... Failed! Probing for `National Semiconductor LM82'... Failed! Probing for `National Semiconductor LM83'... Failed! Client found at address 0x37 Client found at address 0x4c Probing for `National Semiconductor LM75'... Failed! Probing for `Dallas Semiconductor DS1621'... Failed! Probing for `Analog Devices ADM1021'... Failed! Probing for `Analog Devices ADM1021A/ADM1023'... Failed! Probing for `Maxim MAX1617'... Success! (confidence 3, driver `adm1021') Probing for `Maxim MAX1617A'... Failed! Probing for `TI THMC10'... Failed! Probing for `National Semiconductor LM84'... Failed! Probing for `Genesys Logic GL523SM'... Failed! Probing for `Onsemi MC1066'... Failed! Probing for `National Semiconductor LM82'... Failed! Probing for `National Semiconductor LM83'... Failed! Probing for `National Semiconductor LM90'... Success! (confidence 8, driver `lm90') Probing for `National Semiconductor LM89'... Failed! Probing for `National Semiconductor LM86'... Failed! Probing for `Analog Devices ADM1032'... Failed! Probing for `Maxim MAX6657/MAX6658'... Failed! Probing for `Philips Semiconductors PCF8591'... Success! (confidence 1, driver `pcf8591') Client found at address 0x4e Probing for `National Semiconductor LM75'... Success! (confidence 3, driver `lm75') Probing for `Dallas Semiconductor DS1621'... Failed! Probing for `Analog Devices ADM1021'... Failed! Probing for `Analog Devices ADM1021A/ADM1023'... Failed! Probing for `Maxim MAX1617'... Success! (confidence 3, driver `adm1021') Probing for `Maxim MAX1617A'... Failed! Probing for `TI THMC10'... Failed! Probing for `National Semiconductor LM84'... Failed! Probing for `Genesys Logic GL523SM'... Failed! Probing for `Onsemi MC1066'... Failed! Probing for `National Semiconductor LM82'... Failed! Probing for `National Semiconductor LM83'... Failed! Probing for `Philips Semiconductors PCF8591'... Success! (confidence 1, driver `pcf8591') Client found at address 0x52 Probing for `SPD EEPROM'... Success! (confidence 8, driver `eeprom') 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. Do you want to scan the ISA bus? (YES/no): Probing for `National Semiconductor LM78' Trying address 0x0290... Success! (confidence 7, driver `lm78') 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... Failed! 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... Success! (confidence 8, driver `it87') 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. Do you want to scan for Super I/O sensors? (YES/no): Probing for `SMSC 47M10x Super IO Fan Sensors' Failed! Probing for `SMSC 47M14x Super IO Fan Sensors' Failed! Probing for `VT1211 Super IO Sensors' Failed! Probing for `Winbond W83627HF Super IO Sensors' Failed! Probing for `Winbond W83627THF Super IO Sensors' Failed! Probing for `Winbond W83697HF Super IO Sensors' Failed! Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `adm1021' (should be inserted but causes problems): Detects correctly: * Bus `SMBus Via Pro adapter at 5000' (Non-I2C SMBus adapter) Busdriver `i2c-viapro', I2C address 0x18 Chip `National Semiconductor LM84' (confidence: 6) Misdetects: * Bus `SMBus Via Pro adapter at 5000' (Non-I2C SMBus adapter) Busdriver `i2c-viapro', I2C address 0x18 Chip `Maxim MAX1617' (confidence: 3) * Bus `SMBus Via Pro adapter at 5000' (Non-I2C SMBus adapter) Busdriver `i2c-viapro', I2C address 0x4c Chip `Maxim MAX1617' (confidence: 3) * Bus `SMBus Via Pro adapter at 5000' (Non-I2C SMBus adapter) Busdriver `i2c-viapro', I2C address 0x4e Chip `Maxim MAX1617' (confidence: 3) Driver `lm90' (should be inserted): Detects correctly: * Bus `SMBus Via Pro adapter at 5000' (Non-I2C SMBus adapter) Busdriver `i2c-viapro', I2C address 0x4c Chip `National Semiconductor LM90' (confidence: 8) Driver `pcf8591' (may not be inserted): Misdetects: * Bus `SMBus Via Pro adapter at 5000' (Non-I2C SMBus adapter) Busdriver `i2c-viapro', I2C address 0x4c Chip `Philips Semiconductors PCF8591' (confidence: 1) * Bus `SMBus Via Pro adapter at 5000' (Non-I2C SMBus adapter) Busdriver `i2c-viapro', I2C address 0x4e Chip `Philips Semiconductors PCF8591' (confidence: 1) Driver `lm75' (should be inserted): Detects correctly: * Bus `SMBus Via Pro adapter at 5000' (Non-I2C SMBus adapter) Busdriver `i2c-viapro', I2C address 0x4e Chip `National Semiconductor LM75' (confidence: 3) Driver `eeprom' (should be inserted): Detects correctly: * Bus `SMBus Via Pro adapter at 5000' (Non-I2C SMBus adapter) Busdriver `i2c-viapro', I2C address 0x52 Chip `SPD EEPROM' (confidence: 8) Driver `lm78' (may not be inserted): Misdetects: * ISA bus address 0x0290 (Busdriver `i2c-isa') Chip `National Semiconductor LM78' (confidence: 7) Driver `it87' (should be inserted): Detects correctly: * ISA bus address 0x0290 (Busdriver `i2c-isa') Chip `ITE IT8705F / IT8712F / SiS 950' (confidence: 8) 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)? 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 options adm1021 ignore=0,0x18,0,0x4c,0,0x4e #----cut here---- To load everything that is needed, add this to some /etc/rc* file: #----cut here---- # I2C adapter drivers modprobe i2c-viapro modprobe i2c-isa # I2C chip drivers modprobe adm1021 modprobe lm90 modprobe lm75 modprobe eeprom modprobe it87 # sleep 2 # optional /usr/local/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): Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors for initialization at boot time. -------------- next part -------------- [SENSORS OUTPUT] bash-2.05b# sensors lm90-i2c-0-4c Adapter: SMBus Via Pro adapter at 5000 Algorithm: Non-I2C SMBus adapter M/B Temp: +41?C (low = +5?C, high = +70?C) CPU Temp: +63.1?C (low = +5.0?C, high = +70.0?C) tcrit1: +85?C tcrit2: +85?C hyst: +10?C eeprom-i2c-0-52 Adapter: SMBus Via Pro adapter at 5000 Algorithm: Non-I2C SMBus adapter Memory type: DDR SDRAM DIMM Memory size (MB): 512 it87-isa-0290 Adapter: ISA adapter Algorithm: ISA algorithm VCore 1: +1.74 V (min = +1.42 V, max = +1.56 V) ALARM VCore 2: +3.28 V (min = +2.40 V, max = +2.60 V) ALARM +3.3V: +5.94 V (min = +3.12 V, max = +3.44 V) ALARM +5V: +5.12 V (min = +4.72 V, max = +5.24 V) +12V: +9.96 V (min = +11.36 V, max = +12.60 V) ALARM -12V: -16.01 V (min = -12.63 V, max = -11.41 V) ALARM -5V: -6.11 V (min = -5.28 V, max = -4.81 V) ALARM Stdby: +3.28 V (min = +4.72 V, max = +5.24 V) ALARM VBat: +0.00 V fan1: 0 RPM (min = 0 RPM, div = 2) fan2: 4383 RPM (min = 3000 RPM, div = 2) fan3: 0 RPM (min = 3000 RPM, div = 2) ALARM Temp1/MB: +38?C (low = +20?C, high = +40?C) Temp2/CPU: +30?C (low = +25?C, high = +45?C) Temp3: +41?C (low = +25?C, high = +45?C) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 193 bytes Desc: This is a digitally signed message part Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20030918/a9b12c1b/attachment.bin
