From owner-freebsd-stable Fri Jun 23 10: 9: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from corinth.bossig.com (corinth.bossig.com [208.26.239.66]) by hub.freebsd.org (Postfix) with ESMTP id 4218C37BB6F for ; Fri, 23 Jun 2000 10:08:59 -0700 (PDT) (envelope-from kstewart@3-cities.com) Received: from 3-cities.com (unverified [208.26.241.129]) by corinth.bossig.com (Rockliffe SMTPRA 4.2.2) with ESMTP id ; Fri, 23 Jun 2000 10:10:08 -0700 Message-ID: <395399B2.937314CA@3-cities.com> Date: Fri, 23 Jun 2000 10:09:06 -0700 From: Kent Stewart Organization: BOSSig X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Graham Wheeler Cc: Greg Work , freebsd-stable@freebsd.org Subject: Re: Console switching woes remain References: <9c983121ea800eab2aa666dfad50cd16@cequrux.com> <001d01bfdd06$e94022a0$0200a8c0@gwork.org.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Graham Wheeler wrote: > > Greg Work wrote: > > > > As an idea - can you first get moused to start on bootup and make sure that > > works on the console (pre X-startup) then edit your /etc/X11/XF86Config > > file in the mouse section. Change the Option "Protocol" to "auto" and the > > Option "Device" to "/dev/sysmouse" > > > > Sorry, I guess I gave incomplete information. The mouse troubles are > independent of X; I can get the mouse to go nuts running moused as well. > In fact, I think (but I can't say for certain) that I have experienced > keyboard trouble independent of X as well. But runninng X and switching > back to a console seems to be the most reliable way of replicating the > *keyboard* trouble. Replicating the PS/2 *mouse* trouble definitely does > not require me to run X. > > The mouse, BTW, in this case is a Synaptics touchpad. I've run the psm > driver with my own patches specifically for this pad (that detect the > pad, log the model, and set appropriate sync bits given that it is a > two-button mouse which often has overflow bits set), and without those > patches; I observe the same behaviour in each case, so it isn't due to > my patches. > > It is possible, I guess, that the keyboard trouble is related to the > mouse, in that the mouse uses active PS/2 multiplexing, which may be > having some effect (I'm speculating wildly here). Active PS/2 > multiplexing allows the touchpad to continue to work even when an > external PS/2 mouse is connected. I think its a bad thing, personally - > if one plugs in an external mouse, that should be anm indication that > one wants to use the external one instead of the touchpad. > > If I get a chance to this weekend, I'm going to back it all up, install > RedHat Linux, and see if I experience any of the same problems under > Linux. This should at least help in determining whether the problem is > indeed in FreeBSD. If Linux experiences the same problems, then I'll > have to bang a lot harder on MS-Windoze, to try to make sure for once > and for all whether this isn't just flakey hardware. I thought there were some strange things that happen if you use moused and also ran x. You had problems with the mouse unless you used the sysmouse in x. This almost sounds like something similar. Kent -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://www.3-cities.com/~kstewart/index.html http://daily.daemonnews.org/ SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message