/[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.26 Revision 1.41
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.26 2005/10/11 03:46:14 swift Exp $ --> 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"> 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.14</version> 28<version>1.10</version>
22<date>2005-10-11</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>
28<body> 35<body>
29 36
30<p> 37<p>
31With hardware 3D acceleration, three-dimensional rendering uses the graphics 38With hardware 3D acceleration, three-dimensional rendering uses the graphics
32processor on your video card instead of taking up valuable CPU resources 39processor on your video card instead of taking up valuable CPU resources
33drawing 3D images. It's also referred to as "hardware acceleration" instead of 40drawing 3D images. It's also referred to as "hardware acceleration" instead of
34"software acceleration" because without this 3D acceleration your CPU is forced 41"software acceleration" because without this 3D acceleration your CPU is forced
35to draw everything itself using the Mesa software rendering libraries, which 42to draw everything itself using the Mesa software rendering libraries, which
36takes up quite a bit of processing power. While Xorg typically supports 2D 43takes up quite a bit of processing power. While Xorg typically supports 2D
37hardware acceleration, it often lacks hardware 3D acceleration. 44hardware acceleration, it often lacks hardware 3D acceleration.
38Three-dimensional hardware acceleration is valuable in situations requiring 45Three-dimensional hardware acceleration is valuable in situations requiring
39rendering of 3D objects such as games, 3D CAD and modeling. 46rendering of 3D objects such as games, 3D CAD and modeling.
40</p> 47</p>
41 48
42</body> 49</body>
43</section> 50</section>
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>
71</p> 75</p>
72 76
73</body> 77</body>
74</section> 78</section>
75<section> 79<section>
76<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>
77<body> 81<body>
78 82
79<p> 83<p>
80X11-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
81cards by adding the kernel module necessary for direct rendering. 85acceleration for cards by adding the kernel module necessary for direct
86rendering.
82</p> 87</p>
83 88
84</body> 89</body>
85</section> 90</section>
86<section> 91<section>
87<title>Purpose</title> 92<title>Purpose</title>
88<body> 93<body>
89 94
90<p> 95<p>
91This guide is for people who can't get direct rendering working with just Xorg. 96This guide is for people who can't get direct rendering working with just Xorg.
92X11-DRM works for 3dfx, gamma, i8x0, matrox, rage128, radeon, mach64 and sis300 97The DRM works for the following drivers:
93series drivers. See the <uri link="http://dri.freedesktop.org/">DRI 98</p>
94homepage</uri> for more info and documentation. 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
113and documentation.
95</p> 114</p>
96 115
97</body> 116</body>
98</section> 117</section>
99<section> 118<section>
100<title>Feedback</title> 119<title>Feedback</title>
101<body> 120<body>
102 121
103<p> 122<p>
104With suggestions, questions, etc., e-mail <mail 123With suggestions, questions, etc., e-mail <mail
105link="spyderous@gentoo.org">Donnie Berkholz</mail>. 124link="dberkholz@gentoo.org">Donnie Berkholz</mail>.
106</p> 125</p>
107 126
108</body> 127</body>
109</section> 128</section>
110</chapter> 129</chapter>
142generic routines for AGP support. To add this parameter, edit your bootloader 161generic routines for AGP support. To add this parameter, edit your bootloader
143configuration file! 162configuration file!
144</p> 163</p>
145 164
146<p> 165<p>
147Most, 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
148gentoo-sources-2.4.20-r5. 167standard <c>gentoo-sources</c> kernel.
149</p> 168</p>
150 169
151<pre caption="Configuring the kernel"> 170<pre caption="Configuring the kernel">
152# <i>ls -l /usr/src/linux </i> 171# <i>ls -l /usr/src/linux </i>
153lrwxrwxrwx 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
154<comment>(Make sure /usr/src/linux links to your current kernel.)</comment> 173<comment>(Make sure /usr/src/linux links to your current kernel.)</comment>
155# <i>cd /usr/src/linux</i> 174# <i>cd /usr/src/linux</i>
156# <i>make menuconfig</i> 175# <i>make menuconfig</i>
157</pre> 176</pre>
158 177
159<pre caption="make menuconfig options"> 178<pre caption="make menuconfig options">
160Processor type and features ---&gt; 179Processor type and features --->
161&lt;*&gt; MTRR (Memory Type Range Register) support 180&lt;*&gt; MTRR (Memory Type Range Register) support
181Device drivers --->
162Character devices ---&gt; 182 Character devices --->
163&lt;M&gt; /dev/agpgart (AGP Support) 183 &lt;M&gt; /dev/agpgart (AGP Support)
164[*] 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
165<comment>(Enable your chipset instead of the above.)</comment> 186<comment>(Enable your chipset instead of the above.)</comment>
166&lt; &gt; Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) 187 &lt;M&gt; Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
167</pre>
168
169<p>
170Make sure the Direct Rendering Manager (DRM) is <e>off</e>.
171The X11-DRM package will provide its own.
172</p> 188</pre>
173 189
174</body> 190</body>
175</section> 191</section>
176<section> 192<section>
177<title>Compile and install your kernel</title> 193<title>Compile and install your kernel</title>
178<body> 194<body>
179 195
180<pre caption="Compiling and installing kernel"> 196<pre caption="Compiling and installing kernel">
181<comment>(This example is for a 2.4 kernel)</comment>
182# <i>make dep &amp;&amp; make clean bzImage modules modules_install</i> 197# <i>make &amp;&amp; make modules_install</i>
183# <i>mount /boot</i>
184# <i>cp arch/i386/boot/bzImage /boot</i>
185</pre> 198</pre>
186 199
187<p>
188If you want your kernel to be named something other than bzImage, be sure to
189copy to /boot/yourname instead. Don't forget to set up grub.conf or lilo.conf
190and run /sbin/lilo if you use LILO.
191</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>
192 204
193</body> 205</body>
194</section>
195</chapter>
196
197<chapter>
198<title>Install X11-DRM and configure direct rendering</title>
199<section> 206</section>
200<title>Install X11-DRM</title> 207</chapter>
201<body>
202 208
203<pre caption="Installing X11-DRM"> 209<chapter>
204# <i>emerge x11-drm</i> 210<title>Configure direct rendering</title>
205</pre>
206
207</body>
208</section>
209<section id="configure_xorg"> 211<section id="configure_xorg">
210<title>Configure Xorg.conf</title> 212<title>Configure Xorg.conf</title>
211<body> 213<body>
212 214
213<p> 215<p>
214Some chipsets require you to rebuild <c>xorg-x11</c> with
215<c>USE="insecure-drivers"</c>. This applies to mach64, unichrome and savage
216chipsets on xorg-x11-6.8.2, and to mach64 and unichrome on xorg-x11-6.8.99.x.
217Savage users should not try xorg-x11-6.8.99.x as support for the savage there
218is broken.
219</p>
220
221<pre caption="Rebuilding xorg-x11">
222# <i>vim /etc/portage/package.use</i>
223<comment>(Add the following line if you use one of the abovementioned chipsets)</comment>
224x11-base/xorg-x11 insecure-drivers
225
226# <i>emerge xorg-x11</i>
227</pre>
228
229<p>
230Open <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
231it to enable DRI and GLX. 217it to enable DRI and GLX.
232</p> 218</p>
233 219
234<pre caption="xorg.conf"> 220<pre caption="xorg.conf">
235... 221...
239 ... 225 ...
240EndSection 226EndSection
241... 227...
242Section "Device" 228Section "Device"
243 Driver "radeon" 229 Driver "radeon"
230 <comment>(Replace radeon with the name of your driver.)</comment>
244 ... 231 ...
245EndSection 232EndSection
246... 233...
247Section "dri" 234Section "dri"
248 Mode 0666 235 Mode 0666
249EndSection 236EndSection
250</pre> 237</pre>
251 238
252<p> 239</body>
253If 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
254</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>
255 260
256</body> 261</body>
257</section> 262</section>
258</chapter> 263</chapter>
259 264
262<section> 267<section>
263<title>Reboot to the new kernel</title> 268<title>Reboot to the new kernel</title>
264<body> 269<body>
265 270
266<p> 271<p>
267Reboot 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
268rendering 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.
269</p> 276</p>
270 277
271<pre caption="Testing rendering"> 278<pre caption="Testing rendering">
272# <i>startx</i> 279$ <i>startx</i>
273<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>
274<comment>(They will be loaded automatically.)</comment> 281<comment>(They will be loaded automatically.)</comment>
275# <i>glxinfo | grep rendering</i> 282$ <i>glxinfo | grep rendering</i>
276direct rendering: Yes 283direct rendering: Yes
277<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>
278# <i>glxgears</i> 285$ <i>glxgears</i>
279<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
280<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>
281</pre> 289</pre>
282 290
283</body> 291<note>
284</section> 292FPS may be limited by your screen's refresh rate, so keep this in mind if
285</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>
286 296
287<chapter> 297</body>
288<title>Using the CVS sources</title>
289<section> 298</section>
290<body> 299</chapter>
291 300
292<warn> 301<chapter>
293Don't do this if the package worked. 302<title>Tweak your performance</title>
294</warn>
295
296</body>
297</section> 303<section>
298<section> 304<title>Get the most out of direct rendering</title>
299<title>Do you need the CVS?</title>
300<body>
301
302<p>
303First you have to check whether the x11-drm package works. If it doesn't and
304you have checked your logs to verify it's not a configuration error, you might
305want to consider the CVS sources. There are also daily driver snapshots
306available if you do not wish to build the full CVS.
307</p>
308
309</body> 305<body>
310</section>
311<section>
312<title>Do the CVS sources support your card?</title>
313<body>
314 306
315<p>
316Check the DRI <uri link="http://dri.freedesktop.org/wiki/Status">supported
317cards list</uri> to see if the CVS supports your card. Even if it doesn't, but
318it supports a similar card, try it.
319</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>
320 312
321<!-- I see a couple of 8x AGP stuff on the Internet about vanilla 2.4 kernels; 313<p>
322 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
323 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>
324 318
325<warn> 319<pre caption="Video card check">
326"Linux 2.4 doesn't support agp 8x, so I had to go find a backport. The backport 320# <i>lspci -vv</i>
327works .... 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])
328gotten it to work with vanilla, straight from the tarball (not ebuild)). First 322. . .
329go get the 2.4.20-2.4.21 patch from kernel.org .... (then get the patch,) It 323Capabilities: [58] AGP version 2.0
330was 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
331the pci_ids.h file, but if you actually read the file and the reject list, it's 325</pre>
332very easy to fix. But it does load, and it gives me 1600x1200 with video 326
333(although a bit slow b/c of lack of dga) with xfree-drm." (SanityInAnarchy on 327<p>
334#gentoo) 328While quite a lot of information is produced, we are looking for <b>FW</b> in
335</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>
336 333
337<impo> 334<impo>
338The 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
339link="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.
340the link</uri>. If you can disable 8X AGP in your BIOS, change it to 4X and you
341may not need the patch.
342</impo> 337</impo>
343-->
344 338
345</body>
346</section>
347<section>
348<title>Follow the CVS Instructions</title>
349<body>
350
351<p>
352The DRI project has a document about CVS compiling themselves. Please read <uri
353link="http://dri.freedesktop.org/wiki/Building">the document</uri> and follow
354the instructions up to the <e>Installing for X.org</e> part.
355</p> 339<p>
356 340Now let's make sure the motherboard supports fast writes as well. This time,
357</body> 341look at the "Host bridge" section of your <c>lspci</c> output.
358</section>
359<section>
360<title>Install the CVS</title>
361<body>
362
363<p> 342</p>
364Verify 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
365</p> 352<p>
366 353Again, examine the "Status" subsection of your AGP "Capabilities" section. Look
367<pre caption="Verification"> 354for <b>FW</b>. If you see <b>FW+</b>, your motherboard supports fast writes.
368# <i>cd ~/DRI-CVS/build/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel; ls</i>
369</pre>
370
371<p> 355</p>
372For the 3dfx Voodoo, you should see <path>tdfx.o</path>. For the Matrox 356
373G200/G400, you should see <path>mga.o</path>. For the ATI Rage 128, you should 357<impo>
374see <path>r128.o</path>. For the ATI Radeon, you should see 358Remember, both your video card information and your motherboard information
375<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
376If 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>.
377using the right version of the Linux kernel. The most recent kernels are not 361</impo>
378always supported. 362
379</p> 363<p>
380 364Assuming that all has gone well and both your motherboard and video card
381<p> 365support fast writes, let's enable this option in
382Install over your X.org installation. You may wish to back up xorg-x11. 366<path>/etc/X11/xorg.conf</path> and get the best performance out of your
383</p> 367hardware.
384
385<pre caption="Backing up Xorg">
386# <i>quickpkg xorg-x11</i>
387<comment>(This backs up your Xorg-X11 package.)</comment>
388# <i>make install</i>
389</pre>
390
391<p>
392Follow the "Configure Xorg" section above.
393</p>
394
395<p>
396To load the appropriate DRM module in your running kernel, copy the kernel
397module to <path>/lib/modules/`uname -r`/kernel/drivers/char/drm/</path> then
398run <c>modules-update</c> and restart your X server. If you're not running the
399kernel you'll be using it in, instead of <c>`uname -r`,</c> use that kernel's
400name.
401</p>
402
403<warn>
404Make sure you first unload any older DRI kernel modules that might be already
405loaded. Note that some DRM modules require that the agpgart module be loaded
406first.
407</warn>
408
409</body>
410</section>
411</chapter>
412
413<chapter>
414<title>Tweak your performance</title>
415<section>
416<title>Get the most out of direct rendering</title>
417<body>
418
419<p>
420A few options may increase performance by up to 30 percent (or more) over the
421default. Set them in <path>/etc/X11/xorg.conf</path>.
422</p> 368</p>
423 369
424<pre caption="xorg.conf"> 370<pre caption="xorg.conf">
425Section "Device" 371Section "Device"
426 Option "AGPMode" "4" 372 Option "AGPMode" "4"
432 <comment>(This improved FPS from 618 to 702. It also is "risky" but few people have reported problems.)</comment> 378 <comment>(This improved FPS from 618 to 702. It also is "risky" but few people have reported problems.)</comment>
433 ... 379 ...
434EndSection 380EndSection
435</pre> 381</pre>
436 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
437<p> 394<p>
438If you want to set even more features, check out the <uri 395If you want to set even more features, check out the <uri
439link="http://dri.freedesktop.org/wiki/FeatureMatrix">feature matrix</uri> on 396link="http://dri.freedesktop.org/wiki/FeatureMatrix">feature matrix</uri> on
440the DRI web site or the <uri 397the DRI web site or the <uri
441link="http://dri.sourceforge.net/doc/dri_driver_features.phtml">features 398link="http://dri.sourceforge.net/doc/dri_driver_features.phtml">features
447</chapter> 404</chapter>
448 405
449<chapter> 406<chapter>
450<title>Troubleshooting</title> 407<title>Troubleshooting</title>
451<section> 408<section>
452<title>It doesn't work. I just recompiled my kernel or switched to a new one.</title>
453<body>
454
455<p>
456Whenever you rebuild your kernel or switch to another kernel, you'll have to
457rebuild the kernel module. Note that you don't need to remerge xorg-x11, but
458you will need to remerge x11-drm.
459</p>
460
461</body>
462</section>
463
464<section>
465<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>
466<body> 410<body>
467 411
468<p> 412<p>
469Try <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>
470agpgart 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.
471</p> 416</p>
472 417
473</body> 418</body>
474</section> 419</section>
475<section> 420<section>
476<title>When I startx, I get this error: "[drm] failed to load kernel module agpgart"</title> 421<title>When I startx, I get this error: "[drm] failed to load kernel module agpgart"</title>
477<body> 422<body>
478 423
479<p> 424<p>
480That's because you compiled agpgart into the kernel instead of as a module. 425That's because you compiled agpgart into the kernel instead of as a module.
481Ignore it unless you're having problems. 426Ignore it unless you're having problems.
482</p> 427</p>
483 428
484</body> 429</body>
485</section> 430</section>
486<section> 431<section>
487<title>Direct rendering doesn't work, and in /var/log/Xorg.0.log I have an error about driver version too low.</title>
488<body>
489
490<p>
491You aren't using the x11-drm driver. Check if you compiled DRM and the driver
492into the kernel; you shouldn't have.
493</p>
494
495</body>
496</section>
497<section>
498<title>I have a Radeon, and I want TV-Out.</title> 432<title>I have a Radeon, and I want TV-Out.</title>
499<body> 433<body>
500 434
501<p> 435<p>
502Check 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.
503</p> 440</p>
504 441
505</body> 442</body>
506</section>
507<section> 443</section>
444<section>
445<title>
508<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>
509<body> 449<body>
510 450
511<p> 451<p>
512Try 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
513<uri>http://www.schneider-digital.de/html/download_ati.php</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>
514don'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.
515</p> 456</p>
516 457
517</body> 458</body>
518</section> 459</section>
519<section> 460<section>
520<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>
521<body> 462<body>
522 463
523<p> 464<p>
524In section "Device" enable ForcePCIMode. 465Edit <path>/etc/X11/xorg.conf</path>. In section "Device" enable ForcePCIMode.
525</p> 466</p>
526 467
527<pre caption="Enabling ForcePCIMode"> 468<pre caption="Enabling ForcePCIMode">
528Option "ForcePCIMode" "True" 469Option "ForcePCIMode" "True"
529</pre> 470</pre>
537<section> 478<section>
538<body> 479<body>
539 480
540<ol> 481<ol>
541 <li> 482 <li>
542 Christopher Webber for suggesting a troubleshooting question about changing 483 Christopher Webber for suggesting a troubleshooting question about changing
543 or recompiling kernels 484 or recompiling kernels
544 </li> 485 </li>
545 <li> 486 <li>
546 Steve, for suggesting consistency between the cases of dri and DRI in 487 Steve, for suggesting consistency between the cases of dri and DRI in
547 XF86Config 488 XF86Config
548 </li> 489 </li>
549</ol> 490</ol>
550 491
551</body> 492</body>

Legend:
Removed from v.1.26  
changed lines
  Added in v.1.41

  ViewVC Help
Powered by ViewVC 1.1.20