[coreboot] KGPE-D16 BMC port

Timothy Pearson tpearson at raptorengineering.com
Tue Aug 29 20:24:16 CEST 2017


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We are pleased to announce that the OpenBMC port for the KGPE-D16 has
reached the first release stage!

https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php

While it has inherited some of the rough edges of its Facebook
predecessor in terms of its external interfaces, this OpenBMC port is
fully functional for system control and thermal management.  We have
tested both ASMB4 and ASMB5 modules with the KGPE-D16 and both function
the same, so feel free to purchase whichever one is more readily
available in your location.

The weakest part of the port at this time is IPMI (provided by ipmid).
Only the chassis status command really works at this point, but all of
the "plumbing" is present that is required for both external
(network-based) and internal (LPC KCS-based) communication; the ipmitool
utility does have the ability to communicate with the BMC as of this
release.  You may need to modprobe ipmi_si and ipmi_devintf before
ipmitool will function, depending on your distribution's default settings.

One final note: if you enable OpenBMC, don't try to run fan-control
under Linux.  It will cause the hardware control chip on the shared I2C
bus to malfunction, and the BMC will detect this and shut the entire
system down to protect it from overtemperature.  No permanent harm will
be done, but data loss is possible.  The best thing to do is to make
sure the w83795 module is not loaded on the host.

Also, since I think this was buried in another Email thread, I'd like to
mention again that we are offering a 75% discount to the coreboot
community on the REACTS system [1] in an effort to get higher test
coverage.  Use this promotional code when checking out to apply the
discount: COREBOOTREACTS17

Let me know what you think of the OpenBMC system.  We're considering
allowing bugs to be tracked on GitHub; is this something the community
wants to see or would a separate Bugzilla type install be preferred?  We
want to provide the infrastructure needed for the community to start
working with and enhancing this port, so suggestions and comments are
welcome!

[1] https://www.raptorengineering.com/content/REACTS/intro.html

- -- 
Timothy Pearson
Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJZpbFQAAoJEK+E3vEXDOFbWGsH/1WN4KMm1GCYUVdcj2wdD1XF
EkZ5H6Yu6p+8Fj+WkOaNsHb8xSFG5rqPPZC8ubT+tt4gcUqsgFzYLYDXACH6y4Yc
RFoSHd7rXYB9uBG1uzZIhQovfL65a6Y5+LTuhL9CYNXP7iR64L44NjgD1HFv8BS7
ryJ+K/LE941uOin8GQshoFwJ/i88uOMpKunF5Ef+SnGr4VhE5OvUrulpo5iJ/62J
Ia3v9zD9hTppGyi2MNydR7qy5kVrABHiq+6C2LiQtpfBx/GOwNevZbbvt+aswEnc
jEItl/I6YBTAMyT4eGdc5LW+0H83sw8mwynK1DTzZXGGTKw/xvkun5UcvrvU4Q8=
=dqp/
-----END PGP SIGNATURE-----



More information about the coreboot mailing list