Thanks; reassigning to the kernel then, as the keyboard driver must
produce scan codes, otherwise we can't reassign their meaning. Of
course, while doing that it could also just produce correct key codes
:-)
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
The keys are in the position of F keys but are not at all labeled as F keys.
They are all labeled as media keys, basically. I'm not sure what the official
definition of F keys are, but I do know that users of this laptop will not
expect them to type F keys, but instead control the volume, brig
Thanks; seems the chromebook kernel keyboard driver isn't sending scan
codes along, but the actual key codes seem correct (F1 to F10) *if* they
are actually F keys. If they are supposed to do something else, then the
kernel needs to be fixed first to report proper scan codes.
--
You received this
Here is the evtest transcript of my session of pressing the keys on the
top row of the Chromebook, starting with the Left-Arrow key, which is
just to the right of the Esc key:
$ sudo evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: chro
I'll run evtest when I get home today and report back. I attached an
image of the keyboard for reference. You can see that the top row of
keys are labeled like media keys, etc. There is no Fn key on it as far
as I can tell. When I press any of the top row of keys, they send F-key
key codes, so pr
Or do you mean that pressing e. g. "F8" is not actually yielding "F8"
but some special funtion like "projector" or "brightness"? Some laptops
require pressing Fn+F8 to get the actual F8, and the simple "F8" is a
hotkey. This often can be switched around in the BIOS, though.
--
You received this b
