From: Ray Olszewski <ray@comarre.com>
To: linux-newbie@vger.kernel.org
Subject: Re: switching to debian (... and installing the NVIDIA GeForce4)
Date: Fri, 26 Mar 2004 07:37:17 -0800 [thread overview]
Message-ID: <5.1.0.14.1.20040326071220.01f71e80@celine> (raw)
In-Reply-To: <Pine.LNX.4.44.0403260110390.26709-300000@legolas.personal. engin.umich.edu>
At 01:30 AM 3/26/2004 -0500, Karthik Vishwanath wrote:
>make is (was) installed.
>
>sh NVIDIA-Linux-x86-1.0-5336-pkg1.run --kernel-name=2.4.18-k7, did not
>work.
>
>So, I obtained NVIDIA-Linux-x86-1.0-4363.run from nvidia.com, and ran as:
>sh NVIDIA-Linux-x86-1.0-4363.run --kernel-name=2.4.18-k7, and this worked
>(seemingly).
>
>I set my X driver to be nvidia (as indicated) but could not startx.
>
>I tried: # modprobe nvidia and came up with a list of "unresolved
>symbols".
>
>I taken the liberty of attaching both the nvidia-installer.log, as well as
>the output of modprobe nvidia to this message.
>
>Please tell me what to attempt next.
In general, this sort of result means one of two things:
1. You failed to load some needed modules before loading nvidia. In this
instance, this appears NOT to be the actual problem, since
(a) the nvidia installer runs "depmod" for you
(b) 0y install of 4363 here indicates that nvidia has no dependencies
2. A kernel mismatch. Since you are trying to use source to add in modules
to a pre-compiled, stock kernel, it is at least possible that this sort of
mismatch is occurring. It MAY be as simple as the kernel cource having a
.config file that does not match the compiled kernel ... I suggest this
only because I see "devfs" mentioned in some of the unresolved symbols, and
from my setup I know nvidia can run with a kernel that does not have devfs
support compiled in.
Anyway, my best GUESS is that you're running into a problem based on your
wanting to use a precompiled kernel, something I have no experience with
(not in the last few years, anyway). I don't know if you are using Woody,
Sarge, or Sid ... I just checked Sid and see that it does not at the moment
have any kernel-image-2.4.18-k7 package but does have a
kernel-source-2.4.18 ... so there may be a version mismatch problem that
derives from image and souce being at different patchlevels *within* 2.4.18
(Debian occasionally does this, mainly as backpatches for security issues).
So, I can only suggest two options.
First, compile a kernel locally and then try to run the nvidia installer
and to install the nvidia module against it.
Two, try using the nvidia-kernel-source Debian package (with make-kpkg) to
see if doing it "the Debian way" solves some hidden problem.
Other than that, you're sufficiently outside my experience that I cannot
offer suggestions. Sorry.
BTW, my running version of nvidia is the same nvidia version number, but
with a bespoke 2.4.19 kernel.
-
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
next prev parent reply other threads:[~2004-03-26 15:37 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
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 [this message]
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.20040326071220.01f71e80@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