From: Matt Isleb <misleb@onshore.com>
  To  : ggi-develop@eskimo.com
  Date: Thu, 08 Apr 1999 11:37:16 -0500

Re: Riva 128 (Diamond Viper V330 AGP)

>>>> James Simmons wrote:
> On Thu, 8 Apr 1999, Matt Isleb wrote:

> Each /dev/fbX represents another video driver. If you use just vesafb then
> you have just /dev/fb0. When you insert kgicon.o you will get /dev/fb1.
> 
> > I can't perform
> > an fbset on them or run kgicon programs on them. I get "FBIOPUT_VSCREENINFO
> : 
> > Invalid arguement", vesafb complains that I can't change resolutions, then 
> the 
> > program dies. 
> 
> Yep. Vesafb CAN NOT chnage modes after booting. 
> 
> > kgicon.o says it is fb1 and there is a 
> > "1 KGI" entry in /proc/fb. But none of the devices seem to be accessing kgi
> con.
> > What major/minor does kgicon use when something like vesafb is active?
> 
> Thats right. By devices I assume you mean console. In this case /dev/fb0
> is vesafb and /dev/fb1 is kgicon. 

By devices i mean /dev/fb0, /dev/fb1 etc.
I can't do an fbset on /dev/fb1 either. And why is /dev/fb2 active??
All /dev/fb0-2 give me invalid argument when trying to set the videomode.


Matt