White space fix only. Translators can ignore.

This commit is contained in:
Dru Lavigne 2013-10-08 23:04:53 +00:00
parent ee54ccdf52
commit 057950e679
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=42907

View file

@ -27,7 +27,7 @@
<para>An installation of &os; using
<application>bsdinstall</application> does not automatically
install a graphical user interface. This chapter describes
install a graphical user interface. This chapter describes
how to install and configure <application>&xorg;</application>,
which provides the open source X Window System used to provide
a graphical environment. It then describes how to find and
@ -38,11 +38,12 @@
configures the <application>&xorg;</application> and offers
a choice of window managers during installation should
refer to the <ulink
url="http://www.pcbsd.org/">pcbsd.org</ulink> website.</para>
url="http://www.pcbsd.org/">pcbsd.org</ulink>
website.</para>
</note>
<para>For more information on the video hardware that <application>&xorg;</application>
supports, refer to the
<para>For more information on the video hardware that
<application>&xorg;</application> supports, refer to the
<ulink url="http://www.x.org/">x.org</ulink> website.</para>
<para>After reading this chapter, you will know:</para>
@ -54,7 +55,8 @@
</listitem>
<listitem>
<para>How to install and configure <application>&xorg;</application>.</para>
<para>How to install and configure
<application>&xorg;</application>.</para>
</listitem>
<listitem>
@ -63,7 +65,8 @@
</listitem>
<listitem>
<para>How to use &truetype; fonts in <application>&xorg;</application>.</para>
<para>How to use &truetype; fonts in
<application>&xorg;</application>.</para>
</listitem>
<listitem>
@ -254,12 +257,12 @@
<note>
<para>To build <application>&xorg;</application> in its
entirety, be sure to have at least 4&nbsp;GB of free disk space
available.</para>
entirety, be sure to have at least 4&nbsp;GB of free disk
space available.</para>
</note>
<para>Alternatively, <application>&xorg;</application> can be installed directly from packages.
To install the package using
<para>Alternatively, <application>&xorg;</application> can be
installed directly from packages. To install the package using
<application>pkg_add</application>, type:</para>
<screen>&prompt.root; <userinput>pkg_add -r xorg</userinput></screen>
@ -285,99 +288,99 @@
<indexterm><primary>&xorg;</primary></indexterm>
<indexterm><primary><application>&xorg;</application></primary></indexterm>
<para>In most cases, <application>&xorg;</application> is self-configuring. Those with older
or unusual equipment may find it helpful to gather some
hardware information before beginning configuration.</para>
<para>In most cases, <application>&xorg;</application> is
self-configuring. Those with older or unusual equipment may
find it helpful to gather some hardware information before
beginning configuration.</para>
<itemizedlist>
<listitem>
<para>Monitor sync frequencies</para>
</listitem>
<listitem>
<para>Video card chipset</para>
</listitem>
<listitem>
<para>Video card memory</para>
</listitem>
</itemizedlist>
<indexterm>
<primary>horizontal sync frequency</primary>
</indexterm>
<indexterm>
<primary>horizontal scan rate</primary>
<see>horizontal sync frequency</see>
</indexterm>
<indexterm><primary>refresh rate</primary></indexterm>
<indexterm>
<primary>vertical sync frequency</primary>
<see>refresh rate</see>
</indexterm>
<indexterm>
<primary>vertical scan rate</primary>
<see>refresh rate</see>
</indexterm>
<para>Screen resolution and refresh rate are determined by the
monitor's horizontal and vertical sync frequencies. Almost
all monitors support electronic autodetection of these values.
A few monitors do not provide these values, and the
specifications must be determined from the printed manual or
manufacturer web site.</para>
<para>The video card chipset is also autodetected, and used to
select the proper video driver. It is beneficial for the user
to be aware of which chipset is installed for when
autodetection does not provide the desired result.</para>
<para>Video card memory determines the maximum resolution and
color depth which can be displayed.</para>
<sect2>
<title>Caveats</title>
<para>The ability to configure optimal resolution is dependent
upon the video hardware and the support provided by its
driver. At this time, driver support is as follows:</para>
<itemizedlist>
<listitem>
<para>Monitor sync frequencies</para>
<para>NVIDIA: several NVIDIA drivers are available in the
x11 category of the FreeBSD Ports Collection. Install
the driver that matches the model of the NVIDIA
hardware.</para>
</listitem>
<listitem>
<para>Video card chipset</para>
<para>Intel: as of FreeBSD 9.1, 3D acceleration on most
Intel graphics, including IronLake, SandyBridge, and
IvyBridge, is supported. Due to the current KMS
implementation, it is not possible to switch between the
graphical console and a virtual console using
Crtl+Alt+F#.</para>
</listitem>
<listitem>
<para>Video card memory</para>
<para>ATI/Radeon: 3D acceleration will not work on ATI or
Radeon cards until FreeBSD completes its TTM work. These
cards will need to be configured with the 2D driver, and
if that does not work, with the Vesa driver.</para>
</listitem>
<listitem>
<para>Optimus: currently there is no switching support
between the two graphics adapters provided by Optimus.
Optimus implementations vary, so FreeBSD may or may not
be able to successfully load a graphics driver on all
hardware. If you get a blank screen, check if the BIOS
has an option to disable one of the graphics adapters or
to set <quote>discrete</quote> mode.</para>
</listitem>
</itemizedlist>
<indexterm>
<primary>horizontal sync frequency</primary>
</indexterm>
<indexterm>
<primary>horizontal scan rate</primary>
<see>horizontal sync frequency</see>
</indexterm>
<indexterm><primary>refresh rate</primary></indexterm>
<indexterm>
<primary>vertical sync frequency</primary>
<see>refresh rate</see>
</indexterm>
<indexterm>
<primary>vertical scan rate</primary>
<see>refresh rate</see>
</indexterm>
<para>Screen resolution and refresh rate are determined by the
monitor's horizontal and vertical sync frequencies. Almost
all monitors support electronic autodetection of these values.
A few monitors do not provide these values, and the
specifications must be determined from the printed manual
or manufacturer web site.</para>
<para>The video card chipset is also autodetected, and used to
select the proper video driver. It is beneficial for the user
to be aware of which chipset is installed for when
autodetection does not provide the desired result.</para>
<para>Video card memory determines the maximum resolution and
color depth which can be displayed.</para>
<sect2>
<title>Caveats</title>
<para>The ability to configure optimal resolution is dependent
upon the video hardware and the
support provided by its driver.
At this time, driver support is as follows:</para>
<itemizedlist>
<listitem>
<para>NVIDIA: several NVIDIA drivers are available in the
x11 category of the FreeBSD Ports Collection. Install
the driver that matches the model of the NVIDIA
hardware.</para>
</listitem>
<listitem>
<para>Intel: as of FreeBSD 9.1, 3D acceleration on most
Intel graphics, including IronLake, SandyBridge, and
IvyBridge, is supported. Due to the current KMS
implementation, it is not possible to switch between the
graphical console and a virtual console using
Crtl+Alt+F#.</para>
</listitem>
<listitem>
<para>ATI/Radeon: 3D acceleration will not work on ATI or
Radeon cards until FreeBSD completes its TTM work. These
cards will need to be configured with the 2D driver, and
if that does not work, with the Vesa driver.</para>
</listitem>
<listitem>
<para>Optimus: currently there is no switching support
between the two graphics adapters provided by Optimus.
Optimus implementations vary, so FreeBSD may or may not
be able to successfully load a graphics driver on all
hardware. If you get a blank screen, check if the BIOS
has an option to disable one of the graphics adapters or
to set <quote>discrete</quote> mode.</para>
</listitem>
</itemizedlist>
</sect2>
</sect2>
<sect2>
<title>Configuring <application>&xorg;</application></title>
@ -386,16 +389,16 @@
<acronym>HAL</acronym> to autodetect keyboards and mice. The
<filename role="package">sysutils/hal</filename> and
<filename role="package">devel/dbus</filename> ports are
automatically installed as dependencies of
<filename role="package">x11/xorg</filename>, but must be
enabled by adding the following entries to
automatically installed as dependencies of <filename
role="package">x11/xorg</filename>, but must be enabled by
adding the following entries to
<filename>/etc/rc.conf</filename>:</para>
<programlisting>hald_enable="YES"
dbus_enable="YES"</programlisting>
<para>Start these services
before configuring <application>&xorg;</application>:</para>
<para>Start these services before configuring
<application>&xorg;</application>:</para>
<screen>&prompt.root; <userinput>service hald start</userinput>
&prompt.root; <userinput>service dbus start</userinput></screen>
@ -407,11 +410,10 @@ dbus_enable="YES"</programlisting>
<screen>&prompt.root; <userinput>Xorg -configure</userinput></screen>
<para>This will generate a file named
<filename>/root/xorg.conf.new</filename> which attempts
to load the proper drivers for the
detected hardware. Next, test that the automatically generated
configuration file works with the graphics hardware by
typing:</para>
<filename>/root/xorg.conf.new</filename> which attempts to
load the proper drivers for the detected hardware. Next,
test that the automatically generated configuration file
works with the graphics hardware by typing:</para>
<screen>&prompt.root; <userinput>Xorg -config xorg.conf.new -retro</userinput></screen>
@ -470,22 +472,21 @@ dbus_enable="YES"</programlisting>
<programlisting>Option "DontZap" "off"</programlisting>
</note>
<para>If the test is unsuccessful, skip ahead to <xref
linkend="x11-understanding"/>. Once the test is successful,
copy the configuration file to
<filename>/etc/X11/xorg.conf</filename>:</para>
<para>If the test is unsuccessful, skip ahead to <xref
linkend="x11-understanding"/>. Once the test is successful,
copy the configuration file to
<filename>/etc/X11/xorg.conf</filename>:</para>
<screen>&prompt.root; <userinput>cp xorg.conf.new /etc/X11/xorg.conf</userinput></screen>
<note>
<para>Desktop environments like
<application>GNOME</application>,
<application>KDE</application> or
<application>Xfce</application> provide graphical tools
to set parameters such as video resolution.
If the default configuration works, skip to <xref linkend="x11-wm"/>
for examples on how to
install a desktop environment.</para>
to set parameters such as video resolution. If the default
configuration works, skip to <xref linkend="x11-wm"/>
for examples on how to install a desktop environment.</para>
</note>
</sect2>
</sect1>
@ -505,24 +506,26 @@ dbus_enable="YES"</programlisting>
<sect2 id="type1">
<title>Type1 Fonts</title>
<para>The default fonts that ship with <application>&xorg;</application> are less than ideal
for typical desktop publishing applications. Large
presentation fonts show up jagged and unprofessional looking,
and small fonts are almost completely unintelligible.
However, there are several free, high quality Type1
(&postscript;) fonts available which can be readily used with
<application>&xorg;</application>. For instance, the URW font collection
(<filename role="package">x11-fonts/urwfonts</filename>)
includes high quality versions of standard type1 fonts
(<trademark class="registered">Times Roman</trademark>,
<trademark class="registered">Helvetica</trademark>,
<trademark class="registered">Palatino</trademark> and
others). The Freefonts collection
(<filename role="package">x11-fonts/freefonts</filename>)
includes many more fonts, but most of them are intended for
use in graphics software such as the
<application>Gimp</application>, and are not complete enough
to serve as screen fonts. In addition, <application>&xorg;</application> can be configured
<para>The default fonts that ship with
<application>&xorg;</application> are less than ideal for
typical desktop publishing applications. Large presentation
fonts show up jagged and unprofessional looking, and small
fonts are almost completely unintelligible. However, there
are several free, high quality Type1 (&postscript;) fonts
available which can be readily used with
<application>&xorg;</application>. For instance, the URW
font collection (<filename
role="package">x11-fonts/urwfonts</filename>) includes high
quality versions of standard type1 fonts (<trademark
class="registered">Times Roman</trademark>, <trademark
class="registered">Helvetica</trademark>, <trademark
class="registered">Palatino</trademark> and others). The
Freefonts collection (<filename
role="package">x11-fonts/freefonts</filename>) includes
many more fonts, but most of them are intended for use in
graphics software such as the <application>Gimp</application>,
and are not complete enough to serve as screen fonts. In
addition, <application>&xorg;</application> can be configured
to use &truetype; fonts with a minimum of effort. For more
details on this, see the &man.X.7; manual page or the
<link linkend="truetype">section on &truetype;
@ -587,20 +590,21 @@ dbus_enable="YES"</programlisting>
copy all of the &truetype; fonts into this directory. Keep in
mind that &truetype; fonts cannot be directly taken from a
&macintosh;; they must be in &unix;/&ms-dos;/&windows; format
for use by <application>&xorg;</application>. Once the files have been copied into this
directory, use <application>ttmkfdir</application> to create a
for use by <application>&xorg;</application>. Once the
files have been copied into this directory, use
<application>ttmkfdir</application> to create a
<filename>fonts.dir</filename> file, so that the X font
renderer knows that these new files have been installed.
<command>ttmkfdir</command> is available from the FreeBSD
Ports Collection as
<filename role="package">x11-fonts/ttmkfdir</filename>.</para>
Ports Collection as <filename
role="package">x11-fonts/ttmkfdir</filename>.</para>
<screen>&prompt.root; <userinput>cd /usr/local/lib/X11/fonts/TrueType</userinput>
&prompt.root; <userinput>ttmkfdir -o fonts.dir</userinput></screen>
<para>Now add the &truetype; directory to the font path. This
is just the same as described above for
<link linkend="type1">Type1</link> fonts, that is, use</para>
is just the same as described above for <link
linkend="type1">Type1</link> fonts, that is, use</para>
<screen>&prompt.user; <userinput>xset fp+ /usr/local/lib/X11/fonts/TrueType</userinput>
&prompt.user; <userinput>xset fp rehash</userinput></screen>
@ -637,8 +641,8 @@ dbus_enable="YES"</programlisting>
<secondary>anti-aliased</secondary>
</indexterm>
<para>All fonts in <application>&xorg;</application> that are found in
<filename>/usr/local/lib/X11/fonts/</filename> and
<para>All fonts in <application>&xorg;</application> that are
found in <filename>/usr/local/lib/X11/fonts/</filename> and
<filename>~/.fonts/</filename> are automatically made
available for anti-aliasing to Xft-aware applications. Most
recent applications are Xft-aware, including
@ -1465,19 +1469,19 @@ DisplayManager.requestPort: 0</screen>
</sect2>
</sect1>
<sect1 id="x11-understanding">
<sect1 id="x11-understanding">
<title>Troubleshooting</title>
<title>Troubleshooting</title>
<para>If the mouse does not work, you will need to first
configure it before proceeding. See <xref linkend="mouse"/>
in the &os; install chapter. In recent
<application>Xorg</application> versions,
the <literal>InputDevice</literal> sections in
<filename>xorg.conf</filename> are ignored in favor of the
autodetected devices. To restore the old behavior, add the
following line to the <literal>ServerLayout</literal> or
<literal>ServerFlags</literal> section of this file:</para>
<para>If the mouse does not work, you will need to first
configure it before proceeding. See <xref linkend="mouse"/>
in the &os; install chapter. In recent
<application>Xorg</application> versions, the
<literal>InputDevice</literal> sections in
<filename>xorg.conf</filename> are ignored in favor of the
autodetected devices. To restore the old behavior, add the
following line to the <literal>ServerLayout</literal> or
<literal>ServerFlags</literal> section of this file:</para>
<programlisting>Option "AutoAddDevices" "false"</programlisting>
@ -1534,7 +1538,8 @@ DisplayManager.requestPort: 0</screen>
available.</para>
</note>
<indexterm><primary><application>&xorg;</application> tuning</primary></indexterm>
<indexterm><primary><application>&xorg;</application>
tuning</primary></indexterm>
<para>The <filename>xorg.conf.new</filename> configuration file
may now be tuned to taste. Open the file in a text editor
@ -1603,8 +1608,10 @@ EndSection</programlisting>
<note>
<para>One of the tools available to assist you during
troubleshooting process are the <application>&xorg;</application> log files, which contain
information on each device that the <application>&xorg;</application> server attaches to.
troubleshooting process are the
<application>&xorg;</application> log files, which contain
information on each device that the
<application>&xorg;</application> server attaches to.
<application>&xorg;</application> log file names are in the
format of <filename>/var/log/Xorg.0.log</filename>. The
exact name of the log can vary from
@ -1619,9 +1626,10 @@ EndSection</programlisting>
<screen>&prompt.root; <userinput>cp xorg.conf.new /etc/X11/xorg.conf</userinput></screen>
<para>The <application>&xorg;</application> configuration process is now complete.
<application>&xorg;</application> may be now started with the
&man.startx.1; utility. The <application>&xorg;</application> server may also be started
<para>The <application>&xorg;</application> configuration
process is now complete. <application>&xorg;</application>
may be now started with the &man.startx.1; utility. The
<application>&xorg;</application> server may also be started
with the use of &man.xdm.1;.</para>
<sect2>
@ -1634,8 +1642,9 @@ EndSection</programlisting>
<para>Configuration with &intel; i810 integrated chipsets
requires the <devicename>agpgart</devicename> AGP
programming interface for <application>&xorg;</application> to drive the card. See the
&man.agp.4; driver manual page for more information.</para>
programming interface for <application>&xorg;</application>
to drive the card. See the &man.agp.4; driver manual page
for more information.</para>
<para>This will allow configuration of the hardware as any
other graphics board. Note on systems without the
@ -1741,6 +1750,6 @@ EndSection</programlisting>
<para>Now having completed these simple editing steps, X
should start on your new widescreen monitor.</para>
</sect2>
</sect1>
</chapter>
</sect2>
</sect1>
</chapter>