From: pa3gcu <pa3gcu@zeelandnet.nl>
To: Karthik <karthikv@Alum.Dartmouth.ORG>
Cc: linux-newbie@vger.kernel.org
Subject: Re: switching to debian (... and installing the NVIDIA GeForce4)
Date: Thu, 25 Mar 2004 21:46:18 +0100 [thread overview]
Message-ID: <200403252146.18504.pa3gcu@zeelandnet.nl> (raw)
In-Reply-To: <200403252106.04253.pa3gcu@zeelandnet.nl>
On Thursday 25 March 2004 21:06, pa3gcu wrote:
> After all if you read;
> ftp://download.nvidia.com/XFree86/Linux-x86/1.0-5336/README
> You will see that my examples are written there, they are not there for the
> duration, they are there to help you.
I am glad i did not write this README, i have just discovered a somewhat BAD
and rather misleading point, in that readme which i decided to study just to
make sure i got my facts correct, i see the following under section;
sec-04 (if the file is in an editor its +/- line 772)
It says;
cd /lib/modules/`uname -r`/build/
cp configs/kernel-2.4.18-i686-bigmem.config .config
make mrproper oldconfig dep
It an example for redhat but the problems is universal as it concerns
'make mrproper'
make mrproper removes .config meaning if one follows that example ALL will
fail misarably as kernel defaults contained in the different kernel Config.in
files will be used and i can assure you thats not much.
I will send a report to nvidia about it.
--
If the Linux community is a bunch of theives because they
try to imitate windows programs, then the Windows community
is built on organized crime.
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/
-
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-25 20:46 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 [this message]
[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
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=200403252146.18504.pa3gcu@zeelandnet.nl \
--to=pa3gcu@zeelandnet.nl \
--cc=karthikv@Alum.Dartmouth.ORG \
--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