I am posting this message just to say that this bug is being addressed-
on the bug tracker:
http://bugzilla.kernel.org/show_bug.cgi?id=9147
Regards,
--
Daniele C.
legolas558@xxxxxxxxxxxxxxxxxxxxx ha scritto:
legolas558@xxxxxxxxxxxxxxxxxxxxx ha scritto:
Kernel: 2.6.22-r5I am now using kernel 2.6.22-r8 (Gentoo) and the following kernel options:
Kernel option: i8042.nomux=1
i8042.nomux=1 acpi=off
I have tried kernel 2.6.23-rc9 but the problem is still there.
The problem which still remains, and I can't fix or work it around, isWith acpi=off the problem is totally worked around.
witnessed by the below dmesg lines:
-----
atkbd.c: Unknown key released (translated set 2, code 0xe0 on
isa0060/serio0).
atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0xe0 on
isa0060/serio0).
atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0xe0 on
isa0060/serio0).
atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
-----
The release event for some keys is never caught, so all sorts of
troubles happen if for example I use the Del key and it stucks, or if
I use the Ctrl key and it never gets released...pushing again the
stuck key brings back the key in the proper status.
Can somebody please give me some clues about this issue, and possibleI am trying to find a path myself in this issue - which dates back to at
solutions? I have been searching the web for a couple of weeks and
seems like it is a common trouble of notebook users, but nobody has
yet published a solution.
least 2005 and has never been resolved.
I would now try some other kernel parameter in order to preserve ACPI
functionality and possibly prevent ACPI from messing up the keyboard IRQs.
Can somebody please give me istructions regarding the correct tests
(regarding kernel parameters and/or anything else) to perform in order
to better isolate the issue?
Related Gentoo bug tracker item:
http://bugs.gentoo.org/show_bug.cgi?id=194781
Other messages about the same kernel bug (many more can be found
googling around, and no solution yet):
https://lists.linux-foundation.org/pipermail/bugme-new/2005-January/011736.html
http://dev.laptop.org/ticket/2401
Regards,
--
Daniele C.