root@pihole:~# cat /sys/firmware/devicetree/base/model
Raspberry Pi 4 Model B Rev 1.1
root@pihole:~# uname -a
Linux pihole 5.15.76-v8+ #1597 SMP PREEMPT Fri Nov 4 12:16:41 GMT 2022 aarch64 GNU/Linux
root@pihole:~# cat /proc/version
Linux version 5.15.76-v8+ (dom@buildbot) (aarch64-linux-gnu-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1597 SMP PREEMPT Fri Nov 4 12:16:41 GMT 2022
root@pihole:~# cat /etc/*release
PRETTY_NAME=“Debian GNU/Linux 11 (bullseye)”
SUPPORT_URL=“Debian -- User Support”
root@pihole:~# pihole -v
Pi-hole version is v5.14.2 (Latest: v5.14.2)
AdminLTE version is v5.17 (Latest: v5.17)
FTL version is v5.19.2 (Latest: v5.19.2)
Since the last DietPi update, I have found that PADD is not working correctly on my Pi.
I don’t know how to describe it in an understandable way, but the display involuntarily begins to scroll sporadically, which means that new lines appear from below, which cause the view to scroll upwards. Then there is a short reset of the display and everything is ok again for a while.
So far I haven’t encountered any other problems, neither with Pihole nor with DietPi itself.
Have the components been changed by the update that could affect the expenses for TFTs?
these are kernel information messages, created by your UFW firewall. We adjusted the messages a bit, to hide unnecessary kernel information on screen. But looks like UFW feels too important and shows up on screen.
I just set the autologin to another user instead of root (PADD is started under root). The effect also occurs under User dietpi in the console(TFT). After the prompt is available, the screen content begins to scroll after a while and briefly outputs the kernel messages, after which everything is fine again for a short time.
As already told above, we adjusted the visibility of kernel messages on DietPi 8.12. Aim was to reduce the number of messages shown on screen. For your, for whatever reason, this seems to have increased visibility.
I had already understood.
My intention was only to report this again, since the problem also occurs on another system.
Either I did something unusual on both systems or it was the update, at least in my case.
Do you already have an idea how to solve this?
Maybe just a workaround for me?
That’s why I shy away from trying to reinstall the systems and not knowing exactly whether the problem will reappear.