public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: linux-kernel@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: udev on 2.6.14 fails to create /dev/input/event2 on T40 Thinkpad
Date: Sun, 6 Nov 2005 08:55:14 -0500	[thread overview]
Message-ID: <20051106135514.GA8020@thunk.org> (raw)
In-Reply-To: <436DD635.9030103@gmail.com>

On Sun, Nov 06, 2005 at 11:08:53AM +0100, Jiri Slaby wrote:
> 
> >When I upgraded to 2.6.14 from 2.6.14-rc5, my X server failed to stop.  
> >Investigation revealed it was because my CorePointer was the Synaptics
> >driver, and the device corresponding to the Synaptics touchpad
> >(/dev/input/event2 on my laptop) was not being created.  Once I manually
> >created the device with the proper major/minor device numbers, X started
> >correctly.
> >
> >A comparison of "udevinfo -e" on 2.6.14-rc5 and 2.5.14 reveals the
> >following differences.  Was this change deliberate?  And can it be
> >reverted?
> 
> You should also write which version of udev do you use.

Oh, of course.  Version 0.071-1, from Debian unstable.

						- Ted

  reply	other threads:[~2005-11-06 13:55 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 [this message]
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
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=20051106135514.GA8020@thunk.org \
    --to=tytso@mit.edu \
    --cc=jirislaby@gmail.com \
    --cc=kay.sievers@vrfy.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox