Archives/nvidia-all
2
0
Fork 0
mirror of https://github.com/Frogging-Family/nvidia-all synced 2024-10-30 15:20:10 +00:00
Code Issues Packages Projects Releases Wiki Activity
246 Commits 1 Branch 0 Tags 602 KiB
Shell 100%
8b65c62c9e
Go to file
gardotd426 8b65c62c9e
Add support for 535.54.03 (#175) 
* Add support for 535.54.03

* Add support for 535.54.03
2023-06-14 23:29:31 +02:00
patches 470.182.03 + 6.3 patch 2023-05-12 23:53:43 +02:00
system Add support for dracut and booster for the hook (#163) 2023-05-04 20:58:17 +02:00
.gitignore Fix src and pkg path in per-submodule .gitignore 2020-03-28 03:35:58 +01:00
60-nvidia.rules Add the udev rules back - d621f9d527 (comments) 2021-10-08 17:08:42 +02:00
customization.cfg 525.85.05 + bit (#144) 2023-01-20 15:30:01 +01:00
PKGBUILD Add support for 535.54.03 (#175) 2023-06-14 23:29:31 +02:00
README.md 520.56.06 2022-10-12 16:11:28 +02:00

README.md

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 :

Mostlyportable-gcc users :