The first and most efficient thing to do, is for you to eyeball it. Seriously, if you were helpless you wouldn't have gotten this far. Look at the file. Look for anything which screams, "I'm broken! I''m broken!" The wiki page has several hints on what that means. Cut and paste the relevant sections. The X logs are very verbose and chatty, and genrally quite readable.

just to make sure i should type in



i'm not sure what your mean by cut and paste but i will handwrite anything that looks fishy[/code]

Cut & paste with your mouse, window to window. Like highlight source, Ctrl-C, click at destination, Ctrl-V in MS-Windows. This is "How to use a Computer" 101 stuff.

If you haven't gotten your KnoppMyth box set up for remote access yet, you're overdue. http://www.knoppmythwiki.org/index.php?page=RemoteAccessfromWindows

well i guess i set it up for remote access next, now here is everything that looked suspect, hand copyed by me





i have no idea what any of this means just that it looks like an issue

See, I told you that you could do it. Looks like your config file is corrupted, so rather than potentially doing damage X gave up. So now all you have to do is edit your /etc/X11/XF86config-4 file and fix that section.

- Search for Section "Files" the second line down from that is where your problems shows up. That line should either look like this:

or like this (commented out):


- Since that directory doesn't exist anyway you might as well just delete it.

- The syntax of the XF86config-4 file is really pretty simple if you look at it with the right eye.

The # character starts a comment that runs until the end of the line. Tokens are seperated by whitespace. Double quote characters " are used to delimit strings. The basic chunk is:

Section "SectionName"
Stuff here
EndSection

Within each of those sections is a list of lines each of which starts with a keyword and followed by one or more arguments. You can also have a SubSection "SubSectionName" ... EndSubSection block nested inside a section. Anything that doesn't follow those rules is probably broken. OBTW - case probably matters, so make sure it matches.

ok, i will try that, but i am wondering how something small like a font file would cause the GUI to not work

You have utterly missed the point. Something _major_ like a botched configuration file is causing it not to work. It's only got the one configuration file, so if it's roached the server really doesn't have much choice.