Package Details: opencl-nvidia-full-beta-all 370.28-1

Git Clone URL: (read-only)
Package Base: nvidia-full-beta-all
Description: NVIDIA's OpenCL implemention for 'nvidia-utils-full-beta-all'
Upstream URL:
Licenses: custom:NVIDIA
Conflicts: opencl-nvidia
Provides: opencl-nvidia
Submitter: Det
Maintainer: Det
Last Packager: Det
Votes: 18
Popularity: 0.054852
First Submitted: 2013-06-27 12:48
Last Updated: 2016-09-09 11:15

Required by (21)

Sources (4)

Latest Comments

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.

Commander commented on 2016-04-07 17:29

Am I the only one getting;
:: lib32-nvidia-libgl-full-beta-all and lib32-nvidia-utils-full-beta-all are in conflict?

(( Removed all nvidia related ))

Quite amusing that drunken du5tball found it while tired me could not but to be short;
package_nvidia-libgl-full-beta-all() conflicts with libglvnd while
package_nvidia-utils-full-beta-all() provides libglvnd

nvidia-libgl-full-beta-all and nvidia-utils-full-beta-all are in conflict and so are their lib32 counterparts

Best Regards, I'm off to bed.

Det commented on 2016-04-06 20:17

Well, yes, duh.

Commander commented on 2016-04-06 20:17


I thought it wasnt _that_ tied to the GLVND, then maybe just add conflicts('libglvnd' 'lib32-libglvnd') so that users that move from pacman repos don't get errors during installation of this driver?

Det commented on 2016-04-06 16:31

I don't get why people are asking that. That GLVND is synced with the repo driver, which most of the time does not correlate to the bleeding edge one I'm providing here, right?

Commander commented on 2016-03-28 01:22

Not sure how this should be but it conflicts atm with libglvnd and lib32-glvnd for obvious reasons.

Should probably remove glvnd from the pkg and just add that as dependency?

All comments