Configuring the X Window System

  • This document describes how to obtain , Install, configure (configure) XFree86 of Linux system . XFree86 is an enhanced version of Windows x 11r5, mainly in all kinds of support to intel i386 / 486 hard
    Unix system body platform, of course, this also includes the Linux. It currently supports a considerable number of video hardware, and it also
    fixes many mit Standard x windows bugs.
  • The purpose of this document is an attempt to help Linux users how to install and set configuration version of XFree86 2.0, a further
    aim is to answer some questions about the use of x and program

design

Please after reading this document and related files, and then start the installation and start xfree86, so can avoid small
possible hardware damage caused by heart.

  • To see the complete file about xfree86, please refer to the directory under / usr / X386 / lib / X11 / etc
    / usr / X386 / man. Other important files and directories will also be mentioned in this description
  • In addition, this file is not a complete set of XFree86, but we will provide relevant information
    , the main file please refer to: xf86-doc-2.0.tar.gz.
    Other manpages about X11R5 are in: xf86-man-2.0.tar.gz. To see these manpages, you
    can use groff -man *. Man | more or directly set MANPATH to this directory, and then use the
    man, command directly.

What is the X11R5 and XFree86?

X11R5 is for Unix Windows system of the system. x mit Consortium window is raised, and there are
free of copyright, it allows any of the original program is used, as long as the original copyright considerations included into the
go to.
Because x is the Unix system to do business standard Windows system, so there is a considerable number of applications using the x window
which contains free and commercial version of the body.
XFree86 is also a branch of X11R5, mainly supporting several Intel-based Unix and Unix-
like operating systems. XFree86 server portion derived from x386 1.2 edition (which is made public in conjunction with x11r5
shi x server), but most of the newly developed xfree86. From then xfree86-1.3, the most important
change is to accelerate the server; this is a completely new. This version has many new features, efficiency improvements
and some bug improvements.

  • Supported hardware

This is a frequently asked question, do first in this simple explanation. The c urrent version 2.0
supports the following hardware on the XF86_SVGA server:
Non-acceleration cards:
Tseng ET3000, ET4000AX, ET4000 / W32
Western Digital / Paradise PVGA1
Western Digital WD90C00, WD90C10, WD90C11, WD90C30
Genoa GVGA
Trident TVGA8800CS, TVGA8900B, TVGA8900C , TVGA8900CL, TVGA9000
ATI 28800-4, 28800-5, 28800-a
NCR 77C22, 77C22E
Cirrus Logic GLGD5420, CLGD5422, CLGD5424, CLGD6205, CLGD6215,
CLGD6225, CLGD6235
Compaq AVGA (cf the question in the appendix)
OAK OTI067, OTI077
accelerator card:
Cirrus CLGD5426 , CLGD5428
Western Digital WD90C31
NOTE WD90C33 does not work on XFree86-2.0.

These cards support 256 colors (XF86_SVGA) and in monochrome mode (XF86_Mono) except
ATI and Cirrus cards (these two cards only support 256 colors). In addition, ET4000 / W32
only has functions like ET4000, and acceleration functions are not supported.

  • Usually monochrome server also supports VGA card (using an image memory 64k), Hercules card
    and Hyundai HGC-1280 card. But these drivers are not in the XF86_Mono server in.
  • So if you want to use these, you must use LinkKit to reconfigure your XF86_Mono
    server. The appendix mentions how to construct the Hercules mono card.
  • There is an experimental server called the hardware for general VGA card: XF86_VGA16 is a
    16-color server.

XFree86-2.0 has different servers and supports the following hardware:

  • S3 86C911, 86C924, 86C801, 86C805, 86C928 supported by
    the XF86_S3 server
    ATI mach8 supported by the XF86_Mach8 server
    ATI mach32 supported by the XF86_Mach32 server
    IBM 8514 / a and true clones supported by the XF86_8514 server, no
    other hardware is supported, such as Weitek P9000, TIGA, IIT AGX,
    Microfield, the new MGA, etc. None are supported. In future versions,
    we will support these hard bodies. However, TIGA and Microfield like will not be supported, because
    the problem with copyright files.

Be in / usr / X386 / lib X11 under / / etc directory README file for instructions variety of card has a description of the various options and settings.

  • Where can I get XFree86, and what do I need to do to run it?

This section is mainly for Linux executable software.

The executable XFree86-2.0 for Linux can be obtained from ftp to the following places: tsx-11.mit.edu:/pub/linux/packages/X11/XFree86-2.0
or sunsite.unc.edu:/pub/Linux/X11/XFree86 -2.0

  • This software is tarfiles compressed with gzip.

