Date: Wed, 28 Feb 96 22:24 PST From: pete@pelican.com (Pete Carah) To: support@xinside.com Cc: questions@freebsd.org Subject: Re: PS/2 Mouse and Accelerated X Message-ID: <m0ts1mk-0000SMC@pelican.com> In-Reply-To: <3131FF09.3E900E4@xinside.com> References: <199602261634.LAA29467@cray-ymp.acm.stuorg.vt.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <3131FF09.3E900E4@xinside.com> you write: >> I am having problems with my mouse pointer dying under X. I am using Xinside's >> Accelerated X 1.2C and FreeBSD 2.1-STABLE (02/24/96).. >> >> It usually happens after it makes my monitor go to sleep and I wake it up. >> Poof! the mouse is dead. A reset of the server (Ctl-Alt-BS) usually cures it, >> but sometimes it takes two or three times for it to reset. I have seen it >> lockup while it is just sitting there (no screen blank occurs) and it does >> not always lock up when the screen blanks (DPMS). >This problem is 99.99% unlikely to be anything to do with FreeBSD - so >most of you can skip the rest of this message. >Chances are that the problem is the hardware cursor code failing to >restore correctly under some conditions. We've seen a couple of >chipsets exhibit problems either because of manufacturing variations, or >because of particular combinations of resolution and refresh rate. >Can you send us the Server configuration file (usually /etc/Xaccel.ini) >and if you can, the Server text output. Details on how to grab these >can be found at ftp://ftp.xinside.com/mailserver/debug.txt . BTW, >there's also a freebsd.txt listing anything we currently know about >FreeBSD, that is not in our Release Notes. I see this problem also with a straight Xfree86 S3 server (X312B) and a PS/2 mouse; just switching away from the virtual screen and back fixes it. I don't have to wait for a screen blank; just sitting without moving the mouse for a few minutes will do it. It didn't happen with a serial mouse but I had serious jumping problems with the serial mouse as if the driver wasn't disabling the 550A fifos, so went to PS/2 mode... Thus it may not be unique to the xinside server. I'm using a Trio64 PCI Diamond board (the DRAM one with 2mb). >> Has anyone else seen this?? Is there a solution?? Yes... Unknown but I get around it easier than a total server reset (unless a virt-screen switch does a total server reset :-). -- Pete
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0ts1mk-0000SMC>