linux-kernel - Re: [REGRESSION] "bind" a device to a driver doesn't not work anymore

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 22 Oct 2009 19:48:47 +0200
From:	Éric Piel <Eric.Piel@...mplin-utc.net>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:	Greg KH <gregkh@...e.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>
Subject: Re: [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.

Eric
--
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/