回复: busctl call "led method" failed
周 远清
zhouyuanqing8 at outlook.com
Mon Jul 13 21:51:37 AEST 2020
Hi Vishwa
I copied your command and tested it again, the problem is still the same.
I looked at the phosphor-led-manager-master document and saw that the sys/class/leds directory needs to generate the following files.
ls -l /sys/class/leds/fault/
total 0
-rw-r--r-- 1 root root 4096 Jun 21 20:04 brightness
lrwxrwxrwx 1 root root 0 Jun 21 20:29 device -> ../../../leds
-r--r--r-- 1 root root 4096 Jun 21 20:29 max_brightness
drwxr-xr-x 2 root root 0 Jun 21 20:29 power
lrwxrwxrwx 1 root root 0 Jun 21 20:04 subsystem -> ../../../../../class/leds
-rw-r--r-- 1 root root 4096 Jun 21 20:04 trigger
-rw-r--r-- 1 root root 4096 Jun 21 20:04 uevent
However, /sys/class/leds is empty on my board. I am not sure if it will affect this problem.
root at starlake::/# ls /sys/class/leds/
root at starlake::/#
root at starlake:/sys/firmware/devicetree/base/leds# ls
compatible fault identify name power
root at starlake:/sys/firmware/devicetree/base/leds# cd fault/
root at starlake:/sys/firmware/devicetree/base/leds/fault# ls
gpios name
root at starlake:/sys/firmware/devicetree/base/leds/fault#
________________________________
发件人: Vishwanatha Subbanna <vishwa at linux.vnet.ibm.com>
发送时间: 2020年7月13日 17:02
收件人: 周 远清 <zhouyuanqing8 at outlook.com>
抄送: openbmc at lists.ozlabs.org <openbmc at lists.ozlabs.org>; uperic at 163.com <uperic at 163.com>
主题: Re: busctl call "led method" failed
Hi harley,
I am able to see it working. Please check if there was any typo etc.. journalctl would have the info
root at rain4bmc:~# busctl --verbose call xyz.openbmc_project.LED.GroupManager /xyz/openbmc_project/led/groups/power_on org.freedesktop.DBus.Properties Get ss xyz.openbmc_project.Led.Group Asserted
MESSAGE "v" {
VARIANT "b" {
BOOLEAN false;
};
};
root at rain4bmc:~# busctl --verbose call xyz.openbmc_project.LED.GroupManager /xyz/openbmc_project/led/groups/power_on org.freedesktop.DBus.Properties Set ssv xyz.openbmc_project.Led.Group Asserted b true
root at rain4bmc:~# busctl --verbose call xyz.openbmc_project.LED.GroupManager /xyz/openbmc_project/led/groups/power_on org.freedesktop.DBus.Properties Get ss xyz.openbmc_project.Led.Group Asserted
MESSAGE "v" {
VARIANT "b" {
BOOLEAN true;
};
};
root at rain4bmc:~# busctl --verbose call xyz.openbmc_project.LED.GroupManager /xyz/openbmc_project/led/groups/power_on org.freedesktop.DBus.Properties Set ssv xyz.openbmc_project.Led.Group Asserted b false
root at rain4bmc:~# busctl --verbose call xyz.openbmc_project.LED.GroupManager /xyz/openbmc_project/led/groups/power_on org.freedesktop.DBus.Properties Get ss xyz.openbmc_project.Led.Group Asserted
MESSAGE "v" {
VARIANT "b" {
BOOLEAN false;
};
};
root at rain4bmc:~#
Alternatively, you could use bustle set-property
busctl set-property xyz.openbmc_project.LED.GroupManager /xyz/openbmc_project/led/groups/power_on xyz.openbmc_project.Led.Group Asserted b true
busctl get-property xyz.openbmc_project.LED.GroupManager /xyz/openbmc_project/led/groups/power_on xyz.openbmc_project.Led.Group Asserted
Thanks,
!! Vishwa !!
On 13-Jul-2020, at 2:07 PM, 周 远清 <zhouyuanqing8 at outlook.com<mailto:zhouyuanqing8 at outlook.com>> wrote:
Hello everyone,
There are the following calls to busctl, it is normal to use the get command, but the set command prompts "Call failed: path or object not found", and no other log information is output through the journalctl command. Please take a look at how to locate this problem. Thank you!
~# busctl --verbose call xyz.openbmc_project.LED.GroupManager /xyz/openbmc_project/led/groups/power_on org.freedesktop.DBus.Properties Get ss xyz.openbmc_project.Led.Group Asserted
MESSAGE "v" {
VARIANT "b" {
BOOLEAN false;
};
};
~# busctl --verbose call xyz.openbmc_project.LED.GroupManager /xyz/openbmc_project/led/groups/power_on org.freedesktop.DBus.Properties Set ssv xyz.openbmc_project.Led.Group Asserted b true
Call failed: path or object not found
harley
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20200713/3bff145c/attachment-0001.htm>
More information about the openbmc
mailing list