Very Computer

Hi.

I have a strange problem with the XFree X server. After running awhile,
the dotclock seems to be different, this causes the X server to not find
any appropriative resoulutions. This again causes my screen to be reset
each 2 seconds (not good for the monitor I think).

The TSENG ET4000 (Turbo ?)

This is the result when thing seems to work nice :

*****
Setting TCP SO_LINGER: Protocol not available
XFree86 Version 1.3 / X Window System
(protocol Version 11, revision 0, vendor release 5000)
Operating System: Linux
Configured drivers:
  VGA256 (256 colour SVGA):
      et4000, et3000, pvga1, wd90c00, wd90c10, wd90c30, gvga, ati,
      tvga8800cs, tvga8900b, tvga8900c, tvga8900cl, tvga9000, clgd5420,
      clgd5422, clgd5424, clgd5426, ncr77c22, ncr77c22e, cpq_avga
(using VT number 3)

Xconfig: /usr/X386/lib/X11/Xconfig
Mouse: type: MouseSystems, device: /dev/ttyS0, baudrate: 1200
FontPath set to
"/usr/X386/lib/X11/fonts/misc/,/usr/X386/lib/X11/fonts/Type1/,/usr/X38
6/lib/X11/fonts/Speedo/,/usr/X386/lib/X11/fonts/75dpi/"
VGA256: ET4000: Initial hibit state: high
VGA256: et4000 (mem: 1024k numclocks: 16)
VGA256:   clocks:  25.18  28.32  32.50  35.90  39.90  45.00  31.40 37.50
VGA256:   clocks:  50.00  59.90  64.90  74.00  80.50  89.70  62.70 75.10
VGA256: Mode "1152x910": mode clock =  80.000, clock used =  80.500
VGA256: Mode "1024x768": mode clock =  65.000, clock used =  64.900
VGA256: Mode "800x600": mode clock =  50.000, clock used =  50.000
VGA256: Mode "640x480": mode clock =  31.000, clock used =  31.400
VGA256: Virtual resolution set to 1152x910
VGA256: SpeedUp code selection modified because virtualX != 1024
VGA256: SpeedUp mode selected (Flags=0xf)
*****

This is the out put when X is restarting again and again (each 2
seconds) :

*****
Setting TCP SO_LINGER: Protocol not available
XFree86 Version 1.3 / X Window System
(protocol Version 11, revision 0, vendor release 5000)
Operating System: Linux
Configured drivers:
  VGA256 (256 colour SVGA):
      et4000, et3000, pvga1, wd90c00, wd90c10, wd90c30, gvga, ati,
      tvga8800cs, tvga8900b, tvga8900c, tvga8900cl, tvga9000, clgd5420,
      clgd5422, clgd5424, clgd5426, ncr77c22, ncr77c22e, cpq_avga
(using VT number 3)

Xconfig: /usr/X386/lib/X11/Xconfig
Mouse: type: MouseSystems, device: /dev/ttyS0, baudrate: 1200
FontPath set to
"/usr/X386/lib/X11/fonts/misc/,/usr/X386/lib/X11/fonts/Type1/,/usr/X38
6/lib/X11/fonts/Speedo/,/usr/X386/lib/X11/fonts/75dpi/"
VGA256: ET4000: Initial hibit state: low
VGA256: et4000 (mem: 1024k numclocks: 16)
VGA256:   clocks:  25.18  28.32  32.00  35.30  39.60  35.90  30.90 30.50
VGA256:   clocks:  12.30  13.90  16.00  17.70  24.90  22.10  15.50 18.50

Fatal server error:
There is no defined dot-clock matching mode "1152x910"
*****

Somehow it seems that the dot-clock-speed decreases to 1/3 of the
normal. Is is a way to restore the VGA-card back to the original ?

I have to boot just because my VGA card is f.... up.

Hugo E. Gunnarsen

Quote:>Hi.
>I have a strange problem with the XFree X server. After running awhile,
>the dotclock seems to be different, this causes the X server to not find
>any appropriative resoulutions. This again causes my screen to be reset

The dot clock detection only works reliable when there is little or no load.
For this reason, you should start X once to detect the clocks and copy the
values then into your Xconfig.

...

Quote:>This is the result when thing seems to work nice :
...
>VGA256:   clocks:  25.18  28.32  32.50  35.90  39.90  45.00  31.40 37.50
>VGA256:   clocks:  50.00  59.90  64.90  74.00  80.50  89.70  62.70 75.10

This would be:
clocks  25.18 28.32 32.5 35.9 39.9 45.0 31.4 37.5 50.0 59.9 64.9 74.0 80.5 89.7 62.7 75.1

        Joern Rennecke