rhl22.htm

linux的初学电子书

<BR>

<HR ALIGN=CENTER>

</BLOCKQUOTE></BLOCKQUOTE>

<BLOCKQUOTE>

<BLOCKQUOTE>

<HR ALIGN=CENTER>

<BR>

<NOTE>Ensure that the kernel bus mouse driver is using the same IRQ as the bus mouse. If not, you have to change the IRQ and rebuild the kernel. The IRQ for bus mouse devices is given in /usr/src/linux/include/linux/busmouse.h. The macro MOUSE_IRQ contains 
this IRQ and is set to 5 by default.</NOTE>

<BR>

<HR ALIGN=CENTER>

</BLOCKQUOTE></BLOCKQUOTE>

<P>The following is a list of device names for the mouse selection:

<BR>

<UL>

<LI>/dev/inportbm Use for the Microsoft bus mouse. Note that this uses the bus mouse protocol, not the Microsoft protocol.

<BR>

<BR>

<LI>/dev/logibm Use this for the Logitech bus mouse. Note that this uses the bus mouse protocol, not the Logitech protocol.

<BR>

<BR>

<LI>/dev/psaux Select for a PS/2 or quick port mouse. This uses the PS/2 protocol.

<BR>

<BR>

<LI>/dev/atibm For the ATI XL bus mouse. Note that the ATI GU bus mouse is a Logitech or Microsoft bus mouse, depending on the version you have.

<BR>

<BR>

<LI>Other supported mice are serial mice; therefore, the device names are the same as the serial devices (/dev/ttyS? or /dev/ttyS?? for Linux).

<BR>

<BR>

</UL>

<BLOCKQUOTE>

<BLOCKQUOTE>

<HR ALIGN=CENTER>

<BR>

<NOTE>If you have a two-button mouse, you might want to emulate the third button by setting Emulate3Buttons in the mouse section. Emulation is accomplished by pressing both buttons simultaneously. There are quite a number of other settings available, but 
they usually are not needed. Look at the XF86Config man page for a list of available settings.</NOTE>

<BR>

<HR ALIGN=CENTER>

</BLOCKQUOTE></BLOCKQUOTE>

<P>You have to select one type of mouse and its baud rate if it's serial. Note in Listing 22.3 that I have &quot;uncommented&quot; the Microsoft mouse selection for my mouse and the 1200-baud rate line, and you will have to uncomment the line that matches 
your mouse selection. The 1200-baud rate seems to work fine with older mice and using the 9600 rate did not result in a speed difference for newer mice. Your results may vary.

<BR>

<P>

<FONT COLOR="#000080"><B>Listing 22.3. Mouse selection.</B></FONT>

<BR>

<PRE>

<FONT COLOR="#000080">#

Section &quot;Pointer&quot;

# Mouse definition and related parameters

#

#MouseSystems &quot;/dev/mouse&quot;

Microsoft &quot;/dev/mouse&quot;

#MMSeries &quot;/dev/mouse&quot;

#Logitech &quot;/dev/mouse&quot;

#MouseMan &quot;/dev/mouse&quot;

#Busmouse &quot;/dev/mouse&quot;

BaudRate 1200

# BaudRate 9600

# SampleRate 150

# Emulate3Buttons

... &lt;deleted some stuff here &gt; ...

EndSection</FONT></PRE>

<BR>

<A NAME="E69E279"></A>

<H4 ALIGN=CENTER>

<CENTER>

<FONT SIZE=4 COLOR="#FF0000"><B>The Server Section</B></FONT></CENTER></H4>

<BR>

<P>If you want to identify the chip set your graphics card uses, run SuperProbe, a program that comes with XFree86 and is capable of identifying a wide range of graphics hardware. Note that SuperProbe can probe far more hardware than XFree86 supports.

<BR>

<P>Listing 22.4 shows a plain setting for a 640&#180;480 monitor for X with a virtual space of 800&#180;600. A virtual space is an area where the display portion of your monitor is mapped onto. Your monitor is a window into this space.

<BR>

<P>

<FONT COLOR="#000080"><B>Listing 22.4. Server selection.</B></FONT>

<BR>

<PRE>

<FONT COLOR="#000080">#

# First the 8-bit color SVGA driver

#

vga256

#

# To disable SpeedUp, use NoSpeedUp

#

# NoSpeedUp

# Virtual 1152 900

# Virtual 800 600

Virtual 640 480

ViewPort 0 0

# Modes &quot;640x480&quot; &quot;800x600&quot; &quot;1024x768&quot;

# Modes &quot;640x480&quot; &quot;800x600&quot;

Modes &quot;640x480&quot;

#

# Next the 1-bit mono SVGA driver

#

vga2

Virtual 800 600

ViewPort 0 0

Modes &quot;640x480&quot;

# Modes &quot;800x600&quot; &quot;640x480&quot;</FONT></PRE>

<BR>

<A NAME="E69E280"></A>

<H4 ALIGN=CENTER>

<CENTER>

<FONT SIZE=4 COLOR="#FF0000"><B>Setting Up Video Modes</B></FONT></CENTER></H4>

<BR>

<P>This is the hardest part. Please read VideoModes.doc before beginning. If you are using ConfigXF86 (which I strongly recommend), and your monitor is not in the database, choose the generic modes and start making your own modes from there. If you do not 
have ConfigXF86, read the tutorial on building modes in the README.Config file.

<BR>

<BLOCKQUOTE>

<BLOCKQUOTE>

<HR ALIGN=CENTER>

<BR>

<NOTE>I know this entire chapter is full of warnings. Please do not be alarmed. Just be careful and read the instructions for each step before taking it.</NOTE>

<BR>

<HR ALIGN=CENTER>

</BLOCKQUOTE></BLOCKQUOTE>

<P>ConfigXF86 includes a neat utility to tune video modes. Because there is no check on the usability of a mode, you have to check the mode data against your monitor's specifications before testing the mode. The first line of the tuning modes screen gives 
you information on the specifications of the mode. You have to continuously check that these values are within your monitor's capabilities before testing that mode.

<BR>

<P>See Listing 22.5 for the common video modes for XFree86.

<BR>

<P>

<FONT COLOR="#000080"><B>Listing 22.5. Video modes.</B></FONT>

<BR>

<PRE>

<FONT COLOR="#000080">Section &quot;Device&quot;

Identifier &quot;Generic VGA&quot;

VendorName &quot;Unknown&quot;

BoardName &quot;Unknown&quot;

ChipSet &quot;generic&quot;

# VideoRam 256

# Clocks 25.2 28.3

EndSection

# **********************************************************************

# Screen sections

# **********************************************************************

# The color SVGA server

Section &quot;Screen&quot;

Driver &quot;svga&quot;

Device &quot;Generic SVGA&quot;

Monitor &quot;Generic Monitor&quot;

Subsection &quot;Display&quot;

Depth 8

Modes &quot;640x480&quot;

ViewPort 0 0

Virtual 800 600

EndSubsection

EndSection

# The 16-color VGA server

Section &quot;Screen&quot;

Driver &quot;vga16&quot;

Device &quot;Generic VGA&quot;

Monitor &quot;Generic Monitor&quot;

Subsection &quot;Display&quot;

Modes &quot;640x480&quot;

ViewPort 0 0

Virtual 800 600

EndSubsection

EndSection

# The Mono server

Section &quot;Screen&quot;

Driver &quot;vga2&quot;

Device &quot;Generic VGA&quot;

Monitor &quot;Generic Monitor&quot;

Subsection &quot;Display&quot;

Modes &quot;640x480&quot;

ViewPort 0 0

Virtual 800 600

EndSubsection

EndSection</FONT></PRE>

<P>The Mode line in a video section can have up to 10 values. Be very careful when modifying these values because a wrong setting may wind up destroying your monitor! It does not matter if these are not present because defaults can be used. A typical line 
to override defaults for a monitor would be:

<BR>

<BR>

<PRE>

<FONT COLOR="#000080">&quot;640x400&quot; 28 640 480 728 776 480 480 482 494</FONT></PRE>

<P>The 10 values in order from left to right are shown in the following section. These values only make sense to video engineers or those folks who have to work with a monitor not defined in the default modes. Check your monitor's hardware specifications 
and get the values from there to fill in these ten parameters. The following are the fields to set:

<BR>

<UL>

<LI>Label for screen resolution; for example, 640&#180;480 or 1024&#180;768.

<BR>

<BR>

<LI>The clock frequency in mHz.

<BR>

<BR>

<LI>The Horizontal Display End in number of visible dots per line on the screen.

<BR>

<BR>

<LI>The Start Horizontal Retrace value. This specifies the number of pulses before the video sync pulse starts.

<BR>

<BR>

<LI>The End Horizontal Retrace value defines the end of the sync pulse.

<BR>

<BR>

<LI>The Horizontal Total value. This is the total number of dots per line invisible and visible.

<BR>

<BR>

<LI>The Vertical Display End value. The number of visible lines on the screen.

<BR>

<BR>

<LI>The Start Vertical Retrace value. The number of lines before the sync pulse starts.

<BR>

<BR>

<LI>The End Vertical Retrace value is the number of lines at the end of the sync pulse.

<BR>

<BR>

<LI>The Vertical Total value. The total number of lines, invisible plus visible, on the screen.

<BR>

<BR>

</UL>

<P>Multiscan monitors handle frequencies of 15 to 40 mHz. Some monitors work at 72 mHz vertical scan to prevent the flicker. You have to be able to calculate the frequency from the monitor's specification and come up with these numbers. A good place to 
start would be the XFree86-HOWTO document on how to get these values. Keep in mind that your video monitor is just a glorified television. You give it wrong values and you can fry it.

<BR>

<BR>

<A NAME="E69E281"></A>

<H4 ALIGN=CENTER>

<CENTER>

<FONT SIZE=4 COLOR="#FF0000"><B>International Keyboard Layout for XFree86</B></FONT></CENTER></H4>

<BR>

<P>XFree86 servers are able to read the key table from the Linux kernel, so you need to set up only one keyboard layout file (for the kernel). There are some restrictions, though; the kernel can support more keyboard functions than X11. X11 can only modify 
one of the four key tables. This modifier is called ModeShift.

<BR>

<P>Configurable keys for the ModeShift modifier are LeftAlt, RightAlt (=AltGr), RightCtl, and ScrollLock.

<BR>

<P>Usually the AltGr key is used for international keyboard modifications. To enable the XFree86 server to read the AltGr key table from the kernel, you should put the following line in the .olvwmrc file:

<BR>

<BR>

<PRE>

<FONT COLOR="#000080">RightAlt &quot;ModeShift&quot;</FONT></PRE>

<P>Besides supporting only one additional key map, X11 cannot use dead keys. A key is called dead if when it is typed, it does not print a character until a second character is typed. A typical example is an accent key. Such keys are not supported by X11, 
so you need to replace all dead-key symbols with non-dead equivalents. Table 22.1 lists what you have to change.

<BR>

<BR>

<P ALIGN=CENTER>

<CENTER>

<FONT COLOR="#000080"><B>Table 22.1. Key symbols.</B></FONT></CENTER>

<BR>



<TABLE  BORDERCOLOR=#000040 BORDER=1 CELLSPACING=2 WIDTH="100%" CELLPADDING=2 >

<TR>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

<I>Dead</I>

</FONT>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

<I>Non-Dead</I></FONT>

<TR>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

dead_tilde

</FONT>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

ASCII tilde</FONT>

<TR>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

dead_grave

</FONT>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

grave</FONT>

<TR>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

dead_circumflex

</FONT>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

ASCII circum</FONT>

<TR>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

dead_acute

</FONT>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

apostrophe</FONT>

<TR>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

dead_diaeresis

</FONT>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

diaeresis</FONT>

</TABLE><P>Instead of supporting dead keys, XFree86 supports a Compose key. This feature is described in the XFree86kbd man page and can be modified by assigning the Compose function to one of the keys. By default the ScrollLock key has the Compose 
function.

<BR>

<P>If you still want to have the dead keys on the console, you will have to use an xmodmap file to map the keys to the correct symbols under X. This is also the method that must be used with earlier versions of XFree86. On sunsite in the directory 
/pub/Linux/X11/misc, you can find sample xmodmap files for several languages. Note that you have to set the ModeShift modifier to get the right key table working.

<BR>

<P>Please read the kbd.FAQ that comes with the kbd package for Linux. You will find many hints for modifying your keyboard layout on the console, as well as for X.

<BR>