From owner-freebsd-bugs  Mon Feb 10 19:21:08 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA07390
          for bugs-outgoing; Mon, 10 Feb 1997 19:21:08 -0800 (PST)
Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA07381
          for <freebsd-bugs@freebsd.org>; Mon, 10 Feb 1997 19:21:05 -0800 (PST)
Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by nasu.utsunomiya-u.ac.jp (8.8.4+2.7Wbeta4/3.5Wpl3) with ESMTP id MAA15205; Tue, 11 Feb 1997 12:20:54 +0900 (JST)
Received: from zodiac.mech.utsunomiya-u.ac.jp (+eHOXEMpiXu1rDM5rgLok14KkrM+l/jj@zodiac.mech.utsunomiya-u.ac.jp [160.12.33.1]) by outmail.utsunomiya-u.ac.jp (8.8.4+2.7Wbeta4/3.5Wpl3) with ESMTP id MAA30260; Tue, 11 Feb 1997 12:20:49 +0900 (JST)
Received: from zodiac.mech.utsunomiya-u.ac.jp (zenith.mech.utsunomiya-u.ac.jp [160.12.33.60]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP
	id MAA00887; Tue, 11 Feb 1997 12:24:39 +0900 (JST)
Message-Id: <199702110324.MAA00887@zodiac.mech.utsunomiya-u.ac.jp>
To: Zach Heilig <zach@blizzard.gaffaneys.com>
cc: freebsd-bugs@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: Re: moused and X11R6 
In-reply-to: Your message of "10 Feb 1997 12:41:29 CST."
             <87g1z47bc6.fsf@murkwood.gaffaneys.com> 
References: <876804rsia.fsf@murkwood.gaffaneys.com> <Pine.BSF.3.95.970207222919.2151A-100000@chaos.ecpnet.com>
	 <19970208165555.12961@usn.blaze.net.au> <87bu9venx6.fsf@murkwood.gaffaneys.com>
	 <19970208201732.37402@usn.blaze.net.au>  <87g1z47bc6.fsf@murkwood.gaffaneys.com> 
Date: Tue, 11 Feb 1997 12:24:23 +0900
From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


>I'm pretty sure I tracked down my problem.  moused & X are working
>together nicely again.  The problem seemed to be that I had typed:
>
>vidcontrol -m on
>
>in the virtual terminal that was later used to run X.  Problems went
>away after I thought of that and turned it off...

Hmmm. I experimented this; I did

vidcontrol -m on

in a virtual terminal, then from within the same terminal, I started X. 
The X server switches to an unused virtual terminal (this is the way it
works) and my mouse works fine there.  I switch back to the virtual
terminal on which I run vidcontrol, the terminal shows some lines from
the X server AND the mouse cursor.  I can move the mouse cursor and
mark region in the screen with no problem.

I even did `vidcontrol -m on' in yet another virtual terminal, and it
works. No conflicts.

My understanding is that the sysmouse driver, which is actually a part
of the syscons driver, feed mouse data only to the foreground virtual
terminal. So, there should be no conflict, whether `vidcontrol -m on'
in any of the virtual terminals or not.

I may be wrong and I may be just fortunate enough not to have trouble
with moused...

Kazu

>-- 
>Zach Heilig (zach@blizzard.gaffaneys.com) | ALL unsolicited commercial email
>Support bacteria -- it's the only         | is unwelcome.  I avoid dealing
>form of culture some people have!         | with companies that email ads.