summaryrefslogtreecommitdiff
path: root/x11-drivers/nvidia-drivers/files/nvidia.udev-rule
diff options
context:
space:
mode:
authorV3n3RiX <venerix@redcorelinux.org>2017-07-01 06:25:42 +0100
committerV3n3RiX <venerix@redcorelinux.org>2017-07-01 06:25:42 +0100
commitb6cfe8d79d9d9b75fef613e47e7ebfbeb3ea0575 (patch)
tree454f2e9b21490dccabcc2079df4faf64fe440a9d /x11-drivers/nvidia-drivers/files/nvidia.udev-rule
parent9cde11187ee3ce44b76343c2d95c018431012d34 (diff)
x11-drivers/nvidia-drivers : insert modprobe && udev rules when using dkms
Diffstat (limited to 'x11-drivers/nvidia-drivers/files/nvidia.udev-rule')
-rw-r--r--x11-drivers/nvidia-drivers/files/nvidia.udev-rule6
1 files changed, 6 insertions, 0 deletions
diff --git a/x11-drivers/nvidia-drivers/files/nvidia.udev-rule b/x11-drivers/nvidia-drivers/files/nvidia.udev-rule
new file mode 100644
index 00000000..2eb30bb0
--- /dev/null
+++ b/x11-drivers/nvidia-drivers/files/nvidia.udev-rule
@@ -0,0 +1,6 @@
+ACTION=="add", DEVPATH=="/module/nvidia", SUBSYSTEM=="module", RUN+="nvidia-udev.sh $env{ACTION}"
+# Previously the ACTION was "add|remove" but one user on bug #376527 had a
+# problem until he recompiled udev-171-r5, which is one of the versions I
+# tested with and it was fine. I'm breaking the rules out just to be safe
+# so someone else doesn't have an issue
+ACTION=="remove", DEVPATH=="/module/nvidia", SUBSYSTEM=="module", RUN+="nvidia-udev.sh $env{ACTION}"