>You are probably making the classic error of telling the X server that 
>your mouse is a PS2 protocol mouse in the XConfig, which is wrong,
>since the PS2 driver we use turns the mouse events into standard mouse 
>events.

Is there a particular reason the PS2 driver enables this classic error?
Is the PS2 protocol particularly deficient, or was this an attempt to
reduce confusion (by having only one protocol) which winds up enhancing
confusion (since the primary consumer of mouse events, X, documents a
separate protocol for PS/2 mice)?