LILO-config error

[Taldor]

I've edited the lilo.conf file (as root). When I try to change the configuration with the lilo-config script/shell/program/whatever...
I get a message like "are you sure to ...?[Yes]" so I type "y". Then I starts, but after two seconds or so I get this message:

Shell session stopped with status 1

From c++ I learned that it should stop with status 0, but I don't have a clue what I did wrong.

This is my new lilo.conf file:

# Edited: the first line, timeout, default and the available OS's and their names.
# /etc/lilo.conf - See: 'lilo(' and 'lilo.conf(5)',
# --------------- 'install-mbr(', '/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/hda6

# 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

# Default menu for Debian. (Using the images from debian-bootscreen)
# from Philipp Wolfer <phil@newswriter.org>.
bitmap=/usr/share/lilo/contrib/debian.bmp
bmp-colors=1,,0,2,,0
bmp-table=120p,173p,1,15,17
bmp-timer=254p,432p,1,0,0

# Install the specified file as the new boot sector.
# LILO supports built in boot sectory, you only need
# to specify the type, choose one from 'text', 'menu' or 'bitmap'.
# new: install=bmp old: install=/boot/boot-bmp.b
# new: install=text old: install=/boot/boot-text.b
# new: install=menu old: install=/boot/boot-menu.b or boot.b
# default: 'menu' is default, unless you have a bitmap= line
# Note: install=bmp must be used to see the bitmap menu.
# install=menu
# install=bmp
install=bmp

# Specifies the number of _tenths_ of a second LILO should
# wait before booting the first image. LILO
# doesn't wait if DELAY is omitted or if DELAY is set to zero.

delay=10

# Prompt to use certaing image. If prompt is specified without timeout,
# boot will not take place unless you hit RETURN
prompt
timeout=150

# Specifies the location of the map file. If MAP is
# omitted, a file /boot/map is used.
map=/boot/map

# Specifies the VGA text mode that should be selected when
# booting. The following values are recognized (case is ignored):
# NORMAL select normal 80x25 text mode.
# EXTENDED select 80x50 text mode. The word EXTENDED can be
# abbreviated to EXT.
# ASK stop and ask for user input (at boot time).
# <number> use the corresponding text mode. A list of available modes
# can be obtained by booting with vga=ask and pressing [Enter].
vga=791

# 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('.
#
# password=tatercounter2000

# 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
# 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=""
# Boot up WinXP by default.
#
default="WinXP(hda1)"

image=/boot/vmlinuz
label="LinuxNoMouse"
initrd=/boot/initrd.img
append="fromhd=/dev/hda8 ramdisk_size=100000 init=/etc/init lang=be apm=power-off hda=scsi hdb=scsi hdc=scsi screen=1280x1024 home=scan myconfig=scan nomce BOOT_IMAGE=linux26"
read-only
image=/boot/vmlinuz-2.4.26
label="Linux(2.4)-1NoMouse"
initrd=/boot/initrd.img-2.4.26
append="fromhd=/dev/hda8 ramdisk_size=100000 init=/etc/init lang=be apm=power-off hda=scsi hdb=scsi hdc=scsi screen=1280x1024 home=scan myconfig=scan nomce BOOT_IMAGE=linux26"
read-only

image=/boot/vmlinuz-2.6.6
label="Linux(2.6)-2"
initrd=/boot/initrd.img-2.6.6
append="fromhd=/dev/hda8 ramdisk_size=100000 init=/etc/init lang=be apm=power-off hda=scsi hdb=scsi hdc=scsi screen=1280x1024 home=scan myconfig=scan nomce BOOT_IMAGE=linux26"
read-only

# 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="WinXP(hda1)"
other=/dev/hda3
label="Freedos(hda3)"
other=/dev/hda8
label="Knoppix(hda"

[CrashedAgain]

???? lilo-config script/shell/program/whatever...
After you have edited lilo.config to suit your needs, just run lilo.
As root, just type 'lilo' .
I think the config shell script 'thing' is for editing lilo.config, which you have already done.

