Problem with instruktions from sensors-detect
Johan Nilsson
johan.nilsson.8135 at student.uu.se
Fri Jan 30 15:13:18 UTC 2004
I try to activate lm_sensors and run: sensors-detect. And I have some
problem and questions..
1) I wounder were i may find which modules that already are loaded in the
kernel? I said yes, for every thing because I think that the only wrong may
be overestimation of values?
2) Then i almost enden the running I get the instructions to add some
lines. I found /etc/modules.conf and enter the requested lines "alias
char-major-89 i2c-dev" to the plain-text file as modules.conf are,
according to konqueror.
But I don´t know that they mean with "To load everything that is needed,
add this to some /etc/rc* file:"
I have four file beginning with rc in /etc/:
rc, rc.local, rc.news, rc.sysinit.
and directory: rc0.d to rc6.d and rc.d.
All four are all Shell Script and When I try to enter them using Konquer as
"File Manager -Super user mode" I can´t enter. The directory also changes
from /etc/ to /etc/rc.d?? or my computer reboot. :oI. I am very new at
linux...but i suspect that I am not suposed the edit shell script..but the
only files that beginn with rc, are shell-script in /etc/ and the files in
the directory begging with rc* are shell script.
I also attach a .txt file from my running of sensors-detect.
Thanx for any help /Johan.
-------------- next part --------------
>From running /usr/sbin/sensors-detect
[b at gamlabettan b]$ su -
Password:
[root at gamlabettan root]# /usr/sbin/sensors-detect
This program will help you determine which I2C/SMBus modules you n
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/i
files, for most things.
If you have patched your kernel and have some drivers built-in, yo
safely answer NO if asked to load some modules. In this case, thin
seem a bit confusing, but they will still work.
BIOS vendor (ACPI): JETWAY
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): YES
Probing for PCI bus adapters...
Use driver `i2c-viapro' for device 00:07.4: VIA Technologies VT82C
PI
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): YES
Module loaded succesfully.
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.22-1.2149.nptl/unsupported/drivers/i2c/i2c-elektor.o: init_module: No s
uch device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO o
r IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.22-1.2149.nptl/unsupported/drivers/i2c/i2c-elektor.o: insmod /lib/modul
es/2.4.22-1.2149.nptl/unsupported/drivers/i2c/i2c-elektor.o failed
/lib/modules/2.4.22-1.2149.nptl/unsupported/drivers/i2c/i2c-elektor.o: insmod i2c-elekto
r failed
Loading failed... skipping.
Load `i2c-elv' (say NO if built into your kernel)? (YES/no): YES
/lib/modules/2.4.22-1.2149.nptl/unsupported/drivers/i2c/i2c-elv.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.22-1.2149.nptl/unsupported/drivers/i2c/i2c-elv.o: insmod /lib/modules/2.4.22-1.2149.nptl/unsuppor
ted/drivers/i2c/i2c-elv.o failed
/lib/modules/2.4.22-1.2149.nptl/unsupported/drivers/i2c/i2c-elv.o: 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.22-1.2149.nptl/unsupported/drivers/i2c/i2c-velleman.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.22-1.2149.nptl/unsupported/drivers/i2c/i2c-velleman.o: insmod /lib/modules/2.4.22-1.2149.nptl/uns
upported/drivers/i2c/i2c-velleman.o failed
/lib/modules/2.4.22-1.2149.nptl/unsupported/drivers/i2c/i2c-velleman.o: 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).
Next adapter: SMBus Via Pro adapter at 5000 (Non-I2C SMBus adapter)
Do you want to scan it? (YES/no/selectively): YES
Client found at address 0x2d
Probing for `Myson MTP008'... Failed!
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Success!
(confidence 3, driver `lm80')
Probing for `National Semiconductor LM85'... Failed!
Probing for `Analog Devices ADM1027 or ADT7463'... Failed!
Probing for `SMSC EMC6D100 and EMC6D101'... Failed!
Probing for `National Semiconductor LM87'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83783S'... Failed!
Probing for `Winbond W83791D'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Asus AS99127F (rev.1)'... Failed!
Probing for `Asus AS99127F (rev.2)'... Failed!
Probing for `Asus ASB100 Bach'... Failed!
Probing for `Winbond W83L784R/AR'... Failed!
Probing for `Genesys Logic GL518SM Revision 0x00'... Failed!
Probing for `Genesys Logic GL518SM Revision 0x80'... Failed!
Probing for `Genesys Logic GL520SM'... Failed!
Probing for `Genesys Logic GL525SM'... Failed!
Probing for `Analog Devices ADM9240'... Failed!
Probing for `Dallas Semiconductor DS1780'... Failed!
Probing for `National Semiconductor LM81'... Failed!
Probing for `Analog Devices ADM1026'... Failed!
Probing for `Analog Devices ADM1025'... Failed!
Probing for `Philips NE1619'... Failed!
Probing for `Analog Devices ADM1024'... Failed!
Probing for `Analog Devices ADM1022'... Failed!
Probing for `Texas Instruments THMC50'... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'... Failed!
Client found at address 0x4e
Probing for `National Semiconductor LM75'... Success!
(confidence 3, driver `lm75')
Probing for `Dallas Semiconductor DS1621'... Success!
(confidence 3, driver `ds1621')
Probing for `Analog Devices ADM1021'... Failed!
Probing for `Analog Devices ADM1021A/ADM1023'... Failed!
Probing for `Maxim MAX1617'... Failed!
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 0x50
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
Probing for `DDC monitor'... Failed!
Client found at address 0x51
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): 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... 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... Success!
(confidence 9, driver `via686a')
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. Do you want to scan for Super I/O sensors? (YES/no): YES
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 `lm80' (should be inserted):
Detects correctly:
* Bus `SMBus Via Pro adapter at 5000' (Non-I2C SMBus adapter)
Busdriver `i2c-viapro', I2C address 0x2d
Chip `National Semiconductor LM80' (confidence: 3)
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 `ds1621' (may not be inserted):
Misdetects:
* Bus `SMBus Via Pro adapter at 5000' (Non-I2C SMBus adapter)
Busdriver `i2c-viapro', I2C address 0x4e
Chip `Dallas Semiconductor DS1621' (confidence: 3)
Driver `pcf8591' (may not be inserted):
Misdetects:
* Bus `SMBus Via Pro adapter at 5000' (Non-I2C SMBus adapter)
Busdriver `i2c-viapro', I2C address 0x4e
Chip `Philips Semiconductors PCF8591' (confidence: 1)
Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `SMBus Via Pro adapter at 5000' (Non-I2C SMBus adapter)
Busdriver `i2c-viapro', I2C address 0x50
Chip `SPD EEPROM' (confidence: 8)
* Bus `SMBus Via Pro adapter at 5000' (Non-I2C SMBus adapter)
Busdriver `i2c-viapro', I2C address 0x51
Chip `SPD EEPROM' (confidence: 8)
Driver `via686a' (should be inserted):
Detects correctly:
* ISA bus, undetermined address (Busdriver `i2c-isa')
Chip `VIA Technologies VT82C686 Integrated 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-viapro
modprobe i2c-isa
# I2C chip drivers
modprobe lm80
modprobe lm75
modprobe eeprom
modprobe via686a
# 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.
-------------- next part --------------
******************************************************************
Johan Nilsson
Sernandersväg 8:418
752 61 Uppsala
tel 018-461236
mobil 0739-483464
******************************************************************
More information about the fedora-list
mailing list