| View previous topic :: View next topic |
| Author |
Message |
Onturenio
n00b
Joined: 03 Sep 2005
Posts: 49
Location: Ontur
|
 Posted: Wed Sep 21, 2005 9:18 am Post subject: About sensors |
 |
|
I have followed the tuto in this page, and have some sensors recognized, but not seem very util. This is the output i get:
| Quote: |
# /etc/init.d/lm_sensors start
* Loading lm_sensors modules...
* Loading i2c-sis96x ... [ ok ]
* Loading eeprom ... [ ok ]
* Initializing sensors ... [ ok ]
# sensors
eeprom-i2c-0-51
Adapter: SiS96x SMBus adapter at 0x8100
Memory type: DDR SDRAM DIMM
Memory size (MB): 256
eeprom-i2c-0-50
Adapter: SiS96x SMBus adapter at 0x8100
Memory type: DDR SDRAM DIMM
Memory size (MB): 256
|
Only information about RAM, nothing of voltajes or temperature  .
The output of sensors-detect is:
| Quote: |
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):
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.
Load `i2c-sis96x' (say NO if built into your kernel)? (YES/no):
Module loaded succesfully.
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):
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 0x8100
Do you want to scan it? (YES/no/selectively):
Client found at address 0x08
Client found at address 0x10
Client found at address 0x50
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
Probing for `DDC monitor'... Failed!
Probing for `Maxim MAX6900'... Failed!
Client found at address 0x51
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
Client found at address 0x69
Client found at address 0x6a
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):
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 W83627EHF'
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 IT8712F'
Trying address 0x0290... Failed!
Probing for `ITE IT8705F / 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):
Probing for `ITE 8702F Super IO Sensors'
Failed! (0xea11)
Probing for `ITE 8705F Super IO Sensors'
Failed! (0xea11)
Probing for `ITE 8712F Super IO Sensors'
Failed! (0xea11)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87360 Super IO Fan Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87363 Super IO Fan Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87364 Super IO Fan Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87365 Super IO Fan Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87365 Super IO Voltage Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87365 Super IO Thermal Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87366 Super IO Fan Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87366 Super IO Voltage Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87366 Super IO Thermal Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87372 Super IO Fan Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87373 Super IO Fan Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87591 Super IO'
Failed! (0xea)
Probing for `Nat. Semi. PC87371 Super IO'
Failed! (0xea)
Probing for `Nat. Semi. PC97371 Super IO'
Failed! (0xea)
Probing for `Nat. Semi. PC8739x Super IO'
Success... (no hardware monitoring capabilities)
Probing for `Nat. Semi. PC8741x Super IO'
Failed! (0xea)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (0xea)
Probing for `SMSC 47M10x/13x Super IO Fan Sensors'
Failed! (0xea)
Probing for `SMSC 47M14x Super IO Fan Sensors'
Failed! (0xea)
Probing for `SMSC 47M15x/192 Super IO Fan Sensors'
Failed! (0xea)
Probing for `SMSC 47S42x Super IO Fan Sensors'
Failed! (0xea)
Probing for `SMSC 47S45x Super IO Fan Sensors'
Failed! (0xea)
Probing for `SMSC 47M172 Super IO'
Failed! (0xea)
Probing for `SMSC LPC47B397-NC Super IO'
Failed! (0xea)
Probing for `VT1211 Super IO Sensors'
Failed! (0xea)
Probing for `Winbond W83627HF Super IO Sensors'
Failed! (0xea)
Probing for `Winbond W83627THF Super IO Sensors'
Failed! (0xea)
Probing for `Winbond W83637HF Super IO Sensors'
Failed! (0xea)
Probing for `Winbond W83697HF Super IO Sensors'
Failed! (0xea)
Probing for `Winbond W83697SF/UF Super IO PWM'
Failed! (0xea)
Probing for `Winbond W83L517D Super IO'
Failed! (0xea)
Probing for `Winbond W83627EHF Super IO Sensors'
Failed! (0xea11)
Do you want to scan for secondary Super I/O sensors? (YES/no):
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)
Probing for `Winbond W83627EHF Super IO Sensors'
Failed! (skipping family)
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `SiS96x SMBus adapter at 0x8100'
Busdriver `i2c-sis96x', I2C address 0x50
Chip `SPD EEPROM' (confidence: 
* Bus `SiS96x SMBus adapter at 0x8100'
Busdriver `i2c-sis96x', I2C address 0x51
Chip `SPD EEPROM' (confidence:
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)?
If you want to load the modules at startup, generate a config file
below and make sure lm_sensors gets started; e.g
$ rc-update add lm_sensors default.
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
#----end 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.
To load everything that is needed, execute the commands above...
#----cut here----
# I2C adapter drivers
modprobe i2c-sis96x
# I2C chip drivers
modprobe eeprom
# sleep 2 # optional
/usr/bin/sensors -s # recommended
Do you want to overwrite /etc/conf.d/lm_sensors? Enter s to specify other file name?
|
I have enabled as modules in the kernel the two it found, but may be not enought for temperatures. Any idea? |
|
| Back to top |
|
 |
Incabulos
n00b
Joined: 14 Apr 2003
Posts: 28
Location: Sydney, Australia
|
| Posted: Wed Sep 21, 2005 1:00 pm Post subject: |
|
|
Run lsmod and be sure you have sufficient modules loaded ( both hardware-specific and generic ) to handle all the sensors stuff ( putting them in /etc/modules.autoload.d/kernel-2.x is good also ) , or ensure they are compiled in directly.
I'm using the following:
| Code: |
lsmod | grep i2c_core
i2c_core 17936 5 eeprom,i2c_isa,i2c_viapro,it87,i2c_sensor
|
'eeprom' will read the prom on your ram chips and report the no of simms and their capacity, this does not handle the regular hardware sensors. I'm using the it87 driver to talk to the actual sensors. At a guess I would say your setup needs i2c_sensor and possibly i2c_isa loaded and working.
If all else fails, google for your motherboard and chipset and see what other sensor configurations people are recommending. As well as the drivers that pull fan RPM, temperatures, etc from the sensors you will likely need the right settings to scale the sensor outputs to something sensible that reflects the actual measurements - like having the motherboard temperature reading of -28C is probably an indicator that your 'compute' lines in /etc/sensors.conf are wrong.. unless of course you are an overclocking madman 
HTH. |
|
| Back to top |
|
|
wnelson
Tux's lil' helper
Joined: 03 Oct 2004
Posts: 83
|
| Posted: Wed Sep 21, 2005 1:06 pm Post subject: |
|
|
Also what version of lm_sensors are you using? Try using the latest CVS version for the latest device drivers. All you have to do is make user and make user_install.
_________________
P4 2.8Ghz @ 2.8Ghz SL6WT
Zalman CNPS7000-Cu
865PE Neo-2 LS BIOs 2.4
512mb Mushkin Level II
160GB Maxtor HD
Geforce 4 440MX
Antec 3700 1 exhaust and 1 intake fans
Linux 2.6.x
Linux user 314187 |
|
| Back to top |
|
|
Onturenio
n00b
Joined: 03 Sep 2005
Posts: 49
Location: Ontur
|
| Posted: Wed Sep 21, 2005 2:53 pm Post subject: |
|
|
I have not got i2c_core molule running, and i can't start it:
| Code: |
# modprobe i2c_core
FATAL: Module i2c_core not found.
|
But i don't know where is sitted in the kernel menu to activate it .
How can i to know what motherboard have i got? i thing it's a Clevo, and the chipset is SiS 645DX, but not sure.
Sorry, but what is CVS? I'm using lm_sensors-2.9.1. |
|
| Back to top |
|
|
Holderhek
n00b
Joined: 26 May 2005
Posts: 19
Location: Chile - Santiago
|
| Posted: Mon Oct 10, 2005 10:32 pm Post subject: |
|
|
Hello
I have the exactly same problem although I could make it work on Debian. I did the same on Gentoo and all I get is the RAM info.
What could be wrong?
Vigilant ~ # lsmod
Module Size Used by
w83627hf 29128 -
eeprom 5488 -
i2c_sensor 2720 -
i2c_isa 1536 -
i2c_sis96x 4356 -
nvidia 3464220 -
Vigilant ~ # sensors
eeprom-i2c-0-50
Adapter: SiS96x SMBus adapter at 0xe600
Memory type: DDR SDRAM DIMM
Memory size (MB): 512
And I have another problem: I installed the i2c core as module, but, as you can see in my lsmod, it is not loaded. I type modprobe i2c-core and it just wont load.
Please help
_________________
Usque ad gladium iterum procudiat |
|
| Back to top |
|
|
Holderhek
n00b
Joined: 26 May 2005
Posts: 19
Location: Chile - Santiago
|
| Posted: Wed Oct 19, 2005 10:41 am Post subject: |
|
|
Hello
Reading a lot of posts about the same, I found the answer of our problem Onturenio.
First, you dont have the module i2c core because you configured the i2c installed in the kernel, not as module.
You have:
| Code: | Device Drivers
+ I2C support
+ + [*] I2C support |
And Incabulos has:
| Code: | Device Drivers
+ I2C support
+ + [M] I2C support |
It really doesn't matter, the problem is not there, the problem is that from kernels 2.6.11 there is a bug, if you have enabled the opcion ACPI Plug and Play, the sensors wont work (incompatibilities or I dont know.)
So, to get the module w38627hf work you must disable the option that I told you:
| Code: | Device Drivers
+ Plug and Play support
+ + [ ] Plug and Play ACPI support (note, you must disable this) |
Well, I did that, recompiled my kernel, rebooted my machine and tried again with sensors-detect, ./lm_sensors start and executed sensors and all warked just fine.
I hope this helps. Please tell us if it worked and then change the title to [SOLVED] About sensors (if it worked)
Good luck
Bye
_________________
Usque ad gladium iterum procudiat |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
