I need a help with Lilo

[vladx]

I can't boot my new custom kernel. Only old kernel booting
I added some lines in etc/lilo.conf
Label=Knoppix
Label=Fail-Safe

run sbin/lilo and bellow result...

Added Fail-Safe
Added Knoppix
Skipping /vmlinuz.old
Added WinNT(hda1)
Fatal: Default image doesn't exist


The old lilo menu coming when comp starts with labels Linux and WinNT(hda1)
I cant see there Knoppix, Fail-Safe...

Sure knoppix starts with old kernel

Someone replay this post please

[todsr1]

Custom compiling a kernel is not something that should be taken lightly. Could you post the entire contents of your /etc/lilo.conf file and the output of the commands 'ls -ltr /vmlinuz*' and 'ls -ltr /boot/vmlinuz*'

[vladx]

l

vga=791
# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# ---------------       `install-mbr(8)', `/usr/share/doc/lilo/',
#                       and `/usr/share/doc/mbr/'.

# +---------------------------------------------------------------+
# |                        !! Reminder !!                         |
# |                                                               |
# | Don't forget to run `lilo' after you make changes to this     |
# | conffile, `/boot/bootmess.txt', or install a new kernel.  The |
# | computer will most likely fail to boot if a kernel-image      |
# | post-install script or you don't remember to run `lilo'.      |
# |                                                               |
# +---------------------------------------------------------------+

# Support LBA for large hard disks.
#
lba32

# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
#disk=/dev/hde
#    bios=0x81

#disk=/dev/sda
#    bios=0x80

# Specifies the boot device.  This is where Lilo installs its boot
# block.  It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda

# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda2

# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller.  Using `compact' is especially recommended when
# booting from a floppy disk.  It is disabled here by default
# because it doesn't always work.
#
# compact

# Installs the specified file as the new boot sector
# You have the choice between: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details
#
install=/boot/boot-menu.b

# Specifies the location of the map file
#
map=/boot/map

# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration.  If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well.  Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000

# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=20

# You can put a customized boot message up if you like.  If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress.  `single-key' goes with the `alias' lines in the
# `image' configurations below.  eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
prompt
timeout=150
#	prompt
#	single-key
#	delay=100
#	timeout=100

# Kernel command line options that apply to all installed images go
# here.  See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""
append="hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi apm=power-off nomce"

# Boot up Linux by default.
#
default=Linux

image=/boot/vmlinuz-2.4.22-xfs
	label=Fail-Safe
	initrd=/boot/initrd.gz
	read-only
#	restricted
#	alias=1

image=/boot/vmlinuz-2.4.22-xfs-test
        label=Knoppix
        read-only

image=/vmlinuz.old
	label=LinuxOLD
	read-only
	optional
#	restricted
#	alias=2

# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
#	label=HURD
#	restricted
#	alias=3
other=/dev/hda1
  label="WinNT(hda1)"

root@navigator:~# ls -ltr /vmlinuz*
lrwxrwxrwx 1 root root 23 Nov 17 10:36 /vmlinuz -> boot/vmlinuz -2.4.22-xfs
root@navigator:~# ls -ltr /boot/vmlinuz*
-rw-r--r-- 1 root root 921593 Oct 3 21:01 /boot/vmlinuz-2.4.22-xfs
lrwxrwxrwx 1 root root 18 Nov 17 10:23 /boot/vmlinuz.old -> vml inuz-2.4.22-xfs
-rw-r--r-- 1 root root 970618 Nov 17 13:31 /boot/vmlinuz-2.4.22-xfs -test
lrwxrwxrwx 1 root root 23 Nov 17 13:31 /boot/vmlinuz -> vmlinuz -2.4.22-xfs-test
root@navigator:~#


But in the boot lilo menu only Linux and WinNT(hda1)

[Stephen]

l

vga=791
# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# ---------------       `install-mbr(8)', `/usr/share/doc/lilo/',
#                       and `/usr/share/doc/mbr/'.

# +---------------------------------------------------------------+
# |                        !! Reminder !!                         |
# |                                                               |
# | Don't forget to run `lilo' after you make changes to this     |
# | conffile, `/boot/bootmess.txt', or install a new kernel.  The |
# | computer will most likely fail to boot if a kernel-image      |
# | post-install script or you don't remember to run `lilo'.      |
# |                                                               |
# +---------------------------------------------------------------+

# Support LBA for large hard disks.
#
lba32

# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
#disk=/dev/hde
#    bios=0x81

#disk=/dev/sda
#    bios=0x80

# Specifies the boot device.  This is where Lilo installs its boot
# block.  It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda

# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda2

# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller.  Using `compact' is especially recommended when
# booting from a floppy disk.  It is disabled here by default
# because it doesn't always work.
#
# compact

