libGL error: failed to load driver: i915

gh0stzk · 2022-03-30 14:25:08

Hello, with the new mesa 22 my retroarch shows this error in terminal:

libGL error: MESA-LOADER: failed to open i915: /usr/lib/dri/i915_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)
libGL error: failed to load driver: i915

i updated it yesterday mesa package and kernel to 5.17.1 zen. i have xf86-video-intel.

lspci -k:

00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller (rev 10)
	Subsystem: Hewlett-Packard Company Device 2a78
	Kernel modules: intel_agp
00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 10)
	Subsystem: Hewlett-Packard Company Device 2a78
	Kernel driver in use: i915
	Kernel modules: i915

I search in mesa changelog and i found classic/i915: Remove driver
My 20-intel.conf is:

Section "Device"
	Identifier	"Intel Graphics"
	Driver		"Intel"
	Option		"AccelMethod"	"sna"
	Option		"DRI"		"3"
	Option		"TearFree"	"true"
EndSection

My mkinitcpio.conf

MODULES=(intel_agp i915)

as always in this post, yesterday works before update.

so what can i do? ah.. firefox, mpv, popcorn-time, netflix. spotify works fine without lags, is only retroarch.
I know i have old graphics integrated but works fine yesterday.

Last edited by gh0stzk (2022-03-30 14:26:58)

Trilby · 2022-03-30 14:50:29

It appears the mesa package has been split and no longer provides i915. If you really need i915, you can install [extra]/mesa-amber.

Alternatively you could set MESA_LOADER_DRIVER_OVERRIDE to see if retroarch will run with one of the included drivers (eg iris).

Side note: None of your x11 intel driver, 20-intel-conf, or mkinitcpio usage of i915 are related to this. Despite sharing the name, the kernel i915 module and mesa userspace i915 driver refer to different things.

Last edited by Trilby (2022-03-30 14:54:23)

gh0stzk · 2022-03-30 15:12:24

apparently mesa-amber causes a lot of clonflics with intalled packages, i will not mess with that now lol, so maybe next version of retroarch fix problem, well i just change emulator, while all other apps works, im fine. Thank u!

And no, i set MESA_LOADER_DRIVER_OVERRIDE= with d3d12, kms_swrast, swrast, but no works.

V1del · 2022-03-30 15:24:10

Your useful/usable MESA_LOADER_DRIVER_OVERRIDE= values would be iris or crocus all the others don't make much sense.

Not sure what kind of conflicts you are referring to, the point of mesa-amber is that it would be a logical direct replacement of mesa, if you get actual conflicts that would be a packaging bug.

Edit: Which appears to be the case: https://bugs.archlinux.org/task/74277

Last edited by V1del (2022-03-30 15:36:52)

gh0stzk · 2022-03-30 15:35:02

V1del wrote:

Your useful/usable MESA_LOADER_DRIVER_OVERRIDE= values would be iris or crocus all the others don't make much sense.
Not sure what kind of conflicts you are referring to, the point of mesa-amber is that it would be a logical direct replacement of mesa, if you get actual conflicts that would be a packaging bug.

yeah the conflics:

:: mesa-amber y mesa están en conflicto. ¿Quitar mesa? [s/N] s
error: no se pudo preparar la operación (no se pudieron satisfacer las dependencias)
:: quitando mesa se rompe la dependencia con «mesa», necesaria para el paquete gst-plugins-base-libs
:: quitando mesa se rompe la dependencia con «mesa», necesaria para el paquete gtk3
:: quitando mesa se rompe la dependencia con «mesa», necesaria para el paquete libglvnd
:: quitando mesa se rompe la dependencia con «opengl-driver», necesaria para el paquete libglvnd
:: quitando mesa se rompe la dependencia con «mesa», necesaria para el paquete qemu
:: quitando mesa se rompe la dependencia con «mesa», necesaria para el paquete qt5-base
:: quitando mesa se rompe la dependencia con «mesa», necesaria para el paquete retroarch
:: quitando mesa se rompe la dependencia con «mesa», necesaria para el paquete virglrenderer
:: quitando mesa se rompe la dependencia con «mesa», necesaria para el paquete xf86-video-intel

