On Sat, Sep 15, 2018 at 11:55:15AM +0200, Toralf Förster wrote: > Hi, > > I do get for this device > > Bus 001 Device 009: ID 04f2:b39a Chicony Electronics Co., Ltd > > in dmesg these messages during boot: > > udevd[1178]: Error calling EVIOCSKEYCODE on device node > '/dev/input/event9' (scan code 0xc00b8, key code 161): Invalid argument > udevd[1178]: Error calling EVIOCSKEYCODE on device node > '/dev/input/event9' (scan code 0xc0183, key code 226): Invalid argument > udevd[1178]: Error calling EVIOCSKEYCODE on device node > '/dev/input/event9' (scan code 0xc0184, key code 421): Invalid argument > udevd[1178]: Error calling EVIOCSKEYCODE on device node > '/dev/input/event9' (scan code 0xc0186, key code 423): Invalid argument > udevd[1178]: Error calling EVIOCSKEYCODE on device node > '/dev/input/event9' (scan code 0xc018a, key code 155): Invalid argument > udevd[1178]: Error calling EVIOCSKEYCODE on device node > '/dev/input/event9' (scan code 0xc018e, key code 397): Invalid argument > udevd[1178]: Error calling EVIOCSKEYCODE on device node > '/dev/input/event9' (scan code 0xc01b6, key code 212): Invalid argument > udevd[1178]: Error calling EVIOCSKEYCODE on device node > '/dev/input/event9' (scan code 0xc01bc, key code 430): Invalid argument > udevd[1178]: Error calling EVIOCSKEYCODE on device node > '/dev/input/event9' (scan code 0xc0221, key code 217): Invalid argument > > Anything I should worry bout? No, this is benign. You can look through /lib/udev/hwdb.d/ and /etc/udev/hwdb.d and see what file contains v04f2pb39a string (or maybe just v04f2) and set up new keymap for it. Once you've identified the file you can contact authors and let them know that their file casts too wide net. Thanks. -- Dmitry
