> > What kind of framebuffer ? Matrox ? VESA ? KGIcon based ?
> It's VESA framebuffer.
Please check if that really is the case. VESAfb needs to be activated at
boot time, so this is a common misunderstanding. Do you have a "rectangle"
cursor (i.e. not the blinking line HW-cursor ?).
> > > When libggi's using framebuffer (console under framebuffer),
> > > horizontal and vertical frequency of display does not match
> > > to my monitor :(
That should not happen on VESAfb. VESAfb cannot change modes at all.
So chances are, that LibGGI is trying to use some ither target (SVGAlib ?)
which screws things up.
> > You need to set up /etc/fb.modes.
No need for VESAfb, you can't change modes anyway.
> I don't have such file :(
fbset is used to generate it. fbset comes with LibGGI.
> > Please turn on GGI_DEBUG=255.
> How?
When starting a program, say "demo", do it like this:
bash$ GGI_DEBUG=255 ./demo
> What it gives?
Lots of debug info that will help us to track dwon your problem.
> > If it the displays:
> > display-fbdev: cannot get timing from /etc/fb.modes. Just hoping it works.
> No. It doesn't display anything, just runing program.
It will, if you enable GGI_DEBUG=255.
> Actually I see nothing what's happening after runing application :(
> > It probably invokes SVGAlib, then, which seemingly doesn't work correctly
> > for your card.
> I have diamond viper v550 (16MB AGP)...
I have no idea what that card uses as its chipset. Please send us the
contents of /proc/pci.
> Do I have to change my graphic card?!
Well - if you are content with VESAfb or find a good driver or are willing
to write one, probably not.
> > /etc/fb.modes unset or SVGAlib being engaged, when no fbcon is found
> Yes, I have VESAfb...
> I don't have file /etc/fb.module (or any similiar) :(
> Do I need some libraries, or program (fbcon)???
fbset. It comes with LibGGI snapshots. However that will still not allow
to change modes.
> What works? My program? Yeah, my first program draws dot sinus ;)
> When I'm trying to set mode for example 640x480, while my console
> is 800x600 an error occures :(
> But if I'm setting 800x600, or GGI_AUTO everything's OK...
Yes. This is a limitation of VESAfb.
> > What driver are you using ? If you use VESAfb, this is normal. VESAfb sets
> > up the resolution while still in Realmode using BIOS calls. Resolution is
> > fixed after boot.
> I'd like my applications to be independent of machine...
> If someone would use VESAfb 640x480, but my applications need 800x600,
> the program won't run :(
No - the program should adapt to available resolution, if at all possible.
Thus using GGI_AUTO whereever possible is recommended.
> What kind of framebuffer can change it's resolution not at boot time?
Anything but VESAfb.
> My kernel (2.2.14 i386) supports also matrox framebuffer, but I think
> it's only for matrox's cards?
Yes. We'll have to figure out your chipset first, to see what might be
suitable for your card. Brand names unfortunately mean nothing.
Companies even tend to sell different hardware under the same name.
> Where can I get KGIcon framebuffer and it's specification?
It should come with every LibGGI snapshot as available from our webpages.
CU, ANdy
--
= Andreas Beck | Email : <[EMAIL PROTECTED]> =
