Graphics administration guide for HP-UX 11.
Legal Notices © Copyright 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Table of Contents 1 Preface.............................................................................................................................7 Publishing history...................................................................................................................................7 Document conventions...........................................................................................................................7 2 Configuring X Server on HP-UX (OEM graphics cards).........
Miscellaneous..................................................................................................................................30 Fonts...........................................................................................................................................30 Files.............................................................................................................................................30 3 Configuring X server on HP-UX (HP Visualize-FXE)...................
List of Figures 3-1 Results of minimal legal X*screens file.........................................................................................
List of Tables 1-1 2-1 2-2 2-3 2-4 2-5 2-6 2-7 2-8 2-9 3-1 4-1 6 Publishing history details................................................................................................................7 Options for ServerLayout section..................................................................................................13 Options for InputDevice section...................................................................................................15 Options for Screen section.............
1 Preface The purpose of this document is to collect, in one place, all the information necessary to configure and administer graphics cards supported in HP-UX servers running the 11.00, 11i version 1 (11.11), 11i version 2 (11.23), and 11i version 3 (11.31) Operating Systems. NOTE: Previous versions of this document contained information for HP-UX workstations and the graphics adapters supported on workstations. This document deals only with HP-UX servers and the graphics adapters available on servers.
2 Configuring X Server on HP-UX (OEM graphics cards) This chapter documents information specific to the HP Xf86 X Server. The Xf86 X Server is based on the XFree86 version 4.2.0 X Server. This section describes features unique to HP's implementation of the X Server, provides information on how to configure the X Server and includes a list of supported X server configurations. For each supported graphics device, device-dependent configuration information is provided.
Running independent X Servers on an HP Visualize graphics device and an OEM graphics device simultaneously is not supported. Specific XF86 server options can be set with the Modify Server Options menu item. See the item for information on specific options. If you have multiple OEM graphics display devices or a display card with two video outputs, you can configure the X server to have multiple independent screens. Use the Modify Multi-Screen Layout menu item to do this.
NOTE: Changing the monitor type while the X Server is running will necessitate killing and restarting the X Server. In order to change the monitor settings, the X Server needs to be running on the device specified. For these graphics cards, it may not be possible to test some of the monitor settings before making the change permanent. The XF86Config file The XF86Config file is located in /etc/X11/XF86Config. It can be generated automatically or modified using SAM/SMH.
When the unit name is omitted, the correct units will be determined from the value and the expectations of the appropriate range of the value. It is recommended that the units always be specified when using frequency option values to avoid any errors in determining the value. ServerLayout section The ServerLayout section is used to identify which Screen sections are to be used in a multi-headed configuration, the relative layout of those screens, and which InputDevice sections are to be used.
Screen 1 "Screen 1" RightOf "Screen 0" Screen 2 "Screen 2" RightOf "Screen 1" ... EndSection Each InputDevice is followed by an InputDeviceID, a required field that must be enclosed in double quotes. The InputDeviceID must match an Identifier in an InputDevice section. Last, an option may be provided. The option can also be specified in the InputDevice section. Typical options specified here are: CorePointer, CoreKeyboard, and SendCoreEvents. The option must be enclosed in double quotes.
Section "Files" [FontPath . . [ModulePath . . [RgbPath [LogPath EndSection "PathName"] "PathName"] "PathName"] "PathName"] Multiple Font Paths and Module Paths may be specified in two ways, either by multiple lines or by using a “,” delimiter between paths on the same line. Font Path elements may be either absolute directory paths or a font server identifier.
[SubSection “ModuleName” Option . . . EndSubSection] . . . EndSection. Load instructs the server to load the module called ModuleName. The module name given should be the module's extension name, not the module file name. The extension name is case sensitive, and does not include the “lib” prefix, or the “.so.1” or “.1” suffix. Example: the Double Buffered Extension (DBE) can be loaded with the following entry: Load “dbe” SubSection also instructs the server to load the module called ModuleName.
Table 2-2 Options for InputDevice section (continued) AlwaysCore boolean Both of these options are equivalent, and when enabled cause the input device to always report core events. This can be used, for example, to allow additional pointer devices to generate core pointer events (such as moving the cursor, etc). Source: XF86Config man page. integer Sets the motion history size. Default: 0. Source: XF86Config man page.
There will NOT be more than one IRC virtual mouse or keyboard. The hardware does not support it. Screen section The configuration file may have multiple Screen sections. There must be at least one, for the “screen” being used. A “screen” binds a graphics device (Device section) and a monitor (Monitor section) together. A Screen section is considered “active” if it is referenced by an active ServerLayout section.
also be specified. The virtual screen allows you to have a “root window” larger than what can be displayed on the monitor. (for example, the monitor may be a 800x600 display, but have a 1280x1024 virtual size). The Virtual keyword is used to specify this size. Note that many of the new accelerated graphics drivers use non-displayed memory for caching. It is not desirable to use all available memory for the virtual display, as this leaves none for caching, and this can decrease server performance.
The VendorName is an optional entry and is used to specify the monitor's manufacturer. The ModelName is an optional entry that is used to specify the monitor model. HorizSync gives the range(s) of horizontal sync frequencies supported by the monitor. horizsync-range may be a comma separated list of either discrete values or ranges of values. A range of values is two values separated by a dash. By default the values are in units of kHz.
# the XF86Config file. However, the first one in the file is the active # layout, unless otherwise specified by the -layout option from the command # line. Check the "Graphics Administration Guide" (GAG) for other options that # may be set here, or elsewhere, in the XF86Config file. # Section "ServerLayout" # # The ServerLayout ID. A required line. # Identifier "Main Layout" # # # # # # # # The first field on the Screen line specifies the screen number. It is optional. The second field is the Screen ID.
EndSection # # The Module section is used to inform the server which loadable libraries are # to be loaded at run time. There may only be one Module section in the # XF86Config file. # See the GAG for more details. # Section "Module" EndSection # # There may be multiple InputDevice sections. An InputDevice section is active # only if it is specified by the active ServerLayout section.
# Set the default depth. # DefaultDepth 24 # # The subsection associates a buffer depth with a screen size. # SubSection "Display" Depth 24 Modes "1280x1024" EndSubSection EndSection Extensions Double buffer extension (DBE) DBE is an extension to the X Server that provides a double-buffering API.
By default, the DPMS level used is 0 or On (no power savings). If you wish to use power saving, set the following XF86Config file entries before starting the server: standby time, suspend time, and off time. Also set the Option “DPMS” “on” in the monitor section. DPMS should not be confused with screen blanking or screen saving. Screen blanking will merely cause the screen to go dark. Screen saving will display a changing pattern on the screen to avoid the burn-in of a static image.
Dynamically loaded modules are recorded by the X Server in the /var/X11/Xserver/logs directory. The log file reflects the display identifier for a given run. Only the last invocation against a given display identifier is retained. The log file contains the parsed contents of the XF86Config file and the full path name for all dynamically loaded modules for the given X Server invocation. Deferred loaded modules are recorded as they are referenced.
Signals See Xf86(1) for information on how the X Server handles signals. Starting the X Server from the command line Command line options for the X Server are described in Xf86(1). Mapping options from the previous hp X Server to the XF86 hp X Server The purpose of this section is to provide the user who is familiar with the X* screens files or the HP X Server a method of setting the equivalent options in the XF86Config file in the current release of the XF86 HP X Server.
Table 2-6 Keyboard Options Supported by HP (continued) Xleds Integer Specify which keyboard LEDs can be user-controlled (for example, with xset(1)). KBDClass KBDLocal or KBDVirtual This restricts the keyboard to either the local or the virtual IRC keyboard. The absence of this option will enable all keyboards. See the Integrity iLO 2 Integrated Remote Console section.
Supported visuals ATI Radeon family graphics devices support the following visuals: Class Depth PseudoColor 8 TrueColor 24 There are two visuals available with the ATI Radeon family displays, although not at the same time. The X server can be either in depth 8 or depth 24 frame buffer mode. In depth 24 mode the available visual is TrueColor. This is the recommended visual. In depth 8 mode the available visual is PseudoColor. The frame buffer depth is configurable through SAM/SMH.
Table 2-9 Supported Monitor Options (continued) Resolution (HxV) Frequency (Hz) Recommended usage 1280x1024 60 Flat panel 1280x1024 75 1280x1024 85 1600x1200 60 1600x1200 75 1600x1200 85 1920x1200 60 1920x1200 75 1920x1200 85 Flat panel Flat panel Framebuffer depth and colormaps Depth 24 is the recommended depth. The benefit is that with the TrueColor visual, applications have a large 16M color palette available.
For instructions on how to configure the system console to use VGA, see Installation and Update Guide for your operating system at http://docs.hp.com/. The following are required to use IRC: • • • An Integrity server with Integrity iLO 2 management processor and VGA graphics. Integrity iLO 2 Advanced functionality (available as a license key AD301A for entry-class servers). Management processor (MP) firmware version F.02.17 or T.02.17 or newer.
Feature Visualize-FXE Radeon Family Visuals PseudoColor, DirectColor, and TrueColor PseudoColor or TrueColor VGA video output Yes Yes DVI-I video output No Yes (Radeon 7000 and Radeon 7500 only) Maximum resolution in pixels 1600x1200 1920x1200 1600x1200 or 1680x1050 on ES1000 1600x1200 or 1680x1050 on DVI-I digital connector Miscellaneous Fonts The X Server can obtain fonts from directories or font servers.
3 Configuring X server on HP-UX (HP Visualize-FXE) This chapter documents information specific to the HP X Server. It describes features that are unique to HP’s X Server, provides information on how to configure the X Server and includes a list of supported configurations. Information specific to a new release of the X Server, beyond the scope of the general information in this document, can be found in the HP-UX Release Notes located in /usr/share/doc.
To configure a multi-screen layout, first select the devices you want to include. In the X Server Configuration panel click the mouse on the first device, and [Ctrl]-click on the others. All the devices you want to combine into a multi-screen configuration should now be highlighted. Then use the Modify Multi-Screen Layout menu item in the Actions menu to finish the configuration. SLS is a mechanism for treating homogeneous multi-display configurations as a single logical screen.
The X*screens file is used to specify: • • Device-independent server options, and For each screen: — what device file to use (required), — the default visual, — monitor size, and — device-dependent screen options. Note that all of the items above, except for device-independent server options, are specified on a per-screen basis. The X Server supports up to four screens at a time. Specifying more than four screens will cause a server error message.
Specify the size of the graphics shared memory region. The size must be specified in bytes and must be in hexadecimal. Default value: 0x580000 ImmediateLoadDles The X Server delays loading of some X extensions until the first protocol request to the given extension is received. Specifying this server option forces all extensions to be loaded at X Server startup. screen entries The minimum screen entry is a line with the keyword “Screen” followed by a screen device file.
Figure 3-1 Results of minimal legal X*screens file • This sample X*screens file could be used on a system using HP VISUALIZE-FXE with a 17-inch monitor. In this example, the GraphicsSharedMemorySize is decreased to 1 Mbyte in order to reduce the swap space requirements of the system. Decreasing GraphicsSharedMemorySize is appropriate when you do not intend to run any 3D graphics applications.
Performing buffer swaps on vertical blank For performance reasons, the default DBE behavior is to not synchronize buffer swaps with the monitor’s vertical retrace period. In some instances, therefore, image tearing (seeing part of the old image and part of the new image on the display at the same time) could be visible while swapping large DBE windows.
Shared memory XImages are essentially a version of the XImage interface where the actual image data is stored in a shared memory segment, and thus need not be moved through the Xlib interprocess communication channel. For large images, use of this facility can result in increased performance. Shared memory pixmaps are a similar concept implemented for the pixmap interface.
• • EnableIncludeInferiorsFix DisableGlxVisuals HP VISUALIZE-FXE configuration hints Overlay visuals and overlay transparency HP VISUALIZE-FXE devices have two visuals in the overlay planes, both depth-8 PseudoColor. The first (default) overlay visual has 256 entries per colormap and no transparency. The second overlay visual has 255 entries per colormap and supports transparency.
4 X Server configuration details This chapter discusses several details concerning the configuration of X hosts, mouse and keyboard. Making an X*.hosts file The /etc/X0.hosts file is an ASCII text file containing the hostnames of each remote host permitted to access your local server. • • If you are running as a stand-alone system, you must have your system’s name in this file. If you are part of a network, the other system names must be included.
number Specifies a list of button numbers to map the mouse keys to. The order of the numbers refers to the original button mapping. pp Print the current pointer mapping.
Table 4-1 Expression Types To do this. . . Use this expression. . . Assign a key symbol to a keycode keycode = Replace a key symbol expression with another keysym = Clear all keys associated with a modifier key clear Add a key symbol to a modifier add = Remove a key symbol from a modifier remove = keycode Refers to the numerical value that uniquely identifies each key on a keyboard.
On a larger scale, you can change your current keyboard to a Dvorak keyboard by creating a file with the appropriate keyboard mappings. xmodmap .keymap Printing a key map The -pk option prints a list of the key mappings for the current keyboard. xmodmap -pk The list contains the keycode and up to four 2-part columns.
— — /var/dt/Xerrors /var/X11/Xserver/logs/Xf86.0.log; Search the term EE to locate error messages. Stopping the X Windows system After stopping all application programs, stop the window system by holding down the Ctrland Shiftkeys, and then press the Pause/Break key. This stops the display server, and with it the window system.
