📄 139-143.html
字号:
<HTML>
<HEAD>
<TITLE>Linux Configuration and Installation:Installing and Configuring XFree86</TITLE>
<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
<SCRIPT>
<!--
function displayWindow(url, width, height) {
var Win = window.open(url,"displayWindow",'width=' + width +
',height=' + height + ',resizable=1,scrollbars=yes');
}
//-->
</SCRIPT>
</HEAD>
-->
<!--ISBN=1558285660//-->
<!--TITLE=Linux Configuration and Installation//-->
<!--AUTHOR=Patrick Volkerding//-->
<!--AUTHOR=Kevin Reichard//-->
<!--AUTHOR=Eric Foster//-->
<!--PUBLISHER=IDG Books Worldwide, Inc.//-->
<!--IMPRINT=M & T Books//-->
<!--CHAPTER=3//-->
<!--PAGES=139-143//-->
<!--UNASSIGNED1//-->
<!--UNASSIGNED2//-->
<CENTER>
<TABLE BORDER>
<TR>
<TD><A HREF="135-139.html">Previous</A></TD>
<TD><A HREF="../ewtoc.html">Table of Contents</A></TD>
<TD><A HREF="143-145.html">Next</A></TD>
</TR>
</TABLE>
</CENTER>
<P><BR></P>
<H3><A NAME="Heading17"></A><FONT COLOR="#000077">Combining the Graphics Card with the Monitor to Make a Working X Setup</FONT></H3>
<P>The Screen section connects a monitor with a graphics card. Your <B>XF86Config</B> file may have multiple Devices and Monitors defined. It is the Screen section that connects the two.</P>
<P>A complicated Screen section can look something like:</P>
<!-- CODE //-->
<PRE>
Section "Screen"
Driver "accel"
Device "Actix GE32+ 2MB"
Monitor "NEC MultiSync XE17"
Subsection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
Virtual 1024 768
EndSubsection
Subsection "Display"
Depth 16
Modes "640x480" "800x600"
ViewPort 0 0
Virtual 800 600
EndSubsection
Subsection "Display"
Depth 32
Modes "640x400"
ViewPort 0 0
Virtual 640 400
EndSubsection
EndSection
</PRE>
<!-- END CODE //-->
<P>Note that the Screen section uses the monitor and device identifiers we entered earlier. This is essential to connect the screen to the proper monitor and card.
</P>
<P>The Driver tells what kind of X server you’re using; the choices are Accel, SVGA, VGA16, VGA2, or Mono. In almost all cases, you’ll use <I>SVGA</I> for Super VGA cards (and the <B>XF86_SVGA</B> X server) or <I>Accel</I> for any accelerated chipset and X server, such as the <B>XF86_S3</B> server we mentioned in the last chapter.</P>
<P>Each Display subsection covers the modes available at a particular depth. (A depth of eight specifies eight planes for color, or 256 maximum colors.) The Modes used refer back to the Modelines for the monitor that we defined earlier.</P>
<H4 ALIGN="LEFT"><A NAME="Heading18"></A><FONT COLOR="#000077">Virtual Screens</FONT></H4>
<P>The Virtual line allows you to define a virtual screen that is larger than the number of pixels supported by your monitor. The X server will automatically scroll the display when the mouse hits the end. If you like this effect (we don’t), then set the Virtual resolution to something larger than your monitor allows, such as:
</P>
<!-- CODE SNIP //-->
<PRE>
Virtual 1152 900
</PRE>
<!-- END CODE SNIP //-->
<P>This virtual setting creates a traditional Sun Microsystems resolution. This is useful if you need to run older programs that were designed with Sun systems in mind and want to grab more than the default 1024-by-768 screen area available on most PCs.
</P>
<P>The ViewPort line tells where the X server should start up. For example, a ViewPort of 0,0 tells X that when it starts up, it should display position 0,0 in the upper-left-hand corner (which is what you’d expect on X). If you’d rather start in the middle (an unlikely option), you can change this.</P>
<BLOCKQUOTE>
<P><FONT SIZE="-1"><HR><B>WARNING: </B>The <B>fvwm</B> window manager supports a different kind of virtual screen. Don’t mix the two types of virtual screen or you’ll likely have trouble.<HR></FONT>
</BLOCKQUOTE>
<H3><A NAME="Heading19"></A><FONT COLOR="#000077">Running the Xf86config Program</FONT></H3>
<P>Now that we’ve gone over the contents of the <B>XF86Config</B> file, we can run the <B>xf86config</B> program, or, if you’d prefer, fill in the file by hand. We recommend using <B>xf86config</B> and then checking the <B>XF86Config</B> file it builds by hand. The <B>xf86config</B> program isn’t flawless and needs careful supervision.</P>
<P>When you run <B>xf86config</B>, you should not be in the <B>/usr/X11R6/ lib/X11</B> directory. Instead, put an <B>XF86Config</B> file in a directory in your user account and try copying it later to <B>/usr/X11R6/lib/X11</B>.</P>
<P>As the program starts up, it will start asking a lot of questions. The <B>xf86config</B> program will prompt you for a lot of the values necessary for the <B>XF86Config</B> file, such as type of mouse, your desires for the keyboard, and monitor frequencies. When you’re done, <B>xf86config</B> will write out the data into a file named <B>XF86Config</B> in the current directory. (This is why you don’t want to be in <B>/usr/lib/X11</B>, which is a symbolic link to <B>/usr/X11R6/lib/X11</B>, when you run this program.)</P>
<P>Once the <B>xf86config</B> program finishes, you should carefully examine the <B>XF86Config</B> file it generates. This file will still be incomplete, because you haven’t probed for the clocks yet. Edit the <B>XF86Config</B> file. If it looks OK, then, as the root user, copy the file to <B>/usr/X11R6/lib/X11</B>, but be sure to back up any existing <B>XF86Config</B> file first.</P>
<P>Now you’re ready to try <B>X</B> in <B>probeonly</B> mode.</P><P><BR></P>
<CENTER>
<TABLE BORDER>
<TR>
<TD><A HREF="135-139.html">Previous</A></TD>
<TD><A HREF="../ewtoc.html">Table of Contents</A></TD>
<TD><A HREF="143-145.html">Next</A></TD>
</TR>
</TABLE>
</CENTER>
</td>
</tr>
</table>
<!-- begin footer information -->
</body></html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -