Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!ihnp4.ucsd.edu!usc!math.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!news.ecn.bgu.edu!psuvax1.cse.psu.edu!news.pop.psu.edu!news.cac.psu.edu!news.umi.com!umi.com!jbrown From: jbrown@umi.com (Jim Brown) Newsgroups: comp.os.386bsd.questions Subject: Re: Who killed XFree86 ? Date: Mon, 18 Apr 1994 10:40:50 Organization: University Microfilms Inc. Lines: 67 Distribution: world Message-ID: <jbrown.58.000AAE89@umi.com> References: <766429381tim.news@xplora.toppoint.de> NNTP-Posting-Host: 192.195.245.39 X-Newsreader: Trumpet for Windows [Version 1.0 Rev A] In article <766429381tim.news@xplora.toppoint.de> tim@xplora.toppoint.de (Tim Weilkiens) writes: >From: tim@xplora.toppoint.de (Tim Weilkiens) >Subject: Who killed XFree86 ? >Date: Fri, 15 Apr 94 17:03:01 CET >Hello, >the subject is my question. >If I start X (with startx) the graphic screen appears. Then a window opens >and then the system hang up. >With startx >& x.log I get the following output: >XFree86 Version 2.0 / X Window System >(protocol Version 11, revision 0, vendor release 5000) >Operating System: FreeBSD >Configured drivers: > VGA256: server for 8-bit colour SVGA (Patchlevel 0): > et4000, et3000, pvga1, wd90c00, wd90c10, wd90c30, wd90c31, gvga, ati, > tvga8800cs, tvga8900b, tvga8900c, tvga8900cl, tvga9000, clgd5420, > clgd5422, clgd5424, clgd5426, clgd5428, clgd6205, clgd6215, clgd6225, > clgd6235, ncr77c22, ncr77c22e, cpq_avga, oti067, oti077 >Using pccons driver with X support >Xconfig: /usr/X386/lib/X11/Xconfig >(**) stands for supplied, (--) stands for probed/default values >(**) Mouse: type: Microsoft, device: /dev/com0, baudrate: 1200 >(**) FontPath set to "/usr/X386/lib/X11/fonts/misc/,/usr/X386/lib/X11/fonts/Type1/,/usr/X386/lib/X11/fonts/Speedo/,/usr/X386/lib/X11/fonts/75dpi/,/usr/X386/lib/X11/fonts/100dpi/" >(--) Trident chipset version: 0x13 (TVGA8900C) >(--) VGA256: chipset: tvga8900c >(**) VGA256: videoram: 512k >(--) VGA256: clocks: 25.20 28.32 45.00 36.00 57.30 64.90 50.50 40.00 >(--) VGA256: Maximum allowed dot-clock: 90MHz >(**) VGA256: Mode "640x480c": mode clock = 50.000, clock used = 50.500 >(**) VGA256: Virtual resolution set to 800x600 >(--) VGA256: SpeedUp code selection modified because virtualX != 1024 >waiting for X server to shut down XIO: fatal IO error 32 (Broken pipe) on X server ":0.0" > after 395 requests (392 known processed) with 26 events remaining. > The connection was probably broken by a server shutdown or KillClient. >Where is the problem ?? >Please help. >Tim >-- >>>> Do you really want to live forever...? (GENESIS, 1992) <<< >************************************************************** >* Tim Weilkiens, Kiel (Germany), tim@xplora.toppoint.de * >************************************************************** I've seen this on this card where the dot clock used is wrong try using the 25.2 clock for 640x480 in your mode database section. BTW, I also had a problem with the tvga chipset where it would display the curson only on the top line. Beware there... jpb == jbrown@umi.com , in real life Jim Brown | == == 300 N. Zeeb Rd. Ann Arbor, MI 48106 (USA) | Sit up straight. == == (313) 761-4700 x3227 | You're slouching... == ================ All opinions and comment expressly my own. ==============