Bug 101475 - Max Core Profile for OpenGL showing 0.0
Summary: Max Core Profile for OpenGL showing 0.0
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r600 (show other bugs)
Version: 17.1
Hardware: x86-64 (AMD64) Linux (All)
: high major
Assignee: Default DRI bug account
QA Contact: Default DRI bug account
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-17 00:02 UTC by vinf100
Modified: 2018-02-23 23:38 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Full output of glxinfo (84.01 KB, text/plain)
2018-02-23 23:15 UTC, vinf100
Details

Description vinf100 2017-06-17 00:02:04 UTC
Hello,

I have updated my mesa drivers from the oibaf ppa to 17.0.0-rc1.
However, when I run glxinfo | grep -v, it returns:

server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
    Max core profile version: 0.0
    Max compat profile version: 2.1
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 2.0
OpenGL version string: 2.1 Mesa 17.0.0-rc1
OpenGL shading language version string: 1.30
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 17.0.0-rc1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16

Why is it showing my core profile version to be 0.0?
I checked the logs, and I found no errors. When I run applications e.g. Unreal Editor 4 which require above openGL 3.0, they crash saying that they can not create the openGL context. 

I have an AMD graphics card, which is HD 5570.
Comment 1 Dylan Baker 2017-06-17 00:13:18 UTC
You have removed useful information, like which driver was actually loaded. You currently have GL 2.1, but for a core profile you need at least 3.2. I think the most likely scenario is that you're falling back to software rendering.

what does `glxininfo | grep renderer` return?
Comment 2 Dylan Baker 2017-06-17 00:16:45 UTC
Also, are you sure you're running 17.0.0-rc1? That is a very old release candidate, if you are running that you should update to 17.1.2.
Comment 3 vinf100 2017-06-17 00:27:06 UTC
glxinfo | grep renderer returns:
    GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
    GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
Extended renderer info (GLX_MESA_query_renderer):
OpenGL renderer string: Gallium 0.4 on AMD REDWOOD (DRM 2.43.0 / 4.4.0-79-generic, LLVM 3.8.0)

Also, how do  I update to 17.1.2?
Comment 4 vinf100 2017-06-17 00:57:49 UTC
Okay,

I used the ubuntu-x ppa to install the mesa 17.1.2, but for some reason, when I run glxinfo | grep version, it still returns:

server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
    Max core profile version: 0.0
    Max compat profile version: 2.1
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 2.0
OpenGL version string: 2.1 Mesa 17.0.0-rc1
OpenGL shading language version string: 1.30
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 17.0.0-rc1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16

What am I doing wrong?
Comment 5 vinf100 2017-06-17 22:52:07 UTC
I also tried installing it from source but now, it also shows:
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
    Max core profile version: 0.0
    Max compat profile version: 2.1
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 2.0
OpenGL version string: 2.1 Mesa 17.1.2
OpenGL shading language version string: 1.30
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 17.1.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16

glxinfo | grep renderer now returns:
    GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
    GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
Extended renderer info (GLX_MESA_query_renderer):
OpenGL renderer string: Gallium 0.4 on AMD REDWOOD (DRM 2.49.0 / 4.10.0-19-generic, LLVM 4.0.0)
Comment 6 Tobias Droste 2017-06-18 00:39:31 UTC
Do you build with "--enable-texture-float" and have the s3tc library installed?
Comment 7 vinf100 2017-06-18 05:59:06 UTC
I tried using --enable-texture-float, but it returned the same result.
Comment 8 vinf100 2017-06-18 09:41:11 UTC
It turns out that this bug is only minor. Although it reports 0.0, running a program with MESA_GL_VERSION_OVERRIDE works.
Comment 9 Jan Bruns 2017-08-12 09:21:36 UTC
Same here: upgrading from mesa 13.0.6 to 17.0.7 made glxinfo report core profile of 0.0 (from 3.3). But 13.0.6 seems to not support geometry shaders (core GL since 3.2) with AMD-350 APU, so the reported GL-version support probably already was incorrect before.
Comment 10 vinf100 2017-11-02 04:14:16 UTC
Hello, sorry to reopen this thread. 

I am still having the same problem i.e. the max core profile is showing at 0.0. 

glxinfo
Comment 11 vinf100 2017-11-02 04:16:20 UTC
    Hello, sorry to reopen this thread. 

    I am still having the same problem i.e. the max core profile is showing at 0.0. 

    glxinfo  | grep version returns:

    server glx version string: 1.4
    client glx version string: 1.4
    GLX version: 1.4
        Max core profile version: 0.0
        Max compat profile version: 2.1
        Max GLES1 profile version: 1.1
        Max GLES[23] profile version: 2.0
    OpenGL version string: 2.1 Mesa 17.2.4
    OpenGL shading language version string: 1.30
    OpenGL ES profile version string: OpenGL ES 2.0 Mesa 17.2.4
    OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16

    glxinfo | grep renderer:
        GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
        GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
    Extended renderer info (GLX_MESA_query_renderer):
    OpenGL renderer string: AMD REDWOOD (DRM 2.49.0 / 4.10.0-38-generic, LLVM 4.0.0)

    It used to show 3.3, but why does it now show the wrong version.

    Also, when I try to use MESA_GL_VERSION_OVERRIDE, it always fails for values above 2.1
Comment 12 vinf100 2018-02-23 13:11:27 UTC
Hello,

I updated to the 18.x preview release, and it is still not working. I am getting the exact same problem. The version number updates with glxinfo | grep version, but the core profiles values remain exactly the same. I do game design and 3D modelling, and many programs don't support openGl versions 2.x anymore. If this isn't fixed soon, I may have to get a new graphics card. I know this isn't a problem with my graphics card or linux, as I used to be able to get openGl version 3.3. Could someone please help me with this.

----------------------
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
    Max core profile version: 0.0
    Max compat profile version: 2.1
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 2.0
OpenGL version string: 2.1 Mesa 18.0.0-rc4
OpenGL shading language version string: 1.30
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 18.0.0-rc4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
---------------------

Thanks in advance
Comment 13 Emil Velikov 2018-02-23 20:22:49 UTC
vinf100@gmail.com instead of pasting multiple partial copies of the output, simply attach (as plain text) the complete thing - glxinfo &> glxinfo-output

There are multiple things that can go wrong and most can be deducted from ^^ info.

Note: MESA_GL_VERSION_OVERRIDE is more of a hack. In 90%+ of the cases you should not be touching it.

Also, please stop fiddling with the bug severity. Thanks
Comment 14 vinf100 2018-02-23 23:15:55 UTC
Created attachment 137569 [details]
Full output of glxinfo

Here's the full output.
Comment 15 Ilia Mirkin 2018-02-23 23:19:14 UTC
You appear to be missing GL_ARB_texture_float, which in turn means you won't get GL 3.0.

This happens when you haven't built mesa with --enable-texture-float, as you were told earlier.

How sure are you that you've done this?
Comment 16 vinf100 2018-02-23 23:38:25 UTC
OK, it worked now. Using --enable-texture-float now returns a version Max core profile version of 3.3. Don't know why it didn't work before, but it is working now. Thank you for all the help.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.