Simon Taplin wrote:
> I'm trying to get a S3 Trio3D AGP Card to work on RH60. I see the
> Xfree 3.3.5 can get more that 16 colors on the Trio3D. I download
> SVGA.rpm and installed it. RPM gave me no error messages. I
> then ran xf86config and set everything up but the card index still
> says the S3 uses vga16. And when I run Gnome, it still usese
> VGA16.
>
> Should I have also downloaded XF86 S3V server and installed it?
> Or am I doing something stupid?
>
> I'm using a 14inch Sampo screen which supports up to 1024*768
> Non-interlaced, High Frequency and when I try to setup the
> monitor, it gives me the above two seperately, which one should I
> use?
>
> Also, I see when Gnome quits there are some errors messages,
> whats the command line to capture those errorr messages?
>
> Simon
>
> ICQ:15774994
> WinErr: 00F Unexplained error - Please tell us how this
> happened
I went through much grief getting this card to work with RH6.
Unfortunately the box in question is off and at work, so I can't say
what my XF86Config file says till wednesday. The following post by on
comp.os.linux.x may be helpful:
--
Subject:
Re: S3 Trio 3D/2X - 86C368 chip
Date:
Fri, 19 Nov 1999 06:46:07 GMT
From:
[EMAIL PROTECTED] (Tim Roberts)
Organization:
Providenza & Boekelheide, Inc.
Newsgroups:
comp.os.linux.x
References:
1
[EMAIL PROTECTED] wrote:
>I've noticed from various NG posts and other sources on
the net that
>a great many are having problems with getting a decent X
server for
>the S3 Trio 3D/2X but with no apparent solution to the
problem.
>...
>After a *lot* of searching, I found a mention of the
86C368 chip in the
>XFree86 FAQ, Q.F19, along with a workaround and a patch
for the server.
>The quick workaround is to put
> ChipID 0x8a10
> VideoRam 4096
>in the device section of XF86Config or to patch the
server.
>
>My question is this: is the quick workaround more than is
necessary
>and/or does it have undesirable side-effects?
The ChipID/VideoRam hack is enough. The Trio3D/2X is not
actually
supported in XFree86 yet; a driver was submitted, but it
was yanked at
the
last minute for stability problems. However, the
Trio3D/2X is virtually
identical to the ViRGE/GX (chipid 8a10), which IS
supported. The T3D/2X
happens to support more memory than the /GX driver
understands, which is
why you have to limit the VideoRam. Other than that, it
works perfectly
well.
It's the VideoRam thing that causes your slow response.
>If so, has anyone got a compiled binary for RedHat 5.2 +
linux 2.2
kernel?
>and finally ... is more work needed to fully support the
86C368?
Yes, but not much more. I expect full support will be in
3.3.6 which
should be available by 1 December.
>I don't really fancy downloading, patching and compiling
an X server
>unless I have no choice (I have more pressing things to
do).
Honestly: the ChipID hack is a perfectly adequate
solution.
--
- Tim Roberts, [EMAIL PROTECTED]
Providenza & Boekelheide, Inc.
