[Pvfs2-users] unable to insert kernel module pvfs2.ko

[David Brown]

On 5/30/07, Tommy Butler <tommy at atrixnet.com> wrote:
> Time and time again I have failed today, trying to insert the pvfs2.ko
> module into the kernel.  I've spent hours upon hours debugging the problem
> to no avail.
>
> EXECUTIVE SUMMARY
>
> Trying to install pvfs2 on ibm zSeries x86 architecture.  It compiles fine.
> Main problem is that my kernel was compiled with gcc 4.0 and I currently
> have gcc 4.1 installed.  Due to package dependencies on this Debian Linux
> machine, I'm unable to downgrade to 4.0 without a huge amount of pain and
> heartache.  Neither am I able to upgrade to a new kernel at this time.
>
> DETAILS
>
> I've tried setting the CC environment variable to compile with `cc -V 4.0`
> via `export CC="/usr/bin/cc -V 4.0"`.  That makes its way into my Makefile
> and I'm assuming the source code is compiling with that 4.0 directive.  I
> apply the pvfs-lk21.patch to the build tree, and then I go ahead and compile
> with:
> ./configure -with-mpi=/usr/bin/mpirun
> -with-kernel=/usr/src/linux-source-2.6.15/
> make
> make install
> make kmod_install
>
> However when I try to insert the module using either insmod or modprobe I
> encounter errors.
>
> With insmod:
> insmod /usr/src/pvfs2/src/kernel/linux-2.6/pvfs2.ko
> insmod: error inserting '/usr/src/pvfs2/src/kernel/linux-
> 2.6/pvfs2.ko': -1 Invalid module format
> dmesg|tail -n1
> pvfs2: version magic '2.6.15 486 gcc-4.1' should be '2.6.15-1-486 486
> gcc-4.0'
>
> With modprobe (trying to force the module in, despite bad vermagic):
> modprobe -i --force-vermagic pvfs2
> FATAL: Module pvfs2 not found.
> modprobe -i --force-vermagic
> /usr/src/pvfs2/src/kernel/linux-2.6/pvfs2.ko
> FATAL: Module /usr/src/pvfs2/src/kernel/linux_2.6/pvfs2.ko
> not found.
>
> CONCLUSION
>
> Am I a doomed man?  What am I doing wrong?  How can I fix this?  I thank in
> advance any and everyone who helps me to solve this problem.
>

what flavor of debian is this? etch? lenny? sarge?
I don't know any version of debian currently with a 2.6.15 kernel if
its a custom kernel (built in house?) then you should get your hands
on the source and rebuild it for the new compiler so this doesn't come
up again.

also the --force-vermagic only refers to the kernel version (iirc) not
the gcc version. The gcc version is a must to get right sort of thing
with the kernel.

- David Brown