Hi Landon,

According your question, provide some suggestions for you refer it.

 

You can check journal log first for keyword “power-control” to debug why your x86-power-control cannot be activated.

BTW, x86-power-control uses default json file (power-config-host0.json) for GPIO configuration.

You also need to check this json file according your hardware.

 

For busctl set command debugging, you can use dbus-monitor to get more information why the name of property/interface is not activatable.

 

Best regards,

Tim

From: openbmc <openbmc-bounces+chli30=nuvoton.com@lists.ozlabs.org> On Behalf Of Landon
Sent: Monday, June 13, 2022 3:50 PM
To: patrick@stwcx.xyz; jason.m.bills@linux.intel.com; openbmc@lists.ozlabs.org
Subject: OpenBMC state manager problem

 

hello~

now I use aspeed ast2600 openbmc.

At first, I set pwer state command: but failed!

root@ast2600-emmc:~# busctl set-property xyz.openbmc_project.State.Host /xyz/openbmc_project/state/host0 xyz.openbmc_project.State.Host CurrentHostState s "xyz.openbmc_project.State.Host.HostState.Off" Failed to set property CurrentHostState on interface xyz.openbmc_project.State.Host: The name is not activatable root@ast2600-emmc:~# busctl set-property xyz.openbmc_project.State.Host /xyz/openbmc_project/state/host0 xyz.openbmc_project.State.Host CurrentHostState s "xyz.openbmc_project.State.Host.HostState.Running" Failed to set property CurrentHostState on interface xyz.openbmc_project.State.Host: The name is not activatable



so I modify the "\meta-aspeed-sdk\meta-ast2600-sdk\conf\machine\ast2600-emmc.conf", remove the "x86-power-control"...  :

PREFERRED_PROVIDER_virtual/obmc-system-mgmt = "packagegroup-aspeed-obmc"
PREFERRED_PROVIDER_virtual/obmc-host-ipmi-hw = "phosphor-ipmi-kcs"

# I remove the 2 lines :
#VIRTUAL-RUNTIME_obmc-host-state-manager ?= "x86-power-control"
#VIRTUAL-RUNTIME_obmc-chassis-state-manager ?= "x86-power-control"
EXTRA_IMAGEDEPENDS:append = "\
   aspeed-image-recoveryuart \
   aspeed-image-emmcboot \

 

After,  I set pwer state command OK :

root@ast2600-emmc:~# busctl set-property xyz.openbmc_project.State.Host /xyz/openbmc_project/state/host0 xyz.openbmc_project.State.Host CurrentHostState s "xyz.openbmc_project.State.Host.HostState.Off" root@ast2600-emmc:~# busctl set-property xyz.openbmc_project.State.Host /xyz/openbmc_project/state/host0 xyz.openbmc_project.State.Host CurrentHostState s "xyz.openbmc_project.State.Host.HostState.Running"

but, after I update openbmc for the lastest the version, it can't enter the system.

and I open the 2 lines :

VIRTUAL-RUNTIME_obmc-host-state-manager ?= "x86-power-control"
VIRTUAL-RUNTIME_obmc-chassis-state-manager ?= "x86-power-control"

the system is OK.

but, the "x86-power-control" is disable, I set pwer state command is failed !

root@ast2600-emmc:~# busctl set-property xyz.openbmc_project.State.Host /xyz/openbmc_project/state/host0 xyz.openbmc_project.State.Host CurrentHostState s "xyz.openbmc_project.State.Host.HostState.Off"

Failed to set property CurrentHostState on interface xyz.openbmc_project.State.Host: The name is not activatable root@ast2600-emmc:~# busctl set-property xyz.openbmc_project.State.Host /xyz/openbmc_project/state/host0 xyz.openbmc_project.State.Host CurrentHostState s "xyz.openbmc_project.State.Host.HostState.Running" Failed to set property CurrentHostState on interface xyz.openbmc_project.State.Host: The name is not activatable

so how to solve the problem for the set pwer state command ?

Thank you very much !







 

The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Nuvoton is strictly prohibited; and any information in this email irrelevant to the official business of Nuvoton shall be deemed as neither given nor endorsed by Nuvoton.