Recommended Posts

This guide will give you step-by-step instructions on installing Linux Nvidia Display Drivers.

Just like with the ATi guide, you should make sure that your kernel-source is installed, and correctly symlinked to /usr/src/linux (most rpms should do this for you).

* Remember to kill the X server before installing the drivers. This can be done with ctrl-alt-backspace. If you use a graphical logon manager such as gdm, hit ctrl-alt-backspace, then hit ctrl-alt-f1, then, as root, do a killall gdm.

Nvidia Download Page - Version (1.0-4496)

Supported Nvidia Graphics Cards, under (app-a) APPENDIX A

Download The Drivers - Size (7.81 MB)

Make sure you have XFree86 4.0.1 or higher installed before starting (latest version to this date is 4.3.1):

XFree86 --version

- I am going to assume that you placed the downloaded drivers into your /tmp directory for this guide.

- You want to be outside of the 'X' server to install these drivers (as noted above).

- From here, you should be at the command line prompt and you've logged in as root.

Change directory (to where the drivers are located):

cd /tmp

Installation:

sh NVIDIA-Linux-x86-1.0-4496-pkg2.run

- Follow the onscreen instructions (mainly pressing Yes/OK to all the prompts).

- You will be asked a question regarding compiling the Kernel, so let it do that for you. With me, a little error message appeared saying that my kernel isn't compiled for this (or something to that affect)...but the good news is that it will download an update from their FTP server and automatically configure it for you.

- That's it, all done. When the installation has completed, I would recommend rebooting your PC - just to make sure that all went well.

Now you will need to edit a single line from a file named XF86Config before the new drivers will work (/etc/X11/XF86Config):

If you already have an XF86Config file working with a different driver (such as the 'nv' or 'vesa' driver), then all you need to do is find the relevant Device section and replace the line:

Driver "nv" (or Driver "vesa")

with 

Driver "nvidia"

In the Module section, make sure you have:

Load "glx"

You should also remove the following lines:
    
Load "dri"
Load "GLcore"

Useful Driver Update Commands

Log in as root (or "su" from a terminal point) and run one of the commands below in any directory you're in:

nvidia-installer --latest
nvidia-installer --update
nvidia-installer --uninstall

What do they do?

--latest (Displays a record of the latest drivers available)
--update (Same as "--latest", but auto-installs the latest ones for you)
--uninstall (I think you can figure this one out)

Common Problem (Kernel Upgrade)

Q: I just upgraded my kernel, and now the NVIDIA kernel module won't load. What's wrong?

A:The kernel interface layer of the NVIDIA kernel module must be compiled specifically for the configuration and version of your kernel. If you upgrade your kernel, then the simplest solution is to reinstall the driver.

ADVANCED:

You can install the NVIDIA kernel module for a non running kernel (for example: in the situation where you just built and installed a new kernel, but haven't rebooted yet) with a command line such as this:

sh NVIDIA-Linux-x86-1.0-4496-pkg1.run --kernel-name='KERNEL_NAME'

Where 'KERNEL_NAME' is what `uname -r` would report if the target kernel were running.

* This guide worked for me with no problems on (Red Hat 9 / Kernel 2.4.20-20.9 / XFree86 4.3.0 / GeForce 2 Pro / TFT & CRT Monitors).

* Some of the quotes/notes were taken from Nvidia's README file & from the ATi Guide.

Link to comment
https://www.neowin.net/forum/topic/102655-nvidia-drivers/
Share on other sites

  • 2 weeks later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I always thought the moon gets a lot of impact because there’s no atmosphere, so surely building a moon base is only going to end in disaster?
    • Gets them every time !  
    • This piece of ###### is probably one of the most hated apps that ever existed.
    • Microsoft is bringing a much-needed Recap app to Teams, here is a first look by Usama Jawad Microsoft Teams is heavily used in work and school environments, and perhaps one of its core but extremely useful features is the ability to record meetings. In past years, Microsoft has further improved upon this functionality by integrating AI, but you do need a Microsoft 365 Copilot license to leverage most, if not all, all of those capabilities. Now, the Redmond tech firm is making another significant enhancement in the area of Teams meeting recordings. Up until now, if you wanted to access Teams recordings, you had to arduously locate the meeting invite and navigate to the dedicated tab, or go to the cloud storage location such as a SharePoint site. This was a rather overwhelming activity, especially if you don't remember the name of the meeting or the meeting occurred quite a while ago. Microsoft is now attempting to solve this problem through a dedicated Recap app that consolidates all your recordings. This centralized experience will allow users to find all recordings from the past 30 days and also offer access to other related services such as transcripts and AI-powered summaries. Customers will have the option to search for recordings, filter them, and review multiple meetings by generating AI-powered podcast-style recaps. The Recap app will list all available recordings in both thumbnail and list views. The former is shown below: And here is how Teams users with a Microsoft 365 Copilot license can select multiple recordings to generate a podcast-style audio recap: Microsoft has emphasized that the Recap app is pre-installed in Teams but it will not be pinned by default. Users will able to navigate to the Teams app store from the left rail, and pin it from the apps section. It will be enabled by default for all users once it becomes available. It's worth noting that while Teams recordings and transcripts can be accessed by all users governed by existing permissions, AI-powered features like intelligent summaries, audio recaps, and video recaps will require a Microsoft 365 Copilot license. The Recap app will be generally available to Teams users on Windows, Mac, and the web by the end of next month, with mobile support coming soon.
    • It's so stupid that you have to "enroll" in these extended updates.
  • Recent Achievements

    • Week One Done
      tuben earned a badge
      Week One Done
    • First Post
      OffsetAbs earned a badge
      First Post
    • Reacting Well
      OffsetAbs earned a badge
      Reacting Well
    • First Post
      Kolakid60 earned a badge
      First Post
    • Week One Done
      xvvxcvv earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      427
    2. 2
      +Edouard
      184
    3. 3
      PsYcHoKiLLa
      151
    4. 4
      FloatingFatMan
      71
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!