From: "Frédéric L. W. Meunier" <fredlwm@gmail.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: keyboard under X with 2.6.31
Date: Thu, 8 Oct 2009 23:55:19 -0300 (BRST) [thread overview]
Message-ID: <alpine.LNX.2.01.0910082347470.23080@dyndns.pervalidus.net> (raw)
In-Reply-To: <20091009023844.GA26462@core.coreip.homeip.net>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1084 bytes --]
On Thu, 8 Oct 2009, Dmitry Torokhov wrote:
> On Wed, Oct 07, 2009 at 05:19:25PM -0300, Frédéric L. W. Meunier wrote:
>> My keyboard (ABNT2 PS/2) seems to be broken under X with 2.6.31.2. After
>> less than an hour, it starts acting crazy. The first time, all leds
>> turned off and I couldn't type anything. The second time, all leds also
>> turned off, but since it happened while I was pressing the Backspace key
>> to delete text, it continued deleting, like if the key was pressed.
>>
>> In both cases, the mouse (USB) still works and I can exit X, where the
>> keyboard works. There's nothing in the logs.
>>
>> No problem with 2.6.30.9. Is it supposed to be a kernel or X bug ?
>
> It would be interestig to see if the same keyboard continues to work in
> console... if it does then I'd blame X.
I can exit X with the mouse and do anything in the console after
that.
I just reported it to the XOrg mailing-list.
Anyway, I wonder if DRI could mess with the keyboard. I suppose
there were changes (and Radeon related) from 2.6.30 to 2.6.31.
But I can test with it disabled.
next prev parent reply other threads:[~2009-10-09 2:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 20:19 Frédéric L. W. Meunier
2009-10-09 2:38 ` Dmitry Torokhov
2009-10-09 2:55 ` Frédéric L. W. Meunier [this message]
2009-10-09 3:19 ` Justin P. Mattock
2009-10-10 20:18 Boyan
2009-10-11 1:00 ` Ed Tomlinson
2009-10-11 6:34 Boyan
2009-10-11 20:39 ` Frédéric L. W. Meunier
2009-10-12 19:05 ` Marcin Slusarz
2009-10-15 18:31 ` Greg KH
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=alpine.LNX.2.01.0910082347470.23080@dyndns.pervalidus.net \
--to=fredlwm@gmail.com \
--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: 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
all inboxes | Powered by JetHome®