Diamond Stealth 64 DRAM PCI (Trio 64) and vgalib

Diamond Stealth 64 DRAM PCI (Trio 64) and vgalib

Post by David Held » Thu, 18 Jan 1996 04:00:00



        I have a Diamond Stealth 64DRAM, 2meg with the Trio64 chipset
(that's Diamond bios v2.0) and I'm running SVGAlib version 1.2.8 for the
Trio64.  I also used the normal SVGAlib version 1.2.8.  I have tried
changing the libvga.config between unspecified and S3.

Problem:
        The problem is, my old graphics applications do not work - mpeg_vga,
vgamp, zgv.  If I run the application zgv, for instance, I get space fuzz.
When I escape, it doesn't return to the correct video mode - I get more
space fuzz (the clock is messed up).  SVGATextMode won't fix it them.
savetextmode does the same thing.  vgamp will show the mpeg and then escape
and give me space fuzz.

Other Weird Things:
        All these things did work under SlackWare 2.02 (I think.).  I just
switched to RedHat, which came with the new libs.

What might be wrong:
        I suspect that the clockchip on my videocard is getting screwed up.
I'm curious if anyone else has had this problem and was able to fix it.

        Thanks,
        David

 
 
 

Diamond Stealth 64 DRAM PCI (Trio 64) and vgalib

Post by Tim Bandelo » Sat, 20 Jan 1996 04:00:00



>        I have a Diamond Stealth 64DRAM, 2meg with the Trio64 chipset
>(that's Diamond bios v2.0) and I'm running SVGAlib version 1.2.8 for the
>Trio64.  I also used the normal SVGAlib version 1.2.8.  I have tried
>changing the libvga.config between unspecified and S3.

>Problem:
>        The problem is, my old graphics applications do not work - mpeg_vga,
>vgamp, zgv.  If I run the application zgv, for instance, I get space fuzz.
>When I escape, it doesn't return to the correct video mode - I get more
>space fuzz (the clock is messed up).  SVGATextMode won't fix it them.
>savetextmode does the same thing.  vgamp will show the mpeg and then escape
>and give me space fuzz.

>Other Weird Things:
>        All these things did work under SlackWare 2.02 (I think.).  I just
>switched to RedHat, which came with the new libs.

>What might be wrong:
>        I suspect that the clockchip on my videocard is getting screwed up.
>I'm curious if anyone else has had this problem and was able to fix it.

There is a patch on sunsite which fixes exactly this problem with the Trio64:

  .../libs/graphics/svgaTrio.tgz

Bye.
--
+--Tim Bandelow----------------------------------------------------+

|  WWW:            http://www.bauwesen.uni-dortmund.de/~bandelow/  |
+------------------------------------------------------------------+

 
 
 

Diamond Stealth 64 DRAM PCI (Trio 64) and vgalib

Post by David A. Held » Mon, 22 Jan 1996 04:00:00





>There is a patch on sunsite which fixes exactly this problem with the Trio64:

>  .../libs/graphics/svgaTrio.tgz

        Oh, I forgot to mention that I also tried that patch.. It still
doesn't work - what baffles me is that it worked before.  Is there some new
way the newer libvga's handle the monitor scan speed (that is, it's listed
in a config file different than vgalib.config...?

        David
--

Computers are the Evil Minions of Satan!  Read news with a joystick: YOU WILL

 
 
 

Diamond Stealth 64 DRAM PCI (Trio 64) and vgalib

Post by James Sternbe » Fri, 26 Jan 1996 04:00:00



: >
: >        I have a Diamond Stealth 64DRAM, 2meg with the Trio64 chipset
: >(that's Diamond bios v2.0) and I'm running SVGAlib version 1.2.8 for the
: >Trio64.  I also used the normal SVGAlib version 1.2.8.  I have tried
: >changing the libvga.config between unspecified and S3.
: >
: >Problem:
: >        The problem is, my old graphics applications do not work - mpeg_vga,
: >vgamp, zgv.  If I run the application zgv, for instance, I get space fuzz.
: >When I escape, it doesn't return to the correct video mode - I get more
: >space fuzz (the clock is messed up).  SVGATextMode won't fix it them.
: >savetextmode does the same thing.  vgamp will show the mpeg and then escape
: >and give me space fuzz.
: >
: >
: >Other Weird Things:
: >        All these things did work under SlackWare 2.02 (I think.).  I just
: >switched to RedHat, which came with the new libs.
: >
: >
: >What might be wrong:
: >        I suspect that the clockchip on my videocard is getting screwed up.
: >I'm curious if anyone else has had this problem and was able to fix it.

: There is a patch on sunsite which fixes exactly this problem with the Trio64:

:   .../libs/graphics/svgaTrio.tgz

How do either of you get the Stealth 64 DRAM to work at all?  I have one with
1 MB of DRAM and a Trio64 chip, and both svgalib-1.2.9, and svgaTrio.tgz tell
me that I have an unknown chip ID 11e4.

-James Sternberg

 
 
 

Diamond Stealth 64 DRAM PCI (Trio 64) and vgalib

Post by Tim Bandelo » Sat, 27 Jan 1996 04:00:00





>: >
>: >        I have a Diamond Stealth 64DRAM, 2meg with the Trio64 chipset
>: >(that's Diamond bios v2.0) and I'm running SVGAlib version 1.2.8 for the
>: >Trio64.  I also used the normal SVGAlib version 1.2.8.  I have tried
>: >changing the libvga.config between unspecified and S3.
>: >
>: >Problem:
>: >        The problem is, my old graphics applications do not work - mpeg_vga,
>: >vgamp, zgv.  If I run the application zgv, for instance, I get space fuzz.
>: >When I escape, it doesn't return to the correct video mode - I get more
>: >space fuzz (the clock is messed up).  SVGATextMode won't fix it them.
>: >savetextmode does the same thing.  vgamp will show the mpeg and then escape
>: >and give me space fuzz.
>: >
>: >
>: >Other Weird Things:
>: >        All these things did work under SlackWare 2.02 (I think.).  I just
>: >switched to RedHat, which came with the new libs.
>: >
>: >
>: >What might be wrong:
>: >        I suspect that the clockchip on my videocard is getting screwed up.
>: >I'm curious if anyone else has had this problem and was able to fix it.

>: There is a patch on sunsite which fixes exactly this problem with the Trio64:

>:   .../libs/graphics/svgaTrio.tgz

>How do either of you get the Stealth 64 DRAM to work at all?  I have one with
>1 MB of DRAM and a Trio64 chip, and both svgalib-1.2.9, and svgaTrio.tgz tell
>me that I have an unknown chip ID 11e4.

>-James Sternberg

Sorry, I don't think I can help you here. Mine just worked.
svgaTrio also restores the video mode correctly.
I'm running a modified german version of Slackware 3.0.
Perhaps there are different versions of that chip.
The X11 (XFree86 3.1.2B) output for my card shows:

(**) S3: Graphics device ID: "Diamond Stealth 64 DRAM (S3-Trio64)"

(**) S3: Option "diamond"
(--) S3: card type: PCI
(--) S3: chipset:   Trio64 rev. 21
(--) S3: chipset driver: mmio_928
(--) S3: videoram:  2048k
(--) S3: Ramdac type: s3_trio64
(--) S3: Ramdac speed: 135

Best regards.
Tim.
--
+--Tim Bandelow----------------------------------------------------+

|  WWW:            http://www.bauwesen.uni-dortmund.de/~bandelow/  |
+------------------------------------------------------------------+