From: "Theodore Ts'o" <tytso@mit.edu>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: udev on 2.6.14 fails to create /dev/input/event2 on T40 Thinkpad
Date: Mon, 7 Nov 2005 22:30:19 -0500 [thread overview]
Message-ID: <20051108033019.GA6129@thunk.org> (raw)
In-Reply-To: <20051107182434.GC18861@kroah.com>
On Mon, Nov 07, 2005 at 10:24:34AM -0800, Greg KH wrote:
> > from Debian with a post 2.6.14 kernel, and it wasn't working for me.
>
> I see that 073 is in unstable, which fixed a lot of problems with 071,
> 072 and 073 due to Debian configuration issues. I suggest you try that.
I've just tried udev 073 from Debian unstable, with a freshly pulled
kernel 2.6.14 from earlier in the evening on 11/7. Same failure:
/dev/input only has /dev/input/event3, and is missing the event0, event1,
and event2 files that is present if I boot 2.6.14.
So is this a Debian bug, a kernel bug, or a udev bug? What is going
on? I don't know enough about recent changes to udev and/or the
events sent to udev to start debugging this, but this is something
that works in 2.6.14 and fails post-2.6.14....
So this is what I believe Andrew would call "a regression". :-)
- Ted
next prev parent reply other threads:[~2005-11-08 3:30 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 [this message]
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
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=20051108033019.GA6129@thunk.org \
--to=tytso@mit.edu \
--cc=greg@kroah.com \
--cc=linux-kernel@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 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.