Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S270658AbTGUSFt (ORCPT ); Mon, 21 Jul 2003 14:05:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S270692AbTGUSFt (ORCPT ); Mon, 21 Jul 2003 14:05:49 -0400 Received: from msgbas1x.cos.agilent.com ([192.25.240.36]:7145 "EHLO msgbas1x.cos.agilent.com") by vger.kernel.org with ESMTP id S270658AbTGUSFM (ORCPT ); Mon, 21 Jul 2003 14:05:12 -0400 Message-ID: <334DD5C2ADAB9245B60F213F49C5EBCD05D55219@axcs03.cos.agilent.com> From: yiding_wang@agilent.com To: linux-kernel@vger.kernel.org Cc: sartre@linuxbr.com Subject: 2.5.72 insmod question again Date: Mon, 21 Jul 2003 12:19:59 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3524 Lines: 98 Hello , I have patched the module update 0.9.13-pre and rebuilt kernel. However, the insmod is still complainthe same thing because the utility is still from 2.4.20-8. This driver module is not going to be loaded during the kernel boot. I want to use insmod to load the module. I tried load qla1280.o built with kernel and got the same result. I think I may either need a new insmod utility to load the module, missed something or need to follow different procedure. Any idea from this point? By the way, I am using RH 9.0 release as base system fo r2.5.72 upgrade. Thanks! Eddie > -----Original Message----- > From: Cesar Suga [mailto:sartre@linuxbr.com] > Sent: Friday, July 18, 2003 5:27 AM > To: yiding_wang@agilent.com > Subject: RE: 2.5.72 insmod question > > > On Fri, 2003-07-18 at 14:50, yiding_wang@agilent.com wrote: > > You're welcome; > > I've come with some shortcomings upgrading, too... > > []s, > Cesar Suga > > > Thanks for the help! > > > > > -----Original Message----- > > > From: Cesar Suga [mailto:sartre@linuxbr.com] > > > Sent: Friday, July 18, 2003 3:00 AM > > > To: yiding_wang@agilent.com > > > Cc: linux-kernel@vger.kernel.org > > > Subject: Re: 2.5.72 insmod question > > > > > > > > > On Thu, 2003-07-17 at 21:35, yiding_wang@agilent.com wrote: > > > > > > Hello, > > > > > > Install the 'module-init-tools' package, from: > > > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/rusty/modules/ > > > > > > This is required for the new series of kernels, > > > starting with 2.5.50 (I > > > think), 2.5.72 certainly requires it. > > > > > > Cheers, > > > Cesar Suga > > > > > > > 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. > > > > > > > > Regards, > > > > > > > > Eddie > > > > > > > > > > > > > > > > - > > > > 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/ > > > > > > - 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/