Mobeen:
I had the same problem when I updated to the new kernel. Did
you
install with rpm -ivh or rpm -uvh? Your previous kernel will
be there
if you used the "rpm -ivh". As far as how I solved my SCSI
loopback problem was first trying to kill off as many non
essential processes as possible and after I did I would try
the mkinitrd again but I continued to receive the message
"All you loopback devices are in use".
Well I decided to just do a shutdown so I would kill any and
all processes that existed and boot with the old 2.2.16
kernel that I kept because I used rpm -ivh and after it came
back up I had no problem doing the "mkinitrd". If you are
booting off of floppy have you tried to run mkinitrd image
after booting? And the key question is the first one I asked
is how did you do the upgrade, with rpm -ivh or rpm -uvh.
Your still Ok with the rpm -Uvh but you must use the floppy
boot method till you get this new kernel initrd image made.
You are running a SCSI system right, as I don't see the need
for a ramdisk for a non SCSI systems. If you can answer
these questions for me maybe I can help you further.
Eddie Strohmier
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Mobeen
Azhar
Sent: Tuesday, February 13, 2001 6:26 PM
To: [EMAIL PROTECTED]
Subject: Kernel upgrade from 2.2.16 to 2.2.17
Thanks for the reply, Mikkel.
Whenever I type modprobe loop, it comes back and says Can't
locate module
loop. I have a functioning 2.2.16 kernel on a floppy (made
with mkbootdisk)
that I am booting from currently, do I need to somehow put
that back on my
hard drive under /boot before I can do a modprobe loop?
--Moby
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Mikkel
L. Ellertson
> Sent: Tuesday, February 13, 2001 1708
> To: Redhat-List
> Subject: Re: (no subject)
>
>
> On Tue, 13 Feb 2001, Mobeen Azhar wrote:
>
> > Hello all, I upgraded the kernel on my RH 7.0 box from
2.2.16-22 to
> > 2.2.17-14. I successfully installed the following RPMS:
> >
> > kernel-2.2.17-14.i386.rpm
> > kernel-pcmcia-cs-2.2.17-14.i386.rpm
> > kernel-utils-2.2.17-14.i386.rpm
> >
> > All the RPMS installed without a problem. However,
whenever I
> try to run
> > mkinitrd to create a RAM disk image for the new kernel,
> mkinitrd bombs with
> > the message "All you loopback devices are in use". I
even tried to run
> > mkinitrd in single user mode to no avail (thinking
perhaps some
> other stuff
> > running on the box might be using up the loopback
devices). I
> checked and
> > made sure that I have /dev/loop0 through /dev/loop15.
> >
> > Although I am relatively new to Linux, I have done
kernel
> upgrades in the
> > past without a problem. I cannot figure out what is
going
> wrong this time!
> > My system is using mkinitrd from the mkintrd-2.6-1 RPM.
Does
> anyone have
> > any suggestions how to overcome this last hurdle in the
kernel upgade?
> >
> > Thanks in advance for any help,
> > --Moby
> >
> >
> Try running "modprobe loop" before running makeing the RAM
disk.
> Sometimes the module doesn't get loaded when it should.
>
> 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
>
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
