LILO error in 12.1 install

get00x · 05-03-2008, 07:35 PM

Hi all,

Grabbed the new 12.1 cd1 iso with bittorrent and started installing it inside my usual vmware-vm meant for experiments with slack. Everything went really smooth, but after I had configured LILO in the installation (expert mode) and pressed Install, I got the following error:

Code:

sbin/liloconfig: sbin/liloconfig: 1077: lilo: not found

Sorry, but the attempt to install LILO has returned an error, so LILO has not
been correctly installed. You'll have to use a bootdisk to start your machine
instead. It should still be possible to get LILO working by editing the
/etc/lilo.conf and reinstalling LILO manually.
See the LILO man page and documentation in /usr/doc/lilo/ for more help. The
error message may be seen above.

Finished the installation and executed "/mnt/sbin/lilo -r /mnt", not sure if it was needed or not. There was some warnings btw, but no further errors. It turned out good anyway, 12.1 booted all fine, so this is just some sort of heads up I guess.

Here's the LILO conf if anyone's interested. Oh, and it was setup to install to MBR.

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
lba32 # Allow booting past 1024th cylinder with a recent BIOS
boot = /dev/hda
#compact # faster, but won't work on all systems.
# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255
# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Append any additional kernel parameters:
append=" vt.default_utf8=0"
prompt
timeout = 50
# VESA framebuffer console @ 800x600x256
vga = 771
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda1
label = LNX-2.6.24.5
read-only # Partitions should be mounted read-only for checking
# Linux bootable partition config ends

Smedley · 05-03-2008, 10:04 PM

Did you do a "Simple" lilo install or "Expert"?

T3slider · 05-03-2008, 10:20 PM

Quote:

Originally Posted by get00x

Everything went really smooth, but after I had configured LILO in the installation (expert mode)

Quote:

Originally Posted by Smedley

Did you do a "Simple" lilo install or "Expert"?

I'm guessing expert...

Is the error reproducible if you run `liloconfig`?

Smedley · 05-03-2008, 10:24 PM

Quote:

Originally Posted by T3slider

I'm guessing expert...

Is the error reproducible if you run `liloconfig`?

Yup, I'm a 'tard........totally missed that.

T3slider · 05-03-2008, 10:46 PM

Quote:

Originally Posted by Smedley

Yup, I'm a 'tard........totally missed that.

It's alright -- I missed a similar piece of information that was nicely hilighted in red not too long ago.

get00x · 05-04-2008, 02:24 AM

Quote:

Originally Posted by T3slider

Is the error reproducible if you run `liloconfig`?

Nope. Not while inside the installed slackware anyway, perhaps when still using the boot disk.. I'll have to check that out.

konsolebox · 05-04-2008, 03:31 AM

are you still in the boot cd or is it already the new system you installed.. if in the boot cd.. do

Code:

mount --bind /proc /mnt/proc; chroot /mnt; which lilo; lilo

taking that your root filesystem is mounted in /mnt