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? 
Hello, thank you for your detailed description and for sharing the steps you’ve followed.
To set up VNC access on your headless Verdin iMX8MP with the Ivy Carrier Board running Torizon 6.8, you’ll need to make sure the Weston compositor is properly configured to run without a physical monitor. By default, Weston requires an active display and won’t start the graphical environment (and thus VNC) if no display is detected.
Here’s how you can enable headless operation for VNC on your setup:
1. Use the Correct Container Image
With your hardware, use the torizon/weston-imx8 container image, not the Vivante variant. This is recommended for i.MX8MP SoMs:
docker pull torizon/weston-imx8:$CT_TAG_WESTON
2. Start Weston with Headless/Forced Output
You need to force-enable a display output in Weston, even though none is physically connected. This can be done by specifying an output as enabled in the Weston config file.
Create/modify the Weston config file (e.g., /home/torizon/weston.ini) with the following content to force-enable HDMI-A-1 in headless mode:
[output]
name=HDMI-A-1
mode=1920x1080
enable=true
Mount this config into your container. For example:
docker run -e ACCEPT_FSL_EULA=1 -d --rm --name=weston --net=host \
--env ENABLE_VNC=1 --cap-add CAP_SYS_TTY_CONFIG \
-v /dev:/dev -v /tmp:/tmp -v /run/udev/:/run/udev/ \
-v /home/torizon/weston.ini:/etc/xdg/weston/weston.ini \
--device-cgroup-rule='c 4:* rmw' --device-cgroup-rule='c 13:* rmw' \
--device-cgroup-rule='c 199:* rmw' --device-cgroup-rule='c 226:* rmw' \
--device-cgroup-rule='c 253:* rmw' \
torizon/weston-imx8:$CT_TAG_WESTON --developer \
--tty=/dev/tty7
3. Connect your VNC Client
Weston VNC is available on port 5900 by default:
vncviewer <DEVICE_IP>:5900
or
vncviewer <DEVICE_IP>::5900
(TightVNC, RealVNC, and others should work.)
Reference
Note: If you encounter authentication errors, make sure your VNC client does not require a password (the default server setup is without password for Torizon VNC).
Troubleshooting
- If you see errors about unavailable screens/displays in Weston logs (view with
docker logs weston), check your .ini file path and contents.
- Consider cleaning up any previously running Weston containers before starting a new one.
- Ensure that port 5900 is accessible on your network.
Let me know if you need further assistance or if this solves your issue!
Best regards, Toradex AI Assistant.
