doc/en/ati-faq.xml

<?xml version='1.0' encoding="UTF-8"?>
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/ati-faq.xml,v 1.28 2005/07/02 12:51:39 swift Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">

<guide link="/doc/en/ati-faq.xml">
<title>Gentoo Linux ATI FAQ</title>

<author title="Author">
  <mail link="lu_zero@gentoo.org">Luca Barbato</mail>
</author>
<author title="Editor">
  <mail link="peesh@gentoo.org">Jorge Paulo</mail>
</author>
<author title="Editor">
  <mail link="blubber@gentoo.org">Tiemo Kieft</mail>
</author>

<abstract>
This FAQ should help users avoid some common installation and configuration
issues related to DRI and X11 for ATI boards.
</abstract>

<license/>

<version>1.0.12</version>
<date>2005-07-02</date>

<chapter>
<title>Hardware Support</title>
<section>
<title>Is my ATI board supported?</title>
<body>

<p>
Almost every ATI board is supported by <uri 
link="http://www.freedesktop.org/Software/xorg">xorg-x11</uri>, at least for 
the 2D accelerated features.  The 3D support is provided either by <uri 
link="http://dri.sf.net">the DRI project</uri> which is part of xorg-x11, 
or by ATI's <uri 
link="http://mirror.ati.com/support/drivers/linux/radeon-linux.html">closed
source drivers</uri>.
</p>

<table>
<tr>
  <th>GPU</th>
  <th>Common Name</th>
  <th>Support</th>
</tr>
<tr>
  <ti>Rage128</ti>
  <ti>Rage128</ti>
  <ti>xorg DRI</ti>
</tr>
<tr>
  <ti>R100</ti>
  <ti>Radeon7xxx, Radeon64</ti>
  <ti>xorg DRI</ti>
</tr>
<tr>
  <ti>R200, R250, R280</ti>
  <ti>Radeon8500, Radeon9000, Radeon9200</ti>
  <ti>xorg DRI, ATI DRI</ti>
</tr>
<tr>
  <ti>R300, R400, R500</ti>
  <ti>Radeon 9500 - x800</ti>
  <ti>xorg 2D, ATI DRI</ti>
</tr>
</table>

</body>
</section>
<section>
<title>
  I have an All-In-Wonder/Vivo board.  Are the multimedia features supported?
</title>
<body>

<p>
The board's multimedia features are supported by <uri 
link="http://gatos.sf.net">the GATOS project</uri>. These drivers will be 
merged in the xorg tree shortly.
</p>

</body>
</section>
<section>
<title>I'm not using an x86-based architecture.  What are my options?</title>
<body>

<p>
X11 support on the PPC or Alpha platforms is quite similar to x86 X11 support.
However, ATI's closed source drivers are not supported on the PPC or Alpha, so
you cannot use the 3D features of the R300 Graphics Processing Unit (GPU). If
you have such a board and want it supported by X11, contact
<uri link="http://www.ati.com">ATI</uri> and ask them to release the
specifications for your system's GPU. The closed source driver for the AMD64
was released, so AMD64 users can now enjoy the same features as x86 users.
</p>

<impo>
To enable agpgart support for certain AMD64 chip sets, you have to disable 
support for the K8 IOMMU.
</impo>

</body>
</section>
<section>
<title>I have a laptop.  Is my ATI Mobility model supported?</title>
<body>

<p>
It should be, but you may have a configuration issue due to the OEM PCI id that 
such chips may have. In most cases you may have to write the configuration file
yourself or use the <c>xorgconfig</c> utility.
</p>

</body>
</section>
</chapter>

<chapter>
<title>Installation</title>
<section>
<title>Packages</title>
<body>

<ul>
  <li>The <c>xorg-x11</c> ebuild provides the X11 implementation</li>
  <li>
    For a 2.6.x kernel the DRI modules can be built with the kernel or be
    provided by the <c>x11-drm</c> ebuild
  </li>
  <li>
    For a 2.4.x kernel series you must use the <c>x11-drm</c> ebuild
  </li>
  <li>
    The <c>ati-drivers</c> ebuild provides the ATI closed source X drivers
    and kernel modules, for both the 2.4 and 2.6 series kernels
  </li>
</ul>

<p>
If you want to use ATI's <e>internal</e> agpgart support instead of the Linux
kernel one, the agpgart driver and the chip set specific driver (in your kernel
configuration) must be built as modules or not at all.
</p>

<pre caption="Installing drivers">
<comment>(If you want just the Rage128 drivers and modules installed with X11)</comment>
# <i>VIDEO_CARDS="rage128" emerge x11-drm</i>
<comment>(To have just the Radeon support)</comment>
<comment>(R100, R200, R250, R280, but not R300 yet)</comment>
# <i>VIDEO_CARDS="radeon" emerge x11-drm</i>
<comment>(To install the ATI closed source drivers)</comment>
<comment>(R200, R250, R280 and R300 only)</comment>
# <i>emerge ati-drivers</i>
<comment>(To install X11 without any kernel modules)</comment>
# <i>emerge xorg-x11</i>
</pre>

