Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 1 Dec 2003 16:28:08 +0200
From:      Ion-Mihai Tetcu <itetcu@apropo.ro>
To:        Laurent Demaret <laurent.demaret@free.fr>
Cc:        freebsd-newbies@freebsd.org
Subject:   Re: Console ps2 mouse behavior control (was : Re: test)
Message-ID:  <20031201162808.42f45f14.itetcu@apropo.ro>
In-Reply-To: <D702AD3C-235E-11D8-A803-000393A95684@free.fr>
References:  <20031130153549.7a34a835.itetcu@apropo.ro> <D702AD3C-235E-11D8-A803-000393A95684@free.fr>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 30 Nov 2003 18:58:44 +0100
Laurent Demaret <laurent.demaret@free.fr> wrote:

> 
> Hello,
> 
> 
> >> Well hi firstly make sure /etc/rc.conf does set
> >> Emulate3Buttons=yes...YOu didnt specify what mouse you have...
> >                         ^^^^^^^^^^^^
> > So how do you know ?
> It is a ps2 mouse 5 buttons with its clicking wheel
> 
> >
> >> Auto
> >> works fine mos t of the time.
> It does not for me, specially in console mode : when running sysinstall 
> test mouse configuration any move of the mouse close and open several 
> times that dialogue same way if I taped enter on the keyboard. Wich 
> should not be as the others (non auto) protocols do not act that way.
> I verified mouse cable connection wich could give also such a behavior 
> but it did not change anything.

So your problem is clearly not in X config.
 
> >> If you wan mouse wheel add this to
> >> XF86Config
> >>
> >>     Identifier  "Mouse1"
> >>     Driver      "mouse"
> >>     Option "Protocol"    "Auto"
> >>     Option "Device"      "/dev/sysmouse"
> >>     Option "ZAxisMapping" "4 5"
> >>     Option Emulate3Buttons "no"
> >>
> Excepted I leaved Mouse0 that's exactly my /etc/X11/XF86Config file.
> 
> And what I am looking for is a correct behavior of the mouse even in 
> console mode (before starting XFree).

correct.

> > it# cat /etc/rc.conf | grep moused
> > moused_enable="YES"
> > moused_flags="-z 4"
> > moused_type="auto"
> 
> cat/etc/XF86Config | grep moused
> moused_enable="YES"
> moused_port="/dev/psm0"
> moused_type="ps/2"
> moused_port="/dev/psm0"
> mousedd_type="mousesystems"
> moused_enable="YES"
> moused_type="NO"
> moused_enable="NO"
> moused_port="/dev/psm0"
> mousedd_type="mousesystems"
> moused_enable="YES"
> moused_flags=""
> moused_port="/dev/psm0"
> mousedd_type="intellimouse"
> moused_enable="YES"
> 
> I presume the last three lines are the executed ones ?
> And sure I need to clean that file.

Clean it up. Either delete the lines or comment them out by putting an #
before them.

> > and
> >
> > it# cat /etc/X11/XF86Config | grep -A4 Mouse
> >     Identifier  "Mouse1"
> >     Driver      "mouse"
> >     Option "Protocol"    "Auto"
> >     Option "Device"      "/dev/sysmouse"
> >     Option "Buttons" "5"
> 
> cat /etc/X11/XF86Config | grep mouse
> Driver		"mouse"
> Option		"Device" "/dev/sysmouse"
> 
> That's all I get, 

Yes, the -A4 tell grep to also get the 4 lines after the mach. You
could also use -C which stands for context and -B for before. 

> using ee I can tell you
> 
> ee /etc/X11/XF86Config
>      Identifier  "Mouse0"
>      Driver      "mouse"
>      Option "Protocol"    "MouseSystems"
>      Option "Device"      "/dev/sysmouse"
>      Option "Buttons" "5"
> 
> But the bad behavior is not only in XServer but in console mode.
> 
> 
> > it# dmesg | grep psm
> > psm0: <PS/2 Mouse> irq 12 on atkbdc0
> > psm0: model IntelliMouse, device ID 3
> 
> dmesg | grep psm
> psm0: <PS/2 Mouse> irq 12 on atkbdc0
> psm0: model 4D+ Mouse, device ID 8


 
> > Note: this should go on questions@, please follow up there.
> Well what is a newbie then ?
> I would be afraid to do such bad things than no 72 caracters lines ;-/ 
> or even worst (I'm able for worst)

:) well, the newbies list is more a social list that a technical one ...
And you have more chances to get help on questions.


-- 
IOnut
Unregistered ;) FreeBSD user



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031201162808.42f45f14.itetcu>