From: Stefano Sabatini <stefano.sabatini-lala@poste.it>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Module modprobing problem
Date: Tue, 14 Oct 2008 23:14:49 +0200 [thread overview]
Message-ID: <20081014211449.GA11745@geppetto> (raw)
In-Reply-To: <20081010124522.GA30145@geppetto>
On date Friday 2008-10-10 14:45:22 +0200, Stefano Sabatini wrote:
> Hi all,
>
> I'm trying the latest v4l-dvb mercurial and this is the output I get:
>
> stefano@geppetto ~> sudo modprobe dib7000m -v
> insmod /lib/modules/2.6.22-3-486/kernel/drivers/media/dvb/frontends/dibx000_common.ko
> WARNING: Error inserting dibx000_common (/lib/modules/2.6.22-3-486/kernel/drivers/media/dvb/frontends/dibx000_common.ko): Invalid module format
> insmod /lib/modules/2.6.22-3-486/kernel/drivers/media/dvb/frontends/dib7000m.ko
> FATAL: Error inserting dib7000m (/lib/modules/2.6.22-3-486/kernel/drivers/media/dvb/frontends/dib7000m.ko): Invalid module format
>
> stefano@geppetto ~> uname -a
> Linux geppetto 2.6.22-3-486 #1 Mon Nov 12 07:53:08 UTC 2007 i686 GNU/Linux
>
> I get in dmesg:
> dibx000_common: disagrees about version of symbol struct_module
> dib7000m: disagrees about version of symbol struct_module
>
> Any hint will be highly appreciated.
For the archive: the problem was due to the linux headers used when
compiling don't match the effective kernel version. In my case (Debian
system) I had installed linux-headers-2.6.22-3 and running a kernel
2.6.22-2, that was apparently sufficient to get a version symbol
mismatch.
Updated kernel and headers to 2.6.26 and now I can compile and
modprobe them safely.
Regards.
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
prev parent reply other threads:[~2008-10-14 21:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 12:45 [linux-dvb] Module modprobing problem Stefano Sabatini
2008-10-14 21:14 ` Stefano Sabatini [this message]
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=20081014211449.GA11745@geppetto \
--to=stefano.sabatini-lala@poste.it \
--cc=linux-dvb@linuxtv.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 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.