Please can you confirm the revision code for your Pi? "cat /proc/cpuinfo | grep Revision"
The handling of the display on the very early Pis (prior to the A+ and B+) was different to everything that came afterwards.
The rpi-display-backlight.service service is redundant - it's dependent on /proc/device-tree/rpi_backlight existing, which was part of the legacy display stack.
With Bookworm we are using kernel drivers for everything, and you should find the edt_ft5x06 driver bound to the relevant I2C device (address 0x38 on probably i2c-10).
The standard systemd-backlight service should store and reset the brightness on all display backlights over a reboot.
What you are saying would imply that the relevant drivers aren't loading correctly on reboot. Can you SSH in and provide kernel logs please.
The handling of the display on the very early Pis (prior to the A+ and B+) was different to everything that came afterwards.
The rpi-display-backlight.service service is redundant - it's dependent on /proc/device-tree/rpi_backlight existing, which was part of the legacy display stack.
With Bookworm we are using kernel drivers for everything, and you should find the edt_ft5x06 driver bound to the relevant I2C device (address 0x38 on probably i2c-10).
The standard systemd-backlight service should store and reset the brightness on all display backlights over a reboot.
What you are saying would imply that the relevant drivers aren't loading correctly on reboot. Can you SSH in and provide kernel logs please.
Statistics: Posted by 6by9 — Wed Dec 11, 2024 12:20 pm