USB keyboard is split between 2 input events

agolp · 2024-10-16 02:00:50

Hello,

My USB keyboard is split between 2 events in /dev/input, leading to the caps lock not triggering anything. I had this issue before and it went away on its own when after a reboot one of these events was gone. I know it sounds weird, but evtest for event 19 catches almost all my keys, whereas the same test for event21 shows no output.

$ sudo evtest 
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	Power Button
/dev/input/event1:	Power Button
/dev/input/event10:	HD-Audio Generic Rear Mic
/dev/input/event11:	HD-Audio Generic Front Mic
/dev/input/event12:	HD-Audio Generic Line
/dev/input/event13:	HD-Audio Generic Line Out Front
/dev/input/event14:	HD-Audio Generic Line Out Surround
/dev/input/event15:	Razer Pro Click Keyboard
/dev/input/event16:	HD-Audio Generic Line Out CLFE
/dev/input/event17:	Razer Pro Click
/dev/input/event18:	HD-Audio Generic Front Headphone
/dev/input/event19:	Topre REALFORCE 87 US
/dev/input/event2:	PC Speaker
/dev/input/event20:	Microsoft X-Box 360 pad
/dev/input/event21:	Topre REALFORCE 87 US
/dev/input/event3:	HDA NVidia HDMI/DP,pcm=3
/dev/input/event4:	HDA NVidia HDMI/DP,pcm=7
/dev/input/event5:	HDA NVidia HDMI/DP,pcm=8
/dev/input/event6:	HDA NVidia HDMI/DP,pcm=9
/dev/input/event7:	Razer Pro Click
/dev/input/event8:	Razer Pro Click
/dev/input/event9:	Eee PC WMI hotkeys

$ cat /proc/bus/input/devices
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
U: Uniq=
H: Handlers=kbd event0 
B: PROP=0
B: EV=3
B: KEY=8000 10000000000000 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: PROP=0
B: EV=3
B: KEY=8000 10000000000000 0

I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input2
U: Uniq=
H: Handlers=kbd event2 
B: PROP=0
B: EV=40001
B: SND=6

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:03.1/0000:0b:00.1/sound/card0/input3
U: Uniq=
H: Handlers=event3 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=7"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:03.1/0000:0b:00.1/sound/card0/input4
U: Uniq=
H: Handlers=event4 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=8"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:03.1/0000:0b:00.1/sound/card0/input5
U: Uniq=
H: Handlers=event5 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=9"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:03.1/0000:0b:00.1/sound/card0/input6
U: Uniq=
H: Handlers=event6 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0003 Vendor=1532 Product=0080 Version=0111
N: Name="Razer Pro Click"
P: Phys=usb-0000:0d:00.3-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:08.1/0000:0d:00.3/usb5/5-1/5-1:1.0/0003:1532:0080.0001/input/input7
U: Uniq=000000000000
H: Handlers=event7 mouse0 
B: PROP=0
B: EV=17
B: KEY=1f0000 0 0 0 0
B: REL=903
B: MSC=10

I: Bus=0003 Vendor=1532 Product=0080 Version=0111
N: Name="Razer Pro Click"
P: Phys=usb-0000:0d:00.3-1/input2
S: Sysfs=/devices/pci0000:00/0000:00:08.1/0000:0d:00.3/usb5/5-1/5-1:1.2/0003:1532:0080.0002/input/input8
U: Uniq=000000000000
H: Handlers=sysrq kbd leds event8 
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7

I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="Eee PC WMI hotkeys"
P: Phys=eeepc-wmi/input0
S: Sysfs=/devices/platform/eeepc-wmi/input/input9
U: Uniq=
H: Handlers=kbd event9 rfkill 
B: PROP=0
B: EV=100013
B: KEY=7e00000 0 800000000000 0 0 1400b00100000 8300180001100800 e000000000000 2
B: MSC=10

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Rear Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:08.1/0000:0d:00.4/sound/card1/input10
U: Uniq=
H: Handlers=event10 
B: PROP=0
B: EV=21
B: SW=10

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Front Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:08.1/0000:0d:00.4/sound/card1/input11
U: Uniq=
H: Handlers=event11 
B: PROP=0
B: EV=21
B: SW=10

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Line"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:08.1/0000:0d:00.4/sound/card1/input12
U: Uniq=
H: Handlers=event12 
B: PROP=0
B: EV=21
B: SW=2000

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Line Out Front"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:08.1/0000:0d:00.4/sound/card1/input13
U: Uniq=
H: Handlers=event13 
B: PROP=0
B: EV=21
B: SW=40

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Line Out Surround"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:08.1/0000:0d:00.4/sound/card1/input14
U: Uniq=
H: Handlers=event14 
B: PROP=0
B: EV=21
B: SW=40

