problem with cloop module...

[Myrdhin]

Hello,

(excuse for my english, i'm french :D )

I have a Gnu/Debian woody 3.0 with a 2.4.18-386 kernel installed with apt-get. It's not a custom kernel ! I downloaded kernel-headers-2.4.18.

I downloaded http://developer.linuxtag.net/knoppix/i386/cloop-src_0.68-5_all.deb and installed with dpkg -i.

Next :

# cd /usr/src/module/cloop
# debian/rules KSRC=/usr/src/kernel-headers-2.4.18 KVERS=2.4.18-386 kdist_image
# dpkg -i ../cloop-2.4.18-386_0.68-5_i386.deb

all without problem...

i have a morphix image and i would like to load the cloop module :

# insmod cloop file=/morphix/morphix
Using /lib/modules/2.4.18-386/kernel/drivers/block/cloop.o
/lib/modules/2.4.18-386/kernel/drivers/block/cloop.o: unresolved symbol blk_size_Rsmp_a2e0a082
/lib/modules/2.4.18-386/kernel/drivers/block/cloop.o: unresolved symbol filp_open_Rsmp_6c699065
/lib/modules/2.4.18-386/kernel/drivers/block/cloop.o: unresolved symbol do_generic_file_read_Rsmp_dd434ef4
/lib/modules/2.4.18-386/kernel/drivers/block/cloop.o: unresolved symbol end_that_request_last_Rsmp_cab0b716
/lib/modules/2.4.18-386/kernel/drivers/block/cloop.o: unresolved symbol register_blkdev_Rsmp_9a6fb4a6
/lib/modules/2.4.18-386/kernel/drivers/block/cloop.o: unresolved symbol blk_cleanup_queue_Rsmp_fb0da4ac
/lib/modules/2.4.18-386/kernel/drivers/block/cloop.o: unresolved symbol __vmalloc_Rsmp_79995c5b
/lib/modules/2.4.18-386/kernel/drivers/block/cloop.o: unresolved symbol blk_dev_Rsmp_648c21fc
/lib/modules/2.4.18-386/kernel/drivers/block/cloop.o: unresolved symbol blk_init_queue_Rsmp_18ce3577
/lib/modules/2.4.18-386/kernel/drivers/block/cloop.o: unresolved symbol printk_Rsmp_1b7d4074
/lib/modules/2.4.18-386/kernel/drivers/block/cloop.o: unresolved symbol kfree_Rsmp_037a0cba
/lib/modules/2.4.18-386/kernel/drivers/block/cloop.o: unresolved symbol io_request_lock_Rsmp_08c39da6
/lib/modules/2.4.18-386/kernel/drivers/block/cloop.o: unresolved symbol fsync_dev_Rsmp_8ea128e2
/lib/modules/2.4.18-386/kernel/drivers/block/cloop.o: unresolved symbol unregister_blkdev_Rsmp_eac1c4af
/lib/modules/2.4.18-386/kernel/drivers/block/cloop.o: unresolved symbol panic_Rsmp_01075bf0
/lib/modules/2.4.18-386/kernel/drivers/block/cloop.o: unresolved symbol blksize_size_Rsmp_2f30b4b6
/lib/modules/2.4.18-386/kernel/drivers/block/cloop.o: unresolved symbol vfree_Rsmp_2fd1d81c
/lib/modules/2.4.18-386/kernel/drivers/block/cloop.o: unresolved symbol kmalloc_Rsmp_93d4cfe6
/lib/modules/2.4.18-386/kernel/drivers/block/cloop.o: unresolved symbol end_that_request_first_Rsmp_7e7725e9
/lib/modules/2.4.18-386/kernel/drivers/block/cloop.o: unresolved symbol filp_close_Rsmp_a500728f

Why ? :cry: Perhaps a module to load before ? or an option in the kernel ?

thanks for your help,

[garyng]

What compiler did you use ?

These _Rsmp_****** looks very strange. I would suggest you to start everything from scratch(including building the kernel, not just use a header tree). Linux is very picky about kernel and LKM. The only way you can be sure a given kernel work with a modules is to compile them all using the same compiler under the same environment. This is very different than Microsoft's DLL.

[Myrdhin]

thanks !

i have compiled my own custom 2.4.18 kernel and the module cloop again. All works !

Thanks you again :)