public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Egan Ford" <egan@sense.net>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] EMP/IPMI and Lion
Date: Mon, 08 Apr 2002 16:09:53 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905406@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805842@msgid-missing>

If all you want is simple power on/off/state/reset with a simple CLU,
then use kimberlite.

You will need to use smConfig, set the port (COM2:) to 19200 and "Always
Active".

http://oss.missioncriticallinux.com/projects/kimberlite/download.php

EMP patch:

http://gort.metaparadigm.com/

>-----Original Message-----
>From: linux-ia64-admin@linuxia64.org 
>[mailto:linux-ia64-admin@linuxia64.org] On Behalf Of Aaron Burt
>Sent: Friday, April 05, 2002 4:36 PM
>To: linux-ia64@linuxia64.org
>Subject: Re: [Linux-ia64] EMP/IPMI and Lion
>
>
>On Tue, 15 Jan 2002, Egan Ford wrote:
>> Has anyone made use of the IPMI/BMC/EMP hardware on the Lion (4-way 
>> SMP) boxes with Linux?  Looking for links, tip, or hints.
>
>Sorry to reply to a stale message, but I just tested VACM's 
>EMP module on our four Lions (2 from HP, 2 from IBM).  Works 
>fine, or at least as well as VACM ever works. 
>http://vacm.sourceforge.net/
>
>You do have to use the smConfig 
>utility to enable the EMP.
>
>If anyone's aware of any other Linux utilities that talk EMP, 
>I'd be very interested.
>
>
>_______________________________________________
>Linux-IA64 mailing list
>Linux-IA64@linuxia64.org 
>http://lists.linuxia64.org/lists/listinfo/linux>-ia64
>



      parent reply	other threads:[~2002-04-08 16:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-15 23:29 [Linux-ia64] EMP/IPMI and Lion Egan Ford
2002-04-05 23:35 ` Aaron Burt
2002-04-08 16:09 ` Egan Ford [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-ia64-105590701905406@msgid-missing \
    --to=egan@sense.net \
    --cc=linux-ia64@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox