[OpenAFS] Kernel module problems on RHEL2.1

[Matthew Hoskins]

I have a system that needs to run RHEL2.1 (app vendor has not moved to
RHEL3.0 yet), used 1.2.11 built for rh7.3, Tried compiling kernel module
using openafs-kernel-source packages from rhel3.0 and rh7.3.  Both build
fine but the ../afsmodname step fails with:

$../afsmodname  -f SymTable.local -g libafs-2.4.9-e.43.*
Unable to find a suitable symbol reference in 2.4.9-e.43.mp!
Unable to find a suitable symbol reference in 2.4.9-e.43!

Searching using nm as suggested previously on this list...

$nm libafs-2.4.9-e.43* |grep iget
          U iget4
          U iget4


After manually setting LIBAFS= (which also fails) I get the following in
libafs.map:

/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol
inode_setattr
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol dput
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol
flush_signals
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol sock_sendmsg
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol path_release
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol force_sig
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol
generic_file_write
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol
page_follow_link
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol
generic_read_dir
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol
unregister_filesystem
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol iput
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol pidhash
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol
remove_wait_queue
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol dget_locked
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol
generic_file_mmap
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol d_rehash
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol
init_task_union
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol
generic_file_read
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol d_move
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol
register_filesystem
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol
invalidate_inode_pages
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol d_alloc_root
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol
proc_dointvec
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol
unregister_sysctl_table
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol path_init
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol sock_recvmsg
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol
page_readlink
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol
filemap_fdatasync
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol
filemap_fdatawait
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol
add_wait_queue
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol __user_walk
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol sock_release
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol sock_create
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol
shrink_dcache_parent
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol
d_instantiate
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol path_walk
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol
inode_change_ok
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol
truncate_inode_pages
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol iget4
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o: unresolved symbol
register_sysctl_table
/usr/vice/etc/modload/libafs-2.4.9-e.43.mp.o:
Hint: You are trying to load a module without a GPL compatible license
       and it has unresolved symbols.  The module may be trying to access
       GPLONLY symbols but the problem is more likely to be a coding or
       user error.  Contact the module supplier for assistance, only they
       can help you.
============================================================================


What did i do wrong?

PS: system is SMP i686

-Matt