As a follow up, it seems my script for loading the ipmi kernel driver
was wrong.
/sbin/modprobe ipmi_msghandler
/sbin/modprobe ipmi_devintf
/sbin/modprobe ipmi_smb addr=0,0x42
/sbin/modprobe ipmi_watchdog
grep ipmidev /proc/devices
if [ $? != 0 ];
Hi Al.
Thanks for sticking with this.
On Jan 23, 2008 12:34 PM, Al Chu [EMAIL PROTECTED] wrote:
Hey Chris,
Well, its very evident that a lot of stuff does work. Lets try this
one:
ipmi-raw --no-probing -D SSIF --driver-address=0x42 --driver-
device=/dev/i2c-0 --register-spacing=1
You know, I think the vendor does claim that but I've never had any
experience with ipmi before until getting these servers. I was under
the impression that the only way to get detailed board information was
via ipmi. I tried using lm-sensors previously and I believe I only got
information
On Jan 23, 2008 3:57 PM, Al Chu [EMAIL PROTECTED] wrote:
You know, I think the vendor does claim that but I've never had any
experience with ipmi before until getting these servers. I was under
the impression that the only way to get detailed board information was
via ipmi. I tried using
[EMAIL PROTECTED]:~# bmc-info --no-probing -D SSIF --driver-address=0x42
--driver-device=/dev/i2c-0 --register-spacing=1
Device ID: 20
Device Revision: 1
[SDR Support]
Firmware Revision: 2.64
[Device Available (normal operation)]
IPMI Version:
On Tue, 2008-01-22 at 11:24 -0800, Al Chu wrote:
Hey Chris,
It looks like you can communicate w/ the BMC now, which is good. So we
need to figure out why the the SSIF driver is not working by default.
That's bug #1. I have a few ideas about it, hopefully I can deal with
that later.
Hey
On Jan 22, 2008 2:37 PM, Al Chu [EMAIL PROTECTED] wrote:
On Tue, 2008-01-22 at 11:24 -0800, Al Chu wrote:
Hey Chris,
It looks like you can communicate w/ the BMC now, which is good. So we
need to figure out why the the SSIF driver is not working by default.
That's bug #1. I have a few
On Jan 22, 2008 2:47 PM, Chris Morgan [EMAIL PROTECTED] wrote:
On Jan 22, 2008 2:24 PM, Al Chu [EMAIL PROTECTED] wrote:
Hey Chris,
It looks like you can communicate w/ the BMC now, which is good. So we
need to figure out why the the SSIF driver is not working by default.
That's bug #1.
On Jan 22, 2008 2:24 PM, Al Chu [EMAIL PROTECTED] wrote:
Hey Chris,
It looks like you can communicate w/ the BMC now, which is good. So we
need to figure out why the the SSIF driver is not working by default.
That's bug #1. I have a few ideas about it, hopefully I can deal with
that later.
Hey Chris,
The issue w/ ipmimonitoring is there is some bogus info being returned
from the BMC on your motherboard.
[ 0h] = sdr_version_major[ 4b]
[ 0h] = sdr_version_minor[ 4b]
[ 0h] = record_count[16b]
My code, which requires version number 0, is
On Tue, 2008-01-22 at 14:50 -0500, Chris Morgan wrote:
On Jan 22, 2008 2:37 PM, Al Chu [EMAIL PROTECTED] wrote:
On Tue, 2008-01-22 at 11:24 -0800, Al Chu wrote:
Hey Chris,
It looks like you can communicate w/ the BMC now, which is good. So we
need to figure out why the the SSIF
On Jan 22, 2008 4:59 PM, Al Chu [EMAIL PROTECTED] wrote:
Hey Chris,
The issue w/ ipmimonitoring is there is some bogus info being returned
from the BMC on your motherboard.
[ 0h] = sdr_version_major[ 4b]
[ 0h] = sdr_version_minor[ 4b]
[ 0h] =
On Tue, 2008-01-22 at 18:34 -0500, Chris Morgan wrote:
On Jan 22, 2008 4:59 PM, Al Chu [EMAIL PROTECTED] wrote:
Hey Chris,
The issue w/ ipmimonitoring is there is some bogus info being returned
from the BMC on your motherboard.
[ 0h] = sdr_version_major[ 4b]
[
On Jan 22, 2008 6:50 PM, Al Chu [EMAIL PROTECTED] wrote:
On Tue, 2008-01-22 at 18:34 -0500, Chris Morgan wrote:
On Jan 22, 2008 4:59 PM, Al Chu [EMAIL PROTECTED] wrote:
Hey Chris,
The issue w/ ipmimonitoring is there is some bogus info being returned
from the BMC on your
Hey Chris,
Could you try a few other commands too so we can get an idea what is
working/not working so far.
bmc-config --list
pef-config --list
ipmi-chassis -c
ipmi-chassis -s
Al
On Tue, 2008-01-22 at 19:01 -0500, Chris Morgan wrote:
On Jan 22, 2008 6:50 PM, Al Chu [EMAIL PROTECTED]
On Jan 22, 2008 7:15 PM, Al Chu [EMAIL PROTECTED] wrote:
Hey Chris,
Could you try a few other commands too so we can get an idea what is
working/not working so far.
bmc-config --list
[EMAIL PROTECTED]:~# bmc-config --list --debug
ipmi-udm.c: 642: ipmi_open_inband: errnum (5): expression
Hey Chris,
Sorry, could you run with all of the -D SSIF --register-spacing ...
etc.
Thanks,
Al
On Tue, 2008-01-22 at 20:40 -0500, Chris Morgan wrote:
On Jan 22, 2008 7:15 PM, Al Chu [EMAIL PROTECTED] wrote:
Hey Chris,
Could you try a few other commands too so we can get an idea what is
Hi Al,
I think, there is no such device address 42 and 84. I suspect a bug in
SSIF device driver code.
Regards,
Bala
[EMAIL PROTECTED]:~# bmc-info --no-probing -D SSIF --driver-address=42
--driver-device=/dev/i2c-0 --register-spacing=1
ipmi-ssif-api-udm.c: 81: ipmi_ssif_cmd_udm: errnum
Chris,
Is it possible you to compare ipmi-locate 'BMC SMBUS slave address' with
dmidecode output?
Also, please try Motherboard Manufacturer tools (if any) and let me know
the result.
Thanks,
Best Regards,
Bala
---
Free as in freedom
http://www.gnu.org/
On Jan 17, 2008 11:36 AM, Albert
dmidecode code is used inside device probing. If there is a difference in
ipmi-locate and latest dmidecode output, then we need to update our
dmidecode device probing code.
Regards,
Bala
---
Free as in freedom
http://www.gnu.org/
I don't think this would be a kernel related issue. Bala, you
Hey Bala,
How can we go about debugging this?
Al
On Mon, 2008-01-21 at 03:56 -0800, Bala.A wrote:
Hi Al,
I think, there is no such device address 42 and 84. I suspect a bug in
SSIF device driver code.
Regards,
Bala
[EMAIL PROTECTED]:~# bmc-info --no-probing -D SSIF
Here is the entire output from dmidecode, aplogizes because its a lot
of text but I wanted the entire output here for reference.
# dmidecode 2.9
SMBIOS 2.3 present.
50 structures occupying 2332 bytes.
Table at 0x000FCFD0.
Handle 0x, DMI type 0, 20 bytes
BIOS Information
Vendor: Intel
I found that base of number should be specified in --driver-address value.
Please try the following commands
bmc-info --no-probing -D SSIF --driver-address=0x42 \
--driver-device=/dev/i2c-0 --register-spacing=1
bmc-info --no-probing -D SSIF --driver-address=0x84 \
Any more ideas? Have there been any important kernel changes that
should cause me to try to upgrade to 2.6.24?
Chris
On Jan 17, 2008 11:44 AM, Chris Morgan [EMAIL PROTECTED] wrote:
On Jan 17, 2008 11:36 AM, Albert Chu [EMAIL PROTECTED] wrote:
Hi Bala. Thank you for replying.
On
I don't think this would be a kernel related issue. Bala, you have any
ideas?
Al
Any more ideas? Have there been any important kernel changes that
should cause me to try to upgrade to 2.6.24?
Chris
On Jan 17, 2008 11:44 AM, Chris Morgan [EMAIL PROTECTED] wrote:
On Jan 17, 2008 11:36
Hi Bala. Thank you for replying.
On Jan 16, 2008 11:10 PM, Bala.A [EMAIL PROTECTED] wrote:
Hi,
Please find inline replies
# ipmi-locate
Probing KCS device using DMIDECODE... FAILED
Probing SMIC device using DMIDECODE... FAILED
Probing BT device using DMIDECODE... FAILED
On Jan 17, 2008 11:36 AM, Albert Chu [EMAIL PROTECTED] wrote:
Hi Bala. Thank you for replying.
On Jan 16, 2008 11:10 PM, Bala.A [EMAIL PROTECTED] wrote:
Hi,
Please find inline replies
# ipmi-locate
Probing KCS device using DMIDECODE... FAILED
Probing SMIC device
Hi Bala. Thank you for replying.
On Jan 16, 2008 11:10 PM, Bala.A [EMAIL PROTECTED] wrote:
Hi,
Please find inline replies
# ipmi-locate
Probing KCS device using DMIDECODE... FAILED
Probing SMIC device using DMIDECODE... FAILED
Probing BT device using DMIDECODE... FAILED
Hey Chris,
I know a few intel boards use SSIF only, and the below does indicate SSIF
is the inband driver. Does ipmi-locate not find the SSIF device when it
probes via dmi?
Could you try giving ipmi-sensors the -D SSIF option to tell it to use
SSIF. I don't know too much about SSIF, so more
Hi Albert.
Replies inline.
On Jan 16, 2008 10:22 AM, Albert Chu [EMAIL PROTECTED] wrote:
Hey Chris,
I know a few intel boards use SSIF only, and the below does indicate SSIF
is the inband driver. Does ipmi-locate not find the SSIF device when it
probes via dmi?
I think it does use SSIF
On Jan 16, 2008 1:06 PM, Albert Chu [EMAIL PROTECTED] wrote:
Hey Chris,
I think it does use SSIF and I think ipmi-locate finds it. I listed
the output from ipmi-locate in my first mail and I think it listed a
SSIF device at the end of the output.
What about earlier in the output? The
Hi,
Please find inline replies
# ipmi-locate
Probing KCS device using DMIDECODE... FAILED
Probing SMIC device using DMIDECODE... FAILED
Probing BT device using DMIDECODE... FAILED
Probing SSIF device using DMIDECODE... done
IPMI Version: 1.5
IPMI locate driver: DMIDECODE
IPMI
I'm having trouble reading ipmi data with freeipmi and this particular
intel board. Running ubuntu gutsy, 2.6.22.
dmidecode outputs:
...
Handle 0x0030, DMI type 38, 18 bytes
IPMI Device Information
Interface Type: SSIF (SMBus System Interface)
Specification Version: 1.5
33 matches
Mail list logo
