Ever since I upgraded to CentOS 6.8, some software has stopped working alogether. This is related to OpenGL/mesa and can be demonstrated with glxgears:
$ glxgears libGL error: No matching fbConfigs or visuals found 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: 154 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 33 Current serial number in output stream: 35 $
This appears to be a common problem, but I found no solutions that apply here since I believe everything is installed and set up correctly. It all worked with CentOS 6.x, x<8.
https://www.centos.org/forums/viewtopic.php?t=56273 https://ask.fedoraproject.org/en/question/38116/issues-with-libgl-on-fedora-...
On 05/31/2016 06:09 AM, isdtor wrote:
Ever since I upgraded to CentOS 6.8, some software has stopped working alogether. This is related to OpenGL/mesa and can be demonstrated with glxgears:
$ glxgears libGL error: No matching fbConfigs or visuals found 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: 154 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 33 Current serial number in output stream: 35 $
This appears to be a common problem, but I found no solutions that apply here since I believe everything is installed and set up correctly. It all worked with CentOS 6.x, x<8.
https://www.centos.org/forums/viewtopic.php?t=56273 https://ask.fedoraproject.org/en/question/38116/issues-with-libgl-on-fedora-...
I am looking at this issue right now.. more to follow
On 05/31/2016 08:15 AM, Johnny Hughes wrote:
On 05/31/2016 06:09 AM, isdtor wrote:
Ever since I upgraded to CentOS 6.8, some software has stopped working alogether. This is related to OpenGL/mesa and can be demonstrated with glxgears:
$ glxgears libGL error: No matching fbConfigs or visuals found 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: 154 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 33 Current serial number in output stream: 35 $
This appears to be a common problem, but I found no solutions that apply here since I believe everything is installed and set up correctly. It all worked with CentOS 6.x, x<8.
https://www.centos.org/forums/viewtopic.php?t=56273 https://ask.fedoraproject.org/en/question/38116/issues-with-libgl-on-fedora-...
I am looking at this issue right now.. more to follow
[johnny@localhost ~]$ glxgears 1054 frames in 5.0 seconds = 210.750 FPS 1064 frames in 5.0 seconds = 212.735 FPS 1077 frames in 5.0 seconds = 215.366 FPS 1061 frames in 5.0 seconds = 212.018 FPS
[johnny@localhost ~]$ rpm -qa | egrep -i 'glx|mesa' | sort glx-utils-11.0.7-4.el6.x86_64 mesa-dri1-drivers-7.11-8.el6.x86_64 mesa-dri-drivers-11.0.7-4.el6.x86_64 mesa-dri-filesystem-11.0.7-4.el6.x86_64 mesa-libEGL-11.0.7-4.el6.x86_64 mesa-libgbm-11.0.7-4.el6.x86_64 mesa-libGL-11.0.7-4.el6.x86_64 mesa-libGLU-11.0.7-4.el6.x86_64 mesa-libxatracker-11.0.7-4.el6.x86_64 mesa-private-llvm-3.6.2-1.el6.x86_64
[johnny@localhost ~]$ cat /etc/redhat-release CentOS release 6.8 (Final)
========================
I have no issues .. no 3rd party repos on this server.
Can you provide more details .. did you upgrade all the 6.8 RPMS and not just cheery pick updates .. do you have 3rd party repos installed?
Is this i386 or x86_64 CentOS-6.8?
Thanks, Johnny Hughes
(Btw., Johnny, your signatures haven't verified in months. Don't know if the list server is the problem or our corp mail server).
[johnny@localhost ~]$ glxgears 1054 frames in 5.0 seconds = 210.750 FPS 1064 frames in 5.0 seconds = 212.735 FPS 1077 frames in 5.0 seconds = 215.366 FPS 1061 frames in 5.0 seconds = 212.018 FPS
$ glxgears libGL error: No matching fbConfigs or visuals found 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: 154 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 33 Current serial number in output stream: 35 $
Curiously, it works as root. I checked all files owned by mesa* and couldn't find anything wrong with permissions. Ah, I think I found it): library search path is different for root. That is an artifact of our work environment.
$ ldd `which glxinfo` |grep nvidia $
# ldd `which glxinfo` |grep nvidia libGL.so.1 => /usr/lib64/nvidia/libGL.so.1 (0x00007f6de0558000) libnvidia-tls.so.346.35 => /usr/lib64/nvidia/tls/libnvidia-tls.so.346.35 (0x00007f6de0352000) libnvidia-glcore.so.346.35 => /usr/lib64/nvidia/libnvidia-glcore.so.346.35 (0x00007f6ddd67a000) #
Yet, it is strange that it all worked under 6.7 and before.
On Tue, May 31, 2016 at 03:04:56PM +0100, isdtor wrote:
# ldd `which glxinfo` |grep nvidia libGL.so.1 => /usr/lib64/nvidia/libGL.so.1 (0x00007f6de0558000) libnvidia-tls.so.346.35 => /usr/lib64/nvidia/tls/libnvidia-tls.so.346.35 (0x00007f6de0352000) libnvidia-glcore.so.346.35 => /usr/lib64/nvidia/libnvidia-glcore.so.346.35 (0x00007f6ddd67a000) #
Yet, it is strange that it all worked under 6.7 and before.
You've got the 3rd-party nvidia packages installed. Do you know which repo you got them from?
"rpm -qif /usr/lib64/nvidia/libGL.so.1" should tell you which package it is and the Packager.
On Tue, 2016-05-31 at 15:04 +0100, isdtor wrote:
(Btw., Johnny, your signatures haven't verified in months. Don't know if the list server is the problem or our corp mail server).
On mine I get "Signature exists, but need public key"
On 05/31/2016 12:44 PM, Always Learning wrote:
On Tue, 2016-05-31 at 15:04 +0100, isdtor wrote:
(Btw., Johnny, your signatures haven't verified in months. Don't know if the list server is the problem or our corp mail server).
On mine I get "Signature exists, but need public key"
For anyone who cares:
https://pgp.mit.edu/pks/lookup?op=get&search=0x4CA90C826AC163B3
(my public key)
Also, you can just search the public mit server for johnny@centos.org and find it.
Thanks, Johnny Hughes
On Tue, 2016-05-31 at 14:41 -0500, Johnny Hughes wrote:
https://pgp.mit.edu/pks/lookup?op=get&search=0x4CA90C826AC163B3
(my public key)
Thanks.
Curiously my intel 845-G has had gl applications (freecad and wine based windows games) STARTED working correctly with this update.
I see in a latter email that you have a) found a path issue for users vs root, and b) you are using nvidia. This reminded me of an issue I was having with some GL code I use (jogamp based) and nvidia drivers a little over a month ago, this might be something else you want to be aware of.
Nvidia is in the process of making a Vendor-Neutral GL[0], which I think is probably a good thing, but they have found that "several applications relied on behaviors or attributes of the NVIDIA OpenGL driver that fall outside of the Linux OpenGL ABI"[1]. Once I figured out it was kmod-nvidia related, this[2] post helped me figure out the mapping to the other links. for now I have had to stick our nvidia machines at 352.79 until either we get our app working with the GLVND API, or elrepo packages a non-GLVND config[1].
[0] https://github.com/NVIDIA/libglvnd [1] https://devtalk.nvidia.com/default/topic/915640/unix-graphics-announcements-...
[2] https://www.centos.org/forums/viewtopic.php?f=14&t=57047
Even when this disclaimer is not here: I am not a contracting officer. I do not have authority to make or modify the terms of any contract.
________________________________________ From: isdtor [isdtor@gmail.com] Sent: Tuesday, May 31, 2016 7:09 AM To: CentOS mailing list Subject: [CentOS] CenOS 6.8 and libGL failures
Ever since I upgraded to CentOS 6.8, some software has stopped working alogether. This is related to OpenGL/mesa and can be demonstrated with glxgears:
$ glxgears libGL error: No matching fbConfigs or visuals found 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: 154 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 33 Current serial number in output stream: 35 $
This appears to be a common problem, but I found no solutions that apply here since I believe everything is installed and set up correctly. It all worked with CentOS 6.x, x<8.
https://www.centos.org/forums/viewtopic.php?t=56273 https://ask.fedoraproject.org/en/question/38116/issues-with-libgl-on-fedora-...
On 05/31/2016 09:17 AM, Denniston, Todd A CIV NAVSURFWARCENDIV Crane wrote:
Curiously my intel 845-G has had gl applications (freecad and wine based windows games) STARTED working correctly with this update.
I see in a latter email that you have a) found a path issue for users vs root, and b) you are using nvidia. This reminded me of an issue I was having with some GL code I use (jogamp based) and nvidia drivers a little over a month ago, this might be something else you want to be aware of.
Nvidia is in the process of making a Vendor-Neutral GL[0], which I think is probably a good thing, but they have found that "several applications relied on behaviors or attributes of the NVIDIA OpenGL driver that fall outside of the Linux OpenGL ABI"[1]. Once I figured out it was kmod-nvidia related, this[2] post helped me figure out the mapping to the other links. for now I have had to stick our nvidia machines at 352.79 until either we get our app working with the GLVND API, or elrepo packages a non-GLVND config[1].
[0] https://github.com/NVIDIA/libglvnd [1] https://devtalk.nvidia.com/default/topic/915640/unix-graphics-announcements-...
[2] https://www.centos.org/forums/viewtopic.php?f=14&t=57047
Even when this disclaimer is not here: I am not a contracting officer. I do not have authority to make or modify the terms of any contract.
________________________________________ From: isdtor [isdtor@gmail.com] Sent: Tuesday, May 31, 2016 7:09 AM To: CentOS mailing list Subject: [CentOS] CenOS 6.8 and libGL failures
Ever since I upgraded to CentOS 6.8, some software has stopped working alogether. This is related to OpenGL/mesa and can be demonstrated with glxgears:
$ glxgears libGL error: No matching fbConfigs or visuals found 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: 154 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 33 Current serial number in output stream: 35 $
This appears to be a common problem, but I found no solutions that apply here since I believe everything is installed and set up correctly. It all worked with CentOS 6.x, x<8.
https://www.centos.org/forums/viewtopic.php?t=56273 https://ask.fedoraproject.org/en/question/38116/issues-with-libgl-on-fedora-...
There is yet another issue with nvidia drivers and indirect GLX, which will generate almost the same error message. Indirect GLX was disabled by default in Xorg 1.17, which was introduced in Centos 7.2 and 6.8.
This problem only happens if you run the GL application remotely and display on nvidia driver enabled screen. It's not clear from the OP if that is the case here.
The solution would be to add +iglx to Xorg command line, but gdm is hardcoding the Xorg parameters, so if you use gdm/gnome you are out of luck.
https://elrepo.org/bugs/bug_view_advanced_page.php?bug_id=610 https://bugzilla.redhat.com/show_bug.cgi?id=1336014
-Thomas
On Tue, 31 May 2016, Thomas Eriksson wrote:
The solution would be to add +iglx to Xorg command line, but gdm is hardcoding the Xorg parameters, so if you use gdm/gnome you are out of luck.
https://elrepo.org/bugs/bug_view_advanced_page.php?bug_id=610 https://bugzilla.redhat.com/show_bug.cgi?id=1336014
Not out of luck, but certainly in a bit of a pickle. Xorg wrapper script as suggested in the second link certainly works.
I'm assuming given the tickets lurking that they're planning on reverting the default behaviour in future versions, which would certainly be welcomed here.
jh