Controls/gitea-pages
0
2
Fork 0
Code Pull Requests Actions Activity

typos and improvements in understandability

Browse Source
This commit is contained in:
buchel_k
2022-11-28 13:33:32 +00:00
parent 7519014ee2
commit 30f751a426
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
rhel8/nvidia.md
+6 -6
View File
@@ -53,7 +53,7 @@ I did not find much information about Nvidia driver version structure and policy
Their drivers are oranized in driver branches. As you see for example in their [Unix Driver Archive](https://www.nvidia.com/en-us/drivers/unix/) noted as e.g. `470.xx series`.
There are `Production` and `New Feature` branches (and, on the above linked page, a `Beta Version` which is not linked to any of the above branches (yet?).
There are `Production` and `New Feature` branches (and, on the above linked page, a `Beta Version` which is not linked to any of the above branches (yet?)).
Such a branch can be considered a major release and with new braches adding support for new hardware or removing support for old hardware.
The drivers within a branch are maintained quite a long time. Individual drivers in that branch get increasing version numbers which just start with the same first "branch" number.
@@ -66,13 +66,13 @@ Also it is not possible to find out from the package meta information if a drive
To figure out what driver branch to use for given hardware, go to their [Download page](https://www.nvidia.de/Download/index.aspx) and search its Linux driver. It will then point out a driver version and its first number points out the driver branch to use.
Note that this is not always the full story. For example the Tesla K40c gives [driver 460.106.00](https://www.nvidia.de/Download/driverResults.aspx/182244/en-us), where as the 470 branch driver still works, though the [470 driver](https://www.nvidia.com/Download/driverResults.aspx/194637/en-us/) still works, even though the hardware is not listed as supported there. My guess is that they somehow publickly differentiate between "Data Center Driver" and "Display Driver", but still they have everything in, or at least in the production/long term support branch.
Note that this is not always the full story. For example the Tesla K40c gives [driver 460.106.00](https://www.nvidia.de/Download/driverResults.aspx/182244/en-us), whereas the [470 driver](https://www.nvidia.com/Download/driverResults.aspx/194637/en-us/) still works, even though the hardware is not listed as supported there. My guess is that they somehow publickly differentiate between "Data Center Driver" and "Display Driver", but still they have everything in, or at least in the production/long term support branch.
Another option to figure out the driver is the third-party tool [`nvidia-detect`](http://elrepo.org/tiki/nvidia-detect) by ElRepo. It tells which driver package from ElRepo it suggests, but it can also be used to figure out which production/long term support branch can be used (and only production/long term support branch, e.g. it would never point out the 460 branch and this is how I figured out that Tesla K40c works with 470 despite the Nvidia documentation not saying so).
Another option to figure out the driver is the third-party tool [`nvidia-detect`](http://elrepo.org/tiki/nvidia-detect) by ElRepo. It tells which driver package from ElRepo it suggests, but it can also be used to figure out which production/long term support branch can be used (and only production/long term support branches, e.g. it would never point out the 460 branch and this is how I figured out that Tesla K40c works with 470 despite the Nvidia documentation not saying so).
### CUDA - Driver Compatibility
A CUDA version needs a suitably new driver version, which old CUDA versions are supported by newer driver versions. To figure out up to which CUDA version runs on your installed driver, check out "Table 3" of the [CUDA release notes](https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html). For each driver branch there is a major 11.x.0 release with possible further bugfix releases.
A CUDA version needs a suitably new driver version, but old CUDA versions are supported by newer driver versions (drivers are backwards-compatible). To figure out up to which CUDA version runs on your installed driver, check out "Table 3" of the [CUDA release notes](https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html). For each driver branch there is a major 11.x.0 release with possible further bugfix releases.
## Manual Operation
@@ -123,7 +123,7 @@ Hint: [d]efault, [e]nabled, [x]disabled, [i]nstalled
```
The first try would be to pick the number of the desired branch. Currently the `520*` and `latest` are empty because the drivers where removed.
The "number only" module streams contain precompiled drivers for some kernels, but for older branches it must not be the latest one. I found the `*-dkms` branches to work better for newer kernels. But I did not manage to do "real" DKMS with them, that means compiling the translation layer of any given driver version for whatever kernel. Feel free to update this guide or to tell the Core Linux Team if you found a working procedure.
The "number only" module streams contain precompiled drivers for some kernels. Note that for older branches or older drivers it may not be precompiled for the latest kernel version. For older branches I had the experience that the `*-dkms` module stream works better for newer kernels. But I did not manage to do "real" DKMS with them, that means compiling the translation layer of any given driver version for whatever kernel. Feel free to update this guide or to tell the Core Linux Team if you found a working procedure.
Finally the `*-open` module streams contain the new open source drivers which currently do not provide the full feature set of the propretiary ones.
@@ -145,7 +145,7 @@ Note that this will also remove installed CUDA packages.
### Install CUDA
It is not recommended to install the `cuda` meta-package directly, because that required the latest drivers from the "new feature" branch. It is better to install the `cuda-11-x` meta-package instead, which installs the CUDA version suitable to your driver and keeps it then updated with bugfix releases to this specific major release.
It is not recommended to install the `cuda` meta-package directly, because that required the latest drivers from the "new feature" branch. It is better to install the `cuda-11-x` meta-package instead, which installs the CUDA version suitable to your driver and keeps it then updated with bugfix releases to this specific major release. Check out the Table 3 in the [CUDA Release Notes](https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html) for details.
The `cuda` meta-package is by default excluded as explained above. If you still want to use it, do
```