From owner-freebsd-multimedia Sun Jan 4 14:56:12 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA04288 for multimedia-outgoing; Sun, 4 Jan 1998 14:56:12 -0800 (PST) (envelope-from owner-freebsd-multimedia) Received: from rah.star-gate.com ([209.133.7.178]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA04283 for ; Sun, 4 Jan 1998 14:56:09 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id OAA14863; Sun, 4 Jan 1998 14:55:40 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199801042255.OAA14863@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Brian Tao cc: multimedia@FreeBSD.ORG Subject: Re: Gack, again! 3DFX cards. In-reply-to: Your message of "Sun, 04 Jan 1998 17:36:15 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 04 Jan 1998 14:55:39 -0800 From: Amancio Hasty Sender: owner-freebsd-multimedia@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I think that you need syscons since thats I am using over here. It looks like you have a problem with the Mesa library which version are you using? Cheers, Amancio > On Sat, 3 Jan 1998, Amancio Hasty wrote: > > > > Not sure whats going on;however, you are the only so far reporting > > that glquake does not work on current perhaps there are others > > having similar problem however they have not reported anything to me > > or the list. > > This is the tail end of the output when I run glquake from a text > console. The Linux Glide and Mesa libraries were installed according > to the instructions. BTW, does it matter if I'm running syscons or > pcvt? > > # ./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... > -- > Brian Tao (BT300, taob@netcom.ca) > "Though this be madness, yet there is method in't" >