Hi !

> and libgii0{,-dev} (as it seems to be necessary according to dependancies). 

Yes. Looks good.

>     vesafb: mode is 1024x768x16, linelength=2048, pages=0
>     Console: switching to colour frame buffer device 128x48

O.K. - also looks good.

> > SVGAlib, which only happens as "last-resort", i.e. when the framebuffer
> > device does not work as expected.
> I do not think it's ever possible as I have not installed 
> libggi-target-svgalib.

Right. However an unresponsive terminal is usually only encountered when
using a nonworking SVGAlib, so that was my first guess.

> > That doesn't sound like fbcon at all. A nonworking SVGAlib usually causes
> > this.
> Do you mean a nonworking SVGAlib target for libggi? 
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.

> > First check that your LibGGI distribution is intact. For this, start X and
> > run a GGI demo under X. It should pop up in an X window. If that doesn't
> > happen, something is wrong with the LibGGI installation.
> Hmm...  This means I should install x-target, I will try.

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.

> > 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.

> > At that stage, there should at least be no more lockups. If there are still
> > problems, run the "demo" application with "bash$ GGI_DEBUG=255 ./demo".
> This one just core dumps (I tried it before sending my plea for help :).

Oh - that seems like a major problem with the LibGGI installation. It dumps
core before giving a single line of debug info ?
Try finding out where it dumps (strace, gdb) or install a source
distribution of LibGGI, as this will rule out any binary incompatibilities.

CU, Andy

-- 
= Andreas Beck                    |  Email :  <[EMAIL PROTECTED]> =

Reply via email to