I've now had time to reconfigure the lm_sensors install and compare
with my bios settings :-
M8.2 lm_sensors Install No.2 amd configuration 10.11.02
============================================
[root@localhost root]# sensors-detect
This program will help you to determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively.
You need to have done a `make install', issued a `depmod -a' and made sure
`/etc/conf.modules' (or `/etc/modules.conf') contains the appropriate
module path before you can use some functions of this utility. Read
doc/modules for more information.
Also, you need to be `root', or at least have access to the /dev/i2c[-/]* files for some things. You can use prog/mkdev/mkdev.sh to create these /dev files
if you do not have them already.
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.
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): yes
Probing for PCI bus adapters...
Use driver `i2c-viapro' for device 00:11.0: VIA Technologies VT8233 VLink South Bridge
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Module `i2c-viapro' already loaded.
Do you now want to be prompted for non-detectable adapters? (yes/NO): yes
Load `i2c-elektor' (say NO if built into your kernel)? (YES/no): yes
/lib/modules/2.4.18-6mdk/kernel/drivers/i2c/i2c-elektor.o.gz: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
modprobe: insmod /lib/modules/2.4.18-6mdk/kernel/drivers/i2c/i2c-elektor.o.gz failed
modprobe: insmod i2c-elektor failed
Loading failed ()... skipping.
Load `i2c-elv' (say NO if built into your kernel)? (YES/no): yes
/lib/modules/2.4.18-6mdk/kernel/drivers/i2c/i2c-elv.o.gz: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
modprobe: insmod /lib/modules/2.4.18-6mdk/kernel/drivers/i2c/i2c-elv.o.gz failedmodprobe: insmod i2c-elv failed
Loading failed ()... skipping.
Load `i2c-philips-par' (say NO if built into your kernel)? (YES/no): yes
Module loaded succesfully.
Load `i2c-velleman' (say NO if built into your kernel)? (YES/no): yes
/lib/modules/2.4.18-6mdk/kernel/drivers/i2c/i2c-velleman.o.gz: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
modprobe: insmod /lib/modules/2.4.18-6mdk/kernel/drivers/i2c/i2c-velleman.o.gz failed
modprobe: insmod i2c-velleman failed
Loading failed ()... skipping.
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 already loaded.
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 0400 (Non-I2C SMBus adapter)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x18
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83783S'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Asus AS99127F'... Failed!
Probing for `Analog Devices ADM1021'... 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!
Client at address 0x2d can not be probed - unload all client drivers first!
Client found at address 0x30
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83783S'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Asus AS99127F'... Failed!
Client at address 0x48 can not be probed - unload all client drivers first!
Client at address 0x49 can not be probed - unload all client drivers first!
Client found at address 0x50
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83783S'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Asus AS99127F'... Failed!
Probing for `Serial EEPROM (PC-100 DIMM)'... Success!
(confidence 8, driver `eeprom')
Probing for `DDC monitor'... Failed!
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): yes
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... Success!
(confidence 8, driver `w83781d')
Probing for `Winbond W83697HF'
Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
Trying general detect... Failed!
Probing for `VIA Technologies VT 82C686 Integrated Sensors'
Trying general detect... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'
Trying address 0x0290... 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 0400' (Non-I2C SMBus adapter)
Busdriver `i2c-viapro', I2C address 0x18
Chip `National Semiconductor LM84' (confidence: 6)
Misdetects:
* Bus `SMBus Via Pro adapter at 0400' (Non-I2C SMBus adapter)
Busdriver `i2c-viapro', I2C address 0x18
Chip `Maxim MAX1617' (confidence: 3)
Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `SMBus Via Pro adapter at 0400' (Non-I2C SMBus adapter)
Busdriver `i2c-viapro', I2C address 0x50
Chip `Serial EEPROM (PC-100 DIMM)' (confidence: 8)
Driver `w83781d' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `Winbond W83627HF' (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)? ISA/smbus
Use of uninitialized value in string eq at /usr/sbin/sensors-detect line 2371.
Use of uninitialized value in string eq at /usr/sbin/sensors-detect line 2383.
WARNING! If you have some things built into your kernel, the
below list will contain too many modules. Skip the appropriate ones!
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 eeprom
modprobe w83781d
#----cut here----
To make the sensors modules behave correctly, add these lines to either
/etc/modules.conf or /etc/conf.modules:
#----cut here----
# I2C module options
alias char-major-89 i2c-dev
options adm1021 ignore=0,0x18
#----cut here----
[root@localhost root]#
=======================================================
[root@localhost root]# sensors
w83627hf-isa-0290
Adapter: ISA adapter
Algorithm: ISA algorithm
VCore 1: +1.72 V (min = +1.66 V, max = +2.03 V) ALARM
VCore 2: +1.24 V (min = +1.66 V, max = +2.03 V) ALARM
+3.3V: +3.32 V (min = +2.97 V, max = +3.63 V)
+5V: +5.02 V (min = +4.50 V, max = +5.48 V)
+12V: +12.31 V (min = +10.79 V, max = +13.11 V)
-12V: -12.13 V (min = -13.21 V, max = -10.90 V)
-5V: -5.17 V (min = -5.51 V, max = -4.51 V)
V5SB: +5.51 V (min = +4.50 V, max = +5.48 V) ALARM
VBat: +3.42 V (min = +2.70 V, max = +3.29 V) ALARM
fan1: 0 RPM (min = 3000 RPM, div = 2) ALARM
fan2: 0 RPM (min = 3000 RPM, div = 2) ALARM
fan3: 3792 RPM (min = 3000 RPM, div = 2)
temp1: +34°C (limit = +60°C, hysteresis = +50°C) sensor = thermistor
temp2: +45.5°C (limit = +60°C, hysteresis = +50°C) sensor = thermistor
temp3: +208.0°C (limit = +60°C, hysteresis = +50°C) sensor = thermistor
vid: +1.85 V
alarms: Chassis intrusion detection ALARM
beep_enable:
Sound alarm disabled
w83627hf-i2c-1-2d
Adapter: SMBus Via Pro adapter at 0400
Algorithm: Non-I2C SMBus adapter
VCore 1: +1.72 V (min = +1.66 V, max = +2.03 V)
VCore 2: +1.24 V (min = +1.66 V, max = +2.03 V)
+3.3V: +3.29 V (min = +2.97 V, max = +3.63 V)
+5V: +5.04 V (min = +4.50 V, max = +5.48 V)
+12V: +12.27 V (min = +10.79 V, max = +13.11 V)
-12V: -12.24 V (min = -13.21 V, max = -10.90 V)
-5V: -5.20 V (min = -5.51 V, max = -4.51 V)
V5SB: +5.53 V (min = +4.50 V, max = +5.48 V)
VBat: +3.40 V (min = +2.70 V, max = +3.29 V)
fan1: 0 RPM (min = 3000 RPM, div = 2)
fan2: 0 RPM (min = 3000 RPM, div = 2)
fan3: 3770 RPM (min = 3000 RPM, div = 2)
temp1: +34°C (limit = +60°C, hysteresis = +50°C) sensor = thermistor
temp2: +45.0°C (limit = +60°C, hysteresis = +50°C) sensor = thermistor
temp3: +209.0°C (limit = +60°C, hysteresis = +50°C) sensor = thermistor
vid: +1.85 V
alarms: Chassis intrusion detection ALARM
beep_enable:
Sound alarm disabled
lm84-i2c-1-18
Adapter: SMBus Via Pro adapter at 0400
Algorithm: Non-I2C SMBus adapter
temp: +15°C (min = -1°C, max = -49°C)ALARM (LOW,HIGH)
remote_temp:
+0°C (min = +28°C, max = -1°C)
eeprom-i2c-1-50
Adapter: SMBus Via Pro adapter at 0400
Algorithm: Non-I2C SMBus adapter
[root@localhost root]#
=================================================================================
Bios Settings 10.11.02
======================
Spread spectrum +/- 0.25%
CPU FSB Clock 100 /choice 133
CPU FSB/PCI overclocking H/W /choice 164/41.10
163/40.85
162/40.60 etc,etc
CPU Ratio Auto /choice X125/X13.0
X12.0
X11.5 etc etc
CPU Vcore (v) Auto /choice 1.850 etc etc
DDR Voltage (v) Auto /choice 1.850 etc, etc
CPU fan detection enabled
Chassis intrusion disabled
CPU temp 46C/114F
Sustem temp 35C/95F
CPU fan speed 3792rpm
System fan speed 0 rpm
Power fan speed 0 rpm
Vcore 1.712v
Vtt 1.248v
Vio 3.344v
+5.000v 5.140v
+12.000v 12.410v
-12.000v -12.349v
-5.000v -5.127v
Battery 3,424v
+5vsb 5.018v
=============================================
I guess the cpu temperature in lm_sensors is reading 45.0C (temp2)
whereas bios says 46C/114F , not bad , but what the temp3 is
reading @ 209C I cannot guess, I don't think it is reading anything
at all.
What does anyone else think ?
John
--
John Richard Smith
[EMAIL PROTECTED]
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
