On 4 Apr 2001, Dominic Mitchell wrote:

>
> Hi,
>
> I just made a bootdisk for kernel 2.2.18 which seems to be working
> correctly.  However I do not understand why 'mkbootdisk' complains
> that all of my loopback devices are in use and can't open
> /vmlinuz-2.2.18.  See below.
>
> Would someone shed some lights on this?
>
> Thanks.
>
> Dominic.
>
> $ mkbootdisk --verbose 2.2.18
> Insert a disk in /dev/fd0. Any information on the disk will be lost.
> Press <Enter> to continue or ^C to abort:
> Formatting /dev/fd0... done.
> Copying /boot/vmlinuz-2.2.18... done.
> Creating initrd image... All of your loopback devices are in use!
> done.
> Setting up lilo... done.
> open /vmlinuz-2.2.18: No such file or directory
>
> But
>
> $ ls -l /vmlinuz-2.2.18
> -rw-r--r--    1 root     root       555336 avr  4 11:30 /vmlinuz-2.2.18
>
>
mkinitrd needs to use the loop device to put files in the RAM disk
image.   What happens if you run "modprobe loop"?  Or if you are running
a custom kernel, did you leave out loop device support?  The other major
cause of this error is when you use the -U option instead of the -i
option of RPM when installing a new kernel RPM.

>From the error, LILO is probably looking for the initramdisk that didn't
get built.

Mikkel
-- 

    Do not meddle in the affairs of dragons,
 for you are crunchy and taste good with ketchup.



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to