[lkml]   [2009]   [Oct]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [REGRESSION] "bind" a device to a driver doesn't not work anymore
Op 22-10-09 18:22, Dmitry Torokhov schreef:
> On Thu, Oct 22, 2009 at 06:10:52PM +0200, Éric Piel wrote:
>> Op 21-10-09 22:20, Dmitry Torokhov schreef:
>>> Nothing, as far as I can tell... I see you typing "qwerty"... Does the
>>> keyboard work in console (let's say if you boot in run level 3 to take X out
>>> of the picture)? Could you please try compiling evbug module - it will show if
>>> keyboard events are propagated through input core. Also, whta driver are you
>>> using in X? Legacy keyboard or evdev?
>> In the console (in init 3), I haven't managed to reproduce it. In xorg,
>> the keyboard input uses evdev. Now I've just tried "evtest
>> /dev/input/event4", when the keyboard doesn't work... and I see the key
>> presses!
>> So I guess it rules out a bug in the kernel, and I have to talk with the
>> people from Xorg, right?
> Yep... but it is still wierd since evdev driver works fine for me...
> Could it be you are using either too old or too new version of X?
I don't think so: xorg 1.6.5, with xinput-evdev 2.2.5. They are both
latest or second latest stable versions.

In the log I see this:
(--) SynPS/2 Synaptics TouchPad: touchpad found
(II) PS/2 Generic Mouse: Device reopened after 1 attempts.
(EE) AT Translated Set 2 keyboard: device key_bitmask has changed
(EE) AT Translated Set 2 keyboard: Device has changed - disabling.

Quite a few people seem to have the same problem.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2009-10-22 19:51    [W:0.064 / U:57.772 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site