Gabor Hetyei wrote: > > > > I have a Toshiba Satellite 2065 CDS laptop with a 20 GByte (upgraded) > harddrive, a Windows98/SuSe Linux 7.1 dual install and the Xfree 4.2.0 > downloaded and installed from the SuSe website. My laptop has an S3 Virge > MX video card. > > Since I am not really an xpert, I have only used the program sax2 > provided by SuSE to change my XFree86Config file. > > The X server runs mostly well, except for the following issue: > parts of my screen seem to get corrupted in specific situations. > For example, if I run xfig, and turn the > grid on, parts of the grid would be covered by a cloud of pixels. > Or when I start KDE, part (and always about the same part) of the KDE logo > is covered by a similar "cloud". The problem goes away if I turn off > acceleration, but I could not find any other way to prevent the issue. > > I wonder whether anything else could be done to solve the problem. > > Perhaps it is related, perhaps it is not, that my XFree86.0.log and > XFree86.1.log files contain the following error message: > > >(EE) S3VIRGE(0): unknown reason for exception > >(II) S3VIRGE(0): EAX=0x00004f00, EBX=0x00000000, ECX=0x00000000, > >EDX=0x00000000 > >(II) S3VIRGE(0): ESP=0x00000ffa, EBP=0x00000000, ESI=0x00000000, > >EDI=0x00002000 > >(II) S3VIRGE(0): CS=0x0268, SS=0x0100, DS=0x0040, ES=0x0000, FS=0x0000, > >GS=0x0000 > >(II) S3VIRGE(0): EIP=0x00010000, EFLAGS=0x00033282 > >(II) stack at 0x00001ffa: > > 00 06 00 00 00 32 > >(II) S3VIRGE(0): code at 0x00002680: > > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > >(EE) S3VIRGE(0): cannot continue > >(II) S3VIRGE(0): VESA BIOS not detected > > Sample logfiles are available at > http://www.coe.uncc.edu/~ghetyei/X/XFree86.0.log.txt > and > http://www.coe.uncc.edu/~ghetyei/X/XFree86.1.0.log.txt > > Gabor Hetyei > > PS. Please bear with me I am not an expert. Also I am not ready to make > risky experiments: I am just to happy to see the system running as it is.
Hi Gabor, The error above is not related to the problem you are seeing. I notice you mention XFree86 4.2.0 from SuSE, but the log files are from a 4.1.0 run? Have you tried both? Either way, there have been some fixes for ViRGE MX since the driver version you are running. I'd be interested in seeing a test report if you can try a virge driver >= 1.6.16. Either XFree86 4.2.0 would be good, or you can grab the 1.8.0 driver version from my page http://www.user1.netcarrier.com/~kbrosius/pages/virge.html. (Just don't use 1.8.2.) -- Kevin _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
