> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:cooker-owner@linux-
> mandrake.com] On Behalf Of huug
> Sent: Thursday, February 21, 2002 5:00 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [Cooker] kernel-2.4.17.18 installation report
>
> huug <[EMAIL PROTECTED]> writes:
>
> > Borsenkow Andrej <[EMAIL PROTECTED]> writes:
> >
> > > On ���, 2002-02-16 at 01:12, huug wrote:
> > >>
> > >> We've seen that loop stuff already :) But /boot is fish nor flesh
> > >> (vmlinuz new, all others old).
> > >>
> > >> [root@huug2001 huug]# rpm -iv kernel-2.4.17.18mdk-1-1mdk.i586.rpm
> > >> Preparing packages for installation...
> > >> kernel-2.4.17.18mdk-1-1mdk
> > >> mke2fs 1.26 (3-Feb-2002)
> > >> mount: Could not find any loop device.
> > >> Maybe /dev/loop# has a wrong major number?
> > >
> > > Update pam and restart devfsd. If it does not fix it ... I am
interested
> > > in more information.
> >
> > Pam is 0.75.18: I follow Cooker pretty closely, sometime even urpmi
> > --auto-select (when I had a working urpmi;)
> >
> > Well, the kernel is in place now, it just won't boot. When it's time
> > to mount root, it complains about an unsupported feature 4 and that
is
> > that. BRS time :( Yeah, I'm disappointed: .17 was making progress
(by
> > skipping over the mount points in fstab instead of hanging), and now
> > this..
>
> *Blush*, there was no initrd= in lilo.conf, so it tried to boot with
> the one from 8.34mdk... Shouldn't rpm -i have made one?
>
If loop failed to load, there is little chance for initrd to be created.
