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

update Nvidia driver installation documentation

Browse Source
This commit is contained in:
buchel_k
2023-01-13 08:32:15 +01:00
parent 0229077116
commit ecae0fb214
1 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
rhel8/nvidia.md
+7 -5
View File
@@ -44,11 +44,13 @@ This is not recommended, still it is possible to do so by setting the exact driv
If the driver version is too old, it will install an older kernel version and you will need a second reboot to activate it.
### My hardware is too old
### My hardware is very old
The oldest driver branch packaged by Nvidia for RHEL 8 is `470`. You might just live with the fallback to Nouveau (`nvidia::driver::enable: false` in Hiera) or you might try the drivers packaged by ElRepo: `nvidia::driver::branch: elrepo` (or when you want an specific ElRepo branch: `nvidia::driver::branch: 390xx`).
The oldest driver branch packaged by Nvidia for RHEL 8 is `470`. For hardware only supported by older drivers it falls back to ElRepo packaged drivers. You might do that also on purpose in Hiera by setting `nvidia::driver::branch: elrepo` (or when you want an specific ElRepo branch: `nvidia::driver::branch: 390xx`).
You might also just download and install the Nvidia driver manually.
Or you might just live with the fallback to Nouveau (`nvidia::driver::enable: false` in Hiera).
Alternatively you might also just download and install the Nvidia driver manually.
Go to their [Download page](https://www.nvidia.de/Download/index.aspx), select and download the according installer and run it.
You best keep Puppet off your driver by setting `nvidia::driver::enable: false` in Hiera.
@@ -63,7 +65,7 @@ Their drivers are oranized in driver branches. As you see for example in their [
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.
The drivers within certain branches are maintained quite a long time. Individual drivers in that branch get increasing version numbers which just start with the same first "branch" number.
In the RPM repo there are more branches available than listed in the [Unix Driver Archive](https://www.nvidia.com/en-us/drivers/unix/). It is not possible to find out retrospectively to what type of branch it belongs. My guess is that the "Legacy" section lists only the production/long term support branches.
@@ -71,7 +73,7 @@ Also it is not possible to find out from the package meta information if a drive
### What Driver \[Branch] for which Hardware
The most authorative way to do so is to chech the [Appendix A of the README of a decent driver](http://us.download.nvidia.com/XFree86/Linux-x86_64/525.78.01/README/supportedchips.html).
The most authorative way to do so is to chech the [Appendix A of the README of a recent driver](http://us.download.nvidia.com/XFree86/Linux-x86_64/525.78.01/README/supportedchips.html).
There search for your model or PCI ID. Then check out at the top of the respective table which legacy driver it still supports.
Or it might be the current driver.