From: Kay Sievers <kay.sievers@vrfy.org>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: udev on 2.6.14 fails to create /dev/input/event2 on T40 Thinkpad
Date: Sun, 6 Nov 2005 16:03:59 +0100 [thread overview]
Message-ID: <20051106150359.GA9509@vrfy.org> (raw)
In-Reply-To: <E1EYdMs-0001hI-3F@think.thunk.org>
On Sun, Nov 06, 2005 at 12:47:02AM -0500, Theodore Ts'o 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?
>
> --- udevinfo-2.6.14-rc5 2005-11-06 00:17:06.000000000 -0500
> +++ udevinfo-2.6.14 2005-11-06 00:22:42.000000000 -0500
> @@ -86,27 +86,15 @@
> P: /class/cpuid/cpu0
> N: cpu/0/cpuid
>
> -P: /class/input/event0
> -N: input/event0
> -
> -P: /class/input/event1
> -N: input/event1
> -
> -P: /class/input/event2
> -N: input/event2
> -
> -P: /class/input/event3
> +P: /class/input/input3/event3
> N: input/event3
>
> +P: /class/input/input3/mouse1
> +N: input/mouse1
> +
> P: /class/input/mice
> N: input/mice
>
> -P: /class/input/mouse0
> -N: input/mouse0
> -
> -P: /class/input/mouse1
> -N: input/mouse1
> -
> P: /class/misc/device-mapper
> N: mapper/control
The change in the path in udevinfo is correct with that kernel, but it
seems, that you miss some devices.
What does:
find /sys/class/input
print?
What does:
ls -l /dev/input
print?
Are the same modules loaded after bootup?
If the devices show up in /sys/class/input, but not in /dev/input,
does running:
/sbin/udevstart
create them?
Thanks,
Kay
next prev parent reply other threads:[~2005-11-06 15:04 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 [this message]
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=20051106150359.GA9509@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox