Package Details: nvidia-vulkan 515.49.05-1

Git Clone URL: (read-only, click to copy)
Package Base: nvidia-vulkan
Description: NVIDIA drivers for linux (vulkan developer branch)
Upstream URL:
Licenses: custom
Conflicts: nvidia
Provides: nvidia, NVIDIA-MODULE
Submitter: jcstryker
Maintainer: jcstryker
Last Packager: jcstryker
Votes: 29
Popularity: 0.076312
First Submitted: 2018-06-23 01:17 (UTC)
Last Updated: 2022-06-19 20:51 (UTC)

Required by (41)

Sources (4)

Latest Comments

MarsSeed commented on 2022-05-16 15:06 (UTC)

Thanks for the update and the NVIDIA-MODULE provides!

MarsSeed commented on 2022-03-23 16:55 (UTC)

Please kindly add the following to nvidia-vulkan and nvidia-vulkan-dkms, thanks in advance!


jcstryker commented on 2022-03-02 20:26 (UTC)


Just because Vulkan 1.3 development might be complete doesn't mean this branch of the driver is not in use.

This page still exists, and there is no indication the program has ended.

As such, I have removed your out of date flag on this package.

6543 commented on 2022-02-15 16:14 (UTC) (edited on 2022-02-19 18:03 (UTC) by 6543)

[SOLVED] I can not build it anymore :/

kernel: 5.16.8-artix1-2
gcc version: 11.2.0


cc1: error: incompatible gcc/plugin versions
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/

a official rebuild fixed it (kernek: 5.16.10-artix1-1)

ventureo commented on 2022-01-02 11:40 (UTC)

Can you add udev rules and nvidia-uvm loading fixes?

tycho commented on 2021-10-19 10:42 (UTC)

It looks like 470.62.05 broke prime graphics offload. If you compare the output of something like "prime-run vulkaninfo" between 470.62.02 and 470.62.05 on a system with integrated AMD and discrete NVIDIA graphics, you'll find that in the newer driver the NVIDIA GPU is enumerated as the second GPU, so no Vulkan apps will use it. I have not found a workaround for this issue.

Rodancoci commented on 2021-05-08 08:40 (UTC)

5.12 patch works great! Thank you!

hicklemon commented on 2021-05-07 12:12 (UTC)

It looks like drm_gem_dumb_destroy might have been renamed to drm_mode_destroy

Build fail on 5.12.1-arch1-1

Rodancoci commented on 2021-05-07 01:50 (UTC)

Hi, it seems this package is not working with kernel 5.12. Maybe a patch is needed?

damachine commented on 2021-02-17 03:07 (UTC)

hello build with new 5.11 Kernel fails because "modules not found" mkinitcpio.

Estebanium commented on 2020-08-18 20:04 (UTC) (edited on 2020-08-18 20:04 (UTC) by Estebanium)

@mr4ffe: You need to issue two commands:

sudo ln -s /usr/lib/modules/X.X.XX-X-MANJARO/build/ /usr/src/linux
sudo echo $(uname -r) | sudo tee /usr/src/linux/version

Have a look at your modules folder to get the right versioning. This workaround is also described one page before here. Tested on Manjaro

mr4ffe commented on 2020-08-17 14:14 (UTC) (edited on 2020-08-17 14:24 (UTC) by mr4ffe)

When installing I get:

==> Starting build()...
make[1]: *** /usr/src/linux: No such file or directory.  Stop.
make: *** [Makefile:81: modules] Error 2
==> ERROR: A failure occurred in build().

and this command:

sudo echo $(uname -r) | sudo tee /usr/src/linux/version


tee: /usr/src/linux/version: No such file or directory

Only solution I could find searching around the web was a this comment on Reddit but it's for Gentoo and not Manjaro. :(

sburt commented on 2020-06-25 20:57 (UTC)

I'm trying to compile this with Manjaro but I'm getting Errors.

make[1]: *** [Makefile:1530: _module_/home/sburt/.cache/yay/nvidia-vulkan/src/NVIDIA-Linux-x86_64-440.66.17/kernel] Error 2
make[1]: Leaving directory '/usr/lib/modules/4.19.129-1-surface-lts/build'
make: *** [Makefile:81: modules] Error 2
==> ERROR: A failure occurred in build().
Error making: nvidia-vulkan (nvidia-vulkan-utils nvidia-vulkan-dkms)

Any suggestions on modifications I should be making?

Leeo97one commented on 2020-06-20 00:28 (UTC)

The .SRCINFO is not up to date.

Grimish commented on 2020-06-13 00:10 (UTC) (edited on 2020-06-14 15:15 (UTC) by Grimish)

Functioned until today on 5.7.2-2.

Getting ‘set_memory_array_uc’. Appears to very much be the kernel.

EDIT & Clipped!

Had more time to review posts and after reading mistertux post it works as stated. To simplify, Add the patch to the PKGBUILD. There is already a 5.6 patch so follow that and its simple to do. Here is a summary: Add 3 lines to the PKGBUILD file.

Under 'Source' ADD: 'kernel-5.7.patch::'

Under 'sha512sum' ADD:'a010fc217ace313350aca05e3225c328ca98d5ce636d3742fc7a9e353e9af8d9cdd5424bee6dadbe57c8c0cb58f1f204129bf8ac25848256053cae31c286b8cd'

Under 'prepare' ADD: patch -p1 -i '../kernel-5.7.patch'

Compiled packages and packages installed fine! Thanks all

mistertux commented on 2020-06-08 21:55 (UTC)

This can be installed on the 5.7 kernels with the patch on gitlab, Download the snapshot, add the kernel-5.7.patch, and update the PKGBUILD, build and reinstall. This worked just fine for me. Thanks for supplying everyone with this package. The patch can be found here and also Cheers

rtentser commented on 2020-06-05 11:48 (UTC) (edited on 2020-06-05 11:49 (UTC) by rtentser)

Can't build after upgrading to some testing packages. Probably, kernel's fault (5.7).

Why does the nvidia-vulkan-dkms package conflict with nvidia and not with nvidia-dkms?

Yes, why? nvidia-dkms blocks the installation.

Leeo97one commented on 2020-04-26 13:23 (UTC) (edited on 2020-04-26 13:24 (UTC) by Leeo97one)

Why does the nvidia-vulkan-dkms package conflict with nvidia and not with nvidia-dkms?

caffe1neadd1ct commented on 2020-04-25 18:50 (UTC)

Freezing while using PRIME Sync and vsync enabled caused by alt-tabbing out of a window has now been fixed:

SolarAquarion commented on 2020-04-06 13:08 (UTC) i decided to make a package that just compiles the kernel stuff for each kernel on the system, no DKMS. Also kernel 5.6 patch

bsleet commented on 2020-04-06 11:28 (UTC) (edited on 2020-04-06 11:29 (UTC) by bsleet)

I'm also having same issue as damachine's. I guess kernel 5.6 patch isn't included in this package.

damachine commented on 2020-04-05 11:56 (UTC)

install fails on kernel 5.6.2!!

meister1593 commented on 2020-04-02 19:01 (UTC)

Doom eternal is running very poorly without new driver update. Please update)

mozo commented on 2020-04-01 18:49 (UTC)

There's a new version 440.66.07 with Doom Eternal fix! Please update :)

mozo commented on 2020-03-29 07:46 (UTC)

@SolarAquarion, it would be great!

SolarAquarion commented on 2020-03-29 04:11 (UTC)

could you add something like what tk-glitch does with nvidia-all, aka, building for all kernels on the system

RTheren commented on 2020-03-23 16:40 (UTC) (edited on 2020-03-23 16:41 (UTC) by RTheren)

For the unfortunate Manjaro souls, here's how to fix the "/usr/src/linux: No such file or directory"

sudo ln -s /usr/lib/modules/5.4.24-1-MANJARO/build/ /usr/src/linux
sudo echo $(uname -r) | sudo tee /usr/src/linux/version

This will allow you to build the package.

mozo commented on 2020-03-21 15:05 (UTC)

Thank you!

mozo commented on 2020-03-20 11:26 (UTC)

Please, update it in order to run DOOM Eternal!

irb commented on 2020-03-19 20:38 (UTC)

@errcsool Do you have the linux-headers package installed?

errcsool commented on 2020-01-24 22:50 (UTC)

Getting build error on Surface Book 2, kernel version 5.3.15-1:

make[1]: *** /usr/src/linux: No such file or directory. Stop.

How do I fix or debug this?

alexluberg commented on 2019-12-03 18:59 (UTC)

@jcstryker I tried to reproduce the build failure and figured that although the file exists, it didn't match any lines inside which broke the check. Then fixed the regex.

damachine commented on 2019-11-29 15:59 (UTC)

hi. prime syncronisations breaks with 5.4 kernel. any one too?

jcstryker commented on 2019-11-29 15:11 (UTC)


Looks like that did it, thank you for the fix. By the way, how did you discover that $TAB was the issue? I wouldn't have thought of that.

alexluberg commented on 2019-11-28 18:45 (UTC) (edited on 2019-11-28 18:47 (UTC) by alexluberg)

I don't know how to propose a fix correctly here, but the root cause of the build failure on 5.4 kernels is incorrect regex pattern.

Adding these 2 sed modifications fixes the build

After bsdtar -xf nvidia-persistenced-init.tar.bz2:

# Fixing regex pattern for Module.symvers
sed -i "s/${TAB}vmlinux/${TAB}*vmlinux/g" kernel/
sed -i "s/TAB='    '/TAB='\\\t'/g" kernel/

damachine commented on 2019-11-26 01:05 (UTC)

modules for 5.4 kernel cant build. thanks

Plexcon commented on 2019-10-14 23:45 (UTC)

==> Starting build () ... cat:/ usr/lib/modules/extramodules-ARCH/version: File or directory does not exist ==> ERROR: There was a failure in build ().      Canceling ...

damentz commented on 2019-10-14 23:37 (UTC)

Same, getting:

==> Starting build()...
cat: /usr/lib/modules/extramodules-ARCH/version: No such file or directory
==> ERROR: A failure occurred in build().

And the code that causes this is:

build() {
    _kernver="$(cat /usr/lib/modules/${_extramodules}/version)"
    cd "${_pkg}"/kernel
    make SYSSRC=/usr/lib/modules/"${_kernver}/build" module

Looking at where ${_extramodules} comes from, and it's hardcoded here:

Anyone know what causes ${_extramodules} to (not) update to the running kernel?

damachine commented on 2019-10-14 20:09 (UTC)

hallo update failed with: cat: /usr/lib/modules/extramodules-ARCH/version: No such file or directory

commented on 2019-06-24 10:56 (UTC)

Fails to load with 5.1.14-arch1-1-ARCH

veridiam commented on 2019-05-25 06:50 (UTC)

For some reason this package causes vulkan-intel icd to never be automatically selected.

jcstryker commented on 2019-05-23 00:20 (UTC)

Posted new version, with patch for building with 5.1+ kernel (thanks tk glitch). Please report any issues.

cj360 commented on 2019-05-16 22:51 (UTC)

Also tried to update to 5.1.x kernel, had to downgrade to re-enable nvidia driver.

damachine commented on 2019-05-15 12:16 (UTC)

not compatible with 5.1.x kernel. install or update fails

loganj commented on 2019-04-20 06:13 (UTC) (edited on 2019-04-20 12:07 (UTC) by loganj)

I'm new to arch so i might be wrong but is there a lib32 vulkan? i couldn't find any libvulkan in lib32

edit: guess i was wrong. i had to install manually lib32-vulkan-icd-loader. although i've never installed vulkan-icd-loader either. oh well d9vk seems to work now

theriddick commented on 2019-01-13 22:27 (UTC)

I dunno why but my Antergos ARCH system can't see 415.22.05-1, it seems to think this is 415.22.01-1 still, kinda confused how that happens!

jcstryker commented on 2018-12-03 20:45 (UTC)

Driver was updated to version 415.18.04, which should fix the "GetThreadContext failed" error with Unity games. Please report any crashes or performance issues.

Nocifer commented on 2018-11-29 13:56 (UTC) (edited on 2018-11-29 13:58 (UTC) by Nocifer)

A friendly heads-up: after upgrading and rebooting my system, I experienced severe CPU usage resulting in the mouse stuttering, windows hanging, fonts rendering incorrectly or missing completely, etc. The computer was nigh unusable so I didn't even bother to try and debug the situation, I simply degraded via tty2 and that was that.

I don't know if this is the result of the beta nature of the driver itself, or an incompatibility with KDE (SDDM was eating most of that excessive CPU) or even an incompatibility of the new driver with my really old GPU (Nvidia 6xx series) or whatever else. What I do know though, is that the non-beta 415.18 driver works flawlessly, and so does the old 396.54.09.

So, along with the "GetThreadContext failed" thing, this seems like one more good reason to wait before upgrading to the new version.

jcstryker commented on 2018-11-28 22:58 (UTC) (edited on 2018-11-28 22:59 (UTC) by jcstryker)

PSA: Unity Games under DXVK using driver 415.18.02 are reportedly crashing with the error message "GetThreadContext failed". If this is an issue for you, I recommend staying on the old version until a patch is released. You can access the previous version using the following commands:

git clone
cd ./nvidia-vulkan
git reset ac92350fd8540d75a6d6a49373529a31ffcfd77f --hard

jcstryker commented on 2018-11-28 22:35 (UTC)

@everyone The driver is updated to the new branch. This includes a lot of PKGBUILD changes, please report any issues or missing features.

@ChrizVR You need to install either the regular or dkms version, not both. Try using an AUR helper like 'yay' or use makepkg without the -i flag.

Scindix commented on 2018-11-28 15:49 (UTC)

@ChrizVR Could you post the output of "pacman -Qsq nvidia"?

ChrizVR commented on 2018-11-26 16:05 (UTC)

i get the following error:

looking for conflicting packages... error: unresolvable package conflicts detected error: failed to prepare transaction (conflicting dependencies) :: nvidia-vulkan and nvidia-vulkan-dkms are in conflict ==> WARNING: Failed to install built package(s).

anyone know why?

jfernandz commented on 2018-11-15 12:17 (UTC) (edited on 2018-11-26 13:10 (UTC) by jfernandz)

Yes, right now is fixed and working pretty fine. Thank you @jcstryker

Sorry, @Nocifer, I was confusing with the real maintainer, hehe.

mozo commented on 2018-11-15 08:16 (UTC)

Work like a charm. Thank you :)

jcstryker commented on 2018-11-14 21:40 (UTC)

@Nocifer Thanks for your help! I am going to include Tk-Glitch's patch for kernel 4.19 [0]. His patch is very similar to the two that you provided. Hopefully we get a new vulkan release based on the 410 branch soon.

@wyre Please try the new version. I am running the DKMS version without trouble so far, let me know if you run into issues.


jetba commented on 2018-11-14 17:02 (UTC)

@Nocifer Thank you for the patches. I also had success with them on 4.19 kernel, and so far everything is working perfectly.

Nocifer commented on 2018-11-14 15:25 (UTC)

@wyre what do you mean? Of course I applied the patches, that's how I managed to build the package, I just didn't provide the modified PKGBUILD and the two patch files because I wanted to wait for a response from @jcstryker first.

Also, what kind of error does your pacman return? In my case everything built smoothly and all the modules installed correctly, in fact right now I'm booted in a 4.19 system with the nvidia-vulkan modules active. The only problem is that these API changes aren't compatible with the LTS kernel (which I keep installed as a backup), but that's a minor thing. Could it be that you also have the LTS kernel installed, and these errors are produced by it?

jfernandz commented on 2018-11-14 14:04 (UTC) (edited on 2018-11-14 14:35 (UTC) by jfernandz)

lib32-opencl-nvidia-vulkan and lib32-opencl-nvidia-390xx should are in conflict. They are not.

And ... despite of your driver can be compiled and built with those patches ... pacman returns a fail when dkms try to install the module in 4.19 kernel, after the package have been installed. So ... sure, we must wait until nvidia decides merge this features in the main branch.

jfernandz commented on 2018-11-14 13:33 (UTC)

@Nocifer why did you not modify the PKGBUILD to apply this patchs in prepare()?

