From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "Srinivas G." <srinivasg@esntechnologies.co.in>
Cc: linux-kernel-Mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: FATAL: Error inserting fm -- invalid module format
Date: Fri, 21 Jan 2005 08:59:08 -0800 [thread overview]
Message-ID: <41F134DC.8020204@osdl.org> (raw)
In-Reply-To: <4EE0CBA31942E547B99B3D4BFAB348112B93D8@mail.esn.co.in>
Srinivas G. wrote:
> Dear All,
>
> We were developed a block device driver on linux-2.6.x kernel. We want
> to distribute our driver as a RPM Binary. We are using the SuSE 9.1 with
> 2.6.5-7.71 kernel.
>
> We build the RPM file using the fm.ko file on SuSE 9.1 with 2.6.5-7.71
> kernel where fm.ko indicates our Block Driver module. When I try to run
> the RPM file on a different kernel version it has given the following
> error message.
>
> FATAL: Error inserting fm
> (/lib/modules/2.6.4-52-default/kernel/drivers/block/fm.ko): Invalid
> module format
>
> As I know the error message indicates that I compiled the driver under
> 2.6.5-7.71 kernel where as I am trying to insert the module in
> 2.6.4-52-default kernel.
>
> My question is: Is it possible to compile and build a .ko file with out
> including the version information? (i.e. I want to build a RPM file
> using fm.ko file which was compiled using 2.6.5-7.71 and to run the RPM
> file on a different kernel versions.)
>
> We are not very sure of how to achieve this.
> Please help us address this issue.
So you want to get around a mechanism that is preventing your driver
from causing an Oops because of different data structures, different
kernel APIs, etc., between those version? or any versions?
This is just asking for trouble. IOW, forget it.
--
~Randy
next prev parent reply other threads:[~2005-01-21 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 14:08 FATAL: Error inserting fm -- invalid module format Srinivas G.
2005-01-21 14:23 ` Arjan van de Ven
2005-01-21 16:59 ` Randy.Dunlap [this message]
2005-01-24 0:45 ` Kyle Moffett
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=41F134DC.8020204@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivasg@esntechnologies.co.in \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.