Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
root@abacus:~# sensors-detect
# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# Board: Intel SE7520BD23D
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
Intel Core family thermal sensor... No
Intel Atom thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'... Yes
Found `Nat. Semi. PC87427 Super IO Fan Sensors' Success!
(address 0x700, driver `pc87427')
Found `Nat. Semi. PC87427 Super IO Health Sensors' Success!
(address 0x720, driver `to-be-written')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no):
Found `IPMI BMC SSIF'... Success!
(confidence 8, driver `ipmisensors')
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): yes
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): yes
Using driver `i2c-i801' for device 0000:00:1f.3: Intel 82801EB ICH5
Module i2c-dev loaded successfully.
Next adapter: SMBus I801 adapter at 0540 (i2c-0)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: I2C Voodoo3/Banshee adapter (i2c-1)
Do you want to scan it? (YES/no/selectively):
Next adapter: DDC Voodoo3/Banshee adapter (i2c-2)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Probing for `EDID EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `to-be-written':
* ISA bus, address 0x720
Chip `Nat. Semi. PC87427 Super IO Health Sensors' (confidence: 9)
Driver `ipmisensors':
* ISA bus
Chip `IPMI BMC SSIF' (confidence: 8)
Driver `pc87427':
* ISA bus, address 0x700
Chip `Nat. Semi. PC87427 Super IO Fan Sensors' (confidence: 9)
Note: there is no driver for Nat. Semi. PC87427 Super IO Health Sensors yet.
Check http://www.lm-sensors.org/wiki/Devices for updates.
Warning: the required module ipmisensors is not currently installed
on your system. If it is built into the kernel then it's OK.
Otherwise, check http://www.lm-sensors.org/wiki/Devices for
driver availability.
To load everything that is needed, add this to /etc/modules:
#----cut here----
# Adapter drivers
ipmi-si
# Chip drivers
pc87427
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!
Do you want to add these lines automatically to /etc/modules? (yes/NO)yes
Successful!
Monitoring programs won't work until the needed modules are
loaded. You may want to run '/etc/init.d/module-init-tools start'
to load them.
Unloading i2c-dev... OK
root@abacus:~# /etc/init.d/module-init-tools start
Loading kernel modules...done.
root@abacus:~#
And in the dmesg I get....
Code:
root@abacus:~# dmesg |grep -i ipmi
[ 6.714479] ipmi message handler version 39.2
[ 6.718343] IPMI System Interface driver.
[ 6.760594] ipmi_si: Unable to find any System Interface(s)
[ 6.818144] IPMI System Interface driver.
[ 6.892583] ipmi_si: Unable to find any System Interface(s)
[ 6.931632] IPMI System Interface driver.
[ 6.977581] ipmi_si: Unable to find any System Interface(s)
[ 7.016555] IPMI System Interface driver.
[ 7.065581] ipmi_si: Unable to find any System Interface(s)
[58013.982769] IPMI System Interface driver.
[58014.032698] ipmi_si: Unable to find any System Interface(s)
[58351.860438] IPMI Watchdog: driver initialized
[58361.543766] Copyright (C) 2004 MontaVista Software - IPMI Powerdown via sys_reboot.
[58474.252580] ipmi device interface
[58482.195416] IPMI System Interface driver.
[58482.236824] ipmi_si: Unable to find any System Interface(s)
[58524.397374] IPMI System Interface driver.
[58524.437743] ipmi_si: Unable to find any System Interface(s)
[59174.016435] IPMI System Interface driver.
[59174.057912] ipmi_si: Unable to find any System Interface(s)
[59989.836393] IPMI System Interface driver.
[59989.884738] ipmi_si: Unable to find any System Interface(s)
[60038.091423] IPMI System Interface driver.
[60038.136715] ipmi_si: Unable to find any System Interface(s)
root@abacus:~#
and even the command line...
Code:
root@abacus:~# modprobe ipmi_si
FATAL: Error inserting ipmi_si (/lib/modules/2.6.32-5-amd64/kernel/drivers/char/ipmi/ipmi_si.ko): No such device
root@abacus:~#
I tried googling but I haven't found anything that helps or is a recent HOW-TO (July 2004 is the newest I've found). What am i doing wrong?
I've been searching for answers everywhere, but I still can't come up with a solution. All my documentation says my mobo is v1.5 compliant at a minimum, dmesg even says thermal monitoring is present, but I can seem to get anything to work detecting it.
I've downloaded the source code from the Intel website... http://downloadcenter.intel.com/Deta...=ipmi&lang=eng but I'm running into issues compiling it. It requires the linux_source and linux_headers which I have installed. First I was getting the "Missing version.h file" warning, now after installing the headers I'me getting "Missing config.h file" warning. I did some searching and Debian doesn't use config.h files. I also couldn't find any references to it in the source code. The included build script also wants to create an RPM package but being a Debian Squeeze system (2.6.32)I don't have/use RPMs. If someone could take a look at the source code and help me figure out what I need to make it work on my system, I'd really appreciate it. My SE7520 Chipset is listed as compatible in the changelog. Right now I have no system monitoring.
(At one point in time I did try installing RHEL but that actually ran worse - slower - on the system and IPMI wasn't working on it either.)
I'm not quite catching what you are throwing. IPMI is not loading at all. I have the packages above installed, but they aren't talking to my hardware. I was trying to compile Intel's Linux driver for use on my system. I should have an /dev/imb, /dev/ipmi* etc loaded, but I don't. I need to get that working before I can get anything else to work. (don't I?)
I have stumbled upon your question while trying to get some sensor information out of my Fujitsu-Siemens Primergy RX200-S1 (Old piece of junk) that has IPMI 1.5 but is nowhere supported by neither of OpenIPMI or FreeIPMI(latest version 1.1.2).
For many reasons:
1) Its old hardware
2) Its BUGGY/PROPERTARY OEM implimentation of IPMI 1.5 standard
Cuz, I got the IPMI modules loaded and managed to see some info from my hardware but the BMC version, GUID information and all the sensor information is returning garbage (zeros, n/a, n/s <-whatever this means)... If I could just find the specs for Fujitsu's implementation I would extend FreeIPMI to support my server, but I couldn't...
So, I will just give up on finding how hot my processors are running since I don't have the time to research it anymore and probably won't find any documention on the actual implementation of the IPMI on this particular motherboard.
If anyone has some information on how to read the sensor information on this particular hardware I will be more than happy to listen to what you have to say.
However, mpyusko, for your problem I can give you my 2cents :
I see you are running the 64 bit version of the OS, that's probably the reason. The kernel module is not compiled for 64bits!
Is see that you have the i2c module loaded, as seen in your first post.
I think FreeIPMI can be configured to use the SSIF aka I2C interface to do the "in-band testing"(i.e. local information pulling), Haven't done it myself but I read about it here: http://ipmiutil.sourceforge.net/docs/ipmisw-compare.htm
# ipmitool sdr
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
Get Device ID command failed
Unable to open SDR for reading
Quote:
# modprobe ipmi_si
FATAL: Error inserting ipmi_si (/lib/modules/2.6.32-5-amd64/kernel/drivers/char/ipmi/ipmi_si.ko): No such device
Quote:
# modprobe ipmi_si type="kcs" addrs="0xca0"
FATAL: Error inserting ipmi_si (/lib/modules/2.6.32-5-amd64/kernel/drivers/char/ipmi/ipmi_si.ko): No such device
What I found out is the computer needs an add-in board (IMM) that contains the IPMI interfacing components. Apparently the BIOS is IPMI compatible, leaving the necessary channels open should the board be installed. Without it, IPMI will not load.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
IPMI is not loading at all. I have the packages above installed, but they aren't talking to my hardware. I was trying to compile Intel's Linux driver for use on my system. I should have an /dev/imb, /dev/ipmi* etc loaded, but I don't. I need to get that working before I can get anything else to work. (don't I?)
Hints...
