Date: Thu, 23 Sep 1999 10:30:28 +0200 (CEST) From: Marc van Woerkom <van.woerkom@netcologne.de> To: reg@shale.csir.co.za Cc: vallo@matti.ee, aa8vb@ipass.net, multimedia@FreeBSD.ORG Subject: Re: Hardware 3D for FreeBSD (was Re: tee-ing a sound stream) Message-ID: <199909230830.KAA00771@oranje.my.domain> In-Reply-To: <19990923001906.C32068@shale.csir.co.za> (message from Jeremy Lea on Thu, 23 Sep 1999 00:19:06 -0700) References: <199909190024.RAA29548@rah.star-gate.com> <199909190034.CAA02916@oranje.my.domain> <14308.15475.162264.375285@avalon.east> <19990919231119.A1295@ipass.net> <199909210812.KAA00797@oranje.my.domain> <19990921214256.A11482@ipass.net> <19990922190646.A91854@myhakas.matti.ee> <199909222342.BAA00801@oranje.my.domain> <19990923001906.C32068@shale.csir.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
> I built Mesa-3.0 and GLX straight from the (GLX modified) ports on > http://www.freebsd.org/~3d/, with no patches of my own (well except for > tweaking the glx port's PLIST), and everything is working great. PLIST and package building is something I want to straighten at the weekend, so our present ports iron man Chris Piazza has less head pain commiting. Had some mails with Ralph Giles from openprojects about the present state of glx. He has recommended porting to Mesa-3.1 (which turns beta these day) first, and then updating to latest glx, because they are in a clean up process, however there is a slightly newer version i should update to - before their move to the G400 WARP support code. > I've had two random lock-ups from my box in the last 72 hours though. > Once while in a GLX screensaver module from xscreensaver and the other > while display was blanked by DPMS (no xscreensaver running - but I had > been running some GLX tests before, teting a new version of the giram > port). Both times the box was completely ilde, and these could be > related to any number of other things like -CURRENT, RTC breakage on ASUS > P2B-DS boards, up to and including the fact that this is an overclocked > dual Celeron system... But then I named this box 'magma' for a > reason... At present I know of two problems: 1. A memory problem RIVA GLX Version = 1.0 Creating new client: 10! Adding client as resource: 578813952! ### Creating new xsmesa context... ### Creating new xsmesa context... ### Creating new xsmesa context... ### Creating new xsmesa context... destroying a client: 578813952! Xalloc error: Header corrupt in Xfree() :-( destroying a buffer destroying a buffer 2. Switching between text mode and graphics mode while an OpenGL animation is running (ctrl-alt-f1 / to text <-> alt-f4 / to XF86_SVGA) will not switch back properly to graphics mode, but instead drops to a text mode. Mails exchanged with syscons and glx folks suggest that this might a failure in the glx module However I don't want to put too much time in hunting these, because the openprojects glx code is expected to be replaced by the GLX implementation SGI has released... catching up to Mesa-3.1 makes a bit more sense, as this lib will stay with us for while. Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909230830.KAA00771>