HP-2133, Chrome9-Beta, X11 configuration file

Michael S. Zick

June 6, 2008

Contents

1 Overview
2 Layouts
 2.1 Default Selection
 2.2 Dynamic Selection
3 Single Modes
 3.1 LCD-only
 3.2 CRT-only
4 Clone Modes
 4.1 LCD-clone
 4.2 CRT-clone
5 Installation
6 Defaults
 6.1 Correcting Autodetect
 6.2 Generating the default layout
 6.3 X11R7-Chrome9-Beta Defaults

1 Overview

This configuration file was developed on a HP-2133 with the VIA Chrome9 driver package, chrome9.83.40558, installed.

The driver package is a Beta release. Its feature support can be expected to change in the future.

As shipped; This version has only partial support for X11 RandR functions. The support for running independent, dual channel, layouts is broken.

The server layouts in this configuration file are all single channel layouts.

Since RandR is incomplete, the layout can only be set when the server is started. The newer ability to make changes in the layout without a server restart is non-functional.

This configuration file is a direct replacement for the /etc/X11/xorg.conf file and provides four of the server layouts most likely to be needed by users.

2 Layouts

One of the X server layouts should be selected as the default layout.

Any of the layouts may be selected by passing the name of the layout on the X server command line.

2.1 Default Selection

Near the top of the file is the declaration of the default server layout to be used.

Selection is made by commenting out the three declarations not being made the single default entry.

As supplied, the LCD-clone layout is the default, active layout. As shown below:

Section "ServerFlags"

        Option          "DefaultServerLayout"   "LCD-clone"

#       Option          "DefaultServerLayout"   "CRT-clone"

#       Option          "DefaultServerLayout"   "LCD-only"

#       Option          "DefaultServerLayout"   "CRT-only"

        Option          "AllowMouseOpenFail"    "on"

        Option          "Pixmap"                "32"

    EndSection

The initial # character of each line is the comment indicator.

To change the active default, remove the initial # character from the desired declaration and ensure the other three do have the initial # character.

2.2 Dynamic Selection

The server layout may be changed from the declared default by passing the -layout “layout-name” option on the X11 server command line.

How and where to put the X11 layout start-up option depends on the windowing system in use.

The layouts where developed and tested from the command line, using the startx command with its built-in defaults only.

For example, to start the server using the LCD-clone layout:

startx -- -config /root/xorg.mini -layout “LCD-clone”

3 Single Modes

The configuration file has multiple, named, instances of the various X11 server configuration sections.

The single output sections of the file are also re-used in the clone mode outputs.

The sections of the file which are active in each layout are shown in the following as copies of the log file output.

3.1 LCD-only

This layout provides video drive signals to the internal LCD only. The external connector is not driven.

The internal LCD does not return DDC information, so the operating limits are specified within this layout.

(++) Using config file: "/root/xorg.mini"

(++) ServerLayout "LCD-only"

(**) |-->Screen "via-P4M900 Screen 0" (0)

(**) | |-->Monitor "HP-2133 LCD"

(**) | |-->Device "via-P4M900 Device 0"

(**) |-->Input Device "Keyboard 0"

(**) |-->Input Device "Mouse 0"

(**) |-->Input Device "Mouse 1"

(**) Option "AllowMouseOpenFail" "on"

(**) Option "Pixmap" "32"

(**) Option "Xinerama" "off"

3.2 CRT-only

This layout provides video drive signals to the external connector only. The internal LCD is not driven.

This layout is fully dependent on the external device returning proper and complete DDC information.

This does not control power to the LCD and without video drive, it will enter a self-test mode.

Closing the lid will power down the LCD.

Any other actions taken in response to closing the lid are dependent on how the window manager that is running is configured.

(++) Using config file: "/root/xorg.mini"

(++) ServerLayout "CRT-only"

(**) |-->Screen "via-P4M900 Screen 1" (0)

(**) |   |-->Monitor "HP-2133 External"

(**) |   |-->Device "via-P4M900 Device 1"

(**) |-->Input Device "Keyboard 0"

(**) |-->Input Device "Mouse 0"

(**) |-->Input Device "Mouse 1"

(**) Option "AllowMouseOpenFail" "on"

(**) Option "Pixmap" "32"

(**) Option "Xinerama" "off"

4 Clone Modes

These modes both use a single channel (rendering pipeline) on the graphics chip to drive the two outputs with the same video signal.

The terminology used indicates which device controls the display size.

If the commented out virtual size options are not used, the virtual size is set to the physical size of the controlling display.

If the other device can display the scan rate and does not have the width and/or height (in pixels) to display the full virtual size, the display may be smoothly panned to any portion of the virtual display.

