Index: [thread] [date] [subject] [author]
  From: teunis <teunis@computersupportcentre.com>
  To  : GGI Developers <ggi-develop@eskimo.com>
  Date: Wed, 26 May 1999 02:35:23 -0700 (MST)

Re: GGI S3 ViRGE drivers (fwd)

forwarding on request

---------- Forwarded message ----------
Date: Mon, 24 May 1999 23:34:56 -0400 (EDT)
From: Matt Martin <matt@calvin.sfc.lehigh.edu>
Reply-To: matt.martin@ieee.org
To: teunis <teunis@computersupportcentre.com>
Cc: Matt Martin <mmartin@calvin.sfc.lehigh.edu>
Subject: Re: GGI S3 ViRGE drivers


Well, the chip is an S3-ViRGE (don't know beyond that...) and the
code was straight from CVS.

Could you possibly cross-post this....I am not a member of the list.

> Yes actually that DOES mean a bug in the initialization code.
> (btw - you should probably mail to the ggi-developers list as I'm not
> maintaining anything anymore *sigh*)
> 
> Anyways, which S3 do you have?  I'm running an S3-ViRGE/GX (or DX?) and it
> operates 100% (as long as I don't load XFree86 that is).
> 
> Please tell me which chipset you have?  I'm not sure who's maintaining the
> chipset right now though.
> 
> BTW - Are you running the latest CVS?  The archived drivers for S3 have
> had problems IIRC..  Which version are you running?
> 
> G'day, eh? :)
> 	- Teunis
> 
> On Fri, 14 May 1999, Matt Martin wrote:
> 
> > Hello Teunis,
> > 
> > Got your name from the ggi developers page, I hope you are the
> > correct person to contact.
> > 
> > Was trying out the kgicon driver for s3 ViRGE and found out the hard
> > way about locking the system (sometimes) when the module loads, as
> > mentioned in the mailing list archive.
> > 
> > One thing I noticed quite by accident was this: 
> > 	If I am running an X-Server on another virtual terminal and
> > I insert the module, the system does not freeze.  The screen goes
> > white with a blinking black cursor.  I can then switch virtual terms
> > (NOT to the one with X on it) and the text becomes readable.  Then I
> > can switch runmodes or otherwise kill the X-Server and everything
> > works reasonably well. (cube3d, XGGI, etc)
> > 
> > Does this point to some kind of bug in the initialization of the chip?



 Matt Martin
matt.martin@ieee.org

Lehigh U. Microelectronics Research Lab        "The Clubhouse"
16A Memorial Dr. E., Bethlehem,PA,18015      126 East 4th St.
mmartin @ calvin.sfc.lehigh.edu              Bethlehem, PA,18015-1702
Work:(610) 758-3951 (Office)                    MGM1 @ LEHIGH.EDU
              -4518 (Lab)                    Home: (610) 758-9662
 WWW: http://www.lehigh.edu/~mgm1/mgm1.html  AIM ID: MmAaRtTtIN
    PGP Public key at "finger mmartin@calvin.sfc.lehigh.edu"


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