evdev keyboard driver stopped working after upgrading from Kernel 2.6.33-rc8 to 2.6.33 (official release)
Zeno Davatz
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.
Best
Zeno
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Zeno Davatz
> 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.
I did not change anything else on my system except upgrading the kernel.
Mike Galbraith
> On Thu, Mar 4, 2010 at 4:33 AM, Mike Galbraith <efa...@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
Zeno Davatz
Ok, I will try that. Can you give a short input of how I should start bisecting?
Thank you for your Feedback.
Best
Zeno
Mike Galbraith
> Ok, I will try that. Can you give a short input of how I should start bisecting?
git bisect start
git bisect good v2.6.33-rc8
git bisect bad v2.6.33
build and test each iteration, should be quick/painless if it's rc8.
-Mike
Zeno Davatz
> On Thu, 2010-03-04 at 09:03 +0100, Mike Galbraith wrote:
>> On Thu, 2010-03-04 at 08:55 +0100, Zeno Davatz wrote:
>>
>> > Ok, I will try that. Can you give a short input of how I should start bisecting?
>>
>> git bisect start
>> git bisect good v2.6.33-rc8
>> git bisect bad v2.6.33
>>
>> build and test each iteration, should be quick/painless if it's rc8.
>
> to go. �You might need to know that, since you've never done a bisection
> before ;-)
Thanks! I will try asap. First I gonna upgrade Git to 1.7.0
Best
Zeno
Mike Galbraith
> On Thu, 2010-03-04 at 08:55 +0100, Zeno Davatz wrote:
>
> > Ok, I will try that. Can you give a short input of how I should start bisecting?
>
> git bisect start
> git bisect good v2.6.33-rc8
> git bisect bad v2.6.33
>
> build and test each iteration, should be quick/painless if it's rc8.
Um, with git bisect good/bad after each test to tell git which direction
to go. You might need to know that, since you've never done a bisection
before ;-)
--
Zeno Davatz
> On Thu, 2010-03-04 at 08:55 +0100, Zeno Davatz wrote:
>
>> Ok, I will try that. Can you give a short input of how I should start bisecting?
>
> git bisect start
> git bisect good v2.6.33-rc8
> git bisect bad v2.6.33
>
> build and test each iteration, should be quick/painless if it's rc8.
So I do:
git bisect start
git bisect good v2.6.33-rc8
make
copy bzImge
lilo
reboot
see if it works
correct?
best
Zeno
Zeno Davatz
> On Thu, 2010-03-04 at 08:55 +0100, Zeno Davatz wrote:
>
>> Ok, I will try that. Can you give a short input of how I should start bisecting?
>
> git bisect start
> git bisect good v2.6.33-rc8
> git bisect bad v2.6.33
>
> build and test each iteration, should be quick/painless if it's rc8.
Ok I think I am getting it. Forget my last mail.
Best
Zeno
Zeno Davatz
> On Thu, 2010-03-04 at 08:55 +0100, Zeno Davatz wrote:
>
>> Ok, I will try that. Can you give a short input of how I should start bisecting?
>
> git bisect start
> git bisect good v2.6.33-rc8
> git bisect bad v2.6.33
>
> build and test each iteration, should be quick/painless if it's rc8.
Ok, confirmed: http://lkml.org/lkml/2010/3/4/33
With -rc8 my keyboard is backup and working!
So it must be a change between rc8 and final 2.6.33
Thank you for your greenhorn git bisect tutorial.
I am curious where the bug is!
Best
Zeno
Måns Rullgård
> On Thu, Mar 4, 2010 at 4:33 AM, Mike Galbraith <efa...@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.
The inputX numbers are not stable. I've had better luck using lines
like this in xorg.conf:
Section "InputDevice"
[...]
Option "Device" "/dev/input/by-id/usb-_USB_Keyboard-event-kbd"
EndSection
This symlink will always point to whatever input device that keyboard
gets assigned to.
--
M�ns Rullg�rd
ma...@mansr.com