> I've succeeded to setup vesa framebuffer on my computer (2.2.10 on i386).
Are you sure ? Your symptoms rather sound like LibGGI accessing a nonworking
SVGAlib, which only happens as "last-resort", i.e. when the framebuffer
device does not work as expected.
Do you get a graphical console (i.e. no longer a blinking line cursor, but
a blinking block cursor, and a non 80x25 console) ?
The Vesafb must be activated with boottime arguments. This should be
detailed somewhere in /usr/src/linux/Documentation.
> 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.
> 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.
> 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.
> 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.
Then check, that you are really on a fbcon system. Does e.g. cat </dev/fb
>/dev/null work ?
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".
That should give us more information to diagnose the problem.
Eventually we will also need the results of "strace ./demo".
CU, Andy
--
= Andreas Beck | Email : <[EMAIL PROTECTED]> =
