Re: [LUG] suse10 nvidia driver

[Simon Robert <simon.robert@xxxxxxxxxxxxxxxxxxxxxx>]

John Botwright wrote:

> On Mon, Dec 26, 2005 at 11:08:47PM -0000, Mike Tidball wrote:
>  
>
> > I just did a complete re-install in case all the failed installs messed 
> > something up.
> > I had exactly the same error.
> > I then did a fresh install using the 5 cd's I downloaded from the Novell 
> > site and the driver went in first time no problems.
> > I installed exactly the same packages both times so there must be a problem 
> > with the Linux magazine DVD.
> > I have spent all night googleing and yahooing and although lots of people 
> > have had identical problems I have yet to come across a fix.
> > I'll just carry on with this version.
> > Mike Tidball 
> >
> >
> >
> > --
> > The Mailing List for the Devon & Cornwall LUG
> > Mail majordomo@xxxxxxxxxxxxx with "unsubscribe list" in the
> > message body to unsubscribe. FAQ: www.dcglug.org.uk/linux_adm/list-faq.html
> >    
>
> Hi Mike
>
> If you get the same error again, try entering the following commands in a
> terminal window;
> which cc
> which gcc
> - that should give you the location of the 'cc' program or shortcut.
>
> I'd be inclined to believe that the 'cc' program installed in a
> nonstandard location, or the nvidia installer (nv/conftest.sh) was looking
> for it in the wrong places :- IIRC, SUSE uses /opt for lots of things,
> which many third-party programs fail to take into account.
>
> Cheers,
> John
>
>  
I don't know anything much about suse, but I have installed the nvidia 
drivers and had the same set of messages you've had. I think the first 
time around I hadn't installed the the source code package for my 
kernel, which in my case was "kernel-source-2.6-2.6.12-12mdk.rpm". The 
libc package was, if I recall correctly, glibc-devel-2.3.5. Once I had 
them it all went really easy. So have a go with installing the 
equivilent packages for suse and see what happens when you try again.

If you've already installed these things, or it still doesn't work when 
you have, like John Botwright says the commands "which gcc" and "which 
cc" should tell you where these compilers are;

                  [simon@frog-2 ~]$ which gcc
                   /usr/bin/gcc
                   [simon@frog-2 ~]$ which cc
                   /usr/bin/cc

Then create symbolic links called cc and gcc in the places where nvidia 
expects them. So if nvidia thinks gcc lives in /usr/bin and really it's 
in /opt/gcc-bin you need to create a link called gcc in /usr/bin. Start 
a shell, go to /usr/bin and enter

         ln -s /opt/gcc-bin/gcc gcc

so that way the nvidia install scripts get what they expect.

Simon



--
The Mailing List for the Devon & Cornwall LUG
Mail majordomo@xxxxxxxxxxxxx with "unsubscribe list" in the
message body to unsubscribe. FAQ: www.dcglug.org.uk/linux_adm/list-faq.html