NanoPi R4S LEDS

[Meestor_X]

If you'd like to get the LEDs working with armbian, you can run these commands (or one of the other ones if you want different indications):

 

run modprobe ledtrig-netdev to check if it's loading the driver properly. If not, add the file /etc/modules-load.d/ledtrig.conf 
add just this line:

 

ledtrig-netdev

 

Then, create /etc/tmpfiles.d/leds.conf and add this:

 

w /sys/class/leds/green:lan/trigger - - - - netdev
w /sys/class/leds/green:lan/device_name - - - - eth0
w /sys/class/leds/green:lan/link - - - - 1
w /sys/class/leds/green:lan/tx - - - - 1
w /sys/class/leds/green:lan/rx - - - - 1

w /sys/class/leds/green:wan/trigger - - - - netdev
w /sys/class/leds/green:wan/device_name - - - - eth1
w /sys/class/leds/green:wan/link - - - - 1
w /sys/class/leds/green:wan/tx - - - - 1
w /sys/class/leds/green:wan/rx - - - - 1

w /sys/class/leds/red:power/trigger - - - - activity

 

Note that "red:power" is actually the "green:sys" LED. I don't see a way to control the red power led (which is fine, the green:sys is what want to control anyway).

I also use NetworkManager and set my ethernet names to eth0 and eth1 instead of the default names...

 

Here's all the choices available for "triggers":

 

none
usb-gadget usb-host
kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock
disk-activity disk-read disk-write
mtd
nand-disk
heartbeat
cpu cpu0 cpu1 cpu2 cpu3 cpu4 cpu5
activity
default-on
panic
usbport
mmc1
rfkill-any rfkill-none
r8169-0-100:00:link r8169-0-100:00:10Mbps r8169-0-100:00:100Mbps r8169-0-100:00:1Gbps
stmmac-0:01:link stmmac-0:01:10Mbps stmmac-0:01:100Mbps stmmac-0:01:1Gbps
netdev

"activity" is also a good one for red:power if you prefer that to "heartbeat"

Edited March 16 by Meestor_X