Thanks for your reply!
I should also mention that I did experiment a bit longer, with varying results.
1 - I tried plugging in an HDMI cable to the headless PI (without attaching it to a real monitor), to see if it makes a difference. It doesn't (chromium still extremely slow).
2 - I did comment out the linesin the /boot/firmware/config.txt, but then I could get no desktop when remotely connected ("Cannot currently show the desktop").
3 - I also tried to include "video=HDMI-A-1:1920x1080@60" to my /boot/firmware/cmdline.txt - made no difference (no desktop available remotely).
So I reverted all above changes. My "solution" for the time being is to use Firefox browser which runs smoothly under the same conditions where chromium is lagging extremely. When a real monitor is plugged into the raspberry, then chromium runs very smooth, even when accessing the Raspberry remotely - it just has to have a real monitor plugged in.
Through my very limited knowledge - and from what I read when searching - it seems that graphics hardware acceleration doesn't work in chromium when PI is headless for some reason. In PI4 running Bullseye, this could be bypassed by uncommenting hdmi_force_hotplug=1 in /boot/config.txt - but this cannot be achieved in a similar way in Bookworm..
It's a PI5 - with 8GB of RAM.how much RAM does your PI4 have?
I should also mention that I did experiment a bit longer, with varying results.
1 - I tried plugging in an HDMI cable to the headless PI (without attaching it to a real monitor), to see if it makes a difference. It doesn't (chromium still extremely slow).
2 - I did comment out the lines
Code:
#dtoverlay=vc4-kms-v3d#max_framebuffers=23 - I also tried to include "video=HDMI-A-1:1920x1080@60" to my /boot/firmware/cmdline.txt - made no difference (no desktop available remotely).
So I reverted all above changes. My "solution" for the time being is to use Firefox browser which runs smoothly under the same conditions where chromium is lagging extremely. When a real monitor is plugged into the raspberry, then chromium runs very smooth, even when accessing the Raspberry remotely - it just has to have a real monitor plugged in.
Through my very limited knowledge - and from what I read when searching - it seems that graphics hardware acceleration doesn't work in chromium when PI is headless for some reason. In PI4 running Bullseye, this could be bypassed by uncommenting hdmi_force_hotplug=1 in /boot/config.txt - but this cannot be achieved in a similar way in Bookworm..
Statistics: Posted by belalik — Sat Feb 24, 2024 6:58 pm