systemd error

blacksabbath · 2022-05-26 18:11:41

After doing a clean install on my main system, i noticed an error that i've never seen before.

systemd-udevd[298]: event3: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument

udevadm reports:

P: /devices/platform/eeepc-wmi/input/input3/event3
M: event3
R: 3
U: input
D: c 13:67
N: input/event3
L: 0
S: input/by-path/platform-eeepc-wmi-event
E: DEVPATH=/devices/platform/eeepc-wmi/input/input3/event3
E: DEVNAME=/dev/input/event3
E: MAJOR=13
E: MINOR=67
E: SUBSYSTEM=input
E: USEC_INITIALIZED=2313129
E: KEYBOARD_KEY_6b=f21
E: KEYBOARD_KEY_7c=f20
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=platform-eeepc-wmi
E: ID_PATH_TAG=platform-eeepc-wmi
E: LIBINPUT_DEVICE_GROUP=19/0/0:eeepc-wmi
E: DEVLINKS=/dev/input/by-path/platform-eeepc-wmi-event
E: TAGS=:power-switch:
E: CURRENT_TAGS=:power-switch:

Also for some reason my hwdb.d folder is empty.

5.17.9-arch1-1

seth · 2022-05-26 20:15:28

Also for some reason my hwdb.d folder is empty.

/usr/lib/udev/hwdb.d ?

pacman -Qikk systemd

blacksabbath · 2022-05-27 05:12:20

seth wrote:

/usr/lib/udev/hwdb.d ?

Oh, i was searching it in a wrong path..
But seems like systemd 251 has bugs, rolling back to 250 fixes it.

Last edited by blacksabbath (2022-05-27 05:15:48)

seth · 2022-05-27 05:57:20

Somemightsathatsystemd/is/abug… but I guess that you're hitting sth. like https://bugs.launchpad.net/ubuntu/+sour … ug/1890186 (see comment #22)
tl;dr - a udev rule (likely added w/ 251) matches "multiple" devices - you can match

sudo libinput list-devices | grep -E '(Device:|Kernel:)'

and check device & vendor ID for those w/ suspiciously similar names ("sudo udevadm info /dev/input/event<number here>")

alex.leeken · 2022-06-05 01:25:51

Have the same problem, but don't know how to resolve it.

alex.leeken · 2022-06-05 12:27:13

Solved it by blacklisting eeepc_wmi module.

hias · 2022-06-05 17:23:44

I have a semilar error message in Log:

systemd-udevd[361]: event5: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument

While Keyboard and anny "Extra"-Buttons + lid switch work fine.
This message apiers the first time after full system upgrades including systemd 251 (and manny others):

upgraded systemd (250.4-2 -> 251.1-1)
upgraded linux-lts (5.15.35-1 -> 5.15.43-1)
upgraded upower (0.99.17-1 -> 0.99.18-1)
upgraded xorg-server (21.1.3-6 -> 21.1.3-7)

I dosn´t find any ID colision hiere by I trying udevadm info for every event Nr. (ID_INPUT is always = 1)

sudo libinput list-devices | grep -E '(Device:|Kernel:)'
Device:           Power Button
Kernel:           /dev/input/event2
Device:           Video Bus
Kernel:           /dev/input/event3
Device:           Lid Switch
Kernel:           /dev/input/event1
Device:           Sleep Button
Kernel:           /dev/input/event0
Device:           Asus Laptop extra buttons
Kernel:           /dev/input/event5
Device:           AT Translated Set 2 keyboard
Kernel:           /dev/input/event4
Device:           SynPS/2 Synaptics TouchPad
Kernel:           /dev/input/event7

alex.leeken wrote:

Solved it by blacklisting eeepc_wmi module.

Ok, maybe I need to blacklist things like asus_laptop to.

Some more Info:

sudo udevadm info /dev/input/event5
P: /devices/platform/asus_laptop/input/input9/event5
M: event5
R: 5
U: input
D: c 13:69
N: input/event5
L: 0
S: input/by-path/platform-asus_laptop-event
E: DEVPATH=/devices/platform/asus_laptop/input/input9/event5
E: DEVNAME=/dev/input/event5
E: MAJOR=13
E: MINOR=69
E: SUBSYSTEM=input
E: USEC_INITIALIZED=24337325
E: KEYBOARD_KEY_6b=f21
E: KEYBOARD_KEY_7c=f20
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=platform-asus_laptop
E: ID_PATH_TAG=platform-asus_laptop
E: LIBINPUT_DEVICE_GROUP=19/0/0:asus_laptop
E: DEVLINKS=/dev/input/by-path/platform-asus_laptop-event
E: TAGS=:power-switch:
E: CURRENT_TAGS=:power-switch:

uname -a
Linux (...) 5.15.44-1-lts #1 SMP Mon, 30 May 2022 13:45:47 +0000 x86_64 GNU/Linux

pacman -Qi systemd xorg-server xfwm4 | grep -B 1 Version
Name                     : systemd
Version                  : 251.2-1
--
Name                     : xorg-server
Version                  : 21.1.3-7
--
Name                     : xfwm4
Version                  : 4.16.1-3

Last edited by hias (2022-06-05 19:33:45)

hias · 2022-06-05 17:31:01

alex.leeken wrote:

Solved it by blacklisting eeepc_wmi module.

Ok, maybe I need to blacklist things like asus_laptop to.

ewaller · 2022-06-05 17:41:02

hias: Welcome to the Arch Linux forums. I like your avatar -- "Tux, the gate driver".

One point. If you are following up on your own post with no other messages from others in between, we prefer that you edit your post and simply add additional information. Just a preference of style

seth · 2022-06-05 19:48:17

https://bbs.archlinux.org/viewtopic.php … 0#p2037950

The OP wrote:

But seems like systemd 251 has bugs, rolling back to 250 fixes it.

Blacklisting the WMI will prevent a/the device showing up (possibly multiple times) but is hardly a solution to this problem.
If anything, you quite possibly remove HW functionality in order to suppress an error message (that's not reported to be tied to some actual problem)

You're doing this here:
https://www.youtube.com/watch?v=XPpJcnEoijU

Arch Linux

#1 2022-05-26 18:11:41

systemd error

#2 2022-05-26 20:15:28

Re: systemd error

#3 2022-05-27 05:12:20

Re: systemd error

#4 2022-05-27 05:57:20

Re: systemd error

#5 2022-06-05 01:25:51

Re: systemd error

#6 2022-06-05 12:27:13

Re: systemd error

#7 2022-06-05 17:23:44

Re: systemd error

#8 2022-06-05 17:31:01

Re: systemd error

#9 2022-06-05 17:41:02

Re: systemd error

#10 2022-06-05 19:48:17

Re: systemd error

Board footer