Fn-key setting reset after resume of Thinkpad Edge E220S

[Chow Loong Jin]

Some background information:
The Thinkpad Edge E220S has one of those ridiculous keyboard designs that inverts the behaviour of the Fn key with the top row of the keyboard (F1-F12), i.e. to get an actual F1 keystroke, you need to hold down the F1 key. This behaviour is configurable in the BIOS. In my case, I have configured it so that I need to hold the Fn key to access the special functions, but not for the actual F1-12 keypresses.

Problem:
After a resume from suspend-to-RAM, the behaviour of the keyboard reverts to the factory setting, i.e. Fn key required to be held down to get the F1-12 keypresses. I reckon this is either due to a broken BIOS or perhaps something that wasn't done to restore the correct behaviour after resume.

Workaround:
Hibernate the machine and resume.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: pm-utils 1.4.1-7
Uname: Linux 2.6.39-ck1-hyper1 x86_64
Architecture: amd64
Date: Thu Jun 23 19:17:38 2011
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_SG:en
 PATH=(custom, user)
 LANG=en_SG.utf8
 SHELL=/bin/zsh
SourcePackage: pm-utils
UpgradeStatus: Upgraded to natty on 2011-04-24 (60 days ago)

[Chow Loong Jin (hyperair)]

On 23/06/2011 19:26, Chow Loong Jin wrote:
> Public bug reported:
>
> Some background information:
> The Thinkpad Edge E220S has one of those ridiculous keyboard designs that inverts the behaviour of the Fn key with the top row of the keyboard (F1-F12), i.e. to get an actual F1 keystroke, you need to hold down the F1 key. This behaviour is configurable in the BIOS. In my case, I have configured it so that I need to hold the Fn key to access the special functions, but not for the actual F1-12 keypresses.
>
> Problem:
> After a resume from suspend-to-RAM, the behaviour of the keyboard reverts to the factory setting, i.e. Fn key required to be held down to get the F1-12 keypresses. I reckon this is either due to a broken BIOS or perhaps something that wasn't done to restore the correct behaviour after resume.
>
> Workaround:
> Hibernate the machine and resume.

Alright, this is weird. I can't reproduce it reliably by suspending and
resuming. I'll keep observing and post an update when I figure out what causes
the flip back.

--
Kind regards,
Loong Jin

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[nagy.pite (nagy.pite)]

Affects me as well, couldn't yet determine the cause either. It seems as if it sometimes locks itself while normal use.
I have to note though that sometimes other keys lock up as well, namely Alt or the arrow keys. However those can be unlocked by double-tapping the problematic key. But not for the Fn lock, I've tried many combinations without success.

Hibernating is a workaround all right, but it's much slower than a reboot, which makes it a poor option.

Machine's a E420s, with 11.10 amd64

Uname: Linux 3.0.0-14-generic #23-Ubuntu SMP x86_64

[Ted Yin (ted-sybil)]

the same situation as nagy.pite (nagy.pite) .
My machine's a E420s as well.
I'm using Gentoo. The kernel image is compiled by myself.

i686 Intel(R) Core(TM) i3-2310M CPU @ 2.10GHz GenuineIntel GNU/Linux

[Ted Yin (ted-sybil)]

Problem seemed to be solved after I tried to reset my computer ( press the small button in the hole for sevaral seconds).

[Nikita Tsukanov (keks9n)]

T520 and almost simular problem here: after resume from hibernation Fn keys don't work at all.

[penalvch (penalvch)]

Chow Loong Lin, thank you for reporting this bug to Ubuntu. Natty reached EOL on October 28, 2012.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Is this reproducible in the latest release of Ubuntu via http://cdimage.ubuntu.com/daily-live/current/ ?

If so, please execute the following via a terminal in order for the necessary debugging information to be attached:
apport-collect 801106

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]