Lenovo Z370 pressing OneKey Event blocks keyboard

**katastrophenschutzplan** · October 6th, 2011

Hello,

on the Lenovo Z370 on the right side above the keyboard there are five keys. I think the are called OneKey Events.
If I press one of the 3 left keys, they do what the should (sound up, down, mute).
When pressing the 2 other ones nothing seems to happen.

But no matter which one I press afterwards the hole keyboard does not work anymore. Also the indicator-applet(?) lost its menus.

In the kern.log I found this:

Code:

kbd_keycode: 15 callbacks suppressed
keyboard: can't emulate rawmode for keycode 240
keyboard: can't emulate rawmode for keycode 240
keyboard: can't emulate rawmode for keycode 240
...

I do not know, if those two things are related.

And in the file /usr/include/linux/input.h I found this line:

Code:

#define KEY_UNKNOWN             240

Maybe changing KEY_UNKNOWN would help, but I don not know what to write instead..

I am using Ubuntu 11.04 with Unity 3D.

Code:

uname -a
Linux c-Z370 2.6.38-11-generic #50-Ubuntu SMP Mon Sep 12 21:17:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

Any ideas, how I can prevent the blocking?
If there is anything you need to know, please let me know.

Thank you very much

**senkovych** · December 21st, 2011

Look here: http://blog.nexusger.de/?p=36

**katastrophenschutzplan** · December 22nd, 2011

Hello senkovych

Originally Posted by senkovych

Look here: http://blog.nexusger.de/?p=36

Thank you very much! I will try that as soon as possible (that would be in about one and a half week).

Have a nice day

**phooky** · January 29th, 2012

This particular problem has been driving me nuts for a while, because just *brushing* the capacitive buttons can disable your keyboard. I just found a fix this afternoon. Add the following line to your /lib/udev/rules.d/95-keyboard-force-release.rules file:

Code:

ENV{DMI_VENDOR}=="LENOVO", ATTR{[dmi/id]product_name}=="IdeaPad Z370", RUN+="keyboard-force-release.sh $devpath common-volume-keys"

Additionally, if you accidentally lock up your keyboard this way, you can restore it by switching to a virtual terminal and then switching back to X (try Ctrl-Alt-F2 followed by Alt-F7).