Re: logitech cordless optical mouse problems...

On 2004.01.01 09:41:43 +0200, Evren Yurtesen <yurtesen_at_ispro.net.tr>
wrote:

> How do you use the PS/2 converter of the mouse? When I only connect
> the PS/2 converter nothing works. (Unless if I also connect the USB
> which defeats the purpose.)

The cable on your receiver ends in a Y with a USB cable and a PS/2
cable with a green connector, and the kit comes with a purple
USB-to-PS/2 adaptor, correct?  If I had to guess I'd say you either
connect JUST the USB -OR- you attach the purple adaptor to the USB cable
and plug it and the green PS/2 connector into their corresponding PS/2
ports.  You need to read through the instruction booklet to determine
the proper connections.  Connecting them improperly could do real damage
(like shorting the USB and PS/2 ports together).


That aside, this is a general mouse configuration recipe:

Enable moused if you want console mouse functionality (non-X).  If you
have a USB mouse, put usbd_enable="YES" in /etc/rc.conf.  If you have a
PS/2 mouse, put moused_enable="YES" in /etc/rc.conf.  Moused is entirely
unnecessary for X, but the linear acceleration is useful if you need it.

Edit /usr/X11R6/etc/X11/XF86Config.  Find the InputDevice section for
the mouse, and make it look something like this:

Section "InputDevice"
  Identifier	"cordless_mouse"
  Driver	"mouse"
  Option	"Protocol"		"auto"
  Option	"Device"		""
  Option	"Emulate3Buttons"	"off"
  Option	"Buttons"		""
  Option	"ZAxisMapping"		"4 5"
EndSection

If you enabled moused put /dev/sysmouse in the empty double quotes at
the end of the Device option line.  Otherwise, put the actual device
of your mouse.

Count the buttons on your mouse, a scroll wheel counts as three.  Put
that number in in the empty double quotes at the end of the Buttons
option line.

Start X.  Run `xev -display 0:0` from an xterm.  Make sure you can see
the Event Tester window and the xterm, put the cursor in the Event
Tester window that opens and click every button and click and
scroll the wheel.  You may want to pick the mouse up to do this to
avoid movement events.  Each click/scroll should produce an output like
this:

ButtonPress event, serial 22, synthetic NO, window 0x2400001,
    root 0x48, subw 0x0, time 5735091, (94,97), root:(1192,117),
    state 0x10, button 1, same_screen YES

ButtonRelease event, serial 22, synthetic NO, window 0x2400001,
    root 0x48, subw 0x0, time 5735791, (94,97), root:(1192,117),
    state 0x110, button 1, same_screen YES

Note what button number gets reported for each click.  This is the
assignment order you should get:

left button: 1
right button: 3
middle/wheel button: 2
scroll up: 4
scroll down: 5

For left-handed use, swap the left and right button assignments.  If you
don't get an event pair for a button, try bumping up the Buttons number
to something large, like 10.  If you get a different order, you'll need
to remap the buttons using Xmodmap.  Using Xmodmap is a bit more
involved and how it gets used depends on how you start X, so I'll only
provide it if necessary.