Jake7 Posted April 10, 2022 Posted April 10, 2022 Armbianmonitor: http://ix.io/3UN6 Using a clean install of Armbian 22.02.1 with Linux 5.15.25-sunxi on a NanoPi NEO the green & blue LEDs no longer work. Previously they have worked with both Armbian and DietPi. # uname -a Linux nanopineo 5.15.25-sunxi #22.02.1 SMP Sun Feb 27 09:23:25 UTC 2022 armv7l GNU/Linux # cat /sys/devices/platform/leds/leds/nanopi:green:status/trigger cat: '/sys/devices/platform/leds/leds/nanopi:green:status/trigger': No such file or directory # cat /sys/class/leds/led{0,1}/trigger cat: /sys/class/leds/led0/trigger: No such file or directory cat: /sys/class/leds/led1/trigger: No such file or directory # ls -lha /sys/class/leds/ total 0 drwxr-xr-x 2 root root 0 Dec 31 1969 . drwxr-xr-x 62 root root 0 Dec 31 1969 .. # grep led /var/log/syslog Feb 27 22:38:48 nanopineo kernel: [ 2.532268] leds-gpio: probe of leds failed with error -16 Feb 27 22:38:48 nanopineo kernel: [ 2.534730] ledtrig-cpu: registered to indicate activity on CPUs # locate leds /usr/bin/setleds /usr/include/linux/uleds.h /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds /usr/lib/modules/5.15.25-sunxi/kernel/drivers/input/input-leds.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/led-class-flash.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-an30259a.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-axp20x.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-bcm6328.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-bcm6358.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-bd2802.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-cpcap.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-cr0014114.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-dac124s085.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-el15203000.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-is31fl319x.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-is31fl32xx.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm3530.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm3532.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm355x.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm3642.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm3692x.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm3697.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp3944.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp3952.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp5521.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp5523.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp5562.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp55xx-common.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp8501.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp8860.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lt3593.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-max77650.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-mlxreg.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-pca9532.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-pca955x.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-pca963x.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-pwm.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-regulator.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-spi-byte.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-tca6507.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-ti-lmu-common.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-tlc591xx.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash/leds-as3645a.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash/leds-ktd2692.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash/leds-lm3601x.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash/leds-rt4505.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash/leds-rt8515.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-audio.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-backlight.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-camera.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-gpio.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-netdev.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-oneshot.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-pattern.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-timer.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-transient.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-tty.ko.xz /usr/share/X11/xkb/compat/ledscroll /usr/share/man/man1/setleds.1.gz # ls -l /proc/device-tree/leds total 0 -r--r--r-- 1 root root 10 Apr 10 10:35 compatible drwxr-xr-x 2 root root 0 Apr 10 10:30 led-0 drwxr-xr-x 2 root root 0 Apr 10 10:30 led-1 -r--r--r-- 1 root root 5 Apr 10 10:35 name -r--r--r-- 1 root root 8 Apr 10 10:35 pinctrl-0 -r--r--r-- 1 root root 8 Apr 10 10:35 pinctrl-names drwxr-xr-x 2 root root 0 Apr 10 10:30 pwr drwxr-xr-x 2 root root 0 Apr 10 10:30 status # ls -l /proc/device-tree/leds/led-0 total 0 -r--r--r-- 1 root root 16 Apr 10 10:36 gpios -r--r--r-- 1 root root 19 Apr 10 10:36 label -r--r--r-- 1 root root 10 Apr 10 10:36 linux,default-trigger -r--r--r-- 1 root root 6 Apr 10 10:36 name # ls -l /proc/device-tree/leds/led-1 total 0 -r--r--r-- 1 root root 3 Apr 10 10:36 default-state -r--r--r-- 1 root root 16 Apr 10 10:36 gpios -r--r--r-- 1 root root 17 Apr 10 10:36 label -r--r--r-- 1 root root 6 Apr 10 10:36 name # ls -l /proc/device-tree/leds/pwr total 0 -r--r--r-- 1 root root 16 Apr 10 10:37 gpios -r--r--r-- 1 root root 15 Apr 10 10:37 label -r--r--r-- 1 root root 11 Apr 10 10:37 linux,default-trigger -r--r--r-- 1 root root 4 Apr 10 10:37 name # ls -l /proc/device-tree/leds/status total 0 -r--r--r-- 1 root root 16 Apr 10 10:37 gpios -r--r--r-- 1 root root 20 Apr 10 10:37 label -r--r--r-- 1 root root 10 Apr 10 10:37 linux,default-trigger -r--r--r-- 1 root root 7 Apr 10 10:37 name # cat /proc/device-tree/leds/led-0/gpios <nothing> # cat /proc/device-tree/leds/led-0/label nanopi:blue:status # cat /proc/device-tree/leds/led-0/linux,default-trigger heartbeat # cat /proc/device-tree/leds/led-0/name led-0 # cat /proc/device-tree/leds/led-1/default-state on # cat /proc/device-tree/leds/led-1/gpios 9 # cat /proc/device-tree/leds/led-1/label nanopi:green:pwr # cat /proc/device-tree/leds/led-1/name led-1 # cat /proc/device-tree/leds/pwr/gpios 9 # cat /proc/device-tree/leds/pwr/label nanopi:red:pwr # cat /proc/device-tree/leds/pwr/linux,default-trigger default-on # cat /proc/device-tree/leds/pwr/name pwr # cat /proc/device-tree/leds/status/gpios <nothing> # cat /proc/device-tree/leds/status/label nanopi:green:status # cat /proc/device-tree/leds/status/linux,default-trigger heartbeat # cat /proc/device-tree/leds/status/name status In the armbian-config .dts editor I found that led-0 and led-1 are reversed from what I found above. led-0 is blue and led-1 is green. I don't know if that's a show stopper or not. --- current.dts > edit not saved, kept original --- 1463 leds { 1464 compatible = "gpio-leds"; 1465 1466 led-0 { 1467 label = "nanopi:green:pwr"; 1468 gpios = <0x3f 0x00 0x0a 0x00>; 1469 default-state = "on"; 1470 }; 1471 1472 led-1 { 1473 label = "nanopi:blue:status"; 1474 gpios = <0x0e 0x00 0x0a 0x00>; 1475 linux,default-trigger = "heartbeat"; 1476 }; 1477 }; The config-5.15.25-sunxi file shows; # # LED Triggers # CONFIG_LEDS_TRIGGERS=y CONFIG_LEDS_TRIGGER_TIMER=m CONFIG_LEDS_TRIGGER_ONESHOT=m CONFIG_LEDS_TRIGGER_DISK=y CONFIG_LEDS_TRIGGER_MTD=y CONFIG_LEDS_TRIGGER_HEARTBEAT=y CONFIG_LEDS_TRIGGER_BACKLIGHT=m CONFIG_LEDS_TRIGGER_CPU=y CONFIG_LEDS_TRIGGER_ACTIVITY=y CONFIG_LEDS_TRIGGER_GPIO=m CONFIG_LEDS_TRIGGER_DEFAULT_ON=y I booted with a previous version of DietPi and the LEDs were working as before. It looks like everything needed is there and the correct default trigger is shown etc, I'm not sure where to look next. 0 Quote
MichaIng Posted April 27, 2022 Posted April 27, 2022 This issue is not related to the "module not found" errors. modprobe and update-initramfs run without errors, and it is Debian Bullseye which supports xz-compressed modules (the userland tools). 0 Quote
mdrmdr Posted June 6, 2022 Posted June 6, 2022 Same here. LEDs seems to not work anymore. In my case with Armbian 22.05.1 and Linux 5.15.43 on a NanoPi Neo. I always switched the LEDs off at boot with: echo 0 > /sys/class/leds/nanopi:red:pwr/brightness echo 0 > /sys/class/leds/nanopi:green:status/brightness Those files now do not exist anymore. Directory /sys/class/leds/ is empty. Since I like to have the LEDs off anyway, it's not a problem for me but nevertheless it might be a bug in the kernel. 0 Quote
dexamenos Posted July 7, 2022 Posted July 7, 2022 (edited) I am having a similiar issue. LEDs not available anymore. My system is a NanoPi NEO, Bullseye, since updating to Armbian v22.05, the sys fs for leds is empty dmesg ... [ 2.585643] leds-gpio: probe of leds failed with error -16 ... [ 9.156390] systemd[1]: Starting Armbian leds state... [ 9.320604] systemd[1]: armbian-led-state.service: Main process exited, code=exited, status=1/FAILURE [ 9.323242] systemd[1]: armbian-led-state.service: Failed with result 'exit-code'. [ 9.327544] systemd[1]: Failed to start Armbian leds state. ... ls /sys/class/leds <intentionally left empty> Any new ideas, where to start? Edited July 7, 2022 by dexamenos 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.