The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Zeno Davatz <zdavatz@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: evdev keyboard driver stopped working after upgrading from Kernel  2.6.33-rc8 to 2.6.33 (official release)
Date: Thu, 04 Mar 2010 08:47:03 +0100	[thread overview]
Message-ID: <1267688823.7029.8.camel@marge.simson.net> (raw)
In-Reply-To: <40a4ed591003032322l4ad2dc00sd3de718b5a76089b@mail.gmail.com>

On Thu, 2010-03-04 at 08:22 +0100, Zeno Davatz wrote:
> On Thu, Mar 4, 2010 at 4:33 AM, Mike Galbraith <efault@gmx.de> wrote:
> > On Wed, 2010-03-03 at 21:45 +0100, Zeno Davatz wrote:
> 
> >> I am always updating to the latest rc Kernel Release, that Linus shares via Git.
> >>
> >> I also upgraded to the latest stable kernel version after rc-8, to
> >> 2.6.33. But since I am on 2.6.33 my Xorg evdev-Driver stopped working.
> >> I can hit any key on the keyboard, but nothing will happen. The mouse
> >> and the graphics are just fine and work well.
> >>
> >> I have an Asus Eeepc 1101HA, with Gentoo and the psb-kmod driver compiled.
> >>
> >> Xorg starts just fine, does not crash but the keyboard does not react.
> >>
> >> Everything worked fine on 2.6.33-rc8.
> >>
> >> Any hints what changed from 2.6.33-rc8 to 2.6.33 stable that made my
> >> keyboard stop reacting?
> >>
> >> Let me know and I will test.
> >
> > I don't see any obvious candidates rc8->final.  There's _very_ little
> > for input.
> >
> > On the bright side, there are only 225 commits, so a bisection should be
> > almost painless.  That's probably your best bet for rapid resolution.
> 
> Is there a possibility that something changed between rc2 and final,
> something that would concern the evdev driver or the keyboard input?
> It seems that /dev/input/event5 where the keyboard is found does not
> pass anything on to Xorg.

Dunno about rc2, I looked rc8->final.  Not much there.

> I did not change anything else on my system except upgrading the kernel.

I'd bisect it asap.

	-Mike



  reply	other threads:[~2010-03-04  7:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03 20:45 evdev keyboard driver stopped working after upgrading from Kernel 2.6.33-rc8 to 2.6.33 (official release) Zeno Davatz
     [not found] ` <1267673633.6416.7.camel@marge.simson.net>
2010-03-04  7:22   ` Zeno Davatz
2010-03-04  7:47     ` Mike Galbraith [this message]
2010-03-04  7:55       ` Zeno Davatz
2010-03-04  8:03         ` Mike Galbraith
2010-03-04  8:14           ` Mike Galbraith
2010-03-04  8:18             ` Zeno Davatz
2010-03-04  8:27           ` Zeno Davatz
2010-03-04  8:34           ` Zeno Davatz
     [not found]           ` <40a4ed591003040126t751b9ee5o94c2cd3ce2d5f58b@mail.gmail.com>
2010-03-04  9:28             ` Zeno Davatz
2010-03-04 13:25     ` Måns Rullgård

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=1267688823.7029.8.camel@marge.simson.net \
    --to=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zdavatz@gmail.com \
    /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