From: Greg KH <greg@kroah.com>
To: "Marco d'Itri" <md@Linux.IT>
Cc: "Theodore Ts'o" <tytso@mit.edu>, linux-kernel@vger.kernel.org
Subject: Re: udev on 2.6.14 fails to create /dev/input/event2 on T40 Thinkpad
Date: Tue, 8 Nov 2005 13:56:41 -0800 [thread overview]
Message-ID: <20051108215641.GA19289@kroah.com> (raw)
In-Reply-To: <20051108215209.GA24796@wonderland.linux.it>
On Tue, Nov 08, 2005 at 10:52:09PM +0100, Marco d'Itri wrote:
> On Nov 08, Theodore Ts'o <tytso@mit.edu> wrote:
>
> > .. and the Synaptics driver wants to talk to /dev/input/event2, and
> > _not_ /dev/input/event3. But the Debian scripts seem to think that
> > the only thing of value to expose is the /dev/input/event3, the very
> > top of the stack. /dev/input/event1, and /dev/input/event2 are both
> > not showing up on my system once a I boot a post-2.6.14 kernel.
> Yes, sure. The current Debian package uses udevsynthesize, which knows
> nothing about what happened post-2.6.14 in sysfs.
Ugh, you don't use 'udevstart'? Oh well...
Ted, this is a distro issue, not a kernel one. Marco, you are going to
get a lot of error reports about this once 2.6.15-rc1 is out...
Good luck,
greg k-h
next prev parent reply other threads:[~2005-11-08 21:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-06 5:47 udev on 2.6.14 fails to create /dev/input/event2 on T40 Thinkpad Theodore Ts'o
2005-11-06 10:08 ` Jiri Slaby
2005-11-06 13:55 ` Theodore Ts'o
2005-11-06 15:03 ` Kay Sievers
2005-11-06 20:34 ` Greg KH
2005-11-07 5:36 ` Theodore Ts'o
2005-11-07 15:52 ` Greg KH
2005-11-07 18:17 ` Theodore Ts'o
2005-11-07 18:24 ` Greg KH
2005-11-08 3:30 ` Theodore Ts'o
2005-11-08 4:43 ` Greg KH
2005-11-08 13:14 ` Theodore Ts'o
2005-11-08 18:34 ` Greg KH
2005-11-08 21:52 ` Marco d'Itri
2005-11-08 21:56 ` Greg KH [this message]
2005-11-08 23:09 ` maximilian attems
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=20051108215641.GA19289@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=md@Linux.IT \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.