diff options
| author | V3n3RiX <venerix@koprulu.sector> | 2023-05-14 10:33:57 +0100 |
|---|---|---|
| committer | V3n3RiX <venerix@koprulu.sector> | 2023-05-14 10:33:57 +0100 |
| commit | bf434c621ee151cff3a6444443a818244e334029 (patch) | |
| tree | a1f7511444364c22690b4a1580bd57fe18a78512 /sys-kernel/nvidia-drivers-dkms/files/dkms530.patch | |
| parent | 8a9fee0883460449b1dc5e0de3660b1408002de1 (diff) | |
x11-drivers/nvidia-drivers : add SLOT 530 (v530.41.03)
Diffstat (limited to 'sys-kernel/nvidia-drivers-dkms/files/dkms530.patch')
| -rw-r--r-- | sys-kernel/nvidia-drivers-dkms/files/dkms530.patch | 60 |
1 files changed, 60 insertions, 0 deletions
diff --git a/sys-kernel/nvidia-drivers-dkms/files/dkms530.patch b/sys-kernel/nvidia-drivers-dkms/files/dkms530.patch new file mode 100644 index 00000000..8ea36d81 --- /dev/null +++ b/sys-kernel/nvidia-drivers-dkms/files/dkms530.patch @@ -0,0 +1,60 @@ +diff -Nur a/kernel/dkms.conf b/kernel/dkms.conf +--- a/kernel/dkms.conf 2023-03-28 23:02:32.000000000 +0100 ++++ b/kernel/dkms.conf 2023-05-12 18:40:21.194005773 +0100 +@@ -1,12 +1,22 @@ +-PACKAGE_NAME="nvidia" +-PACKAGE_VERSION="__VERSION_STRING" ++PACKAGE_NAME="nvidia-drivers-dkms" ++PACKAGE_VERSION="530.41.03" ++BUILD_EXCLUSIVE_KERNEL="^(5\.[0-9]+\.|6\.[0-3]\.)" # only build for kernels v5.x.x up to and including v6.3.x + 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} IGNORE_CC_MISMATCH='__IGNORE_CC_MISMATCH' 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" ++BUILT_MODULE_NAME[4]="nvidia-peermem" ++DEST_MODULE_LOCATION[4]="/extra/dkms" +diff -Nur a/kernel-open/dkms.conf b/kernel-open/dkms.conf +--- a/kernel-open/dkms.conf 2023-03-28 23:02:32.000000000 +0100 ++++ b/kernel-open/dkms.conf 2023-05-12 18:40:30.254006616 +0100 +@@ -1,12 +1,22 @@ +-PACKAGE_NAME="nvidia" +-PACKAGE_VERSION="__VERSION_STRING" ++PACKAGE_NAME="nvidia-drivers-dkms" ++PACKAGE_VERSION="530.41.03" ++BUILD_EXCLUSIVE_KERNEL="^(5\.[0-9]+\.|6\.[0-3]\.)" # only build for kernels v5.x.x up to and including v6.3.x + 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} IGNORE_CC_MISMATCH='__IGNORE_CC_MISMATCH' 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" ++BUILT_MODULE_NAME[4]="nvidia-peermem" ++DEST_MODULE_LOCATION[4]="/extra/dkms" |