Subject : regression since 2.6.36: backlight in sony-laptop not working
Submitter : Norbert Preining <email@example.com>
Date : 2010-11-04 14:29
Message-ID : 20101104142915.GC7650@gamma.logic.tuwien.ac.at
References : http://marc.info/?l=linux-kernel&m=128888097600601&w=2
This entry is being used for tracking a regression from 2.6.36. Please don't
close it until the problem is fixed in the mainline.
According to the thread, it looks like
input broke some sort of compatibility w/ user-space.
re-categorizing to drivers/input.
From: Mattia Dongili <malattia () linux ! it>
You will need an updated input-kbd to set the scancode map.
> > $ diff -u <(sudo input-kbd 5) vaio-kbd
> > /dev/input/event5
> > bustype : BUS_ISA
> > vendor : 0x104d
> > product : 0x0
> > version : 0
> > name : "Sony Vaio Keys"
> > bits ev : EV_SYN EV_KEY EV_MSC
> root$ input-kbd 8
> protocol version mismatch (expected 65536, got 65537)
> and the same for all event devices??
> I have input-kbd from xserver-xorg-input-kbd in Debian/sid, which is
> at 1:1.4.0-2 version.
> Does that mean that 2.6.37rc is too new for the user space?
Maybe. Anyway if evtest reacts positively to key presses then it's a
userspace issue and not the driver's.
Yup, I confirm that 2.6.36 still works as expected with the very same user space (up2date debian/sid), while 2.6.37-rc1 does not work.
We up-revved the protocol number for evdev to reflect support of large scan codes. If utilities wish to check protocol numbers they should check if the protocol "at least N", not "exactly N".
This is problem with this particular utility and bug should be filed there. BTW, why don't they use udev's facilities to remap keys?
*** Bug 23022 has been marked as a duplicate of this bug. ***
I read the thread above and Norbert reports that
"acpi_listen does not issue anything when these keys are pressed"
However, for me acpi_listen issues normal output as I posted in the duped bug report:
(Ubuntu 10.10, Linux 2.6.37-rc1)
Created attachment 37442 [details]
Fix typo in keycode validation
This patch fixes the issue for me.
thanks, that patch also fixed the issue for me, great.
So at the end it was a bug, puuuhhhhh.... ;-)
Oh well ;)
Handled-By : Mattia Dongili <firstname.lastname@example.org>
Patch : https://bugzilla.kernel.org/attachment.cgi?id=37442
Fixed here too, thanks.
Tested mainline with patch committed to it.
Fixed by commit de391d12500ede13faa7ecadbe900a8de1f76cfa .