Date: Sun, 21 Jun 1998 22:32:13 -0400 (EDT) From: Greg <gpavelcak@philos.umass.edu> To: "Daniel O'Connor" <doconnor@gsoft.com.au> Cc: freebsd-multimedia@FreeBSD.ORG Subject: Re: Quake2 and bad system call Message-ID: <Pine.BSF.3.96.980621221346.5512A-100000@tower.my.domain> In-Reply-To: <199806220130.LAA14918@cain.gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> > I've had Quake2 (That is QUake2-3.13 with 3.14a and 3.15a > > subsequently expanded on top) fail with "bad system call" on > > -current from early April and on -current from about 5/20. > > Just wondering if anyone has a fix for this. I've seen the same > > problem reported in the archives but didn't see a solution. On Mon, 22 Jun 1998, Daniel O'Connor wrote: > Hmm.. Do you have shared memory installed on your system? If having "options SYSVSHM" in my kernel accomplishes that, then the answer is yes. > I know Quake 2 uses shared mem when in X11 mode, and possibly uses it for GL > rendering.. > Just for more info: -I am just trying to get it working on X11, not GL-Quake. -I have tried specifying "+set vid_ref softx", but that didn't help. -I updated my -current again recently (Fri. 6/19), but that didn't help either. I didn't really think it would. -If it helps, while my xterm says "bad system call", the console says "/kernel: pid 7517 (quake2), uid 65535: exited on signal 12" Thanks. Greg 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?Pine.BSF.3.96.980621221346.5512A-100000>