Nocifer commented on 2018-11-14 12:23 (UTC) (edited on 2018-11-14 12:32 (UTC) by Nocifer)

Alright, I looked it up a bit more and it seems it is indeed a change in the API. Also, apparently the 396.54.09 branch will no longer be supported by Nvidia for kernel 4.19 and above, which presumably means they aim to merge it with the main 410 branch at some point in the near future. When exactly, I obviously couldn't say.

In the meantime, the package can be built with just a couple of minor changes.

Nocifer commented on 2018-11-13 21:38 (UTC) (edited on 2018-11-13 21:40 (UTC) by Nocifer)

Getting the following build error with kernel 4.19:

 ../src/NVIDIA-Linux-x86_64-396.54.09/kernel/nvidia-drm/nvidia-drm-encoder.c:219:11: error: implicit declaration of function ‘drm_mode_connector_attach_encoder’; did you mean ‘drm_connector_attach_encoder’? [-Werror=implicit-function-declaration]
 ret = drm_mode_connector_attach_encoder(connector, encoder);

Changing it as suggested produces further, similar errors:


Could this indicate a recent change in the KMS API..?

Also, some quick googling got me this:

mozo commented on 2018-11-13 19:06 (UTC)

Hello, please update it to linux-headers<4.19.1. Thank you.

Kuchiriel commented on 2018-10-31 05:13 (UTC)

cat: /usr/lib/modules/extramodules-ARCH/version: Arquivo ou diretório inexistente

SilverMight commented on 2018-10-29 20:05 (UTC)


Nevermind, after checking dmesg I realized I needed to run mkinitcpio. Thanks

jcstryker commented on 2018-10-29 19:28 (UTC)


I currently run the DKMS version with the stock kernel. Any error messages when you run dmesg?

SilverMight commented on 2018-10-29 19:25 (UTC)

Can't seem to get this to boot using the DKMS package on stock and zen kernel

silelmot commented on 2018-10-27 15:33 (UTC) (edited on 2018-10-27 15:37 (UTC) by silelmot)

@krompus i managed to get steam running after installing the lib32-drivers (and opencl , but dont know if you need this) and than did a restart

jcstryker commented on 2018-10-16 03:00 (UTC)

@chimaera I'm glad you were able to resolve it, arch recently fiddled with the naming of their extramodules directory, but it should be stable now with new kernel releases. Using makepkg -i wont work because this split package includes the dkms version as well, you need to build it then install manually or use an aur helper.

@krompus I'm not sure that your issue with steam is related to the driver update. Make sure you have all the dependencies and try searching for the error that steam gives you if you launch it from the command line.

krompus commented on 2018-10-15 00:24 (UTC)

@jcstryker Thanks! I've managed to install these drivers now, but Steam won't launch anymore.

chimaera commented on 2018-10-14 14:33 (UTC) (edited on 2018-10-14 16:47 (UTC) by chimaera)

cat: '/usr/lib/modules/extramodules-*-ARCH/version': no such as file or directory I get this error during compilation of the nvidia-vulkan

Edit: I solved this issue by updating all my packages. Probably the previous kernel version was too old.

Now it creates all the packages without issues, but there is still one final issue (during the dependency check after I enter the correct user password) preventing the installation:

"nvidia-vulkan and nvidia-vulkan-dkms are in conflict"

What can be the cause of this conflict?

Edit 2: It gave the dependency conflict error via the "makepkg -si" method.

Because I couldn't resolve this conflict via the recommended "makepkg -si" I tried to install the package again but this time by using the AUR helper bauerbill.

And it installed without problems. Maybe it's not because I used bauerbill but because I rebooted, I don't really know. But anyway it worked and I think these instructions may help people with the same problems :)

jcstryker commented on 2018-10-13 18:56 (UTC)


I am getting this error as well, still investigating. The download link does work in firefox but fails when makepkg uses curl.

As a workaround for now, you can create a ~/.curlrc file with the line --http1.1

krompus commented on 2018-10-13 18:10 (UTC)

