Thanks for the tips. It looks like upgrading to 4.2.0 (and using the new
s3virge driver) seems to have done the trick (so far).
One thing I did notice is that "XF86Setup" terms with a segfault. Looks
like a database is corrupt?
blackjack:~# XF86Setup
Warning CHIPSET specification missing in
At 08:44 AM 6/3/2002 +0100, Dr Andrew C Aitchison wrote:
>Eric N. Valor wrote:
> > I've tried stepping through the archives, but the lack of a search
> > engine means that I have to manually parse 80+ megs of information
> > (this takes a human quite a long time).
>
>Have you tried using somethin
Eric N. Valor wrote:
> I've tried stepping through the archives, but the lack of a search
> engine means that I have to manually parse 80+ megs of information
> (this takes a human quite a long time).
Have you tried using something like google to search through the
archives ? I've found that w
I'm reposting to see if anyone has any input on this. For more
information, the card is using the S3 Virge/GX2 chip. I've tried stepping
through the archives, but the lack of a search engine means that I have to
manually parse 80+ megs of information (this takes a human quite a long time).
(sorry for the cross-post, but I'm not sure which is the best list for this)
I have a Number Nine Reality 334 (4mb, AGP) which I'm trying to run with
Debian (Woody). I've set the resolution to 1024x768 at 16bpp. Everything
seems to work fine except when I try to pop open an Xterminal. At th
