[SOLVED] LILO does not display second OS.

saulgoode · 07-23-2014, 04:10 PM

Quote:

Originally Posted by Randicus Draco Albus

Success! I am making this post with the Slackware system. So the problem was not having "prompt" in lilo.conf. Thank you. Although I may need to fiddle a little more. For some reason the boot menu is an ugly combination of red background and white letters, instead of the usual dull blue. Oh, the horror!

http://www.linuxquestions.org/questi...colors-343807/

Or you could examine Slackware's lilo.conf for how to use a bitmap menu.

irgunII · 07-25-2014, 08:36 PM

(I know you've marked this as 'SOLVED', but I just wanna add to it some)

I only use / to put lilo on, always have if I remember right (at least I can't remember ever putting it on mbr).

Here's my lilo for my Slackware 14.1-64 (I'm deleting all the vesa, vga stuff not used):

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sdb2
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="lba32 vt.default_utf8=1"
prompt
#timeout = 300
# VESA framebuffer console @ 1024x768x64k
vga = 791
#
# ramdisk = 0     # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sdb2
  label = Slackware64
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends

And here is for my Slackware 14.1-32 (my main, slackware, by the way):

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
lba32
append=" vt.default_utf8=1"
boot = /dev/sda
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:
prompt
#timeout = 300
# VESA framebuffer console @ 1024x768x64k
vga = 791
#
# ramdisk = 0     # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda1
  label = Slack-main
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
# Other Slackware bootable partition config begins
other = /dev/sdb2
  label = Slackware64
  table = /dev/sdb

Not sure why you're getting such wierd colors. Here's mine...

(By the way, does anyone know how to get a snapshot of this lilo screen when it shows up instead of having to use a camera?)

astrogeek · 07-25-2014, 08:41 PM

Quote:

Originally Posted by irgunII

(By the way, does anyone know how to get a snapshot of this lilo screen when it shows up instead of having to use a camera?)

At first thought that would be kind of difficult as there is no OS running at that point...

On second thought, install to a VM, then do a screenshot from the host OS...?