Ok.  Well, I still think we should add the note to all in-band tools. 
So that users atleast know where to be pointed to. 

Al

--
Albert Chu
[EMAIL PROTECTED]
925-422-5311
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory


----- Original Message -----
From: Anand Babu <[EMAIL PROTECTED]>
Date: Tuesday, April 4, 2006 4:46 pm
Subject: Re: [Freeipmi-devel] 0.2.1 development patch

> Albert Chu wrote:
> >> You know right, On IBM e325, only ipmi-locate and bmc-info works 
> >> inband.BMC doesn't respond properly for other commands.
> > 
> > bmc-config works out of band, so it's not an ipmi compliance 
> issue with
> > the bmc commands.  If it can't work in-band w/ --noprobing, then
> > wouldn't it be a probing/locate issue in the fish code?
> 
> Problem is in crappy KCS controller. bmc-info when forced to work 
> on 
> IO-MAPPED KCS interface, it works OK. Rest of the tools don't. 
> Because 
> get_device_info is a simple IPMI command with no much data. bmc-config
> starts to fetch data and hangs in the middle.
> 
> It may be possible to tweak the KCS driver to work for this BMC, 
> But I 
> don't have access to e325 any more.
> 
> -- 
> Anand Babu
> GPG Key ID: 0x62E15A31
> Blog [http://ab.freeshell.org]
> The GNU Operating System [http://www.gnu.org]
> 
> 



_______________________________________________
Freeipmi-devel mailing list
Freeipmi-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/freeipmi-devel

Reply via email to