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

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

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.42 - (show annotations) (download) (as text)
Wed Sep 10 21:20:28 2008 UTC (5 years, 11 months ago) by nightmorph
Branch: MAIN
Changes since 1.41: +10 -9 lines
File MIME type: application/xml
updated dri-howto per an email. the DRI kernel options have moved around a bit

1 <?xml version="1.0" encoding="UTF-8"?>
2 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/dri-howto.xml,v 1.41 2008/05/21 19:29:22 swift Exp $ -->
3 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4
5 <guide link="/doc/en/dri-howto.xml">
6
7 <title>Hardware 3D Acceleration Guide</title>
8
9 <author title="Author">
10 <mail link="dberkholz@gentoo.org">Donnie Berkholz</mail>
11 </author>
12 <author title="Editor">
13 <mail link="peesh@gentoo.org">Jorge Paulo</mail>
14 </author>
15 <author title="Editor">
16 <mail link="nightmorph@gentoo.org">Joshua Saddler</mail>
17 </author>
18
19 <abstract>
20 This document is a guide to getting 3D acceleration working using the DRM with
21 Xorg in Gentoo Linux.
22 </abstract>
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 -->
26 <license/>
27
28 <version>1.11</version>
29 <date>2008-09-10</date>
30
31 <chapter>
32 <title>Introduction</title>
33 <section>
34 <title>What is hardware 3D acceleration and why do I want it?</title>
35 <body>
36
37 <p>
38 With hardware 3D acceleration, three-dimensional rendering uses the graphics
39 processor on your video card instead of taking up valuable CPU resources
40 drawing 3D images. It's also referred to as "hardware acceleration" instead of
41 "software acceleration" because without this 3D acceleration your CPU is forced
42 to draw everything itself using the Mesa software rendering libraries, which
43 takes up quite a bit of processing power. While Xorg typically supports 2D
44 hardware acceleration, it often lacks hardware 3D acceleration.
45 Three-dimensional hardware acceleration is valuable in situations requiring
46 rendering of 3D objects such as games, 3D CAD and modeling.
47 </p>
48
49 </body>
50 </section>
51 <section>
52 <title>How do I get hardware 3D acceleration?</title>
53 <body>
54
55 <p>
56 In many cases, both binary and open-source drivers exist. Open-source drivers
57 are preferable since we're using Linux and open source is one of its underlying
58 principles. Sometimes, binary drivers are the only option, like with nVidia's
59 cards. Binary drivers include <c>x11-drivers/nvidia-drivers</c> for nVidia cards
60 and <c>x11-drivers/ati-drivers</c> for ATI cards.
61 </p>
62
63 </body>
64 </section>
65 <section>
66 <title>What is DRI?</title>
67 <body>
68
69 <p>
70 The <uri link="http://dri.freedesktop.org/wiki/">Direct Rendering
71 Infrastructure</uri>, also known as the DRI, is a framework for allowing direct
72 access to graphics hardware in a safe and efficient manner. It includes changes
73 to the X server, to several client libraries and to the kernel. The first major
74 use for the DRI is to create fast OpenGL implementations.
75 </p>
76
77 </body>
78 </section>
79 <section>
80 <title>What is the DRM and how does it relate to regular Xorg?</title>
81 <body>
82
83 <p>
84 The DRM (Direct Rendering Manager) is an <e>enhancement</e> to Xorg that adds 3D
85 acceleration for cards by adding the kernel module necessary for direct
86 rendering.
87 </p>
88
89 </body>
90 </section>
91 <section>
92 <title>Purpose</title>
93 <body>
94
95 <p>
96 This guide is for people who can't get direct rendering working with just Xorg.
97 The DRM works for the following drivers:
98 </p>
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>
112 See the <uri link="http://dri.freedesktop.org/">DRI homepage</uri> for more info
113 and documentation.
114 </p>
115
116 </body>
117 </section>
118 <section>
119 <title>Feedback</title>
120 <body>
121
122 <p>
123 With suggestions, questions, etc., e-mail <mail
124 link="dberkholz@gentoo.org">Donnie Berkholz</mail>.
125 </p>
126
127 </body>
128 </section>
129 </chapter>
130
131 <chapter>
132 <title>Install Xorg and configure your kernel</title>
133 <section>
134 <title>Install Xorg</title>
135 <body>
136
137 <p>
138 Please read our <uri link="/doc/en/xorg-config.xml">Xorg Configuration
139 Guide</uri> to get Xorg up and running.
140 </p>
141
142 </body>
143 </section>
144 <section>
145 <title>Configure your kernel</title>
146 <body>
147
148 <p>
149 Probe for your chipset and enable just that one.
150 </p>
151
152 <pre caption="Checking your AGP chipset">
153 # <i>emerge pciutils; lspci | grep AGP</i>
154 # <i>00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)</i>
155 <comment>(Your output may not match the above due to different hardware.)</comment>
156 </pre>
157
158 <p>
159 If your chipset is not supported by the kernel you might have some succes by
160 passing <c>agp=try_unsupported</c> as a kernel parameter. This will use Intel's
161 generic routines for AGP support. To add this parameter, edit your bootloader
162 configuration file!
163 </p>
164
165 <p>
166 Most, if not all, kernels should have these options. This was configured using a
167 standard <c>gentoo-sources</c> kernel.
168 </p>
169
170 <pre caption="Configuring the kernel">
171 # <i>ls -l /usr/src/linux </i>
172 lrwxrwxrwx 1 root root 22 2007-02-14 20:12 /usr/src/linux -> linux-2.6.18-gentoo-r4
173 <comment>(Make sure /usr/src/linux links to your current kernel.)</comment>
174 # <i>cd /usr/src/linux</i>
175 # <i>make menuconfig</i>
176 </pre>
177
178 <pre caption="make menuconfig options">
179 Processor type and features --->
180 &lt;*&gt; MTRR (Memory Type Range Register) support
181 Device drivers --->
182 Graphics support --->
183 &lt;M&gt; /dev/agpgart (AGP 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
186 <comment>(Enable your chipset instead of the above.)</comment>
187 &lt;M&gt; Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) --->
188 &lt;M&gt; <comment>(Select your graphics card from the list)</comment>
189 </pre>
190
191 </body>
192 </section>
193 <section>
194 <title>Compile and install your kernel</title>
195 <body>
196
197 <pre caption="Compiling and installing kernel">
198 # <i>make &amp;&amp; make modules_install</i>
199 </pre>
200
201 <p>
202 Don't forget to set up <path>grub.conf</path> or <path>lilo.conf</path> and run
203 <c>/sbin/lilo</c> if you use LILO.
204 </p>
205
206 </body>
207 </section>
208 </chapter>
209
210 <chapter>
211 <title>Configure direct rendering</title>
212 <section id="configure_xorg">
213 <title>Configure Xorg.conf</title>
214 <body>
215
216 <p>
217 Open <path>/etc/X11/xorg.conf</path> with your favorite text editor and edit
218 it to enable DRI and GLX.
219 </p>
220
221 <pre caption="xorg.conf">
222 ...
223 Section "Module"
224 Load "dri"
225 Load "glx"
226 ...
227 EndSection
228 ...
229 Section "Device"
230 Driver "radeon"
231 <comment>(Replace radeon with the name of your driver.)</comment>
232 ...
233 EndSection
234 ...
235 Section "dri"
236 Mode 0666
237 EndSection
238 </pre>
239
240 </body>
241 </section>
242 <section>
243 <title>Changes to modules.autoload.d</title>
244 <body>
245
246 <p>
247 You will need to add the module name that your card uses to
248 <path>/etc/modules.autoload.d/kernel-2.6</path> to ensure that the module is
249 loaded automatically when the system starts up.
250 </p>
251
252 <pre caption="Editing /etc/modules.autoload.d/kernel-2.6">
253 <comment>(Change module name as required.)</comment>
254 intel-agp
255 </pre>
256
257 <note>
258 If you compiled <c>agpgart</c> as a module, you will also need to add it to
259 <path>/etc/modules.autoload.d/kernel-2.6</path>.
260 </note>
261
262 </body>
263 </section>
264 </chapter>
265
266 <chapter>
267 <title>Test 3D acceleration</title>
268 <section>
269 <title>Reboot to the new kernel</title>
270 <body>
271
272 <p>
273 Reboot your computer to your new kernel and login as a normal user. It's time to
274 see if you have direct rendering and how good it is. <c>glxinfo</c> and
275 <c>glxgears</c> are part of the <c>mesa-progs</c> package, so make sure it is
276 installed before you attempt to run these commands.
277 </p>
278
279 <pre caption="Testing rendering">
280 $ <i>startx</i>
281 <comment>(No need to load modules for your driver or agpgart, even if you compiled them as a module.)</comment>
282 <comment>(They will be loaded automatically.)</comment>
283 $ <i>glxinfo | grep rendering</i>
284 direct rendering: Yes
285 <comment>(If it says "No", you don't have 3D acceleration.)</comment>
286 $ <i>glxgears</i>
287 <comment>(Test your frames per second (FPS) at the default size. The number should be
288 significantly higher than before configuring DRM. Do this while the CPU is as idle as
289 possible.)</comment>
290 </pre>
291
292 <note>
293 FPS may be limited by your screen's refresh rate, so keep this in mind if
294 <c>glxgears</c> reports only about 70-100 FPS. <c>games-fps/ut2004-demo</c> is a
295 better benchmarking tool, as it can give you real-world performance results.
296 </note>
297
298 </body>
299 </section>
300 </chapter>
301
302 <chapter>
303 <title>Tweak your performance</title>
304 <section>
305 <title>Get the most out of direct rendering</title>
306 <body>
307
308 <p>
309 A few options may increase performance by up to 30 percent (or more) over the
310 default. Set them in <path>/etc/X11/xorg.conf</path>. However, you will first
311 need to check that your motherboard and video card support these options.
312 </p>
313
314 <p>
315 First, let's see if your video card can support fast writes. We'll do this by
316 closely inspecting the output from <c>lspci</c>. Specifically, we are looking
317 at the "VGA compatible controller" information.
318 </p>
319
320 <pre caption="Video card check">
321 # <i>lspci -vv</i>
322 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY (prog-if 00 [VGA])
323 . . .
324 Capabilities: [58] AGP version 2.0
325 Status: RQ=48 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
326 </pre>
327
328 <p>
329 While quite a lot of information is produced, we are looking for <b>FW</b> in
330 the "Status" subsection of the AGP "Capabilities" section. If <b>FW+</b> is
331 present in the "Status" line, it means the card supports fast writes. We can
332 now check if the motherboard supports fast writes.
333 </p>
334
335 <impo>
336 If you do not see <b>FW+</b>, but instead see <b>FW-</b>, you cannot enable
337 fast writes in <path>xorg.conf</path>. Your card does not support fast writes.
338 </impo>
339
340 <p>
341 Now let's make sure the motherboard supports fast writes as well. This time,
342 look at the "Host bridge" section of your <c>lspci</c> output.
343 </p>
344
345 <pre caption="Motherboard check">
346 # <i>lspci -vv</i>
347 00:00.0 Host bridge: Intel Corporation 82830 830 Chipset Host Bridge (rev 02)
348 . . .
349 Capabilities: [a0] AGP version 2.0
350 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
351 </pre>
352
353 <p>
354 Again, examine the "Status" subsection of your AGP "Capabilities" section. Look
355 for <b>FW</b>. If you see <b>FW+</b>, your motherboard supports fast writes.
356 </p>
357
358 <impo>
359 Remember, both your video card information and your motherboard information
360 must show the same <b>FW</b> capability. If either device shows <b>FW-</b> in
361 "Status", you cannot enable fast writes in <path>xorg.conf</path>.
362 </impo>
363
364 <p>
365 Assuming that all has gone well and both your motherboard and video card
366 support fast writes, let's enable this option in
367 <path>/etc/X11/xorg.conf</path> and get the best performance out of your
368 hardware.
369 </p>
370
371 <pre caption="xorg.conf">
372 Section "Device"
373 Option "AGPMode" "4"
374 <comment>(This increased FPS from 609 to 618.)</comment>
375 Option "AGPFastWrite" "True"
376 <comment>(This had no measurable effect, but it may increase instability of your computer.)</comment>
377 <comment>(You may also need to set it in your BIOS.)</comment>
378 Option "EnablePageFlip" "True"
379 <comment>(This improved FPS from 618 to 702. It also is "risky" but few people have reported problems.)</comment>
380 ...
381 EndSection
382 </pre>
383
384 <warn>
385 Enabling <c>AGPFastWrite</c> on a VIA chipset will very likely cause your
386 machine to lock up. VIA chipsets do not play nicely with fast writes, so use
387 this setting at your own risk.
388 </warn>
389
390 <note>
391 Remember, if you want fast writes to work properly, you will have to first
392 enable the appropriate option in your BIOS.
393 </note>
394
395 <p>
396 If you want to set even more features, check out the <uri
397 link="http://dri.freedesktop.org/wiki/FeatureMatrix">feature matrix</uri> on
398 the DRI web site or the <uri
399 link="http://dri.sourceforge.net/doc/dri_driver_features.phtml">features
400 listing</uri> on Sourceforge.
401 </p>
402
403 </body>
404 </section>
405 </chapter>
406
407 <chapter>
408 <title>Troubleshooting</title>
409 <section>
410 <title>It doesn't work. I don't have rendering, and I can't tell why.</title>
411 <body>
412
413 <p>
414 Try <c>modprobe radeon</c> before you start the X server (replace <c>radeon</c>
415 with the name of your driver). Also, try building agpgart into the kernel
416 instead of as a module.
417 </p>
418
419 </body>
420 </section>
421 <section>
422 <title>When I startx, I get this error: "[drm] failed to load kernel module agpgart"</title>
423 <body>
424
425 <p>
426 That's because you compiled agpgart into the kernel instead of as a module.
427 Ignore it unless you're having problems.
428 </p>
429
430 </body>
431 </section>
432 <section>
433 <title>I have a Radeon, and I want TV-Out.</title>
434 <body>
435
436 <p>
437 The drivers originally developed by the <uri
438 link="http://gatos.sf.net">GATOS</uri> project have been merged into Xorg's
439 codebase. You don't need anything special for TV-Out;
440 <c>x11-drivers/xf86-video-ati</c> will work just fine.
441 </p>
442
443 </body>
444 </section>
445 <section>
446 <title>
447 It doesn't work. My card is so incredibly new and cool that it isn't supported
448 at all.
449 </title>
450 <body>
451
452 <p>
453 Try out the binary drivers. For <c>ati-drivers</c>, a listing is at
454 <uri>http://ati.amd.com/support/drivers/linux/linux-radeon.html</uri> (for x86)
455 and at <uri>http://ati.amd.com/support/drivers/linux64/linux64-radeon.html</uri>
456 (for amd64). If those don't support it, use fbdev. It's slow, but it works.
457 </p>
458
459 </body>
460 </section>
461 <section>
462 <title>I have a PCI card and it doesn't work. Help!</title>
463 <body>
464
465 <p>
466 Edit <path>/etc/X11/xorg.conf</path>. In section "Device" enable ForcePCIMode.
467 </p>
468
469 <pre caption="Enabling ForcePCIMode">
470 Option "ForcePCIMode" "True"
471 </pre>
472
473 </body>
474 </section>
475 </chapter>
476
477 <chapter>
478 <title>Acknowledgments</title>
479 <section>
480 <body>
481
482 <ol>
483 <li>
484 Christopher Webber for suggesting a troubleshooting question about changing
485 or recompiling kernels
486 </li>
487 <li>
488 Steve, for suggesting consistency between the cases of dri and DRI in
489 XF86Config
490 </li>
491 </ol>
492
493 </body>
494 </section>
495 </chapter>
496
497 <chapter>
498 <title>References</title>
499 <section>
500 <body>
501
502 <ol>
503 <li><uri>http://forums.gentoo.org/viewtopic.php?t=46681</uri></li>
504 <li><uri>http://forums.gentoo.org/viewtopic.php?t=29264</uri></li>
505 <li><uri>http://dri.freedesktop.org/</uri></li>
506 <li><uri>http://www.retinalburn.net/linux/dri_status.html</uri></li>
507 </ol>
508
509 </body>
510 </section>
511 </chapter>
512 </guide>

  ViewVC Help
Powered by ViewVC 1.1.20