From owner-freebsd-hackers  Wed Mar 27 21:02:24 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id VAA29828
          for hackers-outgoing; Wed, 27 Mar 1996 21:02:24 -0800 (PST)
Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA29823
          for <freebsd-hackers@freebsd.org>; Wed, 27 Mar 1996 21:02:18 -0800 (PST)
Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.6.11/8.6.9) id QAA18111; Thu, 28 Mar 1996 16:00:44 +1100
From: David Dawes <dawes@rf900.physics.usyd.edu.au>
Message-Id: <199603280500.QAA18111@rf900.physics.usyd.edu.au>
Subject: Re: STB PowerGraph 64 Video (Trio64V+) and XF86...
To: pascal@pascal.org (Freeman P. Pascal IV)
Date: Thu, 28 Mar 1996 16:00:43 +1100 (EST)
Cc: freebsd-hackers@freebsd.org
In-Reply-To: <3159FBF4.167EB0E7@pascal.org> from "Freeman P. Pascal IV" at Mar 27, 96 06:39:48 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>I upgraded to a P100 PCI motherboard awhile back and with it a new
>video card.  I'm now using a "STB PowerGraph 64 Video" video card
>and I'm having no end to trouble when trying to configure it with
>XF96 (everything else seems to run just fine on this new motherboard).
>
>Has anyone else been able to get this card to work with XF86?
>
>Here's the Device section I'm using:
>
>  Section "Device"
>    Identifier	"STB PowerGraph 64 Video"
>    VendorName	"STB"
>    Chipset	"s3_generic"
>  EndSection
>
>The above settings at lease cause the XF86_S3 server to see the
>card and identify it as having a Trio64V+ chipset when I run with
>"-probeonly".  But when I run the server the screen clears, the
>drive light comes on, and my machine locks up solid.  After
>rebooting I have filesystem damage proportional to how quick I was
>at hitting the reset button.  If I wait too long I get corrupted
>file systems that have extensive damage.
>
>I've tried other settings for Chipset which I've found for other
>Trio64 cards on the Web by running "strings" on the server binary.
>Settings like "s3_trio64", "S3-Trio64", "S3-Trio64V+", "s3_trio64v+",
>"trio64", and "trio64v" have come back as "Unidentified chipset...".

A chipset setting isn't necessary.  Try the 3.1.2D beta version.  There
were problems with the Trio64V+ support in earlier versions.  If that
doesn't work any better, let me know.

David