Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 29 Jan 1998 19:44:51 -0500
From:      Randall Hopper <rhh@ct.picker.com>
To:        Brian Tao <taob@nbc.netcom.ca>, Amancio Hasty <hasty@rah.star-gate.com>
Cc:        multimedia@FreeBSD.ORG
Subject:   Pure3D/GLQuake (was Re: Gack, again! 3DFX cards.)
Message-ID:  <19980129194451.28252@ct.picker.com>
In-Reply-To: <Pine.GSO.3.95.980103232416.26754B-100000@tor-adm1>; from Brian Tao on Sat, Jan 03, 1998 at 11:29:43PM -0500
References:  <199801040119.RAA07678@rah.star-gate.com> <Pine.GSO.3.95.980103232416.26754B-100000@tor-adm1>

next in thread | previous in thread | raw e-mail | index | archive | help
(I know I'm 3 weeks late chiming in on this thread, but I just got to
playing with my Pure3D in FreeBSD w/ GLQuake, Mesa, et all last weekend.
Works nicely.)

Brian Tao:
 |# ./glquake
 |[...]
 |PackFile: ./id1/pak0.pak : gfx/palette.lmp
 |PackFile: ./id1/pak0.pak : gfx/colormap.lmp
 |loop 0
 |svgali vc ?? 1
 |key one 0
 |return from key init
 |./glquake: can't resolve symbol 'fxMesaCreateContext'
 |#
 |
 |    At this point, the machine is still running happily, but the
 |console keyboard mapping is completely hosed, and I have to do a
 |remote reboot to clear it up.  I wouldn't mind so much if it didn't
 |kill the keyboard...

Well, once before I had everything set up quite right I had it dump out on
me, and as you say it hosed the console leaving it in some strange mode.
Once I got setup, the same thing happened anytime I forgot to run it as
root (so glide.so could detect & get at the Voodoo board as I recall).
After I cooked a setuid-root perl wrapper script to run glquake, I haven't
had any problems since.

I'm guessing this whacked-out console state might be libvga not getting an
opportunity to reset the terminal back from that pseudo-raw mode Amancio
mentioned a while back.  But that's just a guess mind you.

Randall



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980129194451.28252>