[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20091024210540.GA15297@core.coreip.homeip.net>
Date: Sat, 24 Oct 2009 14:05:40 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Harald Dunkel <harald.dunkel@...nline.de>
Cc: Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.31.5: /dev/input/event? are gone sometimes
Hi Harald,
On Sat, Oct 24, 2009 at 04:01:12PM +0200, Harald Dunkel wrote:
> Hi folks,
>
> Sometimes (by chance, as it seems) the /dev/input/event? devices
> are not working after power-on or reboot. They are not listed in
> /proc/bus/input/devices. The mouse in X is not moving, keyboard
> is dead, etc. All I can do is reboot and hope.
>
> Below you can find the diff of /proc/bus/input/devices between
> a bad and a good start.
>
>
> udev is 146-5 (included with Debian Sid).
>
>
> Any helpful hints would be highly appreciated. Of course I can
> send you the .config, if there is some interest.
>
>
> Regards
>
> Harri
> ===================================================================
> % diff -u devices.bad devices.good
> --- devices.bad 2009-10-24 15:08:24.000000000 +0200
> +++ devices.good 2009-10-24 15:17:17.000000000 +0200
> @@ -3,7 +3,7 @@
> P: Phys=isa0060/serio0/input0
> S: Sysfs=/devices/platform/i8042/serio0/input/input0
> U: Uniq=
> -H: Handlers=kbd
> +H: Handlers=kbd event0
Since evdev binds to -every_ input device registered its absence in the
handlers list suggests that the module is not loaded. I am not sure how
and when your distribution loads evdev; try making it built-in to avoid
cases when it is not loaded for one reason or another.
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists