From: Ketil Froyn <ketilf@ifi.uio.no>
  To  : ggi-develop@eskimo.com
  Date: Mon, 28 Jun 1999 11:38:34 +0200 (MET DST)

Re: ggi acting up solved

On Mon, 28 Jun 1999, Andreas Beck wrote:

> > > DirectBuffer means direct access to the framebuffer. This is only
> > > supported for the Glide target in recent snapshots.
> > In ggi, xggi or glide? :) Just wondering which one I'm looking forward to
> > downloading :)
> GGI. IIRC you already are using Beta2.1 or newer, so xggi should be fine.
> And AFAIk Glide was always up to that.

You recalled correctly. But does that mean that I should be able to run
xggi on the glide target? Cos xggi dies and complains that it can't access
the framebuffer (or something like that, it is a framebuffer thing).

> Note, that the VooDoos are not quite optimized for DB access.

The hardware or glide or ggi? :)

> > Also, I was wondering about a few other things... Can only root use the
> > glide target? What about /dev/3dfx? I have it, but demos core dump(!) when
> > I try to run them as me.
> That's strange. This could be a problem with VT-switching or needing
> root-access to use the keyboard. Could you run the core file through a
> debugger to see where it dumps ? And/or make GGI_DEBUG=255 logs and strace
> logs ?

I'll have a look at it.

BTW, is there some way to run quake fullscreen using GGI? I've tried
squake, but that seems to be hardcoded to use the libc-version of
libvga.so.1... Symlinking did not remedy this.

Ketil Froyn
--
He who Laughs, Lasts.

http://www.ifi.uio.no/~ketilf/       
mailto:ketilf@ifi.uio.no