Home / ubuntu / Questions

Questions[keycodes](ubuntu)

Martin Hope
Lungten
Asked: 2020-02-26 03:44:43 +0800 CST
  • 2

I am trying to identify scancodes for the three buttons below the space bar (above the trackpad) on my ThinkPad X1C6 using evtest as well as evemu-record. The buttons are working fine but no scancodes are reported.

Output:

Input driver version is 1.0.1
Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
Input device name: "TPPS/2 Elan TrackPoint"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 272 (BTN_LEFT)
    Event code 273 (BTN_RIGHT)
    Event code 274 (BTN_MIDDLE)
  Event type 2 (EV_REL)
    Event code 0 (REL_X)
    Event code 1 (REL_Y)
Properties:
  Property type 0 (INPUT_PROP_POINTER)
  Property type 5 (INPUT_PROP_POINTING_STICK)
Testing ... (interrupt to exit)
Event: time 1582630481.910031, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1582630481.910031, -------------- SYN_REPORT ------------
Event: time 1582630482.071378, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
Event: time 1582630482.071378, -------------- SYN_REPORT ------------
Event: time 1582630483.486559, type 1 (EV_KEY), code 273 (BTN_RIGHT), value 1
Event: time 1582630483.486559, -------------- SYN_REPORT ------------
Event: time 1582630483.607941, type 1 (EV_KEY), code 273 (BTN_RIGHT), value 0
Event: time 1582630483.607941, -------------- SYN_REPORT ------------
Event: time 1582630488.204488, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1
Event: time 1582630488.204488, -------------- SYN_REPORT ------------
emacs thinkpadEvent: time 1582630488.348561, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 0
Event: time 1582630488.348561, -------------- SYN_REPORT ------------

If I can capture the scancodes I intend to remap these buttons as CTRL and ALT keys using udev hwdb if possible.

Some light on how to get the scan codes in such a case would be very much appreciated. BTW, I am on Ubuntu 18.04.4, Linux kernel 5.3.0-41-generic.

emacs thinkpad udev elantech keycodes
Martin Hope
Partack
Asked: 2019-12-01 22:35:15 +0800 CST
  • 0

i'm trying to map my drawing tablet buttons and the command to do that for my particular scenario is:

xsetwacom --set 'Tablet Monitor Pad pad' Button 1 "key a"
xsetwacom --set 'Tablet Monitor Pad pad' Button 2 "key b"

The output would be:

  • pressing button 1 > types the letter A,
  • button 2 > types the letter B, etc.

And this works great, no problems. But when i try to set "key [" or "key ]" the output i get is a key press of the number 8 or 9 respectively.

I tried the command XEV to find the keycode:

XEV screenshot

And it turns out "bracketright" is a thing, but setting this does exactly the same thing as ] (outputs the number 9 instead of ])

i even tried the keycode (keysym?) of 0x5d same result. (outputs 9)

I'm not sure what to try next.. anyone have any ideas?

I'm using Ubuntu 18.04 with the DIGImend drivers (Which i have installed and are working) (my tablet is a Huion H640P if it helps..)

OH, i just thought of something that may help, my keyboard layout is English (UK). Dunno if that might mess with anything? I feel like the XEV would have caught that regardless, but i feel like it's worth mentioning.

Edit: Turns out it does have something to do with the keyboard language, I set my keyboard to US and the output of [ and ] work perfectly.

I checked XEV for the keycode and it's the same as before.

Is this a bug? and should i report it? if so, then where?

And is there a way to check the actual binding/keycode for [ and ] on the British keyboard layout?

shortcut-keys xev 18.04 keycodes
Martin Hope
Jack Finan
Asked: 2018-06-26 07:19:53 +0800 CST
  • 0

I just got a lenovo ideapad 720s and installed Ubuntu. It has no media control keys (play/pause, next/prev track), so I wanted to remap some keys I don't use including the lock screen key. But when I use xev and press the key, the screen locks and the keycode is not displayed in the terminal. Is there another way to find the keycode?

keyboard xev keycodes
Martin Hope
turbo
Asked: 2012-03-28 12:26:35 +0800 CST
  • 5

On my Vostro 1000 notebook the following messages spam my dmesg:

[18678.728936] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0).
[18678.728941] atkbd.c: Use 'setkeycodes e00d <keycode>' to make it known.
[18679.831109] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0).
[18679.831119] atkbd.c: Use 'setkeycodes e00d <keycode>' to make it known.
[18679.841607] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0).
[18679.841615] atkbd.c: Use 'setkeycodes e00d <keycode>' to make it known.
[18680.901733] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0).
[18680.901744] atkbd.c: Use 'setkeycodes e00d <keycode>' to make it known.
[18680.911536] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0).
[18680.911546] atkbd.c: Use 'setkeycodes e00d <keycode>' to make it known.

It's most probably not from an actual key because it appears in regular intervals. First what is it? It could be my battery since it's nearly dead, as in loadable to 11 % of the initial capacity, but I have no evidence for that.

  • What is this / how can I find out where this comes from?
  • How can I get rid of it? Is there a 'dud' keycode?

When I assign a keycode with sudo setkeycode e00d $(random keycode) the key does actually get pressed. That makes it impossible to enter sudo password for example. So any 'real' keycode is not an option.

It hasn't been like that half a year ago. Even better than the dud keycode would be a real fix. It happens from 10.04 to 12.04 (before that I don't know).

I did read zcat /usr/share/doc/udev/README.keymap.txt.gz |less as suggested in the Ubuntu Wiki. /lib/udev/findkeyboards && sudo /lib/udev/keymap -i input/event5 produces what appears to be newlines in rapid succession.

sudo udevadm monitor doesn't show the event.

10.04 dmesg keycodes