Phil H wrote: > putting the loop driver into initrd.gz to get loaded it early in the boot > I deleted those drivers installed in both extra and block previously, > cleaned and ran make again, same result with failed insertion. modules.dep > did get updated. Are you sure that /mnt/sda1/SOURCES/linux-2.6.18.1 kernel configuration is exactly same as in the kernel you are booting? Are you sure all needed "new" drivers are in initrd.gz? Are you sure that your bootloader is configured to load that initrd.gz and not some old one? If using lilo bootloader, did you remember to run "lilo"? Did you remember to reboot to get those "new" drivers loaded from initrd.gz? > INSTALL /mnt/sda1/SOURCES/NewLoopAESources_feb2007/loop-AES-v3.1f/tmp-d-kbuild/loop.ko > INSTALL /mnt/sda1/SOURCES/NewLoopAESources_feb2007/loop-AES-v3.1f/tmp-d-kbuild/loop_blowfish.ko > INSTALL /mnt/sda1/SOURCES/NewLoopAESources_feb2007/loop-AES-v3.1f/tmp-d-kbuild/loop_serpent.ko > INSTALL /mnt/sda1/SOURCES/NewLoopAESources_feb2007/loop-AES-v3.1f/tmp-d-kbuild/loop_twofish.ko > DEPMOD 2.6.18.1 > WARNING: /lib/modules/2.6.18.1/kernel/drivers/net/wan/dscc4.ko needs unknown symbol alloc_hdlcdev > WARNING: /lib/modules/2.6.18.1/kernel/drivers/net/wan/dscc4.ko needs unknown symbol hdlc_close > WARNING: /lib/modules/2.6.18.1/kernel/drivers/net/wan/dscc4.ko needs unknown symbol hdlc_open > WARNING: /lib/modules/2.6.18.1/kernel/drivers/net/wan/dscc4.ko needs unknown symbol hdlc_ioctl > WARNING: /lib/modules/2.6.18.1/kernel/drivers/net/wan/dscc4.ko needs unknown symbol unregister_hdlc_device I don't see loop driver related install or depmod errors above. dscc4.ko module seems to have some unresolved symbols, but those have nothing to do with loop driver. -- Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
