Weston crashing on imx8mp, OS 7.2 for chromium kiosk

Technical Support
, ,
2

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

Did you like my answer? :+1: :-1:

Hello! Thank you for providing detailed logs and a description of your setup. Based on the information you shared, the issue is related to Weston’s use of the g2d renderer on your Verdin iMX8M Plus. The log messages such as:

g2d_blitEx: Invalid src rect, left 0, top 0, right 0, bottom 0, width 0, height 0, stride 0!

indicate that Weston is passing invalid source rectangles to the g2d hardware acceleration driver, which could result in the display going completely black after a while, as you’re observing.

Potential Solutions and Debug Steps:

  1. Disable the g2d Renderer
    Try running Weston without the --use-g2d argument. The g2d renderer can sometimes introduce compatibility or stability issues, depending on the graphics stack and application behaviors.

    Edit your Weston container command to remove --use-g2d. If you’re using a Docker Compose file, look for the line like:

    command: weston -Bdrm-backend.so -Swayland-0 --use-g2d

    and change it to:

    command: weston -Bdrm-backend.so -Swayland-0

    Then restart the container and check if the issue persists.

  2. Review weston.ini Configuration
    Double-check your /etc/xdg/weston/weston.ini (or /etc/xdg/weston-dev/weston.ini) for any unusual display or renderer-related settings that could be causing a conflict. You can find information on how to customize and troubleshoot weston.ini here:
    Working with Weston on Torizon OS | Toradex Developer Center

  3. Verify Display Configuration
    According to your log, your LVDS display is running at 1280x800@60Hz:

    Output LVDS-1 (crtc 33) video modes: 
1280x800@60.0, preferred, current, 68.2 MHz

    Confirm that these match your physical display’s specs and that there haven’t been any recent changes to your device tree or display hardware configuration.

  4. Check DRM Device Selection
    The log shows Weston is initializing with /dev/dri/card1. Make sure this is the correct device for your display subsystem, and that no additional graphics devices have been added/removed which would change device enumeration.
    More information:
    Working with Weston on Torizon OS | Toradex Developer Center

  5. Collect Further Logs
    For more granular debugging, you can inspect complete logs with:

    docker logs weston

    This may help to correlate whether a specific application or process is triggering the g2d errors just before the display goes dark.

Next Steps:
Try the first step—disabling g2d—and see if the black screen issue disappears. If Weston is stable without g2d, that strongly points to a problem in the g2d rendering path, which can sometimes be bypassed on the NXP i.MX8MP SOC family by relying on the software renderer or alternate GPU hardware acceleration.

Let me know if taking these steps resolves your issue or if you need more specific guidance!

Best regards,
Toradex AI Assistant.

References: