rhl21.htm

linux的初学电子书

<LI>Additional libraries. Sometimes you need additional libraries to run binary distributions or to compile an application. If the former is the case, you should find a pointer to that library in the README file of that package. If you do not have a 
pointer, you should look at the /pub/Linux/libs hierarchy at sunsite. Most libraries that work on Linux can be found there. If you cannot find it there and you have Internet access, follow the instructions on getting information in <A 
HREF="rhlxa.htm" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/rhlxa.htm">Appendix A</A>, &quot;Linux FTP Sites and Newsgroups.&quot;

<BR>

<BR>

<LI>Other X11 applications. There are many programs and applications available for X, way too many to list here. Look through the /pub/Linux/X11 hierarchy on <A HREF="tppmsgs/msgs0.htm#72" tppabs="ftp://sunsite.unc.edu/">sunsite.unc.edu</A> for ports with many Linux packages. Most 
programs need no changes to run on Linux, so look at the generic X11 program archives, as well as at the Linux-specific sites. One of the largest X11 sites is <A HREF="tppmsgs/msgs0.htm#79" tppabs="ftp://ftp.x.org/">ftp.x.org</A>. In the /R5contrib directory you can find many programs 
for X11.

<BR>

<BR>

</UL>

<BR>

<A NAME="E68E148"></A>

<H3 ALIGN=CENTER>

<CENTER>

<FONT SIZE=5 COLOR="#FF0000"><B>Compiling Programs That Use X</B></FONT></CENTER></H3>

<BR>

<P>Please read the GCC-FAQ file. This is on the F series of the installation disks and CD-ROM. This file can also be found in the /pub/Linux/docs/faqs directories of sunsite before compiling any programs. Many questions on compiling programs with Linux are 
answered in this FAQ. Many Linux distributions include the most relevant FAQs in the directory /usr/doc, so you might look there first.

<BR>

<P>If you have the source code for a program that uses X11, it usually is shipped with an Imakefile instead of a Makefile.

<BR>

<P>Imakefiles are files that create Makefiles for your system. Discussing Imakefiles is beyond the scope of this book; however, you have to work with Imakefiles if you work at all with X sources. Just remember the shell script xmkmf, and you should be 
okay.

<BR>

<BLOCKQUOTE>

<BLOCKQUOTE>

<HR ALIGN=CENTER>

<BR>

<NOTE>The xmkmf shell script actually runs the imake command with a set of arguments. The most common argument is the -DUseInstalled argument. If you examine xmkmf, (look in /usr/bin/X11/imake), you will see that the xmkmf script is a basic wrapper around 
a call to imake. It's very tempting to use imake on a command line by itself. Do not do so. Run the imake command with the -DUseInstalled argument if you must run imake on the command line. If you do not use this argument, imake will behave as if it were 
re-creating the X Window system on your current directory.</NOTE>

<BR>

<HR ALIGN=CENTER>

</BLOCKQUOTE></BLOCKQUOTE>

<P>Of course, before ever running xmkmf, you should have read the documentation that usually comes with such packages.

<BR>

<P>Run xmkmf in the directory that contains the Imakefile. If there is a hierarchy of directories with Imakefiles, you usually only have to run xmkmf in the root directory of that hierarchy.

<BR>

<P>The xmkmf command builds the Makefiles in all directories in the hierarchy.

<BR>

<P>Then you should run the make command with an argument to let make resolve its dependencies with the following command:

<BR>

<BR>

<PRE>

<FONT COLOR="#000080">$ make depend</FONT></PRE>

<BLOCKQUOTE>

<BLOCKQUOTE>

<HR ALIGN=CENTER>

<BR>

<NOTE>Don't be afraid if include files such as stddef.h, varargs.h, and so on, are not found. They are gcc proprietary header files and therefore not in the standard include directories.</NOTE>

<BR>

<HR ALIGN=CENTER>

</BLOCKQUOTE></BLOCKQUOTE>

<P>After that, you can make the program by running make, and you can install your new utility (usually in /usr/X11R6/bin) by running

<BR>

<BR>

<PRE>

<FONT COLOR="#000080">$ make install</FONT></PRE>

<P>The installation of the man pages is done by running

<BR>

<BR>

