/[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.42
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.42 2008/09/10 21:20:28 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
19<!-- The content of this document is licensed under the CC-BY-SA license --> 24<!-- The content of this document is licensed under the CC-BY-SA license -->
20<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 25<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
21<license/> 26<license/>
22 27
23<version>1.2</version> 28<version>1.11</version>
24<date>2006-02-01</date> 29<date>2008-09-10</date>
25 30
26<chapter> 31<chapter>
27<title>Introduction</title> 32<title>Introduction</title>
28<section> 33<section>
29<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>
30<body> 35<body>
31 36
32<p> 37<p>
33With hardware 3D acceleration, three-dimensional rendering uses the graphics 38With hardware 3D acceleration, three-dimensional rendering uses the graphics
34processor on your video card instead of taking up valuable CPU resources 39processor on your video card instead of taking up valuable CPU resources
35drawing 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
36"software acceleration" because without this 3D acceleration your CPU is forced 41"software acceleration" because without this 3D acceleration your CPU is forced
37to draw everything itself using the Mesa software rendering libraries, which 42to draw everything itself using the Mesa software rendering libraries, which
38takes 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
39hardware acceleration, it often lacks hardware 3D acceleration. 44hardware acceleration, it often lacks hardware 3D acceleration.
40Three-dimensional hardware acceleration is valuable in situations requiring 45Three-dimensional hardware acceleration is valuable in situations requiring
41rendering of 3D objects such as games, 3D CAD and modeling. 46rendering of 3D objects such as games, 3D CAD and modeling.
42</p> 47</p>
43 48
44</body> 49</body>
45</section> 50</section>
46<section> 51<section>
47<title>How do I get hardware 3D acceleration?</title> 52<title>How do I get hardware 3D acceleration?</title>
48<body> 53<body>
49 54
50<p> 55<p>
51In 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
52are 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
53principles. Sometimes, binary drivers are the only option, like with nVidia's 58principles. Sometimes, binary drivers are the only option, like with nVidia's
54cards. Binary drivers include media-video/nvidia-kernel and 59cards. 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 60and <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> 61</p>
60 62
61</body> 63</body>
62</section> 64</section>
63<section> 65<section>
73</p> 75</p>
74 76
75</body> 77</body>
76</section> 78</section>
77<section> 79<section>
78<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>
79<body> 81<body>
80 82
81<p> 83<p>
82X11-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
83cards by adding the kernel module necessary for direct rendering. 85acceleration for cards by adding the kernel module necessary for direct
86rendering.
84</p> 87</p>
85 88
86</body> 89</body>
87</section> 90</section>
88<section> 91<section>
89<title>Purpose</title> 92<title>Purpose</title>
90<body> 93<body>
91 94
92<p> 95<p>
93This 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.
94X11-DRM works for 3dfx, gamma, i8x0, matrox, rage128, radeon, mach64 and sis300 97The DRM works for the following drivers:
95series drivers. See the <uri link="http://dri.freedesktop.org/">DRI 98</p>
96homepage</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.
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>
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<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>
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
164Character devices ---&gt; 181Device drivers --->
182 Graphics support --->
165&lt;M&gt; /dev/agpgart (AGP Support) 183 &lt;M&gt; /dev/agpgart (AGP Support) --->
166[M] 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<comment>(Enable your chipset instead of the above.)</comment> 186 <comment>(Enable your chipset instead of the above.)</comment>
168&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) --->
169</pre> 188 &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> 189</pre>
175 190
176</body> 191</body>
177</section> 192</section>
178<section> 193<section>
179<title>Compile and install your kernel</title> 194<title>Compile and install your kernel</title>
180<body> 195<body>
181 196
182<pre caption="Compiling and installing kernel"> 197<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> 198# <i>make &amp;&amp; make modules_install</i>
185# <i>mount /boot</i>
186# <i>cp arch/i386/boot/bzImage /boot</i>
187</pre> 199</pre>
188 200
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> 201<p>
202Don'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>
194 205
195</body> 206</body>
196</section>
197</chapter>
198
199<chapter>
200<title>Install X11-DRM and configure direct rendering</title>
201<section> 207</section>
202<title>Install X11-DRM</title> 208</chapter>
203<body>
204 209
205<pre caption="Installing X11-DRM"> 210<chapter>
206# <i>emerge x11-drm</i> 211<title>Configure direct rendering</title>
207</pre>
208
209</body>
210</section>
211<section id="configure_xorg"> 212<section id="configure_xorg">
212<title>Configure Xorg.conf</title> 213<title>Configure Xorg.conf</title>
213<body> 214<body>
214 215
215<p> 216<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 217Open <path>/etc/X11/xorg.conf</path> with your favorite text editor and edit
232it to enable DRI and GLX. 218it to enable DRI and GLX.
233</p> 219</p>
234 220
235<pre caption="xorg.conf"> 221<pre caption="xorg.conf">
236... 222...
240 ... 226 ...
241EndSection 227EndSection
242... 228...
243Section "Device" 229Section "Device"
244 Driver "radeon" 230 Driver "radeon"
231 <comment>(Replace radeon with the name of your driver.)</comment>
245 ... 232 ...
246EndSection 233EndSection
247... 234...
248Section "dri" 235Section "dri"
249 Mode 0666 236 Mode 0666
250EndSection 237EndSection
251</pre> 238</pre>
252 239
253<p>
254If you are using a different driver, replace "radeon" with yours.
255</p>
256
257</body> 240</body>
258</section> 241</section>
259<section> 242<section>
260<title>Changes to modules.autoload.d</title> 243<title>Changes to modules.autoload.d</title>
261<body> 244<body>
269<pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> 252<pre caption="Editing /etc/modules.autoload.d/kernel-2.6">
270<comment>(Change module name as required.)</comment> 253<comment>(Change module name as required.)</comment>
271intel-agp 254intel-agp
272</pre> 255</pre>
273 256
257<note>
258If 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
274</body> 262</body>
275</section> 263</section>
276</chapter> 264</chapter>
277 265
278<chapter> 266<chapter>
280<section> 268<section>
281<title>Reboot to the new kernel</title> 269<title>Reboot to the new kernel</title>
282<body> 270<body>
283 271
284<p> 272<p>
285Reboot your computer to your new kernel. It's time to see if you have direct 273Reboot your computer to your new kernel and login as a normal user. It's time to
286rendering and how good it is. 274see 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
276installed before you attempt to run these commands.
287</p> 277</p>
288 278
289<pre caption="Testing rendering"> 279<pre caption="Testing rendering">
290# <i>startx</i> 280$ <i>startx</i>
291<comment>(No need to load modules for your driver or agpgart, if you compiled agpgart as a module.)</comment> 281<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> 282<comment>(They will be loaded automatically.)</comment>
293# <i>glxinfo | grep rendering</i> 283$ <i>glxinfo | grep rendering</i>
294direct rendering: Yes 284direct rendering: Yes
295<comment>(If it says "No," you don't have 3D acceleration.)</comment> 285<comment>(If it says "No", you don't have 3D acceleration.)</comment>
296# <i>glxgears</i> 286$ <i>glxgears</i>
297<comment>(Test your frames per second (FPS) at the default size. The number should be )</comment> 287<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> 288significantly higher than before configuring DRM. Do this while the CPU is as idle as
289possible.)</comment>
299</pre> 290</pre>
300 291
301</body> 292<note>
302</section> 293FPS may be limited by your screen's refresh rate, so keep this in mind if
303</chapter> 294<c>glxgears</c> reports only about 70-100 FPS. <c>games-fps/ut2004-demo</c> is a
295better benchmarking tool, as it can give you real-world performance results.
296</note>
304 297
305<chapter> 298</body>
306<title>Using the CVS sources</title>
307<section> 299</section>
308<body> 300</chapter>
309 301
310<warn> 302<chapter>
311Don't do this if the package worked. 303<title>Tweak your performance</title>
312</warn>
313
314</body>
315</section> 304<section>
316<section> 305<title>Get the most out of direct rendering</title>
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> 306<body>
328</section>
329<section>
330<title>Do the CVS sources support your card?</title>
331<body>
332 307
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> 308<p>
309A few options may increase performance by up to 30 percent (or more) over the
310default. Set them in <path>/etc/X11/xorg.conf</path>. However, you will first
311need to check that your motherboard and video card support these options.
312</p>
338 313
339<!-- I see a couple of 8x AGP stuff on the Internet about vanilla 2.4 kernels; 314<p>
340 is this now available or not? I've commented it out for the time being, 315First, let's see if your video card can support fast writes. We'll do this by
341 hoping that this doesn't affect us :) 316closely inspecting the output from <c>lspci</c>. Specifically, we are looking
317at the "VGA compatible controller" information.
318</p>
342 319
343<warn> 320<pre caption="Video card check">
344"Linux 2.4 doesn't support agp 8x, so I had to go find a backport. The backport 321# <i>lspci -vv</i>
345works .... it doesn't patch quite properly, and it requires 2.4.21 (I've only 32201:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY (prog-if 00 [VGA])
346gotten it to work with vanilla, straight from the tarball (not ebuild)). First 323. . .
347go get the 2.4.20-2.4.21 patch from kernel.org .... (then get the patch,) It 324Capabilities: [58] AGP version 2.0
348was on a mailing list somewhere. It doesn't patch cleanly - - one file fails, 325 Status: RQ=48 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
349the pci_ids.h file, but if you actually read the file and the reject list, it's 326</pre>
350very easy to fix. But it does load, and it gives me 1600x1200 with video 327
351(although a bit slow b/c of lack of dga) with xfree-drm." (SanityInAnarchy on 328<p>
352#gentoo) 329While quite a lot of information is produced, we are looking for <b>FW</b> in
353</warn> 330the "Status" subsection of the AGP "Capabilities" section. If <b>FW+</b> is
331present in the "Status" line, it means the card supports fast writes. We can
332now check if the motherboard supports fast writes.
333</p>
354 334
355<impo> 335<impo>
356The patch is a little tricky to work with but <uri 336If you do not see <b>FW+</b>, but instead see <b>FW-</b>, you cannot enable
357link="http://www.ussg.iu.edu/hypermail/linux/kernel/0302.2/att-1618/01-agp3.diff.bz2">here's 337fast writes in <path>xorg.conf</path>. Your card does not support fast writes.
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> 338</impo>
361-->
362 339
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> 340<p>
374 341Now let's make sure the motherboard supports fast writes as well. This time,
375</body> 342look at the "Host bridge" section of your <c>lspci</c> output.
376</section>
377<section>
378<title>Install the CVS</title>
379<body>
380
381<p> 343</p>
382Verify that the DRI kernel module(s) for your system were built: 344
345<pre caption="Motherboard check">
346# <i>lspci -vv</i>
34700:00.0 Host bridge: Intel Corporation 82830 830 Chipset Host Bridge (rev 02)
348. . .
349Capabilities: [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
383</p> 353<p>
384 354Again, examine the "Status" subsection of your AGP "Capabilities" section. Look
385<pre caption="Verification"> 355for <b>FW</b>. If you see <b>FW+</b>, your motherboard supports fast writes.
386# <i>cd ~/DRI-CVS/build/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel; ls</i>
387</pre>
388
389<p> 356</p>
390For the 3dfx Voodoo, you should see <path>tdfx.o</path>. For the Matrox 357
391G200/G400, you should see <path>mga.o</path>. For the ATI Rage 128, you should 358<impo>
392see <path>r128.o</path>. For the ATI Radeon, you should see 359Remember, both your video card information and your motherboard information
393<path>radeon.o</path>. For the Intel i810, you should see <path>i810.o</path>. 360must show the same <b>FW</b> capability. If either device shows <b>FW-</b> in
394If the DRI kernel module(s) failed to build, you should verify that you're 361"Status", you cannot enable fast writes in <path>xorg.conf</path>.
395using the right version of the Linux kernel. The most recent kernels are not 362</impo>
396always supported. 363
397</p> 364<p>
398 365Assuming that all has gone well and both your motherboard and video card
399<p> 366support fast writes, let's enable this option in
400Install over your X.org installation. You may wish to back up xorg-x11. 367<path>/etc/X11/xorg.conf</path> and get the best performance out of your
401</p> 368hardware.
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>
434<title>Get the most out of direct rendering</title>
435<body>
436
437<p>
438A few options may increase performance by up to 30 percent (or more) over the
439default. Set them in <path>/etc/X11/xorg.conf</path>.
440</p> 369</p>
441 370
442<pre caption="xorg.conf"> 371<pre caption="xorg.conf">
443Section "Device" 372Section "Device"
444 Option "AGPMode" "4" 373 Option "AGPMode" "4"
450 <comment>(This improved FPS from 618 to 702. It also is "risky" but few people have reported problems.)</comment> 379 <comment>(This improved FPS from 618 to 702. It also is "risky" but few people have reported problems.)</comment>
451 ... 380 ...
452EndSection 381EndSection
453</pre> 382</pre>
454 383
384<warn>
385Enabling <c>AGPFastWrite</c> on a VIA chipset will very likely cause your
386machine to lock up. VIA chipsets do not play nicely with fast writes, so use
387this setting at your own risk.
388</warn>
389
390<note>
391Remember, if you want fast writes to work properly, you will have to first
392enable the appropriate option in your BIOS.
393</note>
394
455<p> 395<p>
456If you want to set even more features, check out the <uri 396If you want to set even more features, check out the <uri
457link="http://dri.freedesktop.org/wiki/FeatureMatrix">feature matrix</uri> on 397link="http://dri.freedesktop.org/wiki/FeatureMatrix">feature matrix</uri> on
458the DRI web site or the <uri 398the DRI web site or the <uri
459link="http://dri.sourceforge.net/doc/dri_driver_features.phtml">features 399link="http://dri.sourceforge.net/doc/dri_driver_features.phtml">features
465</chapter> 405</chapter>
466 406
467<chapter> 407<chapter>
468<title>Troubleshooting</title> 408<title>Troubleshooting</title>
469<section> 409<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> 410<title>It doesn't work. I don't have rendering, and I can't tell why.</title>
484<body> 411<body>
485 412
486<p> 413<p>
487Try <c>insmod radeon</c> before you start the X server. Also, try building 414Try <c>modprobe radeon</c> before you start the X server (replace <c>radeon</c>
488agpgart into the kernel instead of as a module. 415with the name of your driver). Also, try building agpgart into the kernel
416instead of as a module.
489</p> 417</p>
490 418
491</body> 419</body>
492</section> 420</section>
493<section> 421<section>
494<title>When I startx, I get this error: "[drm] failed to load kernel module agpgart"</title> 422<title>When I startx, I get this error: "[drm] failed to load kernel module agpgart"</title>
495<body> 423<body>
496 424
497<p> 425<p>
498That's because you compiled agpgart into the kernel instead of as a module. 426That's because you compiled agpgart into the kernel instead of as a module.
499Ignore it unless you're having problems. 427Ignore it unless you're having problems.
500</p> 428</p>
501 429
502</body> 430</body>
503</section> 431</section>
504<section> 432<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> 433<title>I have a Radeon, and I want TV-Out.</title>
517<body> 434<body>
518 435
519<p> 436<p>
520Check out ati-gatos drivers. <c>emerge -s gatos</c>. 437The drivers originally developed by the <uri
438link="http://gatos.sf.net">GATOS</uri> project have been merged into Xorg's
439codebase. You don't need anything special for TV-Out;
440<c>x11-drivers/xf86-video-ati</c> will work just fine.
521</p> 441</p>
522 442
523</body> 443</body>
524</section>
525<section> 444</section>
445<section>
446<title>
526<title>It doesn't work. My card is so incredibly new and cool that it isn't supported at all.</title> 447It doesn't work. My card is so incredibly new and cool that it isn't supported
448at all.
449</title>
527<body> 450<body>
528 451
529<p> 452<p>
530Try out the binary drivers. For ati-drivers, a listing is at 453Try 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 454<uri>http://ati.amd.com/support/drivers/linux/linux-radeon.html</uri> (for x86)
455and at <uri>http://ati.amd.com/support/drivers/linux64/linux64-radeon.html</uri>
532don't support it, use fbdev. It's slow, but it works. 456(for amd64). If those don't support it, use fbdev. It's slow, but it works.
533</p> 457</p>
534 458
535</body> 459</body>
536</section> 460</section>
537<section> 461<section>
538<title>I have a PCI card and it doesn't work. Help!</title> 462<title>I have a PCI card and it doesn't work. Help!</title>
539<body> 463<body>
540 464
541<p> 465<p>
542In section "Device" enable ForcePCIMode. 466Edit <path>/etc/X11/xorg.conf</path>. In section "Device" enable ForcePCIMode.
543</p> 467</p>
544 468
545<pre caption="Enabling ForcePCIMode"> 469<pre caption="Enabling ForcePCIMode">
546Option "ForcePCIMode" "True" 470Option "ForcePCIMode" "True"
547</pre> 471</pre>
555<section> 479<section>
556<body> 480<body>
557 481
558<ol> 482<ol>
559 <li> 483 <li>
560 Christopher Webber for suggesting a troubleshooting question about changing 484 Christopher Webber for suggesting a troubleshooting question about changing
561 or recompiling kernels 485 or recompiling kernels
562 </li> 486 </li>
563 <li> 487 <li>
564 Steve, for suggesting consistency between the cases of dri and DRI in 488 Steve, for suggesting consistency between the cases of dri and DRI in
565 XF86Config 489 XF86Config
566 </li> 490 </li>
567</ol> 491</ol>
568 492
569</body> 493</body>

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

  ViewVC Help
Powered by ViewVC 1.1.20