You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
42 lines
3.0 KiB
Markdown
42 lines
3.0 KiB
Markdown
# Nvidia driver latest to 396 series AIO installer
|
|
|
|
LIBGLVND compatible, with 32 bit libs and DKMS enabled out of the box (you will still be asked if you want to use the regular package). Installs for all currently installed kernels. Comes with custom patches to enhance kernel compatibility, dynamically applied when you're requesting a driver that's not compatible OOTB with your currently installed kernel(s).
|
|
Unwanted packages can be disabled with switches in the PKGBUILD. Defaults to complete installation.
|
|
|
|
Huge thanks to Isaak I. Aleksandrov who has been much faster at offering compat patches than myself for a good while now! https://gitlab.com/EULA
|
|
|
|
You may need/want to add a pacman hook for nvidia depending on your setup : https://wiki.archlinux.org/index.php/NVIDIA#DRM_kernel_mode_setting
|
|
|
|
Vulkan dev drivers : https://developer.nvidia.com/vulkan-driver
|
|
|
|
Regular drivers : https://www.nvidia.com/object/unix.html
|
|
|
|
## How to run the installer
|
|
```
|
|
git clone https://github.com/Frogging-Family/nvidia-all.git
|
|
cd nvidia-all
|
|
makepkg -si
|
|
```
|
|
Then follow the prompts.
|
|
|
|
# DKMS or regular?
|
|
DKMS is recommended as it allows for automatic module rebuilding on kernel updates. As long as you're on the same major version (5.8.x for example), you won't need to regenerate the packages on updates, which is a huge QoL feature. Regular modules can also be problematic on Manjaro due to differences in kernel hooking mechanisms compared to Arch. So if in doubt, go DKMS.
|
|
|
|
|
|
## My DKMS driver installed with kernel X.1 doesn't work/build anymore after I upgraded to kernel X.2! Help!
|
|
- Simply rebuild the packages so the script can detect your currently installed kernel(s) and patch your driver accordingly to fix compatibility issues.
|
|
|
|
# How to generate a package for a driver that isn't listed (390 and lower branches are not supported) :
|
|
- When you are prompted for driver version, select "custom" (choice 8).
|
|
- You'll then be asked the branch group. Select either "Vulkan dev" (choice 2) for Vulkan dev drivers or "stable or regular beta" (choice 1) for every other driver.
|
|
- Now you have to enter the version number of the desired driver. Vulkan dev drivers version is usually formatted as `mainbranch.version.subversion` (i.e.: 415.22.01) while the stable or regular beta drivers version is usually `mainbranch.version` (i.e.: 415.25)
|
|
- To finish, you'll be asked if you want dkms(recommended) or regular modules, similarly to the usual drivers versions.
|
|
|
|
# Optimus users :
|
|
- A great tool exists for you and works with these nvidia-all packages: https://github.com/Askannz/optimus-manager
|
|
- 435.17 beta has introduced PRIME render offload support. You can learn more about the needed setup here: http://us.download.nvidia.com/XFree86/Linux-x86_64/435.17/README/primerenderoffload.html
|
|
|
|
# Mostlyportable-gcc users :
|
|
- For non-dkms nvidia-all packages, setting your `CUSTOM_GCC_PATH` in .cfg is enough.
|
|
- For dkms nvidia-all packages, you'll need to make DKMS aware of your mostlyportable-gcc build. See: https://github.com/Tk-Glitch/PKGBUILDS/issues/334#issuecomment-537197636
|