graphics administration guide for HP-UX 11.
Legal Notices © Copyright 2001-2008 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......................................................................................................................................9 publishing history................................................................................................................9 document conventions.........................................................................................................9 2 configuring X Server on HP-UX (OEM graphics cards).....................................
output devices.....................................................................................................................31 ATI Radeon™ family device-dependent information...................................................31 supported visuals.....................................................................................................31 supported monitor configurations...........................................................................32 Framebuffer depth and colormaps...............
examples ..................................................................................................................52 printing a key map...................................................................................................52 stopping the X Window system .........................................................................................
List of Figures 3-1 6 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 3-1 4-1 publishing history details.............................................................................................9 Options for ServerLayout section...............................................................................16 Options for InputDevice section.................................................................................19 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.
The Configure Print Server item allows you to manage print servers. From this menu item you can create, stop or remove print servers. On systems that contain a mix of HP Visualize and OEM graphics cards, the Configure How X Starts item allows you to choose on which graphics devices the X Server should start. From this action, you can assign which of your configuration files to use as a display connection - the X* screens file for HP Visualize graphics cards or the XF86Config file with OEM graphics cards.
Grayed out screen icons represent screens that have not been configured for use by the X Server. You can select these grayed out icons and choose the Add Screen to Configuration menu item to add screens to the XF86Config file. More information on configuration of the X Server and each of the above actions can be obtained from SAM/SMH on-line Help. using setmon to configure the monitor setmon is a configuration tool used to change the monitor settings for a monitor attached to a graphics device.
NOTE: Hex integer values must be prefixed with “0x”, and octal values with “0”. A special keyword called Option may be used to provide free-form data to various components of the server. The Option keyword takes either one or two string arguments. The first is the option name, and the optional second argument is the option value.
Section “ServerLayout” Identifier “ServerLayoutName” Screen [ScreenNumber] “ScreenID” [Position] [Xcoor] [Ycoor] . . . InputDevice “InputDeviceID” “InputDeviceOption” . . . [Option …] . . . EndSection Keywords, options and values enclosed in [ ] are optional. A number specifying the preferred screen number for that screen may optionally follow each Screen. When no screen number is specified, it is numbered according to the order in which it is listed.
... 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. See the InputDevice section for more information regarding the options.
Font Path elements may be either absolute directory paths or a font server identifier. Font server identifiers have the form: /: where is the transport type to use to connect to the font server (e.g., Unix for UNIX-domain sockets or tcp for a TCP/IP connection), is the hostname of the machine running the font server, and is the port number that the font server is listening on (usually 7000).
. . . [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 Option Value Description CorePointer NA When this is set, the input device is installed as the core (primary) pointer device. There must be no more than one core pointer. If this option is not set here, or in the ServerLayout section, or from the -pointer command line option, then the first input device that is capable of being used as a core pointer will be selected as the core pointer. Source: XF86Config man page.
DefaultDepth Option ... . . SubSection “Display” . . EndSubSection . EndSection The Identifier entry specifies the unique name for this screen. The Identifier generally must match a ScreenID listed in the active ServerLayout section. The Screen section provides information specific to the whole screen, including screen-specific Options. In multi-screen configurations, there will be multiple active Screen sections, one for each head.
Display subsection The Screen sections include one or more Display subsections. One Display subsection may be provided for each depth that the server supports. The size of the Xserver’s virtual screen may also be specified. The virtual screen allows you to have a “root window” larger than what can be displayed on the monitor. (e.g. the monitor may be a 800x600 display, but have a 1280x1024 virtual size). The Virtual keyword is used to specify this size.
Monitor section The configuration file may have multiple Monitor sections. The Monitor section provides information about the specifications of the monitor, monitor-specific Options, and information about the video modes to use with the monitor. There must be at least one Monitor section, for the monitor being used. A Monitor section is considered “active” if it is referenced by an active Screen section.
Section “Device” Identifier Devicefile Option … . . . EndSection “DeviceID” “/dev/gvid” The Identifier entry specifies the unique name for this graphics device. It must match a DriverID in the active Screen section. sample XF86Config file # This is a sample XF86Config file. It can be cut from this document # and placed in the /etc/X11/XF86Config file. # # The config file has a hierarchical “Section” structure along # with some standalone “Sections.
# # # # # # # # Each InputDevice line specifies an InputDevice section ID name and optionally some options that specify the way the device is to be used. Typically there is a pointer device (mouse) and a keyboard. They usually are specified with a CorePointer and CoreKeyboard option respectively. Additional pointers and keyboards are specified with the SendCoreEvents option. The options may also be specified in the InputDevice section. It is not necessary to specify an InputDevice.
# (mouse) and the other for the keyboard. The Driver line is required. It # specifies which driver is to be loaded at run time. See the GAG for more # details on what input devices are supported and which options may be selected. # Section "InputDevice" Identifier "Keyboard0" Driver "keyboard" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "PS/2" EndSection # # There may be multiple Monitor sections.
EndSubSection EndSection extensions double buffer extension (DBE) DBE is an extension to the X Server that provides a double-buffering API.
The actual amount of power saved and the recovery time for each of the states is monitor dependent and may vary widely. The customer can compensate for this by choosing an appropriate level for the monitor that is currently in use. By default, the DPMS level used is 0 or On (i.e. 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.
Table 2-5 DPMS Settings Option Value Default Description BlankTime time 10 Sets the inactivity timeout for the blanking phase of the screensaver. Time is in minutes. This is equivalent to the Xserver's `-s' flag, and the value can be changed at run-time with xset(1). StandbyTime time 20 Sets the inactivity timeout for the “standby” phase of DPMS mode. Time is in minutes, and the value can be changed at run-time with xset(1).
Section “ServerLayout” . . . Option “CursorScaleFactor” Option “MaxCursorSize” . . . EndSection “n” “Size” Where n = 1, 2, 3, … Where Size = 2, 4, 8, 16, 32, 64, … For example, n=2 instructs the X Server to scale all cursors by “2x” so that a 16x16 cursor becomes a 32x32 cursor and a 9x9 cursor becomes an 18x18 cursor, etc. If the scaled width or height of any cursor is greater than Size, the scale factor is reduced so that the net size of the cursor fits into a Size x Size rectangle.
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. Only those options that are currently implemented in the release are documented here. defaultVisual option The default visual in the Xf86 HP X server can be implicitly set by changing the depth of the framebuffer.
Table 2-6 Keyboard Options Supported by HP Options Value Description AutoRepeat Integer Set the keyboard auto repeat parameters. Not all platforms implement this. Xleds Integer … Specify which keyboard LEDs can be user-controlled (for example, with xset(1)). pointers supported pointer drivers The supported pointer driver is: mouse supported pointer options The following is a list of pointer options supported by HP.
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-8 Supported Monitor Options (continued) Resolution (HxV) Frequency (Hz) 1600x1200 75 1600x1200 85 1920x1200 60 1920x1200 75 1920x1200 85 Recommended usage 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. Because the TrueColor colormap is read only, it can be shared among multiple applications without any color flashing problems.
compatibility table with other display adapters The following table illustrates differences between the HP Visualize-FXE graphics devices and the OEM graphics devices.
/usr/lib/X11/fonts/iso_8859.8/75dpi/ /usr/lib/X11/fonts/iso_8859.9/75dpi/ /usr/lib/X11/fonts/iso_8859.15/75dpi/ files The X Server makes use of various files on the system during normal operation. This section lists the default location of the files and gives a brief description of what they do. File Description /etc/X11/XF86Config The configuration file. Xf86 uses this file to configure itself during initialization. /etc/X11/rgb.* The color database. /etc/Xn.
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.
The first group of Actions menus can be thought of as “global” actions. They will typically be active regardless of what has been selected. If any of these menu items are not visible it is because they are not supported under the current configuration. The Configure Print Server item allows you to manage print servers. From this menu item you can create, stop or remove print servers.
Grayed out screen icons represent screens that have not been configured for use by the X Server. You can select these grayed out icons and choose the Add Screen to Configuration menu item to add screens to the X*screens. using setmon to configure the monitor setmon is a configuration tool used to change the monitor settings for a monitor attached to a graphics device. This tool permits you to change the monitor's refresh rate and frame buffer resolution.
syntax guidelines • • Blank lines and comments (text following “#”) are ignored. Entries can occupy more than a single line. All symbols in the file are recognized case-insensitive. the X*screens file format Items must appear in the X*screens file in the order that they are specified below. [ServerOptions . . . ] {Screen } || {SingleLogicalScreen . . .
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.
sample X*screens files Below are several sample X*screens files that illustrate the new format. • This is the minimum legal X*screens file, the “Screen” keyword followed by the screen device. Since no other information is given, the X Server will assume default values for other options and settings. Screen /dev/crt 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.
Screen /dev/crt DefaultVisual Transparent The display diagram would be the same as that of the “Results of Minimal Legal X*screens File” configuration, above. miscellaneous topics double buffer extensions DBE is an extension to the X Server that provides a double-buffering Application Programming Interface (API).
For more information, refer to the DBE man page on XdbeScreenVisualInfo(). display power management signaling (DPMS) Monitors constitute a large percentage of the power used by a workstation even when not actively in use (i.e., during screen blanking).
all other respects, shared memory pixmaps behave the same as ordinary pixmaps and can be modified by the usual Xlib routines. In addition, it is possible to change the contents of these pixmaps directly without the use of Xlib routines merely by modifying the pixmap data. hp Visualize-FXE device-dependent information This section includes information on the HP VISUALIZE-FXE graphics devices. The HP VISUALIZE-FXE has 8 overlay planes, 48 image planes a 24-bit z buffer and 4 hardware colormaps.
NOTE: When running xdpyinfo or calling the XGetVisualInfo() Xlib function, some extra duplicate visuals may appear in the visual list. These extra visuals are created on behalf of the OpenGL extension to X (GLX). If necessary, the extra visuals can be disabled using the DisableGLxVisuals screen option. See the “Disabling the GLX Visuals” section for more information.
hp VISUALIZE-FXE colormaps HP VISUALIZE-FXE devices have a total of 4 hardware colormaps. 2 of the colormaps are dedicated to the overlay planes. The remaining 2 colormaps are dedicated to the image planes. Of the two overlay colormaps, one is permanently reserved for the default colormap. The other overlay colormap is available to applications. changing the monitor type A configuration tool is available to change the monitor type on HP VISUALIZE-FXE devices.
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.
changing mouse button actions The xmodmap utility can be used to change mouse button mappings. The syntax for changing mouse button mappings with xmodmap is: xmodmap {-e “pointer = {default | number [number...]}” | -pp} where: -e Specifies a remapping expression. default Set mouse keys back to default bindings. 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.
Specifies a remapping expression to be executed. -pm, -p Prints the current modifier map to the standard output. This is the default. -pk Prints the current keymap table to the standard output. -pp Print the current pointer map to the standard output. - (dash) Specifies that the standard input should be used for the input file. Specifies a particular key mapping file to be used.
can associate more than one key symbol with a modifier (such as Lock = Shift_R and Lock = Shift_L), and you can associate more than one modifier with a key symbol (for example, Control = Caps_Lock and Lock = Caps_Lock). For example, on a PC-style keyboard, you can press Dto print a lower case "d", Shift Dto print a capital "D", Alt Dto print something else, and Shift Alt Dto print still something else.
The list contains the keycode and up to four 2-part columns. The first column contains unmodified key values, the second column contains shifted key values, the third column contains meta (Extend Char/Alt) key values, and the fourth column contains shifted meta key values. Each column is in two parts: hexadecimal key symbol value, and key symbol name.
