Changeset 19e9cee for x/installing/dri.xml
- Timestamp:
- 09/14/2002 09:47:22 PM (22 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.0, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, v1_0, v5_0, v5_0-pre1, v5_1, v5_1-pre1, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- bc013897
- Parents:
- 07ba0069
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
x/installing/dri.xml
r07ba0069 r19e9cee 11 11 <note><para>These instructions were developed from the DRI Compilation Guide at 12 12 <userinput><ulink url="http://www.xfree86.org/4.2.0/DRIcomp.html"/></userinput> 13 and modified for more recent versions of the DRI. 14 </para></note> 15 16 <para> 17 The DRI drivers generally work on systems with Intel or AMD CPUs. However, 18 there is limited support for Alpha and PowerPC support underway. 19 </para> 20 21 <para> 22 DRI support is currently in beta status. The following video cards are 13 and modified for more recent versions of the DRI.</para></note> 14 15 <para>The DRI drivers generally work on systems with Intel or AMD CPUs. 16 However, there is limited support for Alpha and PowerPC support 17 underway.</para> 18 19 <para>DRI support is currently in beta status. The following video cards are 23 20 presently supported:</para> 21 24 22 <itemizedlist> 23 25 24 <listitem><para>3dfx (Voodoo 5 5500, Voodoo4 4500, Voodoo3 3500 TV, 26 25 Voodoo3 3000 {AGP, PCI}, Voodoo3 2000 {AGP, PCI}, Voodoo Banshee, 27 Velocity 100/200) 28 </para></listitem>29 <listitem><para>Matrox (G200, G400) 30 </para></listitem> 26 Velocity 100/200)</para></listitem> 27 28 <listitem><para>Matrox (G200, G400) </para></listitem> 29 31 30 <listitem><para>Intel Motherboard Chipsets (i810, i810-dc100, i810e, i815, 32 i830) 33 </para></listitem>31 i830) </para></listitem> 32 34 33 <listitem><para>ATI (Rage {128, Fury, Magnum}, XPERT {2000, 128, 99}, 35 All-in-Wonder 128, Radeon {SDR AGP, DDR AGP, 32MB SDR PCI} 36 </para></listitem> 37 <listitem><para>3Dlabs (Oxygen 2000) [No longer actively being developed] 38 </para></listitem> 34 All-in-Wonder 128, Radeon {SDR AGP, DDR AGP, 32MB SDR PCI} </para></listitem> 35 36 <listitem><para>3Dlabs (Oxygen 2000) [No longer actively being 37 developed] </para></listitem> 38 39 39 </itemizedlist> 40 40 41 <para> 42 For 3dfx Voodoo3 hardware, you'll also need Glide3 headers and runtime library. 43 These can be obtained from 44 <userinput><ulink url="http://linux.3dfx.com"/></userinput>. 45 </para> 41 <para>For 3dfx Voodoo3 hardware, you'll also need Glide3 headers and 42 runtime library. These can be obtained 43 from <userinput><ulink url="http://linux.3dfx.com"/></userinput>.</para> 46 44 47 45 <sect2><title>Updating the Kernel</title> 48 <para> 49 In the kernel configuration "Character Devices" section,46 47 <para>In the kernel configuration "Character Devices" section, 50 48 if you havn't already done so, <emphasis>enable</emphasis> Direct Rendering 51 49 Manager. Also select the type of video card(s) that you want to support as 52 50 a <emphasis>module</emphasis>. This is necessary to ensure the kernel 53 has the proper linkages when the DRI code is compiled. 54 </para> 51 has the proper linkages when the DRI code is compiled.</para> 52 55 53 <para>If necessary, recompile the kernel with 56 <screen> make dep &&54 <screen><userinput>make dep && 57 55 make bzImage&& 58 56 make modules && 59 make modules_install</screen> 60 </para> 61 <para> 62 Copy <filename>/usr/src/linux/arch/i386/boot/bzImage</filename> and 57 make modules_install</userinput></screen></para> 58 59 <para>Copy <filename>/usr/src/linux/arch/i386/boot/bzImage</filename> and 63 60 <filename>/usr/src/linux/System.map</filename> to 64 61 <filename>/boot</filename>, edit <filename>/etc/lilo.conf</filename> 65 appropriately and run <userinput>lilo</userinput>. 66 </para> 67 </sect2> 68 69 <sect2> 70 <title>Getting the DRI driver source code</title> 71 <para> 72 Get the DRI sources by 73 <screen>cd /usr/src 62 appropriately and run <userinput>lilo</userinput>.</para> 63 64 </sect2> 65 66 <sect2><title>Getting the DRI driver source code</title> 67 68 <para>Get the DRI sources by 69 <screen><userinput>cd /usr/src 74 70 mkdir DRI-CVS 75 71 cd DRI-CVS 76 cvs -d:pserver:anonymous@cvs.dri.sourceforge.net:/cvsroot/dri login 72 cvs -d:pserver:anonymous@cvs.dri.sourceforge.net:/cvsroot/dri login</userinput> 77 73 (hit ENTER when prompted for a password) 78 cvs -z3 -d:pserver:anonymous@cvs.dri.sourceforge.net:/cvsroot/dri co xc</screen> 79 </para> 74 <userinput>cvs -z3 -d:pserver:anonymous@cvs.dri.sourceforge.net:/cvsroot/dri co xc</userinput></screen></para> 75 80 76 <note><para>The -z3 flag causes compression to be used in order to reduce the 81 77 download time.</para></note> 82 78 83 79 <para>Since, the DRI drivers are beta, you can update the sources by 84 <screen> cd /usr/src/DRI-CVS85 cvs -z3 update -dA xc</ screen></para>80 <screen><userinput>cd /usr/src/DRI-CVS 81 cvs -z3 update -dA xc</userinput></screen></para> 86 82 87 83 <para>There is no need to download or install the Mesa source files separately. 88 The download is about 99Mb and the build size 477Mb. 89 </para> 84 The download is about 99Mb and the build size 477Mb.</para> 85 90 86 </sect2> 91 87 92 88 <sect2><title>Building the DRI</title> 89 93 90 <para>DRI drivers will be built in a separate directory from the main XFree86 94 91 sources. To access the proper files, link the files to a build directoy: 95 <screen> cd /usr/src/DRI-CVS92 <screen><userinput>cd /usr/src/DRI-CVS 96 93 ln -s xc XFree40 97 94 mkdir build 98 95 cd build 99 lndir -silent -ignorelinks ../XFree40</screen> 100 </para> 96 lndir -silent -ignorelinks ../XFree40</userinput></screen></para> 101 97 102 98 <para>Now update the <filename>host.def</filename> file. The only change 103 99 necessary is to uncomment the <parameter>BuildXF86DRM</parameter> define. 104 Since DRI is still in Beta, changing the optimizations is not recommended. 105 </para> 106 <para> 107 If you do not want to build all the drivers, change 108 <parameter>XF86CardDrivers</parameter> and <parameter>DriDrivers</parameter> 109 to eliminate those that you don't want. 110 </para> 100 Since DRI is still in Beta, changing the optimizations is not 101 recommended.</para> 102 103 <para>If you do not want to build all the drivers, 104 change <parameter>XF86CardDrivers</parameter> 105 and <parameter>DriDrivers</parameter> to eliminate those that 106 you don't want.</para> 107 111 108 <para>Ensure the Linux 2.4.x headers are available in 112 109 <filename>/usr/src/linux/include/linux</filename>.</para> … … 118 115 number.</para> 119 116 120 121 117 <sect3><title>Compiling the DRI</title> 122 118 123 <note><para> 124 If you build XFree86 in a chroot environment, make sure the kernel version of the base 125 system and the target system are the same. 126 </para></note> 127 128 <warning><para>Do not use -j option for <filename>make</filename></para>129 </warning> 130 131 < para>Build the system by132 <screen>cd xc && 133 make World 2>&1 | tee World.log</screen></para> 134 135 <para>Using <userinput>less</userinput> or an editor, examine136 <filename>World.log</filename> 137 for errors by searching for the pattern ***. Also examine the directory 138 <filename>/usr/src/DRI-CVS/build/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/</filename>139 for the drivers you built:</para> 119 <note><para>If you build XFree86 in a chroot environment, make sure the 120 kernel version of the base system and the target system are 121 the same.</para></note> 122 123 <warning><para>Do not use -j option 124 for <filename>make</filename></para></warning> 125 126 <para>Build the system using: 127 <screen><userinput>cd xc && 128 make World 2>&1 | tee World.log</userinput></screen></para> 129 130 <para>Using <userinput>less</userinput> or an editor, 131 examine <filename>World.log</filename> for errors by searching for 132 the pattern ***. Also examine the 133 directory <filename>/usr/src/DRI-CVS/build/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/</filename> for 134 the drivers you built:</para> 135 140 136 <itemizedlist> 141 <listitem><para>For the 3dfx Voodoo, you should see <filename>tdfx.o</filename> 142 </para></listitem> 143 <listitem><para>For the Matrox G200/G400, you should see 144 <filename>mga.o</filename> 145 </para></listitem> 146 <listitem><para>For the ATI Rage 128, you should see <filename>r128.o</filename> 147 </para></listitem> 148 <listitem><para>For the ATI Radeon, you should see <filename>radeon.o</filename> 149 </para></listitem> 150 <listitem><para>For the Intel i81x, you should see <filename>i810.o</filename> 151 </para></listitem> 152 <listitem><para>For the Intel i830, you should see <filename>i830.o</filename> 153 </para></listitem> 137 138 <listitem><para>For the 3dfx Voodoo, you should 139 see <filename>tdfx.o</filename></para></listitem> 140 141 <listitem><para>For the Matrox G200/G400, you should 142 see <filename>mga.o</filename></para></listitem> 143 144 <listitem><para>For the ATI Rage 128, you should 145 see <filename>r128.o</filename></para></listitem> 146 147 <listitem><para>For the ATI Radeon, you should 148 see <filename>radeon.o</filename></para></listitem> 149 150 <listitem><para>For the Intel i81x, you should 151 see <filename>i810.o</filename></para></listitem> 152 153 <listitem><para>For the Intel i830, you should 154 see <filename>i830.o</filename></para></listitem> 155 154 156 </itemizedlist> 155 157 … … 158 160 159 161 <sect2><title>Installing the DRI drivers</title> 160 <para>Copy the kernel module that for your video card to 161 <filename>/lib/modules/2.4.x/kernel/drivers/char/drm/</filename> 162 163 <para>Copy the kernel module that for your video card 164 to <filename>/lib/modules/2.4.x/kernel/drivers/char/drm/</filename> 162 165 then run <userinput>modprobe <module name></userinput>.</para> 163 166 … … 167 170 <para>Now install the other portions of the DRI that were built and ensure the 168 171 libraries can be found correctly 169 <screen>make install && 170 ldconfig</screen></para> 171 172 <para> 173 If you use X locale information, do the following 174 <screen>cd /usr/src/DRI-CVS/build/xc/nls 172 <screen><userinput>make install && 173 ldconfig</userinput></screen></para> 174 175 <para>If you use X locale information, do the following 176 <screen><userinput>cd /usr/src/DRI-CVS/build/xc/nls 175 177 ../config/util/xmkmf -a 176 178 make 177 make install</ screen></para>179 make install</userinput></screen></para> 178 180 179 181 </sect2> … … 181 183 <sect2><title>Configuring XFree86 for the DRI</title> 182 184 183 <para>On the DRI web site, 184 <userinput><ulink url="http://dri.sourceforge.net"/></userinput>, 185 in the resources section, you'll find example 186 <filename>XF86Config</filename> 185 <para>On the DRI web site, <ulink url="http://dri.sourceforge.net"/>, 186 in the resources section, you'll find example <filename>XF86Config</filename> 187 187 files for a number of graphics cards. These configuration files also setup 188 DRI options so it's highly recommended that you look at these examples. 189 </para> 190 188 DRI options so it's highly recommended that you look at these examples.</para> 191 189 <para>Generally you can start with your existing configuration file, 192 190 <filename>/etc/X11/XFConfig-4</filename>, but if you run into trouble 193 you may want to start with a new file as in the basic XFree86 installation.194 </para>191 you may want to start with a new file as in the basic XFree86 192 installation.</para> 195 193 196 194 <para>Edit <filename>XF86Config-4</filename> to ensure … … 212 210 213 211 <para>Make any other changes for font paths, screen modes, etc., as needed 214 and save the configuration file. 215 </para> 216 217 <note><para> 218 DMA-based DRI drivers (that's most DRI drivers) cannot function unless 219 bus mastering is enabled for your graphics card. By default, some systems 220 don't having bus mastering on. You should enable it in your BIOS. 221 </para></note> 212 and save the configuration file.</para> 213 214 <note><para>DMA-based DRI drivers (that's most DRI drivers) cannot function 215 unless bus mastering is enabled for your graphics card. By default, some 216 systems don't having bus mastering on. You should enable it in your 217 BIOS.</para></note> 218 222 219 </sect2> 223 220 … … 226 223 <para>Start (or restart) XFree86 with <userinput>startx</userinput>.</para> 227 224 228 <para> 229 Check the XFree86 log file, <filename>/var/log/XFree86.0.log</filename>, 225 <para>Check the XFree86 log file, <filename>/var/log/XFree86.0.log</filename>, 230 226 for a statements like 231 227 <screen>(II) R128(0): [drm] installed DRM signal handler … … 276 272 0x28 16 dc 0 16 0 r y . 5 6 5 0 0 16 8 0 0 0 0 0 0 Slow 277 273 0x29 16 dc 0 16 0 r y . 5 6 5 0 0 16 0 16 16 16 0 0 0 Slow 278 0x2a 16 dc 0 16 0 r y . 5 6 5 0 0 16 8 16 16 16 0 0 0 Slow</screen> 279 </para> 274 0x2a 16 dc 0 16 0 r y . 5 6 5 0 0 16 8 16 16 16 0 0 0 Slow</screen></para> 280 275 281 276 <para>Run <userinput>ldd /usr/X11R6/bin/glxgears</userinput> and look for … … 295 290 <filename>xterm</filename> will display how many frames were drawn every 296 291 five seconds so this is a reasonable benchmark. The window is scalable, and 297 the frames drawn per second is highly dependent on the size of the window.298 </para>299 300 <para> 301 For troubleshooting problems, check the DRI Users Guide at 302 <userinput><ulink url="http://dri.sourceforge.net/doc/DRIuserguide.html"/></userinput>. 303 </ para>304 </sect2> 292 the frames drawn per second is highly dependent on the size of 293 the window.</para> 294 295 <para>For troubleshooting problems, check the DRI Users Guide at 296 <userinput><ulink url="http://dri.sourceforge.net/doc/DRIuserguide.html"/></userinput>.</para> 297 298 </sect2> 299 305 300 </sect1> 306
Note:
See TracChangeset
for help on using the changeset viewer.