Package Details: nvidia-470xx-dkms 470.223.02-1

Git Clone URL: (read-only, click to copy)
Package Base: nvidia-470xx-utils
Description: NVIDIA drivers - module sources
Upstream URL:
Keywords: driver nvidia video
Licenses: custom
Conflicts: nvidia-dkms
Submitter: jonathon
Maintainer: Sinyria (cysp74, SoftExpert)
Last Packager: SoftExpert
Votes: 90
Popularity: 2.17
First Submitted: 2021-10-31 00:50 (UTC)
Last Updated: 2023-10-31 19:08 (UTC)

Latest Comments

1 2 3 4 5 6 .. 28 Next › Last »

picoman commented on 2023-11-07 22:23 (UTC)

Is it just me or is the upstream super slow? It is taking an hour and a half to download.

SoftExpert commented on 2023-11-03 07:33 (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.

qunas commented on 2023-11-03 00:34 (UTC)

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

aqeeliz commented on 2023-11-01 10:13 (UTC)

@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.


SoftExpert commented on 2023-10-31 18:38 (UTC)

@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.

aqeeliz commented on 2023-10-31 16:20 (UTC)

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.

SoftExpert commented on 2023-10-30 08:27 (UTC) (edited on 2023-10-30 08:28 (UTC) by SoftExpert)

@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.

wonton commented on 2023-10-29 03:33 (UTC)

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...

SoftExpert commented on 2023-09-12 10:43 (UTC)

Color profiles (to be pinned)

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.

  • Step 1: Within your Desktop settings, visit the Color management properties editor
  • Step 2: For each monitor, expand the monitor’s profiles, select each profile, and click “Remove profile” until no profiles remain
  • Step 3: Restart Chrome

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)
  colormgr device-add-profile $DISPLAY_PATH $SRGB_PATH;
  colormgr device-make-profile-default $DISPLAY_PATH $SRGB_PATH;

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

Using 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.