Hi @simmania ,
You can check the TorizonCore version by typing
cat /etc/os-release
The graphical glitches appear to be very similar to a Chromium bug we encountered a few months ago:
This only happens on the bullseye version of the Chromium container, which we rolled back for TorizonCore 6.3.0. We did this because the more recent bookworm Chromium container doesn’t work in one of our SoMs (Apalis iMX8QM), but it shouldn’t cause problems on the Verdin iMX8M Plus you’re using.
I’ll pass this issue internally for further investigation.
As a workaround, you can change the Chromium container to the the bookworm one by altering the docker-compose.yml file that is read when initializing the containers:
- As root, access
/var/sota/storage/docker-compose/docker-compose.yml, then change the line:
image: torizon/chromium@sha256:9d363b140a5f4584392432b4ed548c0b6fd5466fbf41b28e834f31924fb62d6d
to
image: torizon/chromium:3
Save the file and reboot the module. You shouldn’t see the graphical glitches on the bookworm version of the Chromium container image.
Best regards,
Lucas Akira