[Slackbuilds-users] Nvidia-legacy304-driver vdpau missing video and opengl/glx as user crash

Willy Sudiarto Raharjo willysr at slackbuilds.org
Sun Oct 16 04:14:44 UTC 2016

> willy flagged an issue on the new nvidia-304.132 drivers.  I decided to
> build a box with an older card (GTX6800) to test on bare metal before I
> update (only so much one can do in qemu).  After fixing a few items, I
> have these issues. The "root" issue nags my memory but I can't seem to
> recall why.
> Clean Slackware64-14.2 updated install, no other files.  AMD Athlon X2 3200+
> 1. logged in as regular user
> glxgears and nvidia-settings crashes:
> ----------------
> $ glxgears
> 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:  30
>   Current serial number in output stream:  31
> When accessing nvidia-settings OpenGL/GLX information:
> $ nvidia-settings
> The program 'nvidia-settings' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadValue (integer parameter out of range for operation)'.
>   (Details: serial 584 error_code 2 request_code 154 minor_code 3)
>   (Note to programmers: normally, X errors are reported asynchronously;
>    that is, you will receive the error a while after causing it.
>    To debug your program, run it with the --sync command line
>    option to change this behavior. You can then get a meaningful
>    backtrace from your debugger if you break on the gdk_x_error() function.)
> ----------------
> mplayer will play via -vo xv but no other driver (Big Buck Bunny
> 1920x1080 30fps).
> 2. logged in as root
> everything works except mplayer -vo {vdpau | xvidix}.  Nvidia-settings
> and glxgears work as expected.
> So there is a vdpau issue, but nothing in logs re: user vs. root running
> GLX.  as far as I know, 'ldd' reports ok.
> Any assistance appreciated.  Files for testing are on
> http:/www.koenigcomputers.com/ (follow biblio links...)
> -Ed

Hi Ed,

thanks for the confirmation of the bug in 304.132 driver
it seems that other users in other distribution are also having this problem



however one person posted an image about a working 304.142 in Fedora 24
with Linux Kernel 4.7

here's what listed as the release highlight of 304.132

Added /var/log/dmesg to the list of paths which are searched by
nvidia-bug-report.sh for kernel messages.
Fixed a bug that caused kernel panics when using the NVIDIA driver on
v4.5 and newer Linux kernels built with CONFIG_DEBUG_VM_PGFLAGS.
Updated nvidia-installer to support ncurses version 6.x.

I'm suspecting that it *might* require newer kernel so for now, i will
stick to the 304.131 which still works fine as it is.


Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20161016/ba14dffd/attachment.asc>

More information about the SlackBuilds-users mailing list