Arch Linux

E404NNF

Member

Registered: 2021-02-08

Posts: 5

[SOLVED] OpenGL behaving weirdly on Intel HD 2500

Hey! I just updated MESA recently and OpenGL apps started to act weirdly, I see some graphical issues (as shown in the screenshot), i tried deleting the shader cache directory in ~/.cache, and still same issue, I also tried downgrading MESA and the same issue still appears, what can i do to try and fix this?

glxinfo output: https://pastebin.com/raw/qPVscubY

glxinfo -B output:

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel Open Source Technology Center (0x8086)
    Device: Mesa DRI Intel(R) HD Graphics 2500 (IVB GT1) (0x152)
    Version: 20.3.4
    Accelerated: yes
    Video memory: 1536MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.2
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.0
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 2500 (IVB GT1)
OpenGL core profile version string: 4.2 (Core Profile) Mesa 20.3.4
OpenGL core profile shading language version string: 4.20
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.0 Mesa 20.3.4
OpenGL shading language version string: 1.30
OpenGL context flags: (none)

OpenGL ES profile version string: OpenGL ES 3.0 Mesa 20.3.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

If any other info is needed tell me! :)

Last edited by E404NNF (2021-02-08 17:45:06)

seth

Member

Registered: 2012-09-03

Posts: 58,748

Re: [SOLVED] OpenGL behaving weirdly on Intel HD 2500

modesetting or xf86-video-intel? Does it matter?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

E404NNF

Member

Registered: 2021-02-08

Posts: 5

Re: [SOLVED] OpenGL behaving weirdly on Intel HD 2500

Sorry i do not understand what you mean, are you asking if i tried modestting or using xf86-video-intel? if yes, i haven't tried both

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,229

Re: [SOLVED] OpenGL behaving weirdly on Intel HD 2500

Which of the two are you using and does it make a difference on this issue if you opt for one or the other (based on past experience, if you are currently using xf86-video-intel you should definitely try without)

E404NNF

Member

Registered: 2021-02-08

Posts: 5

Re: [SOLVED] OpenGL behaving weirdly on Intel HD 2500

I'm not using either, just plain MESA.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,229

Re: [SOLVED] OpenGL behaving weirdly on Intel HD 2500

That's impossible, you run a xorg server (... or wayland in which case we'd suggest to check if you can reproduce on xorg) and xorg will either run on xf86-video-intel if it's installed or on the built-in modesetting driver.

The question here is whether this is an actual issue that's reproducible on either of the two backends, or only a quirk of xf86-video-intel/modesetting in which case it might not be inherently mesa to blame. If you are sure it's a mesa issue (as in you can downgrade just mesa and the issue disappears, you could do a bisection to find the offending commit and report  a bug

Last edited by V1del (2021-02-08 16:54:54)

E404NNF

Member

Registered: 2021-02-08

Posts: 5

Re: [SOLVED] OpenGL behaving weirdly on Intel HD 2500

Oh right, sorry, i forgot about it, yeah I'm using modesetting, sorry again.
The issue seems to be reproducible on Wayland too, and no, downgrading didn't help, which was confusing to me.
I'll try xf86-video-intel

Edit: same issue still occurs

Last edited by E404NNF (2021-02-08 17:19:07)

E404NNF

Member

Registered: 2021-02-08

Posts: 5

Re: [SOLVED] OpenGL behaving weirdly on Intel HD 2500

Nevermind, downgrading the kernel worked for some reason, I downgraded from linux-zen-5.10.13.zen to linux-zen-5.10.11.zen, i was able to reproduce it on linux-5.10.13 but not on linux-5.10.11 too, should i report this bug to the kernel devs or to mesa? I don't know what/who to blame here...
Sorry for disturbance
I'll mark the thread as solved for now
EDIT: The issue seems to be happening only in 5.10.13

Last edited by E404NNF (2021-02-08 18:46:04)