On Sun, Oct 10, 1999 at 02:07:50PM +0200, Andreas Beck wrote:
> > I've succeeded to setup vesa framebuffer on my computer (2.2.10 on i386).
>
> Are you sure ?
Hmm. Let me provide you with more details than I did. :)
I am running debian potato (unstable!). At the moment I have installed all
necesary libraries: libggi2, libggi2-dev (for building those applications),
libggi-target-framebuffer, and libgii0{,-dev} (as it seems to be necessary
according to dependancies). And, as I have already said, I am running Linux
2.2.10 on Intel platform.
I believe these messages permit me to be sure that I'm using vesa framebuffer
now:
vesafb: framebuffer at 0xfd000000, mapped to 0xc4802000, size 2048k
vesafb: mode is 1024x768x16, linelength=2048, pages=0
vesafb: protected mode interface info at c000:49d0
vesafb: scrolling: redraw
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
> 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.
> Do you get a graphical console (i.e. no longer a blinking line cursor, but
> a blinking block cursor, and a non 80x25 console) ?
Yes. I am quite sure the console I have is a graphical one.
> The Vesafb must be activated with boottime arguments. This should be
> detailed somewhere in /usr/src/linux/Documentation.
It is.
> > Now I am trying to run ggi applications.
>
> >From where ? Please do not use stuff like mc. While it should still work, it
> will degrade keyboard performance. Just a hint for the future.
OK. I have plain bash (usually it's sufficient for efficient work :).
> > Every time I start such an application the console just freezes,
>
> That doesn't sound like fbcon at all. A nonworking SVGAlib usually causes
> this.
Do you mean a nonworking SVGAlib target for libggi? If yes, I think this is
the case as I have not installed appropriate package (see above).
> > and the only way for me to get out of this state is the magic button
> > called `Reset'.
>
> Did you Try MagicSysRq ? Must be enabled in Kernel. If it is, try
> Alt-PrintScreen-K (yes, 3 keys together). This should kill off all processes
> on the main console.
OK. I will enable it and try. I just did not think enabling MagicKey could be
necessary. :)
> > Could anybody tell me what exacty should be done for getting something else?
> 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.
> 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.
> If that is o.k. temporarily deinstall SVGAlib, as it usually is the cause
> for lockup-type problems.
> 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 :).
--
Mike
