[Bug 338182] Re: Samsung P560 brightness keys block keyboard and produce all-or-nothing effect
papukaija
338182 at bugs.launchpad.net
Tue May 31 19:59:59 UTC 2011
Just to clarify, is this bug is fixed in Maverick or newer?
** Tags added: patch
** Tags removed: p560 samsung
** Changed in: udev (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to udev in Ubuntu.
https://bugs.launchpad.net/bugs/338182
Title:
Samsung P560 brightness keys block keyboard and produce all-or-nothing
effect
Status in “linux” package in Ubuntu:
Invalid
Status in “udev” package in Ubuntu:
Incomplete
Bug description:
This bug seems to be a duplicate of
https://bugs.launchpad.net/linux/+bug/295251 except that I have a
different Model.
The following FN keys produce these messages in dmesg:
atkbd.c: Unknown key pressed (translated set 2, code 0xb3 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e033 <keycode>' to make it known.
Battery, Videomode, Toggle Backlight, Fn+F7,Fn+F8, Toggle Wlan,
Brightness up, Brightness down
If I set them to the corresponding function using setkeycodes (as
proposed by atkbd.c) the keys work but the keyboard gets stuck, it
seems to think that the Fn key is still pressed. Restarting X lets me
type again.
The patch from http://bugzilla.kernel.org/show_bug.cgi?id=12021 works
if I modify it to suit my keycodes. I have attached my modified patch.
The original patch is only for the NC10.
More information about the foundations-bugs
mailing list