On Apr 29, Tzafrir Cohen <[EMAIL PROTECTED]> wrote:

> So regarding the original problem: either have the udev RUN command pass 
> the vendor/product IDS explicitly or figure them out somehow. The script 
> should not assume it has PRODUCT and ACTION set. (right? I'm not so 
> familiar with udev).
Wrong. The events for USB devices on my system have $PRODUCT set, and
you can verify this by enabling logging in hotplug.rules.
Probably recent versions of udev call the script for multiple events,
and the script is not working for some other reason (which you verified
by manually setting $PRODUCT) while the error message you are seeing is
harmless.
I do not own any device supported by this driver, so I suggest that you
start by investigating the real reason for the script failure.

-- 
ciao,
Marco

Attachment: signature.asc
Description: Digital signature

Reply via email to