if i MESA_LOADER_DRIVER_OVERRIDE=crocus

zsh: segmentation fault (core dumped)  MESA_LOADER_DRIVER_OVERRIDE=crocus retroarch

if i MESA_LOADER_DRIVER_OVERRIDE=iris retroarch

error: Kernel is too old for Iris. Consider upgrading to kernel v4.16.

libGL error: failed to create dri screen
libGL error: failed to load driver: iris

gh0stzk · 2022-03-30 15:36:39

My dri in /usr/lib/dri availables are:

crocus_dri.so* kms_swrast_dri.so* r600_dri.so* virtio_gpu_dri.so*
d3d12_dri.so* nouveau_dri.so* radeonsi_dri.so* vmwgfx_dri.so*
iris_dri.so* r300_dri.so* swrast_dri.so* zink_dri.so*

V1del · 2022-03-30 15:42:14

Yes see my edit, there's indeed a bug in how mesa-amber is packaged. FWIW because it's weird to me that just retroarch would break, without any custom overrides what do you get for

glxinfo -B

from mesa-utils?

gh0stzk · 2022-03-30 15:59:19

V1del wrote:

Yes see my edit, there's indeed a bug in how mesa-amber is packaged. FWIW because it's weird to me that just retroarch would break, without any custom overrides what do you get for
glxinfo -B
from mesa-utils?

glxinfo -B

name of display: :0
libGL error: MESA-LOADER: failed to open i915: /usr/lib/dri/i915_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)
libGL error: failed to load driver: i915
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Mesa/X.org (0xffffffff)
    Device: llvmpipe (LLVM 13.0.1, 128 bits) (0xffffffff)
    Version: 22.0.0
    Accelerated: no
    Video memory: 2970MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.5
    Max compat profile version: 4.5
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Mesa/X.org
OpenGL renderer string: llvmpipe (LLVM 13.0.1, 128 bits)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 22.0.0
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.5 (Compatibility Profile) Mesa 22.0.0
OpenGL shading language version string: 4.50
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

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

Trilby · 2022-03-30 16:27:24

Ah, wait, back up... what kernel are you running, and why is it ~4 years old or older?

Last edited by Trilby (2022-03-30 16:29:27)

V1del · 2022-03-30 16:29:38

Yes so this doesn't actually work properly and you just drop to the software renderer regardless.

Follow the bug I linked, this needs to get fixed there so you can properly switch to amber. If you want to try your own hand at it you could use the ABS https://wiki.archlinux.org/title/Arch_B … _using_Git and adjust the provides line so that the - is a =

But yes the above might also be a worthy consideration, because afaik even old level GPUs should at least pick crocus instead.

Last edited by V1del (2022-03-30 16:30:39)

gh0stzk · 2022-03-30 16:41:18

Trilby wrote:

Ah, wait, back up... what kernel are you running, and why is it ~4 years old or older?

im running latest linux-zen and linux 5.17

gh0stzk · 2022-03-30 16:44:52

V1del wrote:

Yes so this doesn't actually work properly and you just drop to the software renderer regardless.
Follow the bug I linked, this needs to get fixed there so you can properly switch to amber. If you want to try your own hand at it you could use the ABS https://wiki.archlinux.org/title/Arch_B … _using_Git and adjust the provides line so that the - is a =
But yes the above might also be a worthy consideration, because afaik even old level GPUs should at least pick crocus instead.

apparently it's just retroarch, all other apps run even smoother i feel. I just installed epsxe ps emulator and it runs fine, so it will be retroarch problem.

when i start retroarch mi cpu go to 90% load and fans start working faster.

