Message-ID: <1173.4.4.25.4.1058489266.squirrel@www.osdl.org>
Date: Thu, 17 Jul 2003 17:47:46 -0700 (PDT)
Subject: Re: 2.5.72 insmod question
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: <yiding_wang@agilent.com>
In-Reply-To: <334DD5C2ADAB9245B60F213F49C5EBCD05D55212@axcs03.cos.agilent.com>
References: <334DD5C2ADAB9245B60F213F49C5EBCD05D55212@axcs03.cos.agilent.com>
Importance: Normal
Cc: <linux-kernel@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1611
Lines: 38

> 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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" 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.tux.org/lkml/