From owner-freebsd-x11@FreeBSD.ORG Thu Dec 30 10:00:09 2004 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EBBD116A4CF for ; Thu, 30 Dec 2004 10:00:09 +0000 (GMT) Received: from mail1.sciant.com (mail1.sciant.com [62.73.65.35]) by mx1.FreeBSD.org (Postfix) with SMTP id A4E3F43D54 for ; Thu, 30 Dec 2004 10:00:08 +0000 (GMT) (envelope-from kiril.anastasov@sciant.com) Received: (qmail 5751 invoked by uid 1008); 30 Dec 2004 10:00:16 -0000 Received: from kiril.anastasov@sciant.com by mail1 by uid 1001 with qmail-scanner-1.22-st-qms Clear:RC:1(172.16.16.35):. Processed in 0.092023 secs); 30 Dec 2004 10:00:16 -0000 Received: from unknown (HELO wdc.sofia.wizcom.bg) (172.16.16.35) by mail1.sciant.com with SMTP; 30 Dec 2004 10:00:16 -0000 content-class: urn:content-classes:message MIME-Version: 1.0 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Thu, 30 Dec 2004 12:00:06 +0200 Message-ID: <6F96D78604050B4F80E0AB2F9B1426AF010C5BB7@wdc.sofia.wizcom.bg> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re:[SOLVED] Dri on ati rage128 does not work after xorg 6.8.1 upgrade. Thread-Index: AcTuVlbqSjpvI1iPRl2pfTCaRIYoyA== From: "Kiril Anastasov" To: Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: Jung-uk Kim Subject: Re:[SOLVED] Dri on ati rage128 does not work after xorg 6.8.1 upgrade. X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 10:00:10 -0000 > Your Xorg.0.log shows DRI enabled, which means that you're most of the = > way there.=9A The next step is the glxinfo output.=9A However, you = need=20 > LIBGL_DEBUG=3Dverbose set in your environment for glxinfo to be of use = > in debugging.=9A (If capturing the output to send, note that the=20 > important lines are output to stderr) =20 This showed that the WRITE_DEPTH is unresolved external. =20 > Mesa source doesn't seem to include this fix: >=20 > = http://freedesktop.org/cgi-bin/viewcvs.cgi/mesa/Mesa/src/mesa/drivers/dri= /common/depthtmp.h?r1=3D1.4&r2=3D1.5 >=20 > From the commit log you said: >=20 > 'Don't compile WriteMonoDepthSpan if HAVE_HW_DEPTH_SPANS is defined -=20 > it won't be used in that case, and it wanting WRITE_DEPTH was making > r128 die on the undefined symbol.' =20 And this fixed the problem. =20 Thanks guys. =20 Kiril Anastasov