__________________________________________________________________
What Radeons are supported?
All Radeons up until 9500/9700 are supported by the native XFree86
drivers; currently, the free drivers do not do 3D for 9500/9700. Your
best bet there is to use ATI's drivers. If you don't want to do that,
then you'll have to do what I did, which is to settle for a 9000.
Explanation provided by Daniel Stone (Thank you)
_____________________________________________________________________
Parse warning on line 102 of section Keyboard in file /etc/X11/XF86Config
Ignoring obsolete keyword "LeftAlt".
Parse error on line 102 of section Keyboard in file /etc/X11/XF86Config
"Meta" is not a valid keyword in this section.
(EE) Problem parsing the config file
(EE) Error from xf86HandleConfigFile()
Fatal server error:
no screens found
A possibility is that you are using an X 3.3.6 formated config file for X
4.x.x (or the reverse)
look at your log file /var/log/XFree86.0.log there you can see whether you
are running X 3.3.6 or
X 4.0.3 (which I believe was the X 4 version for RH 7.0)
If you are running X 4... then you should be using /etc/X11/XF86Config-4 as
a config file
if you are running X 3.3.6 then you should be using /etc/X11/XF86Config
Explanation provided by Lionel Lecoq (Thank you)
_____________________________________________________________
How to mail your XFree86 log file.
pre-supposing DNS and networking are operational enough for you to mail
yourself the logs.
scanpci 2>&1 | sendmail [EMAIL PROTECTED]
cat /var/log/X* | sendmail [EMAIL PROTECTED]
Explanation provided by Brian A. Seklecki (Thank you)
____________________________________________________________
(EE) No devices detected.
When you see this without any other errors in the XFree log file then it
generally indicates one of three things.
1. You are using the wrong driver.
2. Your video card is unsupported.
3. In rare cases when you use an ISA card and don't specify a chipset
you may get this message because the chip is not autodetected.
Explanation supplied by Egbert Eich (Thank you.)
_______________________________________________________________
*** Font 'Fixed'
Fatal server error:
could not open default font 'fixed'
The Xserver needs at least the 'fixed' and the 'cursor' font
to start up successfully. The 'cursor' font is required to
be able to display a cursor symbol, the 'fixed' font is
required so that an application is able to display text
(an error message saying it cannot find the required set of
fonts).
The server checks if these two fonts are present in the FontPath
which can be specified in the configuration file (-> XF86Config(5))
or on the server command line (-> Xserver(1)). If one of the
two fonts isn't present the server fails to start printing
an error message:
Fatal server error:
could not open default font 'fixed'
If you see the above error message please make sure the fontpath
is set correctly. You can find the currently configured path in
the server log file. Please look for lines beginning with:
FontPath set to: ....
If the font path doesn't look like you expect it to be (in a
default installation it is set to the subdirectories in
/usr/X11R6/lib/X11/fonts/) you may edit your XF86Config file.
Make sure that the fontpath directories exist and contain
fonts. Check if all directories contain a file called 'fonts.dir'.
If not you may run 'mkfontdir' in the font directory to create
this file.
Since fonts are listed by their XLFD name in 'fonts.dir' - not
their abbreviated name - a file called 'fonts.alias' needs to
exist in the font directory specifying the mapping of the
abbreviated names to the XLFD names.
In a default installation the both 'cursor' and 'fixed' font exist
in the directory /usr/X11R6/lib/X11/fonts/misc. fonts.alias must
at least contain the line:
fixed -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1
for the 'fixed' font to be found. The files '6x13-ISO8859-1.pcf.gz'
and cursor.pcf.gz need to be present.
Font don't have to live in files in a local directory. They can
be provided by a fontserver running on a remote machine
(-> XF86Config(5), X(7)). If you are using a font server please
make sure it is running, that it is configured correctly and that
it has access to the fonts. The above also applies to the font
directories on font servers.
The default font server for bitmapped fonts shipped with XFree86
is xfs (-> xfs(1)).
Starting with XFree86 4.3 there are plans to build both fonts
into the Xserver.
Explanation supplied by Egbert Eich (Thank you.)
_______________________________________________________________________
What do I do with this .diff file?
A "diff" is the difference between two versions of a set of source files.
You apply it to the "older" of the two versions with a nice utility called
"patch".
The diff file (also called "a patch") is the result of running the utility
called "diff" on two files or two sets of files. It prints the
differences to stdout, which the programmer can choose to look at or to
redirect to a file (which is what happened in this case).
The diff file is human-readable - go have a look to see which files are
changed and how :)
Three great points about diffs:
o it is used to synchronize developers placed all over the world.
Whenever somebody has written a newer version of some code s/he/it
sends the diff file (usually in the so called "unified" format because
most
people find it easier to read). It is pretty clear to the rest if the
changes are worthwhile or not just from reading those diff.
o you can concatenate several diff files to make one big patch:
cat diff1 diff2 diff3 > bigpatch
o you can insert a diff file right in the middle of an email and later
feed it into patch -- which will obediently ignore the text in
your email and just apply the patch!
Linus Torvalds used to export all the emails with interesting patches to
one big file and then apply the whole shebang. You can also "massage"
patch files pretty easily in a text editor if you need to.
man patch should help you with the rest of the details.
Example Usage:
patch -p0 < radeonpatchwhatever.diff
Type the above while in the directory with all the other source code and
then recompile.
Explanation supplied by Peter Finderup Lund (Thank You)
___________________________________________________________________
_______________________________________________
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
