Michael Klinosky wrote:
> Mikkel:
>> Modified, or added a local rule set. (Or had an extra rule set
>> left from an upgrade...)
>
> Also, I probably didn't add a rule set (not manually, at least).
>
> Btw, I noticed another file: /etc/udev/rules.d/51-hotplug.rules
>
> # do not call hotplug.d and dev.d for "drivers" and "module" events
> SUBSYSTEM=="drivers", GOTO="hotplug_end"
> SUBSYSTEM=="module", GOTO="hotplug_end"
> ACTION=="add", GOTO="hotplug_comp"
> ACTION=="remove", GOTO="hotplug_comp"
>
> GOTO="hotplug_end"
>
> LABEL="hotplug_comp"
> # compatibility support for the obsolete hotplug.d and dev.d directories
> ENV{UDEVD_EVENT}=="1", RUN+="/lib/udev/udev_run_hotplugd"
> RUN+="/lib/udev/udev_run_devd"
>
>
> LABEL="hotplug_end"
>
Part of the standard udev package. But the hotplug rules don't
appear to do much. (You have to have UDEVD_EVENT set to 1 before
/lib/udev/udev_run_hotplugd is run, but it doesn't appear to get set
anywhere...)
You don't have to keep posting the rules - I know about most of
them. When I get some time, I will go over your udev log better, and
try to figure out why it is processing your reader as if it were two
devices. (Analyzing udev logs can make your head spin...)
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
