Torizon OS 7 + weston-imx8 + chromium-imx8: WebGL not supported

Technical Support
, ,
1

I know that Torizon OS 7 is under development, so it’s not stable at all, and the development team has been working hard on it.
I started my test on the first monthly, as I explained here and so I can provide my first feedback.
I started torizon/weston-imx8:next + torizon/chromium-imx8:next as described on github.
I can see https://www.toradex.com/ properly.
But when I try WebGL Fishtank example I see an error page with the message

It does not appear your computer supports WebGL.
Status: Could not create a WebGL context, VENDOR = 0xffff, DEVICE = 0xffff, GL_VENDOR = Disabled, GL_RENDERED = Disabled, Sandboxed = no, Optimus = no, AMD switchable = no, Reset notification strategy = 0x0000, ErrorMessage = BindToCurrentSequence failed.

In case it helps,
docker_log.txt (13.1 KB)
is the log from the two containers.

2

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:

It seems like you’re encountering an issue with WebGL support in the Chromium container on Torizon OS 7 for the i.MX8 platform. Given that Torizon OS 7 is still under development, there might be some instability or missing features.

Here are a few steps you can take to troubleshoot and potentially resolve the issue:

  1. Check GPU Hardware Acceleration:
    Ensure that GPU hardware acceleration is enabled for Chromium. By default, it should be enabled for i.MX8 devices, but you can explicitly set the necessary flags. You can start the Chromium container with the following command:

    docker run -d --rm --name=chromium \
  --network=host \
  --device=/dev/dri \
  --device=/dev/video0 \
  -v /tmp:/tmp \
  -e "WAYLAND_DISPLAY=wayland-0" \
  torizon/chromium-imx8:next \
  --use-gl=egl --enable-webgl --ignore-gpu-blacklist

  2. Verify Weston Configuration:
    Ensure that the Weston container is properly configured to support GPU acceleration. You might need to check the weston.ini file for any necessary configurations. For example, you can bind mount a custom weston.ini file with the appropriate settings.

  3. Check Docker Logs:
    Review the logs from both the Weston and Chromium containers for any errors or warnings that might provide more insight into the issue. You can use the following commands to view the logs:

    docker logs <weston-container-id>
docker logs <chromium-container-id>

  4. Update to Latest Versions:
    Since Torizon OS 7 is under active development, ensure that you are using the latest versions of the Weston and Chromium containers. There might have been recent fixes or improvements that address the issue.

  5. Fallback to Stable Versions:
    If the issue persists and you need a stable environment, consider using the stable versions of Torizon OS and the corresponding containers. This might help you avoid any development-related instability.

  6. Report the Issue:
    If none of the above steps resolve the issue, consider reporting it to the Toradex support team or the Torizon development team. Provide them with detailed logs and steps to reproduce the issue, which will help them diagnose and fix the problem.

Given the context, these steps should help you troubleshoot the WebGL support issue in the Chromium container on Torizon OS 7 for the i.MX8 platform. If you need further assistance, please provide more details or logs, and I’ll do my best to help.

Please, also check if these links can help you solve your problem:

GPU Monitoring on TorizonCore.

3

Greetings @vix,

Thank you very much for the feedback it is appreciated. I’ve forwarded the feedback to our team.

Best Regards,
Jeremias

4

Thanks @jeremias.tx
let me know here the feedback from the team.

5

The team is aware of this issue and will address it when our planning and priority allows it.

Best Regards,
Jeremias

1 Like