OpenBMC state manager problem

[Landon]

hello~
now I use aspeed ast2600 openbmc.
At first, I set pwer state command: but failed!

root at 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 at 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 at 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 at 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 ：
[    8.025630] systemd[1]: Hostname set to .
[    8.034897] systemd[1]: Initializing machine ID from random generator.
[    8.182435] systemd-sysv-generator[179]: SysV service '/etc/init.d/bmc-watchdog' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    8.210534] systemd-sysv-generator[179]: SysV service '/etc/init.d/ipmidetectd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    8.238552] systemd-sysv-generator[179]: SysV service '/etc/init.d/ipmiseld' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    8.783127] systemd[1]: Failed to put bus name to hashmap: File exists
[    8.790587] systemd[1]: xyz.openbmc_project.State.Host at 0.service: Two services allocated for the same bus name xyz.openbmc_project.State.Host0, refusing operation.
[    9.136389] systemd[1]: /lib/systemd/system/host-poweron.service:3: Failed to add dependency on obmc-chassis-poweroff at 0.target.requires, ignoring: Invalid argument
[    9.155891] systemd[1]: /lib/systemd/system/host-reset.service:3: Failed to add dependency on obmc-chassis-poweroff at 0.target.requires, ignoring: Invalid argument
[    9.689673] systemd[1]: /lib/systemd/system/phosphor-ipmi-net at .socket:3: Invalid interface name, ignoring: sys-subsystem-net-devices-%i.device
[    9.711232] systemd[1]: /lib/systemd/system/phosphor-ipmi-net at .socket:3: Invalid interface name, ignoring: sys-subsystem-net-devices-%i.device
[    9.770316] systemd[1]: Failed to isolate default target: Unit xyz.openbmc_project.State.Host at 0.service failed to load properly, please adjust/correct and reload service manager: File exists
[!!!!!!] Failed to isolate default target.
[    9.954507] systemd[1]: Freezing execution.
[   35.674323] SDHCI0 Vcc: disabling
[   35.678049] SDHCI1 Vcc: disabling
[   35.681750] SDHCI1 VccQ: disabling


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 at 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 at 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 !
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20220613/aad35624/attachment-0001.htm>