Thanks Pavel.
I can't even see any phy0xx in trigger. Where do they come from?
I do have kmod-ledtrig-netdev installed.( at least opkg list shows the
package)
Here is also the device tree for that LED:
user { label ="wifired" gpios = <&gpio5 23 0>
default-state ="on" linux,default-trigger = "netdev"}
Thanks,Farid
On Tuesday, March 3, 2015 11:23 AM, Pavel Volkov
<[email protected]> wrote:
On Tuesday, March 3, 2015 8:43:52 PM MSK, Farid Farid wrote:
> What is option sysfs means? Is it the path to /sys/class/leds/?
Yes, in your case it will be 'wifired'.
> Here is the content of trigger for this LED. I am wonder if it is
correct.
>>> cat /sys/class/leds/wifired/trigger
> [none] nand-disk mmc0 timer oneshot heartbeat backlight gpio
> cpu0 default-on transient
You don't have "netdev" listed as a trigger so I think you should install
kmod-ledtrig-netdev first.
Mine looks like this:
# cat /sys/class/leds/bcm47xx\:blue\:wlan/trigger
none nand-disk timer default-on [netdev] phy0rx phy0tx phy0assoc phy0radio
_______________________________________________
openwrt-users mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
_______________________________________________
openwrt-users mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
