From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev rule not working after kernel upgrade
Date: Thu, 08 Dec 2005 02:24:38 +0000 [thread overview]
Message-ID: <20051208022438.GA4163@vrfy.org> (raw)
In-Reply-To: <1134008028.3067.9.camel@stampede>
On Wed, Dec 07, 2005 at 07:13:48PM -0700, Paul Gaynor wrote:
> Hi,
>
> After upgrading to kernel 2.6.14 my udev rule:
>
> BUS="usb", KERNEL="event[0-3]*", SYSFS{product}="USB TouchController",
> SYMLINK="input/touchscreen"
>
> is no longer working. a rule further down in the rules file is being
> ran instead:
>
> KERNEL="event[0-9]*", NAME="input/%k"
>
> from syslog:
>
> Dec 7 18:43:09 localhost udev[4904]: configured rule in
> '/etc/udev/rules.d/udev.rules[68]' applied, 'event1' becomes
> 'input/%k'
>
> Is there something that i might be missing in the kernel for my rule to
> work?
>
> What else should i look into to get my rule working? I can cat the /sys
> for the "product" and it comes up correct. The rule worked fine on
> kernel 2.6.8. Any advice?
What version of udev is that?
Kay
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-12-08 2:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 2:13 udev rule not working after kernel upgrade Paul Gaynor
2005-12-08 2:24 ` Kay Sievers [this message]
2005-12-08 18:13 ` paul.gaynor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051208022438.GA4163@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).