I: Bus=0003 Vendor=1532 Product=0080 Version=0111
N: Name="Razer Pro Click Keyboard"
P: Phys=usb-0000:0d:00.3-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:08.1/0000:0d:00.3/usb5/5-1/5-1:1.1/0003:1532:0080.0003/input/input17
U: Uniq=000000000000
H: Handlers=sysrq kbd event15 
B: PROP=0
B: EV=10001f
B: KEY=33eff 0 0 483ffff17aff32d bfd4444600000000 1 130c730b17c007 ffbf7bfad941dfff febeffdfffefffff fffffffffffffffe
B: REL=1040
B: ABS=100000000
B: MSC=10

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Line Out CLFE"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:08.1/0000:0d:00.4/sound/card1/input15
U: Uniq=
H: Handlers=event16 
B: PROP=0
B: EV=21
B: SW=40

I: Bus=0003 Vendor=1532 Product=0080 Version=0111
N: Name="Razer Pro Click"
P: Phys=usb-0000:0d:00.3-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:08.1/0000:0d:00.3/usb5/5-1/5-1:1.1/0003:1532:0080.0003/input/input18
U: Uniq=000000000000
H: Handlers=event17 
B: PROP=0
B: EV=9
B: ABS=10000000000

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Front Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:08.1/0000:0d:00.4/sound/card1/input16
U: Uniq=
H: Handlers=event18 
B: PROP=0
B: EV=21
B: SW=4

I: Bus=0003 Vendor=045e Product=028e Version=0114
N: Name="Microsoft X-Box 360 pad"
P: Phys=usb-0000:08:00.3-3/input0
S: Sysfs=/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:08:00.3/usb3/3-3/3-3:1.0/input/input20
U: Uniq=
H: Handlers=event20 js0 
B: PROP=0
B: EV=20000b
B: KEY=7cdb000000000000 0 0 0 0
B: ABS=3003f
B: FF=107030000 0

I: Bus=0003 Vendor=0853 Product=0146 Version=0111
N: Name="Topre REALFORCE 87 US"
P: Phys=usb-0000:0d:00.3-2/input0
S: Sysfs=/devices/pci0000:00/0000:00:08.1/0000:0d:00.3/usb5/5-2/5-2:1.0/0003:0853:0146.0004/input/input23
U: Uniq=
H: Handlers=sysrq kbd leds event19 
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=1f

I: Bus=0003 Vendor=0853 Product=0146 Version=0111
N: Name="Topre REALFORCE 87 US"
P: Phys=usb-0000:0d:00.3-2/input1
S: Sysfs=/devices/pci0000:00/0000:00:08.1/0000:0d:00.3/usb5/5-2/5-2:1.1/0003:0853:0146.0005/input/input24
U: Uniq=
H: Handlers=sysrq kbd event21 
B: PROP=0
B: EV=100013
B: KEY=1000000000007 ff981878180117ff febeffdfffefffff fffffffffffffffe
B: MSC=10

$ sudo libinput list-devices
Device:           Power Button
Kernel:           /dev/input/event1
Group:            1
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         0.0

Device:           Power Button
Kernel:           /dev/input/event0
Group:            2
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         0.0

Device:           Razer Pro Click
Kernel:           /dev/input/event7
Group:            3
Seat:             seat0, default
Capabilities:     pointer 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: disabled
Calibration:      n/a
Scroll methods:   button
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   flat *adaptive custom
Rotation:         0.0

Device:           Razer Pro Click Keyboard
Kernel:           /dev/input/event15
Group:            3
Seat:             seat0, default
Capabilities:     keyboard pointer 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    disabled
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         0.0

Device:           Razer Pro Click
Kernel:           /dev/input/event8
Group:            3
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         0.0

Device:           Topre REALFORCE 87 US
Kernel:           /dev/input/event19
Group:            4
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         0.0

Device:           Topre REALFORCE 87 US
Kernel:           /dev/input/event21
Group:            4
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         0.0

Device:           Eee PC WMI hotkeys
Kernel:           /dev/input/event9
Group:            5
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         0.0

journalctl -b output

seth · 2024-10-16 07:01:14

It's common for hardware to show up a multiple logical devices, but I doubt that results in "the caps lock not triggering anything"

sudo libinput debug-events

doesn't register anyhing when pressing that key?
Does it work in some live distro?

Looks like a mechanical switch so the common tactics like whacking the keyboard likely won't work.
Does it "feel" normal (ie. not shaky, makes the same sound and has the same springs as the other keys etc)?

agolp · 2024-10-16 08:58:04

