d mahoney

I'm running RedHat 8.0 on a Compaq ProLiant with a custom 2.4.23 kernel.
I recently tried to install an additional RAID controller, but the
software install died with a warning about "no loopback devices
available". I checked my kernel config, and I did select that the
loopback device be compiled into the kernel, not as a module.

I just built a new kernel, specifying the loopback device to be built as
a module. The make dep, make bzImage, make modules, and make
modules_install all went just fine. When I try to build a new initrd
image using "mkinitrd -v -f /boot/initrd.0202 2.4.23" I get the same
error: "All of your loopback devices are in use".

So, how do I get around this? What do I need to do in order to build an
initrd file?

dan m

A little more info I should have included before: I've got HIGHMEM
defined in this kernel, set for 4 GB. After rebuilding the kernel but
before booting from it, I tried "modprobe loop". This produced:

Using /lib/modules/2.4.23/kernel/drivers/block/loop.o
/lib/modules/2.4.23/kernel/drivers/block/loop.o: unresolved symbol
kunmap_high
/lib/modules/2.4.23/kernel/drivers/block/loop.o: unresolved symbol
create_bounce
/lib/modules/2.4.23/kernel/drivers/block/loop.o: unresolved symbol
highmem_start_page
/lib/modules/2.4.23/kernel/drivers/block/loop.o: unresolved symbol kmap_high

scott hemphill

D Mahoney <dmahoney@deepdata.com> writes:


Probably the easiest way would be to reboot the system with a kernel
that supports the loop device. If you don't have a rescue diskette
from your install, you can just use your RedHat 8.0 installation CD-ROM.

After you get past the welcome, you can just Ctrl-Alt-F2 to get a
bash console. Then you can manually mount the / and /boot partitions,
and use chroot so that mkinitrd is looking at the correct version of
/etc/modules.conf.

Scott
--
Scott Hemphill hemphill@alumni.caltech.edu
"This isn't flying. This is falling, with style." -- Buzz Lightyear