FedoraThis forum is for the discussion of the Fedora Project.
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 just need to enter export CC=gcc32 AFTER you go to text only mode and BEFORE running the NVIDIA-Linux-x86-1.0-4496-pkg2.run file, works like a charm... there are a few issues with the XFree86-MESA-libgl drivers that you can find info on just google it, especially if your going to run things like UT2003 or anything of the sort
Make certain that you have the "gcc32" package installed, because the kernel is built with a different compiler than most other applications.
Removing the Mesa libs is a good idea for almost everyone. The files other packages depend on are replaced by the nVidia installer, so there is rarely any problem with doing so.
rpm -e --nodeps XFree86-Mesa-libGL
I tried you suggestions using gcc32 etc but the RH9 nVidea drivers don't appear to work with Fedora. The video driver defaulted to "nv" and when I changed it to "nvidea" the PC just locked up on boot/X restart.
You may have just typoed in the post, but you mention changing "nv" to "nvidea" which is incorrect spelling. It should be "nvidia".
There are Fedora RPMs available, and I suggest anyone trying to get the drivers running without using the installer provided or source directly, use these and give the packagers feedback about your success. These should handle some of the issues with Mesa as well, but naturally YMMV.
For more problems after you know its installed and configured right, try disabling apic, acpi, and apm as described in the readme from nVidia. This is a good first step in debugging blank screens and full kernel panic or lockup.
Last edited by LordMorgul; 12-03-2003 at 03:50 PM.
.nptli grabbed the nvidia -glx-1.0.4496-0.fdr.10.1.i686 from http://www2.educ.umu.se/~peter/nvidia/
when i ran it it said i needed kernel module nvidia driver (which i got and installed) and also xfree86 mesa libgl. when i got the mesa rpm and tried to install it, an error came back and said a newer version was already installed
my kernel is the standard with fedora core 1, 2.4.22-1.2115.nptl. the nvidia kernel driver i installed is 2.4.22-1.2129.nptl. did i screw something up?
You have used a kernel driver version that does not match your kernel perfectly, that will not work. You need to use the 2115.nptl kernel driver if that is the kernel you are running, be precise when matching these numbers.
I do not know what RPMs are marked as dependencies in those driver RPMs since I haven't personally used any of them yet.
You can check this using the command:
rpm -qpi --requires packagename.rpm
The packages required by packagename.rpm are listed at the bottom of the output, one per line. If you have installed the packages it requires, but it still errors try reinstalling the packages, then use the --nodeps option to rpm while installing and see how it goes (keep in mind that a dependency error usually does mean things aren't quite right).
Last edited by LordMorgul; 12-08-2003 at 05:13 PM.
first off thank you to all who have helped so far. i have the XFree86-Mesa-libGL-4.3.0-42 already installed from the fedora cd. did the just db thing and it said it was already installed. i have updated my kernel as well to 2.4.22-1.2129 and installed the kernel-source 2129. when i run the run file from nvidia it says no kernel source to compile and if i run the nvidia glx install rpm it says it cant fine libgl?????
maybe i should reinstall. update the kernel, make sure all deps are installed and then try again. funny how installing the nvidia driver works so well on other distros. i have installed it fine on slackware 9.1, suse 9, and mandrake (9.1 not 9.2)
I do think this has been discussed in detail in few other threads, but here is the step anyway:
1. Download the LATEST driver from NVidia website
2. Make sure you have gcc32 installed
3. Go to console terminal (CTL-ALT-F1) and logon as root
4. Shutdown X ($ init 3)
5. Remove XFree86-Mesa-libGL ($ rpm -e --nodeps XFree86-Mesa-libGL)
6. Set env variable CC=gcc32 ($ export CC=gcc32)
7. Run NVidia installer ($ sh NVIDIA-Linux-x86-1.0-4496-pkg2.run) and recompile module
8. Edit /etc/X11/XF86Config as per the readme
9. Install Mesa-libGL db only ($ rpm -ivh --nodeps --justdb XFree86-Mesa-libGL)
10. Restart X ($ init 5)
It works for me and hopefully it will work for you too. Good luck.
I've tried to follow those very good instructions, but had a problem knowing how to edit the XF86Config file from the runlevel 3 command line. So I just restarted X and made the changes to the config file and then restarted system. Black screen. From the log files, it seems loading the newest nvidia driver and modules all goes fine until it (I think) tries to hand it back to the xserver, at which point the initialization fails with the message cannot locate suitable screens. Any suggestions would be appreciated.