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.20
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 2 3 4 5 6 7 .. 41 Next › Last »

ventureo commented on 2024-10-08 15:19 (UTC)

Hi. In the latest update, nvidia-utils package enabled the use of nvidia_drm.modeset=1 and nvidia_drm.fbdev=1 by default. Although fbdev=1 option does not exist for the 470.xx driver branch, using modeset=1 by default can be very useful, because although Wayland does not work properly on this version, it is still required for PRIME configurations to work properly (see https://download.nvidia.com/XFree86/Linux-x86_64/470.256.02/README/randr14.html). So I think it would be useful to include this in this package at least through the /usr/lib/modprobe.d file installation.

SoftExpert commented on 2024-10-06 19:50 (UTC)

@Scimmia: Indeed, this seems to be the end.

On the page Current graphics driver releases there is now a (*) next to the 470.239.06 (x86_64 175) - GKxxx “Kepler” GPUs line.

It was not there a few days ago.

They did not even bother to update the link - 470.256.02 is the latest (last ?) version of this driver generation.

What can I say, it was a wild ride ...

I made a big switch - I went with a Minisforum MS-A1 which has a Ryzen 8700G with an integrated Radeon 780M; I did not expect it to work so flawlessly ! Nothing to configure, everything recognized from the start, very good performance. Ah, and a reasonable price (sorry for the pub, I'm just sharing my experience).

Scimmia commented on 2024-10-06 14:51 (UTC)

According to https://nvidia.custhelp.com/app/answers/detail/a_id/5202 , support for the 470 series ended at the end of last month. That page hasn't been updated in a long time, though, does anyone have any newer information?

SoftExpert commented on 2024-09-24 06:24 (UTC)

@Alexey104: The most frequent and frustrating one is occurring several times a day; all the Plasma panels and widgets are frozen; sometimes I'm in the middle of either listening music or in a Teams or Meet call; UI will not respond at all, often even the cursor will be frozen as well - but the sound will continue without interruption. It takes 20s, 30s or more until the notification "Desktop effects were restarted due to a graphics reset" is shown, and then everything is normal again until the next one which can be 50s away or a couple of hours ...

I noticed that using a combination of browsers (Firefox and Chromium-based) seems to increase the chances of having a graphics reset.

The other freeze is due to how NFS waiting time is handled in combination with systemd. I have the same setup of the NFS server and the same hardware for years and things started to go bad more than a year ago. Now it manifests at startup - frozen panels and widgets and then notifications of random file-systems that "are not responding", altough I can access their contents from the conole perfectly fine.

I do not have reboots, though.

Alexey104 commented on 2024-09-23 06:41 (UTC)

@SoftExpert, May I ask which desktop freezes you are referring to? I am asking because I’ve been experiencing hard freezes with spontaneous reboots myself, starting from kernel 6.7 up to the current mainline (no problems with LTS, though), and I am interested in learning more about similar issues.

SoftExpert commented on 2024-09-23 05:51 (UTC)

@drankinatty: We are lucky - for now: the official 6.11 (6.11.0) (official flavor, xanmod) is building fine the driver.

The desktop freeze is more and more frequent, though; I read that it has spread to more recent driver versions and it impacts more powerfull cards. I believe it is an unfortunate mix of kernel changes, resistance to these changes at the driver code plus some systemd quircks that are purposefully hard to isolate.

I think Nvidia is following other priorities - end-user sales are not bringing enough revenue to satisfy their appetite...

I will end up replacing my old and faithful laptop and I will stay away from Nvidia.

Minisforum here I go ... ;-)

drankinatty commented on 2024-09-19 19:03 (UTC)

Well, I'm cautiously optimistic we will have another minor version update to the kernel without a patch required like the 6.8 -> 6.9 update. I've been looking (see nvidia-390xx-utils 390.157-12) for a couple days and all I've uncovered is runtime issues on Fedora with green-screen problems, but no build time problems or patches in the normal spots (herecura git repository, nvidia dev forums, etc..). Fingers crossed.

SoftExpert commented on 2024-09-09 13:31 (UTC)

The 6.11 kernel release is getting closer; on my side, I could compile the nvidia-470xx modules without any additional change - latest RC at this time is RC7.

Is this the case four you also ?

SoftExpert commented on 2024-07-21 07:17 (UTC) (edited on 2024-07-21 07:18 (UTC) by SoftExpert)

Finally, we have a patch that works !

Big thank you to philmmanjaro who posted the patch on the NVidia forum.

With this patch I build successfully the kernel modules on:

  • 6.6.41

  • 6.9.10

  • 6.10

Hopefully it works for all of you out there ..

SoftExpert commented on 2024-07-16 06:58 (UTC) (edited on 2024-07-17 23:46 (UTC) by SoftExpert)

Heads-up: kernel 6.10 does not play nice with our current driver version (470.256.02); I'm still evaluating the patch required to make it work.

Update: a post on Nvidia forum has been created, in search of a solution.

« First ‹ Previous 1 2 3 4 5 6 7 .. 41 Next › Last »