Problem with reload keymap on resume after suspend to ram.

Hello to all!,

I have a problem with the keyboard map when resume the system.

The case it’s the next:

Suspend the system to RAM (before, the keymap is normal, the functions keys operate fine).
When resume of the RAM (the keymap is broken, the all functions keys don’t operating correctly)

Mi device is a Lenovo TinkPad X121e with the LatinAmerican keyboard.

I reviewed the Fn key, and this is before the suspension (reviewed with the xev command):

KeyRelease event, serial 34, synthetic NO, window 0x3e00001,
root 0xaf, subw 0x0, time 330326, (173,-9), root,309),
state 0x0, keycode 151 (keysym 0x1008ff2b, XF86WakeUp), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

this is after the suspension (reviewed with the xev command):

KeymapNotify event, serial 31, synthetic NO, window 0x0,
keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

This same problem occurred with the other funcions keys (Raise Volume, Low Volume, etc)

I review a dump of key after and before and only i see 3 diferences.

diff teclasAntesSuspension.txt teclasDespuesSuspension.txt 44c44
< keycode  13 =
> keycode  13 = questiondown     exclamdown      
< keycode  39 =
> keycode  39 = ntilde           Ntilde          
< keycode  41 = bar             
> keycode  41 = bar              masculine        notsign        

but, i don’t see the keycode for the Fn key.

review the services but the kbd’s don’t operate.

lenovoSLES:/etc # /etc/init.d/kbd statusredirecting to systemctl
          Loaded: masked (/dev/null)
          Active: inactive (dead)

Warning: Unit file changed on disk, 'systemctl --system daemon-reload' recommended.

lenovoSLES:/home/morfeokmg # /etc/init.d/kbd start
redirecting to systemctl
Failed to issue method call: Unit kbd.service is masked.

Will have other method for restore the keymap???

Thanks and greetings!.

some comment??. some idea?, please help me!.

don’t have an expert here???

> some comment??. some idea?, please help me!.
> don’t have an expert here???

i’m not an expert (on anything) but i do know (from reading around in
these forums) that lots of different machines act strangely when coming
out of suspend…

and the “strangely” can appear in many ways: not waking up at all; wake
up but have just a black screen; wake up but the mouse doesn’t work;
wake up but wireless does not work; and on and on and on…here are a
few things you can try:

  1. give the helpers here the minimun information needed to try to help
    you, like: operating system and version, desktop environment and
    version, hardware graphics set and driver in use

[NOTE: read the caveat in my sig before proceeding]

  1. this is probably some kind of driver problem…check with Lenovo and
    make sure you have the Linux drivers they provide for this hardware

  2. maybe it is a graphics driver problem, you might try working your way

  3. if not a driver problem it might be helpful to

a. try adding these two options, to the boot options line presented on
the first green screen during boot, try them first one at a time and
after boot see if it will suspend and wake up ok, if not then try them
both together at the same time:


b. if neither of those work you might try alone


NOTE: any of those three acpi commands may ‘fix’ the recover from
suspend problem BUT at the same time interfere with the cooling fan
causing it to run much louder (or not at all–CAUTION), and maybe
greatly affect battery life…

  1. maybe you can find other similar Lenovo woes already encountered with
    Linux and find other hints here:

  2. or, maybe similar problems with non-Lenovo machines might be helpful,

  3. you might also try joining a Lenovo help forum, especially one where
    Linux users ask/answer questions and see if anyone there has a good
    ideas or two

  4. just don’t suspend…instead of suspending, shutdown.

OH! maybe a newer kernel will work perfectly…


Thanks for you support, I open a new bug in bugzilla novell for this case:

On 10/23/2012 06:16 AM, morfeokmg wrote:
> I open a new bug in bugzilla

lets hope they can kill the bug!