[Lenovo IdeaPad Yoga 13] ubuntu doesn't know about Yoga screen rotation keycodes: atkbd serio0: Use 'setkeycodes e03e <keycode>' to make it known.

[noobermin]

The following spam litters dmesg:

[36294.989706] atkbd serio0: Use 'setkeycodes e03e <keycode>' to make it known.
[36294.995650] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0).
[36294.995661] atkbd serio0: Use 'setkeycodes e03e <keycode>' to make it known.
[36296.016998] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0).
[36296.017002] atkbd serio0: Use 'setkeycodes e03e <keycode>' to make it known.
[36296.021894] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0).
[36296.021907] atkbd serio0: Use 'setkeycodes e03e <keycode>' to make it known.

As can be seen, this occurs frequently. It might be related, but at times, the keyboard freezes for a few seconds and then starts sending a repeating character while no keys are pressed. This behavior is not stopped unless a key (any key) is pressed.

The character that is output is a special character, but I don't know what combination it is specifically.

This might be related to the fact that this is a lenovo yoga 13 ideapad.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-30-generic 3.8.0-30.44
ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
Uname: Linux 3.8.0-30-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: noobermin 1991 F.... pulseaudio
 /dev/snd/pcmC0D0p: noobermin 1991 F...m pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Fri Sep 20 02:07:54 2013
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=7d95a03d-5f38-403f-84d9-51ebca691a4b
InstallationDate: Installed on 2013-08-31 (19 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: LENOVO 20175
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic root=UUID=6a1575e6-9b6a-4086-988e-2efda2c80fd3 ro quiet splash acpi_backlight=vendor vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-30-generic N/A
 linux-backports-modules-3.8.0-30-generic N/A
 linux-firmware 1.106
RfKill:

SourcePackage: linux
StagingDrivers: rts5139
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/22/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 66CN52WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: INVALID
dmi.board.vendor: LENOVO
dmi.board.version: 31900003WIN8 STD MLT
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Yoga 13
dmi.modalias: dmi:bvnLENOVO:bvr66CN52WW:bd11/22/2012:svnLENOVO:pn20175:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr31900003WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13:
dmi.product.name: 20175
dmi.product.version: Lenovo IdeaPad Yoga 13
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[noobermin (fischerhamilton)]

Is anybody out there?

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc1-saucy/

[noobermin (fischerhamilton)]

Forgive the late reply.

Tested on 3.12-rc1...it's still an issue.

[noobermin (fischerhamilton)]

I have noticed something interesting. I have since installed gnome 3 on the gnome3-staging ppa (gnome 3.8) and I am now using gdm instead of lightdm, and I'm still using linux 3.12; in any case, the spam has stopped! I will try using lightdm again and seeing if it returns.

[noobermin (fischerhamilton)]

The plot thickens.

Apparently, I switched to lightdm and I don't see of the errors. Furthermore, I switched back to linux 3.8 and I still don't see any errors. Could there be something in the ppa's that stabilizes this? Just to be sure, I'll try to ppa-purge the ppas and revert to my previous state.

[Donn Morrison (donn-morrison)]

I also have a Yoga and have this issue with 13.04 and kernel 3.8.0-30-generic.

I use

sudo setkeycodes e03e 255

as a workaround to make it stop, but this is obviously does not persist through a reboot.

[penalvch (penalvch)]

noobermin, as per http://download.lenovo.com/express/ddfm.html an update is available for your BIOS (66cn55ww). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Thank you for your understanding.

[Dimitri John Ledkov (xnox)]

These keycodes are sent by Lenovo IdeaPad Yoga 13 as indication which mode the laptop is in (noteboot, or flipped back enough to turn it into a laptop mode). On the right side there a small button which is "screen rotation" lock (portrait/landscape). None of the screen-rotations / tablet-conversions are support out of the box on Ubuntu yet. I'm not sure what are the best way to support them either.

[esion (esion99)]

still here on ubuntu 14.04, no bios update

sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
66CN54WW
01/21/2013

uname -a
Linux dey-mobile 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:07:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

the spam stops when screen is flipped

[Donn Morrison (donn-morrison)]

I reported a bug similar to this a while ago, and after a firmware upgrade (see below) it was fixed. Recently the stuck keys and the syslog spam about keycode e03e have come back.

sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
66CN55WW
02/28/2013

Linux 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

As above, it stops when the screen is flipped.

[Donn Morrison (donn-morrison)]

Forgot link to the other bug:

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1238914

[Jany Belluz (belluzj)]

I have the same problem, almost the same configuration:

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
66CN55WW
02/28/2013

$ uname -a
Linux yoga 3.13.0-38-generic #65-Ubuntu SMP Thu Oct 9 11:36:50 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

I must add that I use Ubuntu 14.10, except for the kernel which I kept from an older ubuntu version (because of the Yoga's wifi card, other problem)

[Andrew Symington (asymingt)]

I also have the same problem with spamming the syslog and repeating keys, which is suppressed with 'sudo setkeycodes e03e 255'. I have stack to 14.04 because I wish to remain on an LTS release.

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
66CN55WW
02/28/2013

$ uname -a
Linux ideapad-yoga13 3.13.0-53-generic #89-Ubuntu SMP Wed May 20 10:34:39 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Is there any way that I can have 'sudo setkeycodes e03e 255' run on boot. Sticking it in /etc/rc.local doesn't seem to work.

[penalvch (penalvch)]

Andrew Symington, please do not toggle the Status. For more on this, please see https://wiki.ubuntu.com/Bugs/Status .

[vak (khamenya)]

sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
66CN55WW
02/28/2013

cat /etc/issue
Ubuntu 16.04 LTS \n \l

uname -a
Linux yogi 4.4.0-22-generic #39-Ubuntu SMP Thu May 5 16:53:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

[spencer (walden)]

I am also having this issue. It started happening for me when I was using ArchLinux during July of 2016; I was thinking about going back to Ubuntu, so I re-installed Lubuntu over Arch. Low and Behold, the issue persists.

My issue is worse in that usually the key(s) that will trigger this repeated key is the arrow keys, which I frequently use to scroll up and down through man pages, web pages, etc. However, when this occurs, my keyboard no longer responds to input, and my mouse will start "falling" to whichever direction the arrow key corresponds (down arrow repeat will cause my mouse cursor to continuously move to the bottom of the screen). I noticed that my dmesg was being spammed with this error too, and when I (temporarily) set the keycodes to 255, the issue persists, but the error message will go away from dmesg.
If my issue seems right for another new bug thread, please let me know.

I'll provide what everyone else has been providing -- welcome to provide any information I can in order to address this bug.

$ cat /etc/issue
Ubuntu 16.04.1 LTS \n \l

$ uname -a
Linux masq-Lu 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12 13:48:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

# dmidecode -s bios-version && dmidecode -s bios-release-date
66CN55WW
02/28/2013

Or if anyone knows generally what might be messed up, I'm pretty experienced using Linux, and I know some C... so I could theoretically fix it myself (I would post any successes I had here).

Cheers

[Stefan van der Walt (si-ubuntu-ed)]

This is exactly the behavior I see on my machine.

Linux shinobi 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:09:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

66CN55WW
02/28/2013

[vak (khamenya)]

went away for a long time, so I refused to do any package updates for several months and everything was fine. Now i did update of packages and thing came back :(

[Ariel Tankus (arielta)]

Same bug affects me (Linux phg 4.9.0-3-amd64 #1 SMP Debian 4.9.25-1 (2017-05-02) x86_64 GNU/Linux).

As a simple bypass, add Donn's suggestion to /etc/rc.local :
/usr/bin/setkeycodes e03e 255

After reboot, no more messages of this type in the log files.