You are not logged in.
So I did a pacman -Syu today and after I restarted X my logitech G5 that was working fine and fully configured to use evdev stopped working. The mouse is still recognized and it starts with the system, but evdev does not. Here is the error log:
(**) Option "CorePointer"
(**) evdev: always reports core events
(EE) evdev: cannot open input pEvdev
(II) UnloadModule: "evdev"
(EE) PreInit returned NULL for "evdev"
Any help?
Offline
I can confirm this. My MX510 stopped working ....
Offline
Same here (Logitech MX 500).
I'm quite happy that I forgot to do 'pacman -Scc' for a few weeks so a simple
pacman -U /var/cache/pacman/pkg/xf86-input-evdev-1.1.5-4-i686.pkg.tar.gz
made my mouse work again.
Offline
Offline
What's your input- and serverlayoutsection of your xorg.conf look like? Did you pacman -Syu to xorg 7.3 before this upgrade (just released to extra last week IIRC), or did it come together with the upgrade to evdev 1.2?
Last week I read that some evdev-problems were solved by changing
SERVERLAYOUT
InputDevice "mouse" "AlwaysCore"
in
SERVERLAYOUT
InputDevice "mouse" "SendCoreEvents"
But these problems were related to the upgrade to xorg 7.3 (EDIT: this problem is related to having two mice on 1 system, f.e. with synaptics touchpad and USB-mouse)
Zl.
Last edited by zenlord (2007-11-16 17:40:02)
Offline
I had been using Xorg 7.3 since it was in someones repo, then swtiched to [testing] and have been using [extra] since it was released. The only package that was updated today was xf86-input-evdev.
In my server layout, the evdev line is
InputDevice "evdev" "CorePointer"
but I'll change it and see what happens.
The InputDevice section is:
Section "InputDevice"
Identifier "evdev"
Driver "evdev"
Option "Name" "Logitech USB Gaming Mouse"
Option "CorePointer"
EndSection
Offline
Then my idea was wrong - so sorry...
Zl.
PS: I edited my previous post after I had found that It should be 'alwayscore' instead of 'alwayscoreevents'...
Offline
I've partially solved the problem by using a mouse configuration (in xorg.con) like this:
Section "InputDevice"
Identifier "Mouse0"
Driver "evdev"
Option "Resolution" "800"
Option "ZAxisMapping" "4 5"
Option "HWHEELRelativeAxisButtons" "7 6"
Option "Name" "Logitech USB Receiver"
# Option "CorePointer" # Old version
EndSection
Section "InputDevice"
Identifier "Mouse1"
Driver "synaptics"
Option "Protocol" "auto-dev"
Option "Device" "/dev/psaux"
Option "LeftEdge" "1900"
Option "RightEdge" "5400"
Option "TopEdge" "1400"
Option "BottomEdge" "4500"
Option "FingerLow" "25"
Option "FingerHigh" "30"
Option "MaxTapTime" "180"
Option "MaxTapMove" "220"
Option "VertScrollDelta" "100"
Option "MinSpeed" "0.06"
Option "MaxSpeed" "0.12"
Option "AccelFactor" "0.0020"
Option "SHMConfig" "on"
EndSection
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
# InputDevice "Mouse0" "CorePointer" # Old version
InputDevice "Mouse0" "SendCoreEvents"
InputDevice "Mouse1" "SendCoreEvents"
EndSection
But now the horizontal scroll (left and right) does not work.
Also if we comment out the line:
Option "HWHEELRelativeAxisButtons" "7 6".
Bye.
Last edited by Giggi (2007-11-17 09:14:11)
Offline
Same problem here Logitech G5. Does anyone know if this is a bug in evdev or is it a bug in the arch build? Or is it even a bug?
charlie dont surf!
Offline
It seems to be a bug in evdev.
Offline
https://bugs.freedesktop.org/show_bug.cgi?id=12655
(dev's response to bug report)
User (and documentation) error.
Quite simply, you need a completely different X config for xf86-input-evdev
1.2.x.For hotplugging, you need to use the server's hotplug stuff.
We should however fix the documentation.
Offline
As long as the documentation is not updated, the package should be put to testing. Couse it will couse everyones mouse to stop working, and with no good docu, there is no way of fixing that quickly. It broke mine too, i reverted to 1.1.5. Works fine now again.
Greetz
Unknown Horizons - Open source real-time strategy game with the comfy Anno 1602 feeling!
Offline
can anyone post a link to the 1.1.5 pkgbuild?
Offline
http://phraktured.net/archmirror/extra/ … pkg.tar.gz
I think so too, the package should stay in testing there is a new documentation....
Offline
Thanks for the info sinister99
charlie dont surf!
Offline
In xorg.conf in mouse section add:
(...)
Option "Device" "/dev/input/eventX"
(...)
Where X is the appropiate event number in
egrep "Name|Handler" /proc/bus/input/devices
Worked for me!
Last edited by noidor (2007-11-18 12:59:45)
Offline
Works for me too, thx!
Offline
Thank you noidor! Works!
charlie dont surf!
Offline
In xorg.conf in mouse section add:
(...) Option "Device" "/dev/input/eventX" (...)
Where X is the appropiate event number in
egrep "Name|Handler" /proc/bus/input/devices
Worked for me!
Does not work.
Please submit your complete config.
Offline
Section "ServerLayout"
Identifier "Xorg Configured"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Evdev Mouse" "SendCoreEvents"
EndSection
Section "InputDevice"
Identifier "Evdev Mouse"
Driver "evdev"
Option "Name" "Logitech USB Receiver"
Option "Device" "/dev/input/event6"
Option "SendCoreEvents" "true"
EndSection
Last edited by qlus (2007-11-18 18:43:58)
Offline
I remember that my device in /dev/input/event* changed number (from event5 to event6 and back) every reboot.. that's why I commented that line in the past. Can anyone confirm this?
/me stuck with evdev and revert to mouse diver :-(
Offline
I had similar problem after upgrade to evdev from testing.
I follow edadvice from this topic, but to avoid problems with the mouse being connected to different USB ports, I added this line to InputDevice section of xorg.conf:
Option "Device" "/dev/input/vx_nano"
And created a file /etc/udev/rules.d/99-vx-nano.rules with this:
SUBSYSTEM=="input", ATTRS{name}=="Logitech USB Receiver", ATTR{dev}=="13:70", SYMLINK+="input/vx_nano"
This is for my VX Nano mouse. To get information about the device, I checked /dev/input/by-path/ directory.
There was a symlink pci-0000:00:1d.1-usb-0:1:1.0-event-mouse pointing to ../event6.
So I run:
find /sys -name event6 -type d
And I run udevinfo, with an argument produced by find command:
udevinfo -a -p /sys/devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/input/input43/event6
Then I took ATTR values from two first sections (the second one looked more descriptive, but without ATTR{dev} wrong symlink was created):
looking at device '/devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/input/input43/event6':
KERNEL=="event6"
SUBSYSTEM=="input"
DRIVER==""
ATTR{dev}=="13:70"
looking at parent device '/devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/input/input43':
KERNELS=="input43"
SUBSYSTEMS=="input"
DRIVERS==""
ATTRS{modalias}=="input:b0003v046DpC521e0111-e0,1,2,k110,111,112,113,114,115,116,117,118,119,11A,11B,11C,11D,11E,11F,r0,1,6,8,amlsfw"
ATTRS{uniq}==""
ATTRS{phys}=="usb-0000:00:1d.1-1/input0"
ATTRS{name}=="Logitech USB Receiver"
I have no idea if it is a correct solution, but so far it works.
Maybe someone else will find it useful
Last edited by tanis (2007-11-18 21:59:35)
Offline
I think event devices should appear in "/dev/input/by-id/" with an almost friendly name, I am using that:
Option "Device" "/dev/input/by-id/usb-Microsoft_Microsoft_IntelliMouse_Optical-event-mouse"
I'm not sure if it's a bug in archlinux udev, but there is no 'by-id' directory and in /dev/udev/rules.d/udev.rules, there is
# by-id links, generic and for the event devices
KERNEL=="mouse*|js*", ENV{ID_SUBSYSTEMS}=="?*", ENV{ID_SERIAL}=="?*", ENV{ID_CLASS}=="?*", SYMLINK+="input/by-id/$env{ID_SUBSYSTEMS}-$env{ID_SERIAL}-$env{ID_CLASS}"
KERNEL=="event*", ENV{ID_SUBSYSTEMS}=="?*", ENV{ID_SERIAL}=="?*", ENV{ID_CLASS}=="?*", SYMLINK+="input/by-id/$env{ID_SUBSYSTEMS}-$env{ID_SERIAL}-event-$env{ID_CLASS}"
if you replace only these 4 ID_SUBSYSTEMS by ID_BUS, it works.
You can find the list of defined variables for the device (here /dev/input/event5) with:
$ udevinfo --query=all --name=/dev/input/event5
P: /devices/pci0000:00/0000:00:07.2/usb1/1-2/1-2.2/1-2.2:1.0/input/input5/event5
N: input/event5
S: input/by-id/usb-Microsoft_Microsoft_IntelliMouse_Optical-event-mouse
S: input/by-path/pci-0000:00:07.2-usb-0:2.2:1.0-event-mouse
E: ID_VENDOR=Microsoft
E: ID_MODEL=Microsoft_IntelliMouse_Optical
E: ID_REVISION=0121
E: ID_SERIAL=Microsoft_Microsoft_IntelliMouse_Optical
E: ID_TYPE=hid
E: ID_BUS=usb
E: ID_CLASS=mouse
E: ID_PATH=pci-0000:00:07.2-usb-0:2.2:1.0
Last edited by alexisdm (2007-11-18 22:49:34)
Offline
Works here too.
You are right, much nicer solution
Btw, maybe it would be a good idea to fill a bug report for udev rules?
Last edited by tanis (2007-11-18 23:04:34)
Offline
Btw, maybe it would be a good idea to fill a bug report for udev rules?
Offline