Re: keyboard evdev
On Thu, Jun 04, 2009 at 06:00:34 -0500, Steve Vejcik wrote:
> Thanks again for the reply-hope this one goes through.
> Below are the commands and responses.
> Steve
>
> ls -l /dev/input/by-id/
>
> total 0lrwxrwxrwx 1 root root 9 Jun 3 02:37
> usb-Chicony_Saitek_Eclipse_II_Keyboard-event-kbd -> ../event3
>
> lshal --show $(hal-find-by-capability --capability input.mouse)
>
> udi =
> '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX_port_logicaldev_input'
> access_control.file = '/dev/input/event0' (string)
> access_control.type = 'mouse' (string)
> info.callouts.add = {'hal-acl-tool --add-device'} (string list)
> info.callouts.remove = {'hal-acl-tool --remove-device'} (string list)
> info.capabilities = {'input', 'input.mouse', 'access_control'} (string list)
[...]
> input.device = '/dev/input/event0' (string)
> input.originating_device =
> '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX_port' (string)
> input.product = 'ImExPS/2 Generic Explorer Mouse' (string)
> input.x11_driver = 'evdev' (string)
> linux.device_file = '/dev/input/event0' (string)
> linux.hotplug_type = 2 (0x2) (int)
> linux.subsystem = 'input' (string)
> linux.sysfs_path = '/sys/class/input/input0/event0' (string)
So the mouse is /dev/input/event0. That probably means that the
event3/event4 double keyboard occurrence in your Xorg.0.log is not
necessarily cause for concern. Also, google turns up a number of xorg
log files with the same double entries. (I suspect that event4 is
related to the multimedia key on the keyboard.)
> grep -Ev '^(#|$)' /etc/X11/xorg.conf
>
> Section "Device"
> Identifier "Configured Video Device"
> EndSection
Unfortunately, no clue here, either.
Earlier you mentioned that the problem started after a system upgrade.
Was the keyboard working with the evdev driver before, or was that
driver introduced for the first time during the same upgrade? Which
options did you have in the keyboard section of xorg.conf when you used
this keyboard with the "kbd" driver?
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
Reply to: