This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

libGL error on running FVP

Hi,

When I try to start "FVP_MPS2_Cortex-M55" I get the following error:

```

telnetterminal0: Listening for serial connection on port 5000
telnetterminal1: Listening for serial connection on port 5001
telnetterminal2: Listening for serial connection on port 5002
libGL error: MESA-LOADER: failed to open iris (search paths /usr/lib/dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open iris (search paths /usr/lib/dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open swrast (search paths /usr/lib/dri)
libGL error: failed to load driver: swrast
X 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 library
local/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 gallium
local/mesa 20.0.6-2
    An open-source implementation of the OpenGL specification
local/mesa-demos 8.4.0-4
    Mesa demos and tools incl. glxinfo + glxgears
local/mesa-vdpau 20.0.6-2
    Mesa VDPAU drivers
local/vulkan-intel 20.0.6-2
    Intel's Vulkan mesa driver
local/vulkan-mesa-layer 20.0.6-2
    Vulkan overlay layer to display information about the application
local/vulkan-radeon 20.0.6-2
    Radeon's Vulkan mesa driver

```

Output of `glxinfo -B`:

```

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended 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.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) HD Graphics 520 (SKL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.0.6
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.0.6
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.0.6
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

```

Any help is appreciated :)

Parents
  • Hi,

    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

Reply
  • Hi,

    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

Children