/[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.28 Revision 1.45
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.28 2006/02/01 11:58:34 neysx Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/dri-howto.xml,v 1.45 2009/12/14 21:26:40 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>
6<title>Hardware 3D Acceleration Guide</title> 6<title>Hardware 3D Acceleration Guide</title>
7
7<author title="Author"> 8<author title="Author">
8<mail link="spyderous@gentoo.org">Donnie Berkholz</mail> 9 <mail link="dberkholz"/>
9</author> 10</author>
10<author title="Editor"> 11<author title="Editor">
11<mail link="peesh@gentoo.org">Jorge Paulo</mail> 12 <mail link="peesh"/>
12</author> 13</author>
14<author title="Editor">
15 <mail link="nightmorph"/>
16</author>
13 17
14<abstract> 18<abstract>
15This document is a guide to getting 3D acceleration working using X11-DRM 19This document is a guide to getting 3D acceleration working using the DRM with
16with Xorg in Gentoo Linux. 20Xorg in Gentoo Linux.
17</abstract> 21</abstract>
18 22
19<!-- The content of this document is licensed under the CC-BY-SA license --> 23<!-- The content of this document is licensed under the CC-BY-SA license -->
20<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 24<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
21<license/> 25<license/>
22 26
23<version>1.2</version> 27<version>1.13</version>
24<date>2006-02-01</date> 28<date>2009-12-14</date>
25 29
26<chapter> 30<chapter>
27<title>Introduction</title> 31<title>Introduction</title>
28<section> 32<section>
29<title>What is hardware 3D acceleration and why do I want it?</title> 33<title>What is hardware 3D acceleration and why do I want it?</title>
30<body> 34<body>
31 35
32<p> 36<p>
33With hardware 3D acceleration, three-dimensional rendering uses the graphics 37With hardware 3D acceleration, three-dimensional rendering uses the graphics
34processor on your video card instead of taking up valuable CPU resources 38processor on your video card instead of taking up valuable CPU resources
35drawing 3D images. It's also referred to as "hardware acceleration" instead of 39drawing 3D images. It's also referred to as "hardware acceleration" instead of
36"software acceleration" because without this 3D acceleration your CPU is forced 40"software acceleration" because without this 3D acceleration your CPU is forced
37to draw everything itself using the Mesa software rendering libraries, which 41to draw everything itself using the Mesa software rendering libraries, which
38takes up quite a bit of processing power. While Xorg typically supports 2D 42takes up quite a bit of processing power. While Xorg typically supports 2D
39hardware acceleration, it often lacks hardware 3D acceleration. 43hardware acceleration, it often lacks hardware 3D acceleration.
40Three-dimensional hardware acceleration is valuable in situations requiring 44Three-dimensional hardware acceleration is valuable in situations requiring
41rendering of 3D objects such as games, 3D CAD and modeling. 45rendering of 3D objects such as games, 3D CAD and modeling.
42</p> 46</p>
43 47
44</body> 48</body>
45</section> 49</section>
46<section> 50<section>
47<title>How do I get hardware 3D acceleration?</title> 51<title>How do I get hardware 3D acceleration?</title>
48<body> 52<body>
49 53
50<p> 54<p>
51In many cases, both binary and open-source drivers exist. Open-source drivers 55In many cases, both binary and open-source drivers exist. Open-source drivers
52are preferable since we're using Linux and open source is one of its underlying 56are preferable since we're using Linux and open source is one of its underlying
53principles. Sometimes, binary drivers are the only option, like with nVidia's 57principles. Sometimes, binary drivers are the only option, like with nVidia's
54cards. Binary drivers include media-video/nvidia-kernel and 58cards. Binary drivers include <c>x11-drivers/nvidia-drivers</c> for nVidia cards
55media-video/nvidia-glx for nVidia cards, media-video/mgavideo for Matrox cards 59and <c>x11-drivers/ati-drivers</c> for ATI cards.
56and media-video/ati-drivers for ATI cards. Other open-source drivers include
57media-video/kyro-kernel for KyroII cards and media-video/ati-gatos for ATI
58cards, which aim to support ATI's video capabilities more fully.
59</p> 60</p>
60 61
61</body> 62</body>
62</section> 63</section>
63<section> 64<section>
73</p> 74</p>
74 75
75</body> 76</body>
76</section> 77</section>
77<section> 78<section>
78<title>What is X11-DRM and how does it relate to regular Xorg?</title> 79<title>What is the DRM and how does it relate to regular Xorg?</title>
79<body> 80<body>
80 81
81<p> 82<p>
82X11-DRM is an <e>enhancement</e> to Xorg that adds 3D acceleration for 83The DRM (Direct Rendering Manager) is an <e>enhancement</e> to Xorg that adds 3D
83cards by adding the kernel module necessary for direct rendering. 84acceleration for cards by adding the kernel module necessary for direct
85rendering.
84</p> 86</p>
85 87
86</body> 88</body>
87</section> 89</section>
88<section> 90<section>
89<title>Purpose</title> 91<title>Purpose</title>
90<body> 92<body>
91 93
92<p> 94<p>
93This guide is for people who can't get direct rendering working with just Xorg. 95This guide is for people who can't get direct rendering working with just Xorg.
94X11-DRM works for 3dfx, gamma, i8x0, matrox, rage128, radeon, mach64 and sis300 96The DRM works for the following drivers:
95series drivers. See the <uri link="http://dri.freedesktop.org/">DRI 97</p>
96homepage</uri> for more info and documentation. 98
99<ul>
100 <li>3dfx</li>
101 <li>intel</li>
102 <li>matrox</li>
103 <li>rage128</li>
104 <li>radeon</li>
105 <li>mach64</li>
106 <li>sis300</li>
107 <li>via</li>
108</ul>
109
110<p>
111See the <uri link="http://dri.freedesktop.org/">DRI homepage</uri> for more info
112and documentation.
97</p> 113</p>
98 114
99</body> 115</body>
100</section> 116</section>
101<section> 117<section>
102<title>Feedback</title> 118<title>Feedback</title>
103<body> 119<body>
104 120
105<p> 121<p>
106With suggestions, questions, etc., e-mail <mail 122With suggestions, questions, etc., e-mail <mail
107link="spyderous@gentoo.org">Donnie Berkholz</mail>. 123link="dberkholz@gentoo.org">Donnie Berkholz</mail>.
108</p> 124</p>
109 125
110</body> 126</body>
111</section> 127</section>
112</chapter> 128</chapter>
144generic routines for AGP support. To add this parameter, edit your bootloader 160generic routines for AGP support. To add this parameter, edit your bootloader
145configuration file! 161configuration file!
146</p> 162</p>
147 163
148<p> 164<p>
149Most, if not all, kernels should have these options. This was configured using 165Most, if not all, kernels should have these options. This was configured using a
150gentoo-sources-2.4.20-r5. 166standard <c>gentoo-sources</c> kernel.
151</p> 167</p>
152 168
153<pre caption="Configuring the kernel"> 169<pre caption="Configuring the kernel">
154# <i>ls -l /usr/src/linux </i> 170# <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 171lrwxrwxrwx 1 root root 22 2007-02-14 20:12 /usr/src/linux -> linux-2.6.18-gentoo-r4
156<comment>(Make sure /usr/src/linux links to your current kernel.)</comment> 172<comment>(Make sure /usr/src/linux links to your current kernel.)</comment>
157# <i>cd /usr/src/linux</i> 173# <i>cd /usr/src/linux</i>
158# <i>make menuconfig</i> 174# <i>make menuconfig</i>
159</pre> 175</pre>
160 176
161<pre caption="make menuconfig options"> 177<pre caption="make menuconfig options">
162Processor type and features ---&gt; 178Processor type and features --->
163&lt;*&gt; MTRR (Memory Type Range Register) support 179&lt;*&gt; MTRR (Memory Type Range Register) support
164Character devices ---&gt; 180Device drivers --->
181 Graphics support --->
165&lt;M&gt; /dev/agpgart (AGP Support) 182 &lt;M&gt; /dev/agpgart (AGP Support) --->
166[M] Intel 440LX/BX/GX and I815/I820/I830M/I830MP/I840/I845/I850/I860 support 183 <comment>(The agpgart option is not present on 64-bit kernels; just choose your chipset support.)</comment>
184 &lt;M&gt; Intel 440LX/BX/GX, I8xx and E7x05 support
167<comment>(Enable your chipset instead of the above.)</comment> 185 <comment>(Enable your chipset instead of the above.)</comment>
168&lt; &gt; Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) 186 &lt;M&gt; Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) --->
169</pre> 187 &lt;M&gt; <comment>(Select your graphics card from the list)</comment>
170
171<p>
172Make sure the Direct Rendering Manager (DRM) is <e>off</e>.
173The X11-DRM package 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<comment>(This example is for a 2.4 kernel)</comment>
184# <i>make dep &amp;&amp; make clean bzImage modules modules_install</i> 197# <i>make &amp;&amp; make modules_install</i>
185# <i>mount /boot</i>
186# <i>cp arch/i386/boot/bzImage /boot</i>
187</pre> 198</pre>
188 199
189<p>
190If you want your kernel to be named something other than bzImage, be sure to
191copy to /boot/yourname instead. Don't forget to set up grub.conf or lilo.conf
192and run /sbin/lilo if you use LILO.
193</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>
194 204
195</body> 205</body>
196</section>
197</chapter>
198
199<chapter>
200<title>Install X11-DRM and configure direct rendering</title>
201<section> 206</section>
202<title>Install X11-DRM</title> 207</chapter>
203<body>
204 208
205<pre caption="Installing X11-DRM"> 209<chapter>
206# <i>emerge x11-drm</i> 210<title>Configure direct rendering</title>
207</pre>
208
209</body>
210</section>
211<section id="configure_xorg"> 211<section id="configure_xorg">
212<title>Configure Xorg.conf</title> 212<title>Configure Xorg.conf</title>
213<body> 213<body>
214 214
215<p> 215<p>
216Some chipsets require you to rebuild <c>xorg-x11</c> with
217<c>USE="insecure-drivers"</c>. This applies to mach64, unichrome and savage
218chipsets on xorg-x11-6.8.2, and to mach64 and unichrome on xorg-x11-6.8.99.x.
219Savage users should not try xorg-x11-6.8.99.x as support for the savage there
220is broken.
221</p>
222
223<pre caption="Rebuilding xorg-x11">
224<comment>(Add the insecure-drivers USE flag if you use one of the aforementioned chipsets)</comment>
225# <i>echo "x11-base/xorg-x11 insecure-drivers" &gt;&gt; /etc/portage/package.use</i>
226
227# <i>emerge xorg-x11</i>
228</pre>
229
230<p>
231Open <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
232it to enable DRI and GLX. 217it to enable DRI and GLX.
233</p> 218</p>
234 219
235<pre caption="xorg.conf"> 220<pre caption="xorg.conf">
236... 221...
240 ... 225 ...
241EndSection 226EndSection
242... 227...
243Section "Device" 228Section "Device"
244 Driver "radeon" 229 Driver "radeon"
230 <comment>(Replace radeon with the name of your driver.)</comment>
245 ... 231 ...
246EndSection 232EndSection
247... 233...
248Section "dri" 234Section "dri"
249 Mode 0666 235 Mode 0666
250EndSection 236EndSection
251</pre> 237</pre>
252 238
253<p>
254If you are using a different driver, replace "radeon" with yours.
255</p>
256
257</body> 239</body>
258</section> 240</section>
259<section> 241<section>
260<title>Changes to modules.autoload.d</title> 242<title>Changes to modules.autoload.d</title>
261<body> 243<body>
269<pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> 251<pre caption="Editing /etc/modules.autoload.d/kernel-2.6">
270<comment>(Change module name as required.)</comment> 252<comment>(Change module name as required.)</comment>
271intel-agp 253intel-agp
272</pre> 254</pre>
273 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>
260
274</body> 261</body>
275</section> 262</section>
276</chapter> 263</chapter>
277 264
278<chapter> 265<chapter>
280<section> 267<section>
281<title>Reboot to the new kernel</title> 268<title>Reboot to the new kernel</title>
282<body> 269<body>
283 270
284<p> 271<p>
285Reboot 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
286rendering 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.
287</p> 276</p>
288 277
289<pre caption="Testing rendering"> 278<pre caption="Testing rendering">
290# <i>startx</i> 279$ <i>startx</i>
291<comment>(No need to load modules for your driver or agpgart, if you compiled agpgart as a module.)</comment> 280<comment>(No need to load modules for your driver or agpgart, even if you compiled them as a module.)</comment>
292<comment>(They will be loaded automatically.)</comment> 281<comment>(They will be loaded automatically.)</comment>
293# <i>glxinfo | grep rendering</i> 282$ <i>glxinfo | grep rendering</i>
294direct rendering: Yes 283direct rendering: Yes
295<comment>(If it says "No," you don't have 3D acceleration.)</comment> 284<comment>(If it says "No", you don't have 3D acceleration.)</comment>
296# <i>glxgears</i> 285$ <i>glxgears</i>
297<comment>(Test your frames per second (FPS) at the default size. The number should be )</comment> 286<comment>(Test your frames per second (FPS) at the default size. The number should be
298<comment>(significantly higher than before installing x11-drm. Do this while the CPU is as idle as possible.)</comment> 287significantly higher than before configuring DRM. Do this while the CPU is as idle as
288possible.)</comment>
299</pre> 289</pre>
300 290
301</body> 291<note>
302</section> 292FPS may be limited by your screen's refresh rate, so keep this in mind if
303</chapter> 293<c>glxgears</c> reports only about 70-100 FPS. <c>games-fps/ut2004-demo</c> or
294other 3D games are better benchmarking tools, as they give you real-world
295performance results.
296</note>
304 297
305<chapter> 298</body>
306<title>Using the CVS sources</title>
307<section> 299</section>
308<body>
309
310<warn>
311Don't do this if the package worked.
312</warn>
313
314</body>
315</section>
316<section>
317<title>Do you need the CVS?</title>
318<body>
319
320<p>
321First you have to check whether the x11-drm package works. If it doesn't and
322you have checked your logs to verify it's not a configuration error, you might
323want to consider the CVS sources. There are also daily driver snapshots
324available if you do not wish to build the full CVS.
325</p>
326
327</body>
328</section>
329<section>
330<title>Do the CVS sources support your card?</title>
331<body>
332
333<p>
334Check the DRI <uri link="http://dri.freedesktop.org/wiki/Status">supported
335cards list</uri> to see if the CVS supports your card. Even if it doesn't, but
336it supports a similar card, try it.
337</p>
338
339<!-- I see a couple of 8x AGP stuff on the Internet about vanilla 2.4 kernels;
340 is this now available or not? I've commented it out for the time being,
341 hoping that this doesn't affect us :)
342
343<warn>
344"Linux 2.4 doesn't support agp 8x, so I had to go find a backport. The backport
345works .... it doesn't patch quite properly, and it requires 2.4.21 (I've only
346gotten it to work with vanilla, straight from the tarball (not ebuild)). First
347go get the 2.4.20-2.4.21 patch from kernel.org .... (then get the patch,) It
348was on a mailing list somewhere. It doesn't patch cleanly - - one file fails,
349the pci_ids.h file, but if you actually read the file and the reject list, it's
350very easy to fix. But it does load, and it gives me 1600x1200 with video
351(although a bit slow b/c of lack of dga) with xfree-drm." (SanityInAnarchy on
352#gentoo)
353</warn>
354
355<impo>
356The patch is a little tricky to work with but <uri
357link="http://www.ussg.iu.edu/hypermail/linux/kernel/0302.2/att-1618/01-agp3.diff.bz2">here's
358the link</uri>. If you can disable 8X AGP in your BIOS, change it to 4X and you
359may not need the patch.
360</impo>
361-->
362
363</body>
364</section>
365<section>
366<title>Follow the CVS Instructions</title>
367<body>
368
369<p>
370The DRI project has a document about CVS compiling themselves. Please read <uri
371link="http://dri.freedesktop.org/wiki/Building">the document</uri> and follow
372the instructions up to the <e>Installing for X.org</e> part.
373</p>
374
375</body>
376</section>
377<section>
378<title>Install the CVS</title>
379<body>
380
381<p>
382Verify that the DRI kernel module(s) for your system were built:
383</p>
384
385<pre caption="Verification">
386# <i>cd ~/DRI-CVS/build/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel; ls</i>
387</pre>
388
389<p>
390For the 3dfx Voodoo, you should see <path>tdfx.o</path>. For the Matrox
391G200/G400, you should see <path>mga.o</path>. For the ATI Rage 128, you should
392see <path>r128.o</path>. For the ATI Radeon, you should see
393<path>radeon.o</path>. For the Intel i810, you should see <path>i810.o</path>.
394If the DRI kernel module(s) failed to build, you should verify that you're
395using the right version of the Linux kernel. The most recent kernels are not
396always supported.
397</p>
398
399<p>
400Install over your X.org installation. You may wish to back up xorg-x11.
401</p>
402
403<pre caption="Backing up Xorg">
404# <i>quickpkg xorg-x11</i>
405<comment>(This backs up your Xorg-X11 package.)</comment>
406# <i>make install</i>
407</pre>
408
409<p>
410Follow the "Configure Xorg" section above.
411</p>
412
413<p>
414To load the appropriate DRM module in your running kernel, copy the kernel
415module to <path>/lib/modules/`uname -r`/kernel/drivers/char/drm/</path> then
416run <c>modules-update</c> and restart your X server. If you're not running the
417kernel you'll be using it in, instead of <c>`uname -r`,</c> use that kernel's
418name.
419</p>
420
421<warn>
422Make sure you first unload any older DRI kernel modules that might be already
423loaded. Note that some DRM modules require that the agpgart module be loaded
424first.
425</warn>
426
427</body>
428</section>
429</chapter>
430
431<chapter>
432<title>Tweak your performance</title>
433<section> 300<section>
434<title>Get the most out of direct rendering</title> 301<title>Get the most out of direct rendering</title>
435<body> 302<body>
436 303
437<p> 304<p>
438A few options may increase performance by up to 30 percent (or more) over the 305If you want to set more features, for performance or other reasons, check out
439default. Set them in <path>/etc/X11/xorg.conf</path>.
440</p>
441
442<pre caption="xorg.conf">
443Section "Device"
444 Option "AGPMode" "4"
445 <comment>(This increased FPS from 609 to 618.)</comment>
446 Option "AGPFastWrite" "True"
447 <comment>(This had no measurable effect, but it may increase instability of your computer.)</comment>
448 <comment>(You may also need to set it in your BIOS.)</comment>
449 Option "EnablePageFlip" "True"
450 <comment>(This improved FPS from 618 to 702. It also is "risky" but few people have reported problems.)</comment>
451 ...
452EndSection
453</pre>
454
455<p>
456If you want to set even more features, check out the <uri
457link="http://dri.freedesktop.org/wiki/FeatureMatrix">feature matrix</uri> on 306the <uri link="http://dri.freedesktop.org/wiki/FeatureMatrix">feature
458the DRI web site or the <uri 307matrix</uri> on the DRI web site or the <uri
459link="http://dri.sourceforge.net/doc/dri_driver_features.phtml">features 308link="http://dri.sourceforge.net/doc/dri_driver_features.phtml">features
460listing</uri> on Sourceforge. 309listing</uri> on Sourceforge.
461</p> 310</p>
462 311
463</body> 312</body>
465</chapter> 314</chapter>
466 315
467<chapter> 316<chapter>
468<title>Troubleshooting</title> 317<title>Troubleshooting</title>
469<section> 318<section>
470<title>It doesn't work. I just recompiled my kernel or switched to a new one.</title>
471<body>
472
473<p>
474Whenever you rebuild your kernel or switch to another kernel, you'll have to
475rebuild the kernel module. Note that you don't need to remerge xorg-x11, but
476you will need to remerge x11-drm.
477</p>
478
479</body>
480</section>
481
482<section>
483<title>It doesn't work. I don't have rendering, and I can't tell why.</title> 319<title>It doesn't work. I don't have rendering, and I can't tell why.</title>
484<body> 320<body>
485 321
486<p> 322<p>
487Try <c>insmod radeon</c> before you start the X server. Also, try building 323Try <c>modprobe radeon</c> before you start the X server (replace <c>radeon</c>
488agpgart into the kernel instead of as a module. 324with the name of your driver). Also, try building agpgart into the kernel
325instead of as a module.
489</p> 326</p>
490 327
491</body> 328</body>
492</section> 329</section>
493<section> 330<section>
494<title>When I startx, I get this error: "[drm] failed to load kernel module agpgart"</title> 331<title>When I startx, I get this error: "[drm] failed to load kernel module agpgart"</title>
495<body> 332<body>
496 333
497<p> 334<p>
498That's because you compiled agpgart into the kernel instead of as a module. 335That's because you compiled agpgart into the kernel instead of as a module.
499Ignore it unless you're having problems. 336Ignore it unless you're having problems.
500</p> 337</p>
501 338
502</body> 339</body>
503</section> 340</section>
504<section> 341<section>
505<title>Direct rendering doesn't work, and in /var/log/Xorg.0.log I have an error about driver version too low.</title>
506<body>
507
508<p>
509You aren't using the x11-drm driver. Check if you compiled DRM and the driver
510into the kernel; you shouldn't have.
511</p>
512
513</body>
514</section>
515<section>
516<title>I have a Radeon, and I want TV-Out.</title> 342<title>I have a Radeon, and I want TV-Out.</title>
517<body> 343<body>
518 344
519<p> 345<p>
520Check out ati-gatos drivers. <c>emerge -s gatos</c>. 346The drivers originally developed by the <uri
347link="http://gatos.sf.net">GATOS</uri> project have been merged into Xorg's
348codebase. You don't need anything special for TV-Out;
349<c>x11-drivers/xf86-video-ati</c> will work just fine.
521</p> 350</p>
522 351
523</body> 352</body>
524</section>
525<section> 353</section>
354<section>
355<title>
526<title>It doesn't work. My card is so incredibly new and cool that it isn't supported at all.</title> 356It doesn't work. My card is so incredibly new and cool that it isn't supported
357at all.
358</title>
527<body> 359<body>
528 360
529<p> 361<p>
530Try out the binary drivers. For ati-drivers, a listing is at 362Try out the binary drivers. For <c>ati-drivers</c>, a listing is at
531<uri>http://www.schneider-digital.de/html/download_ati.php</uri>. If those 363<uri>http://support.amd.com/us/gpudownload/Pages/index.aspx</uri>. If those
532don't support it, use fbdev. It's slow, but it works. 364don't support it, use fbdev. It's slow, but it works.
533</p> 365</p>
534 366
535</body> 367</body>
536</section> 368</section>
537<section> 369<section>
538<title>I have a PCI card and it doesn't work. Help!</title> 370<title>I have a PCI card and it doesn't work. Help!</title>
539<body> 371<body>
540 372
541<p> 373<p>
542In section "Device" enable ForcePCIMode. 374Edit <path>/etc/X11/xorg.conf</path>. In section "Device" enable ForcePCIMode.
543</p> 375</p>
544 376
545<pre caption="Enabling ForcePCIMode"> 377<pre caption="Enabling ForcePCIMode">
546Option "ForcePCIMode" "True" 378Option "ForcePCIMode" "True"
547</pre> 379</pre>
548
549</body>
550</section>
551</chapter>
552
553<chapter>
554<title>Acknowledgments</title>
555<section>
556<body>
557
558<ol>
559 <li>
560 Christopher Webber for suggesting a troubleshooting question about changing
561 or recompiling kernels
562 </li>
563 <li>
564 Steve, for suggesting consistency between the cases of dri and DRI in
565 XF86Config
566 </li>
567</ol>
568 380
569</body> 381</body>
570</section> 382</section>
571</chapter> 383</chapter>
572 384

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

  ViewVC Help
Powered by ViewVC 1.1.20