I have tried to use lm-sensors package on my Intel ISP 1100 server featuring motherboard SCB 2
after sensors-detect and loading found modules the output looks like that:
eeprom-i2c-0-50
Adapter: SMBus OSB4/CSB5 adapter at 0580
Algorithm: Non-I2C SMBus adapter
Memory type: SDRAM DIMM SPD
SDRAM Size (MB): 256
eeprom-i2c-0-53
Adapter: SMBus OSB4/CSB5 adapter at 0580
Algorithm: Non-I2C SMBus adapter
Memory type: SDRAM DIMM SPD
SDRAM Size (MB): 256
i can see no temperatures and other details, just the RAM assignment. How to fix the problem to be able to see sensors temperatures, fan speeds, power voltages etc... ?
My lspci is there:
00:00.0 Host bridge: ServerWorks CNB20HE Host Bridge (rev 23)
00:00.1 Host bridge: ServerWorks CNB20HE Host Bridge (rev 01)
00:00.2 Host bridge: ServerWorks: Unknown device 0006 (rev 01)
00:00.3 Host bridge: ServerWorks: Unknown device 0006 (rev 01)
00:02.0 RAID bus controller: Promise Technology, Inc. 20267 (rev 02)
00:03.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 0d)
00:04.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 0d)
00:0c.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
00:0f.0 ISA bridge: ServerWorks CSB5 South Bridge (rev 92)
00:0f.1 IDE interface: ServerWorks CSB5 IDE Controller (rev 92)
00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (rev 05)
00:0f.3 Host bridge: ServerWorks: Unknown device 0230
and output of sensors-detect here:
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): Probing for PCI bus adapters...
Use driver `i2c-piix4' for device 00:0f.0: ServerWorks South Bridge
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Load `i2c-piix4' (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. If you have a PIIX4, that often
includes addresses 0x69 and/or 0x6a.
Next adapter: SMBus OSB4/CSB5 adapter at 0580 (Non-I2C SMBus adapter)
Do you want to scan it? (YES/no/selectively): Client found at address 0x4e
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM75'... Success!
(confidence 3, driver `lm75')
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 `Dallas Semiconductor DS1621'... 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!
Probing for `ITE IT8705F / IT8712F'... Failed!
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 `ITE IT8705F / IT8712F'... Failed!
Probing for `Serial EEPROM (PC-100 DIMM)'... Success!
(confidence 8, driver `eeprom')
Probing for `DDC monitor'... Failed!
Client found at address 0x53
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 `ITE IT8705F / IT8712F'... Failed!
Probing for `Serial EEPROM (PC-100 DIMM)'... Success!
(confidence 8, driver `eeprom')
Client found at address 0x60
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 `ITE IT8705F / IT8712F'... Failed!
Client found at address 0x61
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 `ITE IT8705F / IT8712F'... Failed!
Client found at address 0x62
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 `ITE IT8705F / IT8712F'... Failed!
Client found at address 0x63
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 `ITE IT8705F / IT8712F'... Failed!
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... 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 VT 82C686 Integrated Sensors'
Trying general detect... Failed!
Probing for `ITE IT8705F / IT8712F'
Trying address 0x0290... Failed!
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `lm75' (may not be inserted):
Misdetects:
* Bus `SMBus OSB4/CSB5 adapter at 0580' (Non-I2C SMBus adapter)
Busdriver `UNKNOWN', I2C address 0x4e
Chip `National Semiconductor LM75' (confidence: 3)
Driver `adm1021' (should be inserted but causes problems):
Detects correctly:
* Bus `SMBus OSB4/CSB5 adapter at 0580' (Non-I2C SMBus adapter)
Busdriver `UNKNOWN', I2C address 0x4e
Chip `National Semiconductor LM84' (confidence: 6)
Misdetects:
* Bus `SMBus OSB4/CSB5 adapter at 0580' (Non-I2C SMBus adapter)
Busdriver `UNKNOWN', I2C address 0x4e
Chip `Maxim MAX1617' (confidence: 3)
Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `SMBus OSB4/CSB5 adapter at 0580' (Non-I2C SMBus adapter)
Busdriver `UNKNOWN', I2C address 0x50
Chip `Serial EEPROM (PC-100 DIMM)' (confidence: 8)
* Bus `SMBus OSB4/CSB5 adapter at 0580' (Non-I2C SMBus adapter)
Busdriver `UNKNOWN', I2C address 0x53
Chip `Serial EEPROM (PC-100 DIMM)' (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)?
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 unknown adapter SMBus OSB4/CSB5 adapter at 0580 using Non-I2C SMBus adapter
# I2C chip drivers
modprobe adm1021
modprobe eeprom
#----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,0x4e
#----cut here----
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20020424/4c6f85d3/attachment.html