Trilby · 2022-03-30 16:58:03

In that case that's a pretty odd error message from retroarch asking you to upgrade to at least 4.16.

V1del · 2022-03-30 17:32:42

It's an iris/mesa message, that probably should rather say something like GPU not supported or so.

@gh0strk that's not really a good comparison, depending on which epsxe plugin you are using it's likely it doesn't even use the GPU, while retroarch wants to use it guaranteed. For all intents and purposes your GPU acceleration is currently broken even if it "appears" fine for plain 2D usecases. xf86-video-intel has actual 2D acceleration without relying on OpenGL, in the few cases were it is still an actually valid option like yours, you are not going to see much difference for non-OpenGL 2D workloads

FWIW you should be able to "fix" retroarch by editing your ~/.config/retroarch.cfg and changing

video_driver = "x11"

to make it use a software X11 only renderer

Last edited by V1del (2022-03-30 17:44:16)

gh0stzk · 2022-03-30 18:13:00

V1del wrote:

It's an iris/mesa message, that probably should rather say something like GPU not supported or so.
@gh0strk that's not really a good comparison, depending on which epsxe plugin you are using it's likely it doesn't even use the GPU, while retroarch wants to use it guaranteed. For all intents and purposes your GPU acceleration is currently broken even if it "appears" fine for plain 2D usecases. xf86-video-intel has actual 2D acceleration without relying on OpenGL, in the few cases were it is still an actually valid option like yours, you are not going to see much difference for non-OpenGL 2D workloads
FWIW you should be able to "fix" retroarch by editing your ~/.config/retroarch.cfg and changing
video_driver = "x11"
to make it use a software X11 only renderer

Ok i understand.
I set x11 to retroarch, but only shows blackscreen on retroarch, i thought it was bspwm but i installed mate and xfce to tet and still blackscreen when loading retroarch.

gh0stzk · 2022-03-30 18:20:09

V1del wrote:

It's an iris/mesa message, that probably should rather say something like GPU not supported or so.
@gh0strk that's not really a good comparison, depending on which epsxe plugin you are using it's likely it doesn't even use the GPU, while retroarch wants to use it guaranteed. For all intents and purposes your GPU acceleration is currently brokenr

yes not good comparision, the plugin i use in epsxe is the core gpu 2.0 with blit mode openglv2

gh0stzk · 2022-03-30 18:55:11

I had no transparencys in picom but i fixed with vsync = false

seth · 2022-03-30 19:21:59

Do you get away w/

pacman -S mesa-amber --assume-installed mesa=21.3.8

(might be preferable to running on SW)

gh0stzk · 2022-03-30 21:14:47

seth wrote:

Do you get away w/
pacman -S mesa-amber --assume-installed mesa=21.3.8
(might be preferable to running on SW)

try it but error, mesa-amber and mesa are in conflict

just tried on qemu in new installation to test, if i just install mesa-amber still error.so maybe i just need to wait for updates

gh0stzk · 2022-03-31 03:21:08

i download previous version of mesa and installed. Hopefully there arent conflics too soon.

kokoko3k · 2022-03-31 13:00:08

Screw THAT, i've had older drm related libs installed, sorry.

Just updated:
My glxinfo is:

koko@Gozer# glxinfo
name of display: :0
Error: couldn't find RGB GLX visual or fbconfig

The following has been set prior to reboot:

koko@Gozer# grep crocus /etc/environment
MESA_LOADER_DRIVER_OVERRIDE=crocus

And i don't know if it is related or not, but that doesn't seem ti be picked by Xorg:

koko@Gozer# sudo strings /proc/`pidof Xorg`/environ 
LANGUAGE=it_IT.UTF-8
PWD=/
SYSTEMD_EXEC_PID=715
LANG=it_IT.UTF-8
INVOCATION_ID=2ef17d0a819548baa4e562169c577b5e
SHLVL=0
JOURNAL_STREAM=8:25607
LC_COLLATE=C
XCURSOR_THEME=Jimmac
XDG_DATA_DIRS=/var/lib/flatpak/exports/share:/usr/local/share/:/usr/share/
PATH=/usr/local/sbin:/usr/local/bin:/usr/bin

