[PLUG] Video problem with new PC

[Eitan Tsur]

Or maybe install something like kernel-headers, etc....?

On Wed, Dec 17, 2008 at 7:08 PM, Carlos Konstanski <
ckonstanski at pippiandcarlos.com> wrote:

> On Wed, 17 Dec 2008, Rich Shepard wrote:
>
> > Date: Wed, 17 Dec 2008 18:49:53 -0800 (PST)
> > From: Rich Shepard <rshepard at appl-ecosys.com>
> > Reply-To: "General Linux/UNIX discussion and help;    civil and on-topic"
> >     <plug at lists.pdxlinux.org>
> > To: "General Linux/UNIX discussion and help;  civil and on-topic"
> >     <plug at lists.pdxlinux.org>
> > Subject: Re: [PLUG] Video problem with new PC
> >
> > On Wed, 17 Dec 2008, David Kaplan wrote:
> >
> >> I would have to install it. but I can't see the bottom of some windows
> where
> >> you have to click next.
> >
> > David,
> >
> >   If you visit the nVidia web site and download the linux driver for your
> > card, it installs in text mode. You untar the download and end up with a
> > file having an extension of .run. For my card I have a file called
> > NVIDIA-Linux-x86-177.82-pkg1.run. As root, invoke it and an ncurses
> > interface comes up in the middle of the monitor screen.
> >
> >   Accept the license, respond appropriately to the other prompts, and it
> > will be installed for you. Check, using lsmod, and you should see
> something
> > like this:
> >
> > nvidia               6904916  0
> >
> >   This works for me. If you go this route, keep that *.run file because
> you
> > may need to reinstall it each time you reboot the machine. I've no idea
> why,
> > but it's a small enough price to pay.
> >
> > Good luck,
> >
> > Rich
>
> Not to confuse the issue, but you probably should know about this.
> The 2.6.28 kernel contains changes that break both nvidia and fglrx
> drivers.  Nvivia has a patch; perhaps ati does too.  Testing with vesa
> will certainly circumvent this issue.  2.6.28 is super-nosebleed, but
> you did mention fedora.
>
> One reason that you might have to rerun the nvidia driver each reboot
> is because you might be using a distro kernel, and have no
> /lib/modules/`uname -r` directory.  That's where the module goes when
> compiled.  Mine is in /lib/modules/2.6.26.7/video/nvidia.ko.  Building
> a custom kernel is one way to ensure that all the parts are there.
>
> Carlos
> _______________________________________________
> PLUG mailing list
> PLUG at lists.pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
>