</body>
</section>
<section>
<title>Configuration</title>
<body>

<p>
The use of <c>xorgcfg</c> or <c>xorgconfig</c> to generate the 
<path>xorg.conf</path> configuration file is suggested. Alternatively, you
may use the Xorg auto configuration option:
</p>

<pre caption="Autoconfiguring X">
# <i>X -configure</i>
</pre>

<p>
For more information on how to get a basic <c>xorg.conf</c> configuration file,
please refer to the <uri link="/doc/en/index.xml?catid=desktop">Gentoo
Desktop Documentation Resources</uri>.
</p>

<note>
You can use <c>fglrxconfig</c> if you have installed the <c>ati-drivers</c>
package.
</note>

<impo>
PPC users could use the <c>Xautoconf</c> stand-alone configuration tool by
emerging the <c>Xautoconf</c> ebuild, but isn't required.
</impo>

</body>
</section>
</chapter>
</guide>
1	peesh	1.1	<?xml version='1.0' encoding="UTF-8"?>
2	swift	1.29	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/ati-faq.xml,v 1.28 2005/07/02 12:51:39 swift Exp $ -->
3	peesh	1.1	<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4
5			<guide link="/doc/en/ati-faq.xml">
6	swift	1.23	<title>Gentoo Linux ATI FAQ</title>
7	swift	1.22
8	swift	1.7	<author title="Author">
9			<mail link="lu_zero@gentoo.org">Luca Barbato</mail>
10	peesh	1.1	</author>
11	swift	1.7	<author title="Editor">
12			<mail link="peesh@gentoo.org">Jorge Paulo</mail>
13	peesh	1.1	</author>
14	swift	1.7	<author title="Editor">
15			<mail link="blubber@gentoo.org">Tiemo Kieft</mail>
16	blubber	1.5	</author>
17	peesh	1.1
18	swift	1.7	<abstract>
19			This FAQ should help users avoid some common installation and configuration
20	swift	1.29	issues related to DRI and X11 for ATI boards.
21	swift	1.7	</abstract>
22	peesh	1.1
23	swift	1.3	<license/>
24
25	swift	1.29	<version>1.0.12</version>
26			<date>2005-07-02</date>
27	peesh	1.1
28			<chapter>
29			<title>Hardware Support</title>
30			<section>
31	peesh	1.2	<title>Is my ATI board supported?</title>
32	peesh	1.1	<body>
33	swift	1.7
34			<p>
35			Almost every ATI board is supported by <uri
36	swift	1.22	link="http://www.freedesktop.org/Software/xorg">xorg-x11</uri>, at least for
37			the 2D accelerated features. The 3D support is provided either by <uri
38	swift	1.28	link="http://dri.sf.net">the DRI project</uri> which is part of xorg-x11,
39			or by ATI's <uri
40			link="http://mirror.ati.com/support/drivers/linux/radeon-linux.html">closed
41			source drivers</uri>.
42	peesh	1.1	</p>
43
44			<table>
45	swift	1.7	<tr>
46			<th>GPU</th>
47			<th>Common Name</th>
48			<th>Support</th>
49			</tr>
50			<tr>
51	swift	1.29	<ti>Rage128</ti>
52	swift	1.7	<ti>Rage128</ti>
53	lu_zero	1.9	<ti>xorg DRI</ti>
54	swift	1.7	</tr>
55			<tr>
56	swift	1.29	<ti>R100</ti>
57	swift	1.7	<ti>Radeon7xxx, Radeon64</ti>
58	lu_zero	1.9	<ti>xorg DRI</ti>
59	swift	1.7	</tr>
60			<tr>
61	swift	1.29	<ti>R200, R250, R280</ti>
62	swift	1.13	<ti>Radeon8500, Radeon9000, Radeon9200</ti>
63	lu_zero	1.9	<ti>xorg DRI, ATI DRI</ti>
64	swift	1.7	</tr>
65			<tr>
66	swift	1.29	<ti>R300, R400, R500</ti>
67	lu_zero	1.25	<ti>Radeon 9500 - x800</ti>
68	lu_zero	1.9	<ti>xorg 2D, ATI DRI</ti>
69	swift	1.7	</tr>
70	peesh	1.1	</table>
71
72			</body>
73			</section>
74			<section>
75	swift	1.7	<title>
76	swift	1.22	I have an All-In-Wonder/Vivo board. Are the multimedia features supported?
77	swift	1.7	</title>
78	peesh	1.1	<body>
79	swift	1.7
80			<p>
81	swift	1.28	The board's multimedia features are supported by <uri
82			link="http://gatos.sf.net">the GATOS project</uri>. These drivers will be
83	swift	1.22	merged in the xorg tree shortly.
84	swift	1.7	</p>
85
86	peesh	1.1	</body>
87			</section>
88			<section>
89	swift	1.28	<title>I'm not using an x86-based architecture. What are my options?</title>
90	peesh	1.1	<body>
91	swift	1.7
92			<p>
93	swift	1.28	X11 support on the PPC or Alpha platforms is quite similar to x86 X11 support.
94			However, ATI's closed source drivers are not supported on the PPC or Alpha, so
95			you cannot use the 3D features of the R300 Graphics Processing Unit (GPU). If
96			you have such a board and want it supported by X11, contact
97			<uri link="http://www.ati.com">ATI</uri> and ask them to release the
98			specifications for your system's GPU. The closed source driver for the AMD64
99			was released, so AMD64 users can now enjoy the same features as x86 users.
100	swift	1.7	</p>
101
102	lu_zero	1.19	<impo>
103	swift	1.28	To enable agpgart support for certain AMD64 chip sets, you have to disable
104			support for the K8 IOMMU.
105	lu_zero	1.19	</impo>
106
107	peesh	1.1	</body>
108			</section>
109			<section>
110	swift	1.28	<title>I have a laptop. Is my ATI Mobility model supported?</title>
111	peesh	1.1	<body>
112	swift	1.7
113			<p>
114	swift	1.28	It should be, but you may have a configuration issue due to the OEM PCI id that
115			such chips may have. In most cases you may have to write the configuration file
116			yourself or use the <c>xorgconfig</c> utility.
117	peesh	1.1	</p>
118
119			</body>
120			</section>
121			</chapter>
122
123			<chapter>
124			<title>Installation</title>
125			<section>
126			<title>Packages</title>
127			<body>
128	swift	1.7
129	swift	1.17	<ul>
130	swift	1.22	<li>The <c>xorg-x11</c> ebuild provides the X11 implementation</li>
131			<li>
132			For a 2.6.x kernel the DRI modules can be built with the kernel or be
133			provided by the <c>x11-drm</c> ebuild
134			</li>
135			<li>
136			For a 2.4.x kernel series you must use the <c>x11-drm</c> ebuild
137			</li>
138			<li>
139			The <c>ati-drivers</c> ebuild provides the ATI closed source X drivers
140			and kernel modules, for both the 2.4 and 2.6 series kernels
141			</li>
142	swift	1.17	</ul>
143	swift	1.7
144	swift	1.21	<p>
145			If you want to use ATI's <e>internal</e> agpgart support instead of the Linux
146	swift	1.23	kernel one, the agpgart driver and the chip set specific driver (in your kernel
147	swift	1.21	configuration) must be built as modules or not at all.
148			</p>
149	swift	1.7
150	swift	1.17	<pre caption="Installing drivers">
151	swift	1.29	<comment>(If you want just the Rage128 drivers and modules installed with X11)</comment>
152	lu_zero	1.9	# <i>VIDEO_CARDS="rage128" emerge x11-drm</i>
153	neysx	1.18	<comment>(To have just the Radeon support)</comment>
154	swift	1.29	<comment>(R100, R200, R250, R280, but not R300 yet)</comment>
155	lu_zero	1.9	# <i>VIDEO_CARDS="radeon" emerge x11-drm</i>
156	neysx	1.18	<comment>(To install the ATI closed source drivers)</comment>
157	swift	1.29	<comment>(R200, R250, R280 and R300 only)</comment>
158	blubber	1.5	# <i>emerge ati-drivers</i>
159	swift	1.29	<comment>(To install X11 without any kernel modules)</comment>
160	lu_zero	1.9	# <i>emerge xorg-x11</i>
161	peesh	1.1	</pre>
162	swift	1.7
163	peesh	1.1	</body>
164			</section>
165			<section>
166			<title>Configuration</title>
167			<body>
168	swift	1.7
169			<p>
170	swift	1.28	The use of <c>xorgcfg</c> or <c>xorgconfig</c> to generate the
171			<path>xorg.conf</path> configuration file is suggested. Alternatively, you
172			may use the Xorg auto configuration option:
173	swift	1.7	</p>
174
175	lu_zero	1.10	<pre caption="Autoconfiguring X">
176	blubber	1.5	# <i>X -configure</i>
177	peesh	1.1	</pre>
178	swift	1.7
179			<p>
180	lu_zero	1.9	For more information on how to get a basic <c>xorg.conf</c> configuration file,
181	neysx	1.27	please refer to the <uri link="/doc/en/index.xml?catid=desktop">Gentoo
182	swift	1.8	Desktop Documentation Resources</uri>.
183	swift	1.7	</p>
184
185			<note>
186	swift	1.28	You can use <c>fglrxconfig</c> if you have installed the <c>ati-drivers</c>
187			package.
188	swift	1.7	</note>
189
190			<impo>
191	swift	1.28	PPC users could use the <c>Xautoconf</c> stand-alone configuration tool by
192	lu_zero	1.14	emerging the <c>Xautoconf</c> ebuild, but isn't required.
193	swift	1.7	</impo>
194
195	peesh	1.1	</body>
196			</section>
197			</chapter>
198			</guide>