Whitespace cleanup.
Translators can ignore.
This commit is contained in:
Benedict Reuschling
parent
5a242b4180
commit
9fd2f7e563
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=46816
1 changed files with 241 additions and 245 deletions
|
|
@ -30,18 +30,17 @@
|
|||
|
||||
<para>An installation of &os; using
|
||||
<application>bsdinstall</application> does not automatically
|
||||
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
|
||||
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
|
||||
install a desktop environment or window manager.</para>
|
||||
|
||||
<note>
|
||||
<para>Users who prefer an installation method that automatically
|
||||
configures the <application>&xorg;</application> and offers
|
||||
a choice of window managers during installation should
|
||||
refer to the <link
|
||||
xlink:href="http://www.pcbsd.org/">pcbsd.org</link>
|
||||
configures the <application>&xorg;</application> and offers a
|
||||
choice of window managers during installation should refer to
|
||||
the <link xlink:href="http://www.pcbsd.org/">pcbsd.org</link>
|
||||
website.</para>
|
||||
</note>
|
||||
|
||||
|
|
@ -103,17 +102,17 @@
|
|||
<listitem>
|
||||
<para>X was designed from the beginning to be
|
||||
network-centric, and adopts a <quote>client-server</quote>
|
||||
model. In this model, the <quote>X server</quote> runs
|
||||
on the computer that has the keyboard, monitor, and mouse
|
||||
attached. The server's responsibility includes tasks
|
||||
such as managing the display, handling input from the
|
||||
keyboard and mouse, and handling input or output from
|
||||
other devices such as a tablet or a video projector.
|
||||
This confuses some people, because the X terminology is
|
||||
exactly backward to what they expect. They expect the
|
||||
<quote>X server</quote> to be the big powerful machine
|
||||
down the hall, and the <quote>X client</quote> to be the
|
||||
machine on their desk.</para>
|
||||
model. In this model, the <quote>X server</quote> runs on
|
||||
the computer that has the keyboard, monitor, and mouse
|
||||
attached. The server's responsibility includes tasks such
|
||||
as managing the display, handling input from the keyboard
|
||||
and mouse, and handling input or output from other devices
|
||||
such as a tablet or a video projector. This confuses some
|
||||
people, because the X terminology is exactly backward to
|
||||
what they expect. They expect the <quote>X server</quote>
|
||||
to be the big powerful machine down the hall, and the
|
||||
<quote>X client</quote> to be the machine on their
|
||||
desk.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
|
@ -133,10 +132,9 @@
|
|||
<para>In a home or small office environment, the X server
|
||||
and the X clients commonly run on the same computer. It
|
||||
is also possible to run the X server on a less powerful
|
||||
computer and to run the X applications on a more
|
||||
powerful system. In this scenario, the communication
|
||||
between the X client and server takes place over the
|
||||
network.</para>
|
||||
computer and to run the X applications on a more powerful
|
||||
system. In this scenario, the communication between the X
|
||||
client and server takes place over the network.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
|
@ -147,23 +145,23 @@
|
|||
<para>X does not dictate what windows should look like on
|
||||
screen, how to move them around with the mouse, which
|
||||
keystrokes should be used to move between windows, what
|
||||
the title bars on each window should look like, whether
|
||||
or not they have close buttons on them, and so on.
|
||||
Instead, X delegates this responsibility to a separate
|
||||
window manager application. There are <link
|
||||
the title bars on each window should look like, whether or
|
||||
not they have close buttons on them, and so on. Instead,
|
||||
X delegates this responsibility to a separate window
|
||||
manager application. There are <link
|
||||
xlink:href="http://xwinman.org/">dozens of window
|
||||
managers</link> available. Each window manager
|
||||
provides a different look and feel: some support virtual
|
||||
desktops, some allow customized keystrokes to manage the
|
||||
desktop, some have a <quote>Start</quote> button, and
|
||||
some are themeable, allowing a complete change of the
|
||||
desktop's look-and-feel. Window managers are available
|
||||
in the <filename>x11-wm</filename> category of the
|
||||
Ports Collection.</para>
|
||||
managers</link> available. Each window manager provides
|
||||
a different look and feel: some support virtual desktops,
|
||||
some allow customized keystrokes to manage the desktop,
|
||||
some have a <quote>Start</quote> button, and some are
|
||||
themeable, allowing a complete change of the desktop's
|
||||
look-and-feel. Window managers are available in the
|
||||
<filename>x11-wm</filename> category of the Ports
|
||||
Collection.</para>
|
||||
|
||||
<para>Each window manager uses a different configuration
|
||||
mechanism. Some expect configuration file written by
|
||||
hand while others provide graphical tools for most
|
||||
mechanism. Some expect configuration file written by hand
|
||||
while others provide graphical tools for most
|
||||
configuration tasks.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
|
@ -193,26 +191,26 @@
|
|||
<para>One focus policy is called
|
||||
<quote>click-to-focus</quote>. In this model, a window
|
||||
becomes active upon receiving a mouse click. In the
|
||||
<quote>focus-follows-mouse</quote> policy, the window
|
||||
that is under the mouse pointer has focus and the focus
|
||||
is changed by pointing at another window. If the mouse
|
||||
is over the root window, then this window is focused.
|
||||
In the <quote>sloppy-focus</quote> model, if the mouse
|
||||
is moved over the root window, the most recently used
|
||||
window still has the focus. With sloppy-focus, focus
|
||||
is only changed when the cursor enters a new window, and
|
||||
not when exiting the current window. In the
|
||||
<quote>click-to-focus</quote> policy, the active window
|
||||
is selected by mouse click. The window may then be
|
||||
raised and appear in front of all other windows. All
|
||||
keystrokes will now be directed to this window, even if
|
||||
the cursor is moved to another window.</para>
|
||||
<quote>focus-follows-mouse</quote> policy, the window that
|
||||
is under the mouse pointer has focus and the focus is
|
||||
changed by pointing at another window. If the mouse is
|
||||
over the root window, then this window is focused. In the
|
||||
<quote>sloppy-focus</quote> model, if the mouse is moved
|
||||
over the root window, the most recently used window still
|
||||
has the focus. With sloppy-focus, focus is only changed
|
||||
when the cursor enters a new window, and not when exiting
|
||||
the current window. In the <quote>click-to-focus</quote>
|
||||
policy, the active window is selected by mouse click. The
|
||||
window may then be raised and appear in front of all other
|
||||
windows. All keystrokes will now be directed to this
|
||||
window, even if the cursor is moved to another
|
||||
window.</para>
|
||||
|
||||
<para>Different window managers support different focus
|
||||
models. All of them support click-to-focus, and the
|
||||
majority of them also support other policies. Consult
|
||||
the documentation for the window manager to determine
|
||||
which focus models are available.</para>
|
||||
majority of them also support other policies. Consult the
|
||||
documentation for the window manager to determine which
|
||||
focus models are available.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
|
@ -229,8 +227,8 @@
|
|||
<application>KDE</application>, and GTK+, used by
|
||||
<application>GNOME</application>. As a result,
|
||||
applications will have a different look and feel,
|
||||
depending upon which widget toolkit was used to create
|
||||
the application.</para>
|
||||
depending upon which widget toolkit was used to create the
|
||||
application.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
|
@ -250,8 +248,8 @@
|
|||
section install the complete <application>&xorg;</application>
|
||||
distribution.</para>
|
||||
|
||||
<para>To build and install <application>&xorg;</application>
|
||||
from the Ports Collection:</para>
|
||||
<para>To build and install <application>&xorg;</application> from
|
||||
the Ports Collection:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /usr/ports/x11/xorg</userinput>
|
||||
&prompt.root; <userinput>make install clean</userinput></screen>
|
||||
|
|
@ -312,8 +310,8 @@ dbus_enable="YES"</programlisting>
|
|||
|
||||
<para>Test the system by moving the mouse and typing text into
|
||||
the windows. If both mouse and keyboard work as expected,
|
||||
see <xref linkend="x11-wm"/> and
|
||||
<xref linkend="x-xdm"/>.</para>
|
||||
see <xref linkend="x11-wm"/> and <xref
|
||||
linkend="x-xdm"/>.</para>
|
||||
|
||||
<para>If the mouse or keyboard do not work, continue with
|
||||
<xref linkend="x-config"/>.</para>
|
||||
|
|
@ -338,9 +336,9 @@ dbus_enable="YES"</programlisting>
|
|||
<indexterm><primary>&xorg;</primary></indexterm>
|
||||
<indexterm><primary><application>&xorg;</application></primary></indexterm>
|
||||
|
||||
<para>Those with older or unusual equipment may
|
||||
find it helpful to gather some hardware information before
|
||||
beginning configuration.</para>
|
||||
<para>Those with older or unusual equipment may find it helpful to
|
||||
gather some hardware information before beginning
|
||||
configuration.</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
|
|
@ -374,16 +372,16 @@ dbus_enable="YES"</programlisting>
|
|||
</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>
|
||||
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>
|
||||
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>
|
||||
|
|
@ -455,29 +453,23 @@ dbus_enable="YES"</programlisting>
|
|||
|
||||
<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>
|
||||
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>
|
||||
|
||||
<para>If a black and grey grid and an X mouse cursor appear,
|
||||
the configuration was successful. To exit the test, switch
|
||||
to the virtual console used to start it by pressing
|
||||
<keycombo action="simul">
|
||||
<keycap>Ctrl</keycap>
|
||||
<keycap>Alt</keycap>
|
||||
<keycap>F<replaceable>n</replaceable></keycap>
|
||||
</keycombo> (<keycap>F1</keycap> for the first virtual
|
||||
console) and press
|
||||
<keycombo action="simul">
|
||||
<keycap>Ctrl</keycap>
|
||||
<keycap>C</keycap>
|
||||
</keycombo>.</para>
|
||||
<para>If a black and grey grid and an X mouse cursor appear, the
|
||||
configuration was successful. To exit the test, switch to the
|
||||
virtual console used to start it by pressing <keycombo
|
||||
action="simul"> <keycap>Ctrl</keycap> <keycap>Alt</keycap>
|
||||
<keycap>F<replaceable>n</replaceable></keycap> </keycombo>
|
||||
(<keycap>F1</keycap> for the first virtual console) and press
|
||||
<keycombo action="simul"> <keycap>Ctrl</keycap>
|
||||
<keycap>C</keycap> </keycombo>.</para>
|
||||
|
||||
<note>
|
||||
<para>The
|
||||
<keycombo action="simul">
|
||||
<para>The <keycombo action="simul">
|
||||
<keycap>Ctrl</keycap>
|
||||
<keycap>Alt</keycap>
|
||||
<keycap>Backspace</keycap>
|
||||
|
|
@ -526,10 +518,10 @@ dbus_enable="YES"</programlisting>
|
|||
<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>
|
||||
<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>
|
||||
</note>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
|
@ -558,24 +550,24 @@ dbus_enable="YES"</programlisting>
|
|||
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 (<package>x11-fonts/urwfonts</package>)
|
||||
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
|
||||
(<package>x11-fonts/freefonts</package>) 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>. For instance, the URW font
|
||||
collection (<package>x11-fonts/urwfonts</package>) 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 (<package>x11-fonts/freefonts</package>)
|
||||
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 <xref
|
||||
linkend="truetype"/>.</para>
|
||||
|
||||
<para>To install the above Type1 font collections from the
|
||||
Ports Collection, run the following commands:</para>
|
||||
<para>To install the above Type1 font collections from the Ports
|
||||
Collection, run the following commands:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /usr/ports/x11-fonts/urwfonts</userinput>
|
||||
&prompt.root; <userinput>make install clean</userinput></screen>
|
||||
|
|
@ -634,8 +626,8 @@ dbus_enable="YES"</programlisting>
|
|||
format 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>, so that the X font
|
||||
renderer knows that these new files have been installed.
|
||||
<filename>fonts.dir</filename>, 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
|
||||
<package>x11-fonts/ttmkfdir</package>.</para>
|
||||
|
|
@ -654,12 +646,12 @@ dbus_enable="YES"</programlisting>
|
|||
<filename>xorg.conf</filename>.</para>
|
||||
|
||||
<para>Now <application>Gimp</application>,
|
||||
<application>OpenOffice</application>, and all of the
|
||||
other X applications should now recognize the installed
|
||||
&truetype; fonts. Extremely small fonts (as with text in a
|
||||
high resolution display on a web page) and extremely large
|
||||
fonts (within <application>&staroffice;</application>) will
|
||||
look much better now.</para>
|
||||
<application>OpenOffice</application>, and all of the other X
|
||||
applications should now recognize the installed &truetype;
|
||||
fonts. Extremely small fonts (as with text in a high
|
||||
resolution display on a web page) and extremely large fonts
|
||||
(within <application>&staroffice;</application>) will look
|
||||
much better now.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 xml:id="antialias">
|
||||
|
|
@ -852,13 +844,13 @@ dbus_enable="YES"</programlisting>
|
|||
|
||||
<sect1 xml:id="x-xdm">
|
||||
<info>
|
||||
<title>The X Display Manager</title>
|
||||
<title>The X Display Manager</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
<personname>
|
||||
<firstname>Seth</firstname>
|
||||
<surname>Kingsley</surname>
|
||||
<personname>
|
||||
<firstname>Seth</firstname>
|
||||
<surname>Kingsley</surname>
|
||||
</personname>
|
||||
<contrib>Contributed by </contrib>
|
||||
</author>
|
||||
|
|
@ -873,7 +865,7 @@ dbus_enable="YES"</programlisting>
|
|||
to connect to and for entering authorization information such as
|
||||
a login and password combination.</para>
|
||||
|
||||
<para> This section demonstrates how to configure the X Display
|
||||
<para>This section demonstrates how to configure the X Display
|
||||
Manager on &os;. Some desktop environments provide their own
|
||||
graphical login manager. Refer to <xref
|
||||
linkend="x11-wm-gnome"/> for instructions on how to configure
|
||||
|
|
@ -982,8 +974,8 @@ dbus_enable="YES"</programlisting>
|
|||
If a display that <application>XDM</application> is
|
||||
trying to start hangs, look at this file for error
|
||||
messages. These messages are also written to the
|
||||
user's <filename>~/.xsession-errors</filename> on
|
||||
a per-session basis.</entry>
|
||||
user's <filename>~/.xsession-errors</filename> on a
|
||||
per-session basis.</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
|
|
@ -1023,13 +1015,13 @@ DisplayManager.requestPort: 0</screen>
|
|||
|
||||
<sect1 xml:id="x11-wm">
|
||||
<info>
|
||||
<title>Desktop Environments</title>
|
||||
<title>Desktop Environments</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
<personname>
|
||||
<firstname>Valentino</firstname>
|
||||
<surname>Vaschetto</surname>
|
||||
<personname>
|
||||
<firstname>Valentino</firstname>
|
||||
<surname>Vaschetto</surname>
|
||||
</personname>
|
||||
<contrib>Contributed by </contrib>
|
||||
<!-- in June 2001 -->
|
||||
|
|
@ -1040,9 +1032,9 @@ DisplayManager.requestPort: 0</screen>
|
|||
<para>This section describes how to install three popular desktop
|
||||
environments on a &os; system. A desktop environment can range
|
||||
from a simple window manager to a complete suite of desktop
|
||||
applications. Over a hundred desktop environments are
|
||||
available in the <filename>x11-wm</filename> category of the
|
||||
Ports Collection.</para>
|
||||
applications. Over a hundred desktop environments are available
|
||||
in the <filename>x11-wm</filename> category of the Ports
|
||||
Collection.</para>
|
||||
|
||||
<sect2 xml:id="x11-wm-gnome">
|
||||
<title>GNOME</title>
|
||||
|
|
@ -1055,7 +1047,7 @@ DisplayManager.requestPort: 0</screen>
|
|||
for applications to cooperate and be consistent with each
|
||||
other. More information regarding
|
||||
<application>GNOME</application> on &os; can be found at <link
|
||||
xlink:href="http://www.FreeBSD.org/gnome">http://www.FreeBSD.org/gnome</link>.
|
||||
xlink:href="http://www.FreeBSD.org/gnome">http://www.FreeBSD.org/gnome</link>.
|
||||
That web site contains additional documentation about
|
||||
installing, configuring, and managing
|
||||
<application>GNOME</application> on &os;.</para>
|
||||
|
|
@ -1075,10 +1067,9 @@ DisplayManager.requestPort: 0</screen>
|
|||
&prompt.root; <userinput>make install clean</userinput></screen>
|
||||
|
||||
<para>For proper operation, <application>GNOME</application>
|
||||
requires <filename>/proc</filename> to be
|
||||
mounted. Add this line to <filename>/etc/fstab</filename> to
|
||||
mount this file system automatically during system
|
||||
startup:</para>
|
||||
requires <filename>/proc</filename> to be mounted. Add this
|
||||
line to <filename>/etc/fstab</filename> to mount this file
|
||||
system automatically during system startup:</para>
|
||||
|
||||
<programlisting>proc /proc procfs rw 0 0</programlisting>
|
||||
|
||||
|
|
@ -1095,8 +1086,7 @@ DisplayManager.requestPort: 0</screen>
|
|||
|
||||
<para>It is often desirable to also start all
|
||||
<application>GNOME</application> services. To achieve this,
|
||||
add a second line to
|
||||
<filename>/etc/rc.conf</filename>:</para>
|
||||
add a second line to <filename>/etc/rc.conf</filename>:</para>
|
||||
|
||||
<programlisting>gnome_enable="YES"</programlisting>
|
||||
|
||||
|
|
@ -1159,9 +1149,9 @@ DisplayManager.requestPort: 0</screen>
|
|||
</indexterm>
|
||||
|
||||
<para><application>KDE</application> requires
|
||||
<filename>/proc</filename> to be mounted. Add
|
||||
this line to <filename>/etc/fstab</filename> to mount this
|
||||
file system automatically during system startup:</para>
|
||||
<filename>/proc</filename> to be mounted. Add this line to
|
||||
<filename>/etc/fstab</filename> to mount this file system
|
||||
automatically during system startup:</para>
|
||||
|
||||
<programlisting>proc /proc procfs rw 0 0</programlisting>
|
||||
|
||||
|
|
@ -1245,50 +1235,50 @@ DisplayManager.requestPort: 0</screen>
|
|||
<para>One way to increase the pleasantness of using a desktop
|
||||
computer is by having nice 3D effects.</para>
|
||||
|
||||
<para>Installing the <application>Compiz Fusion</application>
|
||||
<para>Installing the <application>Compiz Fusion</application>
|
||||
package is easy, but configuring it requires a few steps that
|
||||
are not described in the port's documentation.</para>
|
||||
|
||||
<sect2 xml:id="x-compiz-video-card">
|
||||
<title>Setting up the &os; nVidia driver</title>
|
||||
|
||||
<para>Desktop effects can cause quite a load on the graphics card.
|
||||
For an an nVidia-based graphics card, the proprietary driver
|
||||
is required for good performance. Users of other graphics
|
||||
cards can skip this section and continue with the
|
||||
<para>Desktop effects can cause quite a load on the graphics
|
||||
card. For an an nVidia-based graphics card, the proprietary
|
||||
driver is required for good performance. Users of other
|
||||
graphics cards can skip this section and continue with the
|
||||
<filename>xorg.conf</filename> configuration.</para>
|
||||
|
||||
<para>
|
||||
To determine which nVidia driver is needed see the <link xlink:href="&url.books.faq;/x.html#idp59950544">FAQ question
|
||||
on the subject</link>.
|
||||
</para>
|
||||
<para>To determine which nVidia driver is needed see the <link
|
||||
xlink:href="&url.books.faq;/x.html#idp59950544">FAQ question
|
||||
on the subject</link>.</para>
|
||||
|
||||
<para>Having determined the correct driver to use for your card,
|
||||
installation is as simple as installing any other package.</para>
|
||||
installation is as simple as installing any other
|
||||
package.</para>
|
||||
|
||||
<para>For example, to install the latest driver:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>pkg install x11/nvidia-driver</userinput></screen>
|
||||
|
||||
<para>The driver will create a kernel module, which needs to be loaded
|
||||
at system startup. Add the following line to
|
||||
<para>The driver will create a kernel module, which needs to be
|
||||
loaded at system startup. Add the following line to
|
||||
<filename>/boot/loader.conf</filename>:</para>
|
||||
|
||||
<programlisting>nvidia_load="YES"</programlisting>
|
||||
|
||||
<note>
|
||||
<para>To immediately load the kernel module into the
|
||||
running kernel by issuing a command like
|
||||
<command>kldload nvidia</command>, however it has been noted that
|
||||
the some versions of <application>&xorg;</application> will not
|
||||
function properly if the driver is not loaded at boot time. After
|
||||
editing <filename>/boot/loader.conf</filename>, a reboot is
|
||||
recommended.</para>
|
||||
<para>To immediately load the kernel module into the running
|
||||
kernel by issuing a command like <command>kldload
|
||||
nvidia</command>, however it has been noted that the some
|
||||
versions of <application>&xorg;</application> will not
|
||||
function properly if the driver is not loaded at boot time.
|
||||
After editing <filename>/boot/loader.conf</filename>, a
|
||||
reboot is recommended.</para>
|
||||
</note>
|
||||
|
||||
<para>With the kernel module loaded, you normally only need to change
|
||||
a single line in your <filename>xorg.conf</filename> file to enable
|
||||
the proprietary driver:</para>
|
||||
<para>With the kernel module loaded, you normally only need to
|
||||
change a single line in your <filename>xorg.conf</filename>
|
||||
file to enable the proprietary driver:</para>
|
||||
|
||||
<para>Find the following line in
|
||||
<filename>/etc/X11/xorg.conf</filename>:</para>
|
||||
|
|
@ -1300,7 +1290,7 @@ DisplayManager.requestPort: 0</screen>
|
|||
<programlisting>Driver "nvidia"</programlisting>
|
||||
|
||||
<para>Start the GUI as usual, and you should be greeted by the
|
||||
nVidia splash. Everything should work as usual.</para>
|
||||
nVidia splash. Everything should work as usual.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 xml:id="xorg-configuration">
|
||||
|
|
@ -1310,14 +1300,15 @@ DisplayManager.requestPort: 0</screen>
|
|||
<filename>/etc/X11/xorg.conf</filename> needs to be
|
||||
modified:</para>
|
||||
|
||||
<para>Add the following section to enable composite effects:</para>
|
||||
<para>Add the following section to enable composite
|
||||
effects:</para>
|
||||
|
||||
<programlisting>Section "Extensions"
|
||||
Option "Composite" "Enable"
|
||||
EndSection</programlisting>
|
||||
|
||||
<para>Locate the <quote>Screen</quote> section which should look similar
|
||||
to the one below:</para>
|
||||
<para>Locate the <quote>Screen</quote> section which should look
|
||||
similar to the one below:</para>
|
||||
|
||||
<programlisting>Section "Screen"
|
||||
Identifier "Screen0"
|
||||
|
|
@ -1325,25 +1316,25 @@ DisplayManager.requestPort: 0</screen>
|
|||
Monitor "Monitor0"
|
||||
...</programlisting>
|
||||
|
||||
<para>and add the following two lines (after <quote>Monitor</quote> will
|
||||
do):</para>
|
||||
<para>and add the following two lines (after
|
||||
<quote>Monitor</quote> will do):</para>
|
||||
|
||||
<programlisting>DefaultDepth 24
|
||||
Option "AddARGBGLXVisuals" "True"</programlisting>
|
||||
|
||||
<para>Locate the <quote>Subsection</quote> that refers to the
|
||||
screen resolution that you wish to use. For example, if you wish to
|
||||
use 1280x1024, locate the section that follows. If the desired
|
||||
resolution does not appear in any subsection, you may add the relevant
|
||||
entry by hand:</para>
|
||||
screen resolution that you wish to use. For example, if you
|
||||
wish to use 1280x1024, locate the section that follows. If
|
||||
the desired resolution does not appear in any subsection, you
|
||||
may add the relevant entry by hand:</para>
|
||||
|
||||
<programlisting>SubSection "Display"
|
||||
Viewport 0 0
|
||||
Modes "1280x1024"
|
||||
EndSubSection</programlisting>
|
||||
|
||||
<para>A color depth of 24 bits is needed for desktop composition,
|
||||
change the above subsection to:</para>
|
||||
<para>A color depth of 24 bits is needed for desktop
|
||||
composition, change the above subsection to:</para>
|
||||
|
||||
<programlisting>SubSection "Display"
|
||||
Viewport 0 0
|
||||
|
|
@ -1352,8 +1343,8 @@ DisplayManager.requestPort: 0</screen>
|
|||
EndSubSection</programlisting>
|
||||
|
||||
<para>Finally, confirm that the <quote>glx</quote> and
|
||||
<quote>extmod</quote> modules are loaded in the <quote>Module</quote>
|
||||
section:</para>
|
||||
<quote>extmod</quote> modules are loaded in the
|
||||
<quote>Module</quote> section:</para>
|
||||
|
||||
<programlisting>Section "Module"
|
||||
Load "extmod"
|
||||
|
|
@ -1364,7 +1355,7 @@ DisplayManager.requestPort: 0</screen>
|
|||
<package>x11/nvidia-xconfig</package> by running (as
|
||||
root):</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>nvidia-xconfig --add-argb-glx-visuals</userinput>
|
||||
<screen>&prompt.root; <userinput>nvidia-xconfig --add-argb-glx-visuals</userinput>
|
||||
&prompt.root; <userinput>nvidia-xconfig --composite</userinput>
|
||||
&prompt.root; <userinput>nvidia-xconfig --depth=24</userinput></screen>
|
||||
</sect2>
|
||||
|
|
@ -1377,69 +1368,70 @@ DisplayManager.requestPort: 0</screen>
|
|||
|
||||
<screen>&prompt.root; <userinput>pkg install x11-wm/compiz-fusion</userinput></screen>
|
||||
|
||||
<para>When the installation is finished, start your graphic desktop and
|
||||
at a terminal, enter the following commands (as a normal user):</para>
|
||||
<para>When the installation is finished, start your graphic
|
||||
desktop and at a terminal, enter the following commands (as a
|
||||
normal user):</para>
|
||||
|
||||
<screen>&prompt.user; <userinput>compiz --replace --sm-disable --ignore-desktop-hints ccp &</userinput>
|
||||
&prompt.user; <userinput>emerald --replace &</userinput></screen>
|
||||
|
||||
<para>Your screen will flicker for a few seconds, as your window manager
|
||||
(e.g. <application>Metacity</application> if you are using
|
||||
<application>GNOME</application>) is replaced by
|
||||
<para>Your screen will flicker for a few seconds, as your window
|
||||
manager (e.g. <application>Metacity</application> if you are
|
||||
using <application>GNOME</application>) is replaced by
|
||||
<application>Compiz Fusion</application>.
|
||||
<application>Emerald</application> takes care of the window
|
||||
decorations (i.e. close, minimize, maximize buttons, title bars
|
||||
and so on).</para>
|
||||
decorations (i.e. close, minimize, maximize buttons, title
|
||||
bars and so on).</para>
|
||||
|
||||
<para>You may convert this to a trivial script and have it run at
|
||||
startup automatically (e.g. by adding to <quote>Sessions</quote> in
|
||||
a <application>GNOME</application> desktop):</para>
|
||||
<para>You may convert this to a trivial script and have it run
|
||||
at startup automatically (e.g. by adding to
|
||||
<quote>Sessions</quote> in a <application>GNOME</application>
|
||||
desktop):</para>
|
||||
|
||||
<programlisting>#! /bin/sh
|
||||
compiz --replace --sm-disable --ignore-desktop-hints ccp &
|
||||
emerald --replace &</programlisting>
|
||||
|
||||
<para>Save this in your home directory as, for example,
|
||||
<filename>start-compiz</filename> and make it executable:</para>
|
||||
<filename>start-compiz</filename> and make it
|
||||
executable:</para>
|
||||
|
||||
<screen>&prompt.user; <userinput>chmod +x ~/start-compiz</userinput></screen>
|
||||
|
||||
<para>Then use the GUI to add it to
|
||||
<guimenuitem>Startup Programs</guimenuitem>
|
||||
(located in <guimenuitem>System</guimenuitem>,
|
||||
<para>Then use the GUI to add it to <guimenuitem>Startup
|
||||
Programs</guimenuitem> (located in
|
||||
<guimenuitem>System</guimenuitem>,
|
||||
<guimenuitem>Preferences</guimenuitem>,
|
||||
<guimenuitem>Sessions</guimenuitem> on a
|
||||
<application>GNOME</application> desktop).</para>
|
||||
|
||||
<para>To actually select all the desired effects and their settings,
|
||||
execute (again as a normal user) the
|
||||
<para>To actually select all the desired effects and their
|
||||
settings, execute (again as a normal user) the
|
||||
<application>Compiz Config Settings Manager</application>:</para>
|
||||
|
||||
<screen>&prompt.user; <userinput>ccsm</userinput></screen>
|
||||
|
||||
<note>
|
||||
<para>In <application>GNOME</application>, this can also be found in
|
||||
the <guimenuitem>System</guimenuitem>,
|
||||
<para>In <application>GNOME</application>, this can also be
|
||||
found in the <guimenuitem>System</guimenuitem>,
|
||||
<guimenuitem>Preferences</guimenuitem> menu.</para>
|
||||
</note>
|
||||
|
||||
<para>If you have selected <quote>gconf support</quote> during the build,
|
||||
you will also be able to view these settings using
|
||||
<command>gconf-editor</command> under <literal>apps/compiz</literal>.
|
||||
</para>
|
||||
<para>If you have selected <quote>gconf support</quote> during
|
||||
the build, you will also be able to view these settings using
|
||||
<command>gconf-editor</command> under
|
||||
<literal>apps/compiz</literal>.</para>
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 xml:id="x11-understanding">
|
||||
|
||||
<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
|
||||
<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
|
||||
|
|
@ -1493,8 +1485,7 @@ DisplayManager.requestPort: 0</screen>
|
|||
|
||||
<screen>&prompt.user; <userinput>setxkbmap -model pc102 -layout fr</userinput></screen>
|
||||
|
||||
<para>
|
||||
<filename>/usr/local/share/X11/xkb/rules/base.lst</filename>
|
||||
<para><filename>/usr/local/share/X11/xkb/rules/base.lst</filename>
|
||||
lists the various keyboard, layouts and options
|
||||
available.</para>
|
||||
</note>
|
||||
|
|
@ -1518,8 +1509,8 @@ DisplayManager.requestPort: 0</screen>
|
|||
VertRefresh 48-120
|
||||
EndSection</programlisting>
|
||||
|
||||
<para>Most monitors support sync frequency autodetection,
|
||||
making manual entry of these values unnecessary. For the few
|
||||
<para>Most monitors support sync frequency autodetection, making
|
||||
manual entry of these values unnecessary. For the few
|
||||
monitors that do not support autodetection, avoid potential
|
||||
damage by only entering values provided by the
|
||||
manufacturer.</para>
|
||||
|
|
@ -1536,10 +1527,10 @@ EndSection</programlisting>
|
|||
<primary><filename>xorg.conf</filename></primary>
|
||||
</indexterm>
|
||||
|
||||
<para>While the <filename>xorg.conf.new</filename>
|
||||
configuration file is still open in an editor, select the
|
||||
default resolution and color depth desired. This is defined
|
||||
in the <literal>"Screen"</literal> section:</para>
|
||||
<para>While the <filename>xorg.conf.new</filename> configuration
|
||||
file is still open in an editor, select the default resolution
|
||||
and color depth desired. This is defined in the
|
||||
<literal>"Screen"</literal> section:</para>
|
||||
|
||||
<programlisting>Section "Screen"
|
||||
Identifier "Screen0"
|
||||
|
|
@ -1602,10 +1593,10 @@ EndSection</programlisting>
|
|||
</indexterm>
|
||||
|
||||
<para>Configuration with &intel; i810 integrated chipsets
|
||||
requires the <filename>agpgart</filename> AGP
|
||||
programming interface for <application>&xorg;</application>
|
||||
to drive the card. See the &man.agp.4; driver manual page
|
||||
for more information.</para>
|
||||
requires the <filename>agpgart</filename> AGP 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
|
||||
|
|
@ -1713,48 +1704,53 @@ EndSection</programlisting>
|
|||
should start on your new widescreen monitor.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 xml:id="compiz-troubleshooting">
|
||||
<title>Troubleshooting Compiz Fusion</title>
|
||||
<sect2 xml:id="compiz-troubleshooting">
|
||||
<title>Troubleshooting Compiz Fusion</title>
|
||||
|
||||
<qandaset>
|
||||
<qandaentry>
|
||||
<question xml:id="no-decorations">
|
||||
<para>I have installed
|
||||
<application>Compiz Fusion</application>,
|
||||
and after running the commands you mention, my windows are left
|
||||
without title bars and buttons. What is wrong?</para>
|
||||
</question>
|
||||
<qandaset>
|
||||
<qandaentry>
|
||||
<question xml:id="no-decorations">
|
||||
<para>I have installed
|
||||
<application>Compiz Fusion</application>, and
|
||||
after running the commands you mention, my windows are
|
||||
left without title bars and buttons. What is
|
||||
wrong?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>You are probably missing a setting in
|
||||
<filename>/etc/X11/xorg.conf</filename>. Review this file
|
||||
carefully and check especially the <literal>DefaultDepth</literal>
|
||||
and <literal>AddARGBGLXVisuals</literal> directives.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
<answer>
|
||||
<para>You are probably missing a setting in
|
||||
<filename>/etc/X11/xorg.conf</filename>. Review this
|
||||
file carefully and check especially the
|
||||
<literal>DefaultDepth</literal> and
|
||||
<literal>AddARGBGLXVisuals</literal>
|
||||
directives.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question xml:id="xorg-crash">
|
||||
<para>When I run the command to start
|
||||
<application>Compiz Fusion</application>, the X server
|
||||
crashes and I am back at the console. What is wrong?</para>
|
||||
</question>
|
||||
<qandaentry>
|
||||
<question xml:id="xorg-crash">
|
||||
<para>When I run the command to start
|
||||
<application>Compiz Fusion</application>, the X
|
||||
server crashes and I am back at the console. What is
|
||||
wrong?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>If you check your <filename>/var/log/Xorg.0.log</filename>
|
||||
file, you will probably find error messages during the X
|
||||
startup. The most common would be:</para>
|
||||
<answer>
|
||||
<para>If you check your
|
||||
<filename>/var/log/Xorg.0.log</filename> file, you
|
||||
will probably find error messages during the X
|
||||
startup. The most common would be:</para>
|
||||
|
||||
<screen>(EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
|
||||
<screen>(EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
|
||||
(EE) NVIDIA(0): log file that the GLX module has been loaded in your X
|
||||
(EE) NVIDIA(0): server, and that the module is the NVIDIA GLX module. If
|
||||
(EE) NVIDIA(0): you continue to encounter problems, Please try
|
||||
(EE) NVIDIA(0): reinstalling the NVIDIA driver.</screen>
|
||||
|
||||
<para>This is usually the case when you upgrade
|
||||
<application>&xorg;</application>. You will need to reinstall the
|
||||
<package>x11/nvidia-driver</package> package so
|
||||
glx is built again.</para>
|
||||
<application>&xorg;</application>. You will need to
|
||||
reinstall the <package>x11/nvidia-driver</package>
|
||||
package so glx is built again.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
</qandaset>
|
||||
|
|
|
|||
Loading…
Reference in a new issue