Alberto Vorano <[EMAIL PROTECTED]> writes:
> Hi to all
> After compiling kernel 2.4.1-3mdk, while making initrd I got this message:
> [root@localhost linux]# mkinitrd /boot/initrd-2.4.1-3mdk.img 2.4.1-3mdk
> mke2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
> mount: Could not find any loop device, and, according to /proc/devices,
> this kernel does not know about the loop device.
> (If so, then recompile or `insmod loop.o'.)
> Can't get a loopback device
> As I was quite sure I had selected it I went looking for it, and found in
> /usr/src/linux(-->2.4.1)/drivers/block and in
> /lib/modules/2.4.1-3mdk/kernel/drivers/block
> But when I attempted
> [root@localhost block]# insmod loop.o
> loop.o: unresolved symbol blk_queue_make_request_R88ac0aa0
> loop.o: unresolved symbol generic_make_request_Rc37092df
it look like you have a /boot/vmlinuz=>System.map with versionning
symbol and you try to insmod a loop.o who's doen't have any
versionning info.
> [root@localhost block]# Very luckily, for me, that I had saved
> original modules, so I could copy loop.o from there. Is it a bug?
> Best regards Alberto Vorano
--
MandrakeSoft Inc http://www.chmouel.org
--Chmouel
