You are not logged in.
Pages: 1
i have an ultranav keyboard: "Lite-On Tech IBM USB Keyboard with UltraNav"
the 7 dmesg errors coincide exactly with the seven keyboard keys listed in event1 and event2.
I don't need or use these keys - so any solution which would disable these keys would not be a problem.
udevadm info /dev/input/event1 ## same keyboard_keys for event2
E: KEYBOARD_KEY_900f0=screenlock
E: KEYBOARD_KEY_900f1=wlan
E: KEYBOARD_KEY_900f2=switchvideomode
E: KEYBOARD_KEY_900f3=suspend
E: KEYBOARD_KEY_900f4=brightnessup
E: KEYBOARD_KEY_900f5=brightnessdown
E: KEYBOARD_KEY_900f8=zoomdmesg output
Dec 07 14:38:59 dh67 systemd-udevd[201]: Error calling EVIOCSKEYCODE on device node '/dev/input/event1' (scan code 0x900f0, key code 152): Invalid argument
Dec 07 14:38:59 dh67 systemd-udevd[201]: Error calling EVIOCSKEYCODE on device node '/dev/input/event1' (scan code 0x900f1, key code 238): Invalid argument
Dec 07 14:38:59 dh67 systemd-udevd[201]: Error calling EVIOCSKEYCODE on device node '/dev/input/event1' (scan code 0x900f2, key code 227): Invalid argument
Dec 07 14:38:59 dh67 systemd-udevd[201]: Error calling EVIOCSKEYCODE on device node '/dev/input/event1' (scan code 0x900f3, key code 205): Invalid argument
Dec 07 14:38:59 dh67 systemd-udevd[201]: Error calling EVIOCSKEYCODE on device node '/dev/input/event1' (scan code 0x900f4, key code 225): Invalid argument
Dec 07 14:38:59 dh67 systemd-udevd[201]: Error calling EVIOCSKEYCODE on device node '/dev/input/event1' (scan code 0x900f5, key code 224): Invalid argument
Dec 07 14:38:59 dh67 systemd-udevd[201]: Error calling EVIOCSKEYCODE on device node '/dev/input/event1' (scan code 0x900f8, key code 372): Invalid argument
[/proc/bus/input/devices # just showing the two devices associated with the keyboard.
I: Bus=0003 Vendor=04b3 Product=3018 Version=0110
N: Name="Lite-On Tech IBM USB Keyboard with UltraNav"
P: Phys=usb-0000:00:1a.0-1.5.3/input0
S: Sysfs=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.3/1-1.5.3:1.0/0003:04B3:3018.0005/input/input3
U: Uniq=
H: Handlers=sysrq kbd event1 leds
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7
I: Bus=0003 Vendor=04b3 Product=3018 Version=0110
N: Name="Lite-On Tech IBM USB Keyboard with UltraNav"
P: Phys=usb-0000:00:1a.0-1.5.3/input1
S: Sysfs=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.3/1-1.5.3:1.1/0003:04B3:3018.0006/input/input4
U: Uniq=
H: Handlers=kbd event2 rfkill
B: PROP=0
B: EV=13
B: KEY=7f60000000000000 40000000000000 10000000000000 0 400b00002000 4028c110dc00 1e000000000000 0
B: MSC=10udevadm info /dev/input/event1
P: /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.3/1-1.5.3:1.0/0003:04B3:3018.0005/input/input3/event1
N: input/event1
S: input/by-id/usb-Lite-On_Tech_IBM_USB_Keyboard_with_UltraNav-event-kbd
S: input/by-path/pci-0000:00:1a.0-usb-0:1.5.3:1.0-event-kbd
E: DEVLINKS=/dev/input/by-path/pci-0000:00:1a.0-usb-0:1.5.3:1.0-event-kbd /dev/input/by-id/usb-Lite-On_Tech_IBM_USB_Keyboard_with_UltraNav-event-kbd
E: DEVNAME=/dev/input/event1
E: DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.3/1-1.5.3:1.0/0003:04B3:3018.0005/input/input3/event1
E: ID_BUS=usb
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_INPUT_KEYBOARD=1
E: ID_MODEL=IBM_USB_Keyboard_with_UltraNav
E: ID_MODEL_ENC=IBM\x20USB\x20Keyboard\x20with\x20UltraNav
E: ID_MODEL_ID=3018
E: ID_PATH=pci-0000:00:1a.0-usb-0:1.5.3:1.0
E: ID_PATH_TAG=pci-0000_00_1a_0-usb-0_1_5_3_1_0
E: ID_REVISION=0116
E: ID_SERIAL=Lite-On_Tech_IBM_USB_Keyboard_with_UltraNav
E: ID_TYPE=hid
E: ID_USB_DRIVER=usbhid
E: ID_USB_INTERFACES=:030101:030000:
E: ID_USB_INTERFACE_NUM=00
E: ID_VENDOR=Lite-On_Tech
E: ID_VENDOR_ENC=Lite-On\x20Tech
E: ID_VENDOR_ID=04b3
E: KEYBOARD_KEY_900f0=screenlock
E: KEYBOARD_KEY_900f1=wlan
E: KEYBOARD_KEY_900f2=switchvideomode
E: KEYBOARD_KEY_900f3=suspend
E: KEYBOARD_KEY_900f4=brightnessup
E: KEYBOARD_KEY_900f5=brightnessdown
E: KEYBOARD_KEY_900f8=zoom
E: LIBINPUT_DEVICE_GROUP=3/4b3/3018/110:usb-0000:00:1a.0-1.5
E: MAJOR=13
E: MINOR=65
E: SUBSYSTEM=input
E: USEC_INITIALIZED=5216982udevadm info /dev/input/event2
P: /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.3/1-1.5.3:1.0/0003:04B3:3018.0005/input/input3/event1
N: input/event1
S: input/by-id/usb-Lite-On_Tech_IBM_USB_Keyboard_with_UltraNav-event-kbd
S: input/by-path/pci-0000:00:1a.0-usb-0:1.5.3:1.0-event-kbd
E: DEVLINKS=/dev/input/by-path/pci-0000:00:1a.0-usb-0:1.5.3:1.0-event-kbd /dev/input/by-id/usb-Lite-On_Tech_IBM_USB_Keyboard_with_UltraNav-event-kbd
E: DEVNAME=/dev/input/event1
E: DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.3/1-1.5.3:1.0/0003:04B3:3018.0005/input/input3/event1
E: ID_BUS=usb
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_INPUT_KEYBOARD=1
E: ID_MODEL=IBM_USB_Keyboard_with_UltraNav
E: ID_MODEL_ENC=IBM\x20USB\x20Keyboard\x20with\x20UltraNav
E: ID_MODEL_ID=3018
E: ID_PATH=pci-0000:00:1a.0-usb-0:1.5.3:1.0
E: ID_PATH_TAG=pci-0000_00_1a_0-usb-0_1_5_3_1_0
E: ID_REVISION=0116
E: ID_SERIAL=Lite-On_Tech_IBM_USB_Keyboard_with_UltraNav
E: ID_TYPE=hid
E: ID_USB_DRIVER=usbhid
E: ID_USB_INTERFACES=:030101:030000:
E: ID_USB_INTERFACE_NUM=00
E: ID_VENDOR=Lite-On_Tech
E: ID_VENDOR_ENC=Lite-On\x20Tech
E: ID_VENDOR_ID=04b3
E: KEYBOARD_KEY_900f0=screenlock
E: KEYBOARD_KEY_900f1=wlan
E: KEYBOARD_KEY_900f2=switchvideomode
E: KEYBOARD_KEY_900f3=suspend
E: KEYBOARD_KEY_900f4=brightnessup
E: KEYBOARD_KEY_900f5=brightnessdown
E: KEYBOARD_KEY_900f8=zoom
E: LIBINPUT_DEVICE_GROUP=3/4b3/3018/110:usb-0000:00:1a.0-1.5
E: MAJOR=13
E: MINOR=65
E: SUBSYSTEM=input
E: USEC_INITIALIZED=5216982Offline
ok. found this:
/usr/lib/udev/hwdb.d\60-keyboard.conf
# IBM Thinkpad USB Keyboard Trackpoint
evdev:input:b0003v04B3p301[89]*
KEYBOARD_KEY_900f0=screenlock
KEYBOARD_KEY_900f1=wlan
KEYBOARD_KEY_900f2=switchvideomode
KEYBOARD_KEY_900f3=suspend
KEYBOARD_KEY_900f4=brightnessup
KEYBOARD_KEY_900f5=brightnessdown
KEYBOARD_KEY_900f8=zoomthis matches my keyboard vendor and product id: (04B3 and 3018)
should I disable this from loading or override it with my own udev rule or something else. again I don't use these keys - in fact pressing fn+brightness key causes xorg to freeze up.
Last edited by hamhock (2016-12-08 00:48:59)
Offline
i created this file
/etc/udev/hwdb.d/60-ultranav.hwdb
evdev:input:b0003v04B3p3018*
KEYBOARD_KEY_900f0=esc
KEYBOARD_KEY_900f1=unknown
KEYBOARD_KEY_900f2=unknown
KEYBOARD_KEY_900f3=unknown
KEYBOARD_KEY_900f4=unknown
KEYBOARD_KEY_900f5=unknown
KEYBOARD_KEY_900f8=unknownthen ran:
# udevadm hwdb --update
# sudo udevadm trigger the changes made in /etc/udev did get picked up, but resulted in the same error, just different key codes now:
Dec 07 22:40:26 dh67 systemd-udevd[213]: Error calling EVIOCSKEYCODE on device node '/dev/input/event1' (scan code 0x900f0, key code 1): Invalid argument
Dec 07 22:40:26 dh67 systemd-udevd[213]: Error calling EVIOCSKEYCODE on device node '/dev/input/event1' (scan code 0x900f1, key code 240): Invalid argument
Dec 07 22:40:26 dh67 systemd-udevd[213]: Error calling EVIOCSKEYCODE on device node '/dev/input/event1' (scan code 0x900f2, key code 240): Invalid argument
Dec 07 22:40:26 dh67 systemd-udevd[213]: Error calling EVIOCSKEYCODE on device node '/dev/input/event1' (scan code 0x900f3, key code 240): Invalid argument
Dec 07 22:40:26 dh67 systemd-udevd[213]: Error calling EVIOCSKEYCODE on device node '/dev/input/event1' (scan code 0x900f4, key code 240): Invalid argument
Dec 07 22:40:26 dh67 systemd-udevd[213]: Error calling EVIOCSKEYCODE on device node '/dev/input/event1' (scan code 0x900f5, key code 240): Invalid argument
Dec 07 22:40:26 dh67 systemd-udevd[213]: Error calling EVIOCSKEYCODE on device node '/dev/input/event1' (scan code 0x900f8, key code 240): Invalid argumentare there any key codes I can place in the /etc/udev that won't result in 'Invalid argument' ?
Last edited by hamhock (2016-12-08 16:03:42)
Offline
on the ubuntu forums https://ubuntuforums.org/showthread.php?t=2250210
soultion is to just comment out the lines in /usr/lib/udev/hwdb.d\60-keyboard.hwdb for your keyboard that is triggering the "Invalid argument" errors.
would that be the best solution on my arch install?
Offline
Pages: 1