Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.eng.convex.com!newshost.convex.com!news.duke.edu!news.mathworks.com!newsfeed.internetmci.com!news.sprintlink.net!news.n2.net!jgibbons
From: jgibbons@n2.net (Jeff Gibbons)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: X11 problem (Stealth64)
Date: 15 Jan 1996 05:35:41 GMT
Organization: N2 Networking
Lines: 43
Message-ID: <4dcp3d$hgr@news.n2.net>
References: <4d6trt$gg5@bambam.soi.city.ac.uk>
NNTP-Posting-Host: ravel.n2.net
X-Newsreader: TIN [version 1.2 PL2]
Colin Bridgeman (colin@cs.city.ac.uk) wrote:
: Hi,
: I'm running FreeBSD 2.0.5 on a 75MHz Pentium using a Diamond Stealth
: 64 graphics card with 2Mb of memory. I can get X to start up and . . .
. . .
: after a random amount of time the display locks up and . . .
The same thing is happening to me! I'm running FreeBSD 2.1 with
XFree86 3.1.2 on a 75MHz Pentium with a brand-new Diamond Stealth64
Video 2001 (the one with the Trio64 chip and 2Mb of DRAM). My system runs
perfectly in text mode, but only about 2 or 3 minutes after I start X
using the XF86_S3 driver -- then the screen freezes so tight I can't even
move the mouse.
My freezes seem to occur more quickly with complex graphics on the screen --
a simple xterm lasts longer than Netscape. But I can't correlate the
_timing_ of the freezes with anything -- it will freeze when I'm doing
nothing more than moving the mouse across the screen.
I read in a previous post about the OPTION "sw_cursor" (in XF86Config) to
try to prevent some S3-related lockups, but that didn't help me. I also
read about removing sio3 because some S3 cards have problems with the port
that that serial device uses, but I built a kernel without sio2 and sio3
and even removed the hard-coded reference to the port in
/usr/src/sys/i386/isa/sio.c :
likely_com_ports[] = { 0x3f8, 0x2f8, /* 0x3e8, 0x2e8, */ };
None of that helped me, but maybe one of those ideas will help you. The
good news is that the XF86_VGA16 driver works, so if you are content with
16 colors (Netscape behaves very strangely) at least you can run X. The
XF86_Mono driver also works. My system seems rock-solid using the VGA16
driver at 640x480.
I hope some of this helps you, and if anyone knows why this is happening
or has any other ideas to try, please let us know! And thanks for your
post; at least now I know I'm not the only one with this problem.
Jeff
---------------------------------
Jeff Gibbons jgibbons@n2.net
---------------------------------