From owner-freebsd-hackers@FreeBSD.ORG  Sat Aug 30 18:16:44 2003
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 11ABE16A4C1
	for <hackers@freebsd.org>; Sat, 30 Aug 2003 18:16:44 -0700 (PDT)
Received: from priv-edtnes46.telusplanet.net (defout.telus.net
	[199.185.220.240])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2B4814400B
	for <hackers@freebsd.org>; Sat, 30 Aug 2003 18:16:41 -0700 (PDT)
	(envelope-from s.gecko@telus.net)
Received: from [192.168.10.2] ([216.232.224.119])
	by priv-edtnes46.telusplanet.netESMTP
	<20030831011640.WEJW11996.priv-edtnes46.telusplanet.net@[192.168.10.2]>
	for <hackers@freebsd.org>; Sat, 30 Aug 2003 19:16:40 -0600
From: Stone Gecko <s.gecko@telus.net>
To: hackers@freebsd.org
Date: Sat, 30 Aug 2003 18:16:40 -0700
User-Agent: KMail/1.5.2
Organization: StoneGecko Technical
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200308301816.40115.s.gecko@telus.net>
Subject: refreshing AGP Card Memory??
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Aug 2003 01:16:44 -0000

I have a GF4 MX440 Video card in 5.1_Release running KDE3.1.3 that keeps 
either locking up or putting vertical red/blue lines on the screen. 

Is there any way to manually refresh or repage the memory to see if that helps 
stop the problem? maybe a cron script?

any ideas? did the same with 4.8 Stable

thanks