mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: <yiding_wang@agilent.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.72 insmod question
Date: Thu, 17 Jul 2003 17:47:46 -0700 (PDT)	[thread overview]
Message-ID: <1173.4.4.25.4.1058489266.squirrel@www.osdl.org> (raw)
In-Reply-To: <334DD5C2ADAB9245B60F213F49C5EBCD05D55212@axcs03.cos.agilent.com>

> I completed a fibre channel driver change to support for 2.5.72 (suppose to
> be 2.6 compatible) and compiled it OK.  When trying load the driver with
> "insmod", it complains with the message "insmod: QM_MODULES: Function not
> implemented".
>
> I tried kernel built module qla1280.o and got the same result.  It seems the
> insmod utility in my system is not compatible with new 2.5.72 built module.
>
> I have 2.4.20-8 kernel installed first and driver loads and runs fine.
> Later added 2.5.72 kernel and booted with its bzImage works fine too.
> However, the insmod utility I am using to load new driver was from 2.4.20-8
> which has system_query_module() being called.  I checked Doc. and source
> code for 2.5.72 and could not find same function call in module.c
>
> Some web documents mentioned that the module installation is changed from
> 2.4.x to 2.5.x.  So far I am still looking for the solution and hope someone
> can help me on the issue.
>
> I am compiling the driver out side of kernel source tree but using kernel
> environmental variables for compatibility.

You need to use the 2.5/2.6 module-init-tools from
  http://www.kernel.org/pub/linux/kernel/people/rusty/modules/

modutils from 2.4 won't work with 2.5/2.6.

And you probably should read over the 2.6 migration document:
  http://www.codemonkey.org.uk/post-halloween-2.5.txt

~Randy




  reply	other threads:[~2003-07-18  0:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-18  0:35 yiding_wang
2003-07-18  0:47 ` Randy.Dunlap [this message]
2003-07-18 11:50   ` Tomas Szepe
2003-07-18 14:35     ` Randy.Dunlap
2003-07-18 22:53       ` Ronald Jerome
2003-07-18  9:59 ` Cesar Suga

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=1173.4.4.25.4.1058489266.squirrel@www.osdl.org \
    --to=rddunlap@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yiding_wang@agilent.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

all inboxes | Powered by JetHome®