On Sun, 14 Jun 1998, Lawrence Houston wrote:
> This week I upgraded a RH 4.2 Installtion with Red Hat's recommended
> XFree86 3.3.2-1 for Intel and now XDM is failing to start with Systems's
> "onboard" S3 Trio64V2/DX. The Trio64V2/DX had been working with S3 Server
> included in 3.3.1 (I understood the V2 variety of the Trio64 had been
> unsupported with the XFree86 3.2 included in RH 4.2 the Distribution)!
> Symptoms: VTs 1-7 (including the one for the X-11 Server) are filled with
> virtical lines of junk and the XDM Log reports:
>
> Might there a "bug" in XFree86 3.3.2's X3 support for the Trio64V2/DX
> Chipset, or is there something "new" in the mix since this version was
> built under 2.0.34 and is now being wrapped with "Xwrapper" instead of
> "xserver-wrapper". I am NOT comfortable moving away from 3.3.2 since it
> addressed some Security Issues, but 3.3.1 is the presently the ONLY way
> this baby will "fly"!
I don't know whether this will do any good, but there have always been
some bugs in XFree's driver for that card. The fixes are built into
XFree86, but apparently the same fixes don't work for all versions of the
card, or something, so they have to be applied in your XF86Config. In the
"Device" section, try including this:
Option "Trio64V+_BugX"
with the X replaced with a 1, 2, or 3. All are different and may or may
not work. Of course it's possible that none of them work, but give it a
try anyway.
Maybe I don't know what I'm talking about here, but why would an X server
be to blame for problems on a virtual terminal? I thought the X server
only affected VT #7.
--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--
Greg Fall
[EMAIL PROTECTED], [EMAIL PROTECTED]
http://www-personal.engin.umich.edu/~gmfall
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
