<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Known Problems and Bug Reports</TITLE>
</HEAD>
<BODY BGCOLOR="#efefef" TEXT="black" LINK="blue" VLINK="#551A8B" ALINK="red">

<A HREF="Mach64.html"><EM>Mach64 X Server Release Notes</EM></A>
 <b>:</b> <EM>Known Problems and Bug Reports</EM><BR>
<b>Previous:</b> <A HREF="Mach645.html"><EM>Cards known to work with this release</EM></A><BR>
<b>Next:</b> <A HREF="Mach64.html"><EM>Mach64 X Server Release Notes</EM></A>


<HR NOSHADE>
  <H2><A NAME="6"></A>6. Known Problems and Bug Reports</H2>
<p>There are several known problems with the current version of the
Mach64 X server.  They include:
<ul>
<li>Gamma correction is not currently supported.  It will be
supported in a future release.</li>
<li>Screen blanking in 16bpp and 32bpp modes on certain Mach64 CT
cards does not work.</li>
<li>In doublescan modes, only the top half of the hardware cursor
is displayed.  The hardware cursor works fine in all other
modes.</li>
<li>With high refresh rates on certain cards (VT-A3 and CT-D) noise
can become a problem in 32bpp mode.  This usually only happens
with refresh rates of 85Hz or greater and can be fixed by using
a lower refresh rate (e.g., 72Hz or 75Hz).</li>
<li>ISA cards with more than 12Mb of main memory cannot use the
server due to the requirement of a video memory aperture.  This
a major project.</li>
</ul>
</p>
<p>If you are experiencing problems, first check to make sure that you
have the very latest available release (including beta releases).  ATI
releases new cards throughout the year.  Each of these new cards
require additional programming to support the new Mach64 chips,
RAMDACs and clock chips that appear on them.  The most recent release
is most likely to support your video card.</p>
<p>Second, please check the RELNOTES and README files (as well as the
other documentation available with the release).  Third, make sure you
do not have any Ramdac, ClockChip or Clocks lines in your XF86Config
file (all of these are automatically detected by the Mach64 X server).
The "Device" section should only contain the Identifier, VendorName
and BoardName.  All other options should be automatically detected.</p>
<p>If you are still experiencing problems, please send e-mail to
XFree86@XFree86.org or post to the comp.windows.x.i386unix newsgroup.</p>
<p>Please do NOT send e-mail to me since the developers who answer e-mail
sent to XFree86@XFree86.org are better able to answer most questions
and I would like to spend my minimal free time working on new
enhancements to the X server.  Thanks!</p>


<p>
<pre>
$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/Mach64.sgml,v 3.15.2.7 1999/07/05 09:07:28 hohndel Exp $





$XConsortium: Mach64.sgml /main/8 1996/10/28 05:23:52 kaleb $
</pre>
</p>

 <HR NOSHADE>
<A HREF="Mach64.html"><EM>Mach64 X Server Release Notes</EM></A>
 <b>:</b> <EM>Known Problems and Bug Reports</EM><BR>
<b>Previous:</b> <A HREF="Mach645.html"><EM>Cards known to work with this release</EM></A><BR>
<b>Next:</b> <A HREF="Mach64.html"><EM>Mach64 X Server Release Notes</EM></A>



</BODY>
</HTML>
