From f7c5b04f69e004912327f082be8645b65bb1ff5d Mon Sep 17 00:00:00 2001 From: Kay Sievers Date: Thu, 6 Aug 2009 16:16:26 +0200 Subject: re-enable failed event tracking It did not work for the last couple of releases. If RUN{record_failed}+="..." is given, a non-zero execution will mark the event as failed. Recorded failed events can be re-triggered with: udevadm trigger --type=failed The failed tracking _might_ be useful for things which might not be ready to be executed at early bootup, but a bit later when the needed dependencies are available. In many cases though, it indicates that something is used in a way it should not. --- rules/rules.d/80-drivers.rules | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'rules/rules.d/80-drivers.rules') diff --git a/rules/rules.d/80-drivers.rules b/rules/rules.d/80-drivers.rules index 63409cc01f..d0485e13c4 100644 --- a/rules/rules.d/80-drivers.rules +++ b/rules/rules.d/80-drivers.rules @@ -2,7 +2,7 @@ ACTION!="add", GOTO="drivers_end" -DRIVER!="?*", ENV{MODALIAS}=="?*", RUN{ignore_error}+="/sbin/modprobe -b $env{MODALIAS}" +DRIVER!="?*", ENV{MODALIAS}=="?*", RUN+="/sbin/modprobe -b $env{MODALIAS}" SUBSYSTEM=="tifm", ENV{TIFM_CARD_TYPE}=="SD", RUN+="/sbin/modprobe -b tifm_sd" SUBSYSTEM=="tifm", ENV{TIFM_CARD_TYPE}=="MS", RUN+="/sbin/modprobe -b tifm_ms" SUBSYSTEM=="memstick", RUN+="/sbin/modprobe -b --all ms_block mspro_block" -- cgit v1.2.3-54-g00ecf