Search Criteria
Package Details: opencl-nvidia-525xx 525.116.04-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/nvidia-525xx-utils.git (read-only, click to copy) |
---|---|
Package Base: | nvidia-525xx-utils |
Description: | OpenCL implemention for NVIDIA, 525 branch |
Upstream URL: | http://www.nvidia.com/ |
Licenses: | custom |
Conflicts: | opencl-nvidia |
Provides: | opencl-driver, opencl-nvidia |
Submitter: | Vrakfall |
Maintainer: | Vrakfall |
Last Packager: | Vrakfall |
Votes: | 6 |
Popularity: | 1.17 |
First Submitted: | 2023-04-27 00:33 (UTC) |
Last Updated: | 2023-05-17 13:35 (UTC) |
Dependencies (3)
- zlib (zlib-ng-compat-git, zlib-git, zlib-ng-compat)
- patchelf (make)
- opencl-headers (opencl-headers-git) (optional) – headers necessary for OpenCL development
Required by (70)
- aftershotpro2 (requires opencl-nvidia) (optional)
- aftershotpro3 (requires opencl-nvidia) (optional)
- arrayfire-git (requires opencl-driver) (optional)
- bfgminer (requires opencl-nvidia) (optional)
- bfgminer-git (requires opencl-nvidia) (optional)
- butterflow (requires opencl-nvidia) (optional)
- caffe-opencl-git (requires opencl-driver)
- computecpp (requires opencl-driver)
- cpu-x-opencl (requires opencl-driver) (optional)
- cuda-10.0 (requires opencl-nvidia)
- cuda-10.1 (requires opencl-nvidia)
- cuda-10.2 (requires opencl-nvidia)
- cuda-11.0 (requires opencl-nvidia)
- cuda-11.1 (requires opencl-nvidia)
- cuda-11.7 (requires opencl-nvidia)
- cuda-8.0 (requires opencl-nvidia)
- cuda-9.0 (requires opencl-nvidia)
- cuda-9.1 (requires opencl-nvidia)
- cuda-9.2 (requires opencl-nvidia)
- cuda11.1 (requires opencl-nvidia)
- Show 50 more...
Latest Comments
1 2 Next › Last »
xiota commented on 2023-09-20 09:05 (UTC)
Please remove
replaces
directive. Thank you. (No need to reply via comment; AUR now sends commit notifications.)vpancora commented on 2023-09-13 17:27 (UTC)
Hi, there is a bug that prevents the use of linux 6.5 with 525.125.04 version but the 525.125.06 driver fix it.
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165
When will the new version be released? Tks
Vrakfall commented on 2023-05-30 12:09 (UTC)
@ffernn Yes, the corresponding
lib32-nvidia-utils
is required forSteam
to work. You're welcome. ;)ffernn commented on 2023-05-23 08:46 (UTC)
Ah yep that's working. Thanks sm for putting this package up, easier than trying to use archives
ffernn commented on 2023-05-23 08:36 (UTC)
@Vrakfall I installed nvidia-525xx-dkms and nvidia-525xx-utils. Do I need the lib32 one as well? I guess that makes sense with steam being 32 bit.
Vrakfall commented on 2023-05-22 10:46 (UTC)
@theriddick That's what I thought. If it works on X11, I can't do anything for you, sorry. You could indeed have a script that switches your display's frequency upon login, or you could report it to
Nvidia
so they are aware of the bug and fix it.@ffernn Did you install lib32-nvidia-525xx-utils alongside this package?
ffernn commented on 2023-05-22 10:11 (UTC)
Hey I tried installing this, as I have a 170hz monitor but have been stuck at 120. It works well and I'm able to switch back to 170hz, but trying to open steam throws the error
SteamUpdateUI: An X Error occurred X Error of failed request: BadValue (integer parameter out of range for operation).
I'm using hyprland under arch linux with a 3060ti.
theriddick commented on 2023-05-17 23:25 (UTC) (edited on 2023-05-18 01:16 (UTC) by theriddick)
@Vrakfall it is exclusive to Sway/wlroots AND Wayland Plasma.
This is not a X11 bug and yes X11 works.
Many reports have been around for over a month now.. everyone is left waiting on NVIDIA to fix this. I don't believe this is to blame on wlroots or Plasma.
UPDATE: Finally did some more testing and I can say now that ALL desktops running under wayland will system failure to blackscreen and non-recoverable without reboot if screen hz is above 75.
This includes GNOME as I've did more testing now and found out that also is affected. So a pretty damn major NVIDIA bug if I do say so myself!
...... ......
I DARE SAY that someone SMART enough could find a little hacky fix for this problem as the displays WORK above 75hz if you have them set to that or lower on launch then adjust them afterwards. This is related to compositor launch (I've tested without SDDM login method)
So you could do a hacky thing where it sets them to 60hz on WL launch then sets them back to your proper hz once compositor has loaded. I could probably figure this out eventually but cbf atm.
(or someone could just fix the bug somehow. lol)
1 2 Next › Last »