HP Integrity rx2800 HP Integrity rx2800 i2 2D Graphics Adapter Installation Gu - Page 18

Messages, Screen, ATI FireMV, ATI FireMV 22500, ServerLayout, Identifier, var/X11/Xserver/logs

Page 18 highlights

# Include other Screen info here, including other SubSections EndSection The first Screen section maps the screen Screen 0-1 to the physical device ATI FireMV 2250(0-1). The second Screen section maps the screen Screen 0-2 to the physical device ATI FireMV 2250(0-2). The third Screen section maps the Screen 2-1 to the physical device ATI FireMV 2250(2-1). Once you have the Screen sections set up, you can set up the ServerLayout section. The ServerLayout section uses the Identifier field that was defined for each of the Screen sections. The ServerLayout section describes all of the screens used by the Xserver. The ServerLayout section for this example follows: Section ServerLayout Identifier "Main Layout" Screen 0 "Screen 0-1" 0 0 Screen 1 "Screen 0-2" RightOf "Screen 0-1" Screen 2 "Screen 1-1" RightOf "Screen 0-2" InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection This ServerLayout has three (3) screens associated with it. These screens are accessed through the 0.0, 0.1 and 0.2 displays. The first screen is associated with the Screen 0-1 section and is the anchor screen (at location 0, 0). The second screen is associated with the Screen 0-2 section and its screen coordinates are to the right of the first screen. The third screen is associated with the Screen 1-1 section and its screen coordinates are to the right of the second screen. Messages Xserver messages are typically logged to /var/X11/Xserver/logs. The two files that contain the messages are: /var/X11/Xserver/logs/XF86.*.log /var/X11/Xserver/logs/Xstartup.*.log Where * is the display instance of the Xserver, which is usually 0. The Xstartup.*.log file contains messages from the X loader. The XF86.*.log file contains messages from the XF86 Xserver. The XF86.*.log file is the file that should be checked first, should problems arise. 18 HP-UX Configuration

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19

# Include other Screen info here, including other SubSections
EndSection
The first
Screen
section maps the screen
Screen 0
1
to the physical device
ATI FireMV
2250(0
1)
. The second
Screen
section maps the screen
Screen 0
2
to the physical device
ATI FireMV 2250(0
2)
. The third
Screen
section maps the
Screen 2
1
to the physical
device
ATI FireMV 2250(2
1)
.
Once you have the
Screen
sections set up, you can set up the
ServerLayout
section. The
ServerLayout
section uses the
Identifier
field that was defined for each of the
Screen
sections. The
ServerLayout
section describes all of the screens used by the Xserver. The
ServerLayout
section for this example follows:
Section ServerLayout
Identifier
Main Layout
Screen
0
Screen 0-1
0 0
Screen
1
Screen 0-2
RightOf
Screen 0-1
Screen
2
Screen 1-1
RightOf
Screen 0-2
InputDevice
Mouse0
CorePointer
InputDevice
Keyboard0
CoreKeyboard
EndSection
This
ServerLayout
has three (3) screens associated with it. These screens are accessed through
the 0.0, 0.1 and 0.2 displays. The first screen is associated with the
Screen 0-1
section and is
the anchor screen (at location 0, 0). The second screen is associated with the
Screen 0-2
section
and its screen coordinates are to the right of the first screen. The third screen is associated with
the
Screen 1-1
section and its screen coordinates are to the right of the second screen.
Messages
Xserver messages are typically logged to
/var/X11/Xserver/logs
. The two files that contain
the messages are:
/var/X11/Xserver/logs/XF86.*.log
/var/X11/Xserver/logs/Xstartup.*.log
Where
*
is the display instance of the Xserver, which is usually 0. The
Xstartup.*.log
file
contains messages from the X loader. The
XF86.*.log
file contains messages from the XF86
Xserver. The
XF86.*.log
file is the file that should be checked first, should problems arise.
18
HP-UX Configuration