Dennis Myers wrote:
On Saturday 09 November 2002 12:24 pm, John Richard Smith wrote:Now the config, seems there's more to it than meets the eye,this is how it went,
That's great, glad you got it. One thing though, in a lot of cases the devel packages are not needed, unless you do development work on that particular package which by what I see of your posts you might. (run on sentence). Anyway, it works for me without the devel packages so I don't install them just to keep things neat and tidy. Cheers,
John check and see if you have liblm_sensors1-2.6.4-4mdk installed, itYes, that's the key to it,first find and install from cd1 :-
looks like what you d/l'd may be different versions and they aren't
compatible. My system has lm_sensors-2.6.4-4mdk installed and the above
liblm and works dandy. HTH
liblm_sensors1-2.6.2-4mdk.i586.rpm
liblm_sensors1-devel-2.6.2-4mdk.rpm
then cd2:-
liblm_sensors1-static-devel-2.6.2-4mdk.1586.rpm
lm_sensors-2.6.2-4mdk.i586.rpm
all goes on sweetly, now to configure it.
John
[root@localhost root]# sensors-detect
This program will help you to determine which I2C/SMBus modules you need to
<snip>
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 VT8233 VLink 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): NO
I think I should of said yes here, can I run the prog again.
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 su
ch device
Hint: insmod errors can be caused by incorrect module parameters, including inva
lid IO or IRQ parameters
modprobe: insmod /lib/modules/2.4.18-6mdk/kernel/drivers/i2c/i2c-elektor.o.gz fa
iled
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 d
evice
Hint: insmod errors can be caused by incorrect module parameters, including inva
lid IO or IRQ parameters
modprobe: insmod /lib/modules/2.4.18-6mdk/kernel/drivers/i2c/i2c-elv.o.gz failed
modprobe: 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 not loaded. Do you want to load it now? (YES/no): yes
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).
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 `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
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-isa
# I2C chip drivers
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
#----cut here----
[root@localhost root]#
===============================================================================================
[root@localhost root]# /etc/rc.d/rc.local
[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)
VCore 2: +1.24 V (min = +1.66 V, max = +2.03 V) ALARM
+3.3V: +3.29 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.24 V (min = -13.21 V, max = -10.90 V)
-5V: -5.17 V (min = -5.51 V, max = -4.51 V)
V5SB: +5.56 V (min = +4.50 V, max = +5.48 V) ALARM
VBat: +3.44 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: 3770 RPM (min = 3000 RPM, div = 2)
temp1: +35°C (limit = +60°C, hysteresis = +50°C) sensor = thermistor
temp2: +45.0°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
Not bad I think, seems like I could have another 2 fan sensors,
don't worry about the alarms: Chassis intrusion detection I
just have the side panel off.
can't say I feel comfortable about
temp3: +208.0°C (limit = +60°C, hysteresis = +50°C) sensor = thermistor
how hot can something be and still work ?
John
--
John Richard Smith
[EMAIL PROTECTED]
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
