-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nvidia-driver: detection of nvidia devcies #1364
Comments
Make sense. Could you share examples of NVIDIA_PRODUCT_TYPE where this is needed? |
I think we might need two variables, one for the 'driver type' and one for identifying the devices. Currently, the NVIDIA_PRODUCT_TYPE variable is used for both. For example:
So maybe two variables |
Can you check if the proposed function catches all of the cases that you listed above:
That should be generic enough and leave the user to only have to worry about the driver type to deploy. |
I have tested on systems containing RTX 2000, RTX 4000, RTX 6000 series consumer grade and datacenter GPUs as well as with Tesla A100 and L40 GPUs. Worked everywhere. |
I'll close this since it's going to be part of the next set of releases. |
Description
The nvidia.service uses
lspci | grep -i "${NVIDIA_PRODUCT_TYPE}")"
here to detect the presence of nvidia devices. Not all Nvidia GPUs include their product type in the name that lspci outputs.Changing the product type to something else that matches the devices breaks the download link for the driver files.
Impact
Nvidia driver will not be installed on machines that need the driver.
Expected behavior
Maybe just use
lspci | grep -i NVIDIA
. This is already happening in other places in the install script.Additional information
Flatcar 3815.2.0
The text was updated successfully, but these errors were encountered: