Index: [thread] [date] [subject] [author]
  From: Andrew Apted <ajapted@netspace.net.au>
  To  : ggi-develop@eskimo.com
  Date: Sun, 13 Jun 1999 23:20:12 +1000

Re: GGI Problems

Ketil Froyn writes:

>  LibGGI: display-fbdev: checkmode 0x0#0x0F0[0x1001004]
>  LibGGI: display-fbdev: result 0 80x30#80x30F1[0x1001004]
>  LibGGI: display-fbdev: setmode 80x30#80x30F1[0x1001004]
>  LibGGI: display-fbdev: cannot get timing from /etc/fb.modes. Just hoping
>  it works.
>  display-fbdev: FBIOPUT_VSCREENINFO: Invalid argument
>  LibGGI: Failed to set mode: [T4/16]
>  LibGGI: ggiSetMode: done!
>  
>  What is mode [T4/16]?
 
Text mode (4 bits of color, 16 bit "pixels").  Normal fbdev drivers in
the kernel can't do text modes, because there is no API for setting
different types of modes (only different bit depths).  [For KGICON, we
use a massive hack where bpp=13 means text mode].

What's the program ?

>  Finally I'm getting:
>  LibGGI SVGAlib-wrapper: 320x200.V320x200.F1.D1x1.[P8/8]
>  Terminating on signal 11
>  LibGGI: display-fbdev: GGIdlcleanup start.
>  
>  What happened here?
  
Something bad :).  Most likely either the svgalib-wrapper or the program
in question tried to draw outside the mmap'ed framebuffer.

Cheers,
___________________________________________________
                                               \  /
  Andrew Apted   <ajapted@netspace.net.au>      \/
 

Index: [thread] [date] [subject] [author]