It seems the auto-detection for Linux in configure doesn't work anymore.
As a consequence, none of the KDrive input drivers are enabled, and mouse
and keyboard don't work. build-main/include/kdrive-config.h:
/* #undef KDRIVE_KBD */
/* #undef KDRIVE_MOUSE */
/* #undef KDRIVE_EVDEV */
Explicitly enable kdrive-mouse and kdrive-evdev to fix this.
Notes:
- I did not enable kdrive-kbd, as it's completely broken.
Since it no longer fills in KdKeyboardInfo.minScanCode and
KdKeyboardInfo.maxScanCode, any keypress causes messages like:
driver Linux console keyboard wanted to post scancode x outside of [0, 0]!
- kdrive-mouse still works (e.g. "-mouse ps2", or "-mouse mouse" for
protocol probing, which takes some time), but the recommended way
these days is kbd-evdev, using the following (ugly) command line
parameters:
-keybd evdev,,device=/dev/input/event0
-mouse evdev,,device=/dev/input/event1
- This may be the reason behind
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640699
("keyboard problem with xserver xfbdev: why does it not work?")
- See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646686
("xserver-xephyr: Xephyr doesn't work with evdev input drivers")
Signed-off-by: Geert Uytterhoeven <ge...@linux-m68k.org>
Cc: 640...@bugs.debian.org
Cc: 646...@bugs.debian.org
---
debian/rules | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/debian/rules b/debian/rules
index 3011a78..59f0c4c 100755
--- a/debian/rules
+++ b/debian/rules
@@ -60,6 +60,7 @@ endif
ifeq ($(DEB_HOST_ARCH_OS), linux)
build_xfbdev = --enable-xfbdev
+ build_xfbdev += --enable-kdrive-mouse --enable-kdrive-evdev
selinux = --enable-xselinux
else
build_xfbdev = --disable-xfbdev
--
1.7.0.4
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/1364390451-9656-2-git-send-email-ge...@linux-m68k.org
