With the recently released legacy driver package 304.132, glxinfo reports the following error now:
$ glxinfo
name of display: :0
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: 24 (X_GLXCreateNewContext)
Value in failed request: 0x0
Serial number of failed request: 87
Current serial number in output stream: 88
nvidia-settings crashes when I try to open OpenGL settings, probably for the same reason.
Hardware: GeForce 7300LE
OS: ROSA Linux R8 x86_64
Kernel: I tried both 4.1.33 and 4.7.5 - the error is the same.
X11 server: 1.17.4.
If I remove version 304.132 and install 304.131 back (kernel 4.1.33), glxinfo and other GL apps are working fine on that system. So it looks like a regression.
I’m the same trouble using fedora24.
$ lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation G71 [GeForce 7900 GS] (rev a1)
$ glxinfo
name of display: :0
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: 24 (X_GLXCreateNewContext)
Value in failed request: 0x0
Serial number of failed request: 87
Current serial number in output stream: 88
Isn’t not the way to return it to 304.131, but 304.132 reconsidered?
Well, for now, I am going to try the previous version, 304.131, with both mtrr-related patches and other patches to support kernel 4.6+. Let us see if it still works…
Well, I maintain the packages with Nvidia drivers in ROSA Linux and some of our users still need version 304.x working for different kernels. That is why I am going to experiment with 304.131 more.
That being said, I would also prefer to have 304.132 fixed, of course. However, it seems, the cause of the problem is somewhere in the binary-only part of the X11 driver, difficult to analyze without the sources.
Hi,
When 304.132 isn’t corrected, we’re in trouble, too, but it’s a ubuntu(Unity) distribution that that would be a problem more.
I make a mistake in the corrected order of priority.
304.132 is raised by nvidia ubuntu ppa already.
$ glxinfo
name of display: :0
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: 24 (X_GLXCreateNewContext)
Value in failed request: 0x0
Serial number of failed request: 87
Current serial number in output stream: 88
Please advice me how to diagnose this problem.
or I would like to ask for your assistance in suggesting any possible solution.
Any suggestion will be appreciated.
Is there a permission issue going on somewhere, a conflict with another driver module or something else preventing nvidia driver from creating a new opengl context as a normal user? (i also created a new non-root user and i get the same issue)
Hello,Thanks a lot for the information!
I tested by the root user, too in fedora environment. OpenGL function worked as design.oh my god!!
I think there is a problem about a right of your comment street normal user permission.And a driver’s permission isn’t answering to a right.
nice information!.
Best Regards!
Yea, 304.132 has issues, 304.131 doesn’t. I’ve confirmed this by downgrading to 304.131 on ubuntu 16.04 using the following command and everyhing is fine now:
sudo apt install nvidia-304=304.131-0ubuntu3
I’m going to stay on 304.131 since it works perfectly. The upgrade to 304.132 broke everything. I mean, the bug prevented me from being able to log into unity and prevented plasmashell from loading any menus in kde. on top of that, the crash reporting utility was unable to record a backtrace and thus was not successfully reported through the standard bug tracking system. I bet millions of people are affected by this on ubuntu distros and the devs are unaware because of this fluke in the reporting system.
Unfortunately, downgrading to nvidia-304=304.131-0ubuntu3 does not work for me; I get corrupted graphics upon reaching the desktop in Ubuntu 16.04. Functionality is restored only by purging nvidia* and using the open source driver, but performance is poor as one might assume.