Package Base Details: nvidia-full-beta-all

Git Clone URL: (read-only, click to copy)
Keywords: lib32-opencl-driver lib32-vulkan-driver libglvnd nvidia-settings opencl-driver vulkan-driver
Submitter: Det
Maintainer: dbermond
Last Packager: dbermond
Votes: 32
Popularity: 0.000500
First Submitted: 2013-06-27 12:48
Last Updated: 2020-02-03 16:01

Latest Comments

« First ‹ Previous ... 5 6 7 8 9 10 11 12 13 14 15 ... Next › Last »

t-ask commented on 2016-11-28 21:12

I wonder why the WHQL driver 375.20 is in this beta AUR? Isn't 375.10 the current beta driver? Anyways, 375.20 has a serious opengl issue which breaks at least KDE/Qt applications: So be aware when installing 375.20.

Det commented on 2016-11-18 19:06


solazs commented on 2016-11-18 18:35 md5 check fails for me in version 375.20-1

packer outputs:
==> Validating source_x86_64 files with md5sums... ... HIBA
==> HIBA: Egy vagy több fájl nem ment át az eredetiségellenőrzésen! (ERROR: One or more files did not pass authenticity check!)

ahjolinna commented on 2016-11-01 02:08

@Det: I was wondering if you could split/separate the libglvnd? for stuff like this? so it would be easier to test/use the latest libglvnd (patches)...what I understand there will be more stuff coming to glvnd that will cause problems

ahjolinna commented on 2016-10-25 00:09

there is some bug in glvnd that causes some apps to crash, on KDE it has been the lock screen; anyway, apprently this should fix the issue

Det commented on 2016-07-29 14:54

> there is new beta driver v367.36.02 provides beta support for OpenGL 2016 ARB extensions on capable hardware.

"Developer drivers are usually from a side branch of an earlier driverso may not always contain the latest fixes that are included in newer Geforce GameReady drivers. As the mod stated, in most cases you are better off with the latest GameReady driver."


> also arch has done for nvidia-settings pkgs:
> - split package for libxnvctrl
> - patch to distribute and link against dynlib
> (I dont know if there is a need to follow arch 100%)

Sounds a little weird when you say "arch", you probably mean "stock" or "official" (it's the _Arch_ User Repository), but the patch against dynlib is done by building the thing from source (Github). I only use the blob-bundled nvidia-settings for now, so I can't do that, since it doesn't depend on the

I was supposed to migrate to the anyway, but I'm _way_ behind. Like 4 months, really. At least now I finally got my 3k PC, and that damn non-FE GTX 1080.

Det commented on 2016-07-16 04:50


Note, you might not wanna clear your Pacman cache from .27:

Det commented on 2016-05-13 03:07

I'd say it's the non-GLVND, which prevented crashes in some other Steam games (if not Dota 2) during the transition.

Ropid commented on 2016-05-12 21:01

I tried starting Dota 2 today, but it does not work right. After experimenting a bit, I found it does work with the nvidia packages in the normal Arch repo. Can this really be the case? Is there a difference between how things are packaged here in nvidia-full-beta-all compared to nvidia-libgl, nvidia-dkms etc., or did I make a mistake?

The problem I see is this: the whole desktop freezes when Dota 2 tries to show its main menu. I can switch to a different tty, but this takes about ten seconds to complete. When I am in that other tty, things appear to work normal there. There's no lag trying to type something, etc. I can log in fine. Looking at things with htop, I see that there's two Dota 2 threads that each use a CPU core at full load, so the Dota 2 parent process appear to use 200% CPU.

Before I tried switching packages, I first experimented with different settings (threaded optimizations, __GL_YIELD), different kernels (4.5.3, 4.5.4, 4.4.10-lts), made sure to recompile the nvidia-full-beta-all package after installing the different kernels. I've rebooted a half dozen times and the problem with Dota 2 was like described every single time.

I then switched to the 364.19 packages that are in the normal Arch repos, rebooted, and Dota 2 works fine right now (I started and quit it three times and I see no freezing). I feel a bit lazy right now about switching back to nvidia-full-beta-all to test again.

I'm guessing the last time I had started Dota 2 was about three weeks ago. At that time, things worked fine.

ronoverdrive commented on 2016-04-07 23:44


Happens to me too. Editing the PKGBUILD to remove both the supplies and conflicts with libglvnd in the utils section allows me to avoid the conflicts and install it. However Vulkan still isn't working for me unless I install using the NVIDIA installer.