No, debug-events does not register anything for that key (but all other keys I tried worked). The capslock key feels normal. It might be a coincidence that the problem goes away when there is only one event associated with the keyboard, but I saw that happen twice in the past few weeks. Every time the key was working, there was only one event associated with the keyboard.

I have not tested in a live distrib, it's a great idea, I will come back to you after I try.

Thanks a lot!

seth · 2024-10-16 11:53:50

Another thing you may try is to re-plug the keyboard and see whether this changes anything about the input device count and the behavior.
If so, please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

agolp · 2024-10-16 13:59:10

You were right. My display server crashed (Wayland) and the caps lock key is now working again, while I still have the two logical devices for the keyboard.

Sorry for the long log file: journalctl -b
It started working at the end after I had to reconnect from GDM.

seth · 2024-10-16 14:17:39

No usb device was (re-)added after the boot in that journal (or did you replug the keyboard during the first 2-3 seconds of the boot, before *any* GUI actually started?) and you're not running on wayland but X11 and a bogus, nvidia-settings generated, /etc/X11/xorg.conf file

Enable https://wiki.archlinux.org/title/NVIDIA … de_setting if you ever want a chance to use wayland and use the "nvidia_drm.modeset=1" kernel parameter (modprobe.conf won't do!) to also get rid of the simpledrm device (and pot. software emulation)
In general remove the xorg.conf, but despite the bogus keyboard config in it, I don't think that's causing anything like you're seeing.

Your Razer Pro Click moue also provides a keyboard device, maybe it's interfering?
Do you have a $5 mouse with two buttons or so?

agolp · 2024-10-16 15:23:04

I did not reboot or replug the keyboard today. I tried yesterday, but have no log to show for it, sorry. I'll retry later on and send the log.

$ sudo cat /sys/module/nvidia_drm/parameters/modeset
Y

$ cat /etc/modprobe.d/nvidia.conf 
options nvidia-drm modeset=1
options nvidia-drm fbdev=1

That's what I was using to run Wayland when I got it to work. Steam was using Xwayland. If it's not working anymore, do you recommend adding nvidia_drm.modeset=1 and nvidia_drm.fbdev=1 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub instead of using /etc/modprobe.d/nvidia.conf? I can remove /etc/X11/xorg.conf if it won't mess up anything as well. I like having X11 as a fallback when Wayland stops working after an update.

I have not tried disconnecting the mouse. It's a 4 button mouse I connect with the USB cable (not wirelessly).

Thanks for the time you're taking!

Last edited by agolp (2024-10-16 15:23:27)

seth · 2024-10-16 15:57:29

I did not reboot or replug the keyboard today. I tried yesterday, but have no log to show for it, sorry.

You can access older journals, eg. "sudo journalct -b -1" is the previous boot.

GDM is a bit peculiar reg. wayland on nvidia, https://wiki.archlinux.org/title/GDM#Wa … DIA_driver
Using the kernel commandline instead of the modprobe config will simply make sure that you don't end up running software emulation on the simpledrm device.

https://www.razer.com/gaming-mice/razer … R3U1#specs

I know, the idea was to replace that with some cheap office supply mouse in case the keyboard event of the razer interferes with your real keyboard (given the highly specific symptom rather a wild theory, but still…)

agolp · 2024-10-19 23:46:59

Hey,

I did not touch anything for a few days as caps lock was working again (I turned off the computer at the end of each day but did not do any system update or configuration change). I was looking for the first time things went wrong. In the previous boot, it took a very long time to shut down after the graphical session closed, as if something timed out and the computer turned off anyway.

Caps lock working - previous boot - journalctl
Caps lock not working - current boot - journalctl

Should I try reconnecting the keyboard now?

seth · 2024-10-20 06:39:01

If you're still awake, but we've already established that the input split isn't related to the keyboard malfunction.
(Still worth a shot to see whether that has any impact)

Arch Linux

#1 2024-10-16 02:00:50

USB keyboard is split between 2 input events

#2 2024-10-16 07:01:14

Re: USB keyboard is split between 2 input events

#3 2024-10-16 08:58:04

Re: USB keyboard is split between 2 input events

#4 2024-10-16 11:53:50

Re: USB keyboard is split between 2 input events

#5 2024-10-16 13:59:10

Re: USB keyboard is split between 2 input events

#6 2024-10-16 14:17:39

Re: USB keyboard is split between 2 input events

#7 2024-10-16 15:23:04

Re: USB keyboard is split between 2 input events

#8 2024-10-16 15:57:29

Re: USB keyboard is split between 2 input events

#9 2024-10-19 23:46:59

Re: USB keyboard is split between 2 input events

#10 2024-10-20 06:39:01

Re: USB keyboard is split between 2 input events

Board footer