[Bug 1248808] Re: volume and brightness keys are mismapped on Samsung Chromebook

[Martin Pitt]

Can you please install the "evtest" package, run "sudo evtest", and
select the device which represents your keyboard? Then you can press the
Fn keys and check which of them have a wrong KEY_* code. Please note
down the scan code, current, and intended key code.

 For example,

Event: time 1384346796.203894, type 4 (EV_MSC), code 4 (MSC_SCAN), value 06
Event: time 1384346796.203894, type 1 (EV_KEY), code 227 (KEY_SWITCHVIDEOMODE), value 0

This is scan code 4 (from "code 4 (MSC_SCAN)"), and key code
"SWITCHVIDEOMODE". With the updated map that you provide I can fix
udev's keymaps.

** Changed in: systemd (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1248808

Title:
  [keymap] volume and brightness keys on Samsung Chromebook

Status in “systemd” package in Ubuntu:
  Incomplete

Bug description:
  I've got XUbuntu/saucy on this US$250 Samsung Chromebook 5.  It runs
  very well, it just had a couple of minor issues that need to be fixed
  and it'll be an awesome little Ubuntu laptop with a regular Ubuntu
  install!

  The volume and brightness keys don't work.  When I checked them out
  using xev, they were returning F keys:

  F1 - back (i.e. like in a browser)
  F2 - forward
  F3 - refresh
  F4 - fullscreen
  F5 - switch screen mode
  F6 - brightness down
  F7 - brightness up
  F8 - mute
  F9 - volume down
  F10 - volume up

  I'm happy to try my hand at fixing it, but the documentation in
  https://wiki.ubuntu.com/Hotkeys/Troubleshooting pointed towards a non-
  existent file for directions on the next steps:
  /usr/share/doc/udev/README.keymap.txt

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: udev 204-0ubuntu19
  Uname: Linux 3.4.0-5-chromebook armv7l
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: armhf
  CustomUdevRuleFiles: 99-hide-disks.rules
  Date: Wed Nov  6 22:32:06 2013
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   SHELL=/bin/bash
  ProcKernelCmdLine: cros_secure console= console=tty1 debug verbose root=/dev/mmcblk1p7 rootwait rw lsm.module_locking=0
  SourcePackage: systemd
  UpgradeStatus: Upgraded to saucy on 2013-10-24 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1248808/+subscriptions