Hi, after running the full update with Anthias script, I got errors about insufficient space, I tried different commands to clean up the old anthias installation but the procedure always gives an error about insufficient space, I tried to use these commands to clean up the sd memory card:
sudo apt autoremove --purge
sudo apt clean
sudo rm -rf /tmp/*
sudo rm -rf /var/tmp/*
When i launch command : sudo df -h i get this :
pi@Anthias-Squero:~ $ sudo df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 14G 13G 1.2G 92% /
devtmpfs 266M 0 266M 0% /dev
tmpfs 396M 0 396M 0% /dev/shm
tmpfs 159M 1.5M 157M 1% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
/dev/mmcblk0p1 255M 31M 225M 13% /boot
tmpfs 80M 0 80M 0% /run/user/1000
overlay 14G 13G 1.2G 92% /var/lib/docker/overlay2/7709710b0e902859804b933f22c95ff9273ab5ff7bf2559912d950420b3b8612/merged
overlay 14G 13G 1.2G 92% /var/lib/docker/overlay2/b3417a80dea20f40a49f3785d260bec398bf09109615ae5431d2b0af0e311e27/merged
overlay 14G 13G 1.2G 92% /var/lib/docker/overlay2/ad7f05c5b7834d6fb8d8637189b21107d4b4215297f165b064b7e9cbd59f6dfe/merged
overlay 14G 13G 1.2G 92% /var/lib/docker/overlay2/131470c4a3aa61c4a15b6f7160f74d3b420467a71bd8fafe65d65d65b98e1fe8/merged
overlay 14G 13G 1.2G 92% /var/lib/docker/overlay2/9ec0f26245457bacb70a860daa0a7aedfbc84a4d514296aefdb7426fce34670e/merged
overlay 14G 13G 1.2G 92% /var/lib/docker/overlay2/3facb4a0bb3830e8db6526ab89ebb92d170f2fad027622b890871616a079a54d/merged
I tried already to use “Advanced Options” → “Expand Filesystem” in Raspi Config to extend partition
How do I get more space without reinstalling Raspberry Pi O/S Lite 64bit?
Perhaps i found a solution about space inside this post : Can change all settings but basic authentification - #10 by nicomiguelino
The script ran fine all the way to the end with no more out of space errors. I’ll reboot and test it thoroughly.
Anthias installed without crashing this time but after rebooting the screen remains black even though ssh and web ui works fine. Same problem occurred for which I opened this POST
@nicomiguelino
In this particular TV (one of the 40 digital TVs), to avoid too many factors coming into play, I did not update the TV bios or the Raspberry PI o/s lite 64 version, only Anthias. So I deduce that it depends exclusively on Anthias at this point. Suggestions? I’ll try to copy the new log to you. Let me know if I launched it from the correct user and folder. Thanks.
root@Anthias-Squero:/home/pi/screenly# docker compose logs -ft anthias-viewer
anthias-viewer-1 | 2025-06-27T08:47:25.052316557Z ./bin/start_viewer.sh: line 39: /sys/fs/cgroup/memory/memory.swappiness: No such file or directory
anthias-viewer-1 | 2025-06-27T08:47:44.079283246Z Loading browser…
anthias-viewer-1 | 2025-06-27T08:52:40.387526396Z ./bin/start_viewer.sh: line 39: /sys/fs/cgroup/memory/memory.swappiness: No such file or directory
anthias-viewer-1 | 2025-06-27T08:53:13.815369138Z Loading browser…
anthias-viewer-1 | 2025-06-27T09:22:00.712218636Z ./bin/start_viewer.sh: line 39: /sys/fs/cgroup/memory/memory.swappiness: No such file or directory
anthias-viewer-1 | 2025-06-27T09:22:35.013232905Z Loading browser…
anthias-viewer-1 | 2025-06-27T10:02:25.223966187Z ./bin/start_viewer.sh: line 39: /sys/fs/cgroup/memory/memory.swappiness: No such file or directory
anthias-viewer-1 | 2025-06-27T10:02:58.588486277Z Loading browser…
@caimano, looking at the logs, the browser is not starting.
Could you run the following commands from your terminal?
cd ~/screenly
docker compose exec anthias-viewer bash
sudo -E -u viewer dbus-run-session ScreenlyWebview
After running the ScreenlyWebview command, the screen should go black until you do Ctrl-C. Let me know if you run into some issues. If so, please share the console output that you get.
Hi, i share the ssh console output.
Tv display is black
@caimano, looking at the logs, it seems like the connected display is not being recognized.
What would you get if you run the following inside the anthias-viewer container?
ls -l /dev/fb*
ls -l /dev/dri
It would also be helpful if you check the value of QT_QPA_PLATFORM inside anthias-viewer:
echo $QT_QPA_PLATFORM
Hi, i tried with the first command but There are no directories that begin with the letters fb
root@Anthias-Squero:/# ls -l /dev/fb*
ls: cannot access ‘/dev/fb*’: No such file or directory
With second command:
root@Anthias-Squero:/dev# ls -l /dev/dri
total 0
drwxr-xr-x 2 root root 80 Jul 4 10:17 by-path
crw-rw---- 1 root video 226, 0 Jul 4 10:17 card0
crw-rw---- 1 root render 226, 128 Jul 4 10:17 renderD128
root@Anthias-Squero:/dev#
With third command, nothing happens:
pi@Anthias-Squero:~ $ echo $QT_QPA_PLATFORM
pi@Anthias-Squero:~ $
Same exact situation. Http web ui ok, ssh ok, display dead.
I tried to install the Raspberry Pi OS Legacy Lite 64 version and I noticed that the message on the TV display after initializing the SSH has changed a little bit, but I think it just depends on the OS version.
Why when I install the Raspberry OS on an external PI B3+ device, no messages appears?
I attach the two screenshots with the related messages.
(But in the end everything is as before)
@caimano, it looks like you ran echo $QT_QPA_PLATFORM directly in the host.
You have to get inside the anthias-viewer container. You have to run the following commands in order:
# Running the command below will open up another shell.
docker compose exec anthias-viewer bash
# It's only after running the command above you can run the following:
echo $QT_QPA_PLATFORM # It should show "linuxfb". If it shows otherwise, please let me know.
I’d recommend to stick to the latest RPi OS (i.e., Bookworm) when installing Anthias.
Let me try to come up with a fix. Since running ls -l /dev/fb* gave you nothing, I might change the way how to content is being displayed.
Hi, i run the two commands.
I paste the log:
pi@Anthias-Squero:~/screenly $ docker compose exec anthias-viewer bash
root@4bc5fb7712c6:/usr/src/app# echo $QT_QPA_PLATFORM
linuxfb
root@4bc5fb7712c6:/usr/src/app#
@caimano, thanks for sharing your results. Let me try to fix this by changing QT_QPA_PLATFORM to eglfs and doing other necessary steps. I’ll keep you posted.
1 Like
Hi, I disassembled one of the 40 NEC displays and took it to the lab for testing. Any updates?
@caimano I’m still working on this one. I’ll let you know if there are updates.
I opened the NEC Monitor and found this hardware inside.
The Raspberry Pi appears to be a CM3, not a CM3+ as I initially thought. Could this be helpful? Will it make any difference if I buy a new CM3+ for testing, plugging it into the original NEC CMIO board?
@caimano, thanks! Could you please run the following commands on that CM3 share the console output?
cat /proc/device-tree/model && echo
We modified the scripts to support compute module devices, but we might have missed something. The code currently checks if “Compute Module 3“ is present in `/proc/device-tree/model` and if so, the device will be considered as a Raspberry Pi 3 device.
Hi @nicomiguelino , yes here it is:
pi@raspberrypitest:~ $ cat /proc/device-tree/model && echo
Raspberry Pi Compute Module 3 Rev 1.0
So what should I do now?
This is a secondary test; the previous topic takes priority for me.
While waiting for a response to the previous post, I tried reloading Anthias onto the same CM3 as the NEC TV where I had already inserted it.
The installation produced quite a few errors, eventually crashing.
It seems to be a space issue. Now i have a CM3 with 16GB eMMC. How can I read the flash size everytime, without remove it from the TV? Do you think it makes sense to test with a new CM3 with a 32GB eMMC? Or directly with a 32GB CM3+?
These are the errors:
PLAY RECAP **********************************************************************************************************************************************************************************************
localhost : ok=83 changed=24 unreachable=0 failed=0 skipped=16 rescued=0 ignored=0
┏━ … ━━━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━━━━━┓
┃ ┃
┃ Initialize/Upgrade Docker Containers ┃
┃ ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
[+] Pulling 60/70
⠼ anthias-celery [⣿⣿⣿⣿⣿⣿⣿] 401.1MB / 401.3MB Pulling 738.4s
⠼ anthias-viewer [⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿] 567.5MB / 568.4MB Pulling 738.4s
⠼ anthias-wifi-connect [⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿] 379.8MB / 380.1MB Pulling 738.4s
redis Pulled 218.7s
⠼ anthias-server [⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿] 401.3MB / 401.5MB Pulling 738.4s
anthias-nginx Pulled 218.6s
⠼ anthias-websocket [⣿⣿⣿⣿⣿⣿⣿] 373.7MB / 373.9MB Pulling 738.4s
WARNING: Some service image(s) must be built from source by running:
docker compose build anthias-celery anthias-websocket anthias-server anthias-viewer anthias-wifi-connect
5 errors occurred:
- failed to register layer: write /usr/local/lib/python3.11/dist-packages/django/db/migrations/operations/pycache/models.cpython-311.pyc: no space left on device
- failed to register layer: write /usr/lib/python3.11/encodings/base64_codec.py: no space left on device
- failed to register layer: write /usr/local/lib/python3.11/dist-packages/yt_dlp/extractor/youtube/pycache/_base.cpython-311.pyc: no space left on device
- failed to register layer: write /var/lib/apt/lists/archive.raspbian.org_raspbian_dists_bookworm_main_binary-armhf_Packages.lz4: no space left on device
- failed to register layer: write /usr/share/doc/libcairo2/copyright: no space left on device
pi@raspberrypitest:~ $ ^C
@caimano, thanks for sharing the output of running cat /proc/device-tree/model && echo. Given that, there’s nothing wrong with that part.
You could try testing the installer with the CM3+
Okay, I’ll order it tomorrow morning and then test it with the NEC I/O Board. I’ll keep you posted.
1 Like
