On Thu, Jan 12, 2006 at 09:05:29AM -0700, Jeremy Nickurak wrote: > On Thu, Jan 12, 2006 at 10:03:00AM -0500, David Nusinow wrote: > > evedev support has not been removed. We've switched to upstream's version > > for supporting it. I've added an evdev(4x) manpage to document this, as > > well as the NEWS.Debian.gz entry that you misread. Please try again with > > the evdev support from upstream and let us know if you can't properly > > configure it that way. If you can't, we'll try and track it down and figure > > out how to improve the upstream support to get what you need. > > Let me know if I'm misunderstanding this. the evdev input driver selection is > available, and gives the problem I've described here. The only way in the > past to get the correct mouse behavior, however, was to use the traditional > "mouse" driver, with the evdev protocol (the first configuration block listed > in this bug report). This configuration yields the following error:
Sorry, I misread the second half of your report, my faul entirely. Your new configuration that works is correct. The support for evdev currently removes evdev support specifically from the mouse driver and places it instead in its own evdev driver. This driver doesn't have all the options that the mouse driver has, specifically the ZAxis and ButtonMapping options that you use. I don't know if it makes sense to include these options in the evdev driver, since it's a generic input device driver, but I'll ask upstream. Currently, if you want to use the evdev driver and do your mouse button mappings, xmodmap is probably the way to go. Alternately, you could figure out why the mouse driver isn't working for you. - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
