From owner-freebsd-questions Thu Jul 6 17: 6:45 2000 Delivered-To: freebsd-questions@freebsd.org Received: from wilsonandhorton.co.nz (fw2.wilsonandhorton.co.nz [203.99.66.4]) by hub.freebsd.org (Postfix) with ESMTP id 6708837BADD for ; Thu, 6 Jul 2000 17:06:34 -0700 (PDT) (envelope-from jonc@itouch.co.nz) Received: (from jonc@localhost) by wilsonandhorton.co.nz (8.9.3/8.9.3) id MAA01560; Fri, 7 Jul 2000 12:05:47 +1200 (NZST) (envelope-from jonc) Date: Fri, 7 Jul 2000 12:05:47 +1200 From: Jonathan Chen To: Ruslan Ermilov Cc: freebsd-questions@FreeBSD.ORG Subject: Re: intel chipset810 Message-ID: <20000707120547.B1324@jonc.ntdns.wilsonandhorton.co.n> References: <000501bfe707$07340420$5920fea9@home> <20000706120723.C28850@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000706120723.C28850@sunbay.com>; from ru@sunbay.com on Thu, Jul 06, 2000 at 12:07:23PM +0300 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 06, 2000 at 12:07:23PM +0300, Ruslan Ermilov wrote: [...] > Doug Rabson and I are (slowly) working on this driver. > At the moment I have XFree86 3.3.6 running on an i810 chipset. But the > driver is still incomplete and requires more testing. More power to you both! > But it is possible to run XFree86 3.3.6 without the kernel driver. > You will need to compile from the latest ports/x11/XFree86, have the > I810_UNSUPPORTED_GTT_FALLBACK environment variable set, and have the > following section in your XF86Config: > > : Section "Device" > : Identifier "i810" > : Option "no_accel" > : EndSection Yeah. Well. I'm running 4.0-stable, and doing this *almost* makes it on the way up; but I get a core-dump just before I get a working screen. :-( Here's hoping you get the kernel driver support in. Cheers. -- Jonathan Chen | To do is to be -- Nietzsche | To be is to do -- Sartre | Scooby do be do -- Scooby To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message