Need info on ESM driver and 1950

[Naidu Bollineni]

I see the newer dmidecode is working ok.
I need to deal with h/w component tracking, failures etc, and also IPMI
working. Anybody tried OMSA5.x and openIPMI on RH9 with 1950?

Thanks,
Naidu Bollineni
Senior Member Technical Staff
Kazeon Systems
naidu at kazeon.com
www.kazeon.com

-----Original Message-----
From: Matt Domsch [mailto:Matt_Domsch at dell.com] 
Sent: Monday, August 28, 2006 10:34 AM
To: Naidu Bollineni
Cc: linux-poweredge at dell.com
Subject: Re: Need info on ESM driver and 1950

On Mon, Aug 28, 2006 at 10:19:50AM -0700, Naidu Bollineni wrote:
> Thanks for the response.
> Our functional needs are - IPMI, Component recognition and failure
> reporting, and dmidecode working.
> 
> What I didn't report last time was about dmidecode failing on 1950
with
> the following set of errors repeatedly: I hope this can give any
clues.
> 
> 	DMI 2.4 present.
> 	62 structures occupying 3131 bytes.
> 	DMI table at 0xCFFBC000.
> 	dmi: read: Illegal seek

That's a different problem.  You need a newer copy of dmidecode that
uses mmap(/dev/mem) rather than seeking.  This structure is in high
memory, which isn't seek-able on /dev/mem, but is mmap'able.

> I am hoping IPMI will work as openIPMI says with PE1950. I need
> dmidecode to work, and I am not sure why it is failing. And I need to
> know how to track all components and their failures.

You'll want to use OMSA 5.x to do this, that's why it exists.  To run
OMSA 5.x, you'll need to be running an OMSA-supported OS, such as
RHEL3, RHEL4, SLES9, or (soon) SLES10.

Thanks,
Matt

-- 
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com