/[gentoo]/xml/htdocs/doc/en/dri-howto.xml
Gentoo

Diff of /xml/htdocs/doc/en/dri-howto.xml

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

Revision 1.19 Revision 1.40
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/dri-howto.xml,v 1.19 2005/01/19 14:12:38 swift Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/dri-howto.xml,v 1.40 2007/08/23 22:31:14 nightmorph Exp $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4 4
5<guide link="/doc/en/dri-howto.xml"> 5<guide link="/doc/en/dri-howto.xml">
6
6<title>Hardware 3D Acceleration Guide</title> 7<title>Hardware 3D Acceleration Guide</title>
8
7<author title="Author"> 9<author title="Author">
8<mail link="spyderous@gentoo.org">Donnie Berkholz</mail> 10 <mail link="dberkholz@gentoo.org">Donnie Berkholz</mail>
9</author> 11</author>
10<author title="Editor"> 12<author title="Editor">
11<mail link="peesh@gentoo.org">Jorge Paulo</mail> 13 <mail link="peesh@gentoo.org">Jorge Paulo</mail>
12</author> 14</author>
15<author title="Editor">
16 <mail link="nightmorph@gentoo.org">Joshua Saddler</mail>
17</author>
13 18
14<abstract> 19<abstract>
15This document is a guide to getting 3D acceleration working using X11-DRM 20This document is a guide to getting 3D acceleration working using the DRM with
16with Xorg in Gentoo Linux. 21Xorg in Gentoo Linux.
17</abstract> 22</abstract>
18 23
24<!-- The content of this document is licensed under the CC-BY-SA license -->
25<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
19<license/> 26<license/>
20 27
21<version>1.0.8</version> 28<version>1.10</version>
22<date>2005-01-19</date> 29<date>2007-08-23</date>
23 30
24<chapter> 31<chapter>
25<title>Introduction</title> 32<title>Introduction</title>
26<section> 33<section>
27<title>What is hardware 3D acceleration and why do I want it?</title> 34<title>What is hardware 3D acceleration and why do I want it?</title>
44<section> 51<section>
45<title>How do I get hardware 3D acceleration?</title> 52<title>How do I get hardware 3D acceleration?</title>
46<body> 53<body>
47 54
48<p> 55<p>
49In many cases, both binary and open-source drivers exist. Open-source drivers 56In many cases, both binary and open-source drivers exist. Open-source drivers
50are preferable since we're using Linux and open source is one of its underlying 57are preferable since we're using Linux and open source is one of its underlying
51principles. Sometimes, binary drivers are the only option, like with nVidia's 58principles. Sometimes, binary drivers are the only option, like with nVidia's
52cards. Binary drivers include media-video/nvidia-kernel and 59cards. Binary drivers include <c>x11-drivers/nvidia-drivers</c> for nVidia cards
53media-video/nvidia-glx for nVidia cards, media-video/mgavideo for Matrox cards 60and <c>x11-drivers/ati-drivers</c> for ATI cards.
54and media-video/ati-drivers for ATI cards. Other open-source drivers include
55media-video/kyro-kernel for KyroII cards and media-video/ati-gatos for ATI
56cards, which aim to support ATI's video capabilities more fully.
57</p> 61</p>
58 62
59</body> 63</body>
60</section> 64</section>
61<section> 65<section>
62<title>What is DRI?</title> 66<title>What is DRI?</title>
63<body> 67<body>
64 68
65<p> 69<p>
66The Direct Rendering Infrastructure (<uri 70The <uri link="http://dri.freedesktop.org/wiki/">Direct Rendering
67link="http://dri.sourceforge.net">dri.sourceforge.net</uri>), also known as the 71Infrastructure</uri>, also known as the DRI, is a framework for allowing direct
68DRI, is a framework for allowing direct access to graphics hardware in a safe 72access to graphics hardware in a safe and efficient manner. It includes changes
69and efficient manner. It includes changes to the X server, to several client 73to the X server, to several client libraries and to the kernel. The first major
70libraries and to the kernel. The first major use for the DRI is to create fast 74use for the DRI is to create fast OpenGL implementations.
71OpenGL implementations.
72</p> 75</p>
73 76
74</body> 77</body>
75</section>
76<section> 78</section>
79<section>
77<title>What is X11-DRM and how does it relate to regular Xorg?</title> 80<title>What is the DRM and how does it relate to regular Xorg?</title>
78<body> 81<body>
79 82
80<p> 83<p>
81X11-DRM is an <e>enhancement</e> to Xorg that adds 3D acceleration for 84The DRM (Direct Rendering Manager) is an <e>enhancement</e> to Xorg that adds 3D
82cards by adding the kernel module necessary for direct rendering. 85acceleration for cards by adding the kernel module necessary for direct
86rendering.
83</p> 87</p>
84 88
85</body> 89</body>
86</section> 90</section>
87<section> 91<section>
88<title>Purpose</title> 92<title>Purpose</title>
89<body> 93<body>
90 94
91<p> 95<p>
92This guide is for people who can't get direct rendering working with just 96This guide is for people who can't get direct rendering working with just Xorg.
93Xorg. X11-DRM works for 3dfx, gamma, i8x0, matrox, rage128, radeon, mach64 97The DRM works for the following drivers:
94and sis300 series drivers. See the <uri 98</p>
95link="http://dri.sourceforge.net">DRI homepage</uri> for more info and 99
100<ul>
101 <li>3dfx</li>
102 <li>i8x0</li>
103 <li>matrox</li>
104 <li>rage128</li>
105 <li>radeon</li>
106 <li>mach64</li>
107 <li>sis300</li>
108 <li>via</li>
109</ul>
110
111<p>
112See the <uri link="http://dri.freedesktop.org/">DRI homepage</uri> for more info
96documentation. 113and documentation.
97</p> 114</p>
98 115
99</body> 116</body>
100</section> 117</section>
101<section> 118<section>
102<title>Feedback</title> 119<title>Feedback</title>
103<body> 120<body>
104 121
105<p> 122<p>
106With suggestions, questions, etc., e-mail <mail 123With suggestions, questions, etc., e-mail <mail
107link="spyderous@gentoo.org">Donnie Berkholz</mail>. 124link="dberkholz@gentoo.org">Donnie Berkholz</mail>.
108</p> 125</p>
109 126
110</body> 127</body>
111</section> 128</section>
112</chapter> 129</chapter>
133</p> 150</p>
134 151
135<pre caption="Checking your AGP chipset"> 152<pre caption="Checking your AGP chipset">
136# <i>emerge pciutils; lspci | grep AGP</i> 153# <i>emerge pciutils; lspci | grep AGP</i>
137# <i>00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)</i> 154# <i>00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)</i>
138<codenote>Your output may not match the above due to different hardware.</codenote> 155<comment>(Your output may not match the above due to different hardware.)</comment>
139</pre> 156</pre>
140 157
141<p> 158<p>
142If your chipset is not supported by the kernel you might have some succes by 159If your chipset is not supported by the kernel you might have some succes by
143passing <c>agp=try_unsupported</c> as a kernel parameter. This will use Intel's 160passing <c>agp=try_unsupported</c> as a kernel parameter. This will use Intel's
144generic routines for AGP support. To add this parameter, edit your bootloader 161generic routines for AGP support. To add this parameter, edit your bootloader
145configuration file! 162configuration file!
146</p> 163</p>
147 164
148<p> 165<p>
149Most, if not all, kernels should have these options. This was configured using 166Most, if not all, kernels should have these options. This was configured using a
150gentoo-sources-2.4.20-r5. 167standard <c>gentoo-sources</c> kernel.
151</p> 168</p>
152 169
153<pre caption="Configuring the kernel"> 170<pre caption="Configuring the kernel">
154# <i>ls -l /usr/src/linux </i> 171# <i>ls -l /usr/src/linux </i>
155lrwxrwxrwx 1 root root 22 May 29 18:20 /usr/src/linux -> linux-2.4.20-gentoo-r5 172lrwxrwxrwx 1 root root 22 2007-02-14 20:12 /usr/src/linux -> linux-2.6.18-gentoo-r4
156<codenote>Make sure /usr/src/linux links to your current kernel.</codenote> 173<comment>(Make sure /usr/src/linux links to your current kernel.)</comment>
157# <i>cd /usr/src/linux</i> 174# <i>cd /usr/src/linux</i>
158# <i>make menuconfig</i> 175# <i>make menuconfig</i>
159</pre> 176</pre>
160 177
161<pre caption="make menuconfig options"> 178<pre caption="make menuconfig options">
162Processor type and features ---&gt; 179Processor type and features --->
163&lt;*&gt; MTRR (Memory Type Range Register) support 180&lt;*&gt; MTRR (Memory Type Range Register) support
181Device drivers --->
164Character devices ---&gt; 182 Character devices --->
165&lt;M&gt; /dev/agpgart (AGP Support) 183 &lt;M&gt; /dev/agpgart (AGP Support)
166[*] Intel 440LX/BX/GX and I815/I820/I830M/I830MP/I840/I845/I850/I860 support 184 <comment>(The agpgart option is not present on 64-bit kernels; just choose your chipset support.)</comment>
185 &lt;M&gt; Intel 440LX/BX/GX, I8xx and E7x05 support
167<codenote>Enable your chipset instead of the above.</codenote> 186<comment>(Enable your chipset instead of the above.)</comment>
168[ ] Direct Rendering Manager (XFree86 DRI support) 187 &lt;M&gt; Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
169</pre>
170
171<p>
172Make sure the Direct Rendering Manager (DRM) is <e>off</e>. The X11-DRM
173package will provide its own.
174</p> 188</pre>
175 189
176</body> 190</body>
177</section> 191</section>
178<section> 192<section>
179<title>Compile and install your kernel</title> 193<title>Compile and install your kernel</title>
180<body> 194<body>
181 195
182<pre caption="Compiling and installing kernel"> 196<pre caption="Compiling and installing kernel">
183# <i>make dep &amp;&amp; make clean bzImage modules modules_install</i> 197# <i>make &amp;&amp; make modules_install</i>
184# <i>mount /boot</i>
185# <i>cp arch/i386/boot/bzImage /boot</i>
186</pre> 198</pre>
187 199
188<p>
189If you want your kernel to be named something other than bzImage, be sure to
190copy to /boot/yourname instead. Don't forget to set up grub.conf or lilo.conf
191and run /sbin/lilo if you use LILO.
192</p> 200<p>
201Don't forget to set up <path>grub.conf</path> or <path>lilo.conf</path> and run
202<c>/sbin/lilo</c> if you use LILO.
203</p>
193 204
194</body> 205</body>
195</section>
196</chapter>
197
198<chapter>
199<title>Install X11-DRM and configure direct rendering</title>
200<section> 206</section>
201<title>Install X11-DRM</title> 207</chapter>
202<body>
203 208
204<pre caption="Installing X11-DRM"> 209<chapter>
205# <i>emerge x11-drm</i> 210<title>Configure direct rendering</title>
206</pre> 211<section id="configure_xorg">
207
208</body>
209</section>
210<section>
211<title>Configure Xorg.conf</title> 212<title>Configure Xorg.conf</title>
212<body> 213<body>
213 214
214<p> 215<p>
215Open <path>/etc/X11/xorg.conf</path> with your favorite text editor and edit 216Open <path>/etc/X11/xorg.conf</path> with your favorite text editor and edit
224 ... 225 ...
225EndSection 226EndSection
226... 227...
227Section "Device" 228Section "Device"
228 Driver "radeon" 229 Driver "radeon"
230 <comment>(Replace radeon with the name of your driver.)</comment>
229 ... 231 ...
230EndSection 232EndSection
231... 233...
232Section "dri" 234Section "dri"
233 Mode 0666 235 Mode 0666
234EndSection 236EndSection
235</pre> 237</pre>
236 238
237<p> 239</body>
238If you are using a different driver, replace "radeon" with yours. 240</section>
241<section>
242<title>Changes to modules.autoload.d</title>
243<body>
244
239</p> 245<p>
246You will need to add the module name that your card uses to
247<path>/etc/modules.autoload.d/kernel-2.6</path> to ensure that the module is
248loaded automatically when the system starts up.
249</p>
250
251<pre caption="Editing /etc/modules.autoload.d/kernel-2.6">
252<comment>(Change module name as required.)</comment>
253intel-agp
254</pre>
255
256<note>
257If you compiled <c>agpgart</c> as a module, you will also need to add it to
258<path>/etc/modules.autoload.d/kernel-2.6</path>.
259</note>
240 260
241</body> 261</body>
242</section> 262</section>
243</chapter> 263</chapter>
244 264
247<section> 267<section>
248<title>Reboot to the new kernel</title> 268<title>Reboot to the new kernel</title>
249<body> 269<body>
250 270
251<p> 271<p>
252Reboot your computer to your new kernel. It's time to see if you have direct 272Reboot your computer to your new kernel and login as a normal user. It's time to
253rendering and how good it is. 273see if you have direct rendering and how good it is. <c>glxinfo</c> and
274<c>glxgears</c> are part of the <c>mesa-progs</c> package, so make sure it is
275installed before you attempt to run these commands.
254</p> 276</p>
255 277
256<pre caption="Testing rendering"> 278<pre caption="Testing rendering">
257# <i>startx</i> 279$ <i>startx</i>
258<codenote>No need to load modules for your driver or agpgart, if you compiled agpgart as a module.</codenote> 280<comment>(No need to load modules for your driver or agpgart, even if you compiled them as a module.)</comment>
259<codenote>They will be loaded automatically.</codenote> 281<comment>(They will be loaded automatically.)</comment>
260# <i>glxinfo | grep rendering</i> 282$ <i>glxinfo | grep rendering</i>
261direct rendering: Yes 283direct rendering: Yes
262<codenote>If it says "No," you don't have 3D acceleration.</codenote> 284<comment>(If it says "No", you don't have 3D acceleration.)</comment>
263# <i>glxgears</i> 285$ <i>glxgears</i>
264<codenote>Test your frames per second (FPS) at the default size. The number should be </codenote> 286<comment>(Test your frames per second (FPS) at the default size. The number should be
265<codenote>significantly higher than before installing x11-drm. Do this while the CPU is as idle as possible.</codenote> 287significantly higher than before configuring DRM. Do this while the CPU is as idle as
288possible.)</comment>
266</pre> 289</pre>
267 290
268</body> 291<note>
269</section> 292FPS may be limited by your screen's refresh rate, so keep this in mind if
270</chapter> 293<c>glxgears</c> reports only about 70-100 FPS. <c>games-fps/ut2004-demo</c> is a
294better benchmarking tool, as it can give you real-world performance results.
295</note>
271 296
272<chapter> 297</body>
273<title>Using the CVS sources</title>
274<section> 298</section>
275<body> 299</chapter>
276 300
277<warn> 301<chapter>
278Don't do this if the package worked. 302<title>Tweak your performance</title>
279</warn>
280
281</body>
282</section> 303<section>
283<section> 304<title>Get the most out of direct rendering</title>
284<title>Do you need the CVS?</title>
285<body>
286
287<p>
288First you have to check whether the x11-drm package works. If it doesn't and
289you have checked your logs to verify it's not a configuration error, you might
290want to consider the CVS sources. There are also daily driver snapshots
291available if you do not wish to build the full CVS.
292</p>
293
294</body> 305<body>
295</section>
296<section>
297<title>Do the CVS sources support your card?</title>
298<body>
299 306
300<p>
301Check the DRI <uri
302link="http://dri.sourceforge.net/cgi-bin/moin.cgi/Status">supported cards
303list</uri> to see if the CVS supports your card. Even if it doesn't, but it
304supports a similar card, try it.
305</p> 307<p>
308A few options may increase performance by up to 30 percent (or more) over the
309default. Set them in <path>/etc/X11/xorg.conf</path>. However, you will first
310need to check that your motherboard and video card support these options.
311</p>
306 312
307<!-- I see a couple of 8x AGP stuff on the Internet about vanilla 2.4 kernels; 313<p>
308 is this now available or not? I've commented it out for the time being, 314First, let's see if your video card can support fast writes. We'll do this by
309 hoping that this doesn't affect us :) 315closely inspecting the output from <c>lspci</c>. Specifically, we are looking
316at the "VGA compatible controller" information.
317</p>
310 318
311<warn> 319<pre caption="Video card check">
312"Linux 2.4 doesn't support agp 8x, so I had to go find a backport. The backport 320# <i>lspci -vv</i>
313works .... it doesn't patch quite properly, and it requires 2.4.21 (I've only 32101:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY (prog-if 00 [VGA])
314gotten it to work with vanilla, straight from the tarball (not ebuild)). First 322. . .
315go get the 2.4.20-2.4.21 patch from kernel.org .... (then get the patch,) It 323Capabilities: [58] AGP version 2.0
316was on a mailing list somewhere. It doesn't patch cleanly - - one file fails, 324 Status: RQ=48 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
317the pci_ids.h file, but if you actually read the file and the reject list, it's 325</pre>
318very easy to fix. But it does load, and it gives me 1600x1200 with video 326
319(although a bit slow b/c of lack of dga) with xfree-drm." (SanityInAnarchy on 327<p>
320#gentoo) 328While quite a lot of information is produced, we are looking for <b>FW</b> in
321</warn> 329the "Status" subsection of the AGP "Capabilities" section. If <b>FW+</b> is
330present in the "Status" line, it means the card supports fast writes. We can
331now check if the motherboard supports fast writes.
332</p>
322 333
323<impo> 334<impo>
324The patch is a little tricky to work with but <uri 335If you do not see <b>FW+</b>, but instead see <b>FW-</b>, you cannot enable
325link="http://www.ussg.iu.edu/hypermail/linux/kernel/0302.2/att-1618/01-agp3.diff.bz2">here's 336fast writes in <path>xorg.conf</path>. Your card does not support fast writes.
326the link</uri>. If you can disable 8X AGP in your BIOS, change it to 4X and you
327may not need the patch.
328</impo> 337</impo>
329-->
330 338
331</body>
332</section>
333<section>
334<title>Follow the CVS Instructions</title>
335<body>
336
337<p>
338The DRI project has a document about CVS compiling themselves. Please read <uri
339link="http://dri.sourceforge.net/cgi-bin/moin.cgi/Building">the document</uri>
340and follow the instructions up to the <e>Installing for XFree86</e> or
341<e>Installing for X.org</e> part.
342</p> 339<p>
343 340Now let's make sure the motherboard supports fast writes as well. This time,
344</body> 341look at the "Host bridge" section of your <c>lspci</c> output.
345</section>
346<section>
347<title>Install the CVS</title>
348<body>
349
350<p> 342</p>
351Verify that the DRI kernel module(s) for your system were built: 343
344<pre caption="Motherboard check">
345# <i>lspci -vv</i>
34600:00.0 Host bridge: Intel Corporation 82830 830 Chipset Host Bridge (rev 02)
347. . .
348Capabilities: [a0] AGP version 2.0
349 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
350</pre>
351
352</p> 352<p>
353 353Again, examine the "Status" subsection of your AGP "Capabilities" section. Look
354<pre caption="Verification"> 354for <b>FW</b>. If you see <b>FW+</b>, your motherboard supports fast writes.
355# <i>cd ~/DRI-CVS/build/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel; ls</i>
356</pre>
357
358<p> 355</p>
359For the 3dfx Voodoo, you should see <path>tdfx.o</path>. For the Matrox 356
360G200/G400, you should see <path>mga.o</path>. For the ATI Rage 128, you should 357<impo>
361see <path>r128.o</path>. For the ATI Radeon, you should see 358Remember, both your video card information and your motherboard information
362<path>radeon.o</path>. For the Intel i810, you should see <path>i810.o</path>. 359must show the same <b>FW</b> capability. If either device shows <b>FW-</b> in
363If the DRI kernel module(s) failed to build, you should verify that you're 360"Status", you cannot enable fast writes in <path>xorg.conf</path>.
364using the right version of the Linux kernel. The most recent kernels are not 361</impo>
365always supported. 362
366</p> 363<p>
367 364Assuming that all has gone well and both your motherboard and video card
368<p> 365support fast writes, let's enable this option in
369Install over your XFree86 or X.org installation. You may wish to back up xfree 366<path>/etc/X11/xorg.conf</path> and get the best performance out of your
370or xorg-x11. 367hardware.
371</p>
372
373<pre caption="Backing up Xorg">
374# <i>quickpkg xorg-x11</i>
375<codenote>This backs up your Xorg-X11 package.</codenote>
376# <i>make install</i>
377</pre>
378
379<p>
380Follow the "Configure Xorg" section above.
381</p>
382
383<p>
384To load the appropriate DRM module in your running kernel, copy the kernel
385module to <path>/lib/modules/`uname -r`/kernel/drivers/char/drm/</path> then
386run <c>modules-update</c> and restart your X server. If you're not running the
387kernel you'll be using it in, instead of <c>`uname -r`,</c> use that kernel's
388name.
389</p>
390
391<warn>
392Make sure you first unload any older DRI kernel modules that might be already
393loaded. Note that some DRM modules require that the agpgart module be loaded
394first.
395</warn>
396
397</body>
398</section>
399</chapter>
400
401<chapter>
402<title>Tweak your performance</title>
403<section>
404<title>Get the most out of direct rendering</title>
405<body>
406
407<p>
408A few options may increase performance by up to 30 percent (or more) over the
409default. Set them in <path>/etc/X11/xorg.conf</path>.
410</p> 368</p>
411 369
412<pre caption="xorg.conf"> 370<pre caption="xorg.conf">
413Section "Device" 371Section "Device"
414 Option "AGPMode" "4" 372 Option "AGPMode" "4"
415 <codenote>This increased FPS from 609 to 618.</codenote> 373 <comment>(This increased FPS from 609 to 618.)</comment>
416 Option "AGPFastWrite" "True" 374 Option "AGPFastWrite" "True"
417 <codenote>This had no measurable effect, but it may increase instability of your computer.</codenote> 375 <comment>(This had no measurable effect, but it may increase instability of your computer.)</comment>
418 <codenote>You may also need to set it in your BIOS.</codenote> 376 <comment>(You may also need to set it in your BIOS.)</comment>
419 Option "EnablePageFlip" "True" 377 Option "EnablePageFlip" "True"
420 <codenote>This improved FPS from 618 to 702. It also is "risky" but few people have reported problems.</codenote> 378 <comment>(This improved FPS from 618 to 702. It also is "risky" but few people have reported problems.)</comment>
421 ... 379 ...
422EndSection 380EndSection
423</pre> 381</pre>
424 382
383<warn>
384Enabling <c>AGPFastWrite</c> on a VIA chipset will very likely cause your
385machine to lock up. VIA chipsets do not play nicely with fast writes, so use
386this setting at your own risk.
387</warn>
388
389<note>
390Remember, if you want fast writes to work properly, you will have to first
391enable the appropriate option in your BIOS.
392</note>
393
425<p> 394<p>
426If you want to set even more features, check out the <uri 395If you want to set even more features, check out the <uri
396link="http://dri.freedesktop.org/wiki/FeatureMatrix">feature matrix</uri> on
397the DRI web site or the <uri
427link="http://dri.sourceforge.net/doc/dri_driver_features.phtml">features 398link="http://dri.sourceforge.net/doc/dri_driver_features.phtml">features
428listing</uri> on the DRI Web site. 399listing</uri> on Sourceforge.
429</p> 400</p>
430 401
431</body> 402</body>
432</section> 403</section>
433</chapter> 404</chapter>
434 405
435<chapter> 406<chapter>
436<title>Troubleshooting</title> 407<title>Troubleshooting</title>
437<section> 408<section>
438<title>It doesn't work. I just recompiled my kernel or switched to a new one.</title>
439<body>
440
441<p>
442Whenever you rebuild your kernel or switch to another kernel, you'll have to
443rebuild the kernel module. Note that you don't need to remerge xfree or
444xorg-x11, but you will need to remerge x11-drm.
445</p>
446
447</body>
448</section>
449
450<section>
451<title>It doesn't work. I don't have rendering, and I can't tell why.</title> 409<title>It doesn't work. I don't have rendering, and I can't tell why.</title>
452<body> 410<body>
453 411
454<p> 412<p>
455Try <c>insmod radeon</c> before you start the X server. Also, try building 413Try <c>modprobe radeon</c> before you start the X server (replace <c>radeon</c>
456agpgart into the kernel instead of as a module. 414with the name of your driver). Also, try building agpgart into the kernel
415instead of as a module.
457</p> 416</p>
458 417
459</body> 418</body>
460</section> 419</section>
461<section> 420<section>
468</p> 427</p>
469 428
470</body> 429</body>
471</section> 430</section>
472<section> 431<section>
473<title>Direct rendering doesn't work, and in /var/log/Xorg.0.log I have an error about driver version too low.</title>
474<body>
475
476<p>
477You aren't using the x11-drm driver. Check if you compiled DRM and the driver
478into the kernel; you shouldn't have.
479</p>
480
481</body>
482</section>
483<section>
484<title>I have a Radeon, and I want TV-Out.</title> 432<title>I have a Radeon, and I want TV-Out.</title>
485<body> 433<body>
486 434
487<p> 435<p>
488Check out ati-gatos drivers. <c>emerge -s gatos</c>. 436The drivers originally developed by the <uri
437link="http://gatos.sf.net">GATOS</uri> project have been merged into Xorg's
438codebase. You don't need anything special for TV-Out;
439<c>x11-drivers/xf86-video-ati</c> will work just fine.
489</p> 440</p>
490 441
491</body> 442</body>
492</section>
493<section> 443</section>
444<section>
445<title>
494<title>It doesn't work. My card is so incredibly new and cool that it isn't supported at all.</title> 446It doesn't work. My card is so incredibly new and cool that it isn't supported
447at all.
448</title>
495<body> 449<body>
496 450
497<p> 451<p>
498Try out the binary drivers. For ati-drivers, a listing is at 452Try out the binary drivers. For <c>ati-drivers</c>, a listing is at
499<uri>http://www.schneider-digital.de/html/download_ati.html</uri>. If those 453<uri>http://ati.amd.com/support/drivers/linux/linux-radeon.html</uri> (for x86)
454and at <uri>http://ati.amd.com/support/drivers/linux64/linux64-radeon.html</uri>
500don't support it, use fbdev. It's slow, but it works. 455(for amd64). If those don't support it, use fbdev. It's slow, but it works.
501</p> 456</p>
502 457
503</body> 458</body>
504</section> 459</section>
505<section> 460<section>
506<title>I have a PCI card and it doesn't work. Help!</title> 461<title>I have a PCI card and it doesn't work. Help!</title>
507<body> 462<body>
508 463
509<p> 464<p>
510In section "Device" enable ForcePCIMode. 465Edit <path>/etc/X11/xorg.conf</path>. In section "Device" enable ForcePCIMode.
511</p> 466</p>
512 467
513<pre caption="Enabling ForcePCIMode"> 468<pre caption="Enabling ForcePCIMode">
514Option "ForcePCIMode" "True" 469Option "ForcePCIMode" "True"
515</pre> 470</pre>
542<title>References</title> 497<title>References</title>
543<section> 498<section>
544<body> 499<body>
545 500
546<ol> 501<ol>
547 <li>http://forums.gentoo.org/viewtopic.php?t=46681</li> 502 <li><uri>http://forums.gentoo.org/viewtopic.php?t=46681</uri></li>
548 <li>http://forums.gentoo.org/viewtopic.php?t=29264</li> 503 <li><uri>http://forums.gentoo.org/viewtopic.php?t=29264</uri></li>
549 <li>http://dri.sourceforge.net/</li> 504 <li><uri>http://dri.freedesktop.org/</uri></li>
550 <li>http://www.retinalburn.net/linux/dri_status.html</li> 505 <li><uri>http://www.retinalburn.net/linux/dri_status.html</uri></li>
551</ol> 506</ol>
552 507
553</body> 508</body>
554</section> 509</section>
555</chapter> 510</chapter>

Legend:
Removed from v.1.19  
changed lines
  Added in v.1.40

  ViewVC Help
Powered by ViewVC 1.1.20