You are not logged in.
Pages: 1
I'm running 64 bit arch with xf86-video-ati (on an R9 290). If I run glxgears32, I get the following error:
libGL error: unable to load driver: radeonsi_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: radeonsi
libGL error: unable to load driver: radeonsi_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: radeonsi
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 156 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x0
Serial number of failed request: 42
Current serial number in output stream: 44
But regular "glxgears" works fine. Steam (a 32-bit application) also fails to run, but the Dolphin emulator (a 64-bit application) works fine. This suggests this is strictly a 32-bit issue. I'm not sure what to do, though. I have tried reinstalling the following:
linux
lib32-libglade
lib32-mesa-libgl
libglade
mesa-libgl
qt5-declarative
ttf-liberation
xf86-video-amdgpu
xf86-video-ati
And I have tried adding "radeon" to /etc/modprobe. My xorg.conf have been the same as it's always been, which looks like this:
Section "Device"
Identifier "Radeon"
Driver "radeon"
Option "AccelMethod" "glamor"
Option "DRI" "3"
Option "TearFree" "on"
EndSection
Any ideas? I am not using any kernel headers, and I'm not using any git drivers either, if any of that matters.
Last edited by schmidtbag (2016-06-28 20:42:30)
Offline
you did try re-installing lib32-mesa i hope ?
please post the output of LIBGL_DEBUG=verbose glxinfo32 please.
(glxgears is neither a benchmark nor a diagnostic tool)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
Yes, I did reinstall lib32-mesa. Tried it again, just in case.
name of display: :0
libGL: Can't open configuration file /home/pschmidt/.drirc: No such file or directory.
libGL: pci id for fd 4: 1002:67b1, driver radeonsi
libGL: OpenDriver: trying /usr/lib32/xorg/modules/dri/tls/radeonsi_dri.so
libGL: OpenDriver: trying /usr/lib32/xorg/modules/dri/radeonsi_dri.so
libGL: dlopen /usr/lib32/xorg/modules/dri/radeonsi_dri.so failed (libLLVM-3.8.so: cannot open shared object file: No such file or directory)
libGL error: unable to load driver: radeonsi_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: radeonsi
libGL: pci id for fd 4: 1002:67b1, driver radeonsi
libGL: OpenDriver: trying /usr/lib32/xorg/modules/dri/tls/radeonsi_dri.so
libGL: OpenDriver: trying /usr/lib32/xorg/modules/dri/radeonsi_dri.so
libGL: dlopen /usr/lib32/xorg/modules/dri/radeonsi_dri.so failed (libLLVM-3.8.so: cannot open shared object file: No such file or directory)
libGL error: unable to load driver: radeonsi_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: radeonsi
libGL: OpenDriver: trying /usr/lib32/xorg/modules/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib32/xorg/modules/dri/swrast_dri.so
libGL: dlopen /usr/lib32/xorg/modules/dri/swrast_dri.so failed (libLLVM-3.8.so: cannot open shared object file: No such file or directory)
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request: GLXBadContext
Major opcode of failed request: 156 (GLX)
Minor opcode of failed request: 6 (X_GLXIsDirect)
Serial number of failed request: 55
Current serial number in output stream: 54
And yes, I know glxgears isn't a benchmark or diagnostic tool. But when it doesn't work at all, it's a good enough diagnosis that something is seriously not working.
Offline
Mod note: Moving thread to "Multimedia and Games".
Offline
From the output:
libGL: OpenDriver: trying /usr/lib32/xorg/modules/dri/radeonsi_dri.so
libGL: dlopen /usr/lib32/xorg/modules/dri/radeonsi_dri.so failed (libLLVM-3.8.so: cannot open shared object file: No such file or directory)
/usr/lib32/xorg/modules/dri/radeonsi_dri.so make part of lib32-mesa. Have you installed it properly? Have you this file? What's the output of
ldd /usr/lib32/xorg/modules/dri/radeonsi_dri.so
Are you running an uptodate system, have you not performed a partial update?
Last edited by olive (2016-06-27 07:32:12)
Offline
How would I know if it isn't installed properly? Running the ldd command, this is the result:
[pschmidt@Tornado ~]$ ldd /usr/lib32/xorg/modules/dri/radeonsi_dri.so
linux-gate.so.1 (0xf77ce000)
libgcrypt.so.20 => /usr/lib32/libgcrypt.so.20 (0xf6b6b000)
libpthread.so.0 => /usr/lib32/libpthread.so.0 (0xf6b4b000)
libdl.so.2 => /usr/lib32/libdl.so.2 (0xf6b43000)
libexpat.so.1 => /usr/lib32/libexpat.so.1 (0xf6b13000)
libdrm_nouveau.so.2 => /usr/lib32/libdrm_nouveau.so.2 (0xf6b03000)
libdrm_radeon.so.1 => /usr/lib32/libdrm_radeon.so.1 (0xf6af3000)
libdrm_amdgpu.so.1 => /usr/lib32/libdrm_amdgpu.so.1 (0xf6ae3000)
libdrm.so.2 => /usr/lib32/libdrm.so.2 (0xf6acb000)
libelf.so.1 => /usr/lib32/libelf.so.1 (0xf6aab000)
libLLVM-3.8.so => not found
libstdc++.so.6 => /usr/lib32/libstdc++.so.6 (0xf692b000)
libm.so.6 => /usr/lib32/libm.so.6 (0xf68d3000)
libc.so.6 => /usr/lib32/libc.so.6 (0xf671b000)
libgcc_s.so.1 => /usr/lib32/libgcc_s.so.1 (0xf66fb000)
libgpg-error.so.0 => /usr/lib32/libgpg-error.so.0 (0xf66e3000)
/usr/lib/ld-linux.so.2 (0x56564000)
libz.so.1 => /usr/lib32/libz.so.1 (0xf66cb000)
And yes, my system should be fully up-to-date. I always keep track of that before I post a question.
Offline
@schmidtbag,
to check if a package has been installed properly, you can use
pacman -Qk <pkgname>
or
pacman -Qkk <pkgname>
Offline
I see
libLLVM-3.8.so => not found
So the system cannot load the library. /usr/lib32/libLLVM-3.8.so belong to lib32-llvm-libs which is a dependency of of lib32-mesa-libgl. Have you installed it? You need it for 32 bit opengl applications. If you have it, then check your database integrity (pacman -Dk).
Offline
Turns out lib32-llvm-libs was the problem. I had the SVN version installed, which apparently was conflicting with 32-bit mesa.
Thanks for the help everyone.
Offline
Please mark the thread as solved.
Please disregard the above. I am used to seeing [solved] prepended to the thread title
Offline
Pages: 1