The layout option “Simultaneous” in the corresponding “Screen” section can be set to “true” to disable the mouse pointer on the LCD. Translation: If the LCD has the smaller of the display areas, turning off the mouse pointer disables the ability to pan the view.

The hardware is capable of displaying different scan rates on the two outputs (two channel, DuoView mode) but this feature is not working in the current driver software.

The user can set the virtual size used to larger than the size of the controlling display by changing a commented out option in the file.

4.1 LCD-clone

This layout provides identical video drive signals to both connectors. It is the one most similar to the X11 configuration file in common use on the HP-2133.

The operating limits are set to those defined for the internal LCD. The layout uses the same Monitor and Device sections as the LCD-only layout.

The external monitor must be able to display the resolution and scan rate used for the LCD. There is no protection against sending video signals to the external monitor that might result in damage. Modern monitors will shut down; Old monitors will smoke, burn out and stop working.

(++) Using config file: "/root/xorg.mini"

(++) ServerLayout "LCD-clone"

(**) |-->Screen "via-P4M900 Clone 0" (0)

(**) |   |-->Monitor "HP-2133 LCD"

(**) |   |-->Device "via-P4M900 Device 0"

(**) |-->Input Device "Keyboard 0"

(**) |-->Input Device "Mouse 0"

(**) |-->Input Device "Mouse 1"

(**) Option "AllowMouseOpenFail" "on"

(**) Option "Pixmap" "32"

(**) Option "Xinerama" "off"

As shipped, this layout establishes a virtual screen size that matches the 1280x768 LCD. If the run-time resolution is changed (as with xvidtune) to a smaller resolution, the smaller resolution can be smoothly panned across the full virtual screen.

The layout has a commented out, virtual size option in the named “Screen” section with which the user can set a larger virtual screen size.

The layout has the “Simultaneous” option set to “false” in the named “Screen” section, setting it to “true” removes the mouse pointer from the LCD display.

4.2 CRT-clone

This layout provides identical video drive signals to both connectors.

The operating limits are set to those defined for the external monitor. The layout uses the same Monitor and Device sections as the CRT-only layout which do not consider the operating limits of the internal LCD.

The internal LCD must be able to display the resolution and scan rate used for the external monitor. It is not known if the internal LCD hardware can protect itself against self-destruction.

(++) Using config file: "/root/xorg.mini"

(++) ServerLayout "CRT-clone"

(**) |-->Screen "via-P4M900 Clone 1" (0)

(**) |   |-->Monitor "HP-2133 External"

(**) |   |-->Device "via-P4M900 Device 1"

(**) |-->Input Device "Keyboard 0"

(**) |-->Input Device "Mouse 0"

(**) |-->Input Device "Mouse 1"

(**) Option "AllowMouseOpenFail" "on"

(**) Option "Pixmap" "32"

(**) Option "Xinerama" "off"

This layout will set the resolution to the external monitor’s preferred mode if properly reported by DDC. Otherwise it will set the resolution to the external monitor’s maximum resolution reported by DDC. If the external monitor does not respond to DDC requests, all bets are off. The X11 sections used by this layout are empty of limits, the user can provide hard-coded limits to match strange or ancient external monitors.

As shipped, this layout establishes a virtual screen size that matches the external device’s resolution. If the run-time resolution is changed (as with xvidtune) to a smaller resolution, the smaller resolution can be smoothly panned across the full virtual screen.

The layout has a commented out, virtual size option in the named “Screen” section with which the user can set a larger virtual screen size.

The layout has the “Simultaneous” option set to “false” in the named “Screen” section, setting it to “true” removes the mouse pointer from the LCD display.

5 Installation

The downloadable file is (xorg.mini.gz http://morethan.org/mini-note/xorg.mini.gz)

Enjoy.

6 Defaults

It is possible to run X11 without any configuration file at all. Many of the X11 configuration utilities are based on that feature.

The current Chrome9-beta package is missing a few file changes to make that work.

6.1 Correcting Autodetect

Using a text editor as the admin user (root);

6.2 Generating the default layout

You will want an external keyboard and mouse to run the following in case the internal devices are not properly setup.

Presuming you do not have a file named “dummy” in any of the places that X11 searchs and that you do not have a file named “.viavideorc” in your home directory;

Boot to command line mode (whatever your boot menu calls that);

Enter the command:

startx -- -config dummy

Just enter “exit” from the resulting xterm. You will need your mouse and keyboard working to do that, the reason for the external mouse and keyboard.

6.3 X11R7-Chrome9-Beta Defaults

I have posted the results of the AutoDetect run log output http://morethan.org/mini-note/xorg.no-conf-none-chrome9.log generated.

This default output can be compared with the output of the same command and future versions of the driver to help detect driver changes.

The driver options are listed in the file viax.conf of the driver package.