> Try using the SVGA server.  That is what I did when I was having trouble
> with the S3 server using a Diamond Stealth 64 PCI.
> 
> -Derek

Thanx for answering, but it still doesn't work.  What did you do?

I'm getting the same problem with the SVGA server.  The output is below.
Like the S3 server, the monitor would go into power-saving mode for 0.5
seconds, and then the system would hang.  I configured the system with
Xconfigurator, and did not look thru the video card database list.  I went
straight for the SVGA server.

I did get KDE working once, and that was when I manually changed the
symbolic link for the file X.  It would only come in in either 320x400 or
320x200.  I couldn't change resolution with Ctrl-Alt-'+'/'-' within KDE.


Thanx for the help, Foo

(I manually deleted some modes; hardware seems to check out okay)
X -probeonly output:

> XFree86 Version 3.3.3.1 / X Window System
> (protocol Version 11, revision 0, vendor release 6300)
> Release Date: January 4 1999
>       If the server is older than 6-12 months, or if your card is newer
>       than the above date, look for a newer version before reporting
>       problems.  (see http://www.XFree86.Org/FAQ)
> Operating System: Linux 2.0.36 i686 [ELF] 
> Configured drivers:
>   SVGA: server for SVGA graphics adaptors (Patchlevel 0):
>       NV1, STG2000, RIVA128, RIVATNT, ET4000, ET4000W32, ET4000W32i,
>       ET4000W32i_rev_b, ET4000W32i_rev_c, ET4000W32p, ET4000W32p_rev_a,
>       ET4000W32p_rev_b, ET4000W32p_rev_c, ET4000W32p_rev_d, ET6000, ET6100,
>       et3000, pvga1, wd90c00, wd90c10, wd90c30, wd90c24, wd90c31, wd90c33,
>       gvga, ati, sis86c201, sis86c202, sis86c205, sis86c215, sis86c225,
>       sis5597, sis5598, sis6326, tvga8200lx, tvga8800cs, tvga8900b,
>       tvga8900c, tvga8900cl, tvga8900d, tvga9000, tvga9000i, tvga9100b,
>       tvga9200cxr, tgui9400cxi, tgui9420, tgui9420dgi, tgui9430dgi,
>       tgui9440agi, cyber9320, tgui9660, tgui9680, tgui9682, tgui9685,
>       cyber9382, cyber9385, cyber9388, cyber9397, cyber9520, 3dimage975,
>       3dimage985, clgd5420, clgd5422, clgd5424, clgd5426, clgd5428,
>       clgd5429, clgd5430, clgd5434, clgd5436, clgd5446, clgd5480, clgd5462,
>       clgd5464, clgd5465, clgd6205, clgd6215, clgd6225, clgd6235, clgd7541,
>       clgd7542, clgd7543, clgd7548, clgd7555, clgd7556, ncr77c22, ncr77c22e,
>       cpq_avga, mga2064w, mga1064sg, mga2164w, mga2164w AGP, mgag200,
>       mgag100, oti067, oti077, oti087, oti037c, al2101, ali2228, ali2301,
>       ali2302, ali2308, ali2401, cl6410, cl6412, cl6420, cl6440, video7,
>       ark1000vl, ark1000pv, ark2000pv, ark2000mt, mx, realtek, s3_virge,
>       AP6422, AT24, AT3D, s3_svga, NM2070, NM2090, NM2093, NM2097, NM2160,
>       NM2200, ct65520, ct65525, ct65530, ct65535, ct65540, ct65545, ct65546,
>       ct65548, ct65550, ct65554, ct65555, ct68554, ct69000, ct64200,
>       ct64300, mediagx, V1000, V2x00, p9100, spc8110, generic
> (using VT number 7)
> 
> XF86Config: /usr/X11R6/lib/X11/XF86Config
> (**) stands for supplied, (--) stands for probed/default values
> (**) XKB: keymap: "xfree86(us)" (overrides other XKB settings)
> (**) Mouse: type: Microsoft, device: /dev/mouse, baudrate: 1200
> (**) Mouse: buttons: 3, 3 button emulation (timeout: 50ms)
> (**) SVGA: Graphics device ID: "Diamond Stealth 64 DRAM"
> (**) SVGA: Monitor ID: "Samsung Syncmaster 700p Plus"
> (--) SVGA: Mode "1600x1200" needs hsync freq of 105.77 kHz. Deleted.
> (--) SVGA: Mode "1280x1024" needs hsync freq of 107.16 kHz. Deleted.
> (--) SVGA: Mode "1800X1440" needs hsync freq of 96.15 kHz. Deleted.
> (--) SVGA: Mode "1800X1440" needs hsync freq of 104.52 kHz. Deleted.
> (**) FontPath set to
> "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X1
> 1R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fon
> ts/75dpi/"
> (--) SVGA: chipset:   868 rev. 3
> (--) SVGA: Using new style S3 MMIO
> (--) SVGA: bus type: 386/486 localbus
> (--) SVGA: Detected an S3 SDAC 86C716 RAMDAC and programmable clock
> (--) SVGA: Ramdac type: s3_sdac or compatible.
> (--) SVGA: Max RAMDAC speed for this depth: 135 MHz
> (--) SVGA: Using S3 Gendac/SDAC programmable clock (MCLK 66.222 MHz)
> (--) SVGA: Operating RAMDAC in pixel multiplex mode
> (--) SVGA: chipset:  s3_svga
> (--) SVGA: videoram: 2048k
> (**) SVGA: Using 8 bpp, Depth 8, Color weight: 666
> (--) SVGA: Maximum allowed dot-clock: 135.000 MHz
> (--) SVGA: Resolution 1024x768 too large for virtual 800x600
> (--) SVGA: Resolution 1152x864 too large for virtual 800x600
> (--) SVGA: Resolution 1024x768 too large for virtual 800x600
> (--) SVGA: Resolution 1152x864 too large for virtual 800x600
> (--) SVGA: Resolution 1024x768 too large for virtual 800x600
> (--) SVGA: Resolution 1280x1024 too large for virtual 800x600
> (--) SVGA: Resolution 1024x768 too large for virtual 800x600
> (--) SVGA: Resolution 1152x864 too large for virtual 800x600
> (--) SVGA: Resolution 1280x1024 too large for virtual 800x600
> (--) SVGA: Resolution 1024x768 too large for virtual 800x600
> (--) SVGA: Resolution 1152x864 too large for virtual 800x600
> (--) SVGA: Resolution 1280x1024 too large for virtual 800x600
> (--) SVGA: Resolution 1600x1200 too large for virtual 800x600
> (--) SVGA: Resolution 1152x864 too large for virtual 800x600
> (--) SVGA: Resolution 1280x1024 too large for virtual 800x600
> (--) SVGA: Resolution 1024x768 too large for virtual 800x600
> (--) SVGA: Resolution 1280x1024 too large for virtual 800x600
> (--) SVGA: Resolution 1600x1200 too large for virtual 800x600
> (--) SVGA: Resolution 1152x864 too large for virtual 800x600
> (--) SVGA: Resolution 1280x1024 too large for virtual 800x600
> (--) SVGA: Resolution 1600x1200 too large for virtual 800x600
> (**) SVGA: Mode "640x480": mode clock =  45.800
> (**) SVGA: Mode "800x600": mode clock =  69.650
> (--) SVGA: There is no mode definition named "1024x768"
> (--) SVGA: Removing mode "1024x768" from list of valid modes.
> (**) SVGA: Virtual resolution set to 800x600
> (--) SVGA: SpeedUp code selection modified because virtualX != 1024
> (--) SVGA: Framebuffer aligned on 800 pixel width
> (--) SVGA: Linear mapped framebuffer at 0xf3000000
> (--) SVGA: Using built-in S3 hardware cursor.



> On Tue, 6 Apr 1999, F L wrote:
> 
> > XFree86 version:
> > XFree86-3.3.3.1
> > 
> > OS:
> > Mandrake (of course!) 5.3 (Festen)
> > installation CD made from ISO image
> > 
> > Problem:
> > Well, I spent 3 whole days trying to figure this one out.  Every time I
> > tried to start the X server by typing 'startx', my system would hang.  I
> > can't get any error logs because the only way out is to reboot, and since
> > the disks haven't synced, no error logs.  It seems to go thru the same
> > output that 'X -probeonly' give me and then hang.  I can't say for certain
> > since it goes by so fast, and the error logs don't work (see above).
> > There is no Xerror file in /var/log either.
> > 
> > I've read the parts of the README.S3 docs I thought was relevant to my
> > problem.  I've surfed Dejanews looking for Diamond, Stealth, Mandrake, but
> > none of those had the answer.  The specs are perfectly detected by
> > 'X -probeonly' (included below along with SuperProbe output).  I also
> > emailed the XFree86 team, but haven't got an answer back yet.  I've
> > tried installing Red Hat 5.2 (Apollo) with the 3.3.2.3 X Server and I had
> > the same problem.
> > 
> > All 3 different X configuration tools: xf86config, Xconfigurator, and
> > XF86Setup.  The XF86Setup works okay, so I guess it can run the VGA16
> > server, but not the S3 server which is written specifically for my chipset
> > (what gives?).  The closest I've ever got was going into KDE, it telling
> > me to create /root/Desktop, and then hanging.  This was AFTER I tried
> > XF86Setup, it giving me a "errno = 111", and I went ahead & typed 'startx'
> > anyway.  Strange to say the least since it shouldn't work.
> > 
> > I really need this system for school.  Any & all help is appreciated.  I
> > don't think I can find any other good VLB cards out on the market now, so
> > it looks like I'm stuck with it.  Thanks again.
> 
> --- snip diagnostic output
> 

Reply via email to