<PRE>

<FONT COLOR="#000080">$ make install.man</FONT></PRE>

<BR>

<A NAME="E68E149"></A>

<H3 ALIGN=CENTER>

<CENTER>

<FONT SIZE=5 COLOR="#FF0000"><B>Finding Information on X and XFree86 on the Net</B></FONT></CENTER></H3>

<BR>

<P>There is an excellent document about XFree86 on the Internet by Matt Welsh, called &quot;The Linux XFree86 HOWTO&quot; document. This document will make an excellent resource for you as you install XFree86.

<BR>

<P>The ASCII version of this HOWTO document will be posted regularly to <A HREF="tppmsgs/msgs0.htm#80" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/comp.os.linux.announce">comp.os.linux.announce</A>, <A HREF="tppmsgs/msgs0.htm#81" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/comp.windows.x.i386unix">comp.windows.x.i386unix</A>, <A HREF="tppmsgs/msgs0.htm#82" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/news.answers">news.answers</A>, and <A 
HREF="tppmsgs/msgs0.htm#83" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/comp.answers">comp.answers</A>. The latest version can be found on <A HREF="tppmsgs/msgs0.htm#72" tppabs="ftp://sunsite.unc.edu/">sunsite.unc.edu</A> in the directory /pub/Linux/docs/HOWTO. This document will almost certainly be more current than any printed material because the 
electronic version is constantly updated.

<BR>

<P>For general X questions, you should read the FAQ and the FAQ-Xt. You can get these from <A HREF="tppmsgs/msgs0.htm#79" tppabs="ftp://ftp.x.org/">ftp.x.org</A> in the directory /R5contrib. Many Linux distributions include most relevant FAQs in the directory /usr/doc. Look on the 
CD-ROM for this directory.

<BR>

<P>If you have questions about the XFree86 package and cannot find an answer in the documentation files (XFree86, XF86Config, XF86_* manpages, or the README files in /usr/X11R6/lib/X11/doc), you may want to post a question to a newsgroup. The appropriate 
newsgroup for that purpose is <A HREF="news:comp.windows.x.i386unix">comp.windows.x.i386unix</A>. This newsgroup is dedicated to the XFree86 system. If you have a problem with the server and want to post a question to this newsgroup, you should provide 
enough information for those that want to help you. Here are some things that should be included in all postings concerning server problems:

<BR>

<UL>

<LI>The operating system and which release you are running.

<BR>

<BR>

<LI>Hardware you have (at least bus type [ISA/EISA/VLB/PCI], your graphic card including chip set, video RAM type #[D/VRAM], size, and speed).

<BR>

<BR>

<LI>A concise description of the problem.

<BR>

<BR>

<LI>A printout of the server startup (you can generate that by running startx 2&gt;1 &gt; Xerror.log or startx &gt;&amp; Xerror.log depending on whether you use a Bourne shell or C shell derivative.

<BR>

<BR>

<LI>The used parts of the XF86Config. (It is not a good idea to include all lines commented out by a leading #.) This would be the largest part of your post, and most people will already know the copyright statements.

<BR>

<BR>

<LI>A list of fixes you have already attempted.

<BR>

<BR>

</UL>

<P>Bug reports or questions on XFree86 can be sent directly to [e-mail]. This is the contact address of The XFree86 Project.

<BR>

<BR>

<A NAME="E69E275"></A>

<H4 ALIGN=CENTER>

<CENTER>

<FONT SIZE=4 COLOR="#FF0000"><B>Newsgroups</B></FONT></CENTER></H4>

<BR>

<P>There are some other newsgroups that cover X-related topics:

<BR>

<UL>

<LI><A HREF="news:comp.windows.x.apps">comp.windows.x.apps</A>&#151;X applications

<BR>

<BR>

<LI><A HREF="news:comp.windows.x.intrinsics">comp.windows.x.intrinsics</A>&#151;X-intrinsic toolkit-related information

<BR>

<BR>

<LI><A HREF="news:comp.windows.x.motif">comp.windows.x.motif</A>&#151;Motif extension to X

<BR>

<BR>

<LI><A HREF="news:comp.windows.open">comp.windows.open</A>-look&#151;OPENLOOK and the XView extension to X

<BR>

<BR>

</UL>

<P>Note that most of these groups have FAQ lists that are posted regularly to these groups. As always with regular postings, these can be obtained from <A HREF="tppmsgs/msgs0.htm#84" tppabs="ftp://rtfm.mit.edu/">rtfm.mit.edu</A> via anonymous FTP.

<BR>

<BR>

<A NAME="E68E150"></A>

<H3 ALIGN=CENTER>

<CENTER>

<FONT SIZE=5 COLOR="#FF0000"><B>Some Common Problems</B></FONT></CENTER></H3>

<BR>

<P>Here are some of the problems you might see when you work with XFree86.

<BR>

<UL>

<LI>No windows. All you get is a gray background and no windows. This is due to running without a window manager. Running X only starts the X server, not the window manager. You should use a script shown earlier in startx.

<BR>

<BR>

<LI>Your Logitech serial mouse does not work. The keyword Logitech is reserved for older Logitech serial mice. Use the keyword MouseMan (or Microsoft) for newer mice. Logitech serial mice plugged into a PS/2 port require the keyword PS/2.

<BR>

<BR>

<LI>You get errors about not finding any font files. First check the XF86Config file to see whether the directories in the font path are named correctly and contain fonts. If they are, run mkfontdir in each of those directories to set them up for use with 
X.

<BR>

<BR>

<LI>After leaving X, your screen fonts are not restored. This is a known bug with some servers. There are utilities called runx or restoretext coming with svgalib that can help you in most cases. You can get them from sunsite.unc.edu in the file 
/pub/Linux/libs/graphics/svgalib-1.2.10.tar.gz.

<BR>

<BR>

<LI>You will have some problems with the Diamond, Compaq AVGA, and S3 cards. This is what you have to live with when you are dealing with freeware.

<BR>

<BR>

<LI>The server dies with the message Cannot find a free VT. XFree86 needs a free virtual terminal (VT) on which to run. So if you have put a getty process on every virtual console in your /etc/inittab, XFree86 is not able to start. The common practice is 
to leave /dev/tty8 (for kernel messages) and /dev/tty7 (for XFree86) free of a getty process.

<BR>

<BR>

</UL>

<P>This is not an exhaustive list. Please read the HOWTO documents in /doc/HOWTO on the CD-ROM for more information about other video card problems that are too specific to list here.

<BR>

<BR>

<A NAME="E68E151"></A>

<H3 ALIGN=CENTER>

<CENTER>

<FONT SIZE=5 COLOR="#FF0000"><B>Supported Hardware</B></FONT></CENTER></H3>

<BR>

<P>Currently, XFree86 Version 3.1.2 supports the following chip sets in the XF86_SVGA server. The list will be much much longer by the time this book hits the stands, so use the following list as a guideline:

<BR>

<P>Nonaccelerated chip sets:

<BR>

<UL>

<LI>Tseng ET3000, ET4000AX, ET4000/W32

<BR>

<BR>

<LI>Western Digital/Paradise PVGA1, WD90C00, WD90C10, WD90C11, WD90C24, and WD90C30

<BR>

<BR>

<LI>Genoa GVGA

<BR>

<BR>

<LI>Trident TVGA8800CS, TVGA8900B, TVGA8900C, TVGA8900CL, TVGA9000, TVGA9000i, TVGA9100B, TVGA9200CX, TVGA9320, TVGA9400CX, and TVGA9420

<BR>

<BR>

<LI>ATI 28800-4, 28800-5, 28800-6, 28800-a

<BR>

<BR>

<LI>NCR 77C22, 77C22E, 77C22E+

<BR>

<BR>

<LI>Cirrus Logic CLGD6205, CLGD6215, CLGD6225, CLGD6235

<BR>

<BR>

<LI>Compaq AVGA

<BR>

<BR>

<LI>OAK OTI067, OTI077

<BR>

<BR>

<LI>Cirrus CLGD5420, CLGD5422, CLGD5424, CLGD5426, and CLGD5428 chip sets

<BR>

<BR>

<LI>Western Digital WD90C31 chip sets

<BR>

<BR>

</UL>

<P>These chip sets are all supported in 256-color (XF86_SVGA) and in monochrome mode (XF86_Mono) with the exception of the Cirrus chip sets, which are only supported in 256-color mode.

<BR>

<BLOCKQUOTE>

<BLOCKQUOTE>

<HR ALIGN=CENTER>

<BR>

<NOTE>If you have a grayscale display, you have to run the color server because grayscale behaves just like color, not like monochrome.</NOTE>

<BR>

<HR ALIGN=CENTER>

</BLOCKQUOTE></BLOCKQUOTE>

<P>The monochrome server also supports generic VGA cards (using 64KB of the video memory as a single bank), the Hercules card, and the Hyundai HGC-1280. These drivers are not part of the XF86_Mono server by default. If you want to use these, you have to 
reconfigure your XF86_Mono server using the LinkKit, or of course, the source distribution&#151;but the LinkKit needs less disk space and a shorter compile time.

<BR>

<P>XFree86 supports at least the following accelerated chip sets with separate servers:

<BR>

<UL>

<LI>S3 86C911, 86C924, 86C801, 86C805, and 86C928 supported by the XF86_S3 server

<BR>

<BR>

<LI>ATI mach8 supported by the XF86_Mach8 server

<BR>

<BR>

<LI>ATI mach32 supported by the XF86_Mach32 server

<BR>

<BR>

<LI>ATI Mach64 supported by the XF86_Mach64 server

<BR>

<BR>

<LI>ET4000/W32 supported by the XF86_W32 server

<BR>

<BR>

<LI>IBM 8514/a and true clones supported by the XF86_8514 server

<BR>

<BR>

<LI>S3 Vision864 and Vision964.

<BR>

<BR>

<LI>Weitek P9000.

<BR>

<BR>

</UL>

<P>The hardware that is not currently supported is:

<BR>

<UL>

<LI>TIGA. TIGA will never be supported because it requires licensing materials from TI and may disallow source distributions.

<BR>

<BR>

<LI>Microfield boards. Microfield boards will never be supported because they use proprietary and undocumented custom microcode interfaces.

<BR>

<BR>

<LI>MGA chip sets (Matrox cards).

<BR>

<BR>

</UL>

<P>For some of these chip sets there are specific README files to be found in /usr/X11R6/lib/X11/doc. If there is one for the chip set you use, read it! In these READMEs, the specific options that can be used to configure the server are explained. 
Currently, there are special READMEs for ATI, Trident, Tseng, Western Digital, Cirrus, and manufacturer-specific chip sets.

<BR>

<P>More information on the servers can be found in their man pages. Another place to check is the XFree86-HOWTO file in the sunsite and tsx-11 archives. The HOWTO document will generally be more up-to-date than any printed matter.

<BR>

<BR>

<A NAME="E68E152"></A>

<H3 ALIGN=CENTER>

<CENTER>

<FONT SIZE=5 COLOR="#FF0000"><B>Summary</B></FONT></CENTER></H3>

<BR>

<P>This section covered one of the hardest things you will have to do when installing a package on Linux&#151;installing XFree86. Naturally, all of the possible problems you will face while installing this are too long to list here. After reading this 
chapter, though, you should have an idea of what you are getting yourself into and the general steps you have to take.

<BR>

<P>Do not despair if things don't work out just as the instructions say they will. You should be able to look at the configuration files to determine where the problem is and what might be done to fix it. If nothing works despite your best efforts, you 
have the recourse of knowing where to look for answers in FAQs, newsgroups, and FTP sites on t<A NAME="I2"></A>he Internet for HOWTO and other documents on Linux.

<P ALIGN=LEFT>

<A HREF="tppmsgs/msgs0.htm#21" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/rhl20.htm" TARGET="_self"><IMG SRC="purprev.gif" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/purprev.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Previous Page"></A>

<A HREF="#I0" TARGET="_self"><IMG SRC="purtop.gif" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/purtop.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Page Top"></A>

<A HREF="index-1.htm" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/index.htm" TARGET="_self"><IMG SRC="purtoc.gif" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/purtoc.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="TOC"></A>

<A HREF="rhl22.htm" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/rhl22.htm" TARGET="_self"><IMG SRC="purnext.gif" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/purnext.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Next Page"></A>


</BODY></HTML>