Submitted 27-Jul-00 by Thomas Lockhart:
> 1) after RPM installation, the softlinks in /boot were not consistant
> for using the 2.2.16 kernel. Several links pointed at 2.2.15 items.
Only the vmlinuz and initrd links need to be correct. System.map will
correct itself at boot time.
> 2) there is no initrd file for 2.2.16
> 3) mkinitrd declined to create one, saying that it couldn't find a loop
> device. It suggested running insmod loop.o, but that file is missing
> (see (5) below).
You need to insmod loop *before* upgrading the kernel
>
> Well, afaik initrd isn't necessary (otherwise, the kernel update would
> have provided it, right?).
The RPM upgrade process has no clue about your hardware configuration
and therefore doesn't know to create the initrd.
> 4) unable to boot. I suspect that it is missing the necessary Adaptec
> SCSI driver.
Correct. They would be in the initrd.
> 5) some 2.2.15-4mdk kernel resources are missing, so I can't go back
> afaik. For example, the RPM upgrade removed the contents of
> /lib/modules/2.2.15xxx.
Rule #1 of RPM based kernel upgrades: do rpm -i NOT rpm -U. You want
both kernels on your machine until you are certain that the new one
works well.
--
_
_|_|_
( ) * Anton Graham
/v\ / <[EMAIL PROTECTED]>
/( )X
(m_m) GPG ID: 18F78541
Penguin Powered!
