701 2011-02-07 03:37:37 +0000 xserver: keyboard input not working 2012-06-20 16:11:31 +0000 1 1 7 Build System, Metadata & Runtime OE-Core graphics 1.0 All arm RESOLVED OBSOLETE Pending info from reporter... (11-Aug-2011) Needs Owner. Low normal 1.3 1 wd sgw bluelightning dvhart jessica.zhang meta.mr.watcher meta.watcher poky.adt.watcher poky.watcher yp.kernel.watcher yp.watcher --- --- --- oldest_to_newest 11679 0 wd 2011-02-07 03:37:37 +0000 I'm testing poky-image-sato-sdk, current top of tree, in the qemuarm configuration on real ARM hardware. When attaching a USB keyboard, it gets properly recognized by the Linux kernel; by running "evtest" I can verify that keyboard events arrive as expected. However, none of the applications sees any keyboard input. After manually restarting the xserver ("/etc/init.d/xserver-nodm restart" on the console) keyboard input starts working fine. 12025 1 ke.yu 2011-02-23 18:38:39 +0000 Hi Denk, could you provide more info on the configuration, especially: - Which ARM board are you using - which kernel version - The xserver config file (/etc/X11/xorg.conf) 12043 2 wd 2011-02-23 22:51:35 +0000 As mentioned above, I build for the "qemuarm" configuration, which is generic enough for me to be used on several different boards, including a QONG eval board (Freescale i.MX31 based, see http://denx-cs.de/?q=QONG) and a TWISTER eval board (TI Sitara AM3517 based, see http://denx-cs.de/?q=TAM3517). I'm using our own (basicly mainline) kernel on the Qong (2.6.36 based),and the vendor-provided kernel tree on the Twister (2.6.32 based). For /etc/X11/xorg.conf I used both the unmodified version from the poky build and with the following tuning for the twister board: --- etc/X11/Xserver.ORIG 2011-02-02 18:45:28.000000000 +0000 +++ etc/X11/Xserver 2011-02-03 11:09:06.000000000 +0000 @@ -34,16 +34,6 @@ ARGS="$ARGS -keybd keyboard" - # use usb mouse if present - if [ -z "$TSLIB_TSDEVICE" ] && [ -e /dev/input/mice ]; then - ARGS="$ARGS -mouse mouse,/dev/input/mice" - fi - - # kdrive 1.4 onwards needs -mouse args - if [ -n "$TSLIB_TSDEVICE" ]; then - ARGS="$ARGS -mouse tslib" - fi - # start off server in conventional location. case `module_id` in "Generic OMAP1510/1610/1710") @@ -56,7 +46,19 @@ ARGS="$ARGS -mouse tslib" ;; "Nokia 770") ARGS="$ARGS -mouse tslib" ;; + "TAM3517 EVM") + ARGS="$ARGS -mouse tslib,device=/dev/input/touchscreen0 -mouse mouse,device=/dev/input/mouse1" ;; *) + # use usb mouse if present + if [ -z "$TSLIB_TSDEVICE" ] && [ -e /dev/input/mice ]; then + ARGS="$ARGS -mouse mouse,/dev/input/mice" + fi + + # kdrive 1.4 onwards needs -mouse args + if [ -n "$TSLIB_TSDEVICE" ]; then + ARGS="$ARGS -mouse tslib" + fi + ;; esac 14335 3 dvhart 2011-06-17 14:56:59 +0000 I believe this is due to the AutoAdd clause in the xorg.conf under ServerFlags, at least it caused similar behavior for me on the beagleboard: With: Option "AutoAddDevices" "True" The keyboard would not work at all. With: Option "AutoAddDevices" "False" The keyboard would work if plugged in prior to starting X or after restarting X. Do you observe the same behavior Wolfgang? 14349 4 wd 2011-06-20 03:03:55 +0000 Sorry, but I did not understand what exactly you want me to test. There is no /etc/X11/xorg.conf fine in my image (nor any xorg.conf in the whole file system image). Also, the string "AutoAddDevices" does not appear in any file in /etc. What exactly should I do? 14353 5 dvhart 2011-06-20 14:06:54 +0000 This is a bit of a mess right now as I'm experimenting with replacing kdrive with xf86-lite. However, for your immediate question, try creating /etc/X11/xorg.conf and adding the following to it: Section "ServerFlags" Option "AutoAddDevices" "False" EndSection My suspicion is that xkeyboard-config is reading that - but that's just a hunch. 14709 6 ke.yu 2011-07-13 06:39:28 +0000 Denk, does Darren's suggestion works for you? 15348 7 ke.yu 2011-08-09 06:30:49 +0000 can we lower the priority since the reporter does not response for quite long time. 15415 8 dvhart 2011-08-11 15:41:07 +0000 Wolfgang, is this still an issue for you? 16286 9 bluelightning 2011-09-19 06:38:20 +0000 FWIW I have seen this same problem with a recent build from master on an atom-pc system. Using the suggested workaround fixes it assuming you have the keyboard plugged in at X startup; surely however we want users to be able to plug in a keyboard at any time? 21387 10 dvhart 2012-05-16 21:33:26 +0000 This is certainly a more generic X configuration issue and not a Kernel issue. Recategorizing, it also needs a new owner. 22429 11 sgw 2012-06-20 16:09:09 +0000 As the sumbitter has not updated information in a number of months, I am closing this, it can be repoened if the issue re-appears. 22430 12 bluelightning 2012-06-20 16:11:31 +0000 Rather than just closing this bug on the assumption it is fixed, I would much rather someone actually tested this; it's not hard to test.