I’m checking the following error in journalctl:
fedora kernel: hub 10-0:1.0: config failed, hub doesn't have any ports! (err -19)
fedora (udev-worker)[1046]: event14: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument
From some quick googling, I was able to see some kind of recommendations in the Arch Linux Forums:
- [SOLVED] Odd messages at boot / in journal after systemd 221-1 upgrade
- systemd error, but I only found more problems when executing the tests in the posts:
sudo udevadm info /dev/input/event14
:
P: /devices/platform/eeepc-wmi/input/input28/event14
M: event14
R: 14
U: input
D: c 13:78
N: input/event14
L: 0
S: input/by-path/platform-eeepc-wmi-event
E: DEVPATH=/devices/platform/eeepc-wmi/input/input28/event14
E: DEVNAME=/dev/input/event14
E: MAJOR=13
E: MINOR=78
E: SUBSYSTEM=input
E: USEC_INITIALIZED=7150289
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:
sudo libinput list-devices | grep -E '(Device:|Kernel:)'
Device: Power Button
Kernel: /dev/input/event1
Device: Video Bus
Kernel: /dev/input/event2
Device: Power Button
Kernel: /dev/input/event0
Device: Logitech PRO X Wireless Gaming Headset Consumer Control
Kernel: /dev/input/event6
Device: Logitech Candy
Kernel: /dev/input/event4
Device: Logitech G502 X PLUS
Kernel: /dev/input/event3
Device: ROYUAN EPOMAKER TH80 Pro
Kernel: /dev/input/event8
Device: ROYUAN EPOMAKER TH80 Pro Consumer Control
Kernel: /dev/input/event9
Device: ROYUAN EPOMAKER TH80 Pro System Control
Kernel: /dev/input/event10
Device: ROYUAN EPOMAKER TH80 Pro Keyboard
Kernel: /dev/input/event11
Device: ROYUAN EPOMAKER TH80 Pro Mouse
Kernel: /dev/input/event12
Device: Asus WMI hotkeys
Kernel: /dev/input/event15
Device: Eee PC WMI hotkeys
Kernel: /dev/input/event14
I don’t think blacklisting the eeepc_wmi
module might be a good idea, as stated in the Arch forums. Does anyone else had this issue with an ASUS mobo?