I'd like to try this driver out because I hear that it works better with Proton for Steam than the main nvidia 410.57-4 driver. I'm getting a download error when I try to install this, though. I entered the url in my browser, and it was unresolved. Removed the "s" from https (so, just http), and I was prompted for the download. Tried editing the pkgbuild with that, and the download error persisted. Any ideas what the issue might be? Thanks!

yodaembedding commented on 2018-09-16 03:37 (UTC)

I'm getting the following error:

:: installing nvidia-vulkan-utils (396.54.05-1) breaks dependency 'nvidia-vulkan-utils=396.54.02' required by nvidia-vulkan-dkms

jcstryker commented on 2018-09-10 21:40 (UTC) (edited on 2018-09-11 02:21 (UTC) by jcstryker)


The module needs to be rebuilt with every kernel update. That is why the official repos bump the package version each time they release a kernel. I don't do that with this package because it includes all the other utils needed to use the driver. You simply need to build nvidia-vulkan again with each kernel, and if you use early kernel module loading you need to rebuild your initramfs.

I wish there was a better way to handle this, this all stems from nvidia's shenanigans with their kernel module. It frustrates the official maintainers as well.

pikimeister commented on 2018-09-09 06:48 (UTC) (edited on 2018-09-09 06:49 (UTC) by pikimeister)


This package doesn't seem to work with latest kernel version provided by archlinux (4.18.6-arch1-1-ARCH).

X doesn't start.

Had to uninstall this version and install nvidia 396.54-3 (from default repos) in order to overcome the issue.

jcstryker commented on 2018-09-01 10:45 (UTC) (edited on 2018-09-01 10:48 (UTC) by jcstryker)


That's very strange, it builds fine with no infinite loop on my test server using aurutils and on my desktop using yay.

Which aur helper are you using?

theriddick commented on 2018-09-01 06:09 (UTC)

Well it installed on my system but for some reason it kept infinite loop downloading and installing over and over, dunno why. Canceling it didn't appear to break anything and the packages are installed fine. (along with utils/32bit utils)

t-ask commented on 2018-08-17 18:30 (UTC)

Just to let you know. Kernel update 4.18 leads to "installing linux (4.18.1.arch1-1) breaks dependency 'linux<4.18' required by nvidia-vulkan"

Sneezemeat commented on 2018-08-07 20:13 (UTC) (edited on 2018-08-07 20:16 (UTC) by Sneezemeat)

Based on this commit and this commit, you need to change the line _extramodules=extramodules-4.17-arch to _extramodules=extramodules-ARCH in the PKGBUILD

jcstryker commented on 2018-08-05 13:39 (UTC)


This is due to a change in the extramodules directory with the latest kernel package in the arch repos. Should be resolved now, let me know if you have any other issues.

commented on 2018-08-05 08:37 (UTC)

The build is failing for me with the following error:

==> Starting build()...
cat: /usr/lib/modules/extramodules-4.17-ARCH/version: No such file or directory
==> ERROR: A failure occurred in build().

The file does indeed seem to be missing. Is there some package I'm missing, or is this due to a change in the kernel packages?

jcstryker commented on 2018-07-22 04:16 (UTC)


The regular nvidia-vulkan is packaged for the standard linux kernel in the main repos, while nvidia-vulkan-dkms is packaged for use with dkms and can be used with any kernel(standard, linux-lts, linux-hardened, etc.)

Feature-wise there is no difference, so when in doubt use the non-dkms version.

twisty commented on 2018-07-22 03:13 (UTC)

What is the difference between the two packages (dkms vs not)?

jcstryker commented on 2018-07-17 20:16 (UTC)

@DAVVVVE I am glad you got this working on your system

jcstryker commented on 2018-07-17 20:16 (UTC)

To properly handle the choice between nvidia-vulkan and nvidia-vulkan-dkms, I recommend using an AUR helper with proper split package support.

jcstryker commented on 2018-07-10 18:20 (UTC) (edited on 2018-07-10 18:31 (UTC) by jcstryker)


You are very welcome. I corrected the package to provide nvidia-utils and opencl-nvidia.

While testing, I was able to install cuda on my system. Let me know if you have any other issues.

jcstryker commented on 2018-07-10 17:45 (UTC) (edited on 2018-07-10 18:33 (UTC) by jcstryker)


It is structured as a package group, so this package will build the nvidia driver, utils, lib32-*, etc.

Most aur helpers will let you pick which components of the package group to install, which is where you would choose the main or dkms version of the driver, same process with a standard git clone and makepkg(though I suppose the -i flag would cause issues).

Some aur helpers will let you build the package but install only specific packages of the group e.g.:

'aur-helper -Syu nvidia-vulkan nvidia-vulkan-utils'

This would avoid the conflict between nvidia-vulkan and nvidia-vulkan-dkms.

If you or anyone else has an idea on how to structure this better I would welcome it. However right now it works well for the way I install aur packages (aurman).

mastercoms commented on 2018-07-10 17:42 (UTC) (edited on 2018-07-10 17:49 (UTC) by mastercoms)

Could the nvidia-vulkan-utils package provide nvidia-utils and opencl-nvidia-vulkan provide opencl-nvidia? It is needed for CUDA.

Thank you for your work on this package.

Enverex commented on 2018-07-10 16:31 (UTC)

This package now conflicts with itself:

:: nvidia-vulkan and nvidia-vulkan-dkms are in conflict

Is it now a case of having to manually pick out the parts of the final completed build that you want installed?

jcstryker commented on 2018-07-10 01:09 (UTC)

@pshe94 nvidia-settings is now included in nvidia-vulkan-utils, let me know if you have any other issues

@apathy you are very welcome, glad the package is is working for you now

pshe94 commented on 2018-07-09 23:58 (UTC)

@jcstryker after 396.24.02-4 update nvidia-settings is missing, and trying to install it from Arch repo returns an error: nvidia-utils and nvidia-vulkan-utils are in conflict.

apathy commented on 2018-07-09 21:58 (UTC)

@jcstryker i was getting the libglvnd conflicts too but the new pkgbuild worked hassle-free. thanks for your efforts

jcstryker commented on 2018-07-09 16:25 (UTC) (edited on 2018-07-09 16:25 (UTC) by jcstryker)

Hello, sorry for the delayed response. I was on holiday.

I have rewritten the package following the suggestion from @NoMore66201 to use the official PKGBUILDs from the arch repos.

This should fix the libglvnd(@NoMore66201) and egl-wayland(@vanyasem) conflicts.

@gablink, I have included the dkms package as well but I have not tested it yet. Let me know if you have any issues.

@DocMAX, try the new PKGBUILD and let me know if you are still having issues. It should now depend on libglvnd and cleanly replace nvidia and nvidia-utils.

@Chais, thanks for the suggestion. I was previously following the nvidia-full-beta PKGBUILD but am now basing it off the official Arch PKGBUILD. Let me know if you have any other corrections or improvements, I appreciate the advice.

NoMore201 commented on 2018-07-09 11:50 (UTC) (edited on 2018-07-09 11:50 (UTC) by NoMore201)

If someone else has troubles with this, just download nvidia,nvidia-utils,lib32-nvidia-utils PKGBUILDs from arch repos. All you need to do is modify sources to point to 396.24.02 drivers, update shasums and pkgver variables and build them.

vanyasem commented on 2018-07-08 11:13 (UTC)

Conflicts with egl-wayland

Chais commented on 2018-07-06 01:12 (UTC)


_kernel=$(cat /usr/lib/modules/extramodules-*-ARCH/version)

is not the proper way to determine the kernel version. It necessitates an existing installation of nvidia or nvidia-vulkan to populate that directory. While the target system probably fulfills that assumption, the build system doesn't necessarily. Please use

_kernel=$(uname -r)


DocMAX commented on 2018-07-05 17:26 (UTC) (edited on 2018-07-05 17:26 (UTC) by DocMAX)

can't install:

error: failed to prepare transaction (could not satisfy dependencies)

:: unable to satisfy dependency 'libgl' required by nvidia-vulkan

NoMore201 commented on 2018-07-03 16:17 (UTC)

This package conflicts with libglvnd and provides its libgl package, so that it can't be used with Optimus laptops. Is it intended?

elgabo commented on 2018-07-02 06:52 (UTC)

Hi! Could you do the dkms package too ? (For custom kernels)