>>>rc.i386 configuring syscons: blank_time mousedmoused: mouse type mismatch
>>>(ps/2 != intellimouse), ps/2 is assumed
>>
>> If you read the notice in the mouse configuration screen, you should
>> have understood that you should ALWAYS choose the type "Auto" for ANY
>> mouse connected to the PS/2 mouse port, regardless of the brand and
>> model of the mouse. The type "IntelliMouse" is for the SERIAL
>> IntelliMouse.
>
> On my Fujitsu Lifebook 535Tx I also set 'moused_type="glidepoint"'
>along with the 'moused_port="/dev/psm0"' in /etc/rc.conf and receive the
>abovementioned message on every reboot, BUT with such settings I can
>'tap' and receive button event where as without setting moused_type to
>glidepoint this 'tapping' not works.
I can assure you that setting `moused_type' to "glidepoint" does not
directly affect your pad device. The protocol type "glidepoint" is for
the "serial" GlidePoint. PS/2 GlidePoint should be used with
the "auto" (or "ps/2").
When moused finds that the user selected a protocol type which is
incompatible with the mouse driver (psm or mse), it warns the user:
moused: mouse type mismatch (XXX != YYY), XXX is assumed
Where XXX is the basic, default protocol type of the mouse driver, and
YYY is the protocol type supplied by the user. As you can infer from
the the message, moused will ignore the type supplied by the user and
use the driver's protocol instead. In you case `glidepoint' is
utterly ignored, sorry :-)
As for the `tap' feature, I assume the pad device on your notebook
computer is reporting the `tapping' action as the button 4 click. If
you want `tap' would be the button 1 click, you set
moused_flags="-m 1=4"
in your /etc/rc.conf. You may think this is arcane, but this
arrangement gives us more flexibility; believe it or not, there are
people who don't like the `tap' feature and don't want the button 1
click for `tap'.
Now, you want to ask me a question, don't you? "But `tapping' is
reported as the button 1 down on my machine without the -m option!"
This is because moused finds that a wrong protocol type is supplied,
and tries to use the "basic, default" protocol type the mouse driver
is suggesting. For the PS/2 mouse driver psm, it is the "ps/2"
protocol type which has no provision of accommodating the button 4 (tap)
status. The psm driver "automatically" maps the button 4 click to
the button 1 click when the "ps/2" protocol is being used. This mapping
is done in the psm driver and not in moused.
If no protocol type is supplied or the "auto" is specified to moused,
moused will try to use more advanced protocol type than the mouse
driver's basic default protocol. In such protocol, the button 4
status can be reported and the psm driver won't need to
map the button 4 (tap) to the button 1. That's why you thought
`tapping' didn't work when you had
moused_type="auto"
in your rc.conf.
The recommended settings for you notebook computer is
moused_type="auto"
moused_flags="-m 1=4"
You may use the "ps/2" protocol type in order to avoid setting
mouse_flags.
moused_type="ps/2"
moused_flags=""
(But, I wouldn't recommend this.)
Kazu
Kazu
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
