summaryrefslogtreecommitdiff
path: root/sys-kernel/nvidia-legacy-drivers-dkms/files/nvidia-legacy-drivers-dkms-390.132-conf.patch
diff options
context:
space:
mode:
Diffstat (limited to 'sys-kernel/nvidia-legacy-drivers-dkms/files/nvidia-legacy-drivers-dkms-390.132-conf.patch')
-rw-r--r--sys-kernel/nvidia-legacy-drivers-dkms/files/nvidia-legacy-drivers-dkms-390.132-conf.patch28
1 files changed, 28 insertions, 0 deletions
diff --git a/sys-kernel/nvidia-legacy-drivers-dkms/files/nvidia-legacy-drivers-dkms-390.132-conf.patch b/sys-kernel/nvidia-legacy-drivers-dkms/files/nvidia-legacy-drivers-dkms-390.132-conf.patch
new file mode 100644
index 00000000..3ba17a8c
--- /dev/null
+++ b/sys-kernel/nvidia-legacy-drivers-dkms/files/nvidia-legacy-drivers-dkms-390.132-conf.patch
@@ -0,0 +1,28 @@
+diff -Nur a/kernel/dkms.conf b/kernel/dkms.conf
+--- a/kernel/dkms.conf 2018-03-22 05:39:53.000000000 +0000
++++ b/kernel/dkms.conf 2018-04-09 16:18:23.177125417 +0100
+@@ -1,12 +1,20 @@
+-PACKAGE_NAME="nvidia"
+-PACKAGE_VERSION="__VERSION_STRING"
++PACKAGE_NAME="nvidia-legacy-drivers-dkms"
++PACKAGE_VERSION="390.132"
+ AUTOINSTALL="yes"
+
+ # By default, DKMS will add KERNELRELEASE to the make command line; however,
+ # this will cause the kernel module build to infer that it was invoked via
+ # Kbuild directly instead of DKMS. The dkms(8) manual page recommends quoting
+ # the 'make' command name to suppress this behavior.
+-MAKE[0]="'make' -j__JOBS NV_EXCLUDE_BUILD_MODULES='__EXCLUDE_MODULES' KERNEL_UNAME=${kernelver} modules"
++MAKE[0]="'make' -j`nproc` NV_EXCLUDE_BUILD_MODULES='__EXCLUDE_MODULES' KERNEL_UNAME=${kernelver} modules"
+
+ # The list of kernel modules will be generated by nvidia-installer at runtime.
+-__DKMS_MODULES
++BUILT_MODULE_NAME[0]="nvidia"
++DEST_MODULE_LOCATION[0]="/extra/dkms"
++BUILT_MODULE_NAME[1]="nvidia-uvm"
++DEST_MODULE_LOCATION[1]="/extra/dkms"
++BUILT_MODULE_NAME[2]="nvidia-modeset"
++DEST_MODULE_LOCATION[2]="/extra/dkms"
++BUILT_MODULE_NAME[3]="nvidia-drm"
++DEST_MODULE_LOCATION[3]="/extra/dkms"
++