Hi, Section 3.3 of the kernel HOWTO (http://www.tldp.org/HOWTO/Kernel-HOWTO/) might be applicable to this situation. Venkatesh > > I am still bit confused actually. So, I think these have to be done: > 1. run 'make xconfig' to make sure the loopback support is selected > as built in(not module) > 2. run 'make dep; make bzImage' to rebuild the kernel > 3. copy the bzImage just built to /boot and make grub.conf to use > the newly built kernel to boot from > 4. the next step was what I confused: > - if I now reboot, kernel would panic due to the initrd img > that would work with the newly built kernel wasn't there. > so I cannot reboot yet to use the newly built kernel > - but, if I 'mkinitrd' now, it would fail with the error: > "All of your loopback devices are in use" I think is caused by > the loop.o wasn't built in the kernel that I boot from > > so, I am stuck. what to do? I cannot reboot because it would panic > and if I do mkinitrd trying to make a valid img file that would also > fail due to the loop.o wasn't in the kernel that I booted from. > > cannot seem to figure a way to break this cycle. > > Did I miss anything? > > Thanks, > alan > > -----Original Message----- > From: John Haxby [mailto:jch@xxxxxxxxxxxxxxx] > Sent: Friday, October 03, 2003 12:09 AM > To: redhat-devel-list@xxxxxxxxxx > Subject: Re: mkinitrd failed with 'All of your loopback devices are in > use' > > > Alan Yang wrote: > > >Hello, > > > >I ran into a situation where I don't know how to break the catch-22 cycle. > >The scenario is like this: > >0. from a DELL machine with scsi device > >1. I installed the FreeSwan ipsec that seems like a rebuild of kernel is required > > so that when insmod loads ipsec.o there will be no error caused by the > > unreferenced varibales from the current booting kernel > >2. I rebuilt the kernel, that went fine > >3. but the mkinitrd failed with the error message: > > "Alll of your loopback devices are in use" > > and I think the real problem could be that the loop.o was not loaded > > > > > > You've almost answered your own question. When you configured this > question it looks as though you didn't include the loopback device in > the kernel configuration. It's an easy thing to miss, I know I've > missed it on several occasions. Don't forget to include initial > ramdisk support as well -- and don't make it a module! > > jch > > > _______________________________________________ > Redhat-devel-list mailing list > Redhat-devel-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/redhat-devel-list > > > _______________________________________________ > Redhat-devel-list mailing list > Redhat-devel-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/redhat-devel-list > _______________________________________________ Redhat-devel-list mailing list Redhat-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/redhat-devel-list
