On 02/17/2011 03:17 AM, Cyril Brulebois wrote:
> http://pkg-xorg.alioth.debian.org/howto/configure-input.html should
> get you started. You could try getting rid of the InputDevice bits in

I did: dpkg-reconfigure keyboard-configuration, and
udevadm trigger --subsystem-match=input --action=change, and reboot.

I noticed this in the Xorg.0.log file:

(**) ModulePath set to "/usr/lib/xorg/modules"
(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' wi
ll be disabled.
(WW) Disabling Mouse0
(WW) Disabling Keyboard0
[... NVIDA stuff etc...]
(II) config/udev: Adding input device Power Button (/dev/input/event3)
(**) Power Button: Applying InputClass "evdev keyboard catchall"
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
        compiled for 1.7.6.901, module version = 2.3.2
        Module class: X.Org XInput Driver
        ABI class: X.Org XInput driver, version 7.0
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event3"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc104"
(**) Option "xkb_layout" "us"
(II) config/udev: Adding input device Power Button (/dev/input/event2)
(**) Power Button: Applying InputClass "evdev keyboard catchall"
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event2"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc104"
(**) Option "xkb_layout" "us"
[...]
(II) config/udev: Adding input device AT Translated Set 2 keyboard
(/dev/input/event1)
(**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT Translated Set 2 keyboard: Device: "/dev/input/event1"
(II) AT Translated Set 2 keyboard: Found keys
(II) AT Translated Set 2 keyboard: Configuring as keyboard
(II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard"
(type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc104"
(**) Option "xkb_layout" "us"
[...]
(II) config/udev: Adding input device ACPI Virtual Keyboard Device
(/dev/input/event6)
(**) ACPI Virtual Keyboard Device: Applying InputClass "evdev keyboard catchall"
(**) ACPI Virtual Keyboard Device: always reports core events
(**) ACPI Virtual Keyboard Device: Device: "/dev/input/event6"
(II) ACPI Virtual Keyboard Device: Found keys
(II) ACPI Virtual Keyboard Device: Configuring as keyboard
(II) XINPUT: Adding extended input device "ACPI Virtual Keyboard Device"
(type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc104"
(**) Option "xkb_layout" "us"

To clarify, I have only one keyboard attached through PS/2.

Some additional information that may or may not be relevant:
- I have a streamzap remote connected through a USB port.
- before the upgrade (when the keyboard still worked) I had frequent issues
with the onboard network: the connection speed went to a crawl (like 5000ms
from 0.7ms), an ifdown eth0; ifup eth0 fixed that until the next crawl.  This
may indicate some hardware issue/conflict.
- I ssh-ed in using -X.  DISPLAY=:0 xterm successfully opened a window (where
the keyboard still did not work).
- I have no login set for the default user (this is a mythfrontend machine).
- I configured to have lirc, irxevent, irexec, mythfrontend to run on startup
of Gnome.  ps shows that mythfrontend is running, but there is no GUI
visible.  The mythfrontend log indicates no errors.  This latter makes me
suspect that X/Gnome somehow fails to react and it is not the keyboard at fault.

Thanks again.
-Matyas
-
Every hardware eventually breaks.  Every software eventually works.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to