public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Devin Heitmueller <dheitmueller@kernellabs.com>
To: Edouard Marquez <animatrix30@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Invalid module format
Date: Wed, 9 Sep 2009 12:19:25 -0400	[thread overview]
Message-ID: <829197380909090919o613827d0ye00cbfe3bde888ed@mail.gmail.com> (raw)
In-Reply-To: <200909091814.10092.animatrix30@gmail.com>

On Wed, Sep 9, 2009 at 12:14 PM, Edouard Marquez<animatrix30@gmail.com> wrote:
> Hello,
>
> I am using Gentoo with tuxonice-sources-2.6.3.0-r5 that is to say 2.6.30.5.
> The compilation of v4l-dvb works well (the kernel which is chosen is the
> right), but when I try to modprobe em28xx, I get this :
>
> WARNING: Error inserting videobuf_core (/lib/modules/2.6.30-tuxonice-
> r5/kernel/drivers/media/video/videobuf-core.ko): Invalid module format
> WARNING: Error inserting videobuf_vmalloc (/lib/modules/2.6.30-tuxonice-
> r5/kernel/drivers/media/video/videobuf-vmalloc.ko): Invalid module format
> WARNING: Error inserting v4l2_compat_ioctl32 (/lib/modules/2.6.30-tuxonice-
> r5/kernel/drivers/media/video/v4l2-compat-ioctl32.ko): Invalid module format
> WARNING: Error inserting v4l1_compat (/lib/modules/2.6.30-tuxonice-
> r5/kernel/drivers/media/video/v4l1-compat.ko): Invalid module format
> WARNING: Error inserting videodev (/lib/modules/2.6.30-tuxonice-
> r5/kernel/drivers/media/video/videodev.ko): Invalid module format
> WARNING: Error inserting v4l2_common (/lib/modules/2.6.30-tuxonice-
> r5/kernel/drivers/media/video/v4l2-common.ko): Invalid module format
> WARNING: Error inserting ir_common (/lib/modules/2.6.30-tuxonice-
> r5/kernel/drivers/media/common/ir-common.ko): Invalid module format
> FATAL: Error inserting em28xx (/lib/modules/2.6.30-tuxonice-
> r5/kernel/drivers/media/video/em28xx/em28xx.ko): Invalid module format
>
> I have this error in my dmesg :
>
> [ 3903.465920] tveeprom: disagrees about version of symbol module_layout
>
> I join my .config file.
>
> What do I need to do ?
> Thanks!
>

Usually this occurs when people are using the mrechberger version of
the em28xx driver, and the symbols are in conflict with the rest of
the v4l-dvb tree.

You need to either switch to the v4l-dvb version of the driver
(removing the .ko files for the mrec driver), or recompile and
reinstall the mrec driver *after* you've installed the latest v4l-dvb
code.

Cheers,

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com

  reply	other threads:[~2009-09-09 16:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09 16:14 Invalid module format Edouard Marquez
2009-09-09 16:19 ` Devin Heitmueller [this message]
     [not found]   ` <c2885d2b0909091113h2ae6e27ai7541b3efac0e4606@mail.gmail.com>
2009-09-09 18:20     ` Devin Heitmueller
     [not found]       ` <c2885d2b0909091134w1264b827kf5d4254634bed1d9@mail.gmail.com>
2009-09-09 18:39         ` Devin Heitmueller
2009-09-09 19:02   ` Markus Rechberger
2009-09-09 19:08     ` Markus Rechberger
2009-09-09 19:09     ` Devin Heitmueller
2009-09-09 19:40       ` Markus Rechberger

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=829197380909090919o613827d0ye00cbfe3bde888ed@mail.gmail.com \
    --to=dheitmueller@kernellabs.com \
    --cc=animatrix30@gmail.com \
    --cc=linux-media@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