Bug 2222 – Problem with cryptoapi

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Andreas Proschofsky (RETIRED) 2002-04-29 04:10:13 UTC]

I have a problem with cryptoapi: Emerging works fine, but after that,
trying to do depmod results in:

root@root root # depmod
depmod: *** Unresolved symbols in /lib/modules/misc/cryptoloop.o

and an insmod:

root@root root # insmod cryptoloop
Using /lib/modules/misc/cryptoloop.o
/lib/modules/misc/cryptoloop.o: unresolved symbol
loop_register_transfer_Rsmp_785c6a32
/lib/modules/misc/cryptoloop.o: unresolved symbol
loop_unregister_transfer_Rsmp_bfee3ad5
/lib/modules/misc/cryptoloop.o: unresolved symbol find_transform_by_name
/lib/modules/misc/cryptoloop.o:
Hint: You are trying to load a module without a GPL compatible license
and it has unresolved symbols. Contact the module supplier for
assistance, only they can help you.

I am using latest kernel-2.4.18-xfs, does cryptoapi just work with
gentoo-sources? 

I also use latest util-linux.

[Comment 1 Ryan Phillips (RETIRED) 2002-04-30 01:07:44 UTC]

I have committed an updated to the ebuild... please test it out.

-ryan

[Comment 2 Andreas Proschofsky (RETIRED) 2002-04-30 02:03:31 UTC]

Doesn't change anything for me: I did a emerge rsync, unmerged cryptoapi,
reemerged it and still get the exact same error (except the modules are now
located in /lib/modules/2.4.18-xfs/misc)

Am I supposed to reemerge the xfs-sources? 

[Comment 3 Ryan Phillips (RETIRED) 2002-04-30 02:59:59 UTC]

Hmm. after researching for a bit, I'm under the impression there is a special
patch for xfs kernels:

http://www.kernel.org/pub/linux/kernel/people/hvr/old/

[Comment 4 Andreas Proschofsky (RETIRED) 2002-04-30 03:54:38 UTC]

Yes but not anymore in the current version:

ftp://ftp.kernel.org/pub/linux/kernel/people/hvr/testing/

But anyway you are using Cryptoapi from

http://cryptoapi.sourceforge.net/

And there are no special versions for that one

So the question is now: What to do next?

[Comment 5 Andreas Proschofsky (RETIRED) 2002-04-30 18:52:31 UTC]

Solved the problem. It was caused by not having installed the loopback block
device in the kernel.

Maybe it would be possible to add an advice or a check to the ebuild about that,
to provide information for other users.