On Sun, Oct 10, 1999 at 09:47:35PM +0200, Andreas Beck wrote:
> > Do you mean a nonworking SVGAlib target for libggi?
> Right. However an unresponsive terminal is usually only encountered when
> using a nonworking SVGAlib, so that was my first guess.
>
> No, a nonworking SVGAlib. Our target works nice, but many systems have
> problems with SVGAlib. However, as you have not installed the target, LibGGI
> will never touch SVGAlib, so that possibility is ruled out.
I still do not understand what you mean under `a nonworking svgalib'. The
svgalib I have on my computer works. :) I've got few programs that make use of
it (directly) and they work just fine.
> Good. That will rule out much of the possible mode negotiation and other
> compatibility problems, as if any X application works, the x target should
> also work. If it does not, it indicates a major problem with the XGGI
> installation.
OK. The x taget works just fine. I tried to program peggy, and it showed a nice
X-window with a picture in it.
> > > Then check, that you are really on a fbcon system. Does e.g. cat </dev/fb
> > > >/dev/null work ?
> > It looks like I do not have this device. I do have a whole bunch of /dev/fb?*,
> > but no /dev/fb. This could be the reason.
>
> No. We actually try /dev/fb0. Try with that one, please. Sorry, I have that
> symlink ... my fault.
Well, here we've got a problem. The perms for /dev/fb* are root:tty rw--w--w-.
As result, cat /dev/fb0 > /dev/null does not work. I tried to add sufficient
permissions (rw-rw-rw-), and cat (surprise!, surprise!) works. :) But it did not
change the situation with peggy program.
Now, the most important. :) I've attached two files (log and log2). The first
was created by:
$ strace -o log ./peggy path/to/picture
[ a pause in front of empty screen ]
[ magic-K! ]
The second one -- by:
$ GGI_DEBUG=255 ./strace -o log2 ./peggy path/to/picture
$ echo $?
0
$
I checked the first log file and here is my question: what is kgi? Do I have
to install it?
--
Mike
log.gz
log2.gz
