Re: [Slackbuilds-users] Nvidia-legacy304-driver vdpau missing video and opengl/glx as user crash
On 10/15/2016 09:14 PM, Willy Sudiarto Raharjo wrote: >> 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: >> --snip-- > > 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 > > https://devtalk.nvidia.com/default/topic/968892/geforce-7300le-with-304-132-glxinfo-fails-now-with-quot-x-error-of-failed-request-badvalue-quot-/ > > https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=nvidia-legacy-304xx-driver;dist=unstable > > however one person posted an image about a working 304.142 in Fedora 24 > with Linux Kernel 4.7 > http://media.if-not-true-then-false.com/2015/08/nvidia-304.132-on-fedora-24-lxde.png > > 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. > > Thanks > > Thanks for the links. I overlooked the Nvidia devtalk for some reason. Looks like SBo will have to stick with 304.131 for now. The are 2 minor bugs in the slackbuild and nvdia-switch that I will correct an post today. As for the image of 304.132 on Fedora: Bah. I was able to get that far. The desktop runs fine (2D), but try any 3D opengl/glx function, or even just clicking on OpenGL/GLX Information, and the bug occurs. -Ed signature.asc Description: OpenPGP digital signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Nvidia-legacy304-driver vdpau missing video and opengl/glx as user crash
> 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
https://devtalk.nvidia.com/default/topic/968892/geforce-7300le-with-304-132-glxinfo-fails-now-with-quot-x-error-of-failed-request-badvalue-quot-/
https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=nvidia-legacy-304xx-driver;dist=unstable
however one person posted an image about a working 304.142 in Fedora 24
with Linux Kernel 4.7
http://media.if-not-true-then-false.com/2015/08/nvidia-304.132-on-fedora-24-lxde.png
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.
Thanks
--
Willy Sudiarto Raharjo
signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] Nvidia-legacy304-driver vdpau missing video and opengl/glx as user crash
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
signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
