mirror of
https://github.com/systemd/systemd.git
synced 2024-11-05 15:21:37 +03:00
f7c5b04f69
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.
14 lines
647 B
Plaintext
14 lines
647 B
Plaintext
# do not edit this file, it will be overwritten on update
|
|
|
|
ACTION!="add", GOTO="drivers_end"
|
|
|
|
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"
|
|
SUBSYSTEM=="i2o", RUN+="/sbin/modprobe -b i2o_block"
|
|
SUBSYSTEM=="scsi", ENV{DEVTYPE}=="scsi_device", TEST!="[module/sg]", RUN+="/sbin/modprobe -b sg"
|
|
SUBSYSTEM=="module", KERNEL=="parport_pc", RUN+="/sbin/modprobe -b ppdev"
|
|
|
|
LABEL="drivers_end"
|