There is a problem with xf86-input-evdev-1.2.0 where it doesn't detect the devices. The relevant error log is the following (RatoUsb is my usb mouse, Teclado is the keyboard): (--) Touchpad auto-dev sets device to /dev/input/event5 (**) Option "Device" "/dev/input/event5" (**) Option "SHMConfig" "on" (--) Touchpad touchpad found (**) Option "CorePointer" (**) Touchpad: always reports core events (**) RatoUsb: always reports core events (EE) RatoUsb: cannot open input pEvdev <<<<<<<<< (II) UnloadModule: "evdev" (EE) PreInit returned NULL for "RatoUsb" (**) Option "CoreKeyboard" (**) Teclado: always reports core events (**) Option "Protocol" "standard" (**) Teclado: Protocol: standard (**) Option "AutoRepeat" "500 30" (**) Option "XkbRules" "xorg" (**) Teclado: XkbRules: "xorg" (**) Option "XkbModel" "pc105" (**) Teclado: XkbModel: "pc105" (**) Option "XkbLayout" "pt" (**) Teclado: XkbLayout: "pt" (**) Option "CustomKeycodes" "off" (**) Teclado: CustomKeycodes disabled (II) evaluating device (Teclado) (II) XINPUT: Adding extended input device "Teclado" (type: KEYBOARD) (II) evaluating device (Touchpad) (II) XINPUT: Adding extended input device "Touchpad" (type: MOUSE) Synaptics DeviceInit called SynapticsCtrl called. Synaptics DeviceOn called (--) Touchpad auto-dev sets device to /dev/input/event5 (**) Option "Device" "/dev/input/event5" (--) Touchpad touchpad found The problem is the same with the keyboard if I use the evdev driver for the keyboard (I'm using the "keyboard" driver). I don't think this is related in any way with my config nor any portage options, but please ask them if you think is relevant. There's a similar bug on the debian mailing list (debian bug Bug#443292).
me too
same here (relevant parts of Xorg.log pasted): ... (**) Option "CoreKeyboard" (**) Keyboard: always reports core events (EE) Keyboard: cannot open input pEvdev (II) UnloadModule: "evdev" (EE) PreInit returned NULL for "Keyboard" ... (**) Option "SendCoreEvents" (**) Mouse: always reports core events (EE) Mouse: cannot open input pEvdev (II) UnloadModule: "evdev" (EE) PreInit returned NULL for "Mouse"
(Same here) mouse and Keyboard not working...
Same here, for some reason the device path is not found (pEvdev->device is NULL).
Same here... Section "InputDevice" Identifier "USB Mouse" Driver "evdev" Option "Name" "HID 062a:0000" EndSection (**) Option "SendCoreEvents" (**) USB Mouse: always reports core events (EE) USB Mouse: cannot open input pEvdev (II) UnloadModule: "evdev" (EE) PreInit returned NULL for "USB Mouse"
According to https://bugs.freedesktop.org/show_bug.cgi?id=12655 this is per design. Config change, bug what?
I just unkeyworded 1.2.0 because it apparently requires xorg-server built with hal support and hal 0.5.10 (gentopia overlay only) installed to work properly.
(In reply to comment #6) > According to > https://bugs.freedesktop.org/show_bug.cgi?id=12655 > this is per design. Config change, bug what? > Yeah, it's kind of useless to completely change the config, but not tell anyone how to use it. Even an example "here's how to setup a mouse" in that response would be useful.
This is a popular bug.. http://forums.gentoo.org/viewtopic-t-613733-postdays-0-postorder-asc-start-0.html (me too) W
(In reply to comment #7) > I just unkeyworded 1.2.0 because it apparently requires xorg-server built with > hal support and hal 0.5.10 (gentopia overlay only) installed to work properly. > Looks like Hal 0.5.10 has been added to the portage tree. Should we give this a try again?
(In reply to comment #10) > (In reply to comment #7) > > I just unkeyworded 1.2.0 because it apparently requires xorg-server built with > > hal support and hal 0.5.10 (gentopia overlay only) installed to work properly. > > > > Looks like Hal 0.5.10 has been added to the portage tree. Should we give this a > try again? > Actually problems persist - http://bugs.gentoo.org/show_bug.cgi?id=200087
http://bbs.archlinux.org/viewtopic.php?id=39981 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/173833
The option "Device" or "Path" needs to be set to the /dev/input/eventX device. All other options for device detection were removed. The manpage is outdated but upstream will take care of this and the updated documentation will probably be in 1.2.1. Please mark this as resolved/upstream, since it's not Gentoo spefic.
After reading a few things on xorg mailing list, I followed those suggestions and solved `cannot open input pEvdev` problem by adding AllowEmptyInput in server options and removing Input sections from xorg.conf. As I have only a standard keyboard and a PS2 mouse, whatever hal does, is enough for me. I only needed correct fdi file for my keyboard (with layout and hal-setup-keymap entries - the ones shipped with hal needed to be corrected, were checking for wrong capability).
HAL and evdev were not really ready for xorg-server 1.4. I advise all of you not to use them with that version. However the situation has greatly improved with xorg-server 1.5. Please do try newer versions of xf86-input-evdev and xorg-server and report any bugs you might have wrt input. Thanks
Xorg-server 1.5.3-r5 and xf86-input-evdev 2.1.3 are now both stable. No-one seems to have had further problems, let's close this bug. Thanks to all
