[Click] Click-install "Invalid Module format" error

[dmoore7@nd.edu]

Its working now! Thanks so much.
The trouble turned out to be I hadn't changed the boot-loader over to the
click-modified new version of the kernel.  Thus my kernel "version" was
correct, but not the subversion.
Thanks very much for your help.
  -  David Moore

Quoting Puneet Sood <psood74 at gmail.com>:
> /usr/src/linux/vmlinux is the right place to look if you built the kernel
> there.
> Check the image in /boot which is actually running. It could be
> /boot/vmlinuz also (and have a suffix with the release name).
>
> On 7/20/07, dmoore7 at nd.edu <dmoore7 at nd.edu> wrote:
> > Thanks, I'm looking into this.
> > click.ko's grep reveals:
> > vermagic=2.6.16.13-click SMP 686 REGPARM 4KSTACKS gcc-3.4
> >
> > while vmlinux's grep reveals:
> > Linux version 2.6.16.13-click (root at sybill) (gcc version 3.4.4 20050721
> (Red Hat
> > 3.4.4-2)) #2 SMP Thu Jul 19 15:41:42 EDT 2007
> > 2.6.16.13-click SMP 686 REGPARM 4KSTACKS gcc-3.4
> >
> > So it appears my versions match.  (I found vmlinux in my /usr/src/linux
> > directory, not in /boot, if this makes any difference).  Also, I am not
> > attempting to cross-compile.
> > Is it possible this is not reporting versions properly, or that I have made
> an
> > error in trying to find the versions?
> > All input is appreciated,
> >  - David Moore
> >
> > On 7/20/07, Puneet Sood <psood74 at gmail.com> wrote:
> > > David,
> > >
> > > The problem occurs if different versions of the compiler/linker have
> > > been used to build the kernel and the Click modules.
> > >
> > > You can check the version used to build the modules by doing the
> following:
> > >
> > > $ strings click.ko | grep gcc
> > > $ strings /boot/vmlinux | grep gcc
> > >
> > > The gcc version should match upto the first two digits (x.y) and the
> > > Linux kernel name should match.
> > >
> > > If you used a cross-compiler (or something different than the default
> > > compiler) you need to modify the linuxmodule/Makefile.in file. Add the
> > > two lines referring to CROSS_COMPILE
> > >
> > > CLICK_ELEM2MAKE = $(top_builddir)/click-buildtool elem2make --linux26
> > >
> > > CROSS_COMPILE = /path/to/compiler/executables/
> > > export CROSS_COMPILE
> > >
> > > CLICKCC = @KERNEL_CC@
> > > CLICKCXX = @KERNEL_CXX@
> > >
> > >
> > > > Date: Fri, 20 Jul 2007 11:41:38 -0400
> > > > From: dmoore7 at nd.edu
> > > > Subject: [Click] Click-install "Invalid Module format" error
> > > > To: click at pdos.csail.mit.edu
> > > > Message-ID: <1184946098.46a0d7b20c56d at webmail.nd.edu>
> > > > Content-Type: text/plain; charset=ISO-8859-1
> > > >
> > > > Hello,
> > > > I have a newly patched/compiled 2.6.16.13 vanilla linux kernel running
> > happily,
> > > > and have recompiled click taking care to direct it to my System.map and
> with
> > > > appropriate files in /usr/src/linux.  It compiles properly, without
> errors.
> > > > However, when I attempt to execute a simple click-install:
> > > >
> > > > # click-install ./conf/test.click
> > > > insmod: error inserting '/usr/local/lib/proclikefs.ko': -1 Invalid
> module
> > > > formatclick-install: '/sbin/insmod /usr/local/lib/proclikefs.ko' failed
> > > >
> > > > I encounter the error shown above.  I looked into /var/log/messages
> file and
> > > > found the following message:
> > > > Jul 20 11:34:41 sybill kernel: proclikefs: disagrees about version of
> symbol
> > > > struct_module
> > > >
> > > > I carefully retraced my steps from kernel-patch onward, but have not
> found
> > any
> > > > errors in the output.  However click-install continues to fault as
> shown
> > above.
> > > > Any help or input getting this working is appreciated.
> > > > Thanks,
> > > >  - David Moore
> >
> >
> >
>