XF86_8514.tar.gz Server for
IBM8514 card XF86_Mach32.tar.gz Server for Mach32 card
XF86_Mach8.tar.gz Server for Mach8 card XF86_Mono.tar.gz Server for
monochrome card
XF86_S3.tar.gz device
server XF86_SVGA.tar.gz SVGA card
XF86_VGA16.tar.gz 16 vga card server
xf86-svr-2.0.tar.gz Server for all the above cards
xf86-bin-2.0.tar.gz Some common user programs
xf86-cfg-2.0.tar.gz XDM configuration files and
chooser xf86-fnt-2.0 tar.gz fonts (all of them)
xf86-kit-2.0.tar.gz Linkkit for building X servers
xf86-lib-2.0.tar.gz Dynamic libraries, bitmaps and minimal fonts
xf86-man-2.0.tar .gz Manual pages (both client + programmer)
xf86-pex-2.0.tar.gz PEX libraries and sample clients
xf86-prg-2.0.tar.gz Static libs, dynamic stubs, configs and
include files
xf86-doc-2.0.tar .gz Documentation and release notes for XFree86 2.0
xf86-doc2-2.0.tar.gz This file contains the manpages for Xconfig that
has mistakenly been left out of the -doc- file. In
addition, libc 4.4.1 or later is required to run Free86-2.0. People with accelerated version of the server
you need at least Linux version or update 0.99pl13.

Other servers such as SVGA, VGA16 and Mono require Linux 0.99pl12 or newer.

  • And you must install install David Engel \ s shared dynamic linker ld.so
    1.3 or newer, which can be found in the following places:
    mirrors of tsx-11 in the / pub / linux / packages / GCC directory.
    Memory requirements It is at least 8 MB and virtual memory 16 MB (SWAP file). In fact, if you carefully
    manage the use of memory, 4 MB can also run. Our recommendation is to have at least 8 MB of memory,
    because the swap method will really hurt performance.

     

  • If you want to run a memory- intensive program, such as gcc; then you should have at least 16 MB of memory and
    16MB of swap. If you
    do not install LinkKit, you must have at least 17 MB of disk space. If it is complete, you need 21 MB.
  • If you remove other servers you don’t need, you should be able to save a few MB. Detailed disk

For requirements, please refer to the description of Simon Cooper in the 00README file.

  • Before installation, please back up the files you have changed in case you need them from time to time.

Please handle as root in the / directory)
permission right you should use umask 022.

If I want to compile XWINDOWS myself, what should I do?

  • you should use Link Kit, because it will be much simpler.
    To add SVGA server driver, you need Link Kit.
    You can find the Link Kit in the directory / usr / X386 / lib / Server / VGADriverDoc.
  • Starting with version 2.0, Configuring XFree86 , all XFree86 files are put together. Use tar to combine them into one file:
    xf86-doc-2.0.tar.gz. You must first obtain this file and read these files Only then
  • The correct configuration of XFree86. Some of the steps beneath, is related to the introduction of some of these documents:
    README.Config This file can be said is a brief description of the configuration of XFree86 home, look at this file, and in accordance with
    its instructions step by step.
  • Next, you must use the man command to check the Xconfig, XFree86 and related server instructions
    (the possible servers are XF86_SVGA, XF86_Mono, XF86_VGA16
    , XF86_S3 , XF86_Mach8 , XF86_Mach32 or XF86_8514). Just look at the first section of the manpage (man 1 xconfig)
  • If you cannot determine what kind of video card, you can use the program to check SuperProbe
    check your video card categories. However, if you have a manual video card, of course, it is based on the instruction’s manual you to do.
  • It should be noted that SuperProbe may not be able to correctly check the type of video card. Of course, in this case, the
    XFree86 server is difficult to operate correctly. And the card types that SuperProbe can check are more than the
    number of types supported by XFree86 server.
  • There are some images that can be functioning at XFree86-2.0 version AccelCards this document is an
    accelerator card. See if your card is listed. Of course, there are some cards may not be one of them, but
    it also can function properly.
  • If you are using XS3, then you should see README.XS3, because it was to join XS3 server
    when there are some changes slightly.
  • Several people have pointed out that some XFree86 configuration problems can be solved by changing the shadowing BIOS
    settings and cacheable area. Since these methods, there are some contradictions; so, I will only
    mention some of the problems may be BIOS settings will appear. If you have a problem, or not mentioned by the bottom
    to find the answer file, then of course, the problem may not be a problem bios setting.

