Pi-hole PADD problem under DietPi v8.12.1?

Troubleshooting
1

Hello,

here is some information about my system:

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)”
NAME=“Debian GNU/Linux”
VERSION_ID=“11”
VERSION=“11 (bullseye)”
VERSION_CODENAME=bullseye
ID=debian
HOME_URL=“https://www.debian.org/”
SUPPORT_URL=“Debian -- User Support”
BUG_REPORT_URL=“https://bugs.debian.org/”
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)

PADD v3.9.0

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?

Recently there was a small problem with the display of PADD. But that shouldn’t be the reason, since both the original PADD version and the workarout from Yubiuser don’t affect the problem I’ve noticed after the DietPi update.[Local repo hash has only length of 7 instead of 8 · Issue #5059 · pi-hole/pi-hole · GitHub]

I know this is all very vague and poorly described, but I’m not a Linux pro.

I would be happy to provide more information.

Best regards,

Falconcrest

2

I’m not aware on a change within display area.

If possible, try to restore a backup to check how it is behaving. Once done, run apt update && apt upgrade. Does it change anything?

3

Unfortunately, as is often the case:
No backup was carried out before the update.

I know - no backup, no pity!

I did some screenshots, but they don’t seem to be very meaningful.

Pic1
Pic1800×541 139 KB

Pic2
Pic2800×548 142 KB

Pic3
Pic3800×551 172 KB

4

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.

5

Do you have any ideas or tips on how to correct the ugly display?
Should I report the issue to Github pihole/padd?

6

this has nothing to do with PADD. These are kernel messages generated by UFW. They would appear without PADD same way.

I’m not sure which classes/severity these UFW messages belongs to. Maybe @MichaIng knows

7

Another note, but I can not assess the importance of the statement:
I use Pi-hole with unbound.

8

Totally unrelated. It’s ufw message created by the kernel.

9

Is your DietPi on latest version already? Because we lowered the log level for kernel console logs just with DietPi v8.12.

1 Like
10

Yes, DietPi is v8.12.1.
I would like to say that since the update from v8.11.X to the latest version, this phenomenon occurs.

11

Do you have quiet in your /boot/cmdline.txt?

12

Yes, there is a quiet.

root=PARTUUID=9bcc366d-02 rootfstype=ext4 rootwait fbcon=map:10 fbcon=font:VGA8x8 fsck.repair=yes net.ifnames=0 logo.nologo quiet console=tty1

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.

13

yes kernel messages printed to screen, doesn’t matter which user.

14

With my limited knowledge of Linux, can I provide something else for analysis?

15

No. We will ask if further details are required. We basically know where this is coming from.

16

I only noticed today that a NanoPi M4 with TFT also has problems with the display here.

root@nanopim4-wlan:~# cat /sys/firmware/devicetree/base/model
FriendlyElec NanoPi M4
root@nanopim4-wlan:~# uname -a
Linux nanopim4-wlan 4.4.192-rk3399 #6 SMP Tue Oct 8 18:32:46 CEST 2019 aarch64 GNU/Linux
root@nanopim4-wlan:~# cat /etc/*release
BOARD=nanopim4
BOARD_NAME=“NanoPi M4”
BOARDFAMILY=rk3399
BUILD_REPOSITORY_URL=GitHub - armbian/build: Armbian Linux Build Framework
BUILD_REPOSITORY_COMMIT=90ad4e43
VERSION=5.90
LINUXFAMILY=rk3399
BRANCH=default
ARCH=arm64
IMAGE_TYPE=stable
BOARD_TYPE=conf
INITRD_ARCH=arm64
KERNEL_IMAGE_TYPE=Image
IMAGE_UUID=403e73e5-12c4-48e1-9290-c9b40fd9e432
PRETTY_NAME=“Debian GNU/Linux 10 (buster)”
NAME=“Debian GNU/Linux”
VERSION_ID=“10”
VERSION=“10 (buster)”
VERSION_CODENAME=buster
ID=debian
HOME_URL=“https://www.debian.org/”
SUPPORT_URL=“Debian -- User Support”
BUG_REPORT_URL=“https://bugs.debian.org/”

pic1
pic1800×544 73.1 KB

pic2
pic2800×541 67.4 KB

pic3
pic3800×534 133 KB

Is this based on the same bug?
Are these also kernel messages?
I’ll say very cautiously that this was also not available before the update to v8.12.1.

17

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.

18

I had already understood. :wink:
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.

19

it’s a setting for the kernel message. I guess @MichaIng could give a workaround. He is just on the other side of the globe on vacation. Means we need to take time difference into account :wink:

20

This is not vital, it works, it just looks bad. Let’s wait for the things to come…