Andy Stewart wrote:
On Monday 13 October 2003 2:28 pm, Gregory Avedissian wrote:
Lowres won't work. The problem is it sees the S3Virge chip on the vid card and wants to use the s3virge driver, when it should really be using the 3DLabs driver. In the old sax, it tries to run in lowres first, and it comes up very large and hanging way over the edge of my screen. What I've found to work is this - sax -h 30-70 -v 50-150 -a 1024x768 -s XF86_3DLabs
The "very large and hanging way over the edge of my screen" problem is most likely a funky "modelines" line in your XF86Config file. This can often be remedied by manually adjusting your monitor, or by running (carefully!) xvidtune and noting the new mode line once the screen is properly adjusted. This new mode line would then be hand edited into your XF86Config file. If the XFree86 v3.x driver (XF86_3DLabs) works for you, there may be no need to fuss with the v4.x XFree86 driver.
I've read the help screen for sax2 a bunch of times, and I don't understand how to give it the same information.
sax2 -m 0=vga sort of works. I get a 320x200 image that fills the bottom half of my screen and bleeds way off the right edge.
sax2 -m 0=glint quits and gives me error messages (no device found - the card has a glint 500tx accelerator)
sax2 -m 0=s3virge goes black and locks up, only reset button gets me out
Which version of XFree86 4.x are you trying to use? If you are having problems like this, you most likely need the latest and greatest. However, I have seen cases where XFree86 v3.x works better than v4.x, especially on "weird" video cards that are getting on in years.
Later,
Andy
I'm trying to use 4.1.0. The 3Dlabs driver didn't come with 3.3.6. I had to find it online and unpack it. I also ran the Xinstall script that came with the 4.1.0 tarballs. I thought it had replaced all my files, so I can't tell you for sure which version is really running. I just tried again to run sax2 -m 0=vga, and it ran fine at 640x480. I'm not sure what's different now, but I did install some other packages this afternoon, like openmotif devel and some font packages. Anyway, sax2 does not list my vid card, but sax does. Maybe I should just leave this alone for now, since it works. If it's the source of the kde problem, I can live with it as long as my function keys work. BTW, I had asked you about my other machine, which wouldn't let me switch virtual screens. Turns out my nifty new keyboard has about 10 special buttons for web surfing, and one of them turns off the function keys. Thanks, Greg