From: Dmitry Torokhov <dmitry.torokhov@gmail.com> To: "Éric Piel" <Eric.Piel@tremplin-utc.net> Cc: Greg KH <gregkh@suse.de>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, "linux-input@vger.kernel.org" <linux-input@vger.kernel.org> Subject: Re: [REGRESSION] "bind" a device to a driver doesn't not work anymore Date: Thu, 22 Oct 2009 11:32:50 -0700 [thread overview] Message-ID: <20091022183249.GC18031@core.coreip.homeip.net> (raw) In-Reply-To: <20091022181915.GB18031@core.coreip.homeip.net> On Thu, Oct 22, 2009 at 11:19:15AM -0700, Dmitry Torokhov wrote: > On Thu, Oct 22, 2009 at 07:48:47PM +0200, Éric Piel wrote: > > 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. > > Same here... > > 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. > > The bitmask should not be changing on it's own... Any chance you could > save contents or /proc/bus/input/devices before suspend and after resume > (when X decides to ditch the keyboard) and diff them? > Also, are you using 64 bit userspace? -- Dmitry
WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Torokhov <dmitry.torokhov@gmail.com> To: "Éric Piel" <Eric.Piel@tremplin-utc.net> Cc: Greg KH <gregkh@suse.de>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, "linux-input@vger.kernel.org" <linux-input@vger.kernel.org> Subject: Re: [REGRESSION] "bind" a device to a driver doesn't not work anymore Date: Thu, 22 Oct 2009 11:32:50 -0700 [thread overview] Message-ID: <20091022183249.GC18031@core.coreip.homeip.net> (raw) In-Reply-To: <20091022181915.GB18031@core.coreip.homeip.net> On Thu, Oct 22, 2009 at 11:19:15AM -0700, Dmitry Torokhov wrote: > On Thu, Oct 22, 2009 at 07:48:47PM +0200, Éric Piel wrote: > > 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. > > Same here... > > 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. > > The bitmask should not be changing on it's own... Any chance you could > save contents or /proc/bus/input/devices before suspend and after resume > (when X decides to ditch the keyboard) and diff them? > Also, are you using 64 bit userspace? -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-10-22 18:32 UTC|newest] Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-10-14 2:05 [REGRESSION] "bind" a device to a driver doesn't not work anymore Dmitry Torokhov 2009-10-14 2:05 ` Dmitry Torokhov 2009-10-15 17:24 ` Éric Piel 2009-10-15 18:13 ` Dmitry Torokhov 2009-10-15 18:13 ` Dmitry Torokhov 2009-10-15 18:27 ` Dmitry Torokhov 2009-10-15 18:27 ` Dmitry Torokhov 2009-10-15 19:32 ` Éric Piel 2009-10-15 19:51 ` Dmitry Torokhov 2009-10-15 19:51 ` Dmitry Torokhov 2009-10-15 21:33 ` Éric Piel 2009-10-15 21:59 ` Dmitry Torokhov 2009-10-15 21:59 ` Dmitry Torokhov 2009-10-15 22:44 ` Éric Piel 2009-10-21 19:34 ` Éric Piel 2009-10-21 20:20 ` Dmitry Torokhov 2009-10-21 20:20 ` Dmitry Torokhov 2009-10-22 16:10 ` Éric Piel 2009-10-22 16:22 ` Dmitry Torokhov 2009-10-22 16:22 ` Dmitry Torokhov 2009-10-22 17:48 ` Éric Piel 2009-10-22 17:48 ` Éric Piel 2009-10-22 18:19 ` Dmitry Torokhov 2009-10-22 18:19 ` Dmitry Torokhov 2009-10-22 18:32 ` Dmitry Torokhov [this message] 2009-10-22 18:32 ` Dmitry Torokhov 2009-10-23 8:08 ` Éric Piel 2009-10-23 8:58 ` Dmitry Torokhov 2009-10-23 8:58 ` Dmitry Torokhov 2009-10-23 9:21 ` Éric Piel 2009-10-23 9:21 ` Éric Piel 2009-10-23 16:31 ` Dmitry Torokhov 2009-10-23 16:31 ` Dmitry Torokhov 2009-10-25 11:47 ` Éric Piel 2009-10-25 19:07 ` Dmitry Torokhov 2009-10-25 19:07 ` Dmitry Torokhov -- strict thread matches above, loose matches on Subject: below -- 2009-10-11 0:04 Éric Piel 2009-10-11 3:00 ` Greg KH 2009-10-12 4:35 ` Dmitry Torokhov 2009-10-12 11:46 ` Éric Piel 2009-10-12 14:44 ` Greg KH 2009-10-12 14:44 ` Greg KH 2009-10-12 15:45 ` Dmitry Torokhov 2009-10-12 15:45 ` Dmitry Torokhov 2009-10-12 17:37 ` Greg KH 2009-10-12 17:37 ` Greg KH 2009-10-12 15:48 ` Dmitry Torokhov 2009-10-12 16:48 ` Éric Piel 2009-10-12 16:48 ` Éric Piel 2009-10-12 17:35 ` Greg KH 2009-10-12 18:33 ` Dmitry Torokhov 2009-10-12 18:54 ` Greg KH 2009-10-12 19:20 ` Dmitry Torokhov 2009-10-12 19:58 ` Greg KH 2009-10-13 3:17 ` Dmitry Torokhov 2009-10-18 7:51 ` Dmitry Torokhov 2009-10-18 8:02 ` Greg KH 2009-10-23 2:01 ` Dmitry Torokhov 2009-10-26 20:59 ` Greg KH 2009-10-26 21:34 ` Dmitry Torokhov 2009-10-26 23:59 ` Greg KH 2009-10-27 16:16 ` Dmitry Torokhov 2009-10-13 9:52 ` Éric Piel
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=20091022183249.GC18031@core.coreip.homeip.net \ --to=dmitry.torokhov@gmail.com \ --cc=Eric.Piel@tremplin-utc.net \ --cc=gregkh@suse.de \ --cc=linux-input@vger.kernel.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.