Hi,
I've recently installed NetBSD 1.5.2 on my Acer Travelmate 212TXV Notebook,
and everything works perfectly...  With the exception of mouse input.  After
researching the problem online for the past 2 days, and talking at length
with the guys in #xfree86, I've come to the conclusion that the wscons code
is frieking out a little with my integrated Synaptics PS2 Touchpad.  The
problem is that under X, the wsmouse device sends ButtonPush and
ButtonRelease events simultaneously on the physical release of the mouse
button.  This makes it incredibly difficult to drag anything in X.

Here's my setup.  I've installed XFree86 4.2.0, and am using the wsmouse
protocol to access /dev/wsmouse.  The touchpad is detected at boot as
"wsmouse0 at pms0 mux 0".  When I plug in a USB Optical Mouse, it is
detected as "wsmouse1 at ums0 mux 0" and the USB mouse works exactly as the
Touchpad does...  I can move the cursor fine, but can't drag anything.

This problem exists on the stock 1.5.2 LAPTOP kernel, as well as -current.
I used xev to diagnose what events X was recieving from the wsmouse device.
Like I said above, I can click a button, hold it for some period of time
with no output from xev, and then release the button, and xev spits back a
ButtonPush event followed by a ButtonRelease event.  Both events have
identical timestamps.

I haven't been able to diagnose the mouse in anything but X11, as I dont'
have gdm installed for the console.  I also have NetBSD running on a desktop
machine where XFree86 is using the wsmouse protocol perfectly.  Therefore,
after talking with the guys in #xfree86 at length, we came to the conclusion
that it's most likely a problem with the NetBSD wscons code and some
incompatibility with the Synaptics Touchpad.

After extensive research on google, and reading mailing lists, I haven't
been able to find anyone who has had this problem before.  I was wondering
if any of you have experieneced something similair.  Furthermore, is there a
program to diagnose what /dev/wsmouse is spitting out, much like xev does
for X11, but for the wscons kernel code?  I still need to verify that it
actually is a problem with the kernel not sending events correctly rather
than X not recieveing the events correctly.

This is the only "show-stopper" for running NetBSD on my notebook.
Everything else works like a dream, and I'm rather excited about how wscons
multiplexes mouse input.  It's so cool being able to hot-plug a USB mouse
into my notebook/desktop and have XFree86 work with it like nothing
happened.  Furthermore, everything else works perfectly, Sound, Video,
802.11b, Cardbus, DVD, even APM seems to be OK.

Any help / suggestions would be greatly appreciated.  I'd really like to get
NetBSD running on my notebook.

Thanks a bunch,
Jeff McCune