NanoPi NEO | LEDs have stopped working with Linux v5.15 #5401

mhjessen · 2022-04-03T23:37:49Z

Creating a bug report/issue

Beginning with either v8.1 or v8.2 the green & blue LEDs on my NanoPi NEO have stopped working. I restored an image of v8.0.2 and the LEDs were working again as before. I then upgraded to v8.3.1 and they no longer work.

Required Information

DietPi version | cat /boot/dietpi/.version
G_DIETPI_VERSION_SUB=3
G_DIETPI_VERSION_RC=1
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
Distro version | echo $G_DISTRO_NAME $G_RASPBIAN
bullseye
Kernel version | uname -a
Linux mhj-neo 5.15.25-sunxi #22.02.1 SMP Sun Feb 27 09:23:25 UTC 2022 armv7l GNU/Linux
SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)
NanoPi NEO (armv7l)
Power supply used | (EG: 5V 1A RAVpower)
North Pada 5v 3A (verified via USB multi-meter)
SD card used | (EG: SanDisk ultra)
Samsung 32GB EVO and PNY 32GB Elite

Additional Information (if applicable)

Software title | (EG: Nextcloud) = N/A
Was the software title installed freshly or updated/migrated? = N/A
Can this issue be replicated on a fresh installation of DietPi? = Yes

Bug report ID | echo $G_HW_UUID = 22ab27f3-4601-4df7-b20f-9f32cc6fc943

Steps to reproduce

Either cold start or reboot
...

Expected behaviour

1 : nanopi:green:status [heartbeat]
2 : nanopi:red:pwr [activity]

Actual behaviour

On startup the green LED comes on solid for about 10 seconds then goes out. No LED activity after that.

Extra details

