[Slackbuilds-users] Nvidia-legacy304-driver vdpau missing video and opengl/glx as user crash
kingbeowulf at gmail.com
Sun Oct 16 18:54:41 UTC 2016
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:
> 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.
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 181 bytes
Desc: OpenPGP digital signature
More information about the SlackBuilds-users