# Installs the specified file as the new boot sector
# You have the choice between: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details
#
install=/boot/boot-menu.b

# Specifies the location of the map file
#
map=/boot/map

# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration.  If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well.  Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000

# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=20

# You can put a customized boot message up if you like.  If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress.  `single-key' goes with the `alias' lines in the
# `image' configurations below.  eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
prompt
timeout=150
#	prompt
#	single-key
#	delay=100
#	timeout=100

# Kernel command line options that apply to all installed images go
# here.  See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""
append="hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi apm=power-off nomce"

# Boot up Linux by default.
#
default=Linux

image=/boot/vmlinuz-2.4.22-xfs
	label=Fail-Safe
	initrd=/boot/initrd.gz
	read-only
#	restricted
#	alias=1

image=/boot/vmlinuz-2.4.22-xfs-test
        label=Knoppix
        read-only

image=/vmlinuz.old
	label=LinuxOLD
	read-only
	optional
#	restricted
#	alias=2

# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
#	label=HURD
#	restricted
#	alias=3
other=/dev/hda1
  label="WinNT(hda1)"

root@navigator:~# ls -ltr /vmlinuz*
lrwxrwxrwx 1 root root 23 Nov 17 10:36 /vmlinuz -> boot/vmlinuz -2.4.22-xfs
root@navigator:~# ls -ltr /boot/vmlinuz*
-rw-r--r-- 1 root root 921593 Oct 3 21:01 /boot/vmlinuz-2.4.22-xfs
lrwxrwxrwx 1 root root 18 Nov 17 10:23 /boot/vmlinuz.old -> vml inuz-2.4.22-xfs
-rw-r--r-- 1 root root 970618 Nov 17 13:31 /boot/vmlinuz-2.4.22-xfs -test
lrwxrwxrwx 1 root root 23 Nov 17 13:31 /boot/vmlinuz -> vmlinuz -2.4.22-xfs-test
root@navigator:~#


But in the boot lilo menu only Linux and WinNT(hda1)

You have the symbolic links wrong and with the errors lilo will ignore the entries with them and not display them in the menu. This is how I have set it up on my computer:

HappyTux:/home/stephen# ll /vmlinuz*
lrwxrwxrwx    1 root     root           26 2003-10-20 04:56 /vmlinuz -> boot/vmlinuz-2.4.22.031019
lrwxrwxrwx    1 root     root           35 2003-08-29 02:36 /vmlinuz.failsafe -> /boot/vmlinuz-2.4.20-bf2.4-failsafe
lrwxrwxrwx    1 root     root           26 2003-09-15 03:38 /vmlinuz.old -> boot/vmlinuz-2.4.22.030915

HappyTux:/home/stephen# ll /boot/vmlinuz-2.4.2*
-rw-r--r--    1 root     root         1.3M 2003-08-29 02:31 /boot/vmlinuz-2.4.20-bf2.4-failsafe
-rw-r--r--    1 root     root         993K 2003-09-15 03:24 /boot/vmlinuz-2.4.22.030915
-rw-r--r--    1 root     root         973K 2003-10-19 23:18 /boot/vmlinuz-2.4.22.031019

The /etc/lilo.conf entries:

# Boot up Linux by default.
#
default=Linux

image=/vmlinuz
        label=Linux
        read-only
#       restricted
#       alias=1

image=/vmlinuz.old
        label=LinuxOLD
        read-only
        optional
#       restricted
#       alias=2

image=/vmlinuz.failsafe
        label=LinuxFailsafe
        read-only
        optional

# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
other=/dev/hdb
        label=KDE_CVS
#       restricted
#       alias=3

BTW how did you compile the new kernel it looks like you did not use the Debian method with the kernel-package program it will make a .deb package that you can install and it will take care of all this trouble you are having with updating the lilo.conf and making the correct symbolic links. A guide to creating a custom Debian package with the kernel-package tool. And now that I look at the posts again I see that when you have run /sbin/lilo after having made the changes you did to the lilo.conf it errored because you have no label=Linux entry left in the file so it is still using the old configuration written to the MBR. You need to fix the links and clean up the lilo.conf if you are not going to use a Linux entry as the default=Linux then you have to change it to the name of the label=of_image_you_want_to_use in the sections below it.

[knulle]

Hi !

The reason for error "Fatal: Default image doesn't exist" is that the statement default= must specify a valid label defined in a image-section. In your lilo.conf there is no
image= ...
label=linux
so
default=Linux
will cause this error.

Change it to
default=Knoppix
or which system you want to us as the default booting system if timeout occurs and no system is manually selected.

(had the same error and it took me a whil for finding the reason)

The "skipping"-message occured, because that image coudn't be found too. so this system will not appear in the lilo-booting-menu.

cheers

Knut