I did notice that with v8.0.2 (Linux mhj-neo 5.10.60-sunxi #21.08.2 SMP Tue Sep 14 16:28:44 UTC 2021 armv7l GNU/Linux) none of the files in /lib/modules/5.10.60-sunxi/kernel/drivers/ were xz compressed. In v8.3.1 they are all xz compressed.

- grep led /var/log/syslog
Apr  3 15:21:32 mhj-neo kernel: [    3.302645] leds-gpio: probe of leds failed with error -16

- 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

- dietpi-led_control
[FAILED] DietPi-LED_control | No LED devices found in /sys/class/leds/. Exiting...

- cat /etc/udev/rules.d/dietpi-led_control.rules = 
# Added by DietPi:
SUBSYSTEM=="leds", KERNEL=="nanopi:green:status", ACTION=="add", ATTR{trigger}="heartbeat"
SUBSYSTEM=="leds", KERNEL=="nanopi:red:pwr", ACTION=="add", ATTR{trigger}="activity"

- 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 Apr  3 15:08 .
drwxr-xr-x 60 root root 0 Apr  3 15:08 ..

The text was updated successfully, but these errors were encountered:

MichaIng · 2022-04-04T22:35:27Z

Many thanks for your report.

Seems similar: #5385
Just not the GPIO sysfs interface but the one for the LEDs.

I wonder whether this is the same with stable/supported kernel as well.

If you find some time and a spare SD card, could you test the Armbian image (Debian Bullseye, Kernel 5.15.y): https://www.armbian.com/nanopi-neo/
If it is the same, if can be reported here: https://forum.armbian.com/forum/13-allwinner-h2-h3/

Generally those are defined in the device tree. Does this show something?

ls -l /proc/device-tree/leds

mhjessen · 2022-04-05T20:57:10Z

Thanks for looking into this!

I agree that is does look similar to #5385

I just downloaded from the link you provided; Armbian 22.02 Bullseye Kernel 5.15.y, Size: 330Mb, Updated: Feb 27, 2022
I will try to get it going tonight and update this ticket with the results.

In the meantime;

ls -l /proc/device-tree/leds
total 0
-r--r--r-- 1 root root 10 Apr  5 13:28 compatible
drwxr-xr-x 2 root root  0 Apr  5 13:28 led-0
drwxr-xr-x 2 root root  0 Apr  5 13:28 led-1
-r--r--r-- 1 root root  5 Apr  5 13:28 name
-r--r--r-- 1 root root  8 Apr  5 13:28 pinctrl-0
-r--r--r-- 1 root root  8 Apr  5 13:28 pinctrl-names
drwxr-xr-x 2 root root  0 Apr  5 13:28 pwr
drwxr-xr-x 2 root root  0 Apr  5 13:28 status

ls -l /proc/device-tree/leds/led-0
total 0
-r--r--r-- 1 root root 16 Apr  5 13:28 gpios
-r--r--r-- 1 root root 19 Apr  5 13:28 label
-r--r--r-- 1 root root 10 Apr  5 13:28 linux,default-trigger
-r--r--r-- 1 root root  6 Apr  5 13:28 name

cat /proc/device-tree/leds/led-0/gpios

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

ls -l /proc/device-tree/leds/led-1
total 0
-r--r--r-- 1 root root  3 Apr  5 13:33 default-state
-r--r--r-- 1 root root 16 Apr  5 13:33 gpios
-r--r--r-- 1 root root 17 Apr  5 13:33 label
-r--r--r-- 1 root root  6 Apr  5 13:33 name

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/name
leds

cat /proc/device-tree/leds/pinctrl-0
78

cat /proc/device-tree/leds/pinctrl-names
default

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

ls -l /proc/device-tree/leds/status/
total 0
-r--r--r-- 1 root root 16 Apr  5 13:40 gpios
-r--r--r-- 1 root root 20 Apr  5 13:40 label
-r--r--r-- 1 root root 10 Apr  5 13:40 linux,default-trigger
-r--r--r-- 1 root root  7 Apr  5 13:40 name

cat /proc/device-tree/leds/status/gpios

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

MichaIng · 2022-04-05T23:38:51Z

So on device tree end, the LEDs are there, the correct default trigger is shown etc, but only the sysfs interface to change the triggers is missing. In case of the sysfs GPIO interface, it was deprecated in Linux, in favour of libgpiod, but can be re-enabled. But for LED control I don't see that it is deprecated: https://www.kernel.org/doc/html/latest/leds/leds-class.html

mhjessen · 2022-04-10T21:41:02Z

Apologies for the delayed update. I was challenged by getting a working SDHC setup. NEO doesn't like Sandisk or PNY cards, only Samsung. Anyway...

The results for Armbian are the same. The green LED comes on solid for 10 seconds on startup then both LEDs are off after that. See below for addition information.

I've submitted a bug report to Armbian; https://forum.armbian.com/topic/20245-nanopi-neo-leds-not-working-with-linux-51525-sunxi-armbian-22021/

# 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

# 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

# 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

# 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.

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'll update here when I get word back on the Armbian bug report.

mhjessen · 2022-04-12T18:10:19Z

I've opened case "NanoPi NEO LEDs not working with Linux 5.15.25-sunxi (Armbian 22.02.1)" in the Armbian Allwinner H2 & H3 forum.

https://forum.armbian.com/topic/20245-nanopi-neo-leds-not-working-with-linux-51525-sunxi-armbian-22021/

Fingers crossed!

mhjessen · 2022-04-15T18:12:04Z

Appears the issue is related to; Error loading modules after kernel upgrade
https://forum.armbian.com/topic/20087-error-loading-modules-after-kernel-upgrade/

Solution being worked on is to disable xz module compression; disable module compression for sunxi-current armbian/build#3663
https://github.com/armbian/build/pull/3663/files

mhjessen · 2022-04-21T22:27:10Z

Contributed system information to Error loading modules after kernel upgrade
https://forum.armbian.com/topic/20087-error-loading-modules-after-kernel-upgrade/?do=findComment&comment=138459

MichaIng · 2022-04-22T12:53:09Z

@mhjessen
I'm actually not convinced that your issue is related to the "module not found" errors in this thread. Also I do not see those error messages in any of your logs. You would see them when regenerating the initramfs:

update-initramfs -u

or when trying to load a kernel module:

modprobe ipv6

The error in this forum thread seems to be with older Ubuntu and Debian versions only, where the userland tools like modprobe are not able to deal with xz-compressed modules, but on Debian Bullseye this doesn't seem to be an issue.

mhjessen · 2022-04-26T20:36:08Z

Agreed. I ran both and there's nothing in the logs.

# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.15.25-sunxi

# modprobe ipv6
<nothing>

MichaIng · 2022-04-28T12:48:24Z

So indeed the issues are not related. I added this info to your Armbian forum thread.

Sfinx · 2022-07-30T08:52:46Z

upon configuring LED's kernel prints:

leds-gpio: probe of leds failed with error -16

-16 means EBUSY. Removing shit makes LED's work again. tested at armbian_22.05.4_Nanopineo_jammy_current_5.15.48

--- orig.dts	2022-07-30 11:48:20.657650732 +0300
+++ sys.dts	2022-07-30 11:44:16.388711117 +0300
@@ -1415,22 +1415,10 @@
 		pinctrl-names = "default";
 		pinctrl-0 = <0x37 0x38>;
 
-		led-0 {
-			label = "nanopi:blue:status";
-			gpios = <0x0d 0x00 0x0a 0x00>;
-			linux,default-trigger = "heartbeat";
-		};
-
-		led-1 {
-			label = "nanopi:green:pwr";
-			gpios = <0x39 0x00 0x0a 0x00>;
-			default-state = "on";
-		};
-
 		pwr {
 			label = "nanopi:red:pwr";
 			gpios = <0x39 0x00 0x0a 0x00>;
-			linux,default-trigger = "default-on";
+			default-state = "on";
 		};
 
 		status {

root@cs:~# l /sys/class/leds/
total 0
drwxr-xr-x  2 root root 0 Jan  1  1970 ./
drwxr-xr-x 61 root root 0 Jan  1  1970 ../
lrwxrwxrwx  1 root root 0 Jan  1  1970 nanopi:green:status -> ../../devices/platform/leds/leds/nanopi:green:status/
lrwxrwxrwx  1 root root 0 Jan  1  1970 nanopi:red:pwr -> ../../devices/platform/leds/leds/nanopi:red:pwr/

MichaIng · 2022-07-31T14:00:18Z

@Sfinx
Nice, were these present probably as of an Armbian patch which has now become obsolete and conflicting? So we may open a PR to remove the patch.

Upstream kernel defines the exact same LEDs already. having both defined leads to unusable LED sysfs nodes: MichaIng/DietPi#5401 Signed-off-by: MichaIng <[email protected]>

MichaIng · 2024-05-13T22:37:01Z

Since we create and ship own kernel packages now, I just patched the patch from Armbian, removing their doubled LED nodes: MichaIng/build@4b8a626

Please test whether these help:

cd /tmp
wget https://dietpi.com/downloads/binaries/testing/linux-{image,dtb}-current-sunxi.deb
dpkg -i linux-{image,dtb}-current-sunxi.deb
reboot

MichaIng · 2024-06-02T13:10:17Z

Anyone who is able to test this? Would be great if we could close the issue, but I have no NanoPi NEO to test.

mhjessen · 2024-06-03T01:17:30Z

Apologies on the delay.

I downloaded and did a clean DietPi install to a clean micro-SDHC card which went OK.
I followed the steps above and downgraded linux-dtb-current-sunxi from 24.5.1 to 24.5.0-trunk-dietpi1. That went OK.
I rebooted and the LEDs are now working.
I was able to reprogram them both from the DietPi-Launcher > DietPi-LED_control, and the changes survived a couple of reboots.

My production setup is using DietPi v9.4.2/ 24.5.1on kernel 6.6.31-current-sunxi. I didn't test the above solution on my production setup because there's only 32 MB in the /tmp tmpfs. I also wasn't sure if the above solution would lock me into the test version.

Any suggestions as to how I can get this solution integrated onto my production setup?

Thanks again for your patience and dedication!

Upstream kernel defines the exact same LEDs already. having both defined leads to unusable LED sysfs nodes: MichaIng/DietPi#5401 Signed-off-by: MichaIng <[email protected]>

@mhjessen

- NanoPi NEO | Resolved an issue where LEDs of this SBC could not be configured, due to a conflicting kernel patch. Many thanks to @mhjessen for reporting this issue: #5401

MichaIng · 2024-06-03T14:44:57Z

Great, I just pushed a rebuild of the kernel to our APT server: f324d76

Upstream kernel defines the exact same LEDs already. having both defined leads to unusable LED sysfs nodes: MichaIng/DietPi#5401 Signed-off-by: MichaIng <[email protected]>

MichaIng added the Investigating 🤔 label Apr 4, 2022

MichaIng added NanoPi NEO External bug 🐞 For bugs which are not caused by DietPi. Waiting for external fix ⏳ Kernel related 🧬 labels Apr 12, 2022

MichaIng added this to the v8.4 milestone Apr 12, 2022

MichaIng modified the milestones: v8.4, v8.5 Apr 30, 2022

MichaIng removed the Investigating 🤔 label May 27, 2022

MichaIng modified the milestones: v8.5, v8.6 May 28, 2022

MichaIng added the Armbian label Jun 26, 2022

MichaIng modified the milestones: v8.6, v8.7 Jul 2, 2022

MichaIng modified the milestones: v8.7, v8.8 Jul 31, 2022

MichaIng modified the milestones: v8.8, v8.9 Aug 29, 2022

MichaIng added this to the v9.5 milestone May 13, 2024

MichaIng removed the Waiting for external fix ⏳ label May 13, 2024

MichaIng added the Solution available 🥂 Definite solution has been done label May 13, 2024

MichaIng removed the Testing/testers required 🔽 label Jun 3, 2024

MichaIng added a commit that referenced this issue Jun 3, 2024

v9.5

f324d76

- NanoPi NEO | Resolved an issue where LEDs of this SBC could not be configured, due to a conflicting kernel patch. Many thanks to @mhjessen for reporting this issue: #5401

MichaIng closed this as completed Jun 3, 2024

This was referenced Jun 3, 2024

Beta v9.5.0 #7088

Merged

Open Beta v9.5 | Please help testing and hardening our upcoming release #7097

Closed

MichaIng mentioned this issue Jun 9, 2024

Release v9.5 #7098

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

NanoPi NEO | LEDs have stopped working with Linux v5.15 #5401

NanoPi NEO | LEDs have stopped working with Linux v5.15 #5401

mhjessen commented Apr 3, 2022 •

edited by MichaIng

Loading

MichaIng commented Apr 4, 2022

mhjessen commented Apr 5, 2022

MichaIng commented Apr 5, 2022

mhjessen commented Apr 10, 2022

mhjessen commented Apr 12, 2022

mhjessen commented Apr 15, 2022 •

edited by MichaIng

Loading

mhjessen commented Apr 21, 2022

MichaIng commented Apr 22, 2022

mhjessen commented Apr 26, 2022

MichaIng commented Apr 28, 2022

Sfinx commented Jul 30, 2022

MichaIng commented Jul 31, 2022

MichaIng commented May 13, 2024 •

edited

Loading

MichaIng commented Jun 2, 2024

mhjessen commented Jun 3, 2024 •

edited

Loading

MichaIng commented Jun 3, 2024

NanoPi NEO | LEDs have stopped working with Linux v5.15 #5401

NanoPi NEO | LEDs have stopped working with Linux v5.15 #5401

Comments

mhjessen commented Apr 3, 2022 • edited by MichaIng Loading

Creating a bug report/issue

Required Information

Additional Information (if applicable)

Steps to reproduce

Expected behaviour

Actual behaviour

Extra details

MichaIng commented Apr 4, 2022

mhjessen commented Apr 5, 2022

MichaIng commented Apr 5, 2022

mhjessen commented Apr 10, 2022

mhjessen commented Apr 12, 2022

mhjessen commented Apr 15, 2022 • edited by MichaIng Loading

mhjessen commented Apr 21, 2022

MichaIng commented Apr 22, 2022

mhjessen commented Apr 26, 2022

MichaIng commented Apr 28, 2022

Sfinx commented Jul 30, 2022

MichaIng commented Jul 31, 2022

MichaIng commented May 13, 2024 • edited Loading

MichaIng commented Jun 2, 2024

mhjessen commented Jun 3, 2024 • edited Loading

MichaIng commented Jun 3, 2024

mhjessen commented Apr 3, 2022 •

edited by MichaIng

Loading

mhjessen commented Apr 15, 2022 •

edited by MichaIng

Loading

MichaIng commented May 13, 2024 •

edited

Loading

mhjessen commented Jun 3, 2024 •

edited

Loading