Torizon OS Issue Tracker

Description: When the device boots or reboots, sometimes the GUI is not brought up, and when inspecting the Weston container logs, the error "seatd returns 00:00:00.140 [ERROR] [seatd/seat.c:281] Could not make device fd drm master: Permission denied" is present.

Update: this is fixed on the Debian Containers for Torizon, and all TorizonCore 6 releases, including the 6.3.0, are not affected anymore by this bug. You must just use the "weston" or the ""touch-calibrator" Debian Containers for Torizon with version 3.1.1 or newer. Learn more about container tags and TorizonCore on TorizonCore Containers Tags and Versioning.

Workaround: Use the command "sudo systemctl edit --full docker-compose.service" and change the line with the "After" key from "After=docker.service" to "After=docker.service plymouth-quit.service".

This will increase the time to start the graphical application by a few seconds.

Update: the public workaround is not required anymore.You must just use the "weston" or the ""touch-calibrator" Debian Containers for Torizon with version 3.1.1 or newer. Learn more about container tags and TorizonCore on TorizonCore Containers Tags and Versioning.

Description: NXP GPUs doesn't seem to support GLX, therefore this has been disabled in meta-freescale, as xwayland: Drop GLX for i.MX GPU. This broke Xwayland on the Debian Container for Torizon.

Workaround: Update to the latest version of the Debian Containers for Torizon. At the moment, only software support is provided. 2D graphics acceleration will be added as soon as Xwayland falls back to software rendering due to broken Glamor support on i.MX8-based SoMs is concluded.

Description: On a recent build of the OpenCL sample, a runtime error of "clGetPlatformIDs (-1001) no platforms found" happen and prevents the benchmark from running.

This is fixed, the above sample has been updated.

Description: The Chromium and Cog containers were split, and HW acceleration on the GPU (rendering) enabled on Chromium. These changes have broken the startup of Portainer in our "TorizonCore with Evaluation Containers" image.

Description: The Qt sample "KMS cube" displays horizontal line artifacts and very high FPS on the parallel video output. The issue can only be reproduced on the KMS Cube sample.

This issue is inherited from the Toradex BSP, therefore there are no plans to fix it on the TorizonCore team. See ELB-4203 for more info.

Workaround: See ELB-4203 for a workaround.

Description: The Colibri iMX8X 1.0B is an early sample. We advise you to move to the latest version as soon as possible.

Workaround: While you don't procure a newer version, use the latest supported TorizonCore version 5.4.0.

Description: TorizonCore is rebooting on Colibri IMX8DX 1GB due to low memory issues.

Description: Poor chromium performance on Colibri iMX8X when running the Grafana sample application.

Description: Update Debian packages to the latest NXP BSP release (L5.4.70_2.3.2).

Description: Since we have now Colibri iMX8X V1.0D, let's remove "for V1.0C HW" from the image name.

Description: Add image type information (Docker, Podman) to /etc/os-release.

Description: Bump Portainer container version from 2.0.0 to 2.1.1.

Description: Add VNC and RDP support in the Weston container.

Description: It seems like QApplication which is used for Widgets does not support automatic translation of touch events to mouse events. That leads to touchscreen not working with QTWidgets applications.

Description: Update gstreamer-imx package to match the NXP 5.4 based release.

Description: Provide TorizonCore images for Colibri IMX8X with B0 silicon (hardware version V1.0B)

Description: Provide the OpenCV package and improve the container with DLR support, a compact runtime for Machine Learning Models.

Description: Create Debian packages and a sample container to have Qt with GPU acceleration support on iMX8.

Description: The mwifiex.conf file is missing in /etc/modprobe.d/, therefore it is not possible to use the WiFi interface in access point mode.

Workaround: Create the file on your own with the following content: 'options mwifiex driver_mode=0x3'

Description: Enable parallel RGB on Colibri iMX8X by default. Set resolution to 640x480.

Description: Enable CFS Quota/Period support on i.MX 8 series modules

Description: Create a tool to manage device tree overlays on device

Description: Support for Colibri iMX8X

Description: When running hardware-accelerated Chromium, SVG images are not rendered.

This is an issue in the upstream Chromium project, see the chromium-ozone-wayland 101 SVG issue, therefore the TorizonCore team will wait until there is a fix upstream.

Update: this issue only affects the Torizon container for Debian Bullseye (tag with major number equal to 2). The container for Debian Bookworm (tag with major number equal to 3) is not affected.

Workaround: There are alternatives:

• Use the Cog browser
• Use Chromium with hardware acceleration fully disabled as described in our article.
• Use Chromium with GPU rasterization disabled, but keep other GPU optimizations enabled, as described in the community thread SVG rendering fragmented on Torizon using torizon/weston-vivante:2.7.2 and torizon/chromium:2.6.0 containers
• Use the Chromium container for Debian Bookworm (tag major number equal to 3).