summaryrefslogtreecommitdiff
path: root/x11-drivers/nvidia-drivers/files/nvidia.udev-rule
diff options
context:
space:
mode:
authorV3n3RiX <venerix@rogentos.ro>2016-10-23 17:52:44 +0100
committerV3n3RiX <venerix@rogentos.ro>2016-10-23 17:52:44 +0100
commit8b80388f02dce4d33c9d9b1a4f32cc4bf48b0fcc (patch)
tree24047a9bd21bbab2d64e3f325fe44e8ed9bf59d7 /x11-drivers/nvidia-drivers/files/nvidia.udev-rule
parent12c7a26fc7d6e965a67c1787e12f137c64f11c51 (diff)
nvidia-drivers-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}"