If I try to deactivate the existing session, I get:
> # ipmitool -U root -P calvin -H n003-bmc -I lanplus sol deactivate
> Info: SOL payload already de-activated
>
> Once it's in this state, the only thing I've been able to do to regain
> access to the serial console is re
is currently activated. The 1h = instance_1 indicates that SOL
> >>>> is active. But because instance_capacity is 0, I never look at it, so
> >>>> the calculation is that no SOL is currently active. ipmiconsole
> >>>> attempts to activate a SOL session as alw
On Mon, 2012-02-06 at 12:27 -0800, Götz Waschk wrote:
> On Mon, Feb 6, 2012 at 7:06 PM, Albert Chu wrote:
> > To create SEL events, we can use bmc-device and the --platform-event
> > option. I think the following would be the equivalent to what you've
> > seen before:
> >
> > bmc-device --platfor
Hey Gotz,
> "0x00 0xFF 0xFF"
> > "0x01 0xFF 0xFF"
> > "0x03 0xFF 0xFF"
Could you try a few more 0x04-0x0F
"0x04 0xFF 0xFF"
"0x05 0xFF 0xFF"
...
"0x0E 0xFF 0xFF"
"0x0F 0xFF 0xFF"
I suppose it's possible the Supermicro motherboards only report
overheats in the SEL but nothing self.
Al
On Tue,
Hey Gotz,
Well, I'm going to guess that "OVERHEAT" is the only SEL event that can
occur then. I'll work on a patch.
Al
On Tue, 2012-02-07 at 07:56 -0800, Götz Waschk wrote:
> On Tue, Feb 7, 2012 at 4:44 PM, Al Chu wrote:
> > Could you try a few more 0x04
http://ftp.gnu.org/gnu/freeipmi/freeipmi-1.1.2.tar.gz
FreeIPMI 1.1.2 - 02/06/12
-
Tools
--
o In ipmi-oem, support new Dell C410x OEM extensions
slot-power-toggle, slot-power-control, get-port-map, set-port-map.
o Fix daemon setup race condition in ipmidetectd and bmc-
2-07 at 08:28 -0800, Al Chu wrote:
> Hey Gotz,
>
> Well, I'm going to guess that "OVERHEAT" is the only SEL event that can
> occur then. I'll work on a patch.
>
> Al
>
> On Tue, 2012-02-07 at 07:56 -0800, Götz Waschk wrote:
> > On Tue, Feb 7, 20
You can pick specific sensors via the record-ID associated with the SDR
entry.
I'm not 100% sure what you're trying to program, but you may want to
consider looking at the libipmimonitoring library, which is a wrapper
that hides a lot of the sensor details. There is an example on the
FreeIPMI web
http://ftp.gnu.org/gnu/freeipmi/freeipmi-1.1.3.tar.gz
FreeIPMI 1.1.3 - 03/06/12
-
Tools
--
o Support Supermicro CPU temperature SEL events.
o In ipmi-oem, fix corner case with Dell C410x power control
calculation.
o In all tools, fix error messages to differentiate be
Hey Diego,
Good catch. To be consistent to some other code in FreeIPMI, I fixed it
a slightly different way.
Index: ipmiconsole/ipmiconsole-argp.c
===
--- ipmiconsole/ipmiconsole-argp.c (revision 8805)
+++ ipmiconsole/ipmiconso
Hey Diego,
I'm a little confused on the build problem this fixes. For ipmidetect,
it shouldn't be including libfreeipmi headers at all. In the daemonutil
case, the appropriate tools should be including libfreeipmi headers in
their makefiles.
Perhaps there's a "chain" of inclusions/linking that
Hi Diego,
Applied, thanks. I also added the support for ipmi-sel and the
--output-sensor-state/--output-event-state options.
However, proper --output-sensor-state support, I need to know what the
motherboard manufactuer ID is from bmc-info. Normally I don't need to
ask, but too many Supermicro
Great, it'll be in the next release.
Al
On Mon, 2012-06-18 at 01:46 -0700, Kurt Quehenberger wrote:
> Hi Al,
>
> thanks a lot for the fast support!
> I've tested the svn version, and it works out fine now!
> Please find my test-output of ipmi-sensors enclosed.
>
> Best regards,
> Kurt
>
> Am 2
Hi Corey,
On Sun, 2012-07-22 at 13:20 -0700, Corey Osman wrote:
> Hi,
>
> My ruby implementation is off to a great start but I had a few
> questions with regards to driver types and inband configuration.
>
> Since I will have no idea as to what kind of IPMI device needs to be
> controlled I need
Hi Diego,
It wouldn't be too hard to add the threshold output as new columns in
the ipmi-sensors output (it'll be a bit of work, but not an insane
amount). I'd have to make it an option to maintain the default output.
Is something like this what you are thinking of
1, Proc 1 Temp, Processor, 88.
Hi Corey,
On Sat, 2012-07-28 at 17:52 -0700, Corey Osman wrote:
> Its crucial that the return status actually return the correct
> results. ipmipower should return 1
> version = ipmipower - 1.1.6
I noticed this issue a few months back and fixed it in the main branch,
but elected not to backport
>
> Corey Osman
> co...@logicminds.biz
>
>
> Green IT and Data Center Automation Specialist
>
>
>
>
>
>
>
>
>
>
> On Jul 29, 2012, at 7:41 AM, Al Chu wrote:
>
> > Hi Corey,
> >
> > On Sat, 2012-07-28 at 17:52 -0700, C
ge_level[ 4b]
> > 192.168.1.22: [ 0h] = reserved2[ 4b]
> > 192.168.1.22: IPMI Trailer:
> > 192.168.1.22: --
> > 192.168.1.22: [ 3Dh] = checksum2[ 8b]
> > ipmi-chassis-config: connection timeout
> >
> >
> >
&
On Sun, 2012-07-29 at 11:48 -0700, Corey Osman wrote:
>
>
>
>
> On Jul 29, 2012, at 11:05 AM, Al Chu wrote:
>
> > Hey Corey,
> >
> > For some reason, on your system, HP motherboard sends extra data for
> > this particular IPMI payload.
>
>
>
>
>
>
>
>
>
>
> On Jul 29, 2012, at 12:18 PM, Al Chu wrote:
>
> > On Sun, 2012-07-29 at 11:48 -0700, Corey Osman wrote:
> > >
> > >
> > >
> > >
> > > On Jul 29, 2012, at 11:05 AM, Al Chu wrote:
&
p out.
The issue is the Get System Boot Options IPMI command and the "boot
flags" parameter selector. See Corey's previous link:
http://pastebin.com/6E9R9VNG
which shows a packet trace.
Al
> -- Jim Mankovich | jm...@hp.com --
>
> On 7/29/2012 1:18 PM, Al Chu wrote:
I'll put this on the TODO for a workaround in ipmi-sensors. I have to
think about how I might do this or if I can. It's just so specific to
HP's.
Al
On Wed, 2012-08-22 at 22:15 -0700, Diego Elio Pettenò wrote:
> On 22/08/2012 17:18, Albert Chu wrote:
> > Other than hard coding a workaround for
On Thu, 2013-05-02 at 16:34 +0200, Liebig, Holger wrote:
> >
> > I for one think that's a great idea. Do you happen to know of BMCs which
> > actually support the "Get SEL Time UTC Offset" command?
> [Liebig, Holger]
> I know at least one BMC base firmware provider which supports these 2
> option
Hi Dave,
Huh ... I'm sorta at a loss. The state_data->prog_data data structure
is pretty core. It's set once near the beginning in main and never
written to again once the main code is executed, which may include
threads if you're doing hostranges. Dunno if the threading could be
part of the p
Ping me after the new year and we can look at it more. I'd like to see
the debug output of a --bridge-sensors with one of those ambient
sensors.
That's the one I expected to work. Not what's going on. Could be some
subtle bug ... or possibly an internal timeout or something.
Al
On Fri, 2013-1
Hi Vinny,
The IPMI specification does not support the ability to retrieve/modify
BIOS options per se. The IPMI specification does allow modification of
various motherboard parameters, many of which may happen to be
readable/modifiable/managed by the BIOS.
So if you are looking to use IPMI for qu
ware
versions in ipmi-oem. However, again, it's not necessarily the BIOS
version.
Al
>
> I'll check out your suggestions to see what is configurable and what
> the vendors have added.
>
>
>
>
>
> Thanks,
>
>
>
> Vinny
>
>
>
&
cing with use the same rev
> number for all their device firmware, I may be able to simply query for the
> IPMI firmware version number, correct? Assuming this is part of the IPMI
> spec?
>
>
>
> -----Original Message-
> From: Al Chu [mailto:ch...@llnl.gov]
>
gt; Sent: Tuesday, January 07, 2014 5:02 PM
> To: Vinny Vallarine; Al Chu
> Cc: freeipmi-devel@gnu.org
> Subject: RE: [SPAM] - RE: [Freeipmi-devel] Retrieving BIOS information via
> IPMI - Email found in subject
>
> Did you try with the "--get-system-info" option? T
Try them as command line parameters.
bmc-info -l admin ...
Al
On Wed, 2014-01-08 at 07:59 -0500, Vinny Vallarine wrote:
> Not entirely sure what you mean by this. Could you clarify?
>
> -Original Message-
> From: Al Chu [mailto:ch...@llnl.gov]
> Sent: Tuesday, Januar
008.html
>
> does this ring any bells? My IPMI firmware is 2.34 and freeipmi package is
> at rev 1.3.4 so much latter then the rev mentioned in the article.
>
>
> Thanks,
>
> Vinny
>
> -Original Message-
> From: Al Chu [mailto:ch...@llnl.gov]
> Sent:
ring any bells? My IPMI firmware is 2.34 and freeipmi package is
> at rev 1.3.4 so much latter then the rev mentioned in the article.
>
>
> Thanks,
>
> Vinny
>
> -Original Message-
> From: Al Chu [mailto:ch...@llnl.gov]
> Sent: Wednesday, January 08, 201
Hi Chandan,
Are you looking for a one-time build w/ this new libtool so you can try
it on ppc64le machines? Or are you hoping I will use the newer libtool
for future FreeIPMI releases?
The latter is more difficult for me todo, but I could do a one-off for
ppc64le people to try out.
Is this rela
> Thanks
> Chandan
> On Tue, 2014-01-14 at 09:20 -0800, Al Chu wrote:
> > Hi Chandan,
> >
> > Are you looking for a one-time build w/ this new libtool so you can try
> > it on ppc64le machines? Or are you hoping I will use the newer libtool
> > for future Fr
On Wed, 2014-01-15 at 08:17 -0800, Al Chu wrote:
> Hi Chandan,
>
> I can do it for 1.3.4 and release a special tarball just for this newer
> libtool, and perhaps on-demand as it is needed. But I cannot update the
> build process to use it everytime.
I should say ... can
Hi Shashi,
The patch as a whole looks fine, but how about a few tweaks. Comments
inlined below.
On Wed, 2014-05-07 at 21:34 +, Dande, Shashi wrote:
> Hi Albert
>
> I have attached the patch file to this e-mail per your advice.
>
> I have also copied the content below for your reference.
>
t; fiid_obj_t obj_cmd_rq,
> fiid_obj_t obj_cmd_rs);
>
> -Original Message-
> From: Albert Chu [mailto:ch...@llnl.gov]
> Sent: Thursday, May 29, 2014 2:16 PM
> To: Dande, Shashi
> Subject: RE: FreeIPMI Patch Submission
>
> Hi
Hi,
The most likely issue you're hitting is a bug on many Dell Poweredge
motherboards. If you use this workaround, "-W ignorescanningdisabled",
it should work around. Short description of the workaround, the Dell
motherboards say that a sensor is disabled, but in reality it isn't.
Other possibi
So looking things over, the reason it doesn't support multiple inputs is
due to a architectural decision, mostly lifting conf-file parsing from
many of the other FreeIPMI tools.
Perhaps not the prettiest, but I think the simplest fix is to increase
the max size listed below. Could you give it a t
Hey Florian,
I have an experimental branch called ipmimonitoring-discrete-reading on
github here:
https://github.com/chu11/freeipmi-mirror/tree/ipmimonitoring-discrete-r
eading
./autogen.sh
./configure
make
make install
re-compile ipmimonitoring-sensors.c and try it out
LMK if you need help, li
Hi Andreas,
Unfortunately, I may not be able to add this one to FreeIPMI. The
sensor type "OEM Reserved" indicates it is a OEM specific sensor (I'm
not sure how you arrived at 00B?).
The 6Fh indicates that the events associated with this OEM sensor are
unique to the sensor. So while we may have
https://ftp.gnu.org/gnu/freeipmi/freeipmi-1.6.5.tar.gz
Updates in
o Add FRU parsing workaround for Fujitsu Primergy RX1330, in which a
CEh is used to indicate that no FRU data is available.
o Misc minor fixes.
Al
--
Albert Chu
ch...@llnl.gov
Computer Scientist
High Performance Systems Divisi
Hi,
We don't distribute RPMs. However, the following should work on most
RHEL systems if you have all the appropriate development tools
installed.
rpmbuild -ta freeipmi-VERSION.tar.gz
Al
On Wed, 2020-07-01 at 13:33 +, Wajahath, Mohammad M. wrote:
> Dear Sir,
>
> Hope you are fine.
>
>
Hi Andrew,
Thanks for the report. Since this is a OEM specific command, there is
a good chance this just isn't supported on your motherboard. There is
no way to know what Supermicro may have meant with the 0x83 error code.
Al
On Thu, 2020-08-20 at 18:28 -0400, Andrew Orme wrote:
> admin@server
27;s sometimes an
issue.
Al
> On Wed, Aug 26, 2020 at 1:07 PM Al Chu wrote:
> > Hi Andrew,
> >
> > Thanks for the report. Since this is a OEM specific command, there
> > is
> > a good chance this just isn't supported on your motherboard. There
> > is
w to give firmware fixes, but having
> > the latest available firmware helps.
> >
> > On Thu, Aug 27, 2020 at 2:08 PM Al Chu wrote:
> > > On Thu, 2020-08-27 at 14:04 -0400, Andrew Orme wrote:
> > >
> > >
> > > >
Hi Christian,
LGTM, thanks and thanks for the thorough description. I'm not a
computer that I can apply right now, but will do so later.
This seems like a critical enough bug to do a new release, i will try
to do so by the end of the week.
Al
On Thu, 2020-09-03 at 09:14 +0200, Christian Ehrhar
Hey Christian,
I've applied the patch, thanks! Just wondering how bad this is and if
it warrants a FreeIPMI release. It sounds like on certain systems, a
segfault was probably happening all the time?
Al
On Thu, 2020-09-03 at 02:50 -0700, Al Chu wrote:
> Hi Christian,
>
> LG
Hey Bruce,
Thanks, just wanted to double check. I'll do a release soon.
Al
On Thu, 2020-09-03 at 14:08 -0700, Bryce Harrington wrote:
> On Thu, Sep 03, 2020 at 10:58:20AM -0700, Al Chu wrote:
> > Hey Christian,
> >
> > I've applied the patch, thanks! Just wonde
https://ftp.gnu.org/gnu/freeipmi/freeipmi-1.6.6.tar.gz
o In libfreeipmi, fix segfault in SPMI parsing leading to immediate
failures on some hardware across all tools.
Al
--
Albert Chu
ch...@llnl.gov
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory
Hi George,
> What would I need to do in order to provide dcmi-like support for
> this board in freeipmi?
Have you been able to confirm that the board you have supports DCMI? I
believe you can check with the --get-dcmi-capability-info option. If
DCMI is supported, perhaps there's simply a bug an
There is no guarantee that your ilo5 will export the same sensors as
ilo4. I would contact your vendor to determine what sensors are
available / not available.
You can also try see if some of the workarounds in ipmi-sensors help
display more sensors.
Al
On Tue, 2020-12-22 at 12:01 +0100, Robi
Hi Fabio,
I think that's a good point. And the same argument can maybe be made
for `ipmipower` since it has no "in-band" component. Both are in
/usr/sbin mostly b/c everything else there is.
My one concern is that it's been in /usr/sbin for so long, I'm not sure
how many people may have hard co
Hi Fabio,
Actually thinking about this more, could this argument be made for all
FreeIPMI tools that do out of band communication? On my local redhat
system, I notice they put ipmitool in /usr/bin.
Just wanting to know your opinion on this.
Al
On Sat, 2021-02-06 at 09:50 -0800, Al Chu wrote
Hi Fabio,
Thanks! I suspect the 755 permissions were cut & paste from the old
init scripts. Fix will be there in the next FreeIPMI release.
Al
On Sat, 2021-02-06 at 21:23 +0100, Fabio Fantoni wrote:
> Hi, until now debian packages used its service files instead the
> upstream ones, now for nex
Hi Fabio,
Thanks, I've decreased it and other conf files to 640. I never caught
this b/c the permissions were overwritten to 0600 in the RPM spec
files.
Al
On Sun, 2021-02-07 at 13:17 +0100, Fabio Fantoni wrote:
> Hi, freeipmi.conf could contain sensitive informations, default
> permission sett
Hi Fabio,
Thanks, will fixup in the master branch and merge down into the stable
1.6.X branch.
And yes, savannah hosts the official git repo.
Al
On Sun, 2021-02-07 at 13:55 +0100, Fabio Fantoni wrote:
> Lintian in debian packages (of freeipmi 1.6.6) spotted a list of
> minor
> errors like spell
bution?
> it is better to ask someone else's opinion, especially someone more
> experienced than me
I will ask some power users at my company and ask their opinion.
Al
On Sun, 2021-02-07 at 18:43 +0100, Fabio Fantoni wrote:
> Il 06/02/2021 18:56, Al Chu ha scritto:
> > Hi Fab
On Sun, 2021-02-07 at 19:34 +0100, Fabio Fantoni wrote:
> Il 07/02/2021 19:10, Al Chu ha scritto:
> > Hi Fabio,
> >
> > Thanks, I've decreased it and other conf files to 640. I never
> > caught
> > this b/c the permissions were overwritten to 0600 in the RPM
Hi Ian,
It will be a tad slow going unfortunately, as you're trying to do
multiple steps :-) My recommendation:
- look at the code at bmc-info (which is far simpler), use that to get
an idea of how to setup an IPMI connection.
- once you get that, look at the code ipmi-sensors to see how to rea
https://ftp.gnu.org/gnu/freeipmi/freeipmi-1.6.9.tar.gz
o Support --with-systemconfigdir build option.
o Fix build issue on musl where putmsg/getmsg are not available.
o Fix build issue when inb/outb are not available on some systems.
o Fix static build issues with gcrypt.
o Add conserver documenta
Thanks, these all look. Applied all to master and will backport to 1.6.X
stable branch.
Al
On 11/3/22 19:12, Sam James wrote:
> This achieves the same effect as it'll use -D_GNU_SOURCE when possible
> but it ensures we never forget it in an individual Makefile.am.
>
> AC_USE_SYSTEM_EXTENSIONS w
0x52 0x07 0x78 0x01 0x88
InputVoltage
0x78 first PowerSupply
0x7a second PowerSupply
raw 0x06 0x52 0x07 0x78 0x01 0x90 Fan1
raw 0x06 0x52 0x07 0x78 0x01 0x91 Fan2
The's my old articl.
Андрей Грехов
--
Al Chu
Livermore Computing
Lawrence Livermore National Laboratory
A bunch of x9dr7 and sc-826TQ works only for FRU addresses.
Does
ipmi-oem supermicro get-power-supply-status 1|2|3
work for the older ones?
Al
On 9/4/23 21:46, Андрей Грехов wrote:
Hi.
Понедельник, 4 сентября 2023, 22:27 +07:00 от "Al Chu" :
Hi,
I believe this is already imple
tions.
Al
--
Al Chu
Livermore Computing
Lawrence Livermore National Laboratory
Oops!
FreeIPMI 1.6.14 - 01/27/24
--
o Fix build issue common to non-x86 systems.
https://ftp.gnu.org/gnu/freeipmi/freeipmi-1.6.14.tar.gz
Al
--
Al Chu
Livermore Computing
Lawrence Livermore National Laboratory
tring (ipv6_data.source)) < 0)
+
get_dynamic_address_source_type_string (ipv6_data.source)) < 0)
return (IPMI_CONFIG_ERR_FATAL_ERROR);
rv = IPMI_CONFIG_ERR_SUCCESS;
-
which keeps using ipv6_data.source, which looks uninitialized. This
put (state_data,
kv,
-
get_dynamic_address_source_string (ipv6_data.source)) < 0)
+
get_dynamic_address_source_type_string (ipv6_data.source)) < 0)
return (IPMI_CONFIG_ERR_FATAL_ERROR);
rv = IPMI
scribed to freeipmi-devel
today? I'm not sure what was up with gnu's mailman, but hopefully it's
fixed now.
Al
On 2/21/24 09:25, Pavel Cahyna wrote:
On Wed, Feb 21, 2024 at 09:04:13AM -0800, Al Chu wrote:
On 2/21/24 03:37, Pavel Cahyna wrote:
[ please Cc: me in replies, I
Hey Pavel,
That's awesome. Thanks!
Al
On 2/21/24 13:09, Pavel Cahyna wrote:
On Wed, Feb 21, 2024 at 09:50:35AM -0800, Al Chu wrote:
Yeah, to verify you'd need a BMC that has the ability to configure a dynamic
IP address.
I found that I have such a system, actually, so I tried t
, what do you think
about it? If we reach an agreement on this, I can start working on the
change and send patches.
Best regards,
Pavel Cahyna
Red Hat
--
Al Chu
Livermore Computing
Lawrence Livermore National Laboratory
ation).
Best regards, Pavel
On Wed, Jun 26, 2024 at 11:10:41AM -0700, Al Chu wrote:
Hi Pavel,
You guessed correctly, linking with libgcrypt was specifically due to
licensing issues with openssl when I wrote all that code eons ago (e
2005-ish?).
Skimming the libfreeipmi code, I think the `libc
A.B, Bala,
The ipmi lan stuff is completely broken. I'm not sure what was intended
in the ipmi_sendto() changes, but it's broke.
Al
On Mon, 2006-06-26 at 07:43 -0700, Anand Babu wrote:
> Hi Al,
> Uploaded 0.2.2 release. We have done testing from outside. Please test
> and approve before I make
Hey Anand,
Are you referring to bmc-config? After bmc-config trys to get ipmi 2.0
data (i.e. sol info) subsequent calls in bmc-config fail? Is this in-
band or out-of-band?
Also when you say "subsequent ipmi calls fail" do you mean "return an
error" or "don't respond"?
Also what kind of mach
> > Also when you say "subsequent ipmi calls fail" do you mean "return an
> > error" or "don't respond"?
>
> "return an error". ALL subsequent calls, both 2.0 calls and 1.x calls.
> I"m guessing probably the ipmi_device_t got 'closed' somehow?
What's the completion code?
Al
--
Albert Chu
[
Hi Anand,
I haven't built yet, so I apologize if I'm way off base. These comments
are based on just skimming the code (and prior discussions with you and
others).
1) It seems that both "Password20" and "Password" would be output on a
bmc-config --checkout. Only one should be output.
2) In fun
> A commit wont ignore a blank, It will see if blank is valid via that
> key's validate () function (which is valid only for password) and error
> out.
Ok cool.
> 0 means `autodetect'. It inspects if the initial part of the string is
> "0x" or "0" or otherwise and according treats the string as h
> I can't recall if you can checkout k_r or k_g keys. If we can't, then the
> above also holds for k_r and k_g.
I double checked, and it seems you can checkout k_r and k_g, so the
previous comments I made don't apply to k_r and k_g.
Al
--
Albert Chu
[EMAIL PROTECTED]
925-422-5311
Computer Scie
On Thu, 2006-07-06 at 09:02 -0700, Anand Avati wrote:
> Every keyvalue's ->validate () is called in the 1st pass. there i could
> set two global variables passwd_is_specified and passwd20_is_specified
> and check for the other not being set and set this.
Yeah, I think that would work. Just commen
> Also I have fixed a bug in ipmi_lan_sendto() in Release-0_2_0_branch.
I believe A.B. said we were just going to revert those changes and go
back to the codebase at 0.2.1?
Al
--
Albert Chu
[EMAIL PROTECTED]
925-422-5311
Computer Scientist
High Performance Systems Division
Lawrence Livermore Na
One other thought.
We should also test to see if the output of "Password20" makes sense,
since it won't on many IPMI 1.5 machines. I think it would be
sufficient to run the Set user Password command and try to test a dummy
20 byte password. If the result comes back "invalid input" (I think
th
On Fri, 2006-07-07 at 15:20 -0700, Anand Babu wrote:
> This bug was introduced because of re-transmission feature. I thought,
> that feature was required, so we fix the bug.
These functions were nearly entirely re-written. I have no idea why.
All retransmission code should only be in the UDM cod
Hey Bala,
The issue is that this was a maintenance branch, so that code should
have never been "cleaned up", if there were actually no bugs.
I still think we should still revert the code, so that the differences
between the different releases are still kept to a minimum.
Al
On Fri, 2006-07-07 a
> now freeipmi main branch has C version of ipmi-sel. I have removed scheme
> version of ipmi-sel.
Just remembered, how will we be dealing with bug #16278?
http://savannah.gnu.org/bugs/?func=detailitem&item_id=16278
Al
--
Albert Chu
[EMAIL PROTECTED]
925-422-5311
Computer Scientist
High Perfo
On threshold based events (ipmi 2.0 spec, Table 29-6, row #1 event
data), ipmi-sel outputs something generic like:
1:31-Dec-1969 16:00:24:Voltage #88:Lower Critical - going low:Trigger
reading = 1Eh:Trigger reading = 49h
It should output the actual sensor values:
1:31-Dec-1969 16:00:24:Voltage #
Is there a portability issue on some OS that makes this function a
requirement? I see no reason for it:
A) The IPMI ports are < 1023, which means they are reserved ports
B) Reserved ports shouldn't be gained via an ephemeral port (i.e. bind
to port 0).
Unless there is some wierd OS where 'B' is
No responses, I'll take it there is no issue then.
Al
On Tue, 2006-07-18 at 14:33 -0700, Al Chu wrote:
> Is there a portability issue on some OS that makes this function a
> requirement? I see no reason for it:
>
> A) The IPMI ports are < 1023, which means they are r
Hi David,
I'm not too sure off the top of my head. One of the other developers
might have a better idea.
Admittedly, I sometimes do the "binary search" thing with my input files
(comment out certain chunks, see if it works or not, etc).
One of the developers has re-done bmc-config. So we hop
Hi Bala,
To me, it makes sense to remove 'defaults' from the tool ipmi-locate.
But for library probing, I feel it must still be there.
If there manufacturer offers no inband information for IPMI (through
smbios, dmi, or pci), then at the bare minimum you can try the IPMI
defaults. If you don't
> RPM packages will be available shortly.
Doh! Either logins to the ftp site are broken, or I've forgotten the
login/pass :-(
So RPMs will be available once somebody else can upload them or I get
the login/pass.
Sorry for the delay,
Al
--
Albert Chu
[EMAIL PROTECTED]
925-422-5311
Computer S
is this going to be ported to work with the C version?
Al
--
Albert Chu
[EMAIL PROTECTED]
925-422-5311
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory
___
Freeipmi-devel mailing list
Freeipmi-devel@gnu.org
gt; Al,
> bmc-autoconfig uses bmc-config tool and whether C or scheme, if the
> command line optins still mean the same, it should work.
>
> avati
>
> On Wed, Jul 26, 2006 at 10:56:08AM -0700, Al Chu wrote:
> > is this going to be ported to work with the C version?
&g
Do you think you'd have time to do this Anand? Bmc-autoconfig still
needs a manpage as well.
Al
On Thu, 2006-07-27 at 01:21 +0530, Anand V. Avati wrote:
> > Well, with fish going away in 0.3.0, where should bmc-autoconfig be put
> > then? It clearly doesn't belong under fish/scripts/bmc-autocon
Cool, thanks.
Al
On Wed, 2006-07-26 at 15:26 -0700, Anand Avati wrote:
> > Do you think you'd have time to do this Anand? Bmc-autoconfig still
> > needs a manpage as well.
>
> done,
> avati
>
--
Albert Chu
[EMAIL PROTECTED]
925-422-5311
Computer Scientist
High Performance Systems Division
Law
mc-autoconfig --usage' for more
information.
Thanks,
Al
On Wed, 2006-07-26 at 15:29 -0700, Al Chu wrote:
> Cool, thanks.
>
> Al
> On Wed, 2006-07-26 at 15:26 -0700, Anand Avati wrote:
> > > Do you think you'd have time to do this Anand? Bmc-autoconfig still
There's been a lot of e-mails flying around. I just wanted to get a
summary of the remaining goals before release of 0.3.0.
A) ipmi-sensors: scheme to C conversion
B) bmc-autoconfig: fixed for new bmc-config
C) ipmi-sel: proper trigger output fix
D) Remove Fish
E) debug dumping for all tools
F) i
-0700, Al Chu wrote:
> There's been a lot of e-mails flying around. I just wanted to get a
> summary of the remaining goals before release of 0.3.0.
>
> A) ipmi-sensors: scheme to C conversion
> B) bmc-autoconfig: fixed for new bmc-config
> C) ipmi-sel: proper trigger output f
On Thu, 2006-07-27 at 14:26 -0700, Al Chu wrote:
> I thought of one other possibility. Should we add OpenIPMI in-band
> driver support?
Well, I'm going to work on it. So it's going to be in 0.3.0 now. :P
Al
> The issue I see is some users may want to use FreeIPMI softwar
Hi Ingo,
Great. Thanks for the patch.
> - Several *_commit functions in bmc-sol-conf-section.c used to
>free the kv->value before actually parsing it, resulting in
>the actual parameter being set to 0.
ARGH! This code worked on another machine. I suppose the randomness
of the compile/
Hi Vijay,
I'd be glad to help. I don't quite understand the question though.
Could you rephrase?
Al
On Mon, 2006-09-11 at 11:41 -0700, vijay v wrote:
> There was a broken thread about discovey option ... couldnt figure out
> much from discovery.scm too...
>
> I want a simple C/C++ application
1 - 100 of 431 matches
Mail list logo
