"Konstantin (Kastus) Shchuka" wrote:
On Wed, Dec 05, 2001 at 04:10:06PM +0000, David Spencer wrote:
copied bzImage to /boot/vmlinuz-2.4.16 copied System.map to /boot/System.map-2.4.16
# mk_initrd -k "vmlinuz-2.4.16" -i "initrd-2.4.16" -s auto
When I run this I get: no initrd required; rmdir: too few arguments
^^^^^^^^^^^^^^^^^^ because it is not defined in /etc/lilo.conf for that image.
edit /etc/lilo.conf and change kernel to 2.4.16 (doesn't remove old kernel or modules)
duplicated entry image=/boot/vmlinuz root=/dev/hda7 label=vmlinuz
as image=boot/vmlinuz-2.4.16
^^^^ should be /boot/vmlinuz-2.4.16
oops typo (in email; slash was there in lilo.conf)
root=/dev/hda7 label=vmlinuz-2.4.16
and placed it above the original so the new kernel should boot first.
Now when I run lilo I get: fatal: First boot sector doesn't have a valid LILO signature
Pretty weird. What is boot= set to in your lilo.conf?
Unchanged from the Suse stock 7.2 installation: boot=/dev/hda Have tried different values and get the same error on each occasion. Thanks, Dave.