| Git Clone URL: | https://aur.archlinux.org/nvidia-470xx-utils.git (read-only, click to copy) |
|---|---|
| Package Base: | nvidia-470xx-utils |
| Description: | NVIDIA drivers utilities |
| Upstream URL: | http://www.nvidia.com/ |
| Keywords: | driver nvidia video |
| Licenses: | custom |
| Conflicts: | nvidia-libgl, nvidia-utils |
| Provides: | nvidia-libgl, nvidia-utils, opengl-driver, vulkan-driver |
| Submitter: | jonathon |
| Maintainer: | Sinyria (cysp74, SoftExpert) |
| Last Packager: | SoftExpert |
| Votes: | 103 |
| Popularity: | 1.05 |
| First Submitted: | 2021-10-31 00:50 (UTC) |
| Last Updated: | 2025-02-03 19:42 (UTC) |
@qunas: It's kinda vague ...
What is your current kernel version ?
Did you ran out of storage space when rebuilding the module ?
If you are you using DKMS, have you installed the corresponding kernel headers ?
Can you check if DKMS has successfully built the driver module for your current kernel ?
Where there any updates installed at the same time ?
You see where I'm headed - you need to have a thorough investigation in order to identify what went wrong.
Something about the latest upgrade breaks my DE. It stops at “Notify about reboot on special conditions” and doesn't launch the DE. Everything works fine if I system upgrade with ignoring these packages
@SoftExpert: Thanks for your comment. Actually that's what I am doing. The easiest thing was to check here if everyone is having problem, but it seems not. So, doesn't appear to be a drivers issue.
Will try downgrading the kernel and see if that works. If not, will continue with the other debugging options and try to find a way to get the cable / port checked.
Thanks.
@aqeeliz: It's fairly difficult to pinpoint the source of error. You should proceed by excluding possible causes:
electrical (is the cable in perfect working state, are the connectors loose)
software (which version of kernel has been installed, which version of the driver has been installed, which combination of kernel+driver exhibits the issue, does reverting to previous version stops the issue from appearing)
which configuration has changed
You get the idea, you have to be thorough and apply a consistent method to identify the origin of the problem.
Is anyone else having problem connecting external monitor after the latest update?
I am not sure if it's the drivers, or the kernel, or some issue with the cable / port. Unfortunately I can't test the cable / port right now, so just asking here if anyone noticed any issues.
I am using HP Zbook, which has a "DisplayPort" instead of HDMI, so have to use DisplayPort to HDMI cable for monitor. In case that's relevant.
@wonton: You should expect less compatibility and more issues going forward with this version of the drivers; they are only maintained by Nvidia for a limited amount of time for the older cards out there.
That being said, you could read the following pieces of information:
You can still install the CUDA package (v12.2.2 is the latest, if I'm not mistaken) - I just did it and it did not complain about my version of the drivers.
However, I must insist: since the differences with the actively maintained versions of the drivers are increasing, you should expect increasing instabilities / incompatibilities with the advanced features.
how can we fix Driver does not support the required nvenc API version. Required: 12.1 Found: 11.1 when trying to use nvenc? i can use it with windows drivers but not in linux...
If, like me, you have been affected by a degrading in the quality of colors, the following procedure can help (source). The result affects all applications, but especially Chrome-based browsers and Electron-based applications will benefit.
Chrome retrieves the color profile to use from the _ICC_PROFILE atom on the root window.
Using colormgr from the command line
To persistently set the colord default color space from the command line, copy-paste the following block into a terminal
SRGB_PATH=$(colormgr get-standard-space srgb | grep "Object Path:" | cut -d: -f2);
for DISPLAY_PATH in $(colormgr get-devices display | grep "Object Path:" | cut -d: -f2)
do
colormgr device-add-profile $DISPLAY_PATH $SRGB_PATH;
colormgr device-make-profile-default $DISPLAY_PATH $SRGB_PATH;
done
or follow the below steps:
Step 1: Get the object path for the sRGB colorspace. Do this by running:
colormgr get-standard-space srgb
Note down the “Object Path” (it will be something like /org/freedesktop/…). We’ll refer to this path as SRGB_PATH in future steps.
Step 2: Get the object paths for the devices for which you want to reset. Do this by running
colormgr get-devices
Note down the “Object Path” of each device you want to set the color profile for (again it will be something like /org/freedesktop/…). We’ll refer to each of these paths as DISPLAY_PATH in future steps.
Step 3: For each device, register the sRGB color profile with the device. Do this by running:
colormgr device-add-profile DISPLAY_PATH SRGB_PATH
Where SRGB_PATH is the path obtained in step 1 and DISPLAY_PATH is the path for each device obtained in step 2.
Note that you may ignore error reports saying “profile object path … has already been added”.
Step 4: For each device, set the default color profile to be the sRGB color profile. Do this by running:
colormgr device-make-profile-default DISPLAY_PATH SRGB_PATH
Again, here SRGB_PATH is the path obtained in step 1 and DISPLAY_PATH is the path for each device obtained in step 2.
Step 5: Restart Chrome
xprop (current session only)To remove the color profile for the current session only, run
xprop -root -remove _ICC_PROFILE
You’ll need to restart Chrome for us to re-read the property.
Note that this will only apply to the current session.
@FishBoneEK this is intentional, linux-headers should not be included as a dependency in dkms packages. Wiki link: DKMS guidelines
Pinned Comments
SoftExpert commented on 2025-02-09 10:20 (UTC)
For the beginners in need of assistance, first take a look at this recommended guide https://github.com/korvahannu/arch-nvidia-drivers-installation-guide - maybe it helps to solve the issues your are having with this version of the driver.