Return to BSD News archive
Xref: sserve comp.os.386bsd.bugs:1052 comp.os.386bsd.questions:3530 comp.windows.x.i386unix:2333 comp.os.386bsd.apps:270
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!xlink.net!fauern!news.tu-chemnitz.de!irz401!uriah!not-for-mail
From: j@bonnie.tcd-dresden.de (J Wunsch)
Newsgroups: comp.os.386bsd.bugs,comp.os.386bsd.questions,comp.windows.x.i386unix,comp.os.386bsd.apps
Subject: Re: XFree86 1.3 crashes under 386BSD
Date: 5 Jul 1993 11:24:14 +0200
Organization: Textil Computer Design GmbH, Dresden, Germany
Lines: 23
Distribution: world
Message-ID: <218rvuINN7j1@bonnie.tcd-dresden.de>
References: <20rq0p$iev@email.tuwien.ac.at> <wmbfmk.741712328@rwc.urc.tue.nl>
NNTP-Posting-Host: bonnie.tcd-dresden.de
In article <wmbfmk.741712328@rwc.urc.tue.nl> wmbfmk@rwc.urc.tue.nl (Marc van Kempen) writes:
>mbirgmei@email.tuwien.ac.at (Martin BIRGMEIER) writes:
>
>>One more hint for those who might know the solution: I can trigger a
>>crash most easily if I run xlock with one of the modes which draw lines,
>>e.g. swarm or qix.[...]
>
>BUGS
> There are some graphics bugs that show up when the virtual
> width used is not equal to 1024.
>
From what i know (i don't have an ET4000), this is related to the
speedup code. You can also disable the SpeedUp (NoSpeedUp in Xconfig),
or find out *which* particular speedup option causes the trouble.
(I don't know exactly how, look into README.tseng. The speedup options
are formed of bits, where you can enable/disable each of them by
a particular number.)
--
in real life: J"org Wunsch | ) o o | primary: joerg_wunsch@tcd-dresden.de
above 1.8 MHz: DL 8 DTL | ) | | private: joerg_wunsch@uriah.sax.de
| . * ) == |
``An elephant is a mouse with an operating system.''