From: "J . A . Magallon" <jamagallon@able.es>
To: Josh McKinney <forming@home.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.13-pre6 breaks Nvidia's kernel module
Date: Wed, 24 Oct 2001 00:51:07 +0200 [thread overview]
Message-ID: <20011024005107.A3988@werewolf.able.es> (raw)
In-Reply-To: <200110221846.f9MIkE416013@riker.skynet.be> <3BD532EC.6080803@eisenstein.dk> <20011023130756.A742@cy599856-a.home.com>
In-Reply-To: <20011023130756.A742@cy599856-a.home.com>; from forming@home.com on Tue, Oct 23, 2001 at 20:07:56 +0200
On 20011023 Josh McKinney wrote:
>On approximately Tue, Oct 23, 2001 at 11:05:48AM +0200, Jesper Juhl wrote:
>>
>> I use the same version of the driver with my Geforce3 and I am also
>> running 2.4.13-pre6 and it works just fine so I don't agree with you
>> that it breaks...
>> You do know that there are a few files that need to be recompiled every
>> time you build a new kernel - right?
>>
>
>I have replied to this person personally a when this thread started with what I
>think is the fix to his problem. I have seen this error on my machine before.
>The problem arose when I compiled the running kernel with gcc-3.0. At first I
>thought it was just gcc-3 breaking the kernel. Then I realized that the nvidia
>modules use `cc` to compile. The symlink to cc was gcc-2.95. Changing the
>symlink to gcc-3.0 made the problem go away.
>
The first thing I did was to kach the horrible nVidia's Makefile. For example,
it had the bad intention of compiling and installing against the running kernel
(guess kernel with uname -r). So when you update the kernel, you have to reboot
and make nVidia drivers. I changed it to:
+KREL:=`grep UTS_RELEASE /usr/src/linux/include/linux/version.h | cut -d\" -f2`
-KERNDIR:=/lib/modules/$(shell uname -r)
+KERNDIR:=/lib/modules/$(KREL)
so it builds against a built but not-running kernel.
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.2 (Cooker) for i586
Linux werewolf 2.4.12-ac6-beo #1 SMP Tue Oct 23 21:24:30 CEST 2001 i686
next prev parent reply other threads:[~2001-10-23 22:50 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-22 18:45 2.4.13-pre6 breaks Nvidia's kernel module jarausch
2001-10-22 18:51 ` Benjamin LaHaise
2001-10-22 18:51 ` Alexander Viro
2001-10-22 19:35 ` Rik van Riel
2001-10-22 19:46 ` Christopher Friesen
2001-10-22 19:53 ` Daniel T. Chen
2001-10-22 19:53 ` 2.4.13-pre6 breaks Nvidia's kernel module, or not? Stephan von Krawczynski
2001-10-22 20:24 ` 2.4.13-pre6 breaks Nvidia's kernel module Alan Cox
2001-10-22 22:27 ` drevil
2001-10-22 22:43 ` Charles Cazabon
2001-10-22 22:46 ` Doug McNaught
2001-10-22 22:50 ` Alan Cox
2001-10-23 1:31 ` drevil
2001-10-23 1:43 ` Michael H. Warfield
2001-10-23 2:16 ` drevil
2001-10-23 4:44 ` Nicholas Knight
2001-10-23 5:06 ` Cort Dougan
2001-10-23 11:36 ` Rik van Riel
2001-10-23 16:13 ` Alan Cox
2001-10-23 5:08 ` drevil
2001-10-23 5:18 ` J Sloan
2001-10-23 5:59 ` Nicholas Knight
2001-10-23 7:21 ` Helge Hafting
2001-10-23 5:35 ` Matt D. Robinson
2001-10-23 16:16 ` Alan Cox
2001-10-23 9:50 ` David Woodhouse
2001-10-23 23:45 ` Ragnar Hojland Espinosa
2001-10-23 7:57 ` Alan Cox
2001-10-23 14:18 ` drevil
2001-10-23 16:01 ` Geert Uytterhoeven
2001-10-22 23:48 ` Jeff Golds
2001-10-22 23:53 ` Horst von Brand
2001-10-23 9:05 ` Jesper Juhl
2001-10-23 18:07 ` Josh McKinney
2001-10-23 22:51 ` J . A . Magallon [this message]
2001-10-24 21:06 ` Reid Hekman
2001-10-25 0:19 ` J . A . Magallon
-- strict thread matches above, loose matches on Subject: below --
2001-10-22 18:45 jarausch
2001-10-22 18:45 jarausch
2005-01-13 16:19 ` Arjan van de Ven
2005-01-13 16:50 ` Valdis.Kletnieks
2005-01-13 17:25 ` Zan Lynx
2005-01-13 17:38 ` Zwane Mwaikambo
2001-10-22 18:45 jarausch
2001-10-23 1:50 BH
2001-10-23 9:52 PVotruba
2001-10-23 12:37 Jesse Pollard
[not found] <fa.fm7f5dv.1cn8eg6@ifi.uio.no>
[not found] ` <fa.hbvlhav.v369au@ifi.uio.no>
[not found] ` <023001c15cf4$4fd5ecc0$1a01a8c0@allyourbase>
2001-10-25 4:15 ` Reid Hekman
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=20011024005107.A3988@werewolf.able.es \
--to=jamagallon@able.es \
--cc=forming@home.com \
--cc=linux-kernel@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