[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#347950: xserver-xorg: no longer finding evdev mouse driver on startup!



On Sun, Jan 15, 2006 at 06:27:59AM -0800, Arias Hung wrote:
> On Fri, 13 Jan 2006, David Nusinow delivered in simple text monotype:
> 
> >Have you tried using xmodmap and the evdev driver to supply the necessary
> >parameters for your extra buttons?
> >
> >- David Nusinow
> <---snip--->
> 
> Yes.  If you actually read the startx log of my submitted bug
> report you'll see the:
> 
> (**) Option "Protocol" "evdev"
> (EE) Mouse1: Unknown protocol "evdev"
> (EE) PreInit failed for input device "Mouse1"
> 
> Which chokes startx, due to not being able to find the mouse driver.
> This obviously occurs before even getting to the stage where Xmodmap
> configuration is viable.

Ah, I'm sorry, I had assumed that you knew what you were doing. You'll want
to add a Load "evdev" in the modules section of your config file. You'll
then want to switch the driver for your mouse to "evdev", not the protocol.
Finally, you'll want to point your driver to /dev/input/event#, where # is
whichever file the kernel assigns to your device.

If you look at the manpage for evdev(4x) you'll see that the majority of
your options that are available for the mouse(4x) driver are not available,
so you may as well comment them out. That's why you'll need something like
xmodmap.

 - David Nusinow



Reply to: