Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Distribution: Slackware 11.0; Kubuntu 6.06; OpenBSD 4.0; OS X 10.4.10
Did you compile the kernel with loopback support compiled in? The selection for it is under the "Block Devices" section of menuconfig's display.
You mean kernel 2.4.22, right?
Ok, wait a minute. The coffee has begun to kick in. You are having problems with the kernel you have, not the kernel you compiled. Different problem set. It is possible that you do not have the loopback module loaded. Try 'insmod loop' or 'insmod loop.o' as root. See if that does the trick. If not, we'll scratch our heads for a little while longer.
Ok, I finally got it working after days and days of dragging this problem.
Hussar, as you said, the problem was with the kernel I had 2.4.21(ie. not the kernel I was compiling 2.4.22). I recompiled my old kernel, 2.4.21, after adding the support of "Loopback" under "Block Devices" section and here's the trick that worked for me:
I added Loopback support as a LOADABLE module and NOT built-in. Then once past module compilation step (ie. make modules), I loaded Loopback.o before even re-installing my old kernel and it worked! Why before re-installing? simply because I couldn't even re-install my old kernel and kept saying "All of your loopback devices are in use" after a /sbin/mkinitrd.
To find "loopback.o" location enter "locate loopback.o").