<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi,<div class=""><div class="">Actually I am using the meta-s2600wf as my TEMPLATECONF.</div><div class="">Now switch to Q71L but found some problems :</div><div class=""><br class=""></div><div class="">1. I can not send the same REST command to power up the host. It seems the <span style="font-family: SFMono-Regular, Consolas, "Liberation Mono", Menlo, Courier, monospace; caret-color: rgb(36, 41, 46); color: rgb(36, 41, 46); font-size: 13.600000381469727px;" class="">xyz/openbmc_project/state/host0/attr/RequestedHostTransition </span></div><div class="">is gone. I even can’t see any attributes related to <span style="caret-color: rgb(36, 41, 46); color: rgb(36, 41, 46); font-family: SFMono-Regular, Consolas, "Liberation Mono", Menlo, Courier, monospace; font-size: 13.600000381469727px;" class="">xyz/openbmc_project/state.</span></div><div class=""><span style="caret-color: rgb(36, 41, 46); color: rgb(36, 41, 46); font-family: SFMono-Regular, Consolas, "Liberation Mono", Menlo, Courier, monospace; font-size: 13.600000381469727px;" class=""><br class=""></span></div><div class=""><font color="#24292e" face="SFMono-Regular, Consolas, Liberation Mono, Menlo, Courier, monospace" size="2" class=""><span style="caret-color: rgb(36, 41, 46);" class="">2. I found in quanta-q71l.conf, it remove the obmc-host-state-mgmt, this may be needed when using REST to power on host. Why q71L remove it ? Is it because of not compatible with x86 system ?</span></font></div><div class=""><font color="#24292e" face="SFMono-Regular, Consolas, Liberation Mono, Menlo, Courier, monospace" size="2" class=""><span style="caret-color: rgb(36, 41, 46);" class=""><br class=""></span></font></div><div class=""><font color="#24292e" face="SFMono-Regular, Consolas, Liberation Mono, Menlo, Courier, monospace" size="2" class=""><span style="caret-color: rgb(36, 41, 46);" class="">3. Suppose the REST is not used by Q71L, how can I power it up from LAN ?</span></font></div><div class=""><br class=""></div><div class=""><font color="#24292e" face="SFMono-Regular, Consolas, Liberation Mono, Menlo, Courier, monospace" size="2" class=""><span style="caret-color: rgb(36, 41, 46);" class="">Thanks.</span></font></div><div class=""><font color="#24292e" face="SFMono-Regular, Consolas, Liberation Mono, Menlo, Courier, monospace" size="2" class=""><span style="caret-color: rgb(36, 41, 46);" class=""><br class=""></span></font></div><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Apr 10, 2018, at 21:36, Andrew Jeffery <<a href="mailto:andrew@aj.id.au" class="">andrew@aj.id.au</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi Brad,<br class=""><br class="">On Tue, 10 Apr 2018, at 19:35, Brad Chou wrote:<br class=""><blockquote type="cite" class="">Hi,<br class="">I am going to power on my OEM server board with two Intel x86 CPUs. The <br class="">BMC chip is ASPEED 2500.<br class=""><br class="">By the Intel data sheets, I just need to control a power on GPIO to <br class="">emulate power button behavior.<br class="">The problems are, when I send Host State Control commands as mentioned <br class="">in docs/host-management.md, the journal log shows a lot of systemctl <br class="">errors.<br class=""><br class="">Looks like it is going to start the OpenPower related host control <br class="">services, which only applies to PowerPC system.<br class="">I try to modify GPIO_CONFIGS appears in skeleton recipe to match my <br class="">board, but I still got some other errors says pflash stuffs.<br class=""></blockquote><br class="">It sounds like you're building an OpenPOWER-based BMC image - this is controlled by how you set the TEMPLATECONF environment variable when sourcing the `openbmc-env` file to build (at a guess I'd say you're building for Palmetto, as it's used throughout the examples in the docs repo).<br class=""><br class="">We do have support for a couple of x86 machines in the tree - your best bet is probably the Quanta 71L machine maintained by Patrick Venture:<br class=""><br class=""><a href="https://github.com/openbmc/openbmc/tree/master/meta-openbmc-machines/meta-x86/meta-quanta/meta-q71l" class="">https://github.com/openbmc/openbmc/tree/master/meta-openbmc-machines/meta-x86/meta-quanta/meta-q71l</a><br class=""><br class="">As an aside, if you're experimenting and switching between target machines, it's probably a good idea to blow away your build/conf directory to make sure things get set up correctly when you next set TEMPLATECONF and source openbmc-env.<br class=""><br class=""><blockquote type="cite" class=""><br class="">Because there is no documents to tell me how to customize the openbmc to <br class="">fit on x86 CPUs, so I am not sure the GPIO_CONFIGS in skeleton is the <br class="">right way or not.<br class=""></blockquote><br class="">Yeah, there's not a wealth of documentation on bringing up a new machine. It would be great if you could document your experience once you get there :)<br class=""><br class="">Hope that helps in some way,<br class=""><br class="">Andrew<br class=""></div></div></blockquote></div><br class=""></div></div></body></html>