Hi Phil, On Mon, Jun 27, 2005 at 06:52:15AM -0700, Phil H wrote: > The Debian source for kernel 2.4.27 unpacks into > /usr/src/kernel-source-2.4.27 (that's what's available > debian-source-wise I think), but the running kernel > (precompiled, from the debian install cd) is (from > uname -r) 2.4.27-2-386 ie for i386 architecture. > > So when I built loop.o, it got put in > /lib/modules/2.4.27/block The location depends on the value for EXTRAVERSION that was set during the kernel build. I guess your source tree hasn't been configured, or you used an EXTRAVERSION different from that of the Debian kernel-image? In case you are using make-kpkg, you could try setting --append-to-version -2-386. > This didn't seem to be a problem, however. I did > rmmod loop.o > rm -f > /lib/modules/2.4.27-2-386/kernel/drivers/block/loop.o > cp /lib/modules/2.4.27/block/loop.o > /lib/modules/2.4.27-2-386/kernel/drivers/block > modprobe loop > > and the new loop.o driver seems to be working. > > BUT this same procedure didn't work for the new > modules I built from loop-aes-ciphers v3.0b - modprobe > says it can't find them. This could be caused by outdated depmod information. Does it work after running depmod -a ? > Naively changing the name of the source code directory > to match 2.4.26-2-386 doesn't work ( I didn't think it > would). > > How to I fix this? When building for "official" Debian kernels, I recommend to use module-assistant to prepare a source tree that closely resembles the original - including EXTRAVERSION etc. Just do "m-a fakesource" and build using the source tree in /usr/src/kernel-source-$kvers-$debabi-$subarch Feel free to mail <package>@packages.debian.org or directly to my address if you suspect Debian specific problems. cheers, Max - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