You will need the following information during configuration:
Screen specifications (such as horizontal and vertical frequencies, bandwidth, etc …), this is the most important thing.

  • The name of the card. Some companies will use \ “s3 \” as a synonym for \ “accelerated \”.
  • How much image memory is provided by your card?
  • Your card available dot-clocks are those, or directly to a programmable

This is the most difficult part of the set. There is a description in README.config about how to get this information.
NOTE: The WD90C3x card will have problems during clock probing.
Please use the XFree86-1.3 server to execute the measured clocks and record them in the

  • Xconfig file, then you can run the 2.0 version of the server.
    NOTE: If your RAMDAC processing pixel clocks higher than 110MHz, then
    it may be recent high-end RAMDACs because these are using special way.
    Will be possible, these RAMDACs should not be higher than 85 MHz in the Clock Run
  • The next version should support this hardware. If you are with the current model, with a high speed operation of your RAMDAC, you’ll ruin it. If you have such hardware, please use a speed not higher than 85MHz.
  • The protocol used by the mouse and the connected device. There are listed in the main page in Xconfig available mouse agreements. Below are some device names for mouse connection:
  • / dev / atibm ATI XL busmouse (NOTE: ATI GU busmouse is
    actually, logitech busmouse)
    / dev / logibm for the Logitech busmouse (NOTE: this uses the
    busmouse protocol, NOT the Logitech protocol)
    / dev / inportbm for the microsoft busmouse
    / dev / psaux for a ps / 2 or quickport mouse

NOTE: The names listed above are the new names. Perhaps the old names are still used in the old versions.
new old major minor device number
atibm: bmouseatixl 10 3
logibm: bmouselogitec 10 0
inportbm: bmousems 10 2
psaux: bmouseps2 or ps2aux 10 1

Other mice belong to serial mouse, so they are also connected to some serial ports
like / dev / ttyS ? Or / dev / ttyS ??.

  • busmouse not always easy to see that a device is connected, that is, to determine if
    all the drivers into the kernel, a message appears when you turn and look in the boot
    ,it will tell you it is detected that the busmouse which type. At this point you will know, it
  • Is connected to that device.
    Now look at the README.Config file. If your screen is not in the modeDB.txt file,
  • you should choose a general mode. And make sure that the specifications of the selected mode are among your screen specifications.

If you want to adjust or change a mode, please read VideoModes.doc and follow the instructions to
set it.

  • WARNING: Other people’s Xconfig files may not be suitable for you, because each person’s hardware device is different.

In particular screen mode setting, be sure to determine the specifications of all of your screen, to avoid having the hardware to be damaged.

Configuring the keyboard for non-US-layout Xwindows manager

LET’S BEGIN:

1) If you do not change the original standard settings, the server will automatically activate the US-american keyboard mode

2) If you want different settings, please see the manpage description of xmodmap.

3) In sunsite.unc.edu:/pub/Linux/X11/misc have Xmodmaps Some language keyboard
set instance.

4) There are also several special keys, you can define new correspondence. In Xconfig profile, the complete set advantage
with. Please refer to the XFree86kbd (1) manpage in this regard.

5) tinyX-An x window system based on XFree86, suitable for machines with less ram

6) If your ram is not enough to run XFree86, maybe you can try this stuff.
It is based on XFree86, so the way to configure or set is the same as xfree86.

7) To run tinyX, you must have at least 4 MB RAM and at least 8 MB swap space. The current

8) tinyX there are several versions of the server program to follow instructions on the front of the xfree86-2.0 to choose
select.

the name of the software are as follows:
tinyX-2.0.tar.gz-YYY, YYY the name of the server on behalf of
this software may be made to obtain the nearest station ftp. After obtaining the first set and then untar Xconfig
file, you can also find some of the relevant documents tinyX in the readme directory, the first reading of this file
and then set the Xconfig file.

1) The tinyX file also includes some useful memory saving tips. At least follow some suggestions, you
can also reduce the number of swapping when running tinyX. If you have more than the memory of the implementation
capacity, the system also will be completely locked (in other words, similar

2) to the crash, on most of the situation is only
powered off or press the reset, this is very dangerous), Therefore, before restarting the x
sure, to read that file,
because the tinyX does not contain complete XFree86-2.0, it may encounter when performing, it appears
message program does not exist.

About

Codec Networks provides IT Trainings from EC Council CEH ECSA, LPT, CHFI, Network Security, Penetration Testing, ISACA, ISC2, PECB ISO 27001LA LI, Cisco Networking CCNA CCNP, Linux Administration RHCE, Prog Languages JAVA, Advanced Java, android development. We also offer B2B Industry Solutions and Services in IT | Information|Cyber Security in Delhi NCR India.

View all posts by

Leave a Reply

Your email address will not be published. Required fields are marked *