c6d4a58
--- pcmciautils-014/udev/rules-base.newrules	2006-06-19 09:12:29.000000000 +0200
c6d4a58
+++ pcmciautils-014/udev/rules-base	2006-06-19 09:12:58.000000000 +0200
c6d4a58
@@ -3,12 +3,12 @@
70a1963
 # are so broken that we need to read out random bytes of it
70a1963
 # instead of the manufactor, card or product ID. Then the
70a1963
 # matching is done in userspace.
70a1963
-ACTION=="add", SUBSYSTEM=="pcmcia", MODALIAS=="?*", \
70a1963
+ACTION=="add", SUBSYSTEM=="pcmcia", ENV{MODALIAS}=="?*", \
70a1963
 		RUN+="/sbin/pcmcia-check-broken-cis"
70a1963
 
70a1963
 # However, the "weak" matching by func_id is only allowed _after_ modprobe
70a1963
 # returns, so that "strong" matches have a higher priority.
70a1963
-ACTION=="add", SUBSYSTEM=="pcmcia", MODALIAS=="?*", \
70a1963
+ACTION=="add", SUBSYSTEM=="pcmcia", ENV{MODALIAS}=="?*", \
70a1963
 		RUN+="/bin/sh -c 'echo 1 > /sys/$devpath/allow_func_id_match'"
70a1963
 
70a1963
 # PCMCIA sockets:
c6d4a58
--- pcmciautils-014/udev/rules-modprobe.newrules	2006-06-19 09:12:38.000000000 +0200
c6d4a58
+++ pcmciautils-014/udev/rules-modprobe	2006-06-19 09:13:12.000000000 +0200
c6d4a58
@@ -1,3 +1,3 @@
c6d4a58
 # modprobe $modalias loads all possibly appropriate modules
c6d4a58
-ACTION=="add", SUBSYSTEM=="pcmcia", MODALIAS=="?*", \
c6d4a58
+ACTION=="add", SUBSYSTEM=="pcmcia", ENV{MODALIAS}=="?*", \
c6d4a58
 		RUN+="/sbin/modprobe $modalias"