From owner-svn-doc-all@FreeBSD.ORG Tue Oct 8 23:04:54 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2B0EF1CB; Tue, 8 Oct 2013 23:04:54 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 08A5E2958; Tue, 8 Oct 2013 23:04:54 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id r98N4swo028605; Tue, 8 Oct 2013 23:04:54 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id r98N4rCn028604; Tue, 8 Oct 2013 23:04:53 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201310082304.r98N4rCn028604@svn.freebsd.org> From: Dru Lavigne Date: Tue, 8 Oct 2013 23:04:53 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r42907 - head/en_US.ISO8859-1/books/handbook/x11 X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 23:04:54 -0000 Author: dru Date: Tue Oct 8 23:04:53 2013 New Revision: 42907 URL: http://svnweb.freebsd.org/changeset/doc/42907 Log: White space fix only. Translators can ignore. Modified: head/en_US.ISO8859-1/books/handbook/x11/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/x11/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/x11/chapter.xml Tue Oct 8 22:57:33 2013 (r42906) +++ head/en_US.ISO8859-1/books/handbook/x11/chapter.xml Tue Oct 8 23:04:53 2013 (r42907) @@ -27,7 +27,7 @@ An installation of &os; using bsdinstall does not automatically - install a graphical user interface. This chapter describes + install a graphical user interface. This chapter describes how to install and configure &xorg;, 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 &xorg; and offers a choice of window managers during installation should refer to the pcbsd.org website. + url="http://www.pcbsd.org/">pcbsd.org + website. - - For more information on the video hardware that &xorg; - supports, refer to the + + For more information on the video hardware that + &xorg; supports, refer to the x.org website. After reading this chapter, you will know: @@ -54,7 +55,8 @@ - How to install and configure &xorg;. + How to install and configure + &xorg;. @@ -63,7 +65,8 @@ - How to use &truetype; fonts in &xorg;. + How to use &truetype; fonts in + &xorg;. @@ -254,12 +257,12 @@ To build &xorg; in its - entirety, be sure to have at least 4 GB of free disk space - available. + entirety, be sure to have at least 4 GB of free disk + space available. - Alternatively, &xorg; can be installed directly from packages. - To install the package using + Alternatively, &xorg; can be + installed directly from packages. To install the package using pkg_add, type: &prompt.root; pkg_add -r xorg @@ -285,99 +288,99 @@ &xorg; &xorg; - In most cases, &xorg; is self-configuring. Those with older - or unusual equipment may find it helpful to gather some - hardware information before beginning configuration. + In most cases, &xorg; is + self-configuring. Those with older or unusual equipment may + find it helpful to gather some hardware information before + beginning configuration. - - - Monitor sync frequencies - - - - Video card chipset - + + + Monitor sync frequencies + - - Video card memory - - + + Video card chipset + - - horizontal sync frequency - - - horizontal scan rate - horizontal sync frequency - - refresh rate - - vertical sync frequency - refresh rate - - - vertical scan rate - refresh rate - + + Video card memory + + - 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. - - 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. + + horizontal sync frequency + + + horizontal scan rate + horizontal sync frequency + + refresh rate + + vertical sync frequency + refresh rate + + + vertical scan rate + refresh rate + + + 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. + + 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. - Video card memory determines the maximum resolution and - color depth which can be displayed. + Video card memory determines the maximum resolution and + color depth which can be displayed. - - Caveats + + Caveats - 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: + 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: - - - 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. - + + + 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. + - - 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#. - + + 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#. + - - 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. - + + 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. + - - 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 discrete mode. - - - + + 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 discrete mode. + + + Configuring <application>&xorg;</application> @@ -386,16 +389,16 @@ HAL to autodetect keyboards and mice. The sysutils/hal and devel/dbus ports are - automatically installed as dependencies of - x11/xorg, but must be - enabled by adding the following entries to + automatically installed as dependencies of x11/xorg, but must be enabled by + adding the following entries to /etc/rc.conf: hald_enable="YES" dbus_enable="YES" - Start these services - before configuring &xorg;: + Start these services before configuring + &xorg;: &prompt.root; service hald start &prompt.root; service dbus start @@ -407,11 +410,10 @@ dbus_enable="YES" &prompt.root; Xorg -configure This will generate a file named - /root/xorg.conf.new 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: + /root/xorg.conf.new 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: &prompt.root; Xorg -config xorg.conf.new -retro @@ -470,22 +472,21 @@ dbus_enable="YES" Option "DontZap" "off" - If the test is unsuccessful, skip ahead to . Once the test is successful, - copy the configuration file to - /etc/X11/xorg.conf: + If the test is unsuccessful, skip ahead to . Once the test is successful, + copy the configuration file to + /etc/X11/xorg.conf: &prompt.root; cp xorg.conf.new /etc/X11/xorg.conf - + Desktop environments like GNOME, KDE or Xfce provide graphical tools - to set parameters such as video resolution. - If the default configuration works, skip to - for examples on how to - install a desktop environment. + to set parameters such as video resolution. If the default + configuration works, skip to + for examples on how to install a desktop environment. @@ -505,24 +506,26 @@ dbus_enable="YES" Type1 Fonts - The default fonts that ship with &xorg; 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 - &xorg;. For instance, the URW font collection - (x11-fonts/urwfonts) - includes high quality versions of standard type1 fonts - (Times Roman, - Helvetica, - Palatino and - others). The Freefonts collection - (x11-fonts/freefonts) - includes many more fonts, but most of them are intended for - use in graphics software such as the - Gimp, and are not complete enough - to serve as screen fonts. In addition, &xorg; can be configured + The default fonts that ship with + &xorg; 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 + &xorg;. For instance, the URW + font collection (x11-fonts/urwfonts) includes high + quality versions of standard type1 fonts (Times Roman, Helvetica, Palatino and others). The + Freefonts collection (x11-fonts/freefonts) includes + many more fonts, but most of them are intended for use in + graphics software such as the Gimp, + and are not complete enough to serve as screen fonts. In + addition, &xorg; 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 section on &truetype; @@ -587,20 +590,21 @@ dbus_enable="YES" 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 &xorg;. Once the files have been copied into this - directory, use ttmkfdir to create a + for use by &xorg;. Once the + files have been copied into this directory, use + ttmkfdir to create a fonts.dir file, so that the X font renderer knows that these new files have been installed. ttmkfdir is available from the FreeBSD - Ports Collection as - x11-fonts/ttmkfdir. + Ports Collection as x11-fonts/ttmkfdir. &prompt.root; cd /usr/local/lib/X11/fonts/TrueType &prompt.root; ttmkfdir -o fonts.dir Now add the &truetype; directory to the font path. This - is just the same as described above for - Type1 fonts, that is, use + is just the same as described above for Type1 fonts, that is, use &prompt.user; xset fp+ /usr/local/lib/X11/fonts/TrueType &prompt.user; xset fp rehash @@ -637,8 +641,8 @@ dbus_enable="YES" anti-aliased - All fonts in &xorg; that are found in - /usr/local/lib/X11/fonts/ and + All fonts in &xorg; that are + found in /usr/local/lib/X11/fonts/ and ~/.fonts/ 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 - + - Troubleshooting + Troubleshooting - If the mouse does not work, you will need to first - configure it before proceeding. See - in the &os; install chapter. In recent - Xorg versions, - the InputDevice sections in - xorg.conf are ignored in favor of the - autodetected devices. To restore the old behavior, add the - following line to the ServerLayout or - ServerFlags section of this file: + If the mouse does not work, you will need to first + configure it before proceeding. See + in the &os; install chapter. In recent + Xorg versions, the + InputDevice sections in + xorg.conf are ignored in favor of the + autodetected devices. To restore the old behavior, add the + following line to the ServerLayout or + ServerFlags section of this file: Option "AutoAddDevices" "false" @@ -1534,7 +1538,8 @@ DisplayManager.requestPort: 0 - &xorg; tuning + &xorg; + tuning The xorg.conf.new configuration file may now be tuned to taste. Open the file in a text editor @@ -1603,8 +1608,10 @@ EndSection One of the tools available to assist you during - troubleshooting process are the &xorg; log files, which contain - information on each device that the &xorg; server attaches to. + troubleshooting process are the + &xorg; log files, which contain + information on each device that the + &xorg; server attaches to. &xorg; log file names are in the format of /var/log/Xorg.0.log. The exact name of the log can vary from @@ -1619,9 +1626,10 @@ EndSection &prompt.root; cp xorg.conf.new /etc/X11/xorg.conf - The &xorg; configuration process is now complete. - &xorg; may be now started with the - &man.startx.1; utility. The &xorg; server may also be started + The &xorg; configuration + process is now complete. &xorg; + may be now started with the &man.startx.1; utility. The + &xorg; server may also be started with the use of &man.xdm.1;. @@ -1634,8 +1642,9 @@ EndSection Configuration with &intel; i810 integrated chipsets requires the agpgart AGP - programming interface for &xorg; to drive the card. See the - &man.agp.4; driver manual page for more information. + programming interface for &xorg; + to drive the card. See the &man.agp.4; driver manual page + for more information. This will allow configuration of the hardware as any other graphics board. Note on systems without the @@ -1741,6 +1750,6 @@ EndSection Now having completed these simple editing steps, X should start on your new widescreen monitor. - - - + + +