From: Arjan van de Ven <arjan@infradead.org>
To: "Brian D. McGrew" <brian@visionpro.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Invalid module format?
Date: Fri, 19 May 2006 03:50:39 +0200 [thread overview]
Message-ID: <1148003459.2994.5.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <14CFC56C96D8554AA0B8969DB825FEA0012B321D@chicken.machinevisionproducts.com>
On Thu, 2006-05-18 at 07:01 -0700, Brian D. McGrew wrote:
> I have two device drivers for two separate PCI cards.
>
> Using the 2.6.15.6 I can compile and insert both of these drivers.
>
> I copy my sources to my 2.6.16.16 tree and recompile them. One driver
> inserts just fine (and works) and the other gives me this:
>
> FATAL: Error inserting ibb
> (/lib/modules/2.6.16.16/kernel/drivers/mvp/ibb.ko): Invalid module
> format
>
> The same source file between both kernels and I get no errors at compile
> time.
you forgot to
1) look into dmesg and give us the information that gets printed there
when modprobe returns this error
2) point to the source of the driver
next prev parent reply other threads:[~2006-05-19 1:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 14:01 Brian D. McGrew
2006-05-19 1:50 ` Arjan van de Ven [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-19 18:38 Brian D. McGrew
2006-05-19 20:21 ` Randy.Dunlap
2006-05-20 17:37 ` Randy.Dunlap
2006-05-19 17:23 Brian D. McGrew
2006-05-19 17:11 Brian D. McGrew
2006-05-19 17:19 ` Randy.Dunlap
2006-05-19 17:55 ` Randy.Dunlap
2006-05-19 21:35 ` Sam Ravnborg
2004-06-12 0:38 Invalid module format ? J.A. Magallon
2004-06-12 0:51 ` Matt H.
2004-06-12 0:55 ` J.A. Magallon
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=1148003459.2994.5.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=brian@visionpro.com \
--cc=linux-kernel@vger.kernel.org \
/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®