Date: Fri, 23 Jun 2000 14:33:22 +0200 From: Graham Wheeler <gram@cequrux.com> To: Greg Work <Greg@FatCanary.com.au>, freebsd-stable@freebsd.org Subject: Re: Console switching woes remain Message-ID: <cdea5e9fdce33feb698ee8609ac9125e@cequrux.com> References: <9c983121ea800eab2aa666dfad50cd16@cequrux.com> <001d01bfdd06$e94022a0$0200a8c0@gwork.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- Dr Graham Wheeler E-mail: gram@cequrux.com Director, Research and Development WWW: http://www.cequrux.com CEQURUX Technologies Phone: +27(21)423-6065 Firewalls/VPN Specialists Fax: +27(21)424-3656 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cdea5e9fdce33feb698ee8609ac9125e>