You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of generating management CDI specifications, the container-toolkit container creates control device nodes. This requires reading the device major number from /proc/devices. This fails in drivers from 550.40.x since the nvidia-frontend module was renamed nvidia.
Changed the name visible in /proc/devices of NVIDIA devices and theNVIDIA control device from "nvidia-frontend" to "nvidia" and "nvidiactl".Scripts which parse /proc/devices (such as udev rules) may need to beupdated. Note that the conventional /dev device paths like /dev/nvidia0and /dev/nvidiactl remain unchanged.
This can be triggered by starting the toolkit container with CDI enabled to trigger the code path but will also affect the nvidia-ctk system create-dev-char-symlinks command.
We should probably do the same as this will ensure that we remain compatible across driver versions.
The text was updated successfully, but these errors were encountered:
elezar
changed the title
Add support for 550.x drivers to the toolkit container
Add support for >= 550.40.x drivers to the toolkit container
Jan 31, 2024
As part of generating management CDI specifications, the container-toolkit container creates control device nodes. This requires reading the device major number from
/proc/devices
. This fails in drivers from 550.40.x since thenvidia-frontend
module was renamednvidia
.See: https://www.nvidia.de/Download/driverResults.aspx/218124/en-us
This can be triggered by starting the toolkit container with CDI enabled to trigger the code path but will also affect the
nvidia-ctk system create-dev-char-symlinks
command.Note that
nvidia-modprobe
hardcodes the major number: https://github.com/NVIDIA/nvidia-modprobe/blob/d6bce304f30b6661c9ab6a993f49340eafca7a7e/modprobe-utils/nvidia-modprobe-utils.c#L85We should probably do the same as this will ensure that we remain compatible across driver versions.
The text was updated successfully, but these errors were encountered: