Package Details: opencl-nvidia-470xx 470.256.02-7

Git Clone URL: https://aur.archlinux.org/nvidia-470xx-utils.git (read-only, click to copy)
Package Base: nvidia-470xx-utils
Description: OpenCL implemention for NVIDIA
Upstream URL: http://www.nvidia.com/
Keywords: driver nvidia video
Licenses: custom
Conflicts: opencl-nvidia
Provides: opencl-driver, opencl-nvidia
Submitter: jonathon
Maintainer: Sinyria (cysp74, SoftExpert)
Last Packager: SoftExpert
Votes: 100
Popularity: 1.15
First Submitted: 2021-10-31 00:50 (UTC)
Last Updated: 2024-11-10 08:39 (UTC)

Dependencies (2)

Required by (67)

Sources (11)

Latest Comments

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

pervokur commented on 2024-03-04 09:22 (UTC)

I was able to compile kernel modules with clang-16 (my kernel is x86-64 6.7.8 clang-16 full lto)

1)edit conftest.sh change CC=$1 to CC=gcc, because this script isn't working correctly with clang-16

2) IGNORE_CC_MISMATCH=1 for me reported kernel compiler is something like "clang 16.0.6 ld.lld 16.0.6", so this environment variable helps me to pass compiler check

3) -MMD to -MD I wrapped clang-16, so -MMD option will be replaced with -MD. (maybe it's enough to remove '-MD' from Kbuild file, so there will no conflict between -MMD and -MD)

Ganna commented on 2024-03-02 03:36 (UTC) (edited on 2024-03-02 07:09 (UTC) by Ganna)

@wviana and others. Warning the procedures also uninstall steam. I have to typically install steam doing

pacman -Sdd steam

however reinstalling steam the same way was also no problem.

because for some time steam complains about lib32 stuff for nvidia, its clearly broken and has been for some months.

I had the same error message. I took these steps. First I removed all.

yay -Rc nvidia-470xx-dkms lib32-nvidia-470xx-utils

Then I simple reinstalled them, since they are not present on the system, no dependency errors, and since they reinstalled simultaneously, there is no problem.

yay -S nvidia-470xx-dkms lib32-nvidia-470xx-utils

If not using a helper like yay, I guess you would do something like.

makepkg -sri

From each directory of the extracted snapshot files. It should work, although I don't do this anymore since it has become increasingly complicated to install these drivers correctly. However if doing the manual way issue 'sudo mkinitcpio -p linux' after installing, that usually solved most problems for me in the past.

There will come a time when our hardware is no longer updated, breakage is to be expected at some point.

Sinyria commented on 2024-02-24 20:41 (UTC)

yes, the nvidia-dkms depends on the exact version number of nvidia-utils - so you have to install both a the same time. if you only update utils, your older dkms will have broken dependency, and if you update only dkms, your new dkms will have unmet dependency. so you have to use a smart helper or install both packages simultaneously.

I did as SoftExpert - makepkg -sicC then you have the 3 packages you can install however you'd like sitting in your folder.

yay -S nvidia-470xx-dkms nvidia-470xx-utils opencl-nvidia-470x

should work as well tho!

cotton commented on 2024-02-24 13:10 (UTC)

@SoftExpert thanks, sorted. FWIW I used pikaur -S nvidia-470xx-utils nvidia-470xx-dkms opencl-nvidia-470x

SoftExpert commented on 2024-02-24 05:53 (UTC)

@wviana , @cotton: it looks like a missing / conflicting dependency on your system.

nvidia-470xx-utils produces 3 packages:

  • nvidia-470xx-utils

  • nvidia-470xx-dkms

  • opencl-nvidia-470xx

You have to install all of them.

I can install all 3 packages with a single command makepkg -sicC from the folder where I cloned this repository.

There is also lib32-nvidia-470xx-utils which you might have to install afterwards, the same way.

When installing the NVidia drivers I do not wait for the packages to be pulled from the repository by the update tool (pacman, pamac, yay or other). I do it from the repository folder with the mentioned command. The dependencies are all built at the same time, so there are no conflicts.

cotton commented on 2024-02-24 01:50 (UTC)

I also get the errors wviana has reported.

wviana commented on 2024-02-23 18:20 (UTC)

Today I start getting this errors when trying to update.

==> Sources are ready.
nvidia-470xx-utils-470.239.06-1: parsing pkg list...
:: nvidia-470xx-utils-470.239.06-1 is up to date -- skipping build
loading packages...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing nvidia-470xx-utils (470.239.06-1) breaks dependency 'nvidia-470xx-utils=470.223.02' required by nvidia-470xx-dkms
loading packages...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing nvidia-470xx-utils (470.239.06-1) breaks dependency 'nvidia-470xx-utils=470.223.02' required by nvidia-470xx-dkms
loading packages...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing nvidia-470xx-utils (470.239.06-1) breaks dependency 'nvidia-470xx-utils=470.223.02' required by nvidia-470xx-dkms
error: packages failed to build: lib32-nvidia-470xx-utils-470.239.06-1 (lib32-nvidia-470xx-utils lib32-opencl-nvidia-470xx)  nvidia-470xx-utils-470.239.06-1 (nvidia-470xx-dkms opencl-nvidia-470xx)

SoftExpert commented on 2024-02-17 14:49 (UTC)

@gamezelda: Thanks for the heads-up ! I disabled for now the patch as it builds normally without it with the latest kernels.

gamezelda commented on 2024-02-17 12:23 (UTC)

I believe that you can drop the recent "kernel-6.1.76_6.6.15_6.7.3.patch" patch, as all affected kernels have newer releases (6.1.77, 6.6.16, 6.7.4) which include a commit "mm, kmsan: fix infinite recursion due to RCU critical section" that makes it unnecessary.

I have verified that the driver builds correctly for all kernels in the official repositories (i.e. linux{,-hardened,-lts,-rt,-rt-lts,-zen}) without the patch.

ChrispyChris commented on 2024-02-04 06:29 (UTC)

@SoftExper: Absolutely, I will do that. Thanks and the same to you!