Am 22.01.22 um 12:42 schrieb David W. Legg:
Ah, do you mean the red power LED that stays on after boot?
Yes
If so, will an updated F35 kernel fix it, or should I go back to F34?
I'm just a kernel developer and not involved into Fedora. So cannot answer this question.
:D
On 22/01/2022 11:23, Stefan Wahren wrote:
is the issue about the LEDs already solved? If not, this is the same.
On 1/22/22 09:53, David W. Legg wrote:
Just a quick email to confirm that this works when I revert to a:
5.14.10-300.fc35.aarch64
kernel, on an RPI 4B:
gpioset --active-low --mode=time --sec=1 `gpiofind GPIO21`=0 # works, no error.
It breaks when I upgrade the kernel to:
5.15.14-200.fc35.aarch64
kernel, due to the previously discussed problem with the red LED not going out after boot.
Upgrade to the new kernel. Upgrade the kernel? I can't get it to replicate.
[root@raspi so]# gpiodetect gpiochip0 [pinctrl-bcm2711] (58 lines) gpiochip1 [raspberrypi-exp-gpio] (8 lines) [root@raspi so]# gpioset --active-low --mode=time --sec=1 `gpiofind GPIO21`=0 [root@raspi so]# uname -a Linux raspi 5.15.16-200.fc35.aarch64 #1 SMP Thu Jan 20 15:21:58 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux [root@raspi so]#
Yes, just to confirm that I still have the gpio/LED problem with the latest kernel:
# gpioset `gpiofind GPIO27`=1 gpioset: error setting the GPIO line values: Unknown error 517
# uname -a
Linux arcturus.home 5.15.16-100.fc34.x86_64 #1 SMP Thu Jan 20 16:34:27 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
-
David W. Legg -
Sean -
Stefan Wahren