Note: You sent your last message to me directly with a CC to the list.
It seems that the copy to the list has been blocked, therefore I
reply to the private message. Please fix your email program so
that it replies to the list only and that it does not send an HTML
part. (This should reduce the likelihood of your messages being
considered spam by the list filters.)
On Wed, Jun 03, 2009 at 10:02:46 -0500, Steve Vejcik wrote:
> Thanks for responding-below are the results of the two commands:
>
> grep -Ei 'keyboard|xkb|evdev' /var/log/Xorg.0.log(II) Cannot locate a core
> keyboard device.
> (II) Initializing built-in extension XKEYBOARD
> (II) config/hal: Adding input device Chicony Saitek Eclipse II Keyboard
> (II) LoadModule: "evdev"
> (II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
> (II) Module evdev: vendor="X.Org Foundation"
> (**) Chicony Saitek Eclipse II Keyboard: always reports core events
> (**) Chicony Saitek Eclipse II Keyboard: Device: "/dev/input/event4"
> (II) Chicony Saitek Eclipse II Keyboard: Found 4 mouse buttons
> (II) Chicony Saitek Eclipse II Keyboard: Found keys
> (II) Chicony Saitek Eclipse II Keyboard: Configuring as keyboard
> (**) Chicony Saitek Eclipse II Keyboard: YAxisMapping: buttons 4 and 5
> (**) Chicony Saitek Eclipse II Keyboard: EmulateWheelButton: 4,
> EmulateWheelInertia: 10, EmulateWheelTimeout: 200
> (II) XINPUT: Adding extended input device "Chicony Saitek Eclipse II
> Keyboard" (type: KEYBOARD)
> (**) Option "xkb_rules" "evdev"
> (**) Option "xkb_model" "pc104"
> (**) Option "xkb_layout" "us"
> (II) config/hal: Adding input device Chicony Saitek Eclipse II Keyboard
> (**) Chicony Saitek Eclipse II Keyboard: always reports core events
> (**) Chicony Saitek Eclipse II Keyboard: Device: "/dev/input/event3"
> (II) Chicony Saitek Eclipse II Keyboard: Found keys
> (II) Chicony Saitek Eclipse II Keyboard: Configuring as keyboard
> (II) XINPUT: Adding extended input device "Chicony Saitek Eclipse II
> Keyboard" (type: KEYBOARD)
> (**) Option "xkb_rules" "evdev"
> (**) Option "xkb_model" "pc104"
> (**) Option "xkb_layout" "us"
Hmm, your Xorg finds two keyboard-type devices, event4 and event3. The
first one that it finds has mouse buttons, which does not look right to
me.
> lshal --show $(hal-find-by-capability --capability input.keyboard)
>
> udi =
> '/org/freedesktop/Hal/devices/usb_device_6a3_8021_noserial_if0_logicaldev_input'
> info.addons.singleton = {'hald-addon-input'} (string list)
> info.callouts.add = {'debian-setup-keyboard'} (string list)
> info.capabilities = {'input', 'input.keyboard', 'input.keypad',
> 'input.keys', 'button'} (string list)
> info.category = 'input' (string)
> info.parent =
> '/org/freedesktop/Hal/devices/usb_device_6a3_8021_noserial_if0' (string)
> info.product = 'Chicony Saitek Eclipse II Keyboard' (string)
> info.subsystem = 'input' (string)
> info.udi =
> '/org/freedesktop/Hal/devices/usb_device_6a3_8021_noserial_if0_logicaldev_input'
> (string)
> input.device = '/dev/input/event3' (string)
> input.originating_device =
> '/org/freedesktop/Hal/devices/usb_device_6a3_8021_noserial_if0' (string)
> input.product = 'Chicony Saitek Eclipse II Keyboard' (string)
> input.x11_driver = 'evdev' (string)
> input.xkb.layout = 'us' (string)
> input.xkb.model = 'pc104' (string)
> input.xkb.rules = 'base' (string)
> linux.device_file = '/dev/input/event3' (string)
> linux.hotplug_type = 2 (0x2) (int)
> linux.subsystem = 'input' (string)
> linux.sysfs_path = '/sys/class/input/input3/event3' (string)
This looks good and makes it clear that the keyboard should be
/dev/input/event3.
Now we have to figure out why event4 (the mouse probably) is also seen
as a keyboard. Please post the output of:
ls -l /dev/input/by-id/
lshal --show $(hal-find-by-capability --capability input.mouse)
grep -Ev '^(#|$)' /etc/X11/xorg.conf
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