[Cuddles]

Taldor,

Sorry, I've never run the program lilo-config, I prefer to just "edit" the lilo.conf file directly, never had a problem, unless I made one of my labels too long, but, then again, lilo being run after the edit of the file, has yelled at me, and I have made the changes it has found as problems...

I am also just running Knoppix 2.6.6, even though the 2.4 kernel still is bootable in lilo. I don't have as "extensive" of a boot as you do, only Knoppix.

I guess you can wait to see if someone else has problems using the lilo-config program, and it could be a "problem", at least you can still just edit the file manually, in the mean time.

This could be a dumb thought, but if the "prompt" says it "defaults" to YES, you can either hit [enter] or type in yes - not sure if just entering "y" is enough - never looked at the script / code to see if it may just be "looking" for a "y" or anything else, kinda thing. ( just a thought )

Ms. Cuddles

[pstoddard]

I ran into a problem too running lilo after editing the config file. Got an error that bitmap=/usr/share/lilo/contrib/debian.bmp doesn't exist. so I edited this line in the lilo.conf file to read bitmap=/boot/debian.bmp and lilo ran fine.

I also had to use /sbin/lilo to update it since just running lilo it gave an error that command lilo didn't exist.

[Taldor]

It works now!
As you said, I typed "lilo" in the root command line and i gave an error: "Linux(2.4)-1NoMouse" is to long (fixed). After that I got two warnings: "CHANGE AUTOMATIC assumed with /dev/hda1" and the same warning for /hda3.

When I boot /hda1 or /hda3 I can't see the other anymore.
[edit] warnings fixed

[CrashedAgain]

It works now!
As you said, I typed "lilo" in the root command line and i gave an error: "Linux(2.4)-1NoMouse" is to long (fixed). After that I got two warnings: "CHANGE AUTOMATIC assumed with /dev/hda1" and the same warning for /hda3.

When I boot /hda1 or /hda3 I can't see the other anymore.

There is some info on 'change automatic' in manpage for lilo.conf but I confess I can't figure out what it's referring to.
I assume you mean when you boot hda1 (XP), windows cannot see hda3 (Freedos). Maybe this is normal, Win can't see linux formatted drives either, although I would think freedos should be able to see the XP drive.

default="WinXP(hda1)"

image=/boot/vmlinuz
label="LinuxNoMouse"
initrd=/boot/initrd.img
append="fromhd=/dev/hda8 ramdisk_size=100000 init=/etc/init lang=be apm=power-off hda=scsi hdb=scsi hdc=scsi screen=1280x1024 home=scan myconfig=scan nomce BOOT_IMAGE=linux26"
read-only
image=/boot/vmlinuz-2.4.26
label="Linux(2.4)-1NoMouse"
initrd=/boot/initrd.img-2.4.26
append="fromhd=/dev/hda8 ramdisk_size=100000 init=/etc/init lang=be apm=power-off hda=scsi hdb=scsi hdc=scsi screen=1280x1024 homeCHANGE AUTOMATIC assumed with /dev/hda1=scan myconfig=scan nomce BOOT_IMAGE=linux26"
read-only

image=/boot/vmlinuz-2.6.6
label="Linux(2.6)-2"
initrd=/boot/initrd.img-2.6.6
append="fromhd=/dev/hda8 ramdisk_size=100000 init=/etc/init lang=be apm=power-off hda=scsi hdb=scsi hdc=scsi screen=1280x1024 home=scan myconfig=scan nomce BOOT_IMAGE=linux26"
read-only

# 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="WinXP(hda1)"
other=/dev/hda3
label="Freedos(hda3)"
other=/dev/hda8
label="Knoppix(hda"

There is no need for the last line; you will no doubt find it doesn't do anything. Linux systems need a boot image etc specified which you have done in the 'Linux' entries above. There doesn't appear to be anything in the Linux 2.4 entries which would stop the mouse from working so I don't see why they are specified 'no mouse'.

Otherwise looks OK.