While it is correctly set in the Desktop environment loaded afterwards.

Do i need to install mesa-amber or there is another way to proceed, maybe?

PS: shame on me, and thanks V1del anyway.

Last edited by kokoko3k (2022-03-31 13:12:40)

V1del · 2022-03-31 13:07:54

I'm personally just using /etc/profile for variables I expect to be available everywhere, hasn't failed me yet.

Shiba · 2022-04-03 14:19:43

kokoko3k wrote:

koko@Gozer# glxinfo
name of display: :0
Error: couldn't find RGB GLX visual or fbconfig

I have the same problem and a few things like nextcloud-client segfault. What did you mean by "older drm libs installed"?

Scimmia · 2022-04-03 14:22:38

mesa-amber provides has been fixed. Install it if you need it.

kokoko3k · 2022-04-03 16:28:00

Shiba wrote:

kokoko3k wrote:
koko@Gozer# glxinfo
name of display: :0
Error: couldn't find RGB GLX visual or fbconfig
I have the same problem and a few things like nextcloud-client segfault. What did you mean by "older drm libs installed"?

In the past I made some tests and installed an older libdrm in /usr/local/lib which were loaded instead of the one installed by official repo in /usr/lib
check yours:

>ldd /usr/lib/Xorg |grep drm
        libdrm.so.2 => /usr/lib/libdrm.so.2

and

>pacman -Q libdrm
libdrm 2.4.110-1

Arch Linux

#1 2022-03-30 14:25:08

libGL error: failed to load driver: i915

#2 2022-03-30 14:50:29

Re: libGL error: failed to load driver: i915

#3 2022-03-30 15:12:24

Re: libGL error: failed to load driver: i915

#4 2022-03-30 15:24:10

Re: libGL error: failed to load driver: i915

#5 2022-03-30 15:35:02

Re: libGL error: failed to load driver: i915

#6 2022-03-30 15:36:39

Re: libGL error: failed to load driver: i915

#7 2022-03-30 15:42:14

Re: libGL error: failed to load driver: i915

#8 2022-03-30 15:59:19

Re: libGL error: failed to load driver: i915

#9 2022-03-30 16:27:24

Re: libGL error: failed to load driver: i915

#10 2022-03-30 16:29:38

Re: libGL error: failed to load driver: i915

#11 2022-03-30 16:41:18

Re: libGL error: failed to load driver: i915

#12 2022-03-30 16:44:52

Re: libGL error: failed to load driver: i915

#13 2022-03-30 16:58:03

Re: libGL error: failed to load driver: i915

#14 2022-03-30 17:32:42

Re: libGL error: failed to load driver: i915

#15 2022-03-30 18:13:00

Re: libGL error: failed to load driver: i915

#16 2022-03-30 18:20:09

Re: libGL error: failed to load driver: i915

#17 2022-03-30 18:55:11

Re: libGL error: failed to load driver: i915

#18 2022-03-30 19:21:59

Re: libGL error: failed to load driver: i915

#19 2022-03-30 21:14:47

Re: libGL error: failed to load driver: i915

#20 2022-03-31 03:21:08

Re: libGL error: failed to load driver: i915

#21 2022-03-31 13:00:08

Re: libGL error: failed to load driver: i915

#22 2022-03-31 13:07:54

Re: libGL error: failed to load driver: i915

#23 2022-04-03 14:19:43

Re: libGL error: failed to load driver: i915

#24 2022-04-03 14:22:38

Re: libGL error: failed to load driver: i915

#25 2022-04-03 16:28:00

Re: libGL error: failed to load driver: i915

Board footer