Failed to create SDL window: Couldn't find matching GLX

Support for running, installing or compiling OpenMW

Before you submit a bug report for the first time, please read: Bug reporting guidelines
Post Reply
User avatar
owatnext
Posts: 22
Joined: 21 Apr 2016, 22:35

Failed to create SDL window: Couldn't find matching GLX

Post by owatnext » 24 Feb 2017, 03:57

Hello
I am having an issue with this "GLX error." From what I have gathered, I need to instal or enable some SDL module? I'm not sure exactly, but if that is the case, here is my SDL results of installed packages.

Code: Select all

[email protected]:~ $ dpkg -l *libsdl*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version      Architecture Description
+++-==============-============-============-=================================
un  libsdl-1.3-0   <none>       <none>       (no description available)
ii  libsdl-image1. 1.2.12-5+b5  armhf        Image loading library for Simple 
ii  libsdl-mixer1. 1.2.12-11+b1 armhf        Mixer library for Simple DirectMe
ii  libsdl-ttf2.0- 2.0.11-3     armhf        TrueType Font library for Simple 
un  libsdl1.2      <none>       <none>       (no description available)
un  libsdl1.2-all  <none>       <none>       (no description available)
un  libsdl1.2-esd  <none>       <none>       (no description available)
un  libsdl1.2-nas  <none>       <none>       (no description available)
un  libsdl1.2-oss  <none>       <none>       (no description available)
ii  libsdl1.2debia 1.2.15-10+rp armhf        Simple DirectMedia Layer
un  libsdl1.2debia <none>       <none>       (no description available)
un  libsdl1.2debia <none>       <none>       (no description available)
un  libsdl1.2debia <none>       <none>       (no description available)
un  libsdl1.2debia <none>       <none>       (no description available)
un  libsdl1.2debia <none>       <none>       (no description available)
un  libsdl1.2debia <none>       <none>       (no description available)
ii  libsdl2-2.0-0: 2.0.4+dfsg2- armhf        Simple DirectMedia Layer
glxError.png
Sorry if this is broken up information, I'm just not really sure where to start. Any info you need, just ask and I will provide it. :)

User avatar
psi29a
Posts: 4917
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: Failed to create SDL window: Couldn't find matching GLX

Post by psi29a » 24 Feb 2017, 11:33

What you forgot to mention and I had to infer from your dpkg list is that you are running on armhf.

There can a few things at play here:
* you don't have an opengl stack
* your driver doesn't expose the necessary GL bits
* if using debian's builds of armhf, it is compiled against GLESv2 which won't work


Can you give a bit more context here, including your platform?

User avatar
owatnext
Posts: 22
Joined: 21 Apr 2016, 22:35

Re: Failed to create SDL window: Couldn't find matching GLX

Post by owatnext » 24 Feb 2017, 15:09

Raspberry Pi model 3 B+
Raspbian Jessie, most up to date version.
I know there are problems with OpenMW and Debian/Raspberry Pis, but I have created exceptions in my preferences to allow it to download required packages in the form of a preferences file in /etc/apt/

User avatar
psi29a
Posts: 4917
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: Failed to create SDL window: Couldn't find matching GLX

Post by psi29a » 24 Feb 2017, 15:31

So you've enabled the VC4 driver and run glxinfo to verify that VC4 is listed and not swrast or llvmpipe?

I had a RPi2 and it worked a few months ago with OpenMW, I haven't tested lately however.

User avatar
owatnext
Posts: 22
Joined: 21 Apr 2016, 22:35

Re: Failed to create SDL window: Couldn't find matching GLX

Post by owatnext » 24 Feb 2017, 22:05

psi29a wrote:So you've enabled the VC4 driver and run glxinfo to verify that VC4 is listed and not swrast or llvmpipe
No, I haven't actually. I'll try that as soon as I get the chance and I'll keep you updated. Thanks :)

Update:
Alright, so I've tried enabling the driver via raspi-config, and it initially failed. I checked the terminal output and it appears that the programme had an issue with installing two unauthenticated packages, "compton libconfig9."
So, I manually installed them, successfully at that. Then I didn't have an issue enabling the driver (this one: G1 GL (Full KMS) OpenGL desktop driver with full KMS), so I did. Yet, even after that, I got the same error.

Here is the output of glxinfo, if that helps.
Spoiler: Show
glxgears runs fine, doesn't drop below 60fps if that means anything. I should have checked before I tried enabling the driver :P
But if I recall properly from months ago, it did run. (Don't quote me on that though.)

User avatar
psi29a
Posts: 4917
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: Failed to create SDL window: Couldn't find matching GLX

Post by psi29a » 27 Feb 2017, 15:26

Vendor: VMware, Inc. (0xffffffff)
Device: llvmpipe (LLVM 3.9, 128 bits) (0xffffffff)
Version: 13.0.0
Accelerated: no
Video memory: 925MB
Unified memory: no
Preferred profile: core (0x1)
This should be VC4, not llvmpipe. It is now using software rendering.

Try looking at dmesg and see if you can spot anything VC4 related.

It is entirely possible that you have VC4 loaded, but your xorg.conf is still using the wrong driver.

Look at this, it has screenshots:
https://www.phoronix.com/scan.php?page= ... pbian-RPi2

Straight from the horses' mouth:
https://github.com/anholt/mesa/wiki/VC4

User avatar
owatnext
Posts: 22
Joined: 21 Apr 2016, 22:35

Re: Failed to create SDL window: Couldn't find matching GLX

Post by owatnext » 27 Feb 2017, 22:05

psi29a wrote:
Try looking at dmesg and see if you can spot anything VC4 related.

Code: Select all

[    3.495676] [drm] Initialized drm 1.1.0 20060810
[    3.615166] vc4-drm soc:gpu: bound 3f902000.hdmi (ops vc4_hdmi_ops [vc4])
[    3.615216] vc4_dsi 3f700000.dsi: DSI not set up by firmware.
[    3.615294] vc4-drm soc:gpu: bound 3f700000.dsi (ops vc4_dsi_ops [vc4])
[    3.615389] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4])
[    3.615615] vc4-drm soc:gpu: bound 3f206000.pixelvalve (ops vc4_crtc_ops [vc4])
[    3.616661] vc4-drm soc:gpu: bound 3f207000.pixelvalve (ops vc4_crtc_ops [vc4])
[    3.616866] vc4-drm soc:gpu: bound 3f807000.pixelvalve (ops vc4_crtc_ops [vc4])
[    3.616989] vc4-drm soc:gpu: bound 3fc00000.v3d (ops vc4_v3d_ops [vc4])
Found this with dmesg.

I attempted to look at/modify my Xorg.conf file, but it wasn't there under /etc/X11/, so I assumed I didn't have Xorg installed. Installed Xorg successfully and attempted to generate the file, but I haven't had any success in getting it to appear. Do I need to build any drivers/packages/et cetera? Sorry, I'm just not sure what to do next because everywhere that I am reading says to just enable it via raspi-config. But that didn't work, unfortunately.
Spoiler: Show

Post Reply