public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Ray Olszewski <ray@comarre.com>
To: linux-newbie@vger.kernel.org
Subject: Re: switching to debian (... and installing the NVIDIA  GeForce4)
Date: Thu, 25 Mar 2004 10:25:24 -0800	[thread overview]
Message-ID: <5.1.0.14.1.20040325092417.01f19cb8@celine> (raw)
In-Reply-To: <Pine.LNX.4.44.0403251127320.26064-200000@legolas.personal. engin.umich.edu>

At 11:46 AM 3/25/2004 -0500, Karthik Vishwanath wrote:
>I tried adding/removing spaces from the Makefile and I still cannot get
>'sh NVIDIA-Linux-x86-1.0-5336-pkg1.run' to function alright. I did
>download NVIDIA-Linux-x86-1.0-5336-pkg1.run from nvidia's website and have
>not installed the Debian package nvidia-kernel-source.
>
>'uname -r' gives 2.4.18-k7. The Makefile in /usr/src/linux at its top
>reads:
>
>VERSION = 2
>PATCHLEVEL = 4
>SUBLEVEL = 18
>EXTRAVERSION =-k7
>
>I have attached the nvidia-installer.log as an attachment (as its about
>~2K). I could'nt spot anything significant in that log -- perhaps my eyes
>are unfamiliar wrt to what to seek...
>
>I did not follow Richards suggestion below since the untarring of the
>zipped source did create /usr/src/kernel-source-2.4.18/.

Hmmm ... the log itself is not very informative, and I find that the 
specific error message you're getting does not appear anywhere in the older 
nvidia package I have here ... at least not in any form that "grep" or 
"strings" can find.

Tracking this down involves looking at the source for the nvidia-installer. 
It turns out that this is a 2.6 change ... apparently 2.4.x modules are 
named nvidia.o, while 2.6.x modules are named nvidia.ko, and the installer 
is trying to figure out which name to use. For some reason, the function 
build_kernel_module() is not getting a usable value for this choice.

This is the code fragment that's burning you:

     cmd = nvstrcat("cd ", p->kernel_module_build_directory,
                    "; make print-module-filename", NULL);

     ret = run_command(op, cmd, &p->kernel_module_filename, FALSE, 0, FALSE);

     free(cmd);

     if (ret != 0) {
         ui_error(op, "Unable to determine the NVIDIA kernel module 
filename.");
         /* XXX need more descriptive error message */
         return FALSE;

(Note the comment near the end. I second it.)

  Why this fails is not readily apparent. The first thing to check, I 
suppose, is that you have "make" installed on your system. If not, install 
it ("apt-get install make").

If that's not it, try pecifying the kernel name as a command-line option. 
It's something like the following:

         sh NVIDIA-Linux-x86-1.0-5336-pkg1.run --kernel-name=[KERNELNAME]

replacing [KERNELNAME] with the actual name.

If neither of these tactica work, consider dropping back to an eariler 
version of the NVIDIA package, one known to work with 2.4.x kernels (like 
the 4363 I have working here with a bespoke 2.4.19 .



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  parent reply	other threads:[~2004-03-25 18:25 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-25 14:46 switching to debian (... and installing the NVIDIA GeForce4) Karthik Vishwanath
2004-03-25 16:15 ` pa3gcu
2004-03-25 16:28   ` Ray Olszewski
2004-03-25 16:46     ` Karthik Vishwanath
2004-03-25 20:06       ` pa3gcu
2004-03-25 20:46         ` pa3gcu
     [not found]     ` <Pine.LNX.4.44.0403251127320.26064-200000@legolas.personal. engin.umich.edu>
2004-03-25 18:25       ` Ray Olszewski [this message]
2004-03-26  6:30         ` Karthik Vishwanath
     [not found]         ` <Pine.LNX.4.44.0403260110390.26709-300000@legolas.personal. engin.umich.edu>
2004-03-26 15:37           ` Ray Olszewski
2004-03-25 20:20     ` pa3gcu
2004-03-25 20:25     ` pa3gcu
     [not found] <001b01c413c4$621f4230$130aa8c0@pipotiy3ljnut2>
2004-03-27  7:19 ` pa3gcu
2004-03-27  7:57   ` pa3gcu
     [not found] <Pine.LNX.4.44.0403250945300.26064-100000@legolas.personal. engin.umich.edu>
2004-03-25 15:42 ` Ray Olszewski
2004-03-25 16:07   ` pa3gcu
2004-03-25 16:40     ` Ray Olszewski
2004-03-25 19:36       ` pa3gcu
  -- strict thread matches above, loose matches on Subject: below --
2004-03-23  2:32 Karthik Vishwanath
2004-03-23  3:17 ` joy
2004-03-23  4:44   ` Karthik Vishwanath
2004-03-23 14:49     ` pa3gcu
     [not found]   ` <Pine.LNX.4.44.0403222314190.23426-100000@legolas.personal. engin.umich.edu>
2004-03-23  5:12     ` Ray Olszewski
2004-03-23 17:19       ` joy
2004-03-23 17:45         ` Ray Olszewski
2004-03-24 13:17           ` joy
2004-03-24 16:55             ` Ray Olszewski
2004-03-26 11:13               ` joy
2004-03-23 19:59         ` pa3gcu
2004-03-24 13:22           ` joy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5.1.0.14.1.20040325092417.01f19cb8@celine \
    --to=ray@comarre.com \
    --cc=linux-newbie@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox