public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J . A . Magallon" <jamagallon@able.es>
To: Reid Hekman <reid.hekman@ndsu.nodak.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.13-pre6 breaks Nvidia's kernel module
Date: Thu, 25 Oct 2001 02:19:14 +0200	[thread overview]
Message-ID: <20011025021914.C2928@werewolf.able.es> (raw)
In-Reply-To: <200110221846.f9MIkE416013@riker.skynet.be> <3BD532EC.6080803@eisenstein.dk> <20011023130756.A742@cy599856-a.home.com> <20011024005107.A3988@werewolf.able.es> <3BD72D5C.30604@ndsu.nodak.edu>
In-Reply-To: <3BD72D5C.30604@ndsu.nodak.edu>; from reid.hekman@ndsu.nodak.edu on Wed, Oct 24, 2001 at 23:06:36 +0200


On 20011024 Reid Hekman wrote:
>J . A . Magallon wrote:
>
>> 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.
>> 
>> 
>
>I thought use of /usr/src/linux was not recommended anymore. On my 
>distro, that file would point to the original kernel, the one that 
>glibc, et al. is compiled with, not my current running kernel or ones 
>I've not yet booted with. Perhaps a `uname -r` with command-line 
>override would be more appropriate?
>

As I see it, that is exactly what should not be done. Lets suppose you are
running 2.4.12. You want to upgrade. So you unpack 2.4.13 and build it.
If you go now to build nVidia drivers, with the shipped Makefile they
still build and install against 2.4.12. Sou you have to reboot in runlevel
3 to have 2.4.13 running witoht X, and then install the driver. *grrr*
With the above change, you build your kernel, then you go to the nVidia
sources, build the driver and install on the proper 2.4.13 dir under
/lib/modules, and just reboot in X again.

About /usr/src/linux, what is not recommended is to symlink
/usr/include/asm -> /usr/src/linux/include/asm
/usr/include/linux -> /usr/src/linux/include/linux
but instead have a separate header package that installs under /usr/include.

-- 
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.13-beo #2 SMP Thu Oct 25 00:59:08 CEST 2001 i686

  reply	other threads:[~2001-10-25  0:19 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
2001-10-24 21:06       ` Reid Hekman
2001-10-25  0:19         ` J . A . Magallon [this message]
     [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
  -- strict thread matches above, loose matches on Subject: below --
2001-10-23 12:37 Jesse Pollard
2001-10-23  9:52 PVotruba
2001-10-23  1:50 BH
2001-10-22 18:45 jarausch
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

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=20011025021914.C2928@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reid.hekman@ndsu.nodak.edu \
    /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