Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

X configuration



>I'm running the Mono Server [vga2] with a trident 8900cl
>chipset and using a Tatung monochrome monitor.  I have to
>admit, I also run MS Windows on this machine and can get it to
>show up on the monitor.  So I know the monitor can do graphics.

>From modeDB.txt this entry lists the clock values for trident 8900cl:
###############################################################################
# Card:                 Trident Generic 8900CL (TCK9004N clock chip)
# Contributor:          David Wexelblat [dwex at xfree86.org]
# Last Edit Date:       4/18/93
#
# chip    ram   virtual   clocks                           default-mode  flags
 TVGA8900CL
          1024  1024 768   25  28  45  36  57  65  50  40  "1024x768"
                           88  98 119 108  72  77  80  75
###############################################################################

Also from modeDB.txt:
###############################################################################
#
# VESA 1024x768 at 60Hz Non-Interlaced mode
# Horizontal Sync = 48.4kHz
# Timing: H=(0.12us, 2.22us, 2.58us) V=(0.06ms, 0.12ms, 0.60ms)
#
# name        clock   horizontal timing     vertical timing      flags
 "1024x768"    65     1024 1032 1176 1344    768  771  777  806 -hsync -vsync
###############################################################################

So change the `Clocks' line to

Clocks 65

and put the "1024x768" line as the first entry after:

modeBD
 "1024x768"    65     1024 1032 1176 1344    768  771  777  806 -hsync -vsync

Note: The Clocks entry of 65 will reference the "1024x768" line because
      65 as the first number is a match!

ALSO: This assumes that your monitor can be driven at
`Horizontal Sync = 48.4kHz'  Consult modeDB.txt for additional 
"1024x768" entries.  I chose 65 because that was the lowest freq
and that should do the least damage to the monitor.  You want
to crank up the clock to the highest value that your monitor
can handle and this will give the stablest image.  To high
a value can burn out the monitor though.  It`s a good idea 
to have the specs on the monitor to know what freq. it can
be driven at.  If you have the values for the monitor, using `xclk'
you can tune the monitor to achieve the best freq/resolution
tradeoff.


		Dan Demus
		dan at palette.com
		(617)327-2641
		(603)886-1230x133


PS from modeDB.txt:
###############################################################################
# Monitor:              TATUNG CM-1498X
# Contributor:          Per Lindqvist [pgd at compuram.bbt.se]
# Last Edit Date:       9/21/91
#
# name         clock  horizontal timing     vertical timing      flags
 "640x400"      25     640  648  768  800    400  412  414  449
 "640x480"      25     640  648  768  800    480  487  492  525
 "800x600"      36     800  816  976 1008    600  602  610  628
 "800x655"      36     800  816  976 1008    655  658  660  687

###############################################################################
# Monitor:              Tatung CM14UAS
# Contributor:          David McCullough [davidm at stallio.oz.au]
# Last Edit Date:       11/19/93
#
# name         clock  horizontal timing     vertical timing      flags
 "640x480"     25      640  664  760  800    480  491  493  525
 "800x600"     40      800  840  968 1056    600  601  605  628
>>>> "1024x768"    65     1024 1152 1184 1360    768  766  772  806




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org