2. XF86_S3V server

The S3V server has some minor fixes since 3.3.1. You should find that the ViRGE server is stable at all depths. The server supports 1 and 32 bpp pixmap formats. This fixes known problems with xanim and Netscape clients in early versions of the S3V server. It has been tested with ViRGE cards with 2 and 4MB DRAM, ViRGE/DX 4M, ViRGE/VX 8M (4M VRAM/4M DRAM), and with a 220MHz ViRGE/VX card with 2MB VRAM up to 1600x1200 with 8/15/16bpp.

NOTE: This driver is pretty new, and not everything might work like you expect it to. It shouldn't crash your machine, but you may have video artifacts or missing lines. Please report any and all problems to [email protected] using the appropriate bug report sheet.

2.1. Features:

• Basic support for S3 ViRGE, ViRGE/DX, ViRGE/GX and ViRGE/VX video adapters
• uses linear frame buffer
• it should be possible to reach resolutions up to the maximum supported by your video card memory. (eg. 1600x1200 at 8 and 16bpp, 1280x1024 at 24/32 bpp for a 4 Meg. card)
• it should be possible to use pixel depths of 8, 15, 16, 24, and 32 bits per pixel.
• 32 bpp is implemented as translation to 24 bpp

2.2. Known limitations

• No support for external RAMDACs on the ViRGE/VX.
• No support for VLB cards.
• No support for doublescan modes.
• The driver only works with linear addressing.
• For 24/32 bpp some simple dashed line acceleration is implemented, but sloped dash/double dash are drawn as solid lines.
• No support for current chipsets.
• No longer actively maintained.

2.3. Configuration:

The server auto-detects RAM size, RAMDAC and ClockChip. Do not bother putting these in your "Device" section. The "nolinear" option is unsupported.

2.3.1. Cursor:

• The default is hardware cursor, no option is needed.
• "sw_cursor" switches to software cursor.