/[gentoo]/xml/htdocs/doc/en/ati-faq.xml
Gentoo

Diff of /xml/htdocs/doc/en/ati-faq.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.27 Revision 1.28
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/ati-faq.xml,v 1.27 2005/06/28 16:04:36 neysx Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/ati-faq.xml,v 1.28 2005/07/02 12:51:39 swift Exp $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4 4
5<guide link="/doc/en/ati-faq.xml"> 5<guide link="/doc/en/ati-faq.xml">
6<title>Gentoo Linux ATI FAQ</title> 6<title>Gentoo Linux ATI FAQ</title>
7 7
33 33
34<p> 34<p>
35Almost every ATI board is supported by <uri 35Almost every ATI board is supported by <uri
36link="http://www.freedesktop.org/Software/xorg">xorg-x11</uri>, at least for 36link="http://www.freedesktop.org/Software/xorg">xorg-x11</uri>, at least for
37the 2D accelerated features. The 3D support is provided either by <uri 37the 2D accelerated features. The 3D support is provided either by <uri
38link="http://dri.sf.net">the DRI project</uri>, which is already present inside 38link="http://dri.sf.net">the DRI project</uri> which is part of xorg-x11,
39the xorg-x11, or by closed source drivers <uri 39or by ATI's <uri
40link="http://mirror.ati.com/support/drivers/linux/radeon-linux.html"> 40link="http://mirror.ati.com/support/drivers/linux/radeon-linux.html">closed
41provided</uri> by ATI. 41source drivers</uri>.
42</p> 42</p>
43 43
44<table> 44<table>
45<tr> 45<tr>
46 <th>GPU</th> 46 <th>GPU</th>
76 I have an All-In-Wonder/Vivo board. Are the multimedia features supported? 76 I have an All-In-Wonder/Vivo board. Are the multimedia features supported?
77</title> 77</title>
78<body> 78<body>
79 79
80<p> 80<p>
81The multimedia features are actually supported by <uri 81The board's multimedia features are supported by <uri
82link="http://gatos.sf.net">the GATOS project</uri>, the GATOS drivers will be 82link="http://gatos.sf.net">the GATOS project</uri>. These drivers will be
83merged in the xorg tree shortly. 83merged in the xorg tree shortly.
84</p> 84</p>
85 85
86</body> 86</body>
87</section> 87</section>
88<section> 88<section>
89<title>I'm not using an x86. What are my options?</title> 89<title>I'm not using an x86-based architecture. What are my options?</title>
90<body> 90<body>
91 91
92<p> 92<p>
93You have almost the same x11 support on PPC or Alpha platform but you can't 93X11 support on the PPC or Alpha platforms is quite similar to x86 X11 support.
94use the ATI closed source drivers. That means that you can't use the r300 3d 94However, ATI's closed source drivers are not supported on the PPC or Alpha, so
95you cannot use the 3D features of the R300 Graphics Processing Unit (GPU). If
95features at all. If you have such a board and you want it supported by x11, 96you have such a board and want it supported by X11, contact
96you should contact <uri link="http://www.ati.com">ATI</uri> and ask them to open 97<uri link="http://www.ati.com">ATI</uri> and ask them to release the
97the specs. Recently the AMD64 closed source driver has been released. AMD64 98specifications for your system's GPU. The closed source driver for the AMD64
98users can use it as the x86 users. 99was released, so AMD64 users can now enjoy the same features as x86 users.
99</p> 100</p>
100 101
101<impo> 102<impo>
102In order to enable the agpgart for certain AMD64 chip sets you have to disable 103To enable agpgart support for certain AMD64 chip sets, you have to disable
103the K8 IOMMU support 104support for the K8 IOMMU.
104</impo> 105</impo>
105 106
106</body> 107</body>
107</section> 108</section>
108<section> 109<section>
109<title>I have a laptop. Is my "mobility" ATI model supported?</title> 110<title>I have a laptop. Is my ATI Mobility model supported?</title>
110<body> 111<body>
111 112
112<p> 113<p>
113It should be but you may have a configuration issue due to the OEM PCI id that 114It should be, but you may have a configuration issue due to the OEM PCI id that
114such chips may have. In most cases you may have to write the configuration file 115such chips may have. In most cases you may have to write the configuration file
115yourself or use the <c>xorgconfig</c>. 116yourself or use the <c>xorgconfig</c> utility.
116</p> 117</p>
117 118
118</body> 119</body>
119</section> 120</section>
120</chapter> 121</chapter>
165<section> 166<section>
166<title>Configuration</title> 167<title>Configuration</title>
167<body> 168<body>
168 169
169<p> 170<p>
170It is suggested the use of <c>xorgcfg</c>, <c>xorgconfig</c> or directly by 171The use of <c>xorgcfg</c> or <c>xorgconfig</c> to generate the
172<path>xorg.conf</path> configuration file is suggested. Alternatively, you
171using the Xorg auto configuration option: 173may use the Xorg auto configuration option:
172</p> 174</p>
173 175
174<pre caption="Autoconfiguring X"> 176<pre caption="Autoconfiguring X">
175# <i>X -configure</i> 177# <i>X -configure</i>
176</pre> 178</pre>
180please refer to the <uri link="/doc/en/index.xml?catid=desktop">Gentoo 182please refer to the <uri link="/doc/en/index.xml?catid=desktop">Gentoo
181Desktop Documentation Resources</uri>. 183Desktop Documentation Resources</uri>.
182</p> 184</p>
183 185
184<note> 186<note>
185Users of the ati-drivers can also use <c>fglrxconfig</c>. 187You can use <c>fglrxconfig</c> if you have installed the <c>ati-drivers</c>
188package.
186</note> 189</note>
187 190
188<impo> 191<impo>
189PPC users could use the <c>Xautoconf</c> stand alone configuration tool by 192PPC users could use the <c>Xautoconf</c> stand-alone configuration tool by
190emerging the <c>Xautoconf</c> ebuild, but isn't required. 193emerging the <c>Xautoconf</c> ebuild, but isn't required.
191</impo> 194</impo>
192 195
193</body> 196</body>
194</section> 197</section>

Legend:
Removed from v.1.27  
changed lines
  Added in v.1.28

  ViewVC Help
Powered by ViewVC 1.1.20