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
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"?
]]>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.
]]>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
]]>pacman -S mesa-amber --assume-installed mesa=21.3.8
(might be preferable to running on SW)
]]>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
]]>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.
@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
]]>