Hi all,
I'm using a Raspberry Pi 1 Model B Rev 2, 512 MB RAM. Having just flashed the latest Debian bookworm (12.1) Raspberry Pi OS image, I can no longer see the ACT led lighting up when there is mmc activity. There is brief activity when starting the system, after that it just remains off.
I checked the following things:
Trigger is set to mmc0:
Current brightness is apparently 0:
After setting it to 1, I can see the LED active for a maximum of 1 second, before it powers off again. I did verify the command worked, as the brightness now returns 1/255:
When the light is off, after the maximum of a second, it returns to being 0.
The config.txt file is stock, I do not see any parameters set for controlling the ACT led.
Was the default behavior changed in a recent version of Raspberry Pi OS?
I'm using a Raspberry Pi 1 Model B Rev 2, 512 MB RAM. Having just flashed the latest Debian bookworm (12.1) Raspberry Pi OS image, I can no longer see the ACT led lighting up when there is mmc activity. There is brief activity when starting the system, after that it just remains off.
I checked the following things:
Trigger is set to mmc0:
Code:
$ cat /sys/devices/platform/leds/leds/ACT/triggernone rc-feedback kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock timer oneshot heartbeat backlight cpu cpu0 default-on input panic actpwr [mmc0] rfkill-any rfkill-noneCode:
$ cat /sys/devices/platform/leds/leds/ACT/brightness 0Code:
echo 1 | sudo tee /sys/class/leds/ACT/brightness && cat /sys/devices/platform/leds/leds/ACT/brightness1255The config.txt file is stock, I do not see any parameters set for controlling the ACT led.
Was the default behavior changed in a recent version of Raspberry Pi OS?
Statistics: Posted by boe — Sat Mar 16, 2024 8:41 pm
