Skip to main content
DRM modetest ensures that the DSI and the DPU paths are working effectively. To verify the display driver topology, run the DRM modetest.
You must enable SSH to connect to the target device. For instructions, see Sign in using SSH.
  1. To kill the Weston client application, run the following command in the device shell:
  2. To kill all Weston processes, run the following command:
    Running only the systemctl stop weston.service command generates the following warning:
    Stopping weston.service, but its triggering units are still active: weston.socket
    This behavior is expected because Weston is configured as a socket-activated service. To completely stop the display subsystem, stop both the socket and the service using the command in Step 2.
  3. To change permissions of the modetest application, run the following command:
  4. To view the connector IDs and modes, run the following command:
  5. To verify DRM modes and connector information, pull the /opt/drm_mode.txt file locally on your host computer. Use the Secure Copy Protocol (SCP) to pull the drm_mode.txt file from the device to your host computer. For example:
    When prompted for a password, enter oelinux123.
The following figure shows the output from the /opt/drm_mode.txt file.
Figure: Command prompt output
  1. To set the connector ID and mode name, use the following syntax with the relevant values from the /opt/drm_mode.txt file:
    Where <Connector id> and <mode name> are the values retrieved from the /opt/drm_mode.txt file.
  2. To start the modetest application, run the following sample command using the connector ID and the mode name retrieved from the /opt/drm_mode.txt file. For example:
    Start the DRM test application and ignore the warning log: Failed to set gamma: Function not implemented.
    Figure: DRM modetest output
  3. To kill the modetest application, select CTRL + C.
    Ensure that you Relaunch Weston.