Skip to main content
Welcome guest. | Register | Login | Post

Fixing the Dreaded e02a Bug

No replies
supermike's picture
Offline
Joined: 2006-02-17

If you have Ubuntu, you may have the dreaded e02a bug where, when you do tail -f /var/log/messages and begin typing, eventually an error will repeatedly pop out that complains about setkeycodes and a keystroke named e02a.

Unfortunately many people have put the fix on the Ubuntu site, but then some dope keeps moving it, as if being malicious. Therefore, I'm going to tell you the fix here. I've done it and it works.

Allow me to quote "dcstar" from http://ubuntuforums.org, who writes:

Quote:

There are a lot of complaints of copious dmesg output resembling this:

[4314715.415000] atkbd.c: Unknown key pressed (translated set 2, code 0xaa on isa0060/serio0).
[4314715.415000] atkbd.c: Use 'setkeycodes e02a <keycode>' to make it known.

On some machines, this keycode triggers a hibernate event and is therefore disabled. On other machines e02a is an arrow key and this just causes a mess in dmesg. To quiet these error messages, remove the line from /usr/share/hotkey-setup/generic.hk that reads

setkeycodes e02a 256

and run

sudo /etc/init.d/hotkey-setup restart

and your dmesg should stop filling up with these messages.