Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
i've never used red hat or fedora, and i really dont know too much much about xservers but some time ago, i started xwindows on a minix3 and a slackware machine, reasons they were not being able to start x server was:
minix3 - no xorg.conf file
slackware - wrong xorg.conf file
for both of system i tried ' xorgconfig ' command and tried different values:
slackware retained its x system in 2 attempts
minix3 - i had to change reserve memory for X by chmem command. i guess they had bug.
so if ur red hat supports xorgconfig command try it.
I never use X on my CentOS server (presumably though), but you should look into the Xorg.log file for information. You should get valid info there and paste the log file contents here. Not the complete file but the portion that might be usable.
Before anything else, it would be useful to know what exact version of X are you using. Also, paste these files on some pastebin service and post the links here so we can review them:
Not being able to find input devices via HAL, nowadays, shouldn't prevent the server from starting. But it seems there's also some problem with your video driver. So, please, post also the output for this command: