Hi,
When I try to start "FVP_MPS2_Cortex-M55" I get the following error:
```
telnetterminal0: Listening for serial connection on port 5000telnetterminal1: Listening for serial connection on port 5001telnetterminal2: Listening for serial connection on port 5002libGL error: MESA-LOADER: failed to open iris (search paths /usr/lib/dri)libGL error: failed to load driver: irislibGL error: MESA-LOADER: failed to open iris (search paths /usr/lib/dri)libGL error: failed to load driver: irislibGL error: MESA-LOADER: failed to open swrast (search paths /usr/lib/dri)libGL error: failed to load driver: swrastX Error of failed request: GLXBadContext Major opcode of failed request: 152 (GLX) Minor opcode of failed request: 6 (X_GLXIsDirect) Serial number of failed request: 116 Current serial number in output stream: 115
I'm running on Linux 5.4.36-1-MANJARO
Output of `pacman -Qs mesa`:
local/glu 9.0.1-1 Mesa OpenGL Utility librarylocal/lib32-glu 9.0.1-1 Mesa OpenGL utility library (32 bits)local/lib32-mesa 20.0.6-2 An open-source implementation of the OpenGL specification (32-bit)local/lib32-mesa-demos 8.4.0-1 Mesa demos and tools (32-bit)local/lib32-mesa-vdpau 20.0.6-2 Mesa VDPAU drivers (32-bit)local/lib32-vulkan-intel 20.0.6-2 Intel's Vulkan mesa driver (32-bit)local/lib32-vulkan-radeon 20.0.6-2 Radeon's Vulkan mesa driver (32-bit)local/libva-mesa-driver 20.0.6-2 VA-API implementation for galliumlocal/mesa 20.0.6-2 An open-source implementation of the OpenGL specificationlocal/mesa-demos 8.4.0-4 Mesa demos and tools incl. glxinfo + glxgearslocal/mesa-vdpau 20.0.6-2 Mesa VDPAU driverslocal/vulkan-intel 20.0.6-2 Intel's Vulkan mesa driverlocal/vulkan-mesa-layer 20.0.6-2 Vulkan overlay layer to display information about the applicationlocal/vulkan-radeon 20.0.6-2 Radeon's Vulkan mesa driver
Output of `glxinfo -B`:
name of display: :0display: :0 screen: 0direct rendering: YesExtended renderer info (GLX_MESA_query_renderer): Vendor: Intel (0x8086) Device: Mesa Intel(R) HD Graphics 520 (SKL GT2) (0x1916) Version: 20.0.6 Accelerated: yes Video memory: 3072MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2OpenGL vendor string: IntelOpenGL renderer string: Mesa Intel(R) HD Graphics 520 (SKL GT2)OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.0.6OpenGL core profile shading language version string: 4.60OpenGL core profile context flags: (none)OpenGL core profile profile mask: core profileOpenGL version string: 4.6 (Compatibility Profile) Mesa 20.0.6OpenGL shading language version string: 4.60OpenGL context flags: (none)OpenGL profile mask: compatibility profileOpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.0.6OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
Any help is appreciated :)
Is this inside a VM?I assume other X apps work (such as xclock)?
Can you try
export DISPLAY=0On a terminal before launching the model?
No, this is not inside a VM.
After export DISPLAY=0, I get the following output on running the FVP:
telnetterminal0: Listening for serial connection on port 5000telnetterminal1: Listening for serial connection on port 5001telnetterminal2: Listening for serial connection on port 5002Window could not be created! SDL Error: No available video device
The same happens also when running FVP from inside Arm Development Studio IDE
As Rob notes this is an unsupported distro - so it may involve moving to one of Ubuntu or CentOS/RHEL.I suspect the DISPLAY may be causing issue (as I saw almost the same error a week ago) , the env value I asked to set would disable display completely and we could see if libs really were causing the issue.
Can you check what the DISPLAY env var is normally set to and tell me and then try setting it to "localhost:0.0" or ":0" or ":0.0"?
If this doesn't progress it, trying a supported distro may be the way forward.
Regards
Chris
Hi,It is set to ":0"
Changing it to "localhost:0.0" gives "Window could not be created! SDL Error: No available video device", using ":0" and ":0.0" gives the original error.I've now installed Ubuntu on a VM where it works, so thanks for your help!