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.
you might have an old version of nv_check.sh, where did u get this file from? a newer version I looked at doesn't even have this message.
anyways you can always edit the nv_check.sh and comment out the "exit" line below that message.
ok, I thought that I was going to feel really dumb after getting a newer version of nv_check.sh - but now I don't feel dumb, just more frustrated
I got the newest version I could find listed in the nvidia forums, it finds the GLX no problem, but the rest of the output is now different:
First lets make sure you don't have the old modules still present
You don't appear to have any conflicting older drivers. Now lets check
if the new driver files are in place...
libGLcore.so.1 => /usr/lib/libGLcore.so.1 (0x4005c000)
All the files seem to exist. Now I'm going to see if your kernel
module is loaded correctly...
the NVdriver kernel module does not seem to be loaded. The 3D
drivers will not work without it...please compile it for your
kernel, set it up to insert the module on boot, then run
this script again.
Remember if you are having trouble compiling the module,
try adding -D_LOOSE_KERNEL_NAMES to the Makefile.
UT2003 is working fine here, so I don't understand the error message very well.
and as far as compiling the module: remember - I installed the drivers from the source rpms...
Ok, just download the nvidia kernel file in .tar.gz format and build it against your new kernel, you'll need the kernel matching headers/source for your new kernel installed first. To get to a graphical login try putting the command to start kdm in /etc/rc.r/rc.local
when i get the login prompt in the shell, if i don't login within 10 seconds or so, i get a "bluescreen" with the message that the xserver couldn't start, and it asks me if i want to go into the configure program... the configure program just brings me into the place where i choose a soundcard - and on the bluescreen the "buttons" that should say "yes" or "no" have some strange ascii characters instead of yes or no.....
1. still get shell login
2. as root i can no longer start kdm (that's a new problem)
3. when i type gdm i get the message that gdm is already running (old problem)
4. logging in as user lets me startx - but i'm stuck in kde (i prefer gnome in RH, because kde screwed up when i upgraded to 3.03)