From owner-svn-doc-head@FreeBSD.ORG Tue Oct 8 21:38:25 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4BF14E01; Tue, 8 Oct 2013 21:38:25 +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 373862426; Tue, 8 Oct 2013 21:38:25 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id r98LcPAd082359; Tue, 8 Oct 2013 21:38:25 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id r98LcPdW082358; Tue, 8 Oct 2013 21:38:25 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201310082138.r98LcPdW082358@svn.freebsd.org> From: Dru Lavigne Date: Tue, 8 Oct 2013 21:38:25 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r42905 - 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-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 21:38:25 -0000 Author: dru Date: Tue Oct 8 21:38:24 2013 New Revision: 42905 URL: http://svnweb.freebsd.org/changeset/doc/42905 Log: This patch does the following: - adds pkg instructions to 6.3. Installing Xorg - adds a Caveats section to 6.4. Xorg Configuration - temporarily moves the extra config stuff to a new section called 6.8. Troubleshooting--this text has not yet been reviewed and this section may end up being instead called 6.8. Advanced Configuration or shuffled elsewhere in a subsequent patch - replaces instances of X and X11 with the entity for xorg - some updates to Synopsis, there will be more updates as the chapter is reviewed and shuffled Approved by: bcr (mentor) 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 21:32:37 2013 (r42904) +++ head/en_US.ISO8859-1/books/handbook/x11/chapter.xml Tue Oct 8 21:38:24 2013 (r42905) @@ -7,7 +7,7 @@ - + The X Window System @@ -25,19 +25,25 @@ Synopsis - FreeBSD uses X11 to provide users with - a powerful graphical user interface. X11 - is a freely available version of the X Window System that - is implemented in &xorg; - (and other software packages not discussed here). The - default and official flavor of X11 in &os; is - &xorg;, the X11 server developed by - the X.Org Foundation under a license very similar to the one - used by &os;. - - For more information on the video hardware that X11 - supports, check the - &xorg; web site. + An installation of &os; using + bsdinstall does not automatically + 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 + install a desktop environment or window manager. + + + Users who prefer an installation method that automatically + configures the &xorg; and offers + a choice of window managers during installation should + refer to the pcbsd.org website. + + + For more information on the video hardware that &xorg; + supports, refer to the + x.org website. After reading this chapter, you will know: @@ -48,15 +54,16 @@ - How to install and configure X11. + How to install and configure &xorg;. - How to install and use different window managers. + How to install and configure several window managers + and desktop environments. - How to use &truetype; fonts in X11. + How to use &truetype; fonts in &xorg;. @@ -70,7 +77,7 @@ Know how to install additional third-party - software (). + software as described in . @@ -224,16 +231,20 @@ - Installing X11 + Installing <application>&xorg;</application> - &xorg; is the X11 - implementation for &os;. &xorg; - is the X server of the open source X Window System - implementation released by the X.Org Foundation. - &xorg; is based on the code of - &xfree86; 4.4RC2 and X11R6.6. - The version of &xorg; currently - available in the &os; Ports Collection is &xorg.version;. + &xorg; is the + implementation of the open source X Window System + released by the X.Org Foundation. In &os;, it + can be installed as a package or port. The meta-port for the + complete distribution which includes X servers, clients, + libraries, and fonts is located in x11/xorg. A minimal distribution + is located in x11/xorg-minimal, with separate + ports available for docs, libraries, and apps. + The examples in this section install the complete + &xorg; distribution. To build and install &xorg; from the Ports Collection: @@ -243,57 +254,38 @@ To build &xorg; in its - entirety, be sure to have at least 4 GB of free space + entirety, be sure to have at least 4 GB of free disk space available. - Alternatively, X11 can be installed directly from packages. - Binary packages to use with &man.pkg.add.1; tool are also - available for X11. When the remote fetching feature of - &man.pkg.add.1; is used, the version number of the package must - be removed. &man.pkg.add.1; will automatically fetch the latest - version of the application. - - So to fetch and install the package of - &xorg;, simply type: + Alternatively, &xorg; can be installed directly from packages. + To install the package using + pkg_add, type: &prompt.root; pkg_add -r xorg - - The examples above will install the complete X11 - distribution including the servers, clients, fonts etc. - Separate packages and ports of X11 are also available. - - To install a minimal X11 distribution you can - alternatively install - x11/xorg-minimal. - + To instead install the package using + pkg, type: - The rest of this chapter will explain how to configure - X11, and how to set up a productive desktop - environment. + &prompt.root; pkg install xorg - + + Contributed in July 2001 by - + --> - X11 Configuration + <application>&xorg;</application> Configuration &xorg; - X11 - - - Before Starting + &xorg; - In most cases, X11 is self-configuring. Those with older + 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. @@ -342,68 +334,84 @@ Video card memory determines the maximum resolution and color depth which can be displayed. - + + + 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: + + + + 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#. + + + + 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. + + + - Configuring X11 + Configuring <application>&xorg;</application> &xorg; uses HAL to autodetect keyboards and mice. The sysutils/hal and devel/dbus ports are - installed as dependencies of + automatically installed as dependencies of x11/xorg, but must be - enabled by the following entries in the - /etc/rc.conf file: + enabled by adding the following entries to + /etc/rc.conf: hald_enable="YES" dbus_enable="YES" - These services should be started (either manually or by - rebooting) before further &xorg; - configuration or use is attempted. - - &xorg; can often work without - any further configuration steps by simply typing at - prompt: - - &prompt.user; startx - - The automatic configuration may fail to work with some - hardware, or may not set things up quite as desired. In - these cases, manual configuration will be necessary. + Start these services + before configuring &xorg;: - - Desktop environments like - GNOME, - KDE or - Xfce have tools allowing the user - to easily set the screen parameters such as the resolution. - So if the default configuration is not acceptable and you - planned to install a desktop environment then just continue - with the installation of the desktop environment and use the - appropriate screen settings tool. - + &prompt.root; service hald start +&prompt.root; service dbus start - Configuration of X11 is a multi-step process. The first - step is to build an initial configuration file. As the super - user, simply run: + Once these services are started, check if + &xorg; auto-configures itself by + typing: &prompt.root; Xorg -configure - This will generate an X11 configuration skeleton file in - the /root directory called - xorg.conf.new (whether you &man.su.1; or - do a direct login affects the inherited supervisor - $HOME directory variable). The X11 program - will attempt to probe the graphics hardware on the system and - write a configuration file to load the proper drivers for the - detected hardware on the target system. - - The next step is to test the existing - configuration to verify that &xorg; - can work with the graphics - hardware on the target system. Type: + 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: &prompt.root; Xorg -config xorg.conf.new -retro @@ -462,423 +470,162 @@ dbus_enable="YES" Option "DontZap" "off" - 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" - - Input devices may then be configured as in previous - versions, along with any other options needed (e.g., keyboard - layout switching). + 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 + - As previously explained the - hald daemon will, by default, - automatically detect your keyboard. There are chances that - your keyboard layout or model will not be correct, desktop - environments like GNOME, + Desktop environments like + GNOME, KDE or - Xfce provide tools to configure - the keyboard. However, it is possible to set the keyboard - properties directly either with the help of the - &man.setxkbmap.1; utility or with a - hald's configuration rule. - - For example if one wants to use a PC 102 keys keyboard - coming with a french layout, we have to create a keyboard - configuration file for hald - called x11-input.fdi and saved in the - /usr/local/etc/hal/fdi/policy - directory. This file should contain the following - lines: - - <?xml version="1.0" encoding="iso-8859-1"?> -<deviceinfo version="0.2"> - <device> - <match key="info.capabilities" contains="input.keyboard"> - <merge key="input.x11_options.XkbModel" type="string">pc102</merge> - <merge key="input.x11_options.XkbLayout" type="string">fr</merge> - </match> - </device> -</deviceinfo> + 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. + + + - If this file already exists, just copy and add to your - file the lines regarding the keyboard configuration. + + + + + Using Fonts in <application>&xorg;</application> - You will have to reboot your machine to force - hald to read this file. + + Type1 Fonts - It is possible to do the same configuration from an X - terminal or a script with this command line: + 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; + fonts. - &prompt.user; setxkbmap -model pc102 -layout fr + To install the above Type1 font collections from the + Ports Collection, run the following commands: - The - /usr/local/share/X11/xkb/rules/base.lst - file lists the various keyboard, layouts and options - available. - + &prompt.root; cd /usr/ports/x11-fonts/urwfonts +&prompt.root; make install clean - X11 tuning + And likewise with the freefont or other collections. To + have the X server detect these fonts, add an appropriate line + to the X server configuration file + (/etc/X11/xorg.conf), which reads: - The xorg.conf.new configuration file - may now be tuned to taste. Open the file in a text editor - such as &man.emacs.1; or &man.ee.1;. If the monitor is an - older or unusual model that does not support autodetection of - sync frequencies, those settings can be added to - xorg.conf.new under the - "Monitor" section: + FontPath "/usr/local/lib/X11/fonts/URW/" - Section "Monitor" - Identifier "Monitor0" - VendorName "Monitor Vendor" - ModelName "Monitor Model" - HorizSync 30-107 - VertRefresh 48-120 -EndSection + Alternatively, at the command line in the X session + run: - 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. + &prompt.user; xset fp+ /usr/local/lib/X11/fonts/URW +&prompt.user; xset fp rehash - X allows DPMS (Energy Star) features to be used with - capable monitors. The &man.xset.1; program controls the - time-outs and can force standby, suspend, or off modes. If - you wish to enable DPMS features for your monitor, you must - add the following line to the monitor section: + This will work but will be lost when the X session is + closed, unless it is added to the startup file + (~/.xinitrc for a normal + startx session, or + ~/.xsession when logging in through a + graphical login manager like XDM). + A third way is to use the new + /usr/local/etc/fonts/local.conf file: see + the section on + anti-aliasing. + - Option "DPMS" + + &truetype; Fonts - xorg.conf + TrueType Fonts + + + fonts + TrueType - While the xorg.conf.new - configuration file is still open in an editor, select the - default resolution and color depth desired. This is defined - in the "Screen" section: + &xorg; has built in support for + rendering &truetype; fonts. There are two different modules + that can enable this functionality. The freetype module is + used in this example because it is more consistent with the + other font rendering back-ends. To enable the freetype module + just add the following line to the "Module" + section of the /etc/X11/xorg.conf + file. - Section "Screen" - Identifier "Screen0" - Device "Card0" - Monitor "Monitor0" - DefaultDepth 24 - SubSection "Display" - Viewport 0 0 - Depth 24 - Modes "1024x768" - EndSubSection -EndSection + Load "freetype" - The DefaultDepth keyword describes the - color depth to run at by default. This can be overridden with - the command line switch to - &man.Xorg.1;. The Modes keyword describes - the resolution to run at for the given color depth. Note that - only VESA standard modes are supported as defined by the - target system's graphics hardware. In the example above, the - default color depth is twenty-four bits per pixel. At this - color depth, the accepted resolution is 1024 by 768 - pixels. + Now make a directory for the &truetype; fonts (for + example, + /usr/local/lib/X11/fonts/TrueType) and + 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 + 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. - Finally, write the configuration file and test it using - the test mode given above. + &prompt.root; cd /usr/local/lib/X11/fonts/TrueType +&prompt.root; ttmkfdir -o fonts.dir - - One of the tools available to assist you during - troubleshooting process are the X11 log files, which contain - information on each device that the X11 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 - Xorg.0.log to - Xorg.8.log and so forth. - + Now add the &truetype; directory to the font path. This + is just the same as described above for + Type1 fonts, that is, use - If all is well, the configuration file needs to be - installed in a common location where &man.Xorg.1; can find it. - This is typically /etc/X11/xorg.conf or - /usr/local/etc/X11/xorg.conf. + &prompt.user; xset fp+ /usr/local/lib/X11/fonts/TrueType +&prompt.user; xset fp rehash - &prompt.root; cp xorg.conf.new /etc/X11/xorg.conf + or add a FontPath line to the + xorg.conf file. - The X11 configuration process is now complete. - &xorg; may be now started with the - &man.startx.1; utility. The X11 server may also be started - with the use of &man.xdm.1;. - - - - Advanced Configuration Topics - - - Configuration with &intel; <literal>i810</literal> - Graphics Chipsets - - - Intel i810 graphic chipset - - - Configuration with &intel; i810 integrated chipsets - requires the agpgart AGP - programming interface for X11 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 - &man.agp.4; driver compiled in the kernel, trying to load - the module with &man.kldload.8; will not work. This driver - has to be in the kernel at boot time through being compiled - in or using /boot/loader.conf. - - - - Adding a Widescreen Flatpanel to the Mix - - - widescreen flatpanel configuration - - - This section assumes a bit of advanced configuration - knowledge. If attempts to use the standard configuration - tools above have not resulted in a working configuration, - there is information enough in the log files to be of use in - getting the setup working. Use of a text editor will be - necessary. - - Current widescreen (WSXGA, WSXGA+, WUXGA, WXGA, WXGA+, - et.al.) formats support 16:10 and 10:9 formats or aspect - ratios that can be problematic. Examples of some common - screen resolutions for 16:10 aspect ratios are: - - - - 2560x1600 - - - - 1920x1200 - - - - 1680x1050 - - - - 1440x900 - - - - 1280x800 - - - - At some point, it will be as easy as adding one of these - resolutions as a possible Mode in the - Section "Screen" as such: - - Section "Screen" -Identifier "Screen0" -Device "Card0" -Monitor "Monitor0" -DefaultDepth 24 -SubSection "Display" - Viewport 0 0 - Depth 24 - Modes "1680x1050" -EndSubSection -EndSection - - &xorg; is smart enough to - pull the resolution information from the widescreen via - I2C/DDC information so it knows what the monitor can handle - as far as frequencies and resolutions. - - If those ModeLines do not exist in - the drivers, one might need to give - &xorg; a little hint. Using - /var/log/Xorg.0.log one can extract - enough information to manually create a - ModeLine that will work. Simply look for - information resembling this: - - (II) MGA(0): Supported additional Video Mode: -(II) MGA(0): clock: 146.2 MHz Image Size: 433 x 271 mm -(II) MGA(0): h_active: 1680 h_sync: 1784 h_sync_end 1960 h_blank_end 2240 h_border: 0 -(II) MGA(0): v_active: 1050 v_sync: 1053 v_sync_end 1059 v_blanking: 1089 v_border: 0 -(II) MGA(0): Ranges: V min: 48 V max: 85 Hz, H min: 30 H max: 94 kHz, PixClock max 170 MHz - - This information is called EDID information. Creating a - ModeLine from this is just a matter of - putting the numbers in the correct order: - - ModeLine <name> <clock> <4 horiz. timings> <4 vert. timings> - - So that the ModeLine in - Section "Monitor" for this example would - look like this: - - Section "Monitor" -Identifier "Monitor1" -VendorName "Bigname" -ModelName "BestModel" -ModeLine "1680x1050" 146.2 1680 1784 1960 2240 1050 1053 1059 1089 -Option "DPMS" -EndSection - - Now having completed these simple editing steps, X - should start on your new widescreen monitor. - - - - - - - - - Murray - Stokely - Contributed by - - - - Using Fonts in X11 - - - Type1 Fonts - - The default fonts that ship with X11 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 - X11. 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, X11 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; - fonts. - - To install the above Type1 font collections from the - Ports Collection, run the following commands: - - &prompt.root; cd /usr/ports/x11-fonts/urwfonts -&prompt.root; make install clean - - And likewise with the freefont or other collections. To - have the X server detect these fonts, add an appropriate line - to the X server configuration file - (/etc/X11/xorg.conf), which reads: - - FontPath "/usr/local/lib/X11/fonts/URW/" - - Alternatively, at the command line in the X session - run: - - &prompt.user; xset fp+ /usr/local/lib/X11/fonts/URW -&prompt.user; xset fp rehash - - This will work but will be lost when the X session is - closed, unless it is added to the startup file - (~/.xinitrc for a normal - startx session, or - ~/.xsession when logging in through a - graphical login manager like XDM). - A third way is to use the new - /usr/local/etc/fonts/local.conf file: see - the section on - anti-aliasing. - - - - &truetype; Fonts - - - TrueType Fonts - - - fonts - TrueType - - - &xorg; has built in support for - rendering &truetype; fonts. There are two different modules - that can enable this functionality. The freetype module is - used in this example because it is more consistent with the - other font rendering back-ends. To enable the freetype module - just add the following line to the "Module" - section of the /etc/X11/xorg.conf - file. - - Load "freetype" - - Now make a directory for the &truetype; fonts (for - example, - /usr/local/lib/X11/fonts/TrueType) and - 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 X11. 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. - - &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 - - &prompt.user; xset fp+ /usr/local/lib/X11/fonts/TrueType -&prompt.user; xset fp rehash - - or add a FontPath line to the - xorg.conf file. - - That's it. Now Gimp, - Apache OpenOffice, 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 &staroffice;) will - look much better now. + That's it. Now Gimp, + Apache OpenOffice, 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 &staroffice;) will + look much better now. - + + Updated in May 2003 by - + --> Anti-Aliased Fonts @@ -890,7 +637,7 @@ EndSection anti-aliased - All fonts in X11 that are found in + 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 @@ -1060,13 +807,13 @@ EndSection - + The X Display Manager @@ -1230,7 +977,7 @@ EndSection chooser and login screens. In it, the appearance of the login program can be modified. The format is identical to the app-defaults file described in the - X11 documentation. + &xorg; documentation. @@ -1321,14 +1068,13 @@ DisplayManager.requestPort: 0 - + - + --> Desktop Environments @@ -1718,4 +1464,283 @@ DisplayManager.requestPort: 0 + + + + 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: + + Option "AutoAddDevices" "false" + + Input devices may then be configured as in previous + versions, along with any other options needed (e.g., keyboard + layout switching). + + + As previously explained the + hald daemon will, by default, + automatically detect your keyboard. There are chances that + your keyboard layout or model will not be correct, desktop + environments like GNOME, + KDE or + Xfce provide tools to configure + the keyboard. However, it is possible to set the keyboard + properties directly either with the help of the + &man.setxkbmap.1; utility or with a + hald's configuration rule. + + For example if, one wants to use a PC 102 keys keyboard + coming with a french layout, we have to create a keyboard + configuration file for hald + called x11-input.fdi and saved in the + /usr/local/etc/hal/fdi/policy + directory. This file should contain the following + lines: + + <?xml version="1.0" encoding="iso-8859-1"?> +<deviceinfo version="0.2"> + <device> + <match key="info.capabilities" contains="input.keyboard"> + <merge key="input.x11_options.XkbModel" type="string">pc102</merge> + <merge key="input.x11_options.XkbLayout" type="string">fr</merge> + </match> + </device> +</deviceinfo> + + If this file already exists, just copy and add to your + file the lines regarding the keyboard configuration. + + You will have to reboot your machine to force + hald to read this file. + + It is possible to do the same configuration from an X + terminal or a script with this command line: + + &prompt.user; setxkbmap -model pc102 -layout fr + + The + /usr/local/share/X11/xkb/rules/base.lst + file lists the various keyboard, layouts and options + available. + + + &xorg; tuning + + The xorg.conf.new configuration file + may now be tuned to taste. Open the file in a text editor + such as &man.emacs.1; or &man.ee.1;. If the monitor is an + older or unusual model that does not support autodetection of + sync frequencies, those settings can be added to + xorg.conf.new under the *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***