no success with modules

Dr. Michael Grimm (Michael.Grimm@Schering.DE)
Thu, 19 Oct 1995 14:32:18 +0000


Hi,

I subscribed very recently, and it might well been asked before:

What am I doing wrong with kernel modules? From 1.2.10 upto 1.3.35 I could only
load the hpfs.o module, but not the others which I would like to.

Here's what I'm doing:
- using gcc 2.5.8, libc 4.5.24, and modules 1.2.8
- MAKE config (settings in .config are correct):
- no PCI, no standard hard disk, no net devices, just network (no
modules), no ELF, just support of ELF, no CD-ROM drivers
- modversions=yes
- SCSI support=yes, SCSI disk=yes, SCSI tape=module, SCSI CD-ROM=module,
SCSI generic=module
- AHA1740=yes, all other drivers=no
- EXT2=yes, all others=modules, except NFS, SYSV, and SMB=no
- Microsoft Busmouse=yes, all other character devices=no
- no sound, and no kernel hacking
- MAKE dep
- MAKE clean
- MAKE zImage
- REBOOT (I have read this in a module FAQ, even if this doesn't make
any sense to me. But I did reboot, you never know ... ;=) )
- MAKE modules
- MAKE modules_install

Here's what I'm achieving:
- No unresolved symbols during MAKE zImage
- No complaints during MAKE modules
- MAKE modules_install complains:
> Installing modules under /lib/modules/1.3.35/net
> Installing modules under /lib/modules/1.3.35/scsi
> Installing modules under /lib/modules/1.3.35/fs
> cp: bsd_comp.o: No such file or directory
^^^^^^^^^^ Where did I say YES to that module?
> cp: hpfs.o: No such file or directory
> cp: isofs.o: No such file or directory
> cp: minix.o: No such file or directory
> cp: msdos.o: No such file or directory
> cp: sg.o: No such file or directory
> cp: sr_mod.o: No such file or directory
> cp: st.o: No such file or directory
> cp: umsdos.o: No such file or directory
> Installing modules under /lib/modules/1.3.35/misc
BTW, all files have been copied and are in place!
- /sbin/depmod -a -e -v -a leaves me with:
> *** Unresolved symbols in module /lib/modules/1.3.35/fs/isofs.o
> bad_user_access_length
> *** Unresolved symbols in module /lib/modules/1.3.35/fs/minix.o
> bad_user_access_length
> *** Unresolved symbols in module /lib/modules/1.3.35/fs/msdos.o
> bad_user_access_length
> *** Unresolved symbols in module /lib/modules/1.3.35/fs/umsdos.o
> bad_user_access_length
> *** Unresolved symbols in module /lib/modules/1.3.35/net/bsd_comp.o
> ppp_register_compressor
> ppp_unregister_compressor
> *** Unresolved symbols in module /lib/modules/1.3.35/scsi/sg.o
> bad_user_access_length
> *** Unresolved symbols in module /lib/modules/1.3.35/scsi/sr_mod.o
> bad_user_access_length
> *** Unresolved symbols in module /lib/modules/1.3.35/scsi/st.o
> bad_user_access_length
> /lib/modules/1.3.35/fs/hpfs.o
- find and grep on the kernel tree found:
- bad_user_access_length in ./kernel/panic.c
in ./include/asm-i386/segment.h (and other
asm's)
- ppp_register_compressor and ppp_unregister_compressor
in ./drivers/net/ppp.c
in ./drivers/net/bsd_comp.c
- /sbin/modprobe msdos complains (just one example):
> bad_user_access_length: wrong version
> Failed to load module! The symbols from kernel 1.3.35 don't match
1.3.35
What does that mean ?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Excuse me, if this is should be considered "noisy", but I would really like to
learn, what I am doing wrong. If you need further information, mail me!

Thank you,
Michael

-- 
===========================================================
The opinions expressed above are solely those of the author
and are not necessarily those of Schering.
===========================================================
NAME:  Dr. Michael Grimm            ADDRESS: Schering AG
EMAIL: michael.grimm@schering.de             PCH-TCH
PHONE: +49-30-468-5477                       D-13342 Berlin
FAX:   +49-30-4691-6741                      Germany
===========================================================