public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: lobo@polbox.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: I'm sorry [it was: Nazi Kernels]
Date: Tue, 13 Nov 2001 13:34:03 +1100	[thread overview]
Message-ID: <9823.1005618843@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Tue, 13 Nov 2001 02:48:06 BST." <20011113024806.A13176@chello062179017166.chello.pl>

On Tue, 13 Nov 2001 02:48:06 +0100, 
lobo@polbox.com wrote:
>Now after this introduction, I try to explain whats my problem with
>the new driver policy. When I try to load NVdriver to the kernel
>2.1.14, the modprobe (modutils 2.4.10) writes following line
>"Note: modules without a GPL compatible license cannot use \
>GPLONLY_ symbols".

If you had given the error message the first time instead of
complaining about Nazi kernels then you would have got a decent
response!

insmod issues that message when two conditions are both satisfied:

(1) The module has unresolved references *and*
(2) The module does not have a GPL license.

modprobe does not check if the unresolved references are exported as
GPLONLY or not, the message is jsut a hint about why the load /might/
have failed.  I should change the insmod text to make it more explicit
that this is only a possible explanation.

Since kernel 2.4.14 does not have any GPLONLY exports, your problem is
not that the kernel is restricting access to symbols.  Instead your
problem is that the binary only NVdriver does not match your kernel.
Ask NVidia for help.

Keith [Not a Nazi] Owens, modutils maintainer.


  parent reply	other threads:[~2001-11-13  2:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-13  1:48 I'm sorry [it was: Nazi Kernels] lobo
2001-11-13  1:05 ` Alan Cox
2001-11-13  2:34 ` Keith Owens [this message]
2001-11-17  1:20 ` Jim Roland

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=9823.1005618843@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lobo@polbox.com \
    /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