From owner-freebsd-hackers Thu Feb 20 09:24:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA24675 for hackers-outgoing; Thu, 20 Feb 1997 09:24:29 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA24666 for ; Thu, 20 Feb 1997 09:24:24 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA15442; Thu, 20 Feb 1997 10:20:49 -0700 From: Terry Lambert Message-Id: <199702201720.KAA15442@phaeton.artisoft.com> Subject: Re: Screen flickering To: regnauld@deepo.prosa.dk (Philippe Regnauld) Date: Thu, 20 Feb 1997 10:20:49 -0700 (MST) Cc: brian@awfulhak.demon.co.uk, freebsd-hackers@freebsd.org In-Reply-To: from "Philippe Regnauld" at Feb 20, 97 10:49:51 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Essentially, the syscons screen "flickers" probably every couple of > > seconds on average, and only with "vidcontrol -c destructive". From > > what I can figure, the "while (!(inb(crtc_addr+6)&8)) ;" bit in > > syscons.c doesn't work as expected (although removing it makes > > things a *lot* worse).... > > Got the same thing, except it's when I move the mouse on > the console. Config is: > > 2.2-Beta > Acer 950C P75 / 24 Mb, 800x600 DSTN -- Chips & Tech 65545 > > The screen flickers when I move the mouse in console mode > (Moused). This comes from writing non-VRAM (dual ported) card RAM with pixel values at a time when the raster beam is active, instead of waiting for vertical retrace. The typical fix is to queue draw requests to a queue, and then drive the queue off of IRQ 2, which you dedicate to the video cards vertical retrace interrupt. Alternately, you can buy a modern video card, since it will have VRAM, and writing while the raster is reading won't cause a problem. 8-). > Just for the record, this machine's PCCARD only started working when > I applied the patches for PS/2 Keyboard !! You need to specifically bug-report this; if it is repeatable elsewhere, it's a bad thing. 8-(. > And then, moused won't work with the PS/2 mouse - only with > serial mice. Look at the device node... I suspect you have created the wrong type (non-blocking vs. blocking). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.