SlackwareThis Forum is for the discussion of Slackware Linux.
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.
You can also check your /var/log/XF86Config.0.log log file and see whether you are loading glx. You should see something like:
. (II) LoadModule: "glx"
(II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
Originally posted by Viper I Looked in /etc/X11/XF86Config file and it says:
#This loads the GLX module
# Load "glx"
If you notice from above (and if you INDEED have it written like that in your XF86Config), you are NOT loading the glx module because it is commented out. You may want to uncomment the glx loading line (by removing the # from the line), and try running XFree86 again.
Distribution: Slackware 10, Fedora Core 3, Mac OS X
are you root? before you edit it you need to become the super user by typeing 'su' and then the root password. if its not that then read the following.
vi can be a bugger to use. You have to get your head around the fact that it has two distinct modes. One is the command mode where you type stuff into a prompt and it will do stuff (to get to the prompt press the escape key a number of times until the computer beeps at you then enter a colon and you should see one at the bottom of the screen). The other is the insertion mode. press either the insert key on your keyboard or 'i'. this will allow you to type.
btw when you press backspace the cursor will nip back but it keeps the character in place. It will look like it hasn't worked. Just press escape and the offending character will be replaced (or just leave it and the character will not be kept when you save).
After making the changes go into command mode and type 'wq' and it should save it all and drop you back to the command line. You'll need to be root to make these changes since XF86Config is a configuration file in /etc which is all owned by root.
I personally would use an easier text editor (try emacs, pico or nano) since vi is a bit of a bugger to use when you start out.
Hey, Thanks for the help guys, I could only make heads and tails with the
Vi IMproved editor, now it just says that Atlantis does not support the glx extention, so the heck with it, I've got this baby up and running on DSL right now and